Re: Groovy services and a DSL for OFBiz - a POC
Hi Jacopo, a nice step in the right direction, IMHO. I like it. Do you think it's possible to hack up a transpiler from Minilang to JacopoLang(tm), (i.e. like Coffescript has for Javascript), so that we can get rid of minilang entirely? Greetings, - Karl On 08.03.2012, at 19:02, Jacopo Cappellato wrote: Hi all, I have just completed my first pass in the implementation of a DSL (Domain Specific Language) for OFBiz that can be used by Groovy services to act like a modern version of Minilang. Please review my notes here: https://cwiki.apache.org/confluence/display/OFBIZ/Groovy+Services+and+DSL+for+OFBiz I look forward to your comments and feedback but please consider that 1) it is a work in progress, 2) I spent a lot of time and mental energy in the effort (reaching simplicity is really complex task!)... so please don't be too picky :-) Regards, Jacopo PS: if you find it useful, I can commit the Groovy service mentioned in the page in Confluence
Re: jquey
Hi Jacques et al, there are no real options, IMHO, jQuery is the way to go. jQuery, like it or not, is now a somewhat established 'standard', allowing corporations to hire consultants and coders for. Additionally, the existing Dojo/Prototype/Scriptalicious codebase is a _mess_ and a lot of work to clean up. Sascha did very good work, also the backend seems much faster with jQuery. I think that a good fact/opinion collection already has happened on the mailing list, so that a decision can be made. Please prevent whatever happened that prohibited not actually releasing 10.04 until today. I suggest that, based on the input so far, the three top committers come to a unanimous conclusion and decide where to go and all follow in line. I understand that a lot of people have a stake in OfBiz, but for the sake of advancement of the project I strongly believe that a clear and quick decision is necessary, even when it breaks functionality. The outcome will outweigh the momentary pain. Greetings have a nice weekend, - Karl On 03.12.2010, at 11:47, Jacques Le Roux wrote: IMO, there are 2 options for releasing branch(es). * Only one which will be later the official release. The problem is then whether people want to have Dojo/Prototype or jQuery in this new release branch. * Two branches, one which which will be later the official release and one which will not be officially released. I would consider it as a fork since it would have Dojo/Prototype when the official will have later jQuery. Maybe fork is not really appropriate, but I think you get my point. We could also make 2 official releases. One with Dojo/Prototype and another with jQuery. I'm not quite sure switching from Dojo/Prototype to jQuery requires a specific release... Other opinions, ideas? Thanks Jacques Bruno Busco wrote: Why you think that making a new release branch would create a fork? It will be managed as we manage R10.04 and R9.04 right now. Only bug fixes will be backported. -Bruno 2010/12/2 Jacques Le Roux jacques.le.r...@les7arts.com Ryan Foster wrote: What about creating a tag or branch before the merge so that users who have custom projects or applications based on the trunk have a reference point in the event that they want to freeze their applications at a particular revision? Yes, that's what I have proposed. With another option: to have a branch. But I think the later is more a fork and I prefer the 1st. Oh and +1 on merging in JQuery. I am all for consolidating/simplifying our Javascript libraries. No reason to have 3 libraries that all essentially do the same thing. In the end, Javascript is Javascript. My heart says we should have chosen Prototype as that one (as anyone who knows me would agree, I'm a big Prototype JS evangelist). But, my head says that JQuery is the right choice for the long-term growth and success of the project, as it has definitely become the drug of choice for a majority of developers and has much more wide-spread community involvement as far as development of plugins is concerned. I think we now all agree on that Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Dec 2, 2010, at 11:18 AM, Jacques Le Roux wrote: I'm sorry for Bruno, but it seems everybody is looking forward for this merging. So hopefully I will do it soon. If you are interested you can already check https://issues.apache.org/jira/browse/OFBIZ-3814 Jacques Michael Xu (xudong) wrote: +1 Yeah, I would love such a great Xmas present :-) You're welcome +1 Would be a great Xmas present to merge all the stuff into the trunk :-) Am 02.12.2010 um 10:59 schrieb Erwan de FERRIERES erwan.de-ferrie...@nereide.fr: Le 02/12/2010 10:35, Jacques Le Roux a écrit : Looks like, apart Bruno, we are all on the same page so far Other opinions, ideas? Thanks Jacques The sooner the better ! Thanks for all your work, Jacques and Sascha -- Erwan de FERRIERES www.nereide.biz _ Lusini GmbH Karl Pitrich, Chief Technology Officer Adams-Lehmann-Straße 109, 80797 München Telefon +49 89 416170 113 Telefax +49 89 416170 190 E-Mail karl.pitr...@lusini.com Sitz der Gesellschaft: München, HRB 188366 Amtsgericht München, Geschäftsführer: Markus Bohl USt IdNr. DE 270565360, Steuernr. 152/131/90056 _ smime.p7s Description: S/MIME cryptographic signature
[jira] Commented: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898153#action_12898153 ] Karl Pitrich commented on OFBIZ-3889: - Please hang on, I will checkout the current trunk again, apply my changes and create a new patch. _ Lusini GmbH Adams-Lehmann-Straße 109, 80797 München Mobil +49 171 4970703 E-Mail karl.pitr...@lusini.com _ When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Assignee: Jacques Le Roux Priority: Minor Attachments: fixPortalDnD.diff, OFBIZ-3889 fixPortalDnD.patch When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898153#action_12898153 ] Karl Pitrich edited comment on OFBIZ-3889 at 8/13/10 6:06 AM: -- Please hang on, I will checkout the current trunk again, apply my changes and create a new patch. was (Author: 0xpit): Please hang on, I will checkout the current trunk again, apply my changes and create a new patch. _ Lusini GmbH Adams-Lehmann-Straße 109, 80797 München Mobil +49 171 4970703 E-Mail karl.pitr...@lusini.com _ When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Assignee: Jacques Le Roux Priority: Minor Attachments: fixPortalDnD.diff, OFBIZ-3889 fixPortalDnD.patch When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pitrich updated OFBIZ-3889: Attachment: OFBIZ-3889_fixPortalDnD.trunk-985143.patch Attached new patch against trunk 985143. Tested with Chrome, Safari and Firefox. When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Assignee: Jacques Le Roux Priority: Minor Attachments: fixPortalDnD.diff, OFBIZ-3889 fixPortalDnD.patch, OFBIZ-3889_fixPortalDnD.trunk-985143.patch When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897648#action_12897648 ] Karl Pitrich commented on OFBIZ-3889: - I promise to read the doc prior my next patch :) thank you. When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Assignee: Jacques Le Roux Priority: Minor Attachments: fixPortalDnD.diff When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pitrich updated OFBIZ-3889: Attachment: fixPortalDnD.diff Fix for described Issues. When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Priority: Minor Attachments: fixPortalDnD.diff When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Priority: Minor Attachments: fixPortalDnD.diff When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3889) When editing Portal Pages, Drag Drop for Portlets does not work
[ https://issues.apache.org/jira/browse/OFBIZ-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12897396#action_12897396 ] Karl Pitrich commented on OFBIZ-3889: - Hi, strange. I'm certain diff'ed against the current trunk, gut co'd it ... sorry. the only change in PortalAdmScreens.xml are the addition of these tho lines marked with +: set field=headerItem value=PortalPageAdminItem/ +set field=layoutSettings.javaScripts[] value=/images/myportal.js global=true/ +set field=layoutSettings.styleSheets[+0] value=/images/myportal.css global=true/ - Karl _ Lusini GmbH Adams-Lehmann-Straße 109, 80797 München Mobil +49 171 4970703 E-Mail karl.pitr...@lusini.com _ When editing Portal Pages, Drag Drop for Portlets does not work - Key: OFBIZ-3889 URL: https://issues.apache.org/jira/browse/OFBIZ-3889 Project: OFBiz Issue Type: Bug Components: framework, specialpurpose/myportal Affects Versions: Release Branch 10.04, SVN trunk Reporter: Karl Pitrich Assignee: Jacques Le Roux Priority: Minor Attachments: fixPortalDnD.diff When editing Portlet Pages, either in MyPortal or PortalAdm, Drag Drop of Portlets does not work. Where are several Issues in the MyPortal, some have fixes, none is commited to trunk. Problems: - in myportal.js, function getDestinationInformationPortlets(): DOM ID's are not handled correctly - in framework/webtools/widget/PortalAdmScreens.xml: required javascript + css files are not included -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.