25 Jun
2010
25 Jun
'10
10:30 a.m.
Vincent Massol wrote:
The names sound great and the flow chart looks nice. What will they do? get the document
and render it?
What will the interface look like? Also will seperating Template from Displayer interfere
with the ability of
a script in a document to manipulate the template XDOM around it?
On Jun 25, 2010, at 10:05 AM, Caleb James DeLisle
wrote:
I
see, I noticed "vm file" in the flow chart and jumped to a conclusion.
Do we want to continue with templates in the
filesystem rather than having everything in the database?
Wherever templates are, it doesn't change this high level architecture IMO.
Note that the point of templates is to make xwiki work even when the database is empty...
IMO there should be enough filesystem templates to help the user set up a database and
install an xar.
That is a detail as you said.
If so, will there be a pseudo document so that
the templates don't execute in the security context of whatever document is being
viewed?
I don't see anything about overlays (or skin extensions) and that seems to be
related.
This is a high level architecture. I haven't mentioned the xwiki-skin module and a
few more (xwiki-url , etc).
Before entering into details, I'd like to make sure we agree about this high level
architecture and more specifically to have these 2 modules:
- xwiki-template
- xwiki-displayer
Thanks
-Vincent
Caleb
Vincent Massol wrote:
> Hi,
>
> I've started thinking with Thomas about the new front end architecture and
here's our current idea (without details) for the future:
> http://dev.xwiki.org/xwiki/bin/view/Design/FrontEndArchitecture
>
> If you have ideas about this please send them.
>
> This message is there so that we can share a common vision for the future.
>
> Thanks
> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs