Hello,
Regards, Vinay Agarwal _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Vinay,
Here is the mini-language guide reference: http://www.ofbiz.org/docs/minilang.html. There is a lot that can be done within the widget action syntax. One little trick is that the "set" operation has a "default-value" attribute that can use the interpolation mode (ie. ${...}) to reference stored values. This gives one a one-line if-else statement. The use of embedded "section" elements within the "widget" element and the use of their "condition" elements to conditionally execute the associated actions and widget elements is also a powerful tool. And you can make calls to screens that can be used by multiple screens. The "use-when" attribute in forms is another powerful coding tool. When logic that cannot be handled by the above methods is needed, I believe that David Jones would like to see services generally used in place of bsh files. Services can be written in either in the mini-lang or in java. The best way to get started, other than reading the documentation is to look at its use in OFBiz. -Al Vinay Agarwal wrote: > Hello, > > 1. I assume the xml is preferred to bsh for implementing the > actions. What’s the best way for people to get started who have > hard time reading XSD’s? > 2. Can Java be used in screen widget actions? If yes, what would be > the syntax of the call? > > Regards, > > Vinay Agarwal > >------------------------------------------------------------------------ > > >_______________________________________________ >Users mailing list >[hidden email] >http://lists.ofbiz.org/mailman/listinfo/users > _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Al,
Thanks for a very helpful answer. My big confusion was whether the <actions> took the entire minilang, a subset, or something entirely different. And now it is clear. Regards, Vinay Agarwal -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Al Byers Sent: Tuesday, March 07, 2006 9:01 AM To: OFBiz Users / Usage Discussion Subject: Re: [OFBiz] Users - Actions in Screen Widgets Vinay, Here is the mini-language guide reference: http://www.ofbiz.org/docs/minilang.html. There is a lot that can be done within the widget action syntax. One little trick is that the "set" operation has a "default-value" attribute that can use the interpolation mode (ie. ${...}) to reference stored values. This gives one a one-line if-else statement. The use of embedded "section" elements within the "widget" element and the use of their "condition" elements to conditionally execute the associated actions and widget elements is also a powerful tool. And you can make calls to screens that can be used by multiple screens. The "use-when" attribute in forms is another powerful coding tool. When logic that cannot be handled by the above methods is needed, I believe that David Jones would like to see services generally used in place of bsh files. Services can be written in either in the mini-lang or in java. The best way to get started, other than reading the documentation is to look at its use in OFBiz. -Al Vinay Agarwal wrote: > Hello, > > 1. I assume the xml is preferred to bsh for implementing the > actions. What's the best way for people to get started who have > hard time reading XSD's? > 2. Can Java be used in screen widget actions? If yes, what would be > the syntax of the call? > > Regards, > > Vinay Agarwal > >------------------------------------------------------------------------ > > >_______________________________________________ >Users mailing list >[hidden email] >http://lists.ofbiz.org/mailman/listinfo/users > _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Free forum by Nabble | Edit this page |