Page History

...

People interested: Marco Risaliti
People willing to help: Marco Risaliti

https://issues.apache.org/jira/browse/OFBIZ-1441https://issues.apache.org/jira/browse/OFBIZ-1441https://issues.apache.org/jira/browse/OFBIZ-1441https://issues.apache.org/jira/browse/OFBIZ-1441OFBIZ-1441

Enhance the integration with Google Product DONE

...

People interested: Marco Risaliti
People willing to help: Marco Risaliti

https://issues.apache.org/jira/browse/OFBIZ-1372https://issues.apache.org/jira/browse/OFBIZ-1372https://issues.apache.org/jira/browse/OFBIZ-1372https://issues.apache.org/jira/browse/OFBIZ-1372OFBIZ-1372

Integrate Screen Widget and Form Widget with Dojo.

...

Non Backward Compatible Changes

Use Apache Commons EL instead of the Flexible String Expander

...

DONE

Committed to trunk December 2008.

UEL in OFBiz

For syntax reference see:

http://java.sun.com/products/jsp/syntax/2.0/syntaxref207.html

-Based on early research of the syntax it looks like most of our current Flexible String Expander usage would work with EL. The "${}", "." and "\[\]" syntax elements all appear to be supported. We would also get new features like arithmetic expressions and so on.-

Later note : Regarding using the Apache Commons EL for expression evaluation: the library is designed to work with JSPs, so including it in FlexibleStringExpander would be difficult.

There has been discussion on dev ML abut UEL (Unified Expression Language) recently introduced in OFBiz (12/08), here are some related links
http://java.sun.com/javaee/5/docs/tutorial/backup/doc/JSPIntro7.html
http://jcp.org/aboutJava/communityprocess/final/jsr245/ Click on one of the Download links, accept the terms, then download the file marked: JavaServer Pages 2.1 Expression Language Specification (pdf)

Change the Entity Engine to be user aware for security, logging

...

There are big downsides to this in that it is a real pain to ALWAYS have to know which user is doing stuff, and lots of our services don't know who the user is or use the "system" user to get around security constraints. The same thing would have to happen if we did this for the EE. This would also require major API refactoring, which we would probably want to precede with a big reduction in API size, as has been started but isn't yet finished.

Maybe the API refactoring wouldn't be necessary if we created a user-aware decorator for the GenericDelegator.

UI (User Interface) enhancements

...

• Typography : Typography depends on languages. For instance in French we put a space after colons, there are other cases of course. So punctuation should be always part of labels.
• HTML : We already discussed about not putting any HTML tags in labels. Also we should not put any < and & which would not be correctly rendered (http://www.w3.org/TR/REC-xml/#dt-chardata^{Image Removed}), so should be escaped.