<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On 6 Jan 2016, at 17:40, William Bader <<a href="mailto:williambader@hotmail.com">williambader@hotmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><br><div>> Date: Wed, 6 Jan 2016 11:01:34 -0500<br>> From: <a href="mailto:John@wexfordpress.com">John@wexfordpress.com</a><br>> To: <a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>> Subject: Re: [scribus-dev] Breakdown of Scribus source code.<br>> <br>> On Tue, 5 Jan 2016 17:40:36 +0000<br>> Craig Bradney <<a href="mailto:cbradney@scribus.info">cbradney@scribus.info</a>> wrote:<br>> <br>> > <br>> > <br>> > > On 5 Jan 2016, at 15:59, John Culleton<br>> > > <<a href="mailto:John@wexfordpress.com">John@wexfordpress.com</a>> wrote:<br>> > > <br>> > > I am about to embark on a project to list the<br>> > > C++ modules of Scribus in an hierarchical list<br>> > > such as<br>> > > Top module<br>> > > module x<br>> > > module y<br>> > > module aa<br>> > > <br>> > > Where modules x and y are called from Top<br>> > > module and module aa is called from module y<br>> > > etc. <br>> > > <br>> > > In other words a kind of a hierarchy chart <br>> > > without the graphics.<br>> > > <br>> > > I am going to do this just for my own use in<br>> > > understanding the structure of the stuff I<br>> > > compile every night. If there is another tool<br>> > > to assist in my understanding of what fits<br>> > > where please point me to it. I really don't<br>> > > want to reinvent the wheel. <br>> > > <br>> > > -- <br>> > > <br>> > <br>> > I started something on the wiki that documents<br>> > some of this awhile ago. It's only very basic<br>> > though.<br>> > <br>> > <a href="http://wiki.scribus.net/canvas/Source_Code/scribus">http://wiki.scribus.net/canvas/Source_Code/scribus</a><br>> > <br>> <br>> Useful nonetheless. Thanks.<br><br></div><div><br></div><div>Would using a system based on special comments in the source be easier to maintain?</div><div><br></div><div>Someone has already run Scribus 1.5 through doxygen: <a href="http://fossies.org/dox/scribus-1.5.0/" target="_blank" style="font-size: 12pt;">http://fossies.org/dox/scribus-1.5.0/</a></div><div><br></div><div>Regards, William Bader, Director of Research and Development at SCS, <a href="http://www.newspapersystems.com">http://www.newspapersystems.com</a></div><div><br></div></div></div></blockquote><br><div>Sure</div><div><br></div><div>Doxygen can be run to produce that. The stuff is all in the source already but the comments don't exist in the code to define the design or decisions made.</div><div><br></div><div>Craig</div></body></html>