babeldoc-devel

[Babeldoc-devel] Temp branch

[Michael A. <mic...@ze...>]

Hi,

FYI:
I've created a branch called TEMP_MIKEA, which contains some development
work that I'm busy with.  It is intended that once the maintenance
branch for 1.2 is created, this temp branch will be merged with the
HEAD.

Cheers...


MikeA

Re: [Babeldoc-devel] Temp branch

[Bruce M. <br...@mc...>]

Ok,  can you give some idea (at the merge time) what everything is?

On Wednesday 12 November 2003 06:10 pm, Michael Ansley wrote:
> Hi,
>
> FYI:
> I've created a branch called TEMP_MIKEA, which contains some development
> work that I'm busy with.  It is intended that once the maintenance
> branch for 1.2 is created, this temp branch will be merged with the
> HEAD.
>
> Cheers...
>
>
> MikeA
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

[Michael A. <mic...@ze...>]

Hi,

Yes, of course.

If anybody is interested in the work (jmx scanner and jfreereports
stage), feel free to contact me and help out with development.

Cheers...


MikeA




On Wed, 2003-11-12 at 23:24, Bruce McDonald wrote:
> Ok,  can you give some idea (at the merge time) what everything is?
> 
> On Wednesday 12 November 2003 06:10 pm, Michael Ansley wrote:
> > Hi,
> >
> > FYI:
> > I've created a branch called TEMP_MIKEA, which contains some development
> > work that I'm busy with.  It is intended that once the maintenance
> > branch for 1.2 is created, this temp branch will be merged with the
> > HEAD.
> >
> > Cheers...
> >
> >
> > MikeA
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

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

We should really think about new Babeldoc structure in post 1.2 versions. I
guess that there will be more and more features that not everybody will use.
So it does make sense to include only necessery classes in the main package.
All other modules (including pipeline stages and scanner workers) should be
downloaded separately. That's why I put jabber module in separate cvs
module. Unfortunatelly we really don't have plan how this all should look
like (developing and installing new modules) so it just sit there waiting
for its time ;).

So maybe it is time to start thinking about separating classes into modules.
Or we should let this for Babeldoc 2.0 since there could possibly be many
incompatibilies?

Dejan
P.S.
Bruce, what is happening with tiki-wiki? If you need any help with setting
up please contact me.

----- Original Message ----- 
From: "Michael Ansley" <mic...@ze...>
To: <bab...@li...>
Sent: Thursday, November 13, 2003 1:46 AM
Subject: Re: [Babeldoc-devel] Temp branch


> Hi,
>
> Yes, of course.
>
> If anybody is interested in the work (jmx scanner and jfreereports
> stage), feel free to contact me and help out with development.
>
> Cheers...
>
>
> MikeA
>
>
>
>
> On Wed, 2003-11-12 at 23:24, Bruce McDonald wrote:
> > Ok,  can you give some idea (at the merge time) what everything is?
> >
> > On Wednesday 12 November 2003 06:10 pm, Michael Ansley wrote:
> > > Hi,
> > >
> > > FYI:
> > > I've created a branch called TEMP_MIKEA, which contains some
development
> > > work that I'm busy with.  It is intended that once the maintenance
> > > branch for 1.2 is created, this temp branch will be merged with the
> > > HEAD.
> > >
> > > Cheers...
> > >
> > >
> > > MikeA
> > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by: ApacheCon 2003,
> > > 16-19 November in Las Vegas. Learn firsthand the latest
> > > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > > WebDAV, and more! http://www.apachecon.com/
> > > _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

[Michael A. <mic...@ze...>]

Hi,

I think that we should probably look at guidelines for 1.3, and try to
do as much as possible without breaking anything.  I'm happy to move the
jfreereports stuff into a separate project, even for 1.3.  It's not in
1.2, so there are no issues with compatibility.

In order to set the guidelines, a few questions: what constitutes a core
module (i.e.: one which goes into com.babeldoc.core.pipeline or
com.babeldoc.scanner)?  Or a secondary (i.e.: it goes into e.g.:
com.babeldoc.sql.*), or a peripheral module (i.e.: into it's own CVS
project and separate jar files)

As far as the mechanics go, what about having a "contrib" top-level
project, into which any developer can place any experimental code. 
Postgres do this, and it seems to work quite well.  When something in
contrib is considered to have matured enough, and be demanded enough, to
be in the core system, it's migrated from contrib into the main project.

Thoughts...


MikeA

PS: I added a stack of directories before branching, I'm not sure if
they appear on the HEAD now.  Anybody getting the new directories when
they "cvs update"?


On Thu, 2003-11-13 at 07:56, Dejan Krsmanovic wrote:
> We should really think about new Babeldoc structure in post 1.2 versions. I
> guess that there will be more and more features that not everybody will use.
> So it does make sense to include only necessery classes in the main package.
> All other modules (including pipeline stages and scanner workers) should be
> downloaded separately. That's why I put jabber module in separate cvs
> module. Unfortunatelly we really don't have plan how this all should look
> like (developing and installing new modules) so it just sit there waiting
> for its time ;).
> 
> So maybe it is time to start thinking about separating classes into modules.
> Or we should let this for Babeldoc 2.0 since there could possibly be many
> incompatibilies?
> 
> Dejan
> P.S.
> Bruce, what is happening with tiki-wiki? If you need any help with setting
> up please contact me.
> 
> ----- Original Message ----- 
> From: "Michael Ansley" <mic...@ze...>
> To: <bab...@li...>
> Sent: Thursday, November 13, 2003 1:46 AM
> Subject: Re: [Babeldoc-devel] Temp branch
> 
> 
> > Hi,
> >
> > Yes, of course.
> >
> > If anybody is interested in the work (jmx scanner and jfreereports
> > stage), feel free to contact me and help out with development.
> >
> > Cheers...
> >
> >
> > MikeA
> >
> >
> >
> >
> > On Wed, 2003-11-12 at 23:24, Bruce McDonald wrote:
> > > Ok,  can you give some idea (at the merge time) what everything is?
> > >
> > > On Wednesday 12 November 2003 06:10 pm, Michael Ansley wrote:
> > > > Hi,
> > > >
> > > > FYI:
> > > > I've created a branch called TEMP_MIKEA, which contains some
> development
> > > > work that I'm busy with.  It is intended that once the maintenance
> > > > branch for 1.2 is created, this temp branch will be merged with the
> > > > HEAD.
> > > >
> > > > Cheers...
> > > >
> > > >
> > > > MikeA
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email sponsored by: ApacheCon 2003,
> > > > 16-19 November in Las Vegas. Learn firsthand the latest
> > > > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > > > WebDAV, and more! http://www.apachecon.com/
> > > > _______________________________________________
> > > > Babeldoc-devel mailing list
> > > > Bab...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by: ApacheCon 2003,
> > > 16-19 November in Las Vegas. Learn firsthand the latest
> > > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > > WebDAV, and more! http://www.apachecon.com/
> > > _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

[Bruce M. <br...@mc...>]

I dont mind moving quite a bit of current babeldoc out to modules project.  In 
my mind this includes:

babelfish
conversion
xslfo

Now, at the moment we just place these in a top level directory in the same 
tree as babeldoc - thus restricting committers to the same list as for 
babeldoc.  This could be a problem.  So your idea about another project is 
probably the right idea here.

regards,
Bruce

Tiki-wiki is not happening - how can you help with this?  Do you have a spare 
internet connected server laying around :) ?

On Thursday 13 November 2003 02:56 am, Dejan Krsmanovic wrote:
> We should really think about new Babeldoc structure in post 1.2 versions. I
> guess that there will be more and more features that not everybody will
> use. So it does make sense to include only necessery classes in the main
> package. All other modules (including pipeline stages and scanner workers)
> should be downloaded separately. That's why I put jabber module in separate
> cvs module. Unfortunatelly we really don't have plan how this all should
> look like (developing and installing new modules) so it just sit there
> waiting for its time ;).
>
> So maybe it is time to start thinking about separating classes into
> modules. Or we should let this for Babeldoc 2.0 since there could possibly
> be many incompatibilies?
>
> Dejan
> P.S.
> Bruce, what is happening with tiki-wiki? If you need any help with setting
> up please contact me.
>
> ----- Original Message -----
> From: "Michael Ansley" <mic...@ze...>
> To: <bab...@li...>
> Sent: Thursday, November 13, 2003 1:46 AM
> Subject: Re: [Babeldoc-devel] Temp branch
>
> > Hi,
> >
> > Yes, of course.
> >
> > If anybody is interested in the work (jmx scanner and jfreereports
> > stage), feel free to contact me and help out with development.
> >
> > Cheers...
> >
> >
> > MikeA
> >
> > On Wed, 2003-11-12 at 23:24, Bruce McDonald wrote:
> > > Ok,  can you give some idea (at the merge time) what everything is?
> > >
> > > On Wednesday 12 November 2003 06:10 pm, Michael Ansley wrote:
> > > > Hi,
> > > >
> > > > FYI:
> > > > I've created a branch called TEMP_MIKEA, which contains some
>
> development
>
> > > > work that I'm busy with.  It is intended that once the maintenance
> > > > branch for 1.2 is created, this temp branch will be merged with the
> > > > HEAD.
> > > >
> > > > Cheers...
> > > >
> > > >
> > > > MikeA
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.Net email sponsored by: ApacheCon 2003,
> > > > 16-19 November in Las Vegas. Learn firsthand the latest
> > > > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > > > WebDAV, and more! http://www.apachecon.com/
> > > > _______________________________________________
> > > > Babeldoc-devel mailing list
> > > > Bab...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by: ApacheCon 2003,
> > > 16-19 November in Las Vegas. Learn firsthand the latest
> > > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > > WebDAV, and more! http://www.apachecon.com/
> > > _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> > developments in Apache, PHP, Perl, XML, Java, MySQL,
> > WebDAV, and more! http://www.apachecon.com/
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

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

>
> Tiki-wiki is not happening - how can you help with this?  Do you have a
spare
> internet connected server laying around :) ?
>
Yeah, sure. How many servers do you need?! ;)
Seriously, ifyou need some help on installing tiki wiki, I could help. We
are running it in our intranet last few weeks.

Dejan

Re: [Babeldoc-devel] Temp branch

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

> I think that we should probably look at guidelines for 1.3, and try to
> do as much as possible without breaking anything.  I'm happy to move the
> jfreereports stuff into a separate project, even for 1.3.  It's not in
> 1.2, so there are no issues with compatibility.
>
> In order to set the guidelines, a few questions: what constitutes a core
> module (i.e.: one which goes into com.babeldoc.core.pipeline or
> com.babeldoc.scanner)?  Or a secondary (i.e.: it goes into e.g.:
> com.babeldoc.sql.*), or a peripheral module (i.e.: into it's own CVS
> project and separate jar files)

Well these are the issues we should talk about. I am not very satisfied with
current module organization. IMO, in core module there should be classes
needed by other modules. For example, I would put scanner classes into core
module. However, I would exclude all classes (scaner workers, pipeline
stages, journal implementations) that need some additional jars or that are
not used very often.
All other modules should be developed, maintained and downloaded separately.


> As far as the mechanics go, what about having a "contrib" top-level
> project, into which any developer can place any experimental code.
> Postgres do this, and it seems to work quite well.  When something in
> contrib is considered to have matured enough, and be demanded enough, to
> be in the core system, it's migrated from contrib into the main project.
>
> Thoughts...

I agree. I would even create this as separate CVS project so we can grant
CVS commit rights to everyone who wants.

By the way, what exactly will do your new pipeline stage (jfreereport)?

Dejan

>
> MikeA
>
> PS: I added a stack of directories before branching, I'm not sure if
> they appear on the HEAD now.  Anybody getting the new directories when
> they "cvs update"?

Re: [Babeldoc-devel] Temp branch

[Michael A. <mic...@ze...>]

Hi,

Yes,the contrib sub-project should definitely be open to as many people
as possible.  
But remember that contrib is only a breeding-ground for stable stuff. 
Current stable modules should exist within the main project, but not the
core.  And when contrib projects get stable enough, then they can
possibly be included in the main project, depending on demand (and
whether the developer team feels the module is worthwhile).  For the
main project, we can package the core system into one jar, and the
peripherals into another.  With respect, the entire system is 1.8MB in
jar files (not including the dependency files).  If we get a couple of
extra modules including in the core distro, is it really a problem?  For
me, I'm happy to have the whole thing (the main project, not contrib)
wrapped up in a single jar, and deploy that.

I think that we should ensure that by the time 1.3 is released, the
situation is no worse than it is now, and for 2.0, we rearrange.  Is
there a planned 1.4 release?

Cheers...


MikeA



