Nicola,
as you know, I evaluated the use of Wings and discarded it on purely technical
considerations some months ago: probably things have
improved in the meantime.
We too had the separation of style and content in mind, actually, we have experimented
the use of static style and dynamic data to
make charts in a real-world app.
I think the license objection could be easily overcome, since (L)GPL is not "viral" as
GPL, and allows the embedding of libraries
into software products.
Anyway, I'd like to point out that this is not a race: I'm prepared to be hosted by
Cocoondev until our transformer will mature and
only then choose which one will be best for Cocoon.
As a final remark, let me just tell you that I deem the inclusion of an easy-to-use and
well-documented chart package important for Cocoon now... not in a distant future.
Regards,
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, January 25, 2003 12:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: ChartTransformer 0.0.4 urge a commiter!
>
>
>
> Luca Morandini wrote:
> > Steven,
> >
> > I'll arrange the donation in a few days :)
>
> In Cocoon we already have a chart transformer, based on Krysalis Wings.
> It has evolved, and now we use JCharts, that is APL compatible.
>
> Wings has the possibility of using different charting packages as
> back-ends, and JFreechart too, but it ships with jCharts as default.
>
> I'd personally prefer that we use a completely APL-compatible system for
> charting. Overmore Wings has been developed with separation of content
> and syle in mind...
>
> Anyway, I really don't want to stop this, but I'd like that we decide
> what we want to do.
>
> The fact is that putting something in Cocoon CVS makes it somewhat
> "standard". If this solution had been there for some time, it would be a
> sure bet, and can be inserted by name.
>
> In this case we have two different charting transformers, which to insert?
>
> IMHO the best thing at the moment, and I repeat ATM and IMVHO, is that
> this transformer be hosted on cocoondev so that it can grow.
> And I'd like that we get to combine efforts, so that we can commit a
> unified version to the Cocoon CVS.
>
> What do you think?
>
> --
> Nicola Ken Barozzi [EMAIL PROTECTED]
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
