Re: [Babeldoc-devel] Babeldoc 1.2 Happenings

[Dejan K. <dej...@nb...>]

What about using existing module mechanism but separate core from non-core
modules? Maybe we could even split some modules on more pieces. For example,
current conversion module contains both flat to xml conversions and
conversions from excel to xml files. Now, I guess not all users will need to
use both - I think it should be possible to let them choose which modules
they want to use.... No need to download all 12 MB or more (Babeldoc is
growing every day) if they want to use some simple stages that would need
only 2-3 MB!

When I am talking about core modules I mean on those modules that are used
more frequently and that are used by other modules. IMO we should agree on
which parts of Babeldoc should be "core". Not all classes from current core
module should remain there. Also, I think some classes from other modules
should be packaged into "core" distribution.

My idea was to make new SF project wich would contain babeldoc modules. That
is - pipeline stages, scanner worker implementations, maybe even journal
implementations...  The point is that Babeldoc has very basic architecture
that could be applied in many different contexts (For example in my company
we plan to use Babeldoc for exchanging documents with banks (I work in
Central Bank) and we are also using it for updating our website with
exchange rates etc..). We already have pipeline stages that does so many
different things and there are more and more users with some great ideas
asking if we need some piece of code they write. If we create separate SF
project we could grant CVS rigths to everyone who has some interesing idea
and code. And these "plugins" should be released separately from the core
distribution. So when user needs FO conversion he could download FO module
with all necessary liraries and classes.

Dejan

----- Original Message ----- 
From: "Bruce McDonald" <br...@mc...>
To: <bab...@li...>
Sent: Thursday, October 02, 2003 6:08 AM
Subject: [Babeldoc-devel] Babeldoc 1.2 Happenings


> Hello all!
>
> Babeldoc 1.2 is coming up.  Thank you to all those who made this a great
> release.  Babeldoc is both deeper and wider in all its areas.  Nothing has
> been untouched.  From multitasking to the new scanner to the modular
build.
> Things that need work are J2EE, GUI and web  (Just as ask Bill Harrelson:
> keep talking Bill, we can make this work and get Babeldoc running better).
> Thanks to Qin who came with a pipeline configuration that obviously breaks
> Babeldoc (Qin's arrangement was that the current working directory
contained
> the BABELDOC_USER directory with all the configuration files -
investigation
> is required here - I volunteer, suggestions/patches welcomed).
>
> Just keep coming with the work - its been great working with you all.
>
> Dejan and I were talking today about opening up the modules.  We recognize
> that Babeldoc needs to get bigger than the standard set of modules that it
> comes with.  The issue is then how to manage the creation of modules
(think
> plugins going forward).  Creating and managing modules should be a simple
and
> straightforward.  This includes how and where Babeldoc module source code
> gets stored.   Personally I envisage a command that would download or
> otherwise locate and retrieve a Babeldoc module for building or running.
> (this implies some kind of registry:  UDDI?)    How are you developing
using
> Babeldoc and how do you think that we should be developing with Babeldoc
in
> the future?
>
> regards,
> Bruce.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel