[scribus-dev] Breakdown of Scribus source code.

Craig Bradney cbradney at scribus.info
Wed Jan 6 18:03:05 UTC 2016



> On 6 Jan 2016, at 17:40, William Bader <williambader at hotmail.com> wrote:
> 
> 
> > Date: Wed, 6 Jan 2016 11:01:34 -0500
> > From: John at wexfordpress.com
> > To: scribus-dev at lists.scribus.net
> > Subject: Re: [scribus-dev] Breakdown of Scribus source code.
> > 
> > On Tue, 5 Jan 2016 17:40:36 +0000
> > Craig Bradney <cbradney at scribus.info> wrote:
> > 
> > > 
> > > 
> > > > On 5 Jan 2016, at 15:59, John Culleton
> > > > <John at wexfordpress.com> wrote:
> > > > 
> > > > I am about to embark on a project to list the
> > > > C++ modules of Scribus in an hierarchical list
> > > > such as
> > > > Top module
> > > > module x
> > > > module y
> > > > module aa
> > > > 
> > > > Where modules x and y are called from Top
> > > > module and module aa is called from module y
> > > > etc. 
> > > > 
> > > > In other words a kind of a hierarchy chart 
> > > > without the graphics.
> > > > 
> > > > I am going to do this just for my own use in
> > > > understanding the structure of the stuff I
> > > > compile every night. If there is another tool
> > > > to assist in my understanding of what fits
> > > > where please point me to it. I really don't
> > > > want to reinvent the wheel. 
> > > > 
> > > > -- 
> > > > 
> > > 
> > > I started something on the wiki that documents
> > > some of this awhile ago. It's only very basic
> > > though.
> > > 
> > > http://wiki.scribus.net/canvas/Source_Code/scribus
> > > 
> > 
> > Useful nonetheless. Thanks.
> 
> 
> Would using a system based on special comments in the source be easier to maintain?
> 
> Someone has already run Scribus 1.5 through doxygen: http://fossies.org/dox/scribus-1.5.0/
> 
> Regards, William Bader, Director of Research and Development at SCS, http://www.newspapersystems.com
> 

Sure

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.

Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20160106/cb49d78f/attachment.html>


More information about the scribus-dev mailing list