Hi Dennis,
I haven't worked w/ the L10N and LANG blocks in RIFE yet, so I can't
speak for those, but I worked on a skinnable internationalized web app
for several years, so I'm semi-familiar with the issues involved. :)
I don't remember ltr and rtl being a major issue -- the browsers did a
pretty good job or just 'reversing' everything (<html dir="rtl">?). So,
you should be able to use your element to trigger the direction based on
the locale. It looks like an L10N value might work well for this.
But, if you must manage different templates for ltr and rtl, I'm
guessing you're going to have to manage separate skin files (XSL, PHP,
JSP, whatever) in any solution you decide upon. In that case, you can
code your element to use the selected locale for deciding which template
to load, and you will still get the benefit of RIFE's template system.
> The customers change what data is available to be put on a
> page, but they can change where it is, or decide not to show some of
> the data the application makes available to them. Or add additional
> links, or a frameset, or whatever they want.
I'm not sure if you meant 'customers _can_ change' or 'customers
_cannot_ change'. The logic and presentation separation in RIFE
templates would make it difficult (impossible?) for customers to change
data.
As far as omitting data, you can support this easily by writing your
element so that it checks for the appropriate data hole ("values" in
RIFE's Template terminology) by using Template.hasValueId(String), then
they can omit certain pieces by just not referring to them in the template.
I'm not sure how providing framesets as on option alongside single page
renders would work, but I'm not sure how they would be solved by another
solution either.
Josh
--
Joshua Hansen
Up Bear Enterprises
(541) 760-7685
Dennis wrote:
> Hi. I'm evaluating RIFE as a possible framework for an application
> that we'll be selling. I'm looking for advice and suggestions from
> people that have worked with it.
>
> One of our requirements is that the application be localizable and
> skinnable. Our customers must be able to do substantial customization
> of the user interface. This includes branding, logos, text
> substitution (possibly in multiple languages), colors, and so on. I
> see more or less how to do all that using ResourceBundle techniques in
> RIFE.
>
> However, we also have to support both left-to-right and right-to-left
> languages, and we have to allow our customers to customize the page
> layout. The customers change what data is available to be put on a
> page, but they can change where it is, or decide not to show some of
> the data the application makes available to them. Or add additional
> links, or a frameset, or whatever they want.
>
> I'm looking for some advice how to accomplish this with RIFE.
> Although I see the L10N and LANG variable blocks for templates, I
> don't think that's an appropriate solution for our customers. A
> template for a right-to-left language will have little in common with
> a template for a left-to-right language, and if we've got a site
> supporting multiple languages, the template will very quickly get very
> difficult to maintain.
>
> Any suggestions will be appreciated. Thanks.
>
>
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
