|
From: Artur H. <ko...@pl...> - 2003-10-02 20:15:13
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well,
They are not changes indeed, they are rather adds to existing
set of features. I always try to preserve current functionality
and keep it compatible with earlier versions.
So if something works bad on your system let me know.
But lets present new features and ideas:
1. Started to add support for Java tools. They are important for
at least 2 reasons:
- (S)DocBook XSLT extensions are only implemented for Java tools
- PDF generation (FOP -> PDF) is only implemented in Java tools
2. Some limited support for catalogs for Java tools
3. Let me return to keeping docbook XSLT in CVS repository issue.
I don't like this idea, however I agree that we should provide
complete environment with all necessary libraries.
Our needs are not limited to those XSLT templates but I see also
some Java jars as usefull, at least SDocBook DTD (because we use
it for our guides), fop library to generate PDFs and probably some more.
Keeping all libraries in CVS repository forces us to use outdated
versions or constant updating our repository with new releases.
So I propose to not keep external libraries in our CVS repository at all.
But on the other hand we should include them in release of our
environment. So joining all necessary external libraries should be
part of package build process.
Since they are all available on the net, it seems to me easy to create
appropriate script downloading, unpacking and preconfiguring them.
This script could be used as an automatic tool for building generguide
release or for downloading libraries when generguide is used directly
from CVS.
I became real user of generguide project. I use it for 2 different kinds
of documentation development.
At work I base on Generguide our internal developers guide with some
modifications - use all features of generguide and for separate document
written in Sdocbook so I use generguide only script and libraries.
And as a real user I try to change generguide to my needs. I hope
this is correct, if not let me know I will revisit my approach.
I understand that all important changes should be discussed first but
if I have to do something I have a choice:
1. to write separate tool for this
or
2. to extend generguide with lacking feature.
Below I present what I am going to do in very short future:
1. Complete support for Java tools
2. Support for generating PDF files (FOP)
3. Script downloading and installing in generguide hierarchy
the last releases of all necessary libraries
- docbook xsl
- fop
- sdocbook dtds (they are necessary for complete catalogs support)
4. Complete support for both cygwin and linux systems.
And probably (I am not sure yet if I will be able)
5. Generguide HOWTO
Assuming you agree with my changes I have one issue:
Do you prefer to develop Java-tools support in separate
script or include it in existing one?
1. Separate scripts make them a little bit simpler however forces
us to do some things in two places
2. One script will become a little bit complex but many actions will
be implemented only in one place.
I prefer to do one script now and maybe later divide it into
more parts.
Artur
- --
Artur Hefczyc "Don't change people, just live with them."
Open Source Developer:
http://www.geotools.org/
http://generguide.sourceforge.net/
http://wttools.sourceforge.net/
http://maven-plugins.sourceforge.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/fIcs0/6x1bjSKPkRAl5HAJ9SVN4xay76Pa8DBBWAFKVQBdBFHgCfXCnN
9IWgX3WxLEQiuAWRCt53yyM=
=FVYo
-----END PGP SIGNATURE-----
|