xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremias Maerki <dev.jerem...@greenmail.ch>
Subject Re: FOP API proposal in FOP wiki
Date Mon, 17 Feb 2003 20:26:01 GMT

On 17.02.2003 21:08:20 J.Pietschmann wrote:
> Jeremias Maerki wrote:
> > That was my original idea, to build FOP on Avalon, provide an
> > Avalon-based API (for advanced users and Cocoon) but have a standard
> > easy-to-use API that's not Avalon-based. Unfortunately, the Wiki page
> > currently doesn't reflect this.
> 
> No problem here: edit the proposal to reflect your views.
> It's a wiki!

I'll get to that. I just don't want to stand on your toes. You've got
your view, I've got mine. I want to get a solution that all of us are
happy with.

> > Avalon has a lot of benefits for us
> 
> This is exactly the problem with Avalon: it benefits the
> developers. But does it benefit the *users* in a tangible manner
> (other than getting the software earlier)? Exposing an Avalon-only
> API *will* get us flames.

I know. That's exactly the reason for the "Easy API".

> Users don't want to step up another
> learning curve. Particularly if the accumulated knowledge can't
> be reused elsewhere. How many public projects are there beside
> Cocoon which draw heavily from Avalon? I get 5 in the first 100
> matches of a Google search (one of them, ironically, on savannah).

Yes, yes, heard that argument many times now.

> BTW type "avalon" and "framework" into Google for a surprise.

Already knew that one. 


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Mime
View raw message