> I'm thinking about fixes for your issues. First, a simple way to
insert
> static JavaScript would be nice (both inline, and as references to
> JavaScript stored as an asset).
>
> Second, we could work around <insert/>. For example, we could adopt
an
> additional, Ant-like, syntax, i.e.
>
> function ${function-name} ()
> {
> document.${form.name}. .....
>
> And allow that inside CDATA (which would simplify the business about
XML
> entities such as & and <).
That's good idea. Why not use Velocity for this part? As an example,
right now I have a requirement where I want to generate a set of
javascript calls inside a javascript file and that set of calls are
dynamic (depending on the number of found rows). Let the user hang
himself with a fully featured template system :-)
> > Add to this the problems you face when an html component of tapestry
> > doesn't support a feature pure html provides (my problem for
multiple
> > stylesheet entries for example). The need to change all addresses to
> > context/provate/blabla addresses is a big pain imho. This is where
the
> > components need to redefine/tapestrify some of the stuff you
normally do
> > in html. Can't you just search context then classpath for a link,
with
> > no for an explicit definition by the user?
>
> Tapestry has always had a very fun, evolutionary nature. Rather than
try
> to
> solve every problem first, up front, I've created
> a flexible framework on which to build strong solutions. As the need
for
> a
> new feature becomes evident, it is added to the framework. It's not
that
> Tapestry can't support multiple stylesheets, its that it doesn't do it
> now.
> You can always create a custom version of Shell for your application.
You
> can also add a freakin' bug if you want to see something changed.
>
> You only have to worry about converting things to assets when they are
> dynamic; either dynamic in response to user behavior, or dynamic in
terms
> of
> localization.
I know about evolution of frameworks (I'm the guy who's leading the
XDoclet project and it evolved from a 20KB little tool to a 2.5MB Ant
plugin). My point is that imho there should be less tapistrification
needed for simple html stuff. That makes your life easier when you're
working with a web designer. That's it.
Ara.
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
