You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Thorsten Scherler <th...@apache.org> on 2005/10/13 12:28:29 UTC
[HEADSUP] Views v2 codename: (views-) structurer
El jue, 13-10-2005 a las 10:20 +0000, thorsten@apache.org escribió:
> Author: thorsten
> Date: Thu Oct 13 03:19:07 2005
> New Revision: 320710
>
> URL: http://svn.apache.org/viewcvs?rev=320710&view=rev
> Log:
> Views v2 codename: (views-) structurer
> - forrest:call-template is not working anymore you have to use <jx:import uri="cocoon://prepare.tiles.export-link"/> instead
> - forrest:contracts: You have to include nuggets now with jx:import as well:
> <forrest:property name="content-minitoc-toc" nugget="get.toc">
> - <url>#{$cocoon/parameters/getRequest}.toc.xml</url>
> + <jx:import uri="cocoon://#{$cocoon/parameters/getRequest}.toc.xml"/>
> </forrest:property>
> - All matches in the structurer are using now the lm.
> - No xincludes any more in the structurer, this has to be done now with jx:import.
> - generally slimed done processing pipelines.
>
> In a second step I will refactor as well themes.
> HEADSUP: I did not updated the pelt theme yet! This theme will be broken till I changed the nugget contracts and the forrest:call-templates.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 14-10-2005 a las 22:50 +1000, David Crossley escribió:
> Tim Williams wrote:
> >
> > I think dispatcher sounds like a cool name for developers. I don't
> > think it will resonate with end users. The old "skins" was well known
> > in what one might expect from it. The new "views" could also be
> > understood although confusion came in on the technical side with them.
> > This "dispatcher" tells me nothing about what exactly it does and my
> > contention is that we've got a high enough learning curve being based
> > on Cocoon without introducing naming complexities. I don't think
> > we're doing much for our users by choosing such a name, but I'm only
> > -0 on it.
>
> But in the end the users will not even see any names.
> The machinery will be invisible. These names are just
> for developer documentation. Even the whiteboard plugin
> names will probably go away when it moves into the core
> proper.
Maybe "chameleon"?
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Tim Williams wrote:
>
> I think dispatcher sounds like a cool name for developers. I don't
> think it will resonate with end users. The old "skins" was well known
> in what one might expect from it. The new "views" could also be
> understood although confusion came in on the technical side with them.
> This "dispatcher" tells me nothing about what exactly it does and my
> contention is that we've got a high enough learning curve being based
> on Cocoon without introducing naming complexities. I don't think
> we're doing much for our users by choosing such a name, but I'm only
> -0 on it.
But in the end the users will not even see any names.
The machinery will be invisible. These names are just
for developer documentation. Even the whiteboard plugin
names will probably go away when it moves into the core
proper.
-David
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Tim Williams <wi...@gmail.com>.
On 10/14/05, Thorsten Scherler <th...@apache.org> wrote:
> El vie, 14-10-2005 a las 11:53 +1000, David Crossley escribió:
> > Thorsten Scherler wrote:
> > > David Crossley escribi??:
> > > > Thorsten Scherler wrote:
> > > > > > Log:
> > > > > > Views v2 codename: (views-) structurer
> > > >
> > > > You said in a recent email that "views" were
> > > > more than "structurer". Have we still not got'
> > > > our names right?
> > >
> > > IMO the best name would be "dispatcher view". That is exactly what views
> > > (v1 and v2) is. ;-)
> > >
> > > ...but we wanted to rename them because the term view was causing
> > > confusions (cocoon-views, eclipse-view, ...).
> > >
> > > That is the reason I have chosen the name even if that is not perfect
> > > either.
> >
> > Then "dispatcher" is the name for the whole thing.
> > I have started using that term in the documentation.
>
> +1
>
> that is good stuff.
>
> The forrest dispatcher is based on a structurer and a themer.
>
> Views (codename) = dispatcher (release name)
>
> Views v1 (stable) codename: v1
> Views v2 (testing) codename: v2
>
> salu2
> --
> thorsten
I think dispatcher sounds like a cool name for developers. I don't
think it will resonate with end users. The old "skins" was well known
in what one might expect from it. The new "views" could also be
understood although confusion came in on the technical side with them.
This "dispatcher" tells me nothing about what exactly it does and my
contention is that we've got a high enough learning curve being based
on Cocoon without introducing naming complexities. I don't think
we're doing much for our users by choosing such a name, but I'm only
-0 on it.
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
>>David Crossley escribi??:
...
>>Then "dispatcher" is the name for the whole thing.
>>I have started using that term in the documentation.
>
>
> +1
>
> that is good stuff.
>
> The forrest dispatcher is based on a structurer and a themer.
>
> Views (codename) = dispatcher (release name)
>
> Views v1 (stable) codename: v1
> Views v2 (testing) codename: v2
Woohoo - a name (boy that has been a long haul)
+1000
Ross
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 14-10-2005 a las 11:53 +1000, David Crossley escribió:
> Thorsten Scherler wrote:
> > David Crossley escribi??:
> > > Thorsten Scherler wrote:
> > > > > Log:
> > > > > Views v2 codename: (views-) structurer
> > >
> > > You said in a recent email that "views" were
> > > more than "structurer". Have we still not got'
> > > our names right?
> >
> > IMO the best name would be "dispatcher view". That is exactly what views
> > (v1 and v2) is. ;-)
> >
> > ...but we wanted to rename them because the term view was causing
> > confusions (cocoon-views, eclipse-view, ...).
> >
> > That is the reason I have chosen the name even if that is not perfect
> > either.
>
> Then "dispatcher" is the name for the whole thing.
> I have started using that term in the documentation.
+1
that is good stuff.
The forrest dispatcher is based on a structurer and a themer.
Views (codename) = dispatcher (release name)
Views v1 (stable) codename: v1
Views v2 (testing) codename: v2
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> David Crossley escribi??:
> > Thorsten Scherler wrote:
> > > > Log:
> > > > Views v2 codename: (views-) structurer
> >
> > You said in a recent email that "views" were
> > more than "structurer". Have we still not got'
> > our names right?
>
> IMO the best name would be "dispatcher view". That is exactly what views
> (v1 and v2) is. ;-)
>
> ...but we wanted to rename them because the term view was causing
> confusions (cocoon-views, eclipse-view, ...).
>
> That is the reason I have chosen the name even if that is not perfect
> either.
Then "dispatcher" is the name for the whole thing.
I have started using that term in the documentation.
-David
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 13-10-2005 a las 22:25 +1000, David Crossley escribió:
> Thorsten Scherler wrote:
> > > Log:
> > > Views v2 codename: (views-) structurer
>
> You said in a recent email that "views" were
> more than "structurer". Have we still not got'
> our names right?
IMO the best name would be "dispatcher view". That is exactly what views
(v1 and v2) is. ;-)
...but we wanted to rename them because the term view was causing
confusions (cocoon-views, eclipse-view, ...).
That is the reason I have chosen the name even if that is not perfect
either.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> > Log:
> > Views v2 codename: (views-) structurer
You said in a recent email that "views" were
more than "structurer". Have we still not got'
our names right?
-David
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 14-10-2005 a las 21:11 +1000, David Crossley escribió:
> Cyriaque Dupoirieux wrote:
> > David Crossley a ?crit :
> > >Thorsten Scherler wrote:
> > >>David Crossley escribi??:
> > >>
> > >>>Why is this other plugin called "themes" rather than "themer".
> > >>>
> > >>I reckon it is a typo when I created them. ;-)
> > >>
> > >>Should I rename it?
> > >
> > >Hmmm, i reckon that it is worth it to be consistent.
> > >What do others think?
> > >
> > I like it,
> > BTW, I have some updated pelt templates in my working copy, will I loose
> > them if you rename the plugin ?
> > If it is the case, please warn us when the rename is done, I will make a
> > backup before svu update...
Can you check them in before 15:00? I want to finish the move on the
weekend but do not have internet connection. If not I will go to the
office on the weekend.
> You would not lose anything. Subversion would report
> conflicts to you. Moving your changes to the new plugin
> would then enable 'svn update' to resolve those
> conflicts and so finish the removal of the old files.
>
> Also committers can check the "svn" mailing list
> before doing an update to see what is pending.
>
> But yes, it would be nice to let us know.
Sure I will do, but I reckon we should do it *now* because of my ISP. :(
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Cyriaque Dupoirieux wrote:
> David Crossley a ?crit :
> >Thorsten Scherler wrote:
> >>David Crossley escribi??:
> >>
> >>>Why is this other plugin called "themes" rather than "themer".
> >>>
> >>I reckon it is a typo when I created them. ;-)
> >>
> >>Should I rename it?
> >
> >Hmmm, i reckon that it is worth it to be consistent.
> >What do others think?
> >
> I like it,
> BTW, I have some updated pelt templates in my working copy, will I loose
> them if you rename the plugin ?
> If it is the case, please warn us when the rename is done, I will make a
> backup before svu update...
You would not lose anything. Subversion would report
conflicts to you. Moving your changes to the new plugin
would then enable 'svn update' to resolve those
conflicts and so finish the removal of the old files.
Also committers can check the "svn" mailing list
before doing an update to see what is pending.
But yes, it would be nice to let us know.
-David
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
David Crossley a écrit :
>Thorsten Scherler wrote:
>
>
>>David Crossley escribi??:
>>
>>
>>>Why is this other plugin called "themes" rather than "themer".
>>>
>>>
>>I reckon it is a typo when I created them. ;-)
>>
>>Should I rename it?
>>
>>
>
>Hmmm, i reckon that it is worth it to be consistent.
>What do others think?
>
>
I like it,
BTW, I have some updated pelt templates in my working copy, will I loose
them if you rename the plugin ?
If it is the case, please warn us when the rename is done, I will make a
backup before svu update...
Cyriaque,
>-David
>
>
>
>
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> David Crossley escribi??:
> >
> > Why is this other plugin called "themes" rather than "themer".
>
> I reckon it is a typo when I created them. ;-)
>
> Should I rename it?
Hmmm, i reckon that it is worth it to be consistent.
What do others think?
-David
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 13-10-2005 a las 22:23 +1000, David Crossley escribió:
>
> Why is this other plugin called "themes" rather than "themer".
I reckon it is a typo when I created them. ;-)
Should I rename it?
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> > Author: thorsten
> > Date: Thu Oct 13 03:19:07 2005
> > New Revision: 320710
> >
> > URL: http://svn.apache.org/viewcvs?rev=320710&view=rev
> > Log:
> > Views v2 codename: (views-) structurer
> > - forrest:call-template is not working anymore you have to use <jx:import uri="cocoon://prepare.tiles.export-link"/> instead
> > - forrest:contracts: You have to include nuggets now with jx:import as well:
> > <forrest:property name="content-minitoc-toc" nugget="get.toc">
> > - <url>#{$cocoon/parameters/getRequest}.toc.xml</url>
> > + <jx:import uri="cocoon://#{$cocoon/parameters/getRequest}.toc.xml"/>
> > </forrest:property>
> > - All matches in the structurer are using now the lm.
> > - No xincludes any more in the structurer, this has to be done now with jx:import.
> > - generally slimed done processing pipelines.
> >
> > In a second step I will refactor as well themes.
Why is this other plugin called "themes" rather than "themer".
-David
> > HEADSUP: I did not updated the pelt theme yet! This theme will be broken till I changed the nugget contracts and the forrest:call-templates.
>
> salu2
> --
> thorsten
>
> "Together we stand, divided we fall!"
> Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 13-10-2005 a las 11:48 +0100, Ross Gardler escribió:
...
> It would be interesting to see what effect using jx:import over xinclude
> has on performance.
Not yet because the themer is still heavily using xinclude and I have
not yet fully finished the rewriting.
> (there are many other places we need to address performance too, but as
> I said in the past I don't think we need worry about it, I reckon much
> of this stuff will end up in Java classes and we can cache results in
> there).
Yeah, first I will finish moving (themes is missing) to the lm and then
we can look how to use java in some processing steps. IMO the "xsl
magic" part is a good candidate even if it a good example for advanced
xsl usage. ;-)
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: [HEADSUP] Views v2 codename: (views-) structurer
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> El jue, 13-10-2005 a las 10:20 +0000, thorsten@apache.org escribió:
>
>>Author: thorsten
>>Date: Thu Oct 13 03:19:07 2005
>>New Revision: 320710
>>
>>URL: http://svn.apache.org/viewcvs?rev=320710&view=rev
>>Log:
>>Views v2 codename: (views-) structurer
>>- forrest:call-template is not working anymore you have to use <jx:import uri="cocoon://prepare.tiles.export-link"/> instead
>>- forrest:contracts: You have to include nuggets now with jx:import as well:
>><forrest:property name="content-minitoc-toc" nugget="get.toc">
>>- <url>#{$cocoon/parameters/getRequest}.toc.xml</url>
>>+ <jx:import uri="cocoon://#{$cocoon/parameters/getRequest}.toc.xml"/>
>></forrest:property>
>>- All matches in the structurer are using now the lm.
>>- No xincludes any more in the structurer, this has to be done now with jx:import.
>>- generally slimed done processing pipelines.
>>
>>In a second step I will refactor as well themes.
>>HEADSUP: I did not updated the pelt theme yet! This theme will be broken till I changed the nugget contracts and the forrest:call-templates.
I've not looked at this in detail. But great work.
It would be interesting to see what effect using jx:import over xinclude
has on performance.
(there are many other places we need to address performance too, but as
I said in the past I don't think we need worry about it, I reckon much
of this stuff will end up in Java classes and we can cache results in
there).
Ross