should the tooltip help functionality be listed in new features?
Should the tooltip help functionality be listed in new features? Many thanks, Chris
Fwd: [Travel Assistance] - Applications Open for ApacheCon NA 2010
Begin forwarded message: From: Gav... ga...@16degrees.com.au Date: May 17, 2010 1:25:39 AM GMT+02:00 To: p...@apache.org Subject: [Travel Assistance] - Applications Open for ApacheCon NA 2010 Reply-To: priv...@ofbiz.apache.org Hi PMC's Please distribute this notice to your user and dev lists: The Travel Assistance Committee is now taking in applications for those wanting to attend ApacheCon North America (NA) 2010, which is taking place between the 1st and 5th November in Atlanta. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon, but who need some financial support in order to be able to get there. There are limited places available, and all applications will be scored on their individual merit. Financial assistance is available to cover travel to the event, either in part or in full, depending on circumstances. However, the support available for those attending only the barcamp is smaller than that for people attending the whole event. The Travel Assistance Committee aims to support all ApacheCons, and cross-project events, and so it may be prudent for those in Asia and the EU to wait for an event closer to them. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance are now being accepted, and will close on the 7th July 2010. Good luck to all those that will apply. You are welcome to tweet, blog as appropriate. Regards, The Travel Assistance Committee.
Re: Making the dev process work for me.
Thanks Ean - I will take a look at GIT... If you could make your changes in a cloned GIT repository we might be able to review and commit them en masse. On 05/15/2010 01:45 AM, chris snow wrote: On 15 May 2010 07:38, chris snowchsnow...@googlemail.com wrote: A while back, I had a small improvement committed to provide field tooltip help. I now have the time consuming process of extracting the tooltip help text from the manager references and putting it into the xml property files. The problem is that I have to rely on commiters to take my patches, review and commit them. Erwan is kindly reviewing my patch for the ProductStore and will hopefully commit it at some stage. However, committers have other priorities and getting the huge amount of patches that I will be providing to be committed is going to be very timeconsuming! Contributing to the problem is that I don't want to spend more that half a day on a single patch - I can't aford to lose time on writing patches that may not get committed. Is it possible to give fine grained svn access, I.e. just to the property files that contain the field descriptions? -- Chris Snow - CEng MBCS CITP MBA (Tech Mgmt) (Open) CISSP Tel: 01453 890660 Mob: 07944 880950 Www: www.snowconsulting.co.uk
Re: Making the dev process work for me.
Le 15/05/2010 08:38, chris snow a écrit : A while back, I had a small improvement committed to provide field tooltip help. I now have the time consuming process of extracting the tooltip help text from the manager references and putting it into the xml property files. The problem is that I have to rely on commiters to take my patches, review and commit them. Erwan is kindly reviewing my patch for the ProductStore and will hopefully commit it at some stage. However, committers have other priorities and getting the huge amount of patches that I will be providing to be committed is going to be hard work! Another problem is that I don't want to spend more that half a day on a single patch - I can't aford to lose time on writing patches that may not get committed. Is it possible to give fine grained svn access, I.e. just to the prop Hi Chris, sorry for taking so long for committing your patch... I was a bit busy, and this has been out of my head... Moreover, I was like Jacques sometimes ago with some Internet problems ! So, thanks for those who reviewed and committed instead of me ! -- Erwan de FERRIERES www.nereide.biz
[jira] Updated: (OFBIZ-3693) Allow to open a layer lookup from a layer lookup recursively
[ https://issues.apache.org/jira/browse/OFBIZ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-3693: --- Attachment: OFBIZ-3693_RecurLookup.patch Hey, I have a patch for the recursive lookup problem. But this patch won't work by the [https://localhost:8443/accounting/control/EditAgreementWorkEffortApplics] Lookups. Because, the Lookup definds a normal link (A Tag) as Submit Request. The Layered Lookups looks for a form submit Button to modify and call an ajax request. I don't know why here isn't a such a submit button, strange anyways. The solution for the recursive call is simple, the form were equal in the lookups, thats why it won't work. I make them unique. Allow to open a layer lookup from a layer lookup recursively Key: OFBIZ-3693 URL: https://issues.apache.org/jira/browse/OFBIZ-3693 Project: OFBiz Issue Type: Sub-task Reporter: Jacques Le Roux Attachments: OFBIZ-3693 fieldlookup.js.patch, OFBIZ-3693_RecurLookup.patch This is a special case of OFBIZ-3446 where not only you call a lookup from a lookup but also you can the same type of lookup (for instance a workeffort parent from a workeffort). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3469) Link back to login page from Forgot Password page
[ https://issues.apache.org/jira/browse/OFBIZ-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated OFBIZ-3469: -- Attachment: back.patch Here is the patch which fixes the issue. HTH :) Link back to login page from Forgot Password page - Key: OFBIZ-3469 URL: https://issues.apache.org/jira/browse/OFBIZ-3469 Project: OFBiz Issue Type: Bug Components: party Affects Versions: SVN trunk Environment: Demo site, IE 8 Reporter: Koon Sang Assignee: Jacques Le Roux Priority: Trivial Attachments: back.patch There should be a link back to login page in Forgot Password page (https://ofbiz-vm.apache.org/partymgr/control/forgotPassword) in case the user wants to cancel his operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: should the tooltip help functionality be listed in new features?
Yes sure! Jacques From: chris snow chsnow...@googlemail.com Should the tooltip help functionality be listed in new features? Many thanks, Chris
Re: Making the dev process work for me.
Hi Erwan, The problem with commit lag is not caused by any one person, it is a problem with the process. Based on feedback from others, I think the way around it will be to get my own svn/git branch running and do my work there. I can then submit patches back upstream and not have to worry about the commit lag. Many thanks, Chris Hi Chris, sorry for taking so long for committing your patch... I was a bit busy, and this has been out of my head... Moreover, I was like Jacques sometimes ago with some Internet problems ! So, thanks for those who reviewed and committed instead of me ! -- Erwan de FERRIERES www.nereide.biz
[jira] Created: (OFBIZ-3773) When we use a popup lookup we can't call layered lookups from it.
When we use a popup lookup we can't call layered lookups from it. - Key: OFBIZ-3773 URL: https://issues.apache.org/jira/browse/OFBIZ-3773 Project: OFBiz Issue Type: Sub-task Reporter: Jacques Le Roux Assignee: Jacques Le Roux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3693) Allow to open a layer lookup from a layer lookup recursively
[ https://issues.apache.org/jira/browse/OFBIZ-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-3693: --- Attachment: OFBIZ-3693_testing.patch Hi Sascha, I tried your patch but it does not work with the content case either. I checked the lookup content (which actually extends FinSurvey) does use the submit button. The attached testing patch makes certainly easier to share our tests. Note that I have not changed the other lookups inside FinSurvey to window and I get any responses either. Thanks for your help Allow to open a layer lookup from a layer lookup recursively Key: OFBIZ-3693 URL: https://issues.apache.org/jira/browse/OFBIZ-3693 Project: OFBiz Issue Type: Sub-task Reporter: Jacques Le Roux Attachments: OFBIZ-3693 fieldlookup.js.patch, OFBIZ-3693_RecurLookup.patch, OFBIZ-3693_testing.patch This is a special case of OFBIZ-3446 where not only you call a lookup from a lookup but also you can the same type of lookup (for instance a workeffort parent from a workeffort). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3469) Link back to login page from Forgot Password page
[ https://issues.apache.org/jira/browse/OFBIZ-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868142#action_12868142 ] Jacques Le Roux commented on OFBIZ-3469: Thanks Ankit, Your patch is in trunk at r945037 Link back to login page from Forgot Password page - Key: OFBIZ-3469 URL: https://issues.apache.org/jira/browse/OFBIZ-3469 Project: OFBiz Issue Type: Bug Components: party Affects Versions: SVN trunk Environment: Demo site, IE 8 Reporter: Koon Sang Assignee: Jacques Le Roux Priority: Trivial Attachments: back.patch There should be a link back to login page in Forgot Password page (https://ofbiz-vm.apache.org/partymgr/control/forgotPassword) in case the user wants to cancel his operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OFBIZ-3469) Link back to login page from Forgot Password page
[ https://issues.apache.org/jira/browse/OFBIZ-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-3469: Ankit, I reverted r945037 at r945042 Because I found it's not right when going back from logout - forgot password, I got this error message org.ofbiz.webapp.control.RequestHandlerException: Unknown request [authview]; this request does not exist or cannot be called directly. Link back to login page from Forgot Password page - Key: OFBIZ-3469 URL: https://issues.apache.org/jira/browse/OFBIZ-3469 Project: OFBiz Issue Type: Bug Components: party Affects Versions: SVN trunk Environment: Demo site, IE 8 Reporter: Koon Sang Assignee: Jacques Le Roux Priority: Trivial Attachments: back.patch There should be a link back to login page in Forgot Password page (https://ofbiz-vm.apache.org/partymgr/control/forgotPassword) in case the user wants to cancel his operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3469) Link back to login page from Forgot Password page
[ https://issues.apache.org/jira/browse/OFBIZ-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated OFBIZ-3469: -- Attachment: BACK.patch Hello Jacques, i found the reason its because some controller dont have the request [authview] ,so at some places like content,.. its giving the above error but working at many places like party, accounting, order,... So i add the request in common-controller attached the patch for it. Thanks :) Link back to login page from Forgot Password page - Key: OFBIZ-3469 URL: https://issues.apache.org/jira/browse/OFBIZ-3469 Project: OFBiz Issue Type: Bug Components: party Affects Versions: SVN trunk Environment: Demo site, IE 8 Reporter: Koon Sang Assignee: Jacques Le Roux Priority: Trivial Attachments: BACK.patch, back.patch There should be a link back to login page in Forgot Password page (https://ofbiz-vm.apache.org/partymgr/control/forgotPassword) in case the user wants to cancel his operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3773) When we use a popup lookup we can't call layered lookups from it.
[ https://issues.apache.org/jira/browse/OFBIZ-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868159#action_12868159 ] Jacques Le Roux commented on OFBIZ-3773: If someone try to use a layered lookup from a popup lookup it will not work. Maybe we should simply show a message explaining it's not possible. I don't know yet because I wonder if we should keep the popup feature when all cases will have been handled for layers... When we use a popup lookup we can't call layered lookups from it. - Key: OFBIZ-3773 URL: https://issues.apache.org/jira/browse/OFBIZ-3773 Project: OFBiz Issue Type: Sub-task Reporter: Jacques Le Roux Assignee: Jacques Le Roux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-3544) Incorrect Data Format
[ https://issues.apache.org/jira/browse/OFBIZ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-3544. -- Resolution: Not A Problem I close as not a problem. It's ok to show in this easier to read format. Because you should not change your birth date once set, and not so often the passport date Incorrect Data Format - Key: OFBIZ-3544 URL: https://issues.apache.org/jira/browse/OFBIZ-3544 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 09.04 Environment: IE Reporter: Koon Sang Assignee: Jacques Le Roux Fix For: Release Branch 09.04 Attachments: date.patch After login to Ecommerce, go to Profile and update Personal Information. Enter a valid date for Birth Date and Passport Expire Date (format: -mm-dd). Click Save. Once back to the main screen, click on Update again to update the Personal Information. You will see that the two dates are displayed in wrong date formats, e.g. Aug 25, 1972. So, the date is formatted wrongly somewhere. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Charting in OFBiz
Hi all, Following the discussion about charting and which library to use, I've added at rev. 945044 a full set of charting capabilities to OFBiz. Those is based on flotr, a library using prototype. Its under a MIT license, so there is no problem. The example on how to use it is in the example component. 2 new screens have been added, one for a bar chart, the other for a pie chart. In order to have data to display, you need to create new examples, and use different types, so it would be nicer. The charts are based on a view, which counts the types and totals related to them. From the screens in example, you will see it has a great extending capacity. New chart types can be included, they just have to be developped. Examples on what can be displayed are just a click away : http://phenxdesign.net/projects/flotr/examples/prototype/ Regards, -- Erwan de FERRIERES www.nereide.biz
[jira] Commented: (OFBIZ-3773) When we use a popup lookup we can't call layered lookups from it.
[ https://issues.apache.org/jira/browse/OFBIZ-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868161#action_12868161 ] Jacques Le Roux commented on OFBIZ-3773: A good example at the moment at https://demo-trunk.ofbiz.apache.org/content/control/FindSurvey. But it will dissapear in a day since I fixed it today... When we use a popup lookup we can't call layered lookups from it. - Key: OFBIZ-3773 URL: https://issues.apache.org/jira/browse/OFBIZ-3773 Project: OFBiz Issue Type: Sub-task Reporter: Jacques Le Roux Assignee: Jacques Le Roux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-3469) Link back to login page from Forgot Password page
[ https://issues.apache.org/jira/browse/OFBIZ-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-3469. -- Fix Version/s: SVN trunk Resolution: Fixed Thanks Ankit, Your last patch is in trunk at r945061 Link back to login page from Forgot Password page - Key: OFBIZ-3469 URL: https://issues.apache.org/jira/browse/OFBIZ-3469 Project: OFBiz Issue Type: Bug Components: party Affects Versions: SVN trunk Environment: Demo site, IE 8 Reporter: Koon Sang Assignee: Jacques Le Roux Priority: Trivial Fix For: SVN trunk Attachments: BACK.patch, back.patch There should be a link back to login page in Forgot Password page (https://ofbiz-vm.apache.org/partymgr/control/forgotPassword) in case the user wants to cancel his operation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3544) Incorrect Data Format
[ https://issues.apache.org/jira/browse/OFBIZ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868214#action_12868214 ] Jacques Le Roux commented on OFBIZ-3544: I finally committed Ankit's patch, when he convinced me that this is not working well when you are editing another field Committed in trunk at r945118 R9.04 at r945122 R10.04 at r945123 Thanks Ankit! Incorrect Data Format - Key: OFBIZ-3544 URL: https://issues.apache.org/jira/browse/OFBIZ-3544 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 09.04 Environment: IE Reporter: Koon Sang Assignee: Jacques Le Roux Fix For: Release Branch 09.04 Attachments: date.patch After login to Ecommerce, go to Profile and update Personal Information. Enter a valid date for Birth Date and Passport Expire Date (format: -mm-dd). Click Save. Once back to the main screen, click on Update again to update the Personal Information. You will see that the two dates are displayed in wrong date formats, e.g. Aug 25, 1972. So, the date is formatted wrongly somewhere. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3544) Incorrect Data Format
[ https://issues.apache.org/jira/browse/OFBIZ-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868216#action_12868216 ] Ankit Jain commented on OFBIZ-3544: --- Thanks Jacques HTH :) Incorrect Data Format - Key: OFBIZ-3544 URL: https://issues.apache.org/jira/browse/OFBIZ-3544 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: Release Branch 09.04 Environment: IE Reporter: Koon Sang Assignee: Jacques Le Roux Fix For: Release Branch 09.04 Attachments: date.patch After login to Ecommerce, go to Profile and update Personal Information. Enter a valid date for Birth Date and Passport Expire Date (format: -mm-dd). Click Save. Once back to the main screen, click on Update again to update the Personal Information. You will see that the two dates are displayed in wrong date formats, e.g. Aug 25, 1972. So, the date is formatted wrongly somewhere. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-3586) application - manufacturing
[ https://issues.apache.org/jira/browse/OFBIZ-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Geisert reassigned OFBIZ-3586: Assignee: Christian Geisert application - manufacturing --- Key: OFBIZ-3586 URL: https://issues.apache.org/jira/browse/OFBIZ-3586 Project: OFBiz Issue Type: Sub-task Reporter: Bob Morley Assignee: Christian Geisert Attachments: OFBIZ-3586_ResolveWarningsManufacturing.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r944675 - in /ofbiz/trunk/applications/product: config/ProductEntityLabels.xml entitydef/entitymodel.xml
+1 Cheers, Ruppert On May 16, 2010, at 10:37 AM, Bruno Busco wrote: Thank you. I will do that. -Bruno 2010/5/15 Ashish Vijaywargiya vijaywargiya.ash...@gmail.com +1. -- Ashish On Sat, May 15, 2010 at 10:54 PM, Christopher Snow sno...@snowconsulting.co.uk wrote: I think it should be ok to backport patches that only add documentation. On 15/05/10 17:17, Bruno Busco wrote: What you guys think about backporting patches like this that only add documentation to the 10.04 release branch? 2010/5/15bus...@apache.org Author: buscob Date: Sat May 15 16:14:14 2010 New Revision: 944675 URL: http://svn.apache.org/viewvc?rev=944675view=rev Log: A patch from Chris Snow OFBIZ-3747 - ProductStore missing field title help https://issues.apache.org/jira/browse/OFBIZ-3747 Thank you Chris for your patch and your patience. Modified: ofbiz/trunk/applications/product/config/ProductEntityLabels.xml ofbiz/trunk/applications/product/entitydef/entitymodel.xml Modified: ofbiz/trunk/applications/product/config/ProductEntityLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductEntityLabels.xml?rev=944675r1=944674r2=944675view=diff == --- ofbiz/trunk/applications/product/config/ProductEntityLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductEntityLabels.xml Sat May 15 16:14:14 2010 @@ -2637,4 +2637,237 @@ value xml:lang=thขภงเถื่ภน/value value xml:lang=zh被盗/value /property + +!-- Field Descriptions -- +!-- ProductStore -- +property key=FieldDescription.ProductStore.productStoreId +value xml:lang=enThe id for the product store../value +/property +property key=FieldDescription.ProductStore.primaryStoreGroupId +value xml:lang=enWhat group this store belongs to. Stores can be grouped together with a price for each store group. It can be left blank if there are no store groups set up./value +!-- Store groups cannot be set up in the catalog manager and must be inserted directly into the database. -- +/property +property key=FieldDescription.ProductStore.storeName +value xml:lang=enThis is the name of the store that this catalog represents./value +/property +property key=FieldDescription.ProductStore.companyName +value xml:lang=enThis is the name of the company that this catalog represents./value +/property +property key=FieldDescription.ProductStore.title +value xml:lang=enThis value gets displayed in the header section of the ecommerce store./value +/property +property key=FieldDescription.ProductStore.subtitle +value xml:lang=enThis value gets displayed in the header section of the ecommerce store./value +/property +property key=FieldDescription.ProductStore.payToPartyId +value xml:lang=enNote that this corresponds with the organizationPartyId that GL transactions will be posted to./value +/property +property key=FieldDescription.ProductStore.daysToCancelNonPay +value xml:lang=enTriggers cancellation of orders for non-payment after the number of days entered here./value +!-- There is an automated service that can be scheduled (see Job Scheduler in Webtools) nightly to cancel orders which have not been paid. This defines how many days an order can be outstanding and unpaid before it is canceled. A value of zero here will leave all orders open indefinitely. -- +/property +property key=FieldDescription.ProductStore.manualAuthIsCapture +value xml:lang=enDrop-down Y/N box on the question of whether a Manual Authorization is captured./value !-- TODO - what does this really mean? -- +/property +property key=FieldDescription.ProductStore.prorateShipping +value xml:lang=enWhen some share of the cost of shipping is covered under an account other than the bill-to./value !-- TODO - what does this really mean? -- +/property +property key=FieldDescription.ProductStore.prorateTaxes +value xml:lang=en/value +/property +property key=FieldDescription.ProductStore.viewCartOnAdd +value xml:lang=enControls whether the user is taken to the shopping cart immediately after adding a product to his cart./value +/property +property key=FieldDescription.ProductStore.autoSaveCart +value xml:lang=enDrop-down Y/N box on the question of automatically saving the contents of the shopping cart./value +/property +property key=FieldDescription.ProductStore.autoApproveReviews +value xml:lang=enIf the site allows users to enter product reviews, this controls whether the reviews must be approved, or whether they are automatically shown on the site./value +/property +property key=FieldDescription.ProductStore.isDemoStore +value xml:lang=enIf Yes, any orders created will not be sent, credit card charges will not be made, etc. +/value +/property +property key=FieldDescription.ProductStore.isImmediatelyFulfilled +value xml:lang=enIf Yes, the
Re: https://demo.ofbiz.org
Yes - that should not be the case. I will have it fixed ASAP (if it's still something I can!). Cheers, Ruppert -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 16, 2010, at 9:56 AM, Jacques Le Roux wrote: Hi, I just noticed that https://demo.ofbiz.org is redirecting to stable. Should we not redirect to trunk rather? Jacques
Re: Charting in OFBiz
Hi Erwan, thank you for your work on this subject. I think it will be very usefull. BTW I have tested it on the demo server right now but this link: https://demo-trunk.ofbiz.apache.org/example/control/BarChart gives an error: org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen [component://example/widget/example/ExampleScreens.xml#BarChart]: java.lang.IllegalArgumentException: In find entity by condition could not find definition for entity with name [ExampleCountByType]. (In find entity by condition could not find definition for entity with name [ExampleCountByType].) Could you please check if something is missing? (I did not tested it yet locally) I think it would be the best to have a single entry in the example application menu named Chart examples and then several different screens (they can become many) at a lower level. I used this arrangement in the geo-localizzation example. Thank you, Bruno 2010/5/17 Erwan de FERRIERES erwan.de-ferrie...@nereide.fr Hi all, Following the discussion about charting and which library to use, I've added at rev. 945044 a full set of charting capabilities to OFBiz. Those is based on flotr, a library using prototype. Its under a MIT license, so there is no problem. The example on how to use it is in the example component. 2 new screens have been added, one for a bar chart, the other for a pie chart. In order to have data to display, you need to create new examples, and use different types, so it would be nicer. The charts are based on a view, which counts the types and totals related to them. From the screens in example, you will see it has a great extending capacity. New chart types can be included, they just have to be developped. Examples on what can be displayed are just a click away : http://phenxdesign.net/projects/flotr/examples/prototype/ Regards, -- Erwan de FERRIERES www.nereide.biz
Re: Charting in OFBiz
Bruno, It's because I updated manually for a bug I fixed in layered lookup but I did not take the time to make the whole update process (I only svn updated and ant svninfo). The bot will do it soon (every 24h) So you have to try it locally for now... Jacques From: Bruno Busco bruno.bu...@gmail.com Hi Erwan, thank you for your work on this subject. I think it will be very usefull. BTW I have tested it on the demo server right now but this link: https://demo-trunk.ofbiz.apache.org/example/control/BarChart gives an error: org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen [component://example/widget/example/ExampleScreens.xml#BarChart]: java.lang.IllegalArgumentException: In find entity by condition could not find definition for entity with name [ExampleCountByType]. (In find entity by condition could not find definition for entity with name [ExampleCountByType].) Could you please check if something is missing? (I did not tested it yet locally) I think it would be the best to have a single entry in the example application menu named Chart examples and then several different screens (they can become many) at a lower level. I used this arrangement in the geo-localizzation example. Thank you, Bruno 2010/5/17 Erwan de FERRIERES erwan.de-ferrie...@nereide.fr Hi all, Following the discussion about charting and which library to use, I've added at rev. 945044 a full set of charting capabilities to OFBiz. Those is based on flotr, a library using prototype. Its under a MIT license, so there is no problem. The example on how to use it is in the example component. 2 new screens have been added, one for a bar chart, the other for a pie chart. In order to have data to display, you need to create new examples, and use different types, so it would be nicer. The charts are based on a view, which counts the types and totals related to them. From the screens in example, you will see it has a great extending capacity. New chart types can be included, they just have to be developped. Examples on what can be displayed are just a click away : http://phenxdesign.net/projects/flotr/examples/prototype/ Regards, -- Erwan de FERRIERES www.nereide.biz
Re: Charting in OFBiz
Le 17/05/2010 18:52, Bruno Busco a écrit : Hi Erwan, thank you for your work on this subject. I think it will be very usefull. BTW I have tested it on the demo server right now but this link: https://demo-trunk.ofbiz.apache.org/example/control/BarChart gives an error: org.ofbiz.widget.screen.ScreenRenderException: Error rendering screen [component://example/widget/example/ExampleScreens.xml#BarChart]: java.lang.IllegalArgumentException: In find entity by condition could not find definition for entity with name [ExampleCountByType]. (In find entity by condition could not find definition for entity with name [ExampleCountByType].) Could you please check if something is missing? (I did not tested it yet locally) Hi Bruno, Thanks for your inputs. I will then go this way. For the missing view, the view (ExampleCountByType) is missing. Just restarting the server should do the trick ! Cheers, The example on how to use it is in the example component. 2 new screens have been added, one for a bar chart, the other for a pie chart. In order to have data to display, you need to create new examples, and use different types, so it would be nicer. The charts are based on a view, which counts the types and totals related to them. From the screens in example, you will see it has a great extending capacity. New chart types can be included, they just have to be developped. Examples on what can be displayed are just a click away : http://phenxdesign.net/projects/flotr/examples/prototype/ Regards, -- Erwan de FERRIERES www.nereide.biz -- Erwan de FERRIERES www.nereide.biz
[jira] Created: (OFBIZ-3774) Add The Visitor Pattern To Screen Widget Model Classes
Add The Visitor Pattern To Screen Widget Model Classes -- Key: OFBIZ-3774 URL: https://issues.apache.org/jira/browse/OFBIZ-3774 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Adrian Crum Priority: Minor From time to time there has been interest expressed in introducing the visitor pattern to the screen widget model classes. This issue is intended to provide a forum on the subject and a means to vote on it. Details are in the comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3774) Add The Visitor Pattern To Screen Widget Model Classes
[ https://issues.apache.org/jira/browse/OFBIZ-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-3774: --- Attachment: OFBIZ-3774.patch The attached patch is a beginning step - it has the visitor interface for the screen sub-widgets, and it adds the necessary accept method to the sub-widgets. There is no interface implementation. The screen widget model classes already use a pattern similar to visitor called double dispatch. Essentially, the ScreenStringRenderer implementation calls the renderWidgetString method of each widget, and that widget method calls the renderXxxx method in the ScreenStringRenderer. With the visitor pattern, the renderWidgetString method is called accept, and the renderXxxx method is called visit. So, it's basically the same design but with a slight difference. In the current code, the visitor (ScreenStringRenderer) passes a number of arguments to the model widget renderWidgetString method. In the attached patch, the visitor (ScreenWidgetVisitor) passes only itself as an argument to the model widget accept method. The reason for this difference is flexibility and expandability. Set up this way, the visitor could be anything - a renderer, an artifact info gatherer, a pretty printer, etc. There is no implementation implied in the design. Each renderer would implement ScreenWidgetVisitor. The code inside each model widget renderWidgetString method would be moved to the corresponding visit method in the renderer. Likewise, the artifact-info-gatherer would implement ScreenWidgetVisitor. The existing model widget artifact-info-gathering code would be moved to the corresponding visit method in the artifact-info-gatherer. Once those changes are made, the model widgets will contain only object construction code. Even that code could be moved to a builder class that implements ScreenWidgetVisitor. The benefit of this change will be improved separation of concerns. Right now the screen widget model classes try to be everything to everybody. After the change they will be little more than data structures that various behavior-specific objects will refer to. Rendering code is not mixed in with object construction code or with artifact-gathering code. The API is simplified. A change like this could have serious downstream consequences for OFBiz users who have modified the screen widget model classes. One approach we could take is to put the visit methods in ScreenStringRenderer (instead of having a separate interface) and then deprecate the existing renderXxxx methods. The downside is code maintainance - bug fixes and new features will have to be applied to both patterns. If you believe the change is worthwhile, then please vote on this issue. Add The Visitor Pattern To Screen Widget Model Classes -- Key: OFBIZ-3774 URL: https://issues.apache.org/jira/browse/OFBIZ-3774 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Adrian Crum Priority: Minor Attachments: OFBIZ-3774.patch From time to time there has been interest expressed in introducing the visitor pattern to the screen widget model classes. This issue is intended to provide a forum on the subject and a means to vote on it. Details are in the comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Screen Widget Ideas
I created a Jira issue for this subject: https://issues.apache.org/jira/browse/OFBIZ-3774 -Adrian On 5/15/2010 4:11 AM, Marc Morin wrote: Pure model objects with no behavior in them, and a visitor pattern to externalize the behavior man, that's music to my ears! We've added a visitor pattern to all the model objects, screens, forms, menus, entity, It has proven invaluable to enable walking and manipulating the model, without increasing the complexity of the underlying model objects. Also, as your specific example indicates, the renderers are a perfect use case for visitors, as the rendered is technically and interpreter of the model objects. Marc - Adrian Crumadrian.c...@yahoo.com wrote: --- On Fri, 5/14/10, Scott Grayscott.g...@hotwaxmedia.com wrote: On 15/05/2010, at 3:43 PM, Adrian Crum wrote: I've been thinking about some improvements to the screen widgets, and I thought I would offer some ideas and see if there is any interest. I'm kind of thinking out loud here, so the ideas are not fully developed. Please comment or add your suggestions. 1. Use the factory pattern to create model widgets. Right now model widget construction is handled internally with a pre-defined set of classes. The idea is to move the model widget creation to a factory method that accepts a candidate XML element. If a matching model widget is found, return it, otherwise throw an exception. The factory supports user-created model widgets, so the screen widgets are extensible. In other words, you can create your own model widgets, register them with the factory, and the screen renderer will use them just like any other widget. You could even create your own replacement implentations of existing OFBiz screen widgets. User-created widgets can use namespaces on the XML side to avoid XML parsing errors. That's crazy, I've been looking into this today. I had figured on using an include-widget tag. I was also thinking about the PITA way that we pass widget renderers around and wondering if we couldn't just have a render method on the model that takes a writer, the context and a content type. The model then has an internal factory that gets the configured renderer based on the content type. At least we're basically on the same page. My perspective all along is that the screen widgets should be nothing more than data structures in memory that support the visitor pattern. Renderers implement the visitor interface. Implementations of the visitor interface could be anything: HTML renderers, Swing renderers, artifact gatherers, layout managers (an intermediate form of renderer), pretty printers, etc. There is so much room for improvement, but experience has shown that the screen widgets have become a sort of sacred cow, so changes like that will be met with a lot of resistance. 2. Add Groovy support to theinclude-screen widget. If the location attribute ends with .groovy pass control to the specified Groovy script. The script would behave like a screen widget and it will have access to all model widgets - so existing widget code can still be used. This could help in certain cases where screen widgets can't fulfill a particular need. It has been suggested that CDATA elements be allowed in screen widgets so that free-form code can be inserted in widget XML - this is an alternative solution to that. The benefit is you can leverage the power of Groovy in controlling screen output. The drawback is any such script will break the structure of screen widgets and it will start to look like JSP - where data preparation code is mixed with presentation code. This sounds more like a custom renderer rather than something that should go into the model. It's not a custom renderer - the output is still the same as the original view. It's just a different way of looking at screen rendering. Instead of screen widgets calling scripts, a script calls screen widgets. In other words, instead of XML-generated-widgets being in charge of Groovy, Groovy is in charge of the XML-generated-widgets. Think about it. -Adrian
Re: https://demo.ofbiz.org
This is fixed - there was a bug in the redirect - thanks for reporting Jacques. Cheers, Ruppert On May 17, 2010, at 10:22 AM, Tim Ruppert wrote: Yes - that should not be the case. I will have it fixed ASAP (if it's still something I can!). Cheers, Ruppert -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 16, 2010, at 9:56 AM, Jacques Le Roux wrote: Hi, I just noticed that https://demo.ofbiz.org is redirecting to stable. Should we not redirect to trunk rather? Jacques
Re: https://demo.ofbiz.org
Thanks Tim, I know it's normal to get a blank page when you get to http://demo-trunk.ofbiz.apache.org/ or https://demo-trunk.ofbiz.apache.org/ But before when you typed https://demo.ofbiz.org You were actually redirected to something visible, I guess https://demo-stable.ofbiz.apache.org/catalog/control/login/main What have changed? Jacques From: Tim Ruppert tim.rupp...@hotwaxmedia.com This is fixed - there was a bug in the redirect - thanks for reporting Jacques. Cheers, Ruppert On May 17, 2010, at 10:22 AM, Tim Ruppert wrote: Yes - that should not be the case. I will have it fixed ASAP (if it's still something I can!). Cheers, Ruppert -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 16, 2010, at 9:56 AM, Jacques Le Roux wrote: Hi, I just noticed that https://demo.ofbiz.org is redirecting to stable. Should we not redirect to trunk rather? Jacques
Re: https://demo.ofbiz.org
We managed the redirect at Contegix. We should probably just put this up there in apache - I'm sure Gavin will help out make it happen on each of the instances. Cheers, Ruppert On May 17, 2010, at 3:18 PM, Jacques Le Roux wrote: Thanks Tim, I know it's normal to get a blank page when you get to http://demo-trunk.ofbiz.apache.org/ or https://demo-trunk.ofbiz.apache.org/ But before when you typed https://demo.ofbiz.org You were actually redirected to something visible, I guess https://demo-stable.ofbiz.apache.org/catalog/control/login/main What have changed? Jacques From: Tim Ruppert tim.rupp...@hotwaxmedia.com This is fixed - there was a bug in the redirect - thanks for reporting Jacques. Cheers, Ruppert On May 17, 2010, at 10:22 AM, Tim Ruppert wrote: Yes - that should not be the case. I will have it fixed ASAP (if it's still something I can!). Cheers, Ruppert -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 16, 2010, at 9:56 AM, Jacques Le Roux wrote: Hi, I just noticed that https://demo.ofbiz.org is redirecting to stable. Should we not redirect to trunk rather? Jacques
[jira] Commented: (OFBIZ-3774) Add The Visitor Pattern To Screen Widget Model Classes
[ https://issues.apache.org/jira/browse/OFBIZ-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868470#action_12868470 ] Marc Morin commented on OFBIZ-3774: --- We did a similar visitor pattern to the entire presentment (Screen, Form, Menu) space and the controller. This path, mainly separation of concern, is very powerful, and allows easy extension to the system. The typical implementation path that has been taken, is to develop a series of abstract visitors that have a few base behaviors, navigation of the components, and throwing exceptions for each component. This enables a specific visitors to extend the base navigation class, to get full model navigation and add any specific behavior with a surprisingly small amount of code. We've done Presentment visitors for walking, validation (examining location/name references looking for dangling screen/from/controller references, etc.. used in junit test cases - fail build if broken links), security auto-notation (propagates service security declarations, to screens model objects, and will automatically remove buttons, links to areas in the application that the user doesn't have rights to access.) We have a partial dump (pretty-print) for the PresentmentModel as well. Externalizing the creation of the model objects, is crucial to getting the full power of this type of change. The model objects should have nothing but their attributes with their getter/setter methods (and the accept). Add The Visitor Pattern To Screen Widget Model Classes -- Key: OFBIZ-3774 URL: https://issues.apache.org/jira/browse/OFBIZ-3774 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Adrian Crum Priority: Minor Attachments: OFBIZ-3774.patch From time to time there has been interest expressed in introducing the visitor pattern to the screen widget model classes. This issue is intended to provide a forum on the subject and a means to vote on it. Details are in the comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3774) Add The Visitor Pattern To Screen Widget Model Classes
[ https://issues.apache.org/jira/browse/OFBIZ-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868503#action_12868503 ] Adrian Crum commented on OFBIZ-3774: One thing I would like to clarify: the patch only includes screen sub-widgets, but the goal would be apply the visitor pattern to all screen widget model classes - like Marc mentioned. An abstract class for renderers that navigates the model structure probably won't work - because each rendering format will require its own sequence of events, or its own mode of navigation. You can't determine in advance how a particular rendering format will need to navigate the structure. The existing widget models try to do this form of prediction and it has caused problems in the past. I'm currently working on porting the macro renderer over to the visitor interface to see what kind of problems we might encounter. Add The Visitor Pattern To Screen Widget Model Classes -- Key: OFBIZ-3774 URL: https://issues.apache.org/jira/browse/OFBIZ-3774 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Adrian Crum Priority: Minor Attachments: OFBIZ-3774.patch From time to time there has been interest expressed in introducing the visitor pattern to the screen widget model classes. This issue is intended to provide a forum on the subject and a means to vote on it. Details are in the comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3775) IterateSectionWidget.java Is Not Thread-Safe
IterateSectionWidget.java Is Not Thread-Safe Key: OFBIZ-3775 URL: https://issues.apache.org/jira/browse/OFBIZ-3775 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 09.04, Release Branch 10.04, SVN trunk Reporter: Adrian Crum Multiple threads alter the model object's state. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Application names localizations are defined in the CommonUiLabels framework file
We've talked about this a number of times around the office, not only for the application menu but many menus throughout the site. This could allow a party/content binding component to inject menu entries into otherwise stand-alone party and content applications. Sorry if this is a repetition of ideas that have already been discussed. - Bruno Busco wrote: The injectable menu we are speaking about could be the solution. A simple main menu could be defined in the framework with only the Webtools and Example menu entry. Every application could inject its own application menu. An application could also inject menu entries in several different menus so that for example all application's administrations could be placed in one unique high level admin menu entry. -- Ean Schuessler, CTO e...@brainfood.com 214-720-0700 x 315 Brainfood, Inc. http://www.brainfood.com
[jira] Created: (OFBIZ-3776) ModelScreenWidget.Content Is Not Thread Safe
ModelScreenWidget.Content Is Not Thread Safe Key: OFBIZ-3776 URL: https://issues.apache.org/jira/browse/OFBIZ-3776 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 09.04, Release Branch 10.04, SVN trunk Reporter: Adrian Crum Rev 499264 introduced code that has multiple threads changing the state of the Content model. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
