I wish I had figured it out. As it stands it looks to be quite
impossible to capture the content of a component. I'm beginning to
think that components are woefully insufficient in anything but
trivial examples. More complicated examples like the beanform, or grid
are vastly more complex than they should be. Even the components I've
built out are unnecessarily complex internally.
This whole new component design is reminding me a lot of JSP tags,
except not as powerful. I hope to see some rule bending by HLS in the
future to accommodate strongly related component groups, nesting, etc.
However, it doesn't seem likely.
Even something that seems to be trivial, getting the runtime clientId
of a nested component, is proving to be tremendously difficult. I
truly hope that these are just beta hiccups.
On 9/26/07, Chris Lewis <[EMAIL PROTECTED]> wrote:
> Indeed, but its not declarative and it doesn't address style sheets.
> Like I said, I'm not hell-bent on a declarative solution, but I do not
> want to:
>
> 1) @Inject/@Path my css ...
> 2) .. and provide a getter ...
> 3) .. for every page!
>
> On top of that it would be quite nice to know only from the template
> what other resources (css, js, etc) the page requires. As I said I'd
> settle for a class level annotation that could be applied to
> pages/components to express what css/js assets should be included. While
> not declarative, its a simple, consistent, at-a-glance way to declare
> and know what assets a page/component needs.
>
> Carl Pulley wrote:
> > You can also add javascript code into the document head via
> > PageRenderSupport
> > (see Form.java for a concrete example).
> >
> >
> > redijedi wrote:
> >
> >> I'm trying to create a component that will allow me to define blocks
> >> of HTML to insert into the head. I think this would be useful for ad
> >> hoc JS, style declarations, etc. I know that this can be inserted
> >> using other mechanisms like:
> >>
> >> Element head = writer.getDocument().find("html/head");
> >>
> >> and inserting your element manually, but this isn't pretty or
> >> easy/possible for the script or style tag contents.
> >>
> >> I know that an alternative is just to slap it in the page where the
> >> component is rendered, but that's just sloppy.
> >>
> >>
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