On Thu, 2003-11-13 at 10:06, Dejan Krsmanovic wrote:
> > I think that we should probably look at guidelines for 1.3, and try to
> > do as much as possible without breaking anything.  I'm happy to move the
> > jfreereports stuff into a separate project, even for 1.3.  It's not in
> > 1.2, so there are no issues with compatibility.
> >
> > In order to set the guidelines, a few questions: what constitutes a core
> > module (i.e.: one which goes into com.babeldoc.core.pipeline or
> > com.babeldoc.scanner)?  Or a secondary (i.e.: it goes into e.g.:
> > com.babeldoc.sql.*), or a peripheral module (i.e.: into it's own CVS
> > project and separate jar files)
> 
> Well these are the issues we should talk about. I am not very satisfied with
> current module organization. IMO, in core module there should be classes
> needed by other modules. For example, I would put scanner classes into core
> module. However, I would exclude all classes (scaner workers, pipeline
> stages, journal implementations) that need some additional jars or that are
> not used very often.
> All other modules should be developed, maintained and downloaded separately.
> 
> 
> > As far as the mechanics go, what about having a "contrib" top-level
> > project, into which any developer can place any experimental code.
> > Postgres do this, and it seems to work quite well.  When something in
> > contrib is considered to have matured enough, and be demanded enough, to
> > be in the core system, it's migrated from contrib into the main project.
> >
> > Thoughts...
> 
> I agree. I would even create this as separate CVS project so we can grant
> CVS commit rights to everyone who wants.
> 
> By the way, what exactly will do your new pipeline stage (jfreereport)?
> 
> Dejan
> 
> >
> > MikeA
> >
> > PS: I added a stack of directories before branching, I'm not sure if
> > they appear on the HEAD now.  Anybody getting the new directories when
> > they "cvs update"?
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Temp branch

[Michael A. <mic...@ze...>]

Hi, Dejan,

Sorry for taking so long with this.  It got forgotten in the mail folder
for a while.

The new pipeline stage that I'm building takes as input the document
produced by the SqlQuery stage, as well as a report definition string
(XML), and some other miscellaneous attributes, and uses the
jfreereports library to produce a report as the output document.  The
report can be in HTML, pdf, CSV or Excel format, to being with.  Not
sure what else jfreereports can do.

Any ideas to fit in with that, and I'm all ears.  

Jfreereports expects the report definition in XML format, and it expects
the data in the form of a TableModel.  So, I'm busy writing an
implementation of an AbstractTableModel that can use the xml from
SqlQuery as input.
I figured the report definitions, which are in XML, could be added as
attributes to the data document.

Once that's finished, I want to do the same for jfreechart, which would
then produce, surprise, surprise, charts and graphs of input data.  Same
concept, slightly different output.  Both libraries are available from
www.jfree.org, if you want to have a look at their features and stuff.

Cheers...


MikeA



On Thu, 2003-11-13 at 10:06, Dejan Krsmanovic wrote:
> > I think that we should probably look at guidelines for 1.3, and try to
> > do as much as possible without breaking anything.  I'm happy to move the
> > jfreereports stuff into a separate project, even for 1.3.  It's not in
> > 1.2, so there are no issues with compatibility.
> >
> > In order to set the guidelines, a few questions: what constitutes a core
> > module (i.e.: one which goes into com.babeldoc.core.pipeline or
> > com.babeldoc.scanner)?  Or a secondary (i.e.: it goes into e.g.:
> > com.babeldoc.sql.*), or a peripheral module (i.e.: into it's own CVS
> > project and separate jar files)
> 
> Well these are the issues we should talk about. I am not very satisfied with
> current module organization. IMO, in core module there should be classes
> needed by other modules. For example, I would put scanner classes into core
> module. However, I would exclude all classes (scaner workers, pipeline
> stages, journal implementations) that need some additional jars or that are
> not used very often.
> All other modules should be developed, maintained and downloaded separately.
> 
> 
> > As far as the mechanics go, what about having a "contrib" top-level
> > project, into which any developer can place any experimental code.
> > Postgres do this, and it seems to work quite well.  When something in
> > contrib is considered to have matured enough, and be demanded enough, to
> > be in the core system, it's migrated from contrib into the main project.
> >
> > Thoughts...
> 
> I agree. I would even create this as separate CVS project so we can grant
> CVS commit rights to everyone who wants.
> 
> By the way, what exactly will do your new pipeline stage (jfreereport)?
> 
> Dejan
> 
> >
> > MikeA
> >
> > PS: I added a stack of directories before branching, I'm not sure if
> > they appear on the HEAD now.  Anybody getting the new directories when
> > they "cvs update"?
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL,
> WebDAV, and more! http://www.apachecon.com/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel