Hi Scott, I agree. In my special case, I was backporting the ajax lookup code from 10.04 to 9.04, and encountered the problem where the "set field" function gives a String instead of the EntityCondition object. So if I were to use the makeCondition function, many extra groovy files will be created.
Regards, James Scott Gray-2 wrote: > > I would argue that using groovy is the right approach regardless of the > version. Screen actions are intended to speed up simple tasks, they are > not a substitute for actual scripting. Especially when you consider that > whenever you try and do something complicated with them you end up > spending more time debugging than if you had just put your logic in a > script in the first place. > > Regards > Scott > > On 21/06/2010, at 6:24 PM, james_sg wrote: > >> >> Hi Varun, >> >> What you had wanted to do will work if you are using 10.04. >> So coding it in groovy file is the right approach when using 9.04 >> >> Regards, >> James >> >> >> Hi Scott, >> I have already put the groovy part in a .groovy file, though just wanted >> to >> know if i had missed something. >> Thanks again. >> >> On Sat, Jun 19, 2010 at 12:56 PM, varun bhansaly >> <[email protected]>wrote: >> >>> Hi Atul, >>> Thanks for ur reply. >>> I had already tried that with type = "Object", it still does not work, >>> still seen as instanceof String. >>> >>> Hi Scott, >>> There are no asterisks, for the post i had replaced " with ". >>> >>> >>> >> >> -- >> View this message in context: >> http://ofbiz.135035.n4.nabble.com/groovy-screen-widget-tp2260470p2262179.html >> Sent from the OFBiz - User mailing list archive at Nabble.com. > > > > -- View this message in context: http://ofbiz.135035.n4.nabble.com/groovy-screen-widget-tp2260470p2262209.html Sent from the OFBiz - User mailing list archive at Nabble.com.
