[jira] Commented: (OFBIZ-4081) Form widget improvements
[ https://issues.apache.org/jira/browse/OFBIZ-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978241#action_12978241 ] Bruno Busco commented on OFBIZ-4081: Looking at other open source ERP systems I found that many of the improvement proposed here as sub-tasks are implemented in openCRX (http://demo.opencrx.org). I put here this reference because it could be usefull in our design. Form widget improvements Key: OFBIZ-4081 URL: https://issues.apache.org/jira/browse/OFBIZ-4081 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Bruno Busco Priority: Minor I have a list of ideas about improvements that could be done on the frame widget. I think that creating jiras for these could be a good starting point to discuss, and eventually design and implement them. This issue is an umbrella task for them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-4092) Update The Flat Grey Visual Theme
[ https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978243#action_12978243 ] Bruno Busco commented on OFBIZ-4092: I have an idea for the tab bar. We all agree that it does not show well when it comes to two or three rows. Well, we could only show the tabs that fit in one row and add a tab as last tab. When hovering on the tab the remaining tabs appear like a pull down menu allowing the user to select one of them. The actually selected tab should always be showed as the fist element on the left. What do you think? Could it be done with some jquery script? Update The Flat Grey Visual Theme - Key: OFBIZ-4092 URL: https://issues.apache.org/jira/browse/OFBIZ-4092 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Adrian Crum Assignee: Adrian Crum Priority: Minor Attachments: accounting800x600.png, catalog800x600.png, catalogManager.png, content800x600.png, contentManager.png, flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif, partyDetail.png, partyManager.png, screenshot.gif, timeSheet.png Update the Flat Grey visual theme. Design objectives: 1. Floating, flexible layout - screen can be resized. 2. Sight impaired accessible - users can change font size in their browser. 3. Supports RTL layout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
Sorry Hans,
I think we should discuss this change. It seems we lost many information. At
first glance:
Lookups buttons for category and product
By default in the quick access dropdown, -Product Jump- is replaced by
Product which means less
No distinction between catalog and categories
Only Id for tree nodes, no names
What were the reasons that push you to change? I can't see the plus!
Thanks
Jacques
Author: hansbak
Date: Thu Jan 6 08:36:23 2011
New Revision: 1055790
URL: http://svn.apache.org/viewvc?rev=1055790view=rev
Log:
In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on
categories similar to the new product option
Added:
ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy
ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl
Modified:
ofbiz/trunk/applications/product/config/ProductUiLabels.xml
ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml
ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml
ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml
ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml
ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml
Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff
==
--- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original)
+++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6
08:36:23 2011
@@ -7459,6 +7459,10 @@
property key=PageTitleFacilityGeoLocation
value xml:lang=enFacility Geo Location/value
/property
+property key=PageTitleFindCategory
+value xml:lang=enFind Category/value
+value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value
+/property
property key=PageTitleFindConfigItems
value xml:lang=deKonfigurationsposition suchen/value
value xml:lang=enFind Config Items/value
@@ -7479,7 +7483,7 @@
value xml:lang=itRicerca Stabilimento/value
value xml:lang=roCauta Compartimento/value
value xml:lang=ruÐоиÑк обÑекÑа/value
-value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹/value
+value
xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹à¸²/value
value xml:lang=zhæ¥æ¾åºæ/value
value xml:lang=zh_TWæ¥æ¾å ´æ/value
/property
Added:
ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy?rev=1055790view=auto
==
---
ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy
(added)
+++
ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy
Thu Jan 6 08:36:23 2011
@@ -0,0 +1,64 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+
+import org.ofbiz.base.util.*;
+import org.ofbiz.product.catalog.*;
+import org.ofbiz.product.category.*;
+import org.ofbiz.entity.GenericValue;
+import javolution.util.FastMap;
+import javolution.util.FastList;
+import org.ofbiz.base.util.UtilMisc;
+import org.ofbiz.base.util.UtilValidate;
+import org.ofbiz.entity.GenericValue;
+import org.ofbiz.entity.util.EntityUtil;
+import javax.servlet.http.HttpSession;
+
+prodCatalogList = FastList.newInstance();
+prodCatalogs = delegator.findByAnd(ProdCatalog);
+if (prodCatalogs.size() 0) {
+for (i = 0; i prodCatalogs.size(); i++) {
+
+prodCatalogMap = FastMap.newInstance();
+prodCatalog = prodCatalogs[i];
+prodCatalogId = prodCatalog.getString(prodCatalogId);
+prodCatalogMap.put(prodCatalogId, prodCatalogId);
+prodCatalogMap.put(catalogName,
prodCatalog.getString(catalogName));
+
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
Jacques, see inline On Thu, 2011-01-06 at 10:47 +0100, Jacques Le Roux wrote: Sorry Hans, I think we should discuss this change. It seems we lost many information. At first glance: We just added an option, existing screens were not changed only the catalog/category tree is now using jquery which is working much better. Lookups buttons for category and product By default in the quick access dropdown, -Product Jump- is replaced by Product which means less No distinction between catalog and categories if you think we need 2 trees displaying the same info...sure w can add a jquey version for itdoesn;t ever catalog entry have the word 'catalog' in it? Only Id for tree nodes, no names do not understand that. What were the reasons that push you to change? I can't see the plus! to be able to have a better catalog tree and search functions in categories.we have a customer with many categories with often duplicates which are difficult to spot without a findAlso they think the magento interface is much better as ours, so we went a bit in that direction. Thanks Jacques Author: hansbak Date: Thu Jan 6 08:36:23 2011 New Revision: 1055790 URL: http://svn.apache.org/viewvc?rev=1055790view=rev Log: In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on categories similar to the new product option Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff == --- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6 08:36:23 2011 @@ -7459,6 +7459,10 @@ property key=PageTitleFacilityGeoLocation value xml:lang=enFacility Geo Location/value /property +property key=PageTitleFindCategory +value xml:lang=enFind Category/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value +/property property key=PageTitleFindConfigItems value xml:lang=deKonfigurationsposition suchen/value value xml:lang=enFind Config Items/value @@ -7479,7 +7483,7 @@ value xml:lang=itRicerca Stabilimento/value value xml:lang=roCauta Compartimento/value value xml:lang=ruÐоиÑк обÑекÑа/value -value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹à¸²/value value xml:lang=zhæ¥æ¾åºæ/value value xml:lang=zh_TWæ¥æ¾å ´æ/value /property Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy?rev=1055790view=auto == --- ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy (added) +++ ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy Thu Jan 6 08:36:23 2011 @@ -0,0 +1,64 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * License); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +import org.ofbiz.base.util.*;
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
Hans, Inline, but what about the 2 points below? Lookups buttons for category and product have been removed? By default in the quick access dropdown, -Product Jump- is replaced by Product which means less. I mean, the 1st instanceof the dropdown was actually telling us its purpose, now it's less obvious, why have you changed it? From: Hans Bakker mailingl...@antwebsystems.com Jacques, see inline On Thu, 2011-01-06 at 10:47 +0100, Jacques Le Roux wrote: Sorry Hans, I think we should discuss this change. It seems we lost many information. At first glance: We just added an option, existing screens were not changed only the catalog/category tree is now using jquery which is working much better. Lookups buttons for category and product By default in the quick access dropdown, -Product Jump- is replaced by Product which means less No distinction between catalog and categories if you think we need 2 trees displaying the same info...sure w can add a jquey version for itdoesn;t ever catalog entry have the word 'catalog' in it? Yes I can agree on this point. But what if a catalog has no the catalog word in it, how the distinction can be made. I'd suggest to have different node icons for catalog and categories. And what about changing the title to Browse Catalogs/Categories? Only Id for tree nodes, no names do not understand that. Before you had the Id of the category and its name( like Gizmos [100]), now only the Id, ie 100 What were the reasons that push you to change? I can't see the plus! to be able to have a better catalog tree and search functions in categories.we have a customer with many categories with often duplicates which are difficult to spot without a findAlso they think the magento interface is much better as ours, so we went a bit in that direction. I see, with the minor changes it needs it should be ok... Jacques Thanks Jacques Author: hansbak Date: Thu Jan 6 08:36:23 2011 New Revision: 1055790 URL: http://svn.apache.org/viewvc?rev=1055790view=rev Log: In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on categories similar to the new product option Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff == --- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6 08:36:23 2011 @@ -7459,6 +7459,10 @@ property key=PageTitleFacilityGeoLocation value xml:lang=enFacility Geo Location/value /property +property key=PageTitleFindCategory +value xml:lang=enFind Category/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value +/property property key=PageTitleFindConfigItems value xml:lang=deKonfigurationsposition suchen/value value xml:lang=enFind Config Items/value @@ -7479,7 +7483,7 @@ value xml:lang=itRicerca Stabilimento/value value xml:lang=roCauta Compartimento/value value xml:lang=ruÐоиÑк обÑекÑа/value -value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹à¸²/value value xml:lang=zhæ¥æ¾åºæ/value value xml:lang=zh_TWæ¥æ¾å ´æ/value /property Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy?rev=1055790view=auto == --- ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy (added) +++ ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy Thu Jan 6 08:36:23 2011 @@ -0,0 +1,64 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
From: Hans Bakker mailingl...@antwebsystems.com On Thu, 2011-01-06 at 12:06 +0100, Jacques Le Roux wrote: Hans, Inline, but what about the 2 points below? Lookups buttons for category and product have been removed? can you tell me which url? i still see them on the main screen? I have just updated the trunk demo (no need to load data no to compile for r1055790 http://svn.apache.org/viewvc?rev=1055790view=rev ) and cleared the cache (labels). It's the same than locally there... https://demo-trunk.ofbiz.apache.org/catalog/control/login/main?USERNAME=adminPASSWORD=ofbiz By default in the quick access dropdown, -Product Jump- is replaced by Product which means less. I mean, the 1st instanceof the dropdown was actually telling us its purpose, now it's less obvious, why have you changed it? can you give a url o sceendump, i do not see it is changed? Right, only locally, not sure why... Jacques From: Hans Bakker mailingl...@antwebsystems.com Jacques, see inline On Thu, 2011-01-06 at 10:47 +0100, Jacques Le Roux wrote: Sorry Hans, I think we should discuss this change. It seems we lost many information. At first glance: We just added an option, existing screens were not changed only the catalog/category tree is now using jquery which is working much better. Lookups buttons for category and product By default in the quick access dropdown, -Product Jump- is replaced by Product which means less No distinction between catalog and categories if you think we need 2 trees displaying the same info...sure w can add a jquey version for itdoesn;t ever catalog entry have the word 'catalog' in it? Yes I can agree on this point. But what if a catalog has no the catalog word in it, how the distinction can be made. I'd suggest to have different node icons for catalog and categories. And what about changing the title to Browse Catalogs/Categories? Only Id for tree nodes, no names do not understand that. Before you had the Id of the category and its name( like Gizmos [100]), now only the Id, ie 100 What were the reasons that push you to change? I can't see the plus! to be able to have a better catalog tree and search functions in categories.we have a customer with many categories with often duplicates which are difficult to spot without a findAlso they think the magento interface is much better as ours, so we went a bit in that direction. I see, with the minor changes it needs it should be ok... Jacques Thanks Jacques Author: hansbak Date: Thu Jan 6 08:36:23 2011 New Revision: 1055790 URL: http://svn.apache.org/viewvc?rev=1055790view=rev Log: In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on categories similar to the new product option Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff == --- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6 08:36:23 2011 @@ -7459,6 +7459,10 @@ property key=PageTitleFacilityGeoLocation value xml:lang=enFacility Geo Location/value /property +property key=PageTitleFindCategory +value xml:lang=enFind Category/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value +/property property key=PageTitleFindConfigItems value xml:lang=deKonfigurationsposition suchen/value value xml:lang=enFind Config Items/value @@ -7479,7 +7483,7 @@ value xml:lang=itRicerca Stabilimento/value value xml:lang=roCauta Compartimento/value value xml:lang=ruÐоиÑк обÑекÑа/value -value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸à¸¥à¸±à¸à¸ªà¸´à¸à¸à¹à¸²/value value xml:lang=zhæ¥æ¾åºæ/value value xml:lang=zh_TWæ¥æ¾å ´æ/value /property Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy URL:
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
ok, i looked in he tomahawk theme, we will correct it in the blue-gray theme no problem to get upset? Regardsm' Hans On Thu, 2011-01-06 at 12:53 +0100, Jacques Le Roux wrote: From: Hans Bakker mailingl...@antwebsystems.com On Thu, 2011-01-06 at 12:06 +0100, Jacques Le Roux wrote: Hans, Inline, but what about the 2 points below? Lookups buttons for category and product have been removed? can you tell me which url? i still see them on the main screen? I have just updated the trunk demo (no need to load data no to compile for r1055790 http://svn.apache.org/viewvc?rev=1055790view=rev ) and cleared the cache (labels). It's the same than locally there... https://demo-trunk.ofbiz.apache.org/catalog/control/login/main?USERNAME=adminPASSWORD=ofbiz By default in the quick access dropdown, -Product Jump- is replaced by Product which means less. I mean, the 1st instanceof the dropdown was actually telling us its purpose, now it's less obvious, why have you changed it? can you give a url o sceendump, i do not see it is changed? Right, only locally, not sure why... Jacques From: Hans Bakker mailingl...@antwebsystems.com Jacques, see inline On Thu, 2011-01-06 at 10:47 +0100, Jacques Le Roux wrote: Sorry Hans, I think we should discuss this change. It seems we lost many information. At first glance: We just added an option, existing screens were not changed only the catalog/category tree is now using jquery which is working much better. Lookups buttons for category and product By default in the quick access dropdown, -Product Jump- is replaced by Product which means less No distinction between catalog and categories if you think we need 2 trees displaying the same info...sure w can add a jquey version for itdoesn;t ever catalog entry have the word 'catalog' in it? Yes I can agree on this point. But what if a catalog has no the catalog word in it, how the distinction can be made. I'd suggest to have different node icons for catalog and categories. And what about changing the title to Browse Catalogs/Categories? Only Id for tree nodes, no names do not understand that. Before you had the Id of the category and its name( like Gizmos [100]), now only the Id, ie 100 What were the reasons that push you to change? I can't see the plus! to be able to have a better catalog tree and search functions in categories.we have a customer with many categories with often duplicates which are difficult to spot without a findAlso they think the magento interface is much better as ours, so we went a bit in that direction. I see, with the minor changes it needs it should be ok... Jacques Thanks Jacques Author: hansbak Date: Thu Jan 6 08:36:23 2011 New Revision: 1055790 URL: http://svn.apache.org/viewvc?rev=1055790view=rev Log: In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on categories similar to the new product option Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff == --- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6 08:36:23 2011 @@ -7459,6 +7459,10 @@ property key=PageTitleFacilityGeoLocation value xml:lang=enFacility Geo Location/value /property +property key=PageTitleFindCategory +value xml:lang=enFind Category/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value +/property property key=PageTitleFindConfigItems value xml:lang=deKonfigurationsposition suchen/value value xml:lang=enFind Config Items/value @@ -7479,7 +7483,7 @@ value xml:lang=itRicerca Stabilimento/value value xml:lang=roCauta Compartimento/value
Re: svn commit: r1055790 - in /ofbiz/trunk/applications/product: config/ webapp/catalog/WEB-INF/ webapp/catalog/WEB-INF/actions/category/ webapp/catalog/category/ widget/catalog/
From: Hans Bakker mailingl...@antwebsystems.com ok, i looked in he tomahawk theme, we will correct it in the blue-gray theme no problem to get upset? Regardsm' Hans FYI: I saw the same with Tomahawk, did not look at others themes, could you please check? Thanks Jacques On Thu, 2011-01-06 at 12:53 +0100, Jacques Le Roux wrote: From: Hans Bakker mailingl...@antwebsystems.com On Thu, 2011-01-06 at 12:06 +0100, Jacques Le Roux wrote: Hans, Inline, but what about the 2 points below? Lookups buttons for category and product have been removed? can you tell me which url? i still see them on the main screen? I have just updated the trunk demo (no need to load data no to compile for r1055790 http://svn.apache.org/viewvc?rev=1055790view=rev ) and cleared the cache (labels). It's the same than locally there... https://demo-trunk.ofbiz.apache.org/catalog/control/login/main?USERNAME=adminPASSWORD=ofbiz By default in the quick access dropdown, -Product Jump- is replaced by Product which means less. I mean, the 1st instanceof the dropdown was actually telling us its purpose, now it's less obvious, why have you changed it? can you give a url o sceendump, i do not see it is changed? Right, only locally, not sure why... Jacques From: Hans Bakker mailingl...@antwebsystems.com Jacques, see inline On Thu, 2011-01-06 at 10:47 +0100, Jacques Le Roux wrote: Sorry Hans, I think we should discuss this change. It seems we lost many information. At first glance: We just added an option, existing screens were not changed only the catalog/category tree is now using jquery which is working much better. Lookups buttons for category and product By default in the quick access dropdown, -Product Jump- is replaced by Product which means less No distinction between catalog and categories if you think we need 2 trees displaying the same info...sure w can add a jquey version for itdoesn;t ever catalog entry have the word 'catalog' in it? Yes I can agree on this point. But what if a catalog has no the catalog word in it, how the distinction can be made. I'd suggest to have different node icons for catalog and categories. And what about changing the title to Browse Catalogs/Categories? Only Id for tree nodes, no names do not understand that. Before you had the Id of the category and its name( like Gizmos [100]), now only the Id, ie 100 What were the reasons that push you to change? I can't see the plus! to be able to have a better catalog tree and search functions in categories.we have a customer with many categories with often duplicates which are difficult to spot without a findAlso they think the magento interface is much better as ours, so we went a bit in that direction. I see, with the minor changes it needs it should be ok... Jacques Thanks Jacques Author: hansbak Date: Thu Jan 6 08:36:23 2011 New Revision: 1055790 URL: http://svn.apache.org/viewvc?rev=1055790view=rev Log: In the catalog manager, replace the category and catalog tree by a single jquery tree, add a category option to list and search on categories similar to the new product option Added: ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/actions/category/CategoryTree.groovy ofbiz/trunk/applications/product/webapp/catalog/category/CategoryTree.ftl Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml ofbiz/trunk/applications/product/webapp/catalog/WEB-INF/controller.xml ofbiz/trunk/applications/product/widget/catalog/CatalogMenus.xml ofbiz/trunk/applications/product/widget/catalog/CategoryForms.xml ofbiz/trunk/applications/product/widget/catalog/CategoryScreens.xml ofbiz/trunk/applications/product/widget/catalog/CommonScreens.xml Modified: ofbiz/trunk/applications/product/config/ProductUiLabels.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/product/config/ProductUiLabels.xml?rev=1055790r1=1055789r2=1055790view=diff == --- ofbiz/trunk/applications/product/config/ProductUiLabels.xml (original) +++ ofbiz/trunk/applications/product/config/ProductUiLabels.xml Thu Jan 6 08:36:23 2011 @@ -7459,6 +7459,10 @@ property key=PageTitleFacilityGeoLocation value xml:lang=enFacility Geo Location/value /property +property key=PageTitleFindCategory +value xml:lang=enFind Category/value +value xml:lang=thà¸à¹à¸à¸«à¸²à¸«à¸¡à¸§à¸à¸«à¸¡à¸¹à¹/value +/property property key=PageTitleFindConfigItems value xml:lang=deKonfigurationsposition suchen/value value xml:lang=enFind Config Items/value @@ -7479,7 +7483,7 @@ value xml:lang=itRicerca Stabilimento/value value xml:lang=roCauta Compartimento/value
Re: Discussion: Flat Grey Visual Theme
Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun, 1/2/11, Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com wrote: From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com Subject: Re: Discussion: Flat Grey Visual Theme To: dev@ofbiz.apache.org, Jacques Le Roux jacques.le.r...@les7arts.com Date: Sunday, January 2, 2011, 2:27 AM I really would appreciate to keep the Flat Gray. But you're right it needs a few visual improvements. Let me think about this, maybe somethink comes to my mind . :-) Cheers 2010/12/29 Jacques Le Roux jacques.le.r...@les7arts.com IIRW, it's the only really RTL capable. So a big YES to keep it, of course. I have no ideas though :/ Jacques From: Adrian Crum adrian.c...@yahoo.com The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the Spring of 2007 I added some gradient gifs to make the original style a little more interesting. After that, the visual theme was converted to a floating flexible layout (to fit any size screen), it was made sight-impaired accessible (font size can be changed), and it added support for bi-directional layout (for rtl languages). Those design decisions were made by the OFBiz community and, in my opinion, continue to make the Flat Grey theme the fallback theme when all else fails. It just works. Despite its advantages, it looks dated. I would like to update it to make it more modern, but maintain its advantages over the other themes. I'm thinking it only needs css and gif file updates. The current templates and javascripts would be maintained. If anyone is interested, they are welcome to help out. I would also appreciate any suggestions or comments. Let me know what you think. -Adrian -- Sascha Rodekamp Lynx-Consulting GmbH Johanniskirchplatz 6 D-33615 Bielefeld http://www.lynx.de
Re: Discussion: Flat Grey Visual Theme
From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun, 1/2/11, Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com wrote: From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com Subject: Re: Discussion: Flat Grey Visual Theme To: dev@ofbiz.apache.org, Jacques Le Roux jacques.le.r...@les7arts.com Date: Sunday, January 2, 2011, 2:27 AM I really would appreciate to keep the Flat Gray. But you're right it needs a few visual improvements. Let me think about this, maybe somethink comes to my mind . :-) Cheers 2010/12/29 Jacques Le Roux jacques.le.r...@les7arts.com IIRW, it's the only really RTL capable. So a big YES to keep it, of course. I have no ideas though :/ Jacques From: Adrian Crum adrian.c...@yahoo.com The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the Spring of 2007 I added some gradient gifs to make the original style a little more interesting. After that, the visual theme was converted to a floating flexible layout (to fit any size screen), it was made sight-impaired accessible (font size can be changed), and it added support for bi-directional layout (for rtl languages). Those design decisions were made by the OFBiz community and, in my opinion, continue to make the Flat Grey theme the fallback theme when all else fails. It just works. Despite its advantages, it looks dated. I would like to update it to make it more modern, but maintain its advantages over the other themes. I'm thinking it only needs css and gif file updates. The current templates and javascripts would be maintained. If anyone is interested, they are welcome to help out. I would also appreciate any
Re: Discussion: Flat Grey Visual Theme
Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun, 1/2/11, Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com wrote: From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com Subject: Re: Discussion: Flat Grey Visual Theme To: dev@ofbiz.apache.org, Jacques Le Roux jacques.le.r...@les7arts.com Date: Sunday, January 2, 2011, 2:27 AM I really
Re: Discussion: Flat Grey Visual Theme
Yes, but why not create an evolution and keep the old one? Is it so bad that Ryan and you want to remove it? I like plurality, and especially I'm sure it will be easier for some of our users to have it at hand... Any other opinions? Jacques From: Adrian Crum adri...@hlmksw.com From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun, 1/2/11, Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com wrote: From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com Subject: Re: Discussion: Flat Grey Visual Theme To: dev@ofbiz.apache.org, Jacques Le Roux jacques.le.r...@les7arts.com Date: Sunday, January 2, 2011, 2:27 AM I really would appreciate to keep the Flat Gray. But you're right it needs a few visual improvements. Let me think about this, maybe somethink comes to my mind . :-) Cheers 2010/12/29 Jacques Le Roux jacques.le.r...@les7arts.com IIRW, it's the only really RTL capable. So a big YES to keep it, of course. I have no ideas though :/ Jacques From: Adrian Crum adrian.c...@yahoo.com The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the Spring of 2007 I added some gradient gifs to make the original style a little more interesting. After that, the visual theme was converted to a floating flexible layout (to fit any size screen), it was made sight-impaired accessible (font size can be changed), and it added support for bi-directional layout (for rtl languages). Those design decisions were made by the OFBiz community and, in my opinion, continue to make the Flat Grey theme the fallback theme when all else fails. It just works. Despite its advantages, it looks dated. I would like to
Re: Discussion: Flat Grey Visual Theme
Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun,
Re: Discussion: Flat Grey Visual Theme
inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I
DockBook anchors
been adding anchors in the docbooks anchor xml:id=CreateMaintainProductFeatures/ the lets us use #CreateMaintainProductFeatures in URLS. so this will allow using these in the mailing list. would like to use it as the way to sync to the help for instance the features has many section that are individual help but it is one file about features. have not looked into what it takes yet. = 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
I'm all for plurality as well. In fact, I have at least 10 more front-end and backend themes that I am working on or planning. I'm just not sure I want to maintain 10 more themes in the trunk. What if Bruno, Ean or anyone else creates more themes as well? Do we really want to constantly maintain 10, 20, 30 different themes?... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:29 AM, Jacques Le Roux wrote: Yes, but why not create an evolution and keep the old one? Is it so bad that Ryan and you want to remove it? I like plurality, and especially I'm sure it will be easier for some of our users to have it at hand... Any other opinions? Jacques From: Adrian Crum adri...@hlmksw.com From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas outside of this mailing list discussion. Consequently, as far as new admin themes go, I guess I can use this as an opportunity as well to drop a teaser about a new theme I have been working on already for some time now that I honestly hope will become the go-to theme for scalability and customization, and that will eventually replace the Flat Grey theme altogether. The new theme scales down very well to 800x600 and has minimal styling for maximum flexibility and customization. Stay tuned for more details in the next few days... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 3, 2011, at 11:04 AM, Adrian Crum wrote: Chiclet refers to a brand of chewing gum. The tabs look like pieces of Chiclets chewing gum. They look terrible when they are displayed in two rows. -Adrian --- On Mon, 1/3/11, Jacques Le Roux jacques.le.r...@les7arts.com wrote: By chiclet main navigation style, you mean the tabs? Then I think we should keep Flat Grey as it is (because there are advantages to have tabs) and create a Flat Grey evolution... Jacques From: Adrian Crum adrian.c...@yahoo.com I was thinking we could use colors from the Apache logo and the BizznessTime theme. I would also like to get rid of the chiclet main navigation style, and maybe have that menu in a collapsible left column. -Adrian --- On Sun, 1/2/11, Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com wrote: From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com Subject: Re: Discussion: Flat Grey Visual Theme To: dev@ofbiz.apache.org, Jacques Le Roux jacques.le.r...@les7arts.com Date: Sunday, January 2, 2011, 2:27 AM I really would appreciate to keep the Flat Gray. But you're right it needs a few visual improvements. Let me think about this, maybe somethink comes to my mind . :-) Cheers 2010/12/29 Jacques Le Roux jacques.le.r...@les7arts.com IIRW, it's the only really RTL capable. So a big YES to keep it, of course. I have no ideas though :/ Jacques From: Adrian Crum adrian.c...@yahoo.com The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the
[jira] Created: (OFBIZ-4095) Catalog Help docbook files
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 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
On 1/6/2011 11:11 AM, Ryan Foster wrote: I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This was discussed when we first added visual theme capability. There is nothing blocking third-party visual themes being offered on other sites. It was suggested that OFBiz have only one theme, but the decision was made to have more than one so that visual theme selection could be demonstrated. -Adrian
[jira] Commented: (OFBIZ-2361) Category URL conflicts with product URL
[ https://issues.apache.org/jira/browse/OFBIZ-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978472#action_12978472 ] Wickersheimer Jeremy commented on OFBIZ-2361: - Just noticed the same problem, it is confusing and it will probably hit a lot of people since the default IDs (when creating categories and products from the catalog) are sure to conflict. As a result the category navigation menu (left column) in ecommerce is broken. Perhaps a quick fix is for the `CatalogUrlServlet` to only consider products when using the p_ prefix syntax ? Anyway there seems to be no way to be ''smart'' since /ecommerce/products/1/10001 could be either sub category 10001 in category 1 or product 10001 in category 1. Category URL conflicts with product URL --- Key: OFBIZ-2361 URL: https://issues.apache.org/jira/browse/OFBIZ-2361 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: red hat, postgres Reporter: Rohit Sureka Hi, I just found out a potential bug in the new URL structure for category links in the ecommerce page. The new URL's for a category link reads as http://demo.ofbiz.org/ecommerce/products/100/100 here 100 is the category ID, this URL should ideally list all products in the category with ID 100. However if we create a product with ID 100 ie. product_id=100, there arise the bug. Instead of all item being shown in the category, the product page for product_id 100 is displayed, irrespective of the category/catalog/store that product ID belongs to. I think this is a unusual behavior, and may cause problems for people wanting to move on to newer code. Please let me know if should open a jira issue for it. Rohit -- 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
Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the better, I like to have the choice. Some (rare) people prefer to use old things, see games machines or synthesizers for instance (I still love the DX-7 sound http://en.wikipedia.org/wiki/Yamaha_DX7 http://www.vintagesynth.com/yamaha/dx7.php) There are any evolved version of Flat Grey yet. So this could be the 1st modern one still using the RTL mechanism introduced by Adrian. Just choice the name! Thanks Jacques Ryan Foster wrote: IMO I see no reason to have a Flat Grey Evolution theme. Adrian is right, the Flat Grey theme hasn't had a visual update in years and it looks very dated. It needs some love. Let's not add another improved version, let's just improve the version we have now. I think that is more efficient and more beneficial in the long run. As far as the tabs go, we can still keep a horizontal, tab-like navigation without actually having the tabs look like tabs. Because, the absolutely do look terrible displayed in two rows. Adrian, I would be happy to collaborate with you on this. I think I have some ideas that could help. Email me directly if you want to hash out some ideas
Re: Discussion: Flat Grey Visual Theme
Adrian Crum wrote: On 1/6/2011 11:11 AM, Ryan Foster wrote: I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This was discussed when we first added visual theme capability. There is nothing blocking third-party visual themes being offered on other sites. It was suggested that OFBiz have only one theme, but the decision was made to have more than one so that visual theme selection could be demonstrated. -Adrian I guess Ryan would hope to have a mechanism to handle it graciously Jacques
[jira] Created: (OFBIZ-4096) Error in order email confirmation template
Error in order email confirmation template
--
Key: OFBIZ-4096
URL: https://issues.apache.org/jira/browse/OFBIZ-4096
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/ecommerce
Affects Versions: Release Branch 10.04, SVN trunk
Reporter: Wickersheimer Jeremy
Fix For: Release Branch 10.04, SVN trunk
In :
{code:title=specialpurpose/ecommerce/webapp/ecommerce/order/orderheader.ftl:123|borderStyle=solid}
#assign pmBillingAddress = creditCard.getRelatedOne(PostalAddress)
{code}
is missing the ?if_exists causing errors in some cases.
--
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, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Roux jacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we have the
Re: Discussion: Flat Grey Visual Theme
From: Bruno Busco bruno.bu...@gmail.com Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno Sounds like a plan! Jacques 2011/1/6 Jacques Le Roux jacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any risks with it? Also I can't see any issues with having more themes. The more we
Re: Discussion: Flat Grey Visual Theme
+1. I think that is a good start. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 1:53 PM, Jacques Le Roux wrote: From: Bruno Busco bruno.bu...@gmail.com Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno Sounds like a plan! Jacques 2011/1/6 Jacques Le Roux jacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance
Re: Discussion: Flat Grey Visual Theme
is there any thought to production servers. or is this just a developers paradise = 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/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe
Re: Discussion: Flat Grey Visual Theme
how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If I'm not available, someone else could fix it, etc. -Adrian On 1/6/2011 6:02 AM, Jacques Le Roux wrote: Ryan, Your screen copies at https://issues.apache.org/jira/browse/OFBIZ-4092 looks really great! Looking forward for the implementation... My concerns are that maybe you will not have enough time later to keep up with possible bugs or other issues. Look for instance what happened to Bizzness Time https://issues.apache.org/jira/browse/OFBIZ-2398. Even if it looks a bit old, we have a theme which works great. Why taking any
[jira] Closed: (OFBIZ-4096) Error in order email confirmation template
[
https://issues.apache.org/jira/browse/OFBIZ-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-4096.
--
Resolution: Fixed
Assignee: Jacques Le Roux
Thanks Jeremy,
Your suggested change is in trunk at r1056072, R10.04 at r1056077.
I fixed the same at line 164
Error in order email confirmation template
--
Key: OFBIZ-4096
URL: https://issues.apache.org/jira/browse/OFBIZ-4096
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/ecommerce
Affects Versions: Release Branch 10.04, SVN trunk
Reporter: Wickersheimer Jeremy
Assignee: Jacques Le Roux
Fix For: Release Branch 10.04, SVN trunk
In :
{code:title=specialpurpose/ecommerce/webapp/ecommerce/order/orderheader.ftl:123|borderStyle=solid}
#assign pmBillingAddress = creditCard.getRelatedOne(PostalAddress)
{code}
is missing the ?if_exists causing errors in some cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
buildbot failure in ASF Buildbot on ofbiz-trunk
The Buildbot has detected a new failure of ofbiz-trunk on ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-trunk/builds/1007 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: Build Source Stamp: [branch ofbiz/trunk] 1056092 Blamelist: mrisaliti BUILD FAILED: failed compile sincerely, -The Buildbot
Re: Discussion: Flat Grey Visual Theme
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 Freeman bjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't necessarily afford custom development. This makes good sense indeed. The only difference, I guess, is unfortunately the width of the audience. This does not mean that we should not try... Jacques Jacques Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 8:17 AM, Adrian Crum wrote: From my perspective, I don't see much chance in the Flat Grey visual theme being abandoned. Enough people use it that it will get the attention it needs. If Ryan isn't available to fix something, I can fix it. If
[jira] Created: (OFBIZ-4097) Removal of duplicates between pt and pt_BR labels in framework/common/config
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 Priority: Trivial Fix For: SVN trunk 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] Updated: (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 ] Luís Alfredo Harriss Maranesi updated OFBIZ-4097: - Attachment: OFBIZ-4097_Common-duplicates-removal-pt-pt_BR.patch Removal of duplicates between pt and pt_BR labels in framework/common/config 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 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.
buildbot success in ASF Buildbot on ofbiz-trunk
The Buildbot has detected a restored build of ofbiz-trunk on ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-trunk/builds/1008 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: Build Source Stamp: [branch ofbiz/trunk] 1056098 Blamelist: mrisaliti Build succeeded! sincerely, -The Buildbot
Re: Discussion: Flat Grey Visual Theme
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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and companies in the Wordpress community that make their living solely by selling themes and plugins. This furthers solidifies the base of support for the project by offering a mid-tier option for someone who wants something more than OOTB but can't
Re: Discussion: Flat Grey Visual Theme
The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freeman bjf...@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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this way fosters wider community support by delegating maintenance of these themes to individual contributors rather than forcing it on a handful of committers and also allows developers to monetize there contributions by offering premium themes and plugins. In fact, there are many individuals and
Re: Discussion: Flat Grey Visual Theme
Agreed. I don't know anyone that updates a production server directly from a development trunk, especially not a community driven open-source development trunk. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:33 PM, Bruno Busco wrote: The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freeman bjf...@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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress install. Doing it this
Re: Discussion: Flat Grey Visual Theme
As I said before, there are so many themes in the trunk right now just to avoid troubles to users. But we have seen that this is not a good way to manage themes in the long time. We need to break this chain now or we will have too many themes in the trunk. -Bruno 2011/1/6 Bruno Busco bruno.bu...@gmail.com The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freeman bjf...@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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one official theme that is included with the install, but there are literally thousands of themes that are not maintained by Wordpress that they list on there site http://wordpress.org/extend/themes/, and now with the 3.0 release you can even search for new themes and install them automatically from inside your Wordpress
Re: Discussion: Flat Grey Visual Theme
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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is one
Re: Discussion: Flat Grey Visual Theme
Sorry, my last response sounded a bit arrogant after I re-read it. My apologies to anyone who might actually be doing this. I just personally feel like that is not a good idea. Way too many unknown variables on a day to day basis. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:37 PM, Ryan Foster wrote: Agreed. I don't know anyone that updates a production server directly from a development trunk, especially not a community driven open-source development trunk. Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 3:33 PM, Bruno Busco wrote: The theme will still be present in the 10.04 releases. No production servers should rely on trunk. -Bruno 2011/1/6 BJ Freeman bjf...@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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe it would be a good idea to have a theme repo outside of the trunk that individuals could commit to? The problem with theme maintenance once a new theme has been added to the trunk is that not everyone has commit privileges to the trunk. This makes the process of maintenance a lot more time consuming for individual contributors as they have to rely on patches, updates, collaboration, etc, rather than just monitoring and maintaining their own code. This could certainly be discussed as themes are no blocking parts as long as *at least one works perfectly* (another way is to become committer), opinions? I think the way that Magento and Wordpress do it are good examples. With Wordpress, there is
Re: Discussion: Flat Grey Visual Theme
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.com http://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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any rate, my time issues and focus have shifted significantly over the last few months as I have left HotWax and gone into independent consulting and freelance development. I plan on taking a much more active role in the community in the months and years ahead. That's really a good, very good news! As far as theme contributions go, I wonder if maybe
Re: Discussion: Flat Grey Visual Theme
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. 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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that Ryan. It's only because I know you were one of the fathers (the most important I guess) and helped much at the beginning, my apologies. At any
Re: Discussion: Flat Grey Visual Theme
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. 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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM, Jacques Le Roux wrote: Ryan Foster wrote: Jacques, I understand your concerns about support, and your thoughts on the themes has some valid points. However, in regards to the BizznessTime theme, I never really intended for that to be my theme anyway. I always viewed it as a community theme as that was it's original intent and it was truly a collaborative effort to build it between myself, my colleagues at HotWax, BrainFood, and other members of the the OFBiz community. Right, sorry for that
Re: Discussion: Flat Grey Visual Theme
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. 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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution of the other. Each time we decided to create a new theme instead of replacing the one existing just to avoid problems to users. My proposal is to remove Bluelight, Dropping Crumbs and BizznessTime from the trunk and put them in a separate themes repository as suggested by Ryan. Remove the actual version of the Flat Grey from the trunk and put it in the themes repository. Improve the Flat Grey theme in the trunk with the work you guys are doing. In this way we will have in the trunk two themes for the backend (Actual FlatGrey and Tomahawk) and two themes for the ecommerce (Default and Multiflex). In the themes repository there will be Bluelight, Dropping Crumbs, BizznessTime and the actual FlatGrey. It could be a nice start for the theme repository (and gallery) start. -Bruno 2011/1/6 Jacques Le Rouxjacques.le.r...@les7arts.com Ryan Foster wrote: inline... Ryan L. Foster 801.671.0769 cont...@ryanlfoster.com On Jan 6, 2011, at 11:38 AM,
[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=12978579#action_12978579 ] Paul Foxworthy commented on OFBIZ-4090: --- Is it easy for you to post a screenshot showing the problem? I don't use Eclipse, so I can't see what you're seeing. 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
I think we should work on some animations and gif files. It should be added in the existing theme. Because it will improve look and feel of the theme. Also we should update our themes regularly so that we can compete with other framework applications. I know it would not be easy but by using animations we can express our ideas in effective manner. Thanks Regards, Ajay Lashkari On Wed, Dec 29, 2010 at 11:58 AM, Adrian Crum adrian.c...@yahoo.com wrote: The Flat Grey visual theme is getting old. The current version of the theme is based on the original look and feel of OFBiz when I first joined the community - back in 2004. Around the Spring of 2007 I added some gradient gifs to make the original style a little more interesting. After that, the visual theme was converted to a floating flexible layout (to fit any size screen), it was made sight-impaired accessible (font size can be changed), and it added support for bi-directional layout (for rtl languages). Those design decisions were made by the OFBiz community and, in my opinion, continue to make the Flat Grey theme the fallback theme when all else fails. It just works. Despite its advantages, it looks dated. I would like to update it to make it more modern, but maintain its advantages over the other themes. I'm thinking it only needs css and gif file updates. The current templates and javascripts would be maintained. If anyone is interested, they are welcome to help out. I would also appreciate any suggestions or comments. Let me know what you think. -Adrian
[jira] Updated: (OFBIZ-4095) Catalog Help docbook files
[ https://issues.apache.org/jira/browse/OFBIZ-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BJ Freeman updated OFBIZ-4095: -- Attachment: OFBIZ-4095porduct1.patch first installment of help files for full documents. 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.
[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=12978628#action_12978628 ] BJ Freeman commented on OFBIZ-4095: --- you can view http://demo-trunk.businessesnetwork.com/cmssite/cms/APACHE_OFBIZ_HTML#ProductCatalogComponent 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
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. 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 Freemanbjf...@free-man.net how about those that are using ofbiz for SAS and will have many themes for their clients. Bruno Busco sent the following on 1/6/2011 12:51 PM: Yes, having more than one theme in the trunk was originally accepted in order to use and show the visual theme selection feature OOTB. Actually Bluelight, Dropping Crumbs and Tomahawk are one the evolution
[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=12978663#action_12978663 ] Jacques Le Roux commented on OFBIZ-4095: Thanks BJ, Your patch is in trunk at r1056212 Fill free to close if you have no more patches for this issue 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.
