|
From: Mark de W. <ko...@xs...> - 2006-01-06 20:26:05
|
On Thu, Dec 22, 2005 at 09:49:35PM +0100, Michalis Kamburelis wrote: > Mark de wever wrote: > >On Thu, Dec 15, 2005 at 09:05:28AM +0100, Michalis Kamburelis wrote: > > > >>Mark de Wever wrote: > >> > > > >[..] > > > >>a) prepare another image img/defined_in_implementation.gif (based on > >>e.g. img/private.gif in pasdoc sources) > >> > > > >FYI the images in img are not used in the output, in fact they're not > >the same as in the output. I'm putting my image in this directory based > >upon the images as used in the output. > > > > Ups, you're right. Looking at CVS logs, it seems that at the beginning > images in img/*.gif directory corresponded to include files in > source/component/*.inc. But then on August 4th, 2003 new version of > images were committed -- images in source/component/*.inc were updated, > but their corresponding files in img/*.gif were left outdated... > > I just fixed this situation and did some related cleaning that was > pending. Up-to-date *.gif images are now placed inside > source/components/images/, along with their corresponding *.gif.inc > files and a small Makefile to use tools/file_to_pascal_data program to > convert between *.gif and *.gif.inc files. Old images in img/ and old > include files in source/component/ are removed now. This should make > this whole situation cleaner. [..] Should pasdoc.css be also be put in the same directory so it's also always updated? Regards, Mark de Wever |