could just leverage the existing tagId attribute and script container support. It would basically extend the HtmlBaseTag. Thanks for the feedback. Carlin On 12/13/06, Eddie O'Neil wrote: > That makes sense -- it seems like the same functionality be > generally implemented by doing something similar to > which creates a scoped name, makes it available in the pageContext, > and registers it with list of HTML ids to render. How about a new > rewriteName attribute or a new tag that does the same for page scoped > names? > > That would be a solution that could be used on all HTML tags. > > Eddie > > > On 12/13/06, Carlin Rogers wrote: > > Eddie, > > > > Yes, correct. And in addition, if this was within a > > > > ... > > > > > > the id would be scoped, so rendered like... > > > >

...

> > > > Carlin > > > > On 12/13/06, Eddie O'Neil wrote: > > > Carlin-- > > > > > > Right -- you're talking about scoping in the page rather than > > > scoping a request, though I'm still not sure I'm clear on the use of > > > the tag. > > > > > > Is the goal to have a NetUI tag that renders a

which is > > > registered with the rendered tagId / id mapping JavaScript? Something > > > like: > > > > > > > > > .... > > > > > > > > > that renders: > > > > > >

...

> > > > > > along with the JavaScript to map the rendered

into the > > > netui_names / netui_tagIdNameMap. > > > > > > Eddie > > > > > > > > > On 12/13/06, Carlin Rogers wrote: > > > > Eddie, > > > > > > > > The tag is designed to participate in URL > > > > rewriting. Say in a portal, the URL rewriting is for the scoping a > > > > request to a portlet and just prepends the portlet scope to a name. > > > > This request scoping is different than the scoping generated with the > > > > NetUI tag and JavaScript support within > > > generateIdScope="true">. The tags generate a map in a page for the > > > > tagId attributes of NetUI tags and can scope them to the > > > > scriptContainer tag... but it's a different scoping. > > > > > > > > The tag is used as a dynamic client side routine for > > > > switching between different template sections within the panel. At > > > > first I thought this could be used but the generated id on the > > > > rendered div tags doesn't seem to work for this case. I just tried a > > > > simple test. There may be a way to get this to go but still does not > > > > feel very intuitive as it involves using , > > > > etc. > > > > > > > > Carlin > > > > > > > > On 12/13/06, Eddie O'Neil wrote: > > > > > Carlin-- > > > > > > > > > > Interesting idea, though I thought this could be accomplished with a > > > > > regular HTML

, the generated NetUI JavaScript, and the > > > > > tag. For example, the type of thing that's > > > > > available here in "web/tags/rewriteTags/index.jsp". > > > > > > > > > > Would the panel do something different? > > > > > > > > > > Eddie > > > > > > > > > > > > > > > > > > > > On 12/13/06, Carlin Rogers wrote: > > > > > > At the moment there isn't an easy way to map a fragment of markup with > > > > > > a NetUI tag using a tagId to use with the NetUI client side JavaScript > > > > > > support. Most of the NetUI tags have the tagId attribute for the > > > > > > JavaScript support but the tags map to specific form controls and > > > > > > acnhors, etc. > > > > > > > > > > > > I'd like to propose adding a tag to the set of NetUI HTML tags. > > > > > > > > > > > > One use case is a page using the NetUI tag scoping of the generated > > > > > > HTML id attributes and custom client side JavaScript code that needs > > > > > > to access a fragment of markup using the NetUI lookIdByTagId() > > > > > > JavaScript function. The markup in the fragment may not require or use > > > > > > other NetUI tags. Something like... > > > > > > > > > > > > > > > > > > > > > > > > ... > > > > > >

> > > > > > > > > > > > Any concerns or thoughts? > > > > > > > > > > > > Thanks, > > > > > > Carlin > > > > > > > > > > > > > > > > > > > > >