You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2005/03/01 23:49:22 UTC
Re: [RT] Publets, Portlets, Blocks, Publiations, Configuration Management
and the good old SoC (was Re: Contrib directory)
Torsten Schlabach wrote:
[...]
> A major step might be to challenge our current concept of "publication".
> Today a publication is content + functionality to edit the content
> (where it overrides or adds to the basic capabilities that the Lenya
> core provides). IMO, we should not start to make the Lenya core modular
> and introduce publication level modular functionaliy as well. (I said
> functionaliy, not content.)
Would that mean you assemble your publication features
by using different blocks providing the desired functionality?
> Also with repository integration it might be necessary to better
> separate content from editing functionality.
That would be a perfect world :)
But I see a huge barrier there. Currently the editor configuration
is strongly related to the document structure. Disentangling this
could mean for instance to generate a forms editor XSLT from an XSD
schema ...
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [RT] Publets, Portlets, Blocks, Publiations, Configuration Management
and the good old SoC (was Re: Contrib directory)
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Andreas Hartmann wrote:
>> Also with repository integration it might be necessary to better
>> separate content from editing functionality.
>
>
> That would be a perfect world :)
>
> But I see a huge barrier there. Currently the editor configuration
> is strongly related to the document structure. Disentangling this
> could mean for instance to generate a forms editor XSLT from an XSD
> schema ...
BXE 2.0 is able to use the same XSL for editing that you use for
viewing, so this should become much simpler. once chregu is back from
his nice vacations we can think about switching trunk to bxe 2.0
the one form editor already supports that :)
it is probably possible to generate XSL for the forms editor from the
schema, at least for relatively simple schemas. another question is of
course the longer-term viability of xupdate (unfortunately a spec with 0
momentum at this time)
kupu is xhtml-only, so it is right out. (although see
http://issues.apache.org/bugzilla/show_bug.cgi?id=33314 to address this
to some extent)
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [RT] Publets, Portlets, Blocks, Publiations, Configuration Management
and the good old SoC (was Re: Contrib directory)
Posted by Michael Wechner <mi...@wyona.com>.
Andreas Hartmann wrote:
> Disentangling this
> could mean for instance to generate a forms editor XSLT from an XSD
> schema ...
this is actually what we originally had in mind for the form editor
and is still possible of course ;-) but never got implemented.
Michi
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org