Geert, OK I see what you mean. I wanted to avoid an embedded element as I think it adds complexity to the solution where it could be avoided. On the other side an embedded element encapsulated functionality that could be reused. What I ask myself here is: Is it possible implementing/calling a functionality that does exactly what an embedded element does, namely to render a template and return the result to the caller? With that I could skip the quite lengthy declaration of the embedded element in the site definition, the target template and in the calling element class (as there the ID of the embedded element has to be provided)?
What comes to my mind right now: If the embedded element contains form input elements that will finally be embedded within a form that lies in the embedding template, are the embedded form input elements processed correctly in the sense of that they are available of the embedding element as if they were there already? Best Klaus On 27 Aug., 09:33, Geert Bevin <[EMAIL PROTECTED]> wrote: > Hi Klaus, > > you can't add a tag like that. > > Since you want a UI component, write an embedded element, which you > can provide properties and such to configure it. I don't think that > an embedded element is overkill at all for this. If you just want to > render a UI snippet, you could use a value renderer (http:// > rifers.org/wiki/display/RIFE/Value+renderers), but that is very limited. > > You have to shift around your thinking about template engines in > RIFE. The templates themselves only create values and block that you > name. Whatever happens with those values, is up to you. RIFE supports > for instance a number of filtered value tags (http://rifers.org/wiki/ > display/RIFE/Filtered+values+tags), which is what the template engine > does with those value names when you print a template through the > element. > > Take care, > > Geert > > On 27 Aug 2007, at 09:19, Klaus wrote: > > > How can I add custom template tags? E.g. imagine I want to add a new > > tag RICHTEXTEDIT, so that I can write: > > <r:RICHTEXTEDIT name="xxx"> > > > Even better would be to be able specifying additional attributes, so > > that one could write: > > <r:RICHTEXTEDIT name="xxx" maxlength="20"> > > > IMO, there is a strong tendency to easy-to-build GUIs, which seems a > > problem with RIFE up to now. Compare the click framework or other > > similar ones! > > > In general, I want to add custom tags of any kind, not just such to > > implant a UI component (but also header information, Javascript, > > etc.)! > > -- > 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 -~----------~----~----~----~------~----~------~--~---
