Em Thu, 02 Oct 2008 18:04:24 -0300, Alex Kotchnev <[EMAIL PROTECTED]>
escreveu:
Who would have thought this much discussion would come out of this :-)
Unanimities are boring and we learn next to nothing with them. :)
I am not advocating the usage of some "other" magical framework to
ma
Hi all,I think that Chris' points are the most important ones, together with
the #5 from Tobias (resolving template/component class names, i.e. naming
strategy). Mainly the configurable URL's, the built in feature is REALLY
great, but it's tricky sometimes...
Adding these features to the core will
-
Subject: Re: My Tapestry5 suggestion list
From: Chris Lewis <[EMAIL PROTECTED]>
Date: 10/02/2008 21:43
Good point.
Markus Joschko wrote:
> Talking about configurable URLs: Don't forget i18n issues.
> We once had a product where customers wanted to have the UR
Good point.
Markus Joschko wrote:
> Talking about configurable URLs: Don't forget i18n issues.
> We once had a product where customers wanted to have the URL
> internationalized to be meaningful in different countries.
> This requirement is not uncommon in Europa at least.
>
>
Talking about configurable URLs: Don't forget i18n issues.
We once had a product where customers wanted to have the URL
internationalized to be meaningful in different countries.
This requirement is not uncommon in Europa at least.
--
Hello,
The only one of these that I'm interested in is the ability to have
class-less components (just markup, no logic). I filed an issue for this
many months ago, and am no longer certain where in the mix it is. I'll
add one:
Configurable URL-mapping service.
I loathe - /loathe/ the fact that
Who would have thought this much discussion would come out of this :-)
Anyway, some more comments from me :
On Thu, Oct 2, 2008 at 1:51 PM, Thiago H. de Paula Figueiredo <
[EMAIL PROTECTED]> wrote:
> Em Thu, 02 Oct 2008 13:10:23 -0300, Alex Kotchnev <[EMAIL PROTECTED]>
> escreveu:
>
> 5. resolv
On Wed, Oct 1, 2008 at 4:38 AM, Tobias Marx <[EMAIL PROTECTED]> wrote:
> Hi there!
>
> Here is my list of Tapestry5 suggestions:
>
>
> Tapestry5 Suggestions:
>
> 1. User .tpl instead of .tml. This way there is also no problem with syntax
> highlighting in most editors.
>
We already voted a while
Em Thu, 02 Oct 2008 13:10:23 -0300, Alex Kotchnev <[EMAIL PROTECTED]>
escreveu:
5. resolving template/component class names:
This one seems interesting, certainly some variation in the allowed
naming
conventions seems nice if it's configurable (e.g. a naming strategy)
I don't know wheth
Hi,
On 2008-10-02 18:10, Alex Kotchnev wrote:
4. Allow the use of templates without having to have a corresponding
Java
class for it.
This would certainly be nice, as on a small project that I do (that for now
only has little functionality) I already have a whole bunch of dumb java
classes
5. resolving template/component class names:
This one seems interesting, certainly some variation in the allowed naming
conventions seems nice if it's configurable (e.g. a naming strategy)
>
> > 1. User .tpl instead of .tml. This way there is also no problem with
> > syntax highlighting in mos
Tapestry users"
> Betreff: My Tapestry5 suggestion list
> Hi there!
>
> Here is my list of Tapestry5 suggestions:
>
>
> Tapestry5 Suggestions:
>
> 1. User .tpl instead of .tml. This way there is also no problem with
> syntax highlighting in most editor
Hi there!
Here is my list of Tapestry5 suggestions:
Tapestry5 Suggestions:
1. User .tpl instead of .tml. This way there is also no problem with syntax
highlighting in most editors.
2. Make those templates compatible with SSI templates.
This is because most HTMLers will slice PSD
13 matches
Mail list logo
