Yes, the element declaration within the site's definition is too complex for me. Also see my other answer. I appreciate a lot the request you mentioned as I see a strong need for supporting UI richness with RIFE.
On 27 Aug., 09:44, Geert Bevin <[EMAIL PROTECTED]> wrote: > If you just want to generate text, you can use value renderers > (http://rifers.org/wiki/display/RIFE/Value+renderers). > > If you want to interact with the request/response cycle, write an > embedded element. Do you think that is too complex? > > The only downside is that you embedded element has to be registered > into your site. For the next release I'm planning to provide a > solution for this:http://uwyn.com/issues/browse/RIFE-237 > > If you have any suggestions for how this should function, please > comment in the issue. > > On 27 Aug 2007, at 09:35, Klaus wrote: > > > > > Again, to clarify my request: > > Evaluating the name attribute of a r:v tag is not difficult within a > > specific element class, but it should be done generally. Maybe it is > > possible with a template transformer you just mentioned in my other > > question? > > -- > Geert Bevin > Terracotta -http://www.terracotta.org > Uwyn "Use what you need" -http://uwyn.com > RIFE Java application framework -http://rifers.org > Music and words -http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
