Re: Discussion: Flat Grey Visual Theme
The themes repository should not actually be a SVN repository but the https://cwiki.apache.org/confluence/display/OFBIZ/Visual+Themes+Gallery can be a right place to host them. Simpler, easier to access. -Bruno 2011/1/7 Jacques Le Roux jacques.le.r...@les7arts.com OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/6/2011 2:51 PM: I completely agree with you BJ. Considerations definitely have to be made when things are removed, especially if they are tied to the framework. What is being discussed is whether to remove themes, which can be hot-deployed from being maintained in the trunk. For future releases, all you would need to do is manually add your themes, custom or otherwise, to your production instance. If they are no longer tied in svn to the trunk, they would not be effected by any updates or releases. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:40 PM, BJ Freeman wrote: so there will not be any more releases based on the trunk? I was speaking in the future when 11.04 or 12.04 happen. it is the disregard of those that actually use this software instead of just enjoy developing it. I am a developer second and a business man first. basically you can add all you want but when you want to remove you must consider those that have counted on what was provided. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:33 PM: The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freemanbjf...@free-man.net I have one that uses the flat grey as default so if I do an update from the svn the flat grey will and my customization disappear. my sas uses all those in the themes, with my modification. they will be removed. when the svn update is run. those are just a few examples. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:00 PM: I am sorry, BJ, I do not see your point. What could be the issue? We will have less themes to maintain in the trunk (just Flat Grey, Tomahawk, Default and Multiflex). We will have more people that will be able to maintain additional themes in the Themes Gallery. Production servers will have each one its selected theme (one of the OOTB, one of the Themes Gallery or a customized version of them). -Bruno 2011/1/6 BJ
[jira] Commented: (OFBIZ-4090) Add Support For Compound Screen Widget XML Files
[
https://issues.apache.org/jira/browse/OFBIZ-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978686#action_12978686
]
Adrian Crum commented on OFBIZ-4090:
Here is the root schema I tried:
{code}
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
elementFormDefault=qualified
xs:element name=root
xs:complexType
xs:all minOccurs=0 maxOccurs=1
xs:element name=site-conf/
xs:element name=simple-methods/
xs:element name=forms/
xs:element name=menus/
xs:element name=trees/
xs:element name=screens/
/xs:all
/xs:complexType
/xs:element
/xs:schema
{code}
In Eclipse, you can right-click on an XML element and a popup menu appears with
valid selections for that element - based on the schema. I can't provide a
screen shot because now the popup menu doesn't show any suggestions from the
schema. I'm almost certain it's a bug in Eclipse's XML editor.
Add Support For Compound Screen Widget XML Files
Key: OFBIZ-4090
URL: https://issues.apache.org/jira/browse/OFBIZ-4090
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: SVN trunk
Reporter: Adrian Crum
Priority: Minor
Attachments: CompoundWidgetFiles.patch, CompoundWidgetFiles.patch
Add the ability to include screen widgets, form widgets, menu widgets, and
simple methods in a single XML file. This approach could be used in
situations where the widgets share a logical grouping - so they can be kept
in one place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Discussion: Flat Grey Visual Theme
Yes, but it's not like that for the moment. And BJ complaint's are a reality for maybe more than one person... And what if you want to override a theme (solution 2 below) to follow its progress? Jacques From: Bruno Busco bruno.bu...@gmail.com The themes repository should not actually be a SVN repository but the https://cwiki.apache.org/confluence/display/OFBIZ/Visual+Themes+Gallery can be a right place to host them. Simpler, easier to access. -Bruno 2011/1/7 Jacques Le Roux jacques.le.r...@les7arts.com OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/6/2011 2:51 PM: I completely agree with you BJ. Considerations definitely have to be made when things are removed, especially if they are tied to the framework. What is being discussed is whether to remove themes, which can be hot-deployed from being maintained in the trunk. For future releases, all you would need to do is manually add your themes, custom or otherwise, to your production instance. If they are no longer tied in svn to the trunk, they would not be effected by any updates or releases. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:40 PM, BJ Freeman wrote: so there will not be any more releases based on the trunk? I was speaking in the future when 11.04 or 12.04 happen. it is the disregard of those that actually use this software instead of just enjoy developing it. I am a developer second and a business man first. basically you can add all you want but when you want to remove you must consider those that have counted on what was provided. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:33 PM: The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freemanbjf...@free-man.net I have one that uses the flat grey as default so if I do an update from the svn the flat grey will and my customization disappear. my sas uses all those in the themes, with my modification. they will be removed. when the svn update is run. those are just a few examples. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:00 PM: I am sorry, BJ, I do not see your point. What could be the issue? We will have less themes to maintain in the trunk (just Flat Grey, Tomahawk, Default and Multiflex). We will have more people that will be able to maintain additional themes in the Themes Gallery. Production servers will
[jira] Commented: (OFBIZ-4095) Catalog Help docbook files
[ https://issues.apache.org/jira/browse/OFBIZ-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978731#action_12978731 ] BJ Freeman commented on OFBIZ-4095: --- will do and thanks. have a lot more under catalog. Catalog Help docbook files -- Key: OFBIZ-4095 URL: https://issues.apache.org/jira/browse/OFBIZ-4095 Project: OFBiz Issue Type: Sub-task Components: product Affects Versions: SVN trunk Reporter: BJ Freeman Priority: Minor Attachments: OFBIZ-4095porduct1.patch top sub task for products component. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Discussion: Flat Grey Visual Theme
more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/6/2011 2:51 PM: I completely agree with you BJ. Considerations definitely have to be made when things are removed, especially if they are tied to the framework. What is being discussed is whether to remove themes, which can be hot-deployed from being maintained in the trunk. For future releases, all you would need to do is manually add your themes, custom or otherwise, to your production instance. If they are no longer tied in svn to the trunk, they would not be effected by any updates or releases. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:40 PM, BJ Freeman wrote: so there will not be any more releases based on the trunk? I was speaking in the future when 11.04 or 12.04 happen. it is the disregard of those that actually use this software instead of just enjoy developing it. I am a developer second and a business man first. basically you can add all you want but when you want to remove you must consider those that have counted on what was provided. = BJ Freeman Strategic Power Office with Supplier Automationhttp://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:33 PM: The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freemanbjf...@free-man.net I have one that uses the flat grey as default so if I do an update from the svn the flat grey will and my customization disappear.
Re: Discussion: Flat Grey Visual Theme
From: BJ Freeman bjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/6/2011 2:51 PM: I completely agree with you BJ. Considerations definitely have to be made when things are removed, especially if they are tied to the framework. What is being discussed is whether to remove themes, which can be hot-deployed from being maintained in the trunk. For future releases, all you would need to do is manually add your themes, custom or otherwise, to your production instance. If they are no longer tied in svn to the trunk, they would not be effected by any updates or releases. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:40 PM, BJ Freeman wrote: so there will not be any more releases based on the trunk? I was speaking in the future when 11.04 or 12.04 happen. it is the disregard of those that actually use this software instead of just enjoy developing it. I am a developer second and a business man first. basically you can add all you want but when you want to remove you must consider those that have counted on what was provided. = BJ Freeman Strategic Power Office with Supplier Automationhttp://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/6/2011 2:33 PM: The theme will still be present in the 10.04 releases. No production servers should rely on
Re: Discussion: Flat Grey Visual Theme
Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Roux jacques.le.r...@les7arts.com From: BJ Freeman bjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/6/2011 2:51 PM: I completely agree with you BJ. Considerations definitely have to be made when things are removed, especially if they are tied to the framework. What is being discussed is whether to remove themes, which can be hot-deployed from being maintained in the trunk. For future releases, all you would need to do is manually add your themes, custom or otherwise, to your production instance. If they are no longer tied in svn to the trunk, they would not be effected by any updates or releases. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:40 PM,
[jira] Closed: (OFBIZ-4093) Bizzness Time Theme - Unable to use preference or application menu
[ https://issues.apache.org/jira/browse/OFBIZ-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4093. -- Resolution: Fixed Fix Version/s: SVN trunk Release Branch 10.04 Release Branch 09.04 Assignee: Jacques Le Roux Thanks Scott, Your modified patch is in trunk at r1056333, R10.04 at r1056336, R9.04 at r1056335 FYI: you made a typo in visibility (was visbility) Bizzness Time Theme - Unable to use preference or application menu -- Key: OFBIZ-4093 URL: https://issues.apache.org/jira/browse/OFBIZ-4093 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Release Branch 10.04, SVN trunk Environment: User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB6.6; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDS; InfoPath.2; .NET CLR 1.1.4322; Tablet PC 2.0; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; .NET4.0C; .NAP 1.1) Timestamp: Wed, 29 Dec 2010 14:40:44 UTC Reporter: ScottA Assignee: Jacques Le Roux Fix For: Release Branch 09.04, Release Branch 10.04, SVN trunk Attachments: OFBIZ-4093_Bizzness_Time_Theme_IE_Fix.patch I am using Win7 Pro, IE 8.0.7600 and when I log into current trunk, Business time theme, I am unable to use the applications or preferences menu. The page is here; https://demo-trunk.ofbiz.apache.org/catalog/control/login/main?USERNAME=flexadminPASSWORD=ofbizJavaScriptEnabled=Y# The dropdown menu will not open at all. Appears to work fine in Firefox. The only error I get is the following; Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB6.6; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MDDS; InfoPath.2; .NET CLR 1.1.4322; Tablet PC 2.0; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; .NET4.0C; .NAP 1.1) Timestamp: Wed, 29 Dec 2010 14:40:44 UTC Message: Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus. Line: 85 Char: 7 Code: 0 URI: https://demo-trunk.ofbiz.apache.org/bizznesstime/js/application.js -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Discussion: Flat Grey Visual Theme
I understand BJ concerns, but again, I'm with Bruno on this. Themes are modular and preferential by nature. Not every user will want or have a need for every theme. For instance, if I develop a women's boutique front-end theme, it may be of great interest to an owner of a women's boutique but the owner of an auto parts store could probably care less. Why not leave 2-3 official release themes in the trunk that are up to date and maintained consistently by the community and move everything else to an external directory. Then, let the user/developer pick and choose what themes to install. In the end, we all decide whether we want to contribute the code we develop back to the code base or not. For existing themes, my vote is to keep the active themes in the trunk and move the deprecated/ unsupported / un-evolved themes out to the theme gallery. This means BizznessTime?(which unfortunately seems to be rapidly losing community backing), Bluelight, and DroppingCrumbs. For future themes that I develop, the choice is easy for me. I will simply not grant the theme ASF license to be included in the trunk. I will release the theme to the public and post the theme to the theme gallery or distribute through some other method. If we decide to create a new theme from Flat Grey, I am calling the new theme Dorian Gray (http://en.wikipedia.org/wiki/Dorian_Gray). The new theme will continue to look young, fresh and modern, while it's reflection, Flat Grey, will continue to look older and more dated with each passing year... ;) Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 5:06 AM, Bruno Busco wrote: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Roux jacques.le.r...@les7arts.com From: BJ Freeman bjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't
Re: Discussion: Flat Grey Visual Theme
From: Bruno Busco bruno.bu...@gmail.com Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. Mmm, I can't see any examples on how to maintain themes database there http://www.templatemonster.com is actually a 3rd site which is selling templates The others simply provide a way to dowload templates. With a bit more information than we give at https://cwiki.apache.org/confluence/display/OFBIZ/Visual+Themes+Gallery. I agree we could update it according to your proposition. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. It's ok with me. It seems to be only a problem for BJ, but I know other sites which are using the same technique and override OOTB templates, they will have to adapt... I think we should simply put a link to our Visual Themes Gallery from the ListVisualThemes page. Jacques -Bruno 2011/1/7 Jacques Le Roux jacques.le.r...@les7arts.com From: BJ Freeman bjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freeman bjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man
Re: Discussion: Flat Grey Visual Theme
to paraphrase what I think you said the current themes are not independent of each other so can not be removed, without causing failure in another The links you gave and the themes depository in wiki will not facilitate an end user on selecting or installing the themes from ofbiz like the current theme selection. again the rule is not to remove what is already put in Update and modify only. Now if all new themes are put in the themes gallery I see no problem with that. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 4:06 AM: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Rouxjacques.le.r...@les7arts.com From: BJ Freemanbjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freemanbjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk, then perhaps you should fund their upkeep. -Adrian On 1/6/2011 2:58 PM, BJ Freeman wrote: so you will be glad to fund the effort to do that. Time is money. and anything the effects the ROI needs to be considered, if the software is to be widely accepted. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52
Re: Discussion: Flat Grey Visual Theme
Bruno says: Dependencies between themes do not allow modular selection, distribution and installation. You say they are modular. David has commented that he started this project with Idea that Trained consultants in ofbiz would be paid to install modify, and customize ofbiz. That model in my opinion does not work, as David has since said, with open source. Especially being in ASF. I have some modules that once the design time has be amortized I will release to open source. Till then they cost. However my main thrust with ofbiz is first make it widely accepted so by sheer numbers, there will those that want to hire consultants. So my focus is a good online embedded Doc and help, along with a flexible and powerful setup that will lead a end user through a complete setup. Part of that setup is a java based component that will go get ofbiz and download it then ask if they want demo or Production setup. I can see in that phase of the setup making the end user aware of themes in galleries they can then have installed. To that end I believe the current themes should be left in place and future themes that people want to get paid for be put on their own website where they can amortize their efforts. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/7/2011 8:52 AM: I understand BJ concerns, but again, I'm with Bruno on this. Themes are modular and preferential by nature. Not every user will want or have a need for every theme. For instance, if I develop a women's boutique front-end theme, it may be of great interest to an owner of a women's boutique but the owner of an auto parts store could probably care less. Why not leave 2-3 official release themes in the trunk that are up to date and maintained consistently by the community and move everything else to an external directory. Then, let the user/developer pick and choose what themes to install. In the end, we all decide whether we want to contribute the code we develop back to the code base or not. For existing themes, my vote is to keep the active themes in the trunk and move the deprecated/ unsupported / un-evolved themes out to the theme gallery. This means BizznessTime?(which unfortunately seems to be rapidly losing community backing), Bluelight, and DroppingCrumbs. For future themes that I develop, the choice is easy for me. I will simply not grant the theme ASF license to be included in the trunk. I will release the theme to the public and post the theme to the theme gallery or distribute through some other method. If we decide to create a new theme from Flat Grey, I am calling the new theme Dorian Gray (http://en.wikipedia.org/wiki/Dorian_Gray). The new theme will continue to look young, fresh and modern, while it's reflection, Flat Grey, will continue to look older and more dated with each passing year... ;) Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 5:06 AM, Bruno Busco wrote: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Rouxjacques.le.r...@les7arts.com From: BJ Freemanbjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see
a full setup for ofbiz
I use http://izpack.org/documentation/ which is like windows installer and is java based. the I am not sure if the Creative Commons Attribution-ShareAlike 3.0 Unported License. is compatible with ASF. however I believe like other binaries they can be worked around. this would allow one link to setup. let the person installing create: Developmental Demo Production system. it would to check and download for missing pieces, like the JDK. eventually the setup would run the ant install in appropriate for their use. I see the scripts for this to be in the setup component where anyone can put scripts particular to thier interests that izpack will pull from the svn. any thoughts? = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man
Re: Discussion: Flat Grey Visual Theme
On Jan 7, 2011, at 10:17 AM, BJ Freeman wrote: David has commented that he started this project with Idea that Trained consultants in ofbiz would be paid to install modify, and customize ofbiz. That model in my opinion does not work, as David has since said, with open source. Especially being in ASF. I don't believe I ever said any such thing. In fact, I've said many times that most users of OFBiz do everything on their own and never hire a consultant, and for the project that is a very good thing. Not everyone will want to do that, and it won't always be the most cost-effective (and certainly not time-effective) thing to do, so there is certainly a market for consulting. However, that is not and never should be considered a requirement for using the project or a design objective of the project. Not ever. -David
Re: Discussion: Flat Grey Visual Theme
I apologize is I paraphrased this wrong http://mail-archives.apache.org/mod_mbox/ofbiz-user/201009.mbox/%3c7ddc589c-fce5-4e71-97c9-f5f8147ab...@me.com%3e = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man David E Jones sent the following on 1/7/2011 10:58 AM: On Jan 7, 2011, at 10:17 AM, BJ Freeman wrote: David has commented that he started this project with Idea that Trained consultants in ofbiz would be paid to install modify, and customize ofbiz. That model in my opinion does not work, as David has since said, with open source. Especially being in ASF. I don't believe I ever said any such thing. In fact, I've said many times that most users of OFBiz do everything on their own and never hire a consultant, and for the project that is a very good thing. Not everyone will want to do that, and it won't always be the most cost-effective (and certainly not time-effective) thing to do, so there is certainly a market for consulting. However, that is not and never should be considered a requirement for using the project or a design objective of the project. Not ever. -David
Re: Discussion: Flat Grey Visual Theme
I don't want to misquote Bruno, but I believe what he was saying was if we create dependencies between themes, it does not allow modular selection, distribution, and installation. Not that those dependencies already exist, because they don't. I am not saying that I want to get paid for all of the themes I create, I'm simply suggesting it would be better in the long run if we leave modularized theming options open, monetized or otherwise, and let the user pick and choose what they want to install. Installing themes does not require a paid consultant to install. A new theme can be installed on-the-fly using the xml data import feature in webtools in a few minutes, with very little knowledge or instruction. You do bring up an interesting idea though... Say for instance we have just 2 themes in the OOTB installation with a link under the selection list that said get more themes. Clicking that would bring up a list of themes in an external themes repo. We could then have a script that allows the user to grab the external themes XML seed data and download the themes assets to their installed instance. Might be a good idea for a future enhancement. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 11:17 AM, BJ Freeman wrote: Bruno says: Dependencies between themes do not allow modular selection, distribution and installation. You say they are modular. David has commented that he started this project with Idea that Trained consultants in ofbiz would be paid to install modify, and customize ofbiz. That model in my opinion does not work, as David has since said, with open source. Especially being in ASF. I have some modules that once the design time has be amortized I will release to open source. Till then they cost. However my main thrust with ofbiz is first make it widely accepted so by sheer numbers, there will those that want to hire consultants. So my focus is a good online embedded Doc and help, along with a flexible and powerful setup that will lead a end user through a complete setup. Part of that setup is a java based component that will go get ofbiz and download it then ask if they want demo or Production setup. I can see in that phase of the setup making the end user aware of themes in galleries they can then have installed. To that end I believe the current themes should be left in place and future themes that people want to get paid for be put on their own website where they can amortize their efforts. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/7/2011 8:52 AM: I understand BJ concerns, but again, I'm with Bruno on this. Themes are modular and preferential by nature. Not every user will want or have a need for every theme. For instance, if I develop a women's boutique front-end theme, it may be of great interest to an owner of a women's boutique but the owner of an auto parts store could probably care less. Why not leave 2-3 official release themes in the trunk that are up to date and maintained consistently by the community and move everything else to an external directory. Then, let the user/developer pick and choose what themes to install. In the end, we all decide whether we want to contribute the code we develop back to the code base or not. For existing themes, my vote is to keep the active themes in the trunk and move the deprecated/ unsupported / un-evolved themes out to the theme gallery. This means BizznessTime?(which unfortunately seems to be rapidly losing community backing), Bluelight, and DroppingCrumbs. For future themes that I develop, the choice is easy for me. I will simply not grant the theme ASF license to be included in the trunk. I will release the theme to the public and post the theme to the theme gallery or distribute through some other method. If we decide to create a new theme from Flat Grey, I am calling the new theme Dorian Gray (http://en.wikipedia.org/wiki/Dorian_Gray). The new theme will continue to look young, fresh and modern, while it's reflection, Flat Grey, will continue to look older and more dated with each passing year... ;) Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 5:06 AM, Bruno Busco wrote: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is -
Re: Discussion: Flat Grey Visual Theme
I a not saying that actual themes are dependent from each other. At least I am not aware of this dependency. I mean that, generally, a theme A is dependent from theme B than you cannot download theme A from the Theme Gallery and install it if you do not install theme B also. That simple. 2011/1/7 BJ Freeman bjf...@free-man.net to paraphrase what I think you said the current themes are not independent of each other so can not be removed, without causing failure in another The links you gave and the themes depository in wiki will not facilitate an end user on selecting or installing the themes from ofbiz like the current theme selection. again the rule is not to remove what is already put in Update and modify only. Now if all new themes are put in the themes gallery I see no problem with that. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 4:06 AM: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Rouxjacques.le.r...@les7arts.com From: BJ Freemanbjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freemanbjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Adrian Crum sent the following on 1/6/2011 3:23 PM: That can go both ways. If your deployments depends upon the visual themes being in the trunk,
Re: Discussion: Flat Grey Visual Theme
You do bring up an interesting idea though... Say for instance we have just 2 themes in the OOTB installation with a link under the selection list that said get more themes. Clicking that would bring up a list of themes in an external themes repo. We could then have a script that allows the user to grab the external themes XML seed data and download the themes assets to their installed instance. Might be a good idea for a future enhancement. That's nice indeed !!
Re: Discussion: Flat Grey Visual Theme
Please make that a configurable option, since in a SAS, muiltitenant environment that may not be advisable. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 11:54 AM: You do bring up an interesting idea though... Say for instance we have just 2 themes in the OOTB installation with a link under the selection list that said get more themes. Clicking that would bring up a list of themes in an external themes repo. We could then have a script that allows the user to grab the external themes XML seed data and download the themes assets to their installed instance. Might be a good idea for a future enhancement. That's nice indeed !!
Re: Discussion: Flat Grey Visual Theme
thanks for clarifying = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 11:52 AM: I a not saying that actual themes are dependent from each other. At least I am not aware of this dependency. I mean that, generally, a theme A is dependent from theme B than you cannot download theme A from the Theme Gallery and install it if you do not install theme B also. That simple. 2011/1/7 BJ Freemanbjf...@free-man.net to paraphrase what I think you said the current themes are not independent of each other so can not be removed, without causing failure in another The links you gave and the themes depository in wiki will not facilitate an end user on selecting or installing the themes from ofbiz like the current theme selection. again the rule is not to remove what is already put in Update and modify only. Now if all new themes are put in the themes gallery I see no problem with that. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 4:06 AM: Dependencies between themes do not allow modular selection, distribution and installation. Please give a look to these web sites: http://www.templatemonster.com/magento-themes.php http://wordpress.org/extend/themes/ http://drupal.org/project/Themes they are all examples of how to maintain themes database. In a production installation one can choose between: - using one of the OOTB themes as it is - use one of the themes from the theme gallery as it is - start from one of the OOTB or gallery themes to build a new customized one Moving a theme from OOTB to the theme gallery should not be an issue. It simply slightly changes the way how a production server is updated. -Bruno 2011/1/7 Jacques Le Rouxjacques.le.r...@les7arts.com From: BJ Freemanbjf...@free-man.net more the second. however I am reacting more to a pattern change. for instance ecommerce was downgraded from a main app to a specialpurpose. I was not removed. the architecture lets it be moved with out any code changes to custom components already developed against it. Yes, I completly understand your point... And I guess you are not alone in this situation... related to themes, and multitenacy, not every user is going to want the same theme so the themes folder will be filled with `100's eventually. the script I started, https://issues.apache.org/jira/browse/OFBIZ-3490 is getting fancier. I can see templates for functionality of themes instead of the themes themselves. the seup app reads the data templateThemeData.xml and modifies it on the fly to the way the customer wants it. This way we don't have a lot of inactive themes and all the possibilities are in the template data. this is a flexible change once the Setup structure is in place. see https://issues.apache.org/jira/browse/OFBIZ-635 comment - 05/May/09 02:14 PM As I planned initially, to be discussed... Jacques = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Jacques Le Roux sent the following on 1/6/2011 11:15 PM: OK, that was the reason I had some concerns. Let's discuss it seriously... I think there are 2 ways to create a new themes from an existing one (a brand new one is not a problem). Duplicate an OOTB existing one and peek an poke there (resourceValues in ThemeNameThemeData.xml are all refering to locations in this theme) pros: independent from changes in the original theme (no pb if the theme dissapears, is changed for any reasons, etc.) cons: independent from changes in the original theme (you can't benefit from bug fixes, improvements, enhancements, etc.) Create a new theme by keeping references to an OOTB existing (some resourceValues in ThemeNameThemeData.xml are still refering to locations in this original theme) As (almost) ever there are 2 faces to the coin, the pros and cons are reversed from above. Which one are you using BJ? I guess the second. Else you would not have any concerns Jacques From: BJ Freemanbjf...@free-man.net Adrian i am sure as a business man you understand if it ain't broke don't fix it. Now if you talking about new themes I can agree, but no one has proposed any or give an price. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52
Re: Discussion: Flat Grey Visual Theme
the route I am headed is to use Gimp's macro to allow users to create Themes = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/7/2011 11:44 AM: I don't want to misquote Bruno, but I believe what he was saying was if we create dependencies between themes, it does not allow modular selection, distribution, and installation. Not that those dependencies already exist, because they don't. I am not saying that I want to get paid for all of the themes I create, I'm simply suggesting it would be better in the long run if we leave modularized theming options open, monetized or otherwise, and let the user pick and choose what they want to install. Installing themes does not require a paid consultant to install. A new theme can be installed on-the-fly using the xml data import feature in webtools in a few minutes, with very little knowledge or instruction. You do bring up an interesting idea though... Say for instance we have just 2 themes in the OOTB installation with a link under the selection list that said get more themes. Clicking that would bring up a list of themes in an external themes repo. We could then have a script that allows the user to grab the external themes XML seed data and download the themes assets to their installed instance. Might be a good idea for a future enhancement. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 11:17 AM, BJ Freeman wrote: Bruno says: Dependencies between themes do not allow modular selection, distribution and installation. You say they are modular. David has commented that he started this project with Idea that Trained consultants in ofbiz would be paid to install modify, and customize ofbiz. That model in my opinion does not work, as David has since said, with open source. Especially being in ASF. I have some modules that once the design time has be amortized I will release to open source. Till then they cost. However my main thrust with ofbiz is first make it widely accepted so by sheer numbers, there will those that want to hire consultants. So my focus is a good online embedded Doc and help, along with a flexible and powerful setup that will lead a end user through a complete setup. Part of that setup is a java based component that will go get ofbiz and download it then ask if they want demo or Production setup. I can see in that phase of the setup making the end user aware of themes in galleries they can then have installed. To that end I believe the current themes should be left in place and future themes that people want to get paid for be put on their own website where they can amortize their efforts. = BJ Freeman Strategic Power Office with Supplier Automationhttp://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.comhttp://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Ryan Foster sent the following on 1/7/2011 8:52 AM: I understand BJ concerns, but again, I'm with Bruno on this. Themes are modular and preferential by nature. Not every user will want or have a need for every theme. For instance, if I develop a women's boutique front-end theme, it may be of great interest to an owner of a women's boutique but the owner of an auto parts store could probably care less. Why not leave 2-3 official release themes in the trunk that are up to date and maintained consistently by the community and move everything else to an external directory. Then, let the user/developer pick and choose what themes to install. In the end, we all decide whether we want to contribute the code we develop back to the code base or not. For existing themes, my vote is to keep the active themes in the trunk and move the deprecated/ unsupported / un-evolved themes out to the theme gallery. This means BizznessTime?(which unfortunately seems to be rapidly losing community backing), Bluelight, and DroppingCrumbs. For future themes that I develop, the choice is easy for me. I will simply not grant the theme ASF license to be included in the trunk. I will release the theme to the public and post the theme to the theme gallery or distribute through some other method. If we decide to create a new theme from Flat Grey, I am calling the new theme Dorian Gray (http://en.wikipedia.org/wiki/Dorian_Gray). The new theme will continue to look young, fresh and modern, while it's reflection, Flat Grey, will continue to look older and more dated with each passing year... ;) Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 7, 2011, at 5:06 AM, Bruno Busco wrote: Dependencies between themes do not allow modular selection, distribution and installation.
Re: Discussion: Flat Grey Visual Theme
Yes, it makes sense to have it configurable. 2011/1/7 BJ Freeman bjf...@free-man.net Please make that a configurable option, since in a SAS, muiltitenant environment that may not be advisable. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Bruno Busco sent the following on 1/7/2011 11:54 AM: You do bring up an interesting idea though... Say for instance we have just 2 themes in the OOTB installation with a link under the selection list that said get more themes. Clicking that would bring up a list of themes in an external themes repo. We could then have a script that allows the user to grab the external themes XML seed data and download the themes assets to their installed instance. Might be a good idea for a future enhancement. That's nice indeed !!
[jira] Closed: (OFBIZ-3964) Localisation of labels in javascript
[
https://issues.apache.org/jira/browse/OFBIZ-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-3964.
--
Resolution: Fixed
Fix Version/s: SVN trunk
Thanks Sascha,
Your slightly modified patches are in trunk at r1056497
I finally simply replaced some
showErrorAlert(${uiLabelMap.ErrorLoadingContent}, ...
by
showErrorAlert(${uiLabelMap.CommonErrorMessage2}, ...
Localisation of labels in javascript
Key: OFBIZ-3964
URL: https://issues.apache.org/jira/browse/OFBIZ-3964
Project: OFBiz
Issue Type: Sub-task
Affects Versions: jQuery
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
Fix For: SVN trunk, jQuery
Attachments: OFBIZ-3964_RemoveAllJsAlerts.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch,
OFBIZ-3964_uiLabelFromJsCode_POC.patch, OFBIZ-3964_uiLAbelUpdate.patch
The idea is to use [Adam's
advice|http://markmail.org/message/kai5lfvlnsz7xwki]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-4097) Removal of duplicates between pt and pt_BR labels in framework/common/config
[ https://issues.apache.org/jira/browse/OFBIZ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum reassigned OFBIZ-4097: -- Assignee: Adrian Crum Removal of duplicates between pt and pt_BR labels in framework/common/config Key: OFBIZ-4097 URL: https://issues.apache.org/jira/browse/OFBIZ-4097 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Environment: Revision 1056083 Reporter: Luís Alfredo Harriss Maranesi Assignee: Adrian Crum Priority: Trivial Fix For: SVN trunk Attachments: OFBIZ-4097_Common-duplicates-removal-pt-pt_BR.patch Removal of duplicates between pt and pt_BR labels in framework/common/config -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-4097) Removal of duplicates between pt and pt_BR labels in framework/common/config
[ https://issues.apache.org/jira/browse/OFBIZ-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum closed OFBIZ-4097. -- Resolution: Fixed Luis, Watch out for unintended file changes made by Label Manager. Your last two patches removed the CommonEmptyHeader label. Patch applied to trunk with manual change by me, rev 1056625. Thanks Luis! Removal of duplicates between pt and pt_BR labels in framework/common/config Key: OFBIZ-4097 URL: https://issues.apache.org/jira/browse/OFBIZ-4097 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Environment: Revision 1056083 Reporter: Luís Alfredo Harriss Maranesi Assignee: Adrian Crum Priority: Trivial Fix For: SVN trunk Attachments: OFBIZ-4097_Common-duplicates-removal-pt-pt_BR.patch Removal of duplicates between pt and pt_BR labels in framework/common/config -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
