cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Geissel" <ageis...@zenark.com>
Subject Re: sharing microsoft experience
Date Fri, 30 Nov 2001 12:13:49 GMT
----- Original Message -----
From: Giacomo Pati <giacomo@apache.org>
To: <cocoon-dev@xml.apache.org>; <bdelacretaz@codeconsult.ch>
Sent: Friday, November 30, 2001 7:31 AM
Subject: Re: sharing microsoft experience


> Quoting Bertrand Delacretaz <bdelacretaz@codeconsult.ch>:
>
> > (this is getting very interesting but slighlty OT - maybe we should
> > start a
> > new list where we could also discuss the requirements of a content
> > editor?)
> >
> > I agree with Steven that installing yet another browser is mostly seen
> > as a
> > PITA by administrators.
> >
> > But IMHO a content editor could be seen and "marketed" as a separate
> > application - basing it on the Mozilla code base (assuming it makes
> > sense)
> > would not necessarily mean saying "Mozilla can now be used as a content
> > editor" but could be "we have a content editor, and the code is based on
> > Mozilla, by the way".
>
> Yes, this is the way to go.
>
> >
> > I don't think people would resist installing a new client application if
> > it
> > brings measurable benefits regarding content editing. Just don't tell
> > them
> > it's a new *browser*.
>
> Absolutely. Many use cases for CMS like apps will really benefit if you
can base
> your content on Schemas. Sure there are cases where a "free form HTML
editor"
> will be appropriate but often content writer will be supposed to write the
> content based on a fixed Schema.
>

Q: Is this discussion about writing just another HTML editor, or about
building an abstracted content editor where structure, layout and style can
be assembled from the contributions of multiple authors (using XML, XSLT,
etc., of course). The real trick is to build a really neat (and usable) XSLT
editor for writing the stylesheets that enable abstract data (XML) to be
generated into human readable form.

Adrian

> > I don't know enough about the Mozilla code to be positive about this,
> > but
> > maybe there are other code bases that would be better suited to creating
> > an
> > XML content editor - Amaya, Swing, OpenOffice, others?
>
> As I can see it today (sure I'm not the dancing on all floors) mozilla
promises
> the most adaptable open source code base to build such an editor upon.
>
> Giacomo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


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


Mime
View raw message