On Thu, 2007-05-10 at 11:15 -0500, Richard Frovarp wrote:
> Thorsten Scherler wrote:
...
> >> When should we change this? RC1 / RC2 / 1.4.1 ?
> >>
> >
> > I am not sure, but I would not make it a blocker, since it would need
> > much testing. I would first test it local and if it works I will
Thorsten Scherler wrote:
On Thu, 2007-05-10 at 11:38 +0200, Andreas Hartmann wrote:
...
Yes, agree that is even better since it is more efficient.
3) Populate the file from step 2 with java objects that are in the
request.
Where 1 is a match of its own (for caching reasons) and 2 an
Thorsten Scherler schrieb:
[...]
> Actually for me that "every non-trivial operation requires offloading to
> java code" is a benefit since it keeps the heavy logic out of the
> templates. I guess we all have seen once in our life a jsp that
> contained an actual java class within, well let alone
On Thu, 2007-05-10 at 11:55 +0200, Joern Nettingsmeier wrote:
> Andreas Hartmann wrote:
> > Joern Nettingsmeier schrieb:
> >> Thorsten Scherler wrote:
> >
> > [...]
> >
> >>> Further it would be possible to have url specific extension of extra
> >>> content and/or extra functionality. Imagine I d
On Thu, 2007-05-10 at 12:07 +0200, Jörn Nettingsmeier wrote:
> Thorsten Scherler wrote:
> > I agree totally with you. A trivial example is doing string operations
> > in xsl is total nightmare.
>
> which i think is a big bonus. string operations should hurt. you should
> think twice before mungin
Josias Thöny schrieb:
[...]
> The menu generation is slowed down considerably by all the precondition
> checks of the usecases in the menu.
> Some time ago I noticed that in the "authoring" view, the usecases which
> appear only in the "site" view are checked, too. This is probably not
> necessar
Jörn Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> Jörn Nettingsmeier schrieb:
>>> Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
> i think you may be a little biased against xslts...
I used to like it a lot, and I still like it for certain purposes, but
it tends to g
Thorsten Scherler wrote:
I agree totally with you. A trivial example is doing string operations
in xsl is total nightmare.
which i think is a big bonus. string operations should hurt. you should
think twice before munging strings, and then it should be a royal pain.
no. i'm not trolling. loo
On Thu, 2007-05-10 at 11:38 +0200, Andreas Hartmann wrote:
...
> > Yes, agree that is even better since it is more efficient.
> >
> >>> 3) Populate the file from step 2 with java objects that are in the
> >>> request.
> >>>
> >>> Where 1 is a match of its own (for caching reasons) and 2 and 3 in
On Thu, 2007-05-10 at 11:38 +0200, Andreas Hartmann wrote:
> Thorsten Scherler schrieb:
> > On Thu, 2007-05-10 at 10:57 +0200, Andreas Hartmann wrote:
> >> Thorsten Scherler schrieb:
> >>> On Wed, 2007-05-09 at 23:01 +0200, Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
> > Joern Nett
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
Thorsten Scherler wrote:
[...]
Further it would be possible to have url specific extension of extra
content and/or extra functionality. Imagine I do not want the breadcrumb
or the lanuageselector on some pages but on other I do. Now I alwa
On Thu, 2007-05-10 at 11:28 +0200, Joern Nettingsmeier wrote:
> Thorsten Scherler wrote:
> > Right now in the menu we can decide when and which item to show. I agree
> > that the xsp approach needs rethinking but why not use jx instead. This
> > would make it possible to keep presentation logic in
Andreas Hartmann wrote:
Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
i think you may be a little biased against xslts...
I used to like it a lot, and I still like it for certain purposes, but
it tends to get in your way when you try to increase the performa
Thorsten Scherler schrieb:
> On Thu, 2007-05-10 at 10:57 +0200, Andreas Hartmann wrote:
>> Thorsten Scherler schrieb:
>>> On Wed, 2007-05-09 at 23:01 +0200, Jörn Nettingsmeier wrote:
Andreas Hartmann wrote:
> Joern Nettingsmeier schrieb:
>>> ...
> Our menu is a special case - it has a
On Thu, 2007-05-10 at 10:57 +0200, Andreas Hartmann wrote:
> Thorsten Scherler schrieb:
> > On Wed, 2007-05-09 at 23:01 +0200, Jörn Nettingsmeier wrote:
> >> Andreas Hartmann wrote:
> >>> Joern Nettingsmeier schrieb:
> > ...
> >>> Our menu is a special case - it has a basic structure (which XML is
Joern Nettingsmeier schrieb:
> Thorsten Scherler wrote:
[...]
>> Further it would be possible to have url specific extension of extra
>> content and/or extra functionality. Imagine I do not want the breadcrumb
>> or the lanuageselector on some pages but on other I do. Now I always get
>> this par
Thorsten Scherler wrote:
Right now in the menu we can decide when and which item to show. I agree
that the xsp approach needs rethinking but why not use jx instead. This
would make it possible to keep presentation logic in an easy way. From
my experience xsl it is not very suitable to implement p
Thorsten Scherler schrieb:
> On Wed, 2007-05-09 at 23:01 +0200, Jörn Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>>> Joern Nettingsmeier schrieb:
> ...
>>> Our menu is a special case - it has a basic structure (which XML is
>>> fine for), but there's some logic to control the details. We have
Jörn Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> Joern Nettingsmeier schrieb:
>>> i think you may be a little biased against xslts...
>>
>> I used to like it a lot, and I still like it for certain purposes, but
>> it tends to get in your way when you try to increase the performance.
>
> i
On Wed, 2007-05-09 at 23:01 +0200, Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
> > Joern Nettingsmeier schrieb:
...
> > Our menu is a special case - it has a basic structure (which XML is
> > fine for), but there's some logic to control the details. We have to
> > find a way to separate t
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
i think you may be a little biased against xslts...
I used to like it a lot, and I still like it for certain purposes,
but it tends to get in your way when you try to increase the
performance.
i don't really buy that argument. granted, t
Jörn Nettingsmeier schrieb:
> Richard Frovarp wrote:
[...]
>> We
>> might want to strip out the SSL checkbox option from the pages, as
>> this isn't going to do anything and will just be confusing.
Would that mean either everything is served with SSL or nothing?
Well, I guess that's OK for the a
Joern Nettingsmeier schrieb:
[...]
>> The menus contain a lot of functionality. The usecase framework has
>> improved this a bit, but has also brought a performance penalty.
>> I wouldn't like to put more logic in XSLTs. I agree that XSPs are bad,
>> we have to find a way to move the logic to Jav
Richard Frovarp wrote:
Like you said, the live side is fine, so long as you don't try to
protect anything behind SSL.
have you succeeded in hiding the /live from the URLs?
It is unfortunate that for authoring Lenya
has to run in the root context, but it is at least a solution. One could
wo
Andreas Hartmann wrote:
Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
(yeah, i'm still trying to fix the proxying issue. some clown has
written stylesheets that generate stylesheets to generate menus...
I guess that clown was me (at least some parts of the c
and
the core sitemaps completely fail to use the base-url module, which is
apparently the only one that is proxy-aware...)
That's because the core sitemaps are much older than the base-url
module.
Is there something particular I could help you with?
A test case / setup description wou
Jörn Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> Joern Nettingsmeier schrieb:
>>> (yeah, i'm still trying to fix the proxying issue. some clown has
>>> written stylesheets that generate stylesheets to generate menus...
>>
>> I guess that clown was me (at least some parts of the clownery) :)
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
(yeah, i'm still trying to fix the proxying issue. some clown has
written stylesheets that generate stylesheets to generate menus...
I guess that clown was me (at least some parts of the clownery) :)
evil!
talk about not allowing broken wi
28 matches
Mail list logo
