[ 
https://issues.apache.org/jira/browse/OFBIZ-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469510
 ] 

Jacques Le Roux commented on OFBIZ-642:
---------------------------------------

Adrian,

I think I had well understood you. What I mean is that it's better to keep this 
OOTB behaviour. Because it shows to all possible prospective users that their 
languagues is there, and it shows it quickly in a "marketing" way (only have to 
throw a glance to the combo, no need to follow a link, come back, etc.). 

My suggestion is to use only languages really implemented in production site by 
specifying them with best practices, ie using locales.available in 
general.properties. In such case you will only have some HTM lines wich are not 
a big deal.

Keep in mind that people have often already experienced rich client UIs and 
they wait for the same (or aspire if you want) on the web (hence Ajax).

BTW I don't know if you have already dealed with multi-languages sites; but one 
big problem is currency and and even more prices (same currency but differents 
prices, like in EU for instance). Hence, often people use different stores for 
each language (a bit out of subject, ok ;o).

> Make OFBiz more dial-up friendly
> --------------------------------
>
>                 Key: OFBIZ-642
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-642
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>            Reporter: Adrian Crum
>            Priority: Trivial
>
> Reduce OFBiz's HTML output so that pages load faster on dial-up lines.
> Three things can be done to achieve that goal:
> 1. Reduce HTML code through better use of styles (currently in progress).
> 2. Eliminate the language selection code that is sent out with every page 
> request. Intead of having a selection box in the header, just display the 
> currently selected language and provide a link to change it. Clicking on the 
> link could produce a language selection popup window - similar to the current 
> lookup windows.
> 3. Freemarker has the <#compress></#compress> directives which eliminate 
> unnecessary HTML white space. A recent test showed the directives can yield a 
> 33% reduction in markup. Problem is, that only works if the directive is 
> placed in every FTL file. There needs to be a way to make that a global 
> setting in Freemarker, so that ALL markup is reduced - without any additional 
> FTL coding. I looked around the Freemarker website for a way to do that, but 
> couldn't find anything.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to