from:"Ryan Foster"


[ 
https://issues.apache.org/jira/browse/OFBIZ-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983816#action_12983816
 ] 

Ryan Foster commented on OFBIZ-4127:


Erwan, not sure what you are talking about here.  The buttons in the button-bar 
look exactly the way that they are supposed to look, which is illustrated by 
your screenshot.  They are styled to look like buttons, because that is what 
they are.  Their style definition is located on line 1394 in maincss.css

Close this task, there is no issue here.

 Styles for the button-bar buttons are not created
 -

 Key: OFBIZ-4127
 URL: https://issues.apache.org/jira/browse/OFBIZ-4127
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Priority: Minor
 Fix For: SVN trunk

 Attachments: fg_button-bar.png


 The buttons in button-bar have no style definition. You can see it through 
 the screenshot, or going to the layout demo page (nice idea, BTW!).
 Cheers,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-4127) Styles for the button-bar buttons are not created


[ 
https://issues.apache.org/jira/browse/OFBIZ-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983832#action_12983832
 ] 

Ryan Foster commented on OFBIZ-4127:


Yes, and my point was that they shouldn't use different CSS classes.  If we 
call it a button, and it acts like a button, then it should look like all of 
the other buttons.  It's not a style regression, it's a style consolidation.

Also, where is the Layout Demo page by the way?

 Styles for the button-bar buttons are not created
 -

 Key: OFBIZ-4127
 URL: https://issues.apache.org/jira/browse/OFBIZ-4127
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Priority: Minor
 Fix For: SVN trunk

 Attachments: fg_button-bar.png


 The buttons in button-bar have no style definition. You can see it through 
 the screenshot, or going to the layout demo page (nice idea, BTW!).
 Cheers,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-4127) Styles for the button-bar buttons are not created


[ 
https://issues.apache.org/jira/browse/OFBIZ-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983881#action_12983881
 ] 

Ryan Foster commented on OFBIZ-4127:


Then style the 2 different button-bar elements that contain them, not the 
buttons themselves, to show the relationship.  Buttons in row 1 have X in 
common and buttons in row 2 have Y in common, but one thing that they all share 
Z in common is that they are all BUTTONS.  The UI suffers much, much more when 
you have a group of common elements that all act the same way, but look 
different.  A user has a much more consistent and intuitive experience when 
they know that a button is a button, regardless of its relationship with other 
buttons.

 Styles for the button-bar buttons are not created
 -

 Key: OFBIZ-4127
 URL: https://issues.apache.org/jira/browse/OFBIZ-4127
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Priority: Minor
 Fix For: SVN trunk

 Attachments: fg_button-bar.png


 The buttons in button-bar have no style definition. You can see it through 
 the screenshot, or going to the layout demo page (nice idea, BTW!).
 Cheers,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-4127) Styles for the button-bar buttons are not created


[ 
https://issues.apache.org/jira/browse/OFBIZ-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983966#action_12983966
 ] 

Ryan Foster commented on OFBIZ-4127:


Sounds good.  I'll see if I can something together over the next couple of 
days.  I did notice that the disabled button styling was not getting picked 
in the Layout Test.  The attached patch fixes that issue.

 Styles for the button-bar buttons are not created
 -

 Key: OFBIZ-4127
 URL: https://issues.apache.org/jira/browse/OFBIZ-4127
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Priority: Minor
 Fix For: SVN trunk

 Attachments: fg_button-bar.png


 The buttons in button-bar have no style definition. You can see it through 
 the screenshot, or going to the layout demo page (nice idea, BTW!).
 Cheers,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-4127) Styles for the button-bar buttons are not created


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4127:
---

Attachment: disabledBtn.patch

adds disabled styling to a type button elements

 Styles for the button-bar buttons are not created
 -

 Key: OFBIZ-4127
 URL: https://issues.apache.org/jira/browse/OFBIZ-4127
 Project: OFBiz
  Issue Type: Bug
  Components: themes
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Priority: Minor
 Fix For: SVN trunk

 Attachments: disabledBtn.patch, fg_button-bar.png


 The buttons in button-bar have no style definition. You can see it through 
 the screenshot, or going to the layout demo page (nice idea, BTW!).
 Cheers,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: New Flat Grey default?

2011-01-18 Thread Ryan Foster

No misunderstanding, thanks for the compliment.  I tend to agree with you Tim.  
As much as my natural human tendency would be to toot my own horn and show 
off the new theme, I don't really see a need to change the default them every 
time something new comes along, which has kind of been the trend lately.  
Changing the default locally is quick and easy, and on the demo site, what 
theme is selected depends on who was using the trunk demo last so that changes 
all the time anyway.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com
ryanlfoster.com

On Jan 18, 2011, at 10:35 AM, Tim Ruppert wrote:

 Just so I'm not misunderstood here - the new Flat Grey does look extremely 
 awesome - great work everyone!
 
 Cheers,
 Ruppert
 
 On Jan 18, 2011, at 10:06 AM, Tim Ruppert wrote:
 
 -1 - the Tomahawk theme has been awesome - no real to mess with it IMO. 
 
 Cheers,
 Ruppert
 
 On Jan 18, 2011, at 3:39 AM, Jacques Le Roux wrote:
 
 Hi,
 
 As it's the sole theme handling RTL languages, I think we should make the 
 New Flat Grey as default. It will also help to find issues (if any ;o)
 
 Jacques

Re: Updated Flat Grey Visual Theme (was: [jira] Commented: (OFBIZ-4120) Umbrella task for features which use javascript to degrade gracefully)

2011-01-17 Thread Ryan Foster

That was exactly what I was trying to do.  It seemed even more weird to me to 
have theme selection and language in the header, but have timezone selection in 
the footer and to have half of the application links in the header and the 
other half in the footer.  The new grouping is much more logical in my opinion. 
 All of the applications are now grouped together in the header, and all of the 
user preference selections, which are secondary, are grouped together in the 
footer.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com
ryanlfoster.com

On Jan 17, 2011, at 7:30 AM, Adrian Crum wrote:

 Ryan can answer that question. I believe he was trying to keep the masthead 
 small so there is more room for the main content.
 
 -Adrian
 
 --- On Mon, 1/17/11, Jacques Le Roux (JIRA) j...@apache.org wrote:
 Also I asked
 {quote}
 BTW I was surprised that Ryan and you put the access to
 preferences and languages features in the footer. It's not
 always visible and seems a bit weird to me 
 {quote}
 
 Any answers? ;)

[jira] Commented: (OFBIZ-4092) Update The Flat Grey Visual Theme

2011-01-17 Thread Ryan Foster (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982762#action_12982762
]

Ryan Foster commented on OFBIZ-4092:

The _MACOSX folder is a hidden system folder for Apple. Not necessary. Feel
free to blow that away. My original intent was actually to create a generic
login screen style, similar to the way the BizznessTime theme, but that task
got lost in the shuffle. I'll see if I can get you a new patch that addresses
that within the next couple of days.

All in all, I think everything looks great. I look forward to community
feedback.

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: ac_flatgrey.patch, ac_flatgrey.patch, ac_images.zip,
ac_images.zip, accounting800x600.png, brushed-aluminum.gif,
catalog800x600.png, catalogManager.png, content800x600.png,
contentManager.png, flatgrey.patch, flatgrey.patch, flatgrey.patch,
flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif, partyDetail.png,
partyManager.png, rf_flatgrey.patch, rf_flatgrey_images.zip, 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.
4. Does not require JavaScript. JavaScript can be used to add embellishments,
but the theme can't depend on it.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Updated Flat Grey Visual Theme (was: [jira] Commented: (OFBIZ-4120) Umbrella task for features which use javascript to degrade gracefully)

2011-01-17 Thread Ryan Foster

I guess it really just comes down to the approach.  The objective of the task 
was to update the Flat Grey theme.  So, I approached the design as a realign 
rather than a redesign.  I did not look at any other themes as examples, I 
simply focused on how Flat Grey looked and functioned and then tried to make 
the smallest amount of CSS and markup changes possible in order to achieve the 
objective and stay with the scope of the task.

I understand your bias, because I have it as well, as probably every other 
active OFBiz developer does.  But for the average user, the vast majority are 
going to select one language, one time zone, and one theme and then never touch 
this section again.   Also, for a developer deploying OFBiz across a large 
organization, they may even decide to set these preferences globally across the 
entire organization and not allow the user to have these selections.  In that 
case, it becomes much easier for them because they can simply disable the 
footer in the theme and it does not affect anything else at all.
 
Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com
ryanlfoster.com

On Jan 17, 2011, at 11:07 AM, Jacques Le Roux wrote:

 Ryan Foster wrote:
 That was exactly what I was trying to do.  It seemed even more weird to me 
 to have theme selection and language in the header,
 but have timezone selection in the footer and to have half of the 
 application links in the header and the other half in the
 footer.  The new grouping is much more logical in my opinion.  All of the 
 applications are now grouped together in the header,
 and all of the user preference selections, which are secondary, are grouped 
 together in the footer.
 
 That was true for the old Flat Grey but what about how it's handled in 
 Tomahawk for instance. Maybe I'm biased though because for testing purpose 
 I'm always switching languages and themes... BTW the time zone selection is 
 missing in Tomahawk...
 
 Jacques
 
 Ryan L. Foster
 801.671.0769
 cont...@ryanlfoster.com
 ryanlfoster.com
 
 On Jan 17, 2011, at 7:30 AM, Adrian Crum wrote:
 
 Ryan can answer that question. I believe he was trying to keep the masthead 
 small so there is more room for the main content.
 
 -Adrian
 
 --- On Mon, 1/17/11, Jacques Le Roux (JIRA) j...@apache.org wrote:
 Also I asked
 {quote}
 BTW I was surprised that Ryan and you put the access to
 preferences and languages features in the footer. It's not
 always visible and seems a bit weird to me
 {quote}
 
 Any answers? ;)

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme

2011-01-14 Thread Ryan Foster (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ryan Foster updated OFBIZ-4092:
---

Attachment: rf_flatgrey.patch

Incorporated Adrian's styling and bug fixes from latest patch, dialed back
styling from my latest patch.

Adrian,
I see where you were going with the whole resizing header idea, but IMHO, I
just don't think it looks good. Having a scrollbar in the masthead just feels
really weird to me. My latest patch leaves that piece out.

Also updated app-navigation background image with a new darker, textured image.
Not as bold as your brushed aluminum, but not quite as light as the image I
had there before. Take a look and let me know what you think. This is my last
patch for this effort. Feel free to make any other mods that you think might
be necessary, but I am pretty comfortable rolling with this as-is.

Update The Flat Grey Visual Theme
-

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme

2011-01-14 Thread Ryan Foster (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: rf_flatgrey_images.zip

 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: ac_flatgrey.patch, ac_flatgrey.patch, ac_images.zip, 
 ac_images.zip, accounting800x600.png, brushed-aluminum.gif, 
 catalog800x600.png, catalogManager.png, content800x600.png, 
 contentManager.png, flatgrey.patch, flatgrey.patch, flatgrey.patch, 
 flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif, partyDetail.png, 
 partyManager.png, rf_flatgrey.patch, rf_flatgrey_images.zip, 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.
 4. Does not require JavaScript. JavaScript can be used to add embellishments, 
 but the theme can't depend on it.

-- 
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

2011-01-12 Thread Ryan Foster (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980862#action_12980862
]

Ryan Foster commented on OFBIZ-4092:

I agree with you on the casing for the navigation and title.

The casing on the buttons, and in fact the buttons themselves, are a different
issue entirely. The reason why I changed the casing with CSS is because there
is no consistency in casing in the markup and labels. Some button labels and
values are all caps, some are lowercase, some are normal case; it's all over
the map.

Button styling in OFBiz has been something that has bugged me for years and I
think it would be very beneficial to look at this as a separate issue in the
near future. There are currently 13, yes 13!, different button styles
currently defined right now. Just look at lines 2556 through 2573 in
maincss.css. We have:

.buttontext,
.buttontextbig,
.smallSubmit,
.mediumSubmit,
.largeSubmit,
.loginButton,
.button-style-1,
.button-style-2,
.button,
button,
input[type=reset],
input[type=submit],
input[type=button]

it's kind of ridiculous. Why can't we simply have 1 button class and call it
some obvious like .button or .btn? We have been having a great discussion on
UI labeling consistency, Edit vs. Update vs. Save, etc. which is awesome,
but I think all of that is meaningless if the buttons themselves don't look the
same. Okay, I'll end my rant there. Can you tell this is something of a hot
button issue with me, pun completely intended ;)

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: ac_flatgrey.patch, ac_images.zip, accounting800x600.png,
brushed-aluminum.gif, catalog800x600.png, catalogManager.png,
content800x600.png, contentManager.png, flatgrey.patch, flatgrey.patch,
flatgrey.patch, flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif,
partyDetail.png, partyManager.png, screenshot.gif, timeSheet.png

--
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

2011-01-12 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980883#action_12980883
 ] 

Ryan Foster commented on OFBIZ-4092:


I tried deleting deprecated styles and letting things break when I created the 
BizznessTime theme... mostly just pissed people off.  :)

 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: ac_flatgrey.patch, ac_images.zip, accounting800x600.png, 
 brushed-aluminum.gif, catalog800x600.png, catalogManager.png, 
 content800x600.png, contentManager.png, flatgrey.patch, flatgrey.patch, 
 flatgrey.patch, 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.
 4. Does not require JavaScript. JavaScript can be used to add embellishments, 
 but the theme can't depend on it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (OFBIZ-4092) Update The Flat Grey Visual Theme

2011-01-12 Thread Ryan Foster

Bruno,

I'll see your 2 cents, and raise you a dollar. I agree, the naming of an
element should never dictate how it looks or behaves; that is what properties
are for. You are opening up a can of worms with me when you start down that
path, so careful what you wish for. Buttons aren't the only offenders when it
comes to that, the problem starts with the main decorator. The layout of the
backend and the front end center around the fact that we have column layouts
with classNames of .left, .right, and .center. What if I don't want .left on
the left anymore?...

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com
ryanlfoster.com

On Jan 12, 2011, at 1:01 PM, Bruno Busco wrote:

In addition, when deprecating or selecting styles to be used we should
better use style names that describe what the button IS in the screen and
not HOW it should appear.

So style names like
.buttontextbig, .smallSubmit, .mediumSubmit, .largeSubmit,
.button-style-1, .button-style-2,

should not be used.

Style names like:
.buttontext,
.loginButton,
.button,
input[type=reset],
input[type=submit],
input[type=button]

are OK.
In this way the theme can make a button larger or smaller than another
button according to its function.

My two cents.
-Bruno

2011/1/12 Ryan Foster (JIRA) j...@apache.org

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980883#action_12980883]

Ryan Foster commented on OFBIZ-4092:

I tried deleting deprecated styles and letting things break when I created
the BizznessTime theme... mostly just pissed people off. :)

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: ac_flatgrey.patch, ac_images.zip,
accounting800x600.png, brushed-aluminum.gif, catalog800x600.png,
catalogManager.png, content800x600.png, contentManager.png, flatgrey.patch,
flatgrey.patch, flatgrey.patch, 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.
4. Does not require JavaScript. JavaScript can be used to add
embellishments, but the theme can't depend on it.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Discussion: CSS styles (was: [jira] Commented: (OFBIZ-4092) Update The Flat Grey Visual Theme)

2011-01-12 Thread Ryan Foster

Consistency is not synonymous with monotonous. Hey, that sounds like a good
catch phrase... Consistency is not synonymous with monotonous™

But seriously, if different elements perform the same way then they should look
the same and be called the same thing. There is no reason why we can't have
button class=btn, input type=submit class=btn, and a class=btn if
they all do the same thing. That doesn't make the UI bland, it makes it
consistent and familiar. I'm all for having options, but they should be done
with a purpose. For instance, we could a primary button style, a secondary
button style and a tertiary button style, but these should be combinations, not
individual style. For example:

a href=# class=btn primary
a href=# class=btn secondary
a href=# class=btn tertiary

That way, we could apply a consistent button style and then make adjustments if
we need to based on what action the button performs, Save vs. Cancel, etc. But
simply having a button-style-1, and a button-style-2 because maybe we want to
have a blue button and a green button is not a good reason, no is it a good
idea. Having 2 buttons that perform the same, but look different just confuses
the user and makes an already complex application even more difficult to use.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com
ryanlfoster.com

On Jan 12, 2011, at 1:30 PM, Adrian Crum wrote:

We need the smallSubmit style so we can style links to look like submit
buttons. Maybe we could change the CSS class to a.smallSubmit to make sure
it is used only for a elements.

The button-style-1 and button-style-2 style names are pretty generic - they
don't indicate how the button should appear (aside from the obvious - that
they should look like buttons). Originally, the rows of buttons below the
page title had two styles that indicated two types of buttons: those that
linked to other pages within the application (intra-app) and others that
linked to pages outside the application (inter-app). That distinction has
been lost in recent changes.

A similar thing was done with the table header styles - there are two styles
to choose from, depending on how you use them. The style names don't indicate
what they look like.

I don't think there is anything wrong with having more than one style to
choose from. If we were to cut back too much on the selection, then the UI
would start to look bland or monotonous.

I created a Wiki page that listed some of the deprecated styles and another
page that describes the new styles and how they should be used. Those pages
are effective only when people take the time to read them.

-Adrian

On 1/12/2011 12:01 PM, Bruno Busco wrote:
In addition, when deprecating or selecting styles to be used we should
better use style names that describe what the button IS in the screen and
not HOW it should appear.

So style names like
.buttontextbig, .smallSubmit, .mediumSubmit, .largeSubmit,
.button-style-1, .button-style-2,

should not be used.

Style names like:
.buttontext,
.loginButton,
.button,
input[type=reset],
input[type=submit],
input[type=button]

are OK.
In this way the theme can make a button larger or smaller than another
button according to its function.

My two cents.
-Bruno

2011/1/12 Ryan Foster (JIRA)j...@apache.org

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980883#action_12980883]

Ryan Foster commented on OFBIZ-4092:

I tried deleting deprecated styles and letting things break when I created
the BizznessTime theme... mostly just pissed people off. :)

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: ac_flatgrey.patch, ac_images.zip,
accounting800x600.png, brushed-aluminum.gif, catalog800x600.png,
catalogManager.png, content800x600.png, contentManager.png, flatgrey.patch,
flatgrey.patch, flatgrey.patch, 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.
4. Does not require JavaScript. JavaScript can be used to add
embellishments, but the theme can't depend on it.

--
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

2011-01-11 Thread Ryan Foster (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980217#action_12980217
]

Ryan Foster commented on OFBIZ-4092:

I agree with you. I'm starting to stray from my original design concept which
was meant to be subtle, sophisticated and conservative. Things are starting to
pop out a bit too much in places. Time to rein it in ;). I'll take a look at
this today. We are definitely very close.

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: ac_flatgrey.patch, ac_images.zip, accounting800x600.png,
catalog800x600.png, catalogManager.png, content800x600.png,
contentManager.png, flatgrey.patch, flatgrey.patch, flatgrey.patch,
flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif, partyDetail.png,
partyManager.png, screenshot.gif, timeSheet.png

--
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

2011-01-11 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980331#action_12980331
 ] 

Ryan Foster commented on OFBIZ-4092:


I'll do my best to take a look at what you have and finalize my changes today.

 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: ac_flatgrey.patch, ac_images.zip, accounting800x600.png, 
 brushed-aluminum.gif, catalog800x600.png, catalogManager.png, 
 content800x600.png, contentManager.png, flatgrey.patch, flatgrey.patch, 
 flatgrey.patch, 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.
 4. Does not require JavaScript. JavaScript can be used to add embellishments, 
 but the theme can't depend on it.

-- 
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=12979626#action_12979626
 ] 

Ryan Foster commented on OFBIZ-4092:


Oops, sorry Adrian.  I actually just did all these same things from your latest 
patch over the weekend. No big deal, I'll just patch your patch and go from 
there.  What other items do you have on your priority list that you are working 
on so we are not stepping on each others toes?

 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, 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.
 4. Does not require JavaScript. JavaScript can be used to add embellishments, 
 but the theme can't depend on it.

-- 
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=12979632#action_12979632
]

Ryan Foster commented on OFBIZ-4092:

I'm not sure that hard-coding the column count to 7 is that big of a deal.
That 7 is actually a max of 7, not a hard seven. The script loops through the
list items and fills the columns from top to bottom, left to right until it
reaches the end of the list. So, if there are only 8 applications in the list,
you will only have 2 columns, 12 apps means 3 columns, etc. 7 was chosen
because that is the break point of the horizontal fold. Anymore that 7 columns
and a horizontal scrollbar is created on an 800px width browser viewport.

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, flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif,
partyDetail.png, partyManager.png, screenshot.gif, timeSheet.png

--
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=12979639#action_12979639
]

Ryan Foster commented on OFBIZ-4092:

I also noticed you changed the design objectives to include a statement that
javascript should not be required. If that is the case, then I will really
have to step back and think about my approach for graceful degradation on the
main navigation since the key design principle for this section is based on the
fact that the list falls into columns.

I am curious as to why you feel this should be a key objective. Since the
framework web apps themselves are heavily dependent on javascript in certain
areas, shouldn't it be assumed that the user will always have javascript
available? If they don't, they are going have a lot more issues with
functionality than just having a visual display that is a little off.

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, flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif,
partyDetail.png, partyManager.png, screenshot.gif, timeSheet.png

--
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=12979652#action_12979652
]

Ryan Foster commented on OFBIZ-4092:

hmm... Is there a way we can do something similar using FreeMarker in
appbar.ftl instead of using Javascript? Could we create a macro that reads the
numbers of apps then outputs a series of lists in the appropriate amount of
columns. If that is possible that would actually be a better solution since
then we wouldn't have to wait until the page fully loads and the DOM is ready
before applying the column styling.

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, flatgrey.patch, flatgrey.patch, images.zip, ofbiz_logo.gif,
partyDetail.png, partyManager.png, screenshot.gif, timeSheet.png

--
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=12979870#action_12979870
]

Ryan Foster commented on OFBIZ-4092:

duh, I guess I should have actually read your patch first before I started
thinking out loud. Your solution looks great. I made couple of small tweaks
to it to remove some markup that I thought wasn't really necessary. For
instance, we don't really need to enclose each app title in in a p tag since
the a is already set to display block. I also put a set height to the li
tag and removed the empty p tags with spaces from the last li. Please
don't take this personally, but one of my biggest pet peeves is using spaces
and breaks in markup to control layout. Let's try to avoid that as much as
possible.

I have incorporated the changes from your last patch and made a few more design
changes as well in my latest patch.

1. added additional styling to the main navigation to highlight the select app
a bit more.
2. expanded on your change to the selected app navigation link to give it even
more distinction
3. enhanced the styling of the tab-bar area.
4. added some misc. CSS3 styling enhancements to main nav and app nav areas
for browsers that support text-shadow.

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, flatgrey.patch, flatgrey.patch, flatgrey.patch, images.zip,
ofbiz_logo.gif, partyDetail.png, partyManager.png, screenshot.gif,
timeSheet.png

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: flatgrey.patch

 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, flatgrey.patch, 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.
 4. Does not require JavaScript. JavaScript can be used to add embellishments, 
 but the theme can't depend on it.

-- 
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

2011-01-07 Thread Ryan Foster

 fix it.
 Now if you talking about new themes I can agree, but no one has
 proposed any or give an price.
 
 =
 BJ Freeman
 Strategic Power Office with Supplier Automation
 http://www.businessesnetwork.com/automation/viewforum.php?f=52
 Specialtymarket.com http://www.specialtymarket.com/
 Systems Integrator-- Glad to Assist
 
 Chat Y! messenger: bjfr33man
 
 
 Adrian Crum sent the following on 1/6/2011 3:23 PM:
 
 That can go both ways. If your deployments depends upon the visual
 themes being in the trunk, then perhaps you should fund their upkeep.
 
 -Adrian
 
 On 1/6/2011 2:58 PM, BJ Freeman wrote:
 
 so you will be glad to fund the effort to do that.
 Time is money. and anything the effects the ROI needs to be
 considered,
 if the software is to be widely accepted.
 
 =
 BJ Freeman
 Strategic Power Office with Supplier Automation
 http://www.businessesnetwork.com/automation/viewforum.php?f=52
 Specialtymarket.com http://www.specialtymarket.com/
 Systems Integrator-- Glad to Assist
 
 Chat Y! messenger: bjfr33man
 
 
 Ryan Foster sent the following on 1/6/2011 2:51 PM:
 
 I completely agree with you BJ. Considerations definitely have to be
 made when things are removed, especially if they are tied to the
 framework. What is being discussed is whether to remove themes, which
 can be hot-deployed from being maintained in the trunk. For future
 releases, all you would need to do is manually add your themes,
 custom
 or otherwise, to your production instance. If they are no longer tied
 in svn to the trunk, they would not be effected by any updates or
 releases.
 
 Ryan L. Foster
 801.671.0769
 cont...@ryanlfoster.com
 
 On Jan 6, 2011, at 3:40 PM, BJ Freeman wrote:
 
 so there will not be any more releases based on the trunk?
 I was speaking in the future when 11.04 or 12.04 happen.
 
 it is the disregard of those that actually use this software instead
 of just enjoy developing it.
 
 I am a developer second and a business man first.
 
 basically you can add all you want but when you want to remove you
 must consider those that have counted on what was provided.
 
 =
 BJ Freeman
 Strategic Power Office with Supplier
 Automation
 http://www.businessesnetwork.com/automation/viewforum.php?f=52
 
 
 
 Specialtymarket.comhttp://www.specialtymarket.com/
 Systems Integrator-- Glad to Assist
 
 Chat Y! messenger: bjfr33man
 
 
 Bruno Busco sent the following on 1/6/2011 2:33 PM:
 
 The theme will still be present in the 10.04 releases.
 No production servers should rely on trunk.
 
 -Bruno
 
 2011/1/6 BJ Freemanbjf...@free-man.net
 
 I have one that uses the flat grey as default
 so if I do an update from the svn the flat grey will and my
 customization
 disappear.
 
 my sas uses all those in the themes, with my modification.
 they will be removed. when the svn update is run.
 
 those are just a few examples.
 
 
 =
 BJ Freeman
 Strategic Power Office with Supplier Automation
 http://www.businessesnetwork.com/automation/viewforum.php?f=52
 Specialtymarket.comhttp://www.specialtymarket.com/
 Systems Integrator-- Glad to Assist
 
 Chat Y! messenger: bjfr33man
 
 
 Bruno Busco sent the following on 1/6/2011 2:00 PM:
 
 I am sorry, BJ, I do not see your point.
 
 
 What could be the issue?
 We will have less themes to maintain in the trunk (just Flat
 Grey,
 Tomahawk,
 Default and Multiflex).
 We will have more people that will be able to maintain additional
 themes
 in
 the Themes Gallery.
 
 Production servers will have each one its selected theme (one of
 the OOTB,
 one of the Themes Gallery or a customized version of them).
 
 -Bruno
 
 2011/1/6 BJ 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

Re: Discussion: Flat Grey Visual Theme

2011-01-07 Thread Ryan Foster

I don't want to misquote Bruno, but I believe what he was saying was if we 
create dependencies between themes, it does not allow modular selection, 
distribution, and installation.  Not that those dependencies already exist, 
because they don't.

I am not saying that I want to get paid for all of the themes I create, I'm 
simply suggesting it would be better in the long run if we leave modularized 
theming options open, monetized or otherwise, and let the user pick and choose 
what they want to install.  Installing themes does not require a paid 
consultant to install.  A new theme can be installed on-the-fly using the xml 
data import feature in webtools in a few minutes, with very little knowledge or 
instruction.

You do bring up an interesting idea though...

Say for instance we have just 2 themes in the OOTB installation with a link 
under the selection list that said get more themes.  Clicking that would 
bring up a list of themes in an external themes repo.  We could then have a 
script that allows the user to grab the external themes XML seed data and 
download the themes assets to their installed instance.  Might be a good idea 
for a future enhancement.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com

On Jan 7, 2011, at 11:17 AM, BJ Freeman wrote:

 Bruno says:
 Dependencies between themes do not allow modular selection, distribution and 
 installation.
 You say they are modular.
 
 David has commented that he started this project with Idea that Trained 
 consultants in ofbiz would be paid to install modify, and customize ofbiz.
 That model in my opinion does not work, as David has since said, with open 
 source. Especially being in ASF.
 I have some modules that once the design time has be amortized I will release 
 to open source. Till then they cost.
 
 However my main thrust with ofbiz is first make it widely accepted so by 
 sheer numbers, there will those that want to hire consultants. So my focus is 
 a good online embedded Doc and help, along with a flexible and powerful setup 
 that will lead a end user through a complete setup.
 Part of that setup is a java based component that will go get ofbiz and 
 download it then ask if  they want demo or Production setup.  I can see in 
 that phase of the setup making the end user aware of themes in galleries they 
 can then have installed.
 
 To that end I believe the current themes should be left in place and future 
 themes that people want to get paid for be put on their own website where 
 they can amortize their efforts.
 
 
 
 =
 
 BJ Freeman
 Strategic Power Office with Supplier Automation  
 http://www.businessesnetwork.com/automation/viewforum.php?f=52
 Specialtymarket.com  http://www.specialtymarket.com/
 Systems Integrator-- Glad to Assist
 
 Chat  Y! messenger: bjfr33man
 
 
 Ryan Foster sent the following on 1/7/2011 8:52 AM:
 I understand BJ concerns, but again, I'm with Bruno on this.  Themes are 
 modular and preferential by nature.  Not every user will want or have a need 
 for every theme.  For instance, if I develop a women's boutique front-end 
 theme, it may be of great interest to an owner of a women's boutique but the 
 owner of an auto parts store could probably care less.  Why not leave 2-3 
 official release themes in the trunk that are up to date and maintained 
 consistently by the community and move everything else to an external 
 directory.  Then, let the user/developer pick and choose what themes to 
 install.
 
 In the end, we all decide whether we want to contribute the code we develop 
 back to the code base or not.  For existing themes, my vote is to keep the 
 active themes in the trunk and move the deprecated/ unsupported / 
 un-evolved themes out to the theme gallery.  This means 
 BizznessTime?(which unfortunately seems to be rapidly losing community 
 backing), Bluelight, and DroppingCrumbs.
 
 For future themes that I develop, the choice is easy for me.  I will simply 
 not grant the theme ASF license to be included in the trunk.  I will release 
 the theme to the public and post the theme to the theme gallery or 
 distribute through some other method.  If we decide to create a new theme 
 from Flat Grey, I am calling the new theme Dorian Gray 
 (http://en.wikipedia.org/wiki/Dorian_Gray).  The new theme will continue to 
 look young, fresh and modern, while it's reflection, Flat Grey, will 
 continue to look older and more dated with each passing year... ;)
 
 Ryan L. Foster
 801.671.0769
 cont...@ryanlfoster.com
 
 On Jan 7, 2011, at 5:06 AM, Bruno Busco wrote:
 
 Dependencies between themes do not allow modular selection, distribution and
 installation.
 Please give a look to these web sites:
 
 http://www.templatemonster.com/magento-themes.php
 http://wordpress.org/extend/themes/
 http://drupal.org/project/Themes
 
 they are all examples of how to maintain themes database.
 
 In a production installation one can choose between:
 - using one of the OOTB themes

Re: Discussion: Flat Grey Visual Theme

2011-01-06 Thread Ryan Foster

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

2011-01-06 Thread Ryan Foster

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

Re: Discussion: Flat Grey Visual Theme

2011-01-06 Thread Ryan Foster

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

Re: Discussion: Flat Grey Visual Theme

2011-01-06 Thread Ryan Foster

+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

2011-01-06 Thread Ryan Foster

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

Re: Discussion: Flat Grey Visual Theme

2011-01-06 Thread Ryan Foster

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

Re: Discussion: Flat Grey Visual Theme

2011-01-06 Thread Ryan Foster

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

[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=12977470#action_12977470
 ] 

Ryan Foster commented on OFBIZ-4092:


I suggest making a few small markup changes in order to bring this theme up to 
date.  For instance, the secondary app bar in the footer uses the deprecated 
center/center tag.  Things like this should be cleaned up.

 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

 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.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: partyDetail.png
contentManager.png
catalogManager.png

 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, catalogManager.png, 
 contentManager.png, partyDetail.png, partyManager.png, 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.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: content800x600.png
catalog800x600.png

 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, partyDetail.png, 
 partyManager.png, 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.

[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=12977485#action_12977485
]

Ryan Foster commented on OFBIZ-4092:

I have attached screen grabs of my WIP. Here is a quick breakdown of changes:

1. Remove top tab navigation and replace with a column list navigation.
2. Move user preferences to footer.
3. Move secondary apps to top nav and integrate with main apps in column list
navigation
4. Remove unnecessary CSS and XHTML validation icons from footer (I don't
think that the markup has validated 100% for a while. C'est la vie, but let's
no draw attention to it)
5. Removed collapsed header preference and instead keep header collapsed
permanently to save space.
6. Update general look and feel.
7. Update form and buttons styles

Update The Flat Grey Visual Theme
-

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: ofbiz_logo.gif
images.zip
flatgrey.patch

Steps for applying theme patch:

1.  Apply flatgrey.patch
2.  Update images in themes/flatgrey/webapp/flatgrey/images with new provided 
images
3.  Update OFBiz logo (ofbiz_logo.gif) in /framework/images/webapp/images with 
new attached logo.

 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, 
 images.zip, ofbiz_logo.gif, partyDetail.png, partyManager.png, 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.

[jira] Updated: (OFBIZ-4092) Update The Flat Grey Visual Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-4092:
---

Attachment: screenshot.gif

 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, 
 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.

[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=12977501#action_12977501
 ] 

Ryan Foster commented on OFBIZ-4092:


Thanks.  Good luck.  Let me know if you run into any problems.  I sure there 
will be a bug or two, as I have to admit that I just got a spark of an idea and 
just banged this all out last night.  I haven't done thorough browser tested 
yet, but it looks good so far on FF, Safari, and Chrome.

 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, 
 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: Discussion: Flat Grey Visual Theme

2011-01-03 Thread Ryan Foster

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

2011-01-03 Thread Ryan Foster

That sounds great.  Create the issue and send me a link to it and I'll get to 
work.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com

On Jan 3, 2011, at 1:37 PM, Adrian Crum wrote:

 That's great news Ryan - I can't wait to see the new theme!
 
 It's good to know you're willing to help with Flat Grey - I'm no graphics 
 artist. As far as updating Flay Grey - I can create a Jira issue and you can 
 supply patches if you like. I really don't have much to say in addition to 
 what I've said on the mailing list.
 
 Maybe the location of the main navigation tab bar can be controlled by a user 
 setting - top, left, or right.
 
 -Adrian
 
 --- On Mon, 1/3/11, Ryan Foster cont...@ryanlfoster.com 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: jquey

2010-12-02 Thread Ryan Foster

What about creating a tag or branch before the merge so that users who have 
custom projects or applications based on the trunk have a reference point in 
the event that they want to freeze their applications at a particular revision?

Oh and +1 on merging in JQuery.  I am all for consolidating/simplifying our 
Javascript libraries.  No reason to have 3 libraries that all essentially do 
the same thing.  In the end, Javascript is Javascript.  My heart says we should 
have chosen Prototype as that one (as anyone who knows me would agree, I'm a 
big Prototype JS evangelist).  But, my head says that JQuery is the right 
choice for the long-term growth and success of the project, as it has 
definitely become the drug of choice for a majority of developers and has much 
more wide-spread community involvement as far as development of plugins is 
concerned.

Ryan L. Foster
801.671.0769
cont...@ryanlfoster.com

On Dec 2, 2010, at 11:18 AM, Jacques Le Roux wrote:

 I'm sorry for Bruno, but it seems everybody is looking forward for this 
 merging. So hopefully I will do it soon.
 If you are interested you can already check 
 https://issues.apache.org/jira/browse/OFBIZ-3814
 
 Jacques
 
 Michael Xu (xudong) wrote:
 +1
 
 Yeah, I would love such a great Xmas present :-)
 
 
 You're welcome
 +1
 
 Would be a great Xmas present to merge all the stuff into the trunk :-)
 
 Am 02.12.2010 um 10:59 schrieb Erwan de FERRIERES 
 erwan.de-ferrie...@nereide.fr:
 
 Le 02/12/2010 10:35, Jacques Le Roux a écrit :
 Looks like, apart Bruno, we are all on the same page so far
 
 Other opinions, ideas?
 
 Thanks
 
 Jacques
 
 
 The sooner the better !
 
 Thanks for all your work, Jacques and Sascha
 
 --
 Erwan de FERRIERES
 www.nereide.biz

Re: [jira] Commented: (OFBIZ-4003) OnePageCheckout isn't displayed right

2010-10-29 Thread Ryan Foster

You should be shot for suggesting that ;).  All kidding aside, adding a line 
break should NEVER be used to fix a layout problem, no matter what it is.

Ryan Foster
Evitus
801.671.0769
r...@evitus.net



On Oct 29, 2010, at 3:16 AM, Sascha Rodekamp (JIRA) wrote:

 
[ 
 https://issues.apache.org/jira/browse/OFBIZ-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926219#action_12926219
  ] 
 
 Sascha Rodekamp commented on OFBIZ-4003:
 
 
 Try a 
 {code}
 br style=clear:both;/
 {code}
 
 At the end of the fieldset in the OnePageCheckoutProcess.ftl
 
 That helps me to format it the right way :-)
 
 OnePageCheckout isn't displayed right
 -
 
Key: OFBIZ-4003
URL: https://issues.apache.org/jira/browse/OFBIZ-4003
Project: OFBiz
 Issue Type: Bug
 Components: specialpurpose/ecommerce
   Affects Versions: Release Branch 10.04, SVN trunk
Environment: Ubuntu 10.10 (Firefox and Chrome) and Windows XP SP2 
 (Firefox, Chrome, IE7 and IE8)
   Reporter: David - DiSiD Technologies
Fix For: Release Branch 10.04, SVN trunk
 
Attachments: bugOnePageCheckout.jpg
 
 
 OnePageCheckout isn't displayed right when go to Step 2 of the checkout 
 process.
 To repeat, go to 
 https://demo-trunk.ofbiz.apache.org:8443/ecommerce/control/onePageCheckout 
 (login and add an item to cart if needed) and try to go to Step 2.
 
 -- 
 This message is automatically generated by JIRA.
 -
 You can reply to this email to add a comment to the issue online.

Re: The ofbiz.org domain

2010-04-15 Thread Ryan Foster

Ruth,

I disagree with you on point number 2.  Ofbiz.org is not just a domain name.  
The name OFBiz is a product, and a brand-able, trademark-able product at that.  
So, while the domain may not have as much brand value as apple.com, 
microsoft.com, or, from an open source perspective, wordpress.com; the same 
principle applies.  So even though WordPress is widely distributed and 
thousands of people make boatloads of money selling themes, customizations, 
implementation, etc. I think you would have a very tough trying to get anyone 
to sell you the wordpress.org or the wordpress.com domain.

The license for OFBiz resides with Apache, so the domain should reside with 
them as well.  The brand name, OFBiz, is intellectual property and any 
derivatives of that name including ofbiz.org, ofbiz.net, ofbiz.com, etc are 
part of the intellectual property.

As far as your commercial success goes, I think you should make money.  Lots 
and lots of money.  If you spend time and effort writing good books that 
provide valuable information, what's wrong with making a profit on them?  Most, 
if not all of the information contained in the 50-60 books I own on design and 
development could have been found combing through resources on the internet, 
but I bought them because the were well written, information books.  I know 
every book that Zeldman wrote on CSS, but I don't think he ever tried to 
register css.org -- he can't, because it's owned by The Colorado Springs School 
luck bastards ;-)

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Apr 15, 2010, at 9:47 AM, Ruth Hoffman wrote:

 Hi Jacques:
 
 Wow, I'm flattered that you would compare myOFBiz.com to Java! Or at least 
 juxtapose it with the big boys :-)
 
 Just to clear the air:
 
 1) myOFBiz.com is not an organization, company or any other commercially 
 viable entity. It is a domain name and a server running an instance of OFBiz.
 
 2) Like myOFBiz.com, ofbiz.org is only a domain name. Both have no 
 intellectual property or other proprietary resources that could be sold. The 
 only thing that can be sold, in either case, is the domain name. Which, I 
 have to admit for ofbiz.org has brand recognition - at least today. That is 
 why I'm interested in it. .
 
 3) I fully understand your position. IMO  the ofbiz.org domain is not a 
 sacred icon. In fact, as each day goes by, it has less and less meaning. If 
 project committers and other OFBiz devotees wish to worship at the ofbiz.org 
 shrine, then who am I to ask why?. It is you belief that ofbiz.org has 
 value. I'm very progressive in at least this regard: I believe, to each 
 his/her own.
 
 On a related note, do you feel that there is something wrong with commercial 
 success? What I mean is, why can't OFBiz enjoy some commercial success? Or 
 maybe I should ask, what do you mean by commercial?
 
 Kind Regards,
 Ruth
 
 Thanks
 
 Jacques Le Roux wrote:
 Hi Ruth,
 
 I'm sorry to say that I agree with Jeroen. I'd never have made a proposition 
 like yours: for me ofbiz.org is clearly and should
 remain a community name.
 
 It's not directed against you, because I believe in your faith in OFBiz. But 
 who knows what will happen with your effort? It's hard
 to trust people, even when you have a good feeling, but it's even harder to 
 trust organizations. Look for instance at what happened
 recently to Java now owned by Oracle (and BTW according to Tiobe recenlty 
 lost its 1st place as a language
 http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html), MySql may 
 also suffer for the same reason, and we know the IT
 history is cluttered of such cases.
 
 Also I was already dissapointed by the Opentaps experience. Even if Si has 
 been almost clear about his intentions (not sure at which
 point though) see How to make money from open source at 
 http://www.opensourcestrategies.org/.
 
 My 2 cts
 
 Jacques
 
 From: Ruth Hoffman rhoff...@aesolves.com
 Hi Jeroen:
 If this was a directed to me, then:
 
 1) My enterprise is not a money making, commercial concern. My mission 
 has always been to provide high quality affordable
 learning resources to the community at large. My view of the community is 
 anyone looking for OFBiz materials, not just project
 committers. The only way I can possible afford to do that is charge a 
 nominal fee for some of these books. And, believe me, I'm
 not making any money on this endeavor. As I've said before, it is a labor 
 of love.
 
 2) Want to donate money to help the cause? Buy some of my books. You will 
 help pay for the server and hosting, quality content
 creation tools, professional editors, SME's time in reviewing 
 materials...and I could go on.
 
 Regards,
 Ruth
 
 Find me on the web at http://www.myofbiz.com or Google keyword myofbiz
 ruth.hoff...@myofbiz.com
 
 Jeroen van der Wal wrote:
 I don't like to see ofbiz.org to be used for commercial purposes. If
 the subscription cost

Re: The ofbiz.org domain

2010-04-15 Thread Ryan Foster

Ruth,

I disagree with you on point number 2.  Ofbiz.org is not just a domain name.  
The name OFBiz is a product, and a brand-able, trademark-able product at that.  
So, while the domain may not have as much brand value as apple.com, 
microsoft.com, or, from an open source perspective, wordpress.com; the same 
principle applies.  So even though WordPress is widely distributed and 
thousands of people make boatloads of money selling themes, customizations, 
implementation, etc. I think you would have a very tough trying to get anyone 
to sell you the wordpress.org or the wordpress.com domain.

The license for OFBiz resides with Apache, so the domain should reside with 
them as well.  The brand name, OFBiz, is intellectual property and any 
derivatives of that name including ofbiz.org, ofbiz.net, ofbiz.com, etc are 
part of the intellectual property.

As far as your commercial success goes, I think you should make money.  Lots 
and lots of money.  If you spend time and effort writing good books that 
provide valuable information, what's wrong with making a profit on them?  Most, 
if not all of the information contained in the 50-60 books I own on design and 
development could have been found combing through resources on the internet, 
but I bought them because the were well written, information books.  I own 
every book that Zeldman wrote on CSS, but I don't think he ever tried to 
register css.org -- he can't, because it's owned by The Colorado Springs School 
luck bastards ;-)

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Apr 15, 2010, at 1:08 PM, Ruth Hoffman wrote:

 
 
 Jacques Le Roux wrote:
 Ruth,
 
 From: Ruth Hoffman rhoff...@aesolves.com
 Hi Jacques:
 
 Wow, I'm flattered that you would compare myOFBiz.com to Java! Or at least 
 juxtapose it with the big boys :-)
 
 Just to clear the air:
 
 1) myOFBiz.com is not an organization, company or any other commercially 
 viable entity. It is a domain name and a server running an instance of 
 OFBiz.
 
 2) Like myOFBiz.com, ofbiz.org is only a domain name. Both have no 
 intellectual property or other proprietary resources that could be sold. 
 The only thing that can be sold, in either case, is the domain name. Which, 
 I have to admit for ofbiz.org has brand recognition - at least today. That 
 is why I'm interested in it. .
 
 3) I fully understand your position. IMO  the ofbiz.org domain is not a 
 sacred icon. In fact, as each day goes by, it has less and less meaning. 
 
 Less meaning? Why?
 Because it has been superseded by the Apache brand. IMO, if the Apache brand 
 catches on, then the ofbiz.org brand will fade. And we all want the Apache 
 brand to succeed. That ofbiz.org does not (and should not) compete with 
 Apache is a good thing. Better to just put it to rest and be done with it. 
 I'm not against ASF having it, I just wanted to continue to market and push 
 it as a complement to the ASF brand.
 If project committers and other OFBiz devotees wish to worship at the 
 ofbiz.org shrine, then who am I to ask why?. It is you belief that 
 ofbiz.org has value. I'm very progressive in at least this regard: I 
 believe, to each his/her own.
 
 to each his/her own: a new idiom for me
 How about, live and let live.
 
 On a related note, do you feel that there is something wrong with 
 commercial success? What I mean is, why can't OFBiz enjoy some commercial 
 success? Or maybe I should ask, what do you mean by commercial?
 
 To paraphrase a famous predecessor I challenge you to quote where I said 
 that. :D
 Ok, fair. Sorry. I didn't mean any disrespect.
 
 Jacques
 PS: BTW I wish you all the best with myOfbiz.com. Because I know it will be 
 good for OFBiz and the community at large...
 Thanks. I am certainly trying to make it so!
 Regards,
 Ruth
 
 Kind Regards,
 Ruth
 
 Thanks
 
 Jacques Le Roux wrote:
 Hi Ruth,
 
 I'm sorry to say that I agree with Jeroen. I'd never have made a 
 proposition like yours: for me ofbiz.org is clearly and should
 remain a community name.
 
 It's not directed against you, because I believe in your faith in OFBiz. 
 But who knows what will happen with your effort? It's hard
 to trust people, even when you have a good feeling, but it's even harder 
 to trust organizations. Look for instance at what happened
 recently to Java now owned by Oracle (and BTW according to Tiobe recenlty 
 lost its 1st place as a language
 http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html), MySql 
 may also suffer for the same reason, and we know the IT
 history is cluttered of such cases.
 
 Also I was already dissapointed by the Opentaps experience. Even if Si has 
 been almost clear about his intentions (not sure at which
 point though) see How to make money from open source at 
 http://www.opensourcestrategies.org/.
 
 My 2 cts
 
 Jacques
 
 From: Ruth Hoffman rhoff...@aesolves.com
 Hi Jeroen:
 If this was a directed to me, then:
 
 1) My enterprise is not a money making, commercial concern

Re: Screen Widget screenlet and the hard coded br class=clear

2010-01-13 Thread Ryan Foster

I think that is kind of the point Adrian.  Many screens are fragile because 
they have been hacked together with br tags, inline styles, etc, not in spite 
of that fact.  We should remove these everywhere they are found and replace 
them with proper markup that is more stable and more flexible.  You can just as 
easily clear the floated element with the element underneath or use any number 
CSS solutions that will make the element clear itself without any additional 
empty tags.  In the Bizznesstime Theme, this is already built in.  If you want 
an element to clear itself, just give it a clear name of clearfix.  At the 
very least, we should replace the br tag with a div tag.  At least then we 
are using better markup.  Line breaks should be used in text, as they are 
intended, not for layout.

Sorry for the soapbox, but as the lone wolf front-end developer on this list 
sometimes, I feel like I need to speak up when there is something I feel 
strongly about.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Jan 12, 2010, at 11:28 PM, Adrian Crum wrote:

 I disagree. The stuff we have doesn't work just fine. Try removing the 
 clearing element and see what happens. The multi-column layout you're working 
 on looks great, but now everything else is broken.
 
 Our existing multi-column layout is extremely fragile and easily broken. 
 That's why I suggested the column widgets. It's a bigger issue than dragging 
 columns or changing sizes.
 
 -Adrian
 
 --- On Tue, 1/12/10, David E Jones d...@me.com wrote:
 
 From: David E Jones d...@me.com
 Subject: Re: Screen Widget screenlet and the hard coded br class=clear
 To: dev@ofbiz.apache.org
 Date: Tuesday, January 12, 2010, 10:20 PM
 
 The point isn't to accommodate multi-column layouts, we
 already have basic stuff for that which works just fine. I'm
 not talking about anything like dragging columns or
 configuring sizes or anything like that. It's an interesting
 idea, but a different one.
 
 The question I have is do we really want this br
 class=clear/ tag always inserted when you use the
 screen widget screenlet element?
 
 Right now there is a bit of a hack in place to cause this
 tag to do nothing, and that is by wrapping the screenlet in
 a container with a style of no-clear.
 
 So, the point is that is seems like in most cases this
 clear isn't needed and we can avoid the no-clear hack by
 having something explicit when it is needed.
 
 -David
 
 
 On Jan 13, 2010, at 12:13 AM, Adrian Crum wrote:
 
 We had a discussion about accommodating multi-column
 layouts. Search the dev list for Subject = Discussion:
 Column Widgets (was: How to add a splitter to adjust the
 left column width by dragging it?
 
 -Adrian
 
 --- On Tue, 1/12/10, David E Jones d...@me.com
 wrote:
 
 From: David E Jones d...@me.com
 Subject: Screen Widget screenlet and the hard
 coded br class=clear
 To: dev@ofbiz.apache.org
 Date: Tuesday, January 12, 2010, 10:07 PM
 
 I am looking into an issue with formatting using
 a
 CSS-based multiple column layout and with
 screenlets in each
 column.
 
 The problem is that in the
 htmlScreenMacroLibrary.ftl file
 there is a hard-coded clear on line 148:
 
 br class=clear /
 
 With most browsers these clears are no
 context-sensitive,
 they clear ALL floats. This means that it messes
 up the
 multi-column formatting.
 
 Would anyone be too disappointed if we removed
 this, and if
 you need a clear below your screenlet then just
 use a
 container element after the screenlet element in
 your screen
 definition?
 
 Also, does anyone know the reason this was put
 there in the
 first place?
 
 Can anyone think of any issues removing this might
 cause?
 
 -David

Re: breadcrums dropdown scheme

2010-01-06 Thread Ryan Foster

I think what your customer might be looking for (and consequently, what you are 
looking for) is not transparent, but semi-transparent.  If you make the 
background completely transparent, you won't be able to see the menu and it 
will be completely useless.  However, you could make the background color 
semi-transparent/opaque, allowing you to see the menu and also see what is 
underneath it (like a lightbox type effect).  Here is a cross-browser CSS 
transparency solution:

.transparent_class {
 background-color:#333;
 filter:alpha(opacity=50);  
 -moz-opacity:0.5;  
 -khtml-opacity: 0.5;  
 opacity: 0.5;
 -ms-filter: progid:DXImageTransform.Microsoft.Alpha(Opacity=50);  
}

This will result in a 50% gray opaque background.  Hope this help Hans.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Jan 6, 2010, at 6:17 AM, Hans Bakker wrote:

 Thank you very much for your help, that is what i was just looking
 for...
 
 Regards,
 Hans
 
 On Wed, 2010-01-06 at 18:44 +0530, Rishi Solanki wrote:
 Hi Hans,
 breadcrumbs dropdown's style.css line 1080 of  #main-navigation ul li ul,
 #app-navigation ul li ul
 make its background to transparent will solves the transparent background
 problem. But for sure it should not be recommended.
 
 
 Rishi Solanki
 Enterprise Software Developer
 HotWax Media Pvt. Ltd.
 
 
 On Wed, Jan 6, 2010 at 11:32 AM, Rishi Solanki 
 rishisolan...@gmail.comwrote:
 
 Sorry, I see you are asking for breadcrubs dropdown, for that I'm not able
 to figure out how it can be achieve.
 
 
 Rishi Solanki
 Enterprise Software Developer
 HotWax Media Pvt. Ltd.
 
 
 On Wed, Jan 6, 2010 at 10:59 AM, Rishi Solanki 
 rishisolan...@gmail.comwrote:
 
 To make the dropdown menu transparent go to style.css of bizznesstime
 theme and on line 556 change the css of #header-nav to ;
 background:transparent none repeat scroll 0 0;
 If we look at the particular applications menu in bizzness time theme it
 will be shown as transparent. May need to do some more fixes in css to
 better show it on UI.
 So it is possible but should not recommended as the underlying screen text
 overlapped on the menu links, in turn it will be a pain for user to select
 on the correct menu item.
 
 Rishi Solanki
 Enterprise Software Developer
 HotWax Media Pvt. Ltd.
 
 
 
 On Wed, Jan 6, 2010 at 7:53 AM, Hans Bakker 
 mailingl...@antwebsystems.com wrote:
 
 A question from one of my customers:
 
 the dropdown menu, is it possible to make this transparent so you can
 see the underlying screen?
 
 Thanks in advance for your answer,
 
 regards,
 Hans
 
 
 --
 Antwebsystems.com: Quality OFBiz services for competitive rates
 
 
 
 
 -- 
 Antwebsystems.com: Quality OFBiz services for competitive rates

Re: DOCTYPE setting in HtmlScreenRenderer

2009-12-17 Thread Ryan Foster

+1 for moving it to a config file.  This is something that I have always found 
to be a little annoying.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Dec 17, 2009, at 9:11 AM, Adrian Crum wrote:

 That would be cool, but the DOCTYPE element is emitted before any widgets are 
 rendered. It is set up that way so no widget comments or other markup can 
 precede the DOCTYPE element.
 
 -Adrian
 
 David E Jones wrote:
 This is probably something that should be in the decorator templates. Then 
 it can be customized along with the other HTML.
 -David
 On Dec 17, 2009, at 9:54 AM, Adrian Crum wrote:
 Converting hard-coded settings to configuration files is always encouraged.
 
 -Adrian
 
 Adrian Cumiskey wrote:
 Hi all,
 My client has a requirement for XHTML 1.0 Strict compliance in their OFBiz
 implementatoin.  I've been hunting around and discovered that the DOCTYPE 
 is
 set in the class org.ofbiz.widget.html.HtmlScreenRenderer in the
 renderScreenBegin() method.   Now I could simply change the line of code or
 extend HtmlScreenRenderer, but I was thinking that it might be better to
 have this setting in a configuration file somewhere instead (perhaps in
 common/config/general.properties?).  I would be interested to hear your
 thoughts.
 Cheers,
 Adrian Cumiskey.

Re: Working together. was: plans are nice, but what then?

2009-10-22 Thread Ryan Foster

I really was trying not to say anything here, first because I do not  
wish to add any fuel to the fire, and secondly because this  
conversation did not personally concern me.  However, I fail see any  
circumstance when a personal conversation is very much bad form.   
Isn't the opposite generally true?  I have found that if two people  
are having a disagreement, a phone call clears the air much, much  
faster than a vague, insincere, public mailing list.  Wouldn't you  
agree?


Just because something starts in public, doesn't mean it has to end in  
public.  If I lose my temper and yell at my wife in the middle of the  
grocery store, I am certainly not going to take her back there  
tomorrow and apologize to her in front of the cashier and the stock  
boy.  It's none of their business, and it's none of yours either.  As  
far as I am concerned, this conversation was a disagreement between  
Hans and Tim.  If they decide they want to resolve their conflicts by  
emailing each other privately, Tim calls to apologize to Hans, Hans  
calls to apologize to Tim, or the two of them sit down and have a beer  
together at ApacheCon and then punch each other in the face, that is  
really none of my business.


Let's keep the dev list for discussions about OFBiz development.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Oct 22, 2009, at 4:20 PM, Adam Heath wrote:


Tim Ruppert wrote:
Just so everyone is on the up and up, Hans and I are offline  
reconciling
_both_ attacks and will figure a way forward.  Thanks for the  
help and

the concern.


Offline?  Why?  This incident occurred in public, so should be
resolved in public.  Private emails, private phone calls, are very
much bad form.

Additionally, if there are internal things(thoughts, circumstances,
etc) that make you(or anyone else) think a certain way, then it's not
correct for you to get upset when the rest of us call you(or whoever)
out about it.  We do *not* know what makes other people tick.  We can
only see what is *done*.

Re: not serving a particular browser version

2009-10-20 Thread Ryan Foster

There are lots of ways to detect browsers using javascript or  
conditional statements, but IMHO your plan seems to me to be a very  
bad approach, especially on an ecommerce site.  You are essentially  
turning away the largest customer base at the door (like it or not,  
IE7 still has the largest browser market share).  Not many users are  
going to download and install a new browser if they don't have it  
already just to buy a shirt, or a pair of shoes, etc. when there are a  
thousand other sites selling exactly the same thing that do support IE7.


You are much better off creating an IE7 specific stylesheet and using  
a conditional statement to attach it to the page only when the user is  
using IE7:


http://msdn.microsoft.com/en-us/library/ms537512%28VS.85%29.aspx

Or a quick and dirty method if you want to use only one stylesheet is  
to use javascript to detect the browser and OS and create browser  
specific styling in your main stylesheet.  This method allows you to  
do this without hacks, so your CSS will still validate against  
standards:


http://rafael.adm.br/css_browser_selector/
http://github.com/rafaelp/css_browser_selector

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Oct 19, 2009, at 11:37 PM, aswath narayana wrote:


Any ideas on this...
My ecommerce pages are very bad in IE7.  Hence, I don't want to  
support

IE7.
Where are the hooks to provide this kind of check?

Thanks a lot.
Aswath

On Mon, Oct 19, 2009 at 12:08 PM, aswath narayana 
aswath.satras...@gmail.com wrote:


Hello,
I don't want to support IE7, so I want to display a message to the  
user

saying
'use IE8, firefox etc.'

How can this be done

Regards
-Aswath

Re: maincss.css : relative path error

2009-09-14 Thread Ryan Foster

So it sounds like the simplest solution would be to copy the styles  
used by the email templates from maincss.css to ecommain.css and then  
change the path to point to ecommain.css.


One thing I would like to propose for development going forward,  
however,  is that we move ecommain.css and related images into its own  
folder in the /themes directory and classify it as a front-end theme  
as well, just the same we have done for the rest of the themes  
(bizznesstime, flatgrey, multiflex, bluelight, etc.).  Now that we  
have implemented themes functionality, it doesn't make sense to leave  
ecommain.css in the framework images folder.  There should be no  
reason we should have any hard-coded stylesheet values in screen  
definitions or Freemarker templates in the framework, front-end or  
back-office.  This should be controlled by the theme parameters.


Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Sep 14, 2009, at 6:59 AM, Scott Gray wrote:

They may display better with main.css but if they are ecommerce  
emails then they should use the ecommerce stylesheet.


Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 15/09/2009, at 12:47 AM, Eric DE MAULDE wrote:


Thanks Ryan

I don't have a solution to manage maincss.css according to the theme.

For example, mails are a better display with maincss.css than  
ecommain.css


Eric

- Original Message - From: Ryan Foster ryan.fos...@hotwaxmedia.com 


To: u...@ofbiz.apache.org
Sent: Monday, September 14, 2009 5:58 AM
Subject: Re: maincss.css : relative path error



Jacques,
That is correct.  There is only one maincss.css file.  It used to  
be  located in the images folder when flatgrey was the only/ 
default  theme for the OFBiz back office applications.  It was  
moved to the / flatgrey webapp theme when we added the additional  
themes  (bizznesstime and bluelight) and made bizznesstime the  
default theme.

Eric,
It does appear the files you listed do have an incorrect relative   
path.  However, it seems to me that there is another problem  
beyond  the relative path issue.  The files mentioned below apply  
to the  ecommerce component don't they?  They should be  
referencing  ecommain.css not maincss.css.  Also, any back office  
screen view  should not have a hard-coded path to maincss.css  
anyway.  The  stylesheet should be controlled by the themes  
component.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com
On Sep 10, 2009, at 2:06 AM, Jacques Le Roux wrote:

Hi Eric,

I'm not totally sure, but as there are no other maincss.css file  
I  guess so... Maybe there is something else to change, themes  
gurus ?


Jacques

From: Eric DE MAULDE eric...@free.fr
Hi

maincss.css file is into the webapp flatgrey
So its relative path is /flatgrey/maincss.css

But a lot of files include a wrong relative path :
${baseUrl}/images/maincss.css

Files are :
OrderNoticeEmail.ftl
ContactListVerifyEmail.ftl
/ecommerce/blog/main.ftl
webpos/widget/CommonScreens.xml
...


Is there an error ?
Have I to create a patch ?

Eric

[jira] Commented: (OFBIZ-2832) css layout issue IE8

2009-09-04 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12751492#action_12751492
 ] 

Ryan Foster commented on OFBIZ-2832:


We need to fix the issues.  Believe it or not, it is possible to code a layout 
that works in IE6/IE7/IE8, Firefox, and Safari without any sort of crazy CSS 
hacks or Javascript.  I've done it many, many times, and so have most of you.  
The frontend OOTB Ecommerce component layout needs an overhaul.  The OOTB 
layout has not changed in years.  We need to present a layout OOTB that 
reflects todays web standards and techniques.  Do that, and IE will fall in 
line.

 css layout issue IE8
 

 Key: OFBIZ-2832
 URL: https://issues.apache.org/jira/browse/OFBIZ-2832
 Project: OFBiz
  Issue Type: Bug
  Components: ALL COMPONENTS
Affects Versions: Release Branch 9.04, SVN trunk
 Environment: IE8
Reporter: chris snow
 Attachments: Screenshot-1.png, Screenshot.png


 main section is positioned under last box on the left hand column.
 see screenshot(s)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2592) BizznessTime Theme : Displayed text is not clear.

2009-06-11 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718569#action_12718569
 ] 

Ryan Foster commented on OFBIZ-2592:


Look at you already flexing your new design skills.  Thanks for the catch and 
fix on that.

  BizznessTime Theme :  Displayed text is not clear.
 ---

 Key: OFBIZ-2592
 URL: https://issues.apache.org/jira/browse/OFBIZ-2592
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Affects Versions: SVN trunk
Reporter: Sumit Pandit
Priority: Minor
 Attachments: Picture 1.png, Picture 2.png, style_css.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Use Prototype or JQuery for Ajax goodies

2009-06-03 Thread Ryan Foster

Jquery and Prototype can and do live relatively easily along side each  
other...

http://docs.jquery.com/Using_jQuery_with_Other_Libraries

As for what to maintain in the trunk, I would like to offer option C:  
none of the above, but rather suggest using the Google JS API to load  
in the library of the users choosing:


http://code.google.com/apis/ajaxlibs/

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Jun 3, 2009, at 12:19 AM, Raj Saini wrote:


Hi Ashish,
Raj, Thanks for sharing your thoughts on this. I haven't looked too  
much

details about JQuery.
What about your vote? Which one is good to become part of OFBiz trunk
Prototype or JQuery ?

--
Ashish


I would like go with JQuery as it is light weight, modular and  
feature rich. Dojo is good but some time it is a overkill. I have  
not worked much with Prototype though.


Thanks,

Raj

Re: Use Prototype or JQuery for Ajax goodies

2009-06-03 Thread Ryan Foster


Jacopo,

The Google API works by calling the available library from Google,  
rather than from your instance of OFBiz.  So rather that including  
javascript like OFBiz current does, instead it would pull in the  
library in this method:


script src=http://www.google.com/jsapi; type=text/javascript/ 
script
script type=text/javascriptgoogle.load(prototype, 1.6.0.3);/ 
script
script type=text/javascriptgoogle.load(scriptaculous, 1.8.2);/ 
script


You would simply substitute prototype and scriptaculous with jquery  
(or dojo or mootools, depending on your preference).


There are several advantages to this approach, with one big  
disadvantage, which you alluded to:


PRO: It taps into Google's existing server network, with the JS being  
served up by the server that is closest to you, which in many cases  
may allow the library to load faster.
PRO: If the user previously visited a site that was also using the  
Google API, then the library would simply be loaded in for the users  
cache instead of the server, making the load time tremendously faster
PRO: No need to maintain the library in the trunk.  As a new version  
is released and becomes available from the Google API, you simply  
update the version number.
PRO: Availability of all major Javascript Frameworks. Dojo, Mootools,  
Prototype/Scriptaculous, and YUI are supported.


CON: Lack of availability if the user does not have an internet  
connection.


That last one is obviously a big one, and may be a deal breaker since  
OFBiz instances in Internal LANs would not be able to use this  
option.  But maybe we could try a hybrid approach; try requesting the  
library from Google first, and if not available, request from the  
trunk.  Or, make it a configurable user option, allowing the user to  
turn the Google API feature on or off at install/implementation.



Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Jun 3, 2009, at 2:22 AM, Jacopo Cappellato wrote:


Hi Ryan,

this is interesting, and maybe I didn't fully get how Google JS API  
works, but what about OFBiz instances that are in internal lan with  
no access to the Internet? What about the license?


Cheers,

Jacopo

On Jun 3, 2009, at 9:02 AM, Ryan Foster wrote:

Jquery and Prototype can and do live relatively easily along side  
each other...

http://docs.jquery.com/Using_jQuery_with_Other_Libraries

As for what to maintain in the trunk, I would like to offer option  
C: none of the above, but rather suggest using the Google JS API to  
load in the library of the users choosing:


http://code.google.com/apis/ajaxlibs/

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On Jun 3, 2009, at 12:19 AM, Raj Saini wrote:


Hi Ashish,
Raj, Thanks for sharing your thoughts on this. I haven't looked  
too much

details about JQuery.
What about your vote? Which one is good to become part of OFBiz  
trunk

Prototype or JQuery ?

--
Ashish


I would like go with JQuery as it is light weight, modular and  
feature rich. Dojo is good but some time it is a overkill. I have  
not worked much with Prototype though.


Thanks,

Raj

[jira] Created: (OFBIZ-2543) Multiple DOCTYPE in rendered HTML

2009-05-28 Thread Ryan Foster (JIRA)

Multiple DOCTYPE in rendered HTML
-

 Key: OFBIZ-2543
 URL: https://issues.apache.org/jira/browse/OFBIZ-2543
 Project: OFBiz
  Issue Type: Bug
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
Priority: Minor
 Attachments: Picture 1.JPG, Picture 2.JPG, Picture 3.JPG

The XHTML Transitional DOCTYPE is being duplicated for each screen definition 
when each view is rendered in HTML.

Looked into this a bit and it looks like the  !DOCTYPE html PUBLIC 
-//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; DOCTYPE declaration 
is being called in multiple files:

1. In HtmlScreenRenderer.java at line 75
2. In htmlScreenMacroLibrary.ftl at line 21
3. In headerHead.ftl at line 19 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2543) Multiple DOCTYPE in rendered HTML

2009-05-28 Thread Ryan Foster (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2543:
---

Attachment: Picture 3.JPG
Picture 2.JPG
Picture 1.JPG

Screenshots of rendered source code for ecommerce/control/main view

 Multiple DOCTYPE in rendered HTML
 -

 Key: OFBIZ-2543
 URL: https://issues.apache.org/jira/browse/OFBIZ-2543
 Project: OFBiz
  Issue Type: Bug
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
Priority: Minor
 Attachments: Picture 1.JPG, Picture 2.JPG, Picture 3.JPG


 The XHTML Transitional DOCTYPE is being duplicated for each screen definition 
 when each view is rendered in HTML.
 Looked into this a bit and it looks like the  !DOCTYPE html PUBLIC 
 -//W3C//DTD XHTML 1.0 Transitional//EN 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; DOCTYPE 
 declaration is being called in multiple files:
 1. In HtmlScreenRenderer.java at line 75
 2. In htmlScreenMacroLibrary.ftl at line 21
 3. In headerHead.ftl at line 19 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2543) Multiple DOCTYPE in rendered HTML

2009-05-28 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12714119#action_12714119
 ] 

Ryan Foster commented on OFBIZ-2543:


That makes sense to me, but why do we have a function in 
HtmlScreenRenderer.java that reads:

public void renderScreenBegin(Appendable writer, MapString, Object context) 
throws IOException {
writer.append(!DOCTYPE html PUBLIC \-//W3C//DTD XHTML 1.0 
Transitional//EN\ 
\http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\;);
appendWhitespace(writer);
}

and then in htmlScreenMacroLibrary.ftl we have:

#macro renderScreenBegin
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
/#macro

If the function is already writing it in, then why are we also calling it 
inside the function that should be writing it in already?  Shouldn't it be one 
or the other?

 Multiple DOCTYPE in rendered HTML
 -

 Key: OFBIZ-2543
 URL: https://issues.apache.org/jira/browse/OFBIZ-2543
 Project: OFBiz
  Issue Type: Bug
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
Assignee: Anil K Patel
Priority: Minor
 Attachments: Picture 1.JPG, Picture 2.JPG, Picture 3.JPG


 The XHTML Transitional DOCTYPE is being duplicated for each screen definition 
 when each view is rendered in HTML.
 Looked into this a bit and it looks like the  !DOCTYPE html PUBLIC 
 -//W3C//DTD XHTML 1.0 Transitional//EN 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; DOCTYPE 
 declaration is being called in multiple files:
 1. In HtmlScreenRenderer.java at line 75
 2. In htmlScreenMacroLibrary.ftl at line 21
 3. In headerHead.ftl at line 19 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2469) CSS fixes for Linux + Firefox 3

2009-05-17 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12710266#action_12710266
 ] 

Ryan Foster commented on OFBIZ-2469:


Shi,

If you are gong to modify widths on the 4 input fields referenced above (or any 
input fields for that matter)...

1. Don't use the size attribute as in  input 
type=textname=SEARCH_STRING size=20...
2. Don't use an inline style width either, as in style=width:173px;...

Having an inline size and width is redundant, and size will render 
differently in different browsers.  You are much better off assigning the input 
field a class name and then setting the width in an external style sheet.  That 
way, you can adjust the width on a per browser basis if you need to.  Using an 
inline style on the examples above makes it impossible to adjust the width 
using of those fields using CSS, because an inline style will always trump an 
ID or Class name.  


 CSS fixes for Linux + Firefox 3
 ---

 Key: OFBIZ-2469
 URL: https://issues.apache.org/jira/browse/OFBIZ-2469
 Project: OFBiz
  Issue Type: Improvement
Affects Versions: Release Branch 9.04
 Environment: OFBiz 9.0.4 + Fedora 10 + Firefox 3 + Chinese Language + 
 OpenJDK 1.6.0
Reporter: Shi Yusen
Priority: Trivial
 Attachments: catalog09.04-Fedora10-FF3.png, 
 ecommerce09.04-Fedora10-FF3.png, OFBIZ-2469-20090513.patch


 1. themes/smoothfeather/webapp/smoothfeather/css/forms.css
 add white-space: nowrap; to 
 .label {
   margin:0;
   padding:0;
   font-size:11px;
   line-height:10px;
 }
 URL to see the improvement: 
 /myportal/control/showPortalPage?portalPageId=MYPORTAL_EMPLOYEE1parentPortalPageId=MYPORTAL_EMPLOYEE
 2. applications/product/webapp/catalog/find/keywordsearchbox.ftl
 Change 
 span class=label${uiLabelMap.ProductKeywords}:/spaninput 
 type=textname=SEARCH_STRING size=20 maxlength=50 
 value=${requestParameters.SEARCH_STRING?if_exists}/
 to
 span class=label${uiLabelMap.ProductKeywords}:/spaninput 
 type=textname=SEARCH_STRING size=20 maxlength=50 
 value=${requestParameters.SEARCH_STRING?if_exists} style=width:173px;/
 3. applications/order/webapp/ordermgr/entry/catalog/keywordsearchbox.ftl
 Change 
 input type=text name=SEARCH_STRING size=14 maxlength=50 
 value=${requestParameters.SEARCH_STRING?if_exists}/
 to
 input type=text name=SEARCH_STRING size=14 maxlength=50 
 value=${requestParameters.SEARCH_STRING?if_exists} style=width:135px;/
 4. 
 specialpurpose/ecommerce/webapp/ecommerce/customer/miniSignUpForContactList.ftl
 Change 
 input size=20 maxlength=255 name=email class=inputBox value= 
 type=text
 to 
 input size=20 maxlength=255 name=email class=inputBox value= 
 type=text style=width:135px;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Plan on deprecating old themes

2009-05-07 Thread Ryan Foster

I am aware that it will be dropped, and I welcome it. +1 as well for  
dropping it from the Confluence page.  I would prefer if people did  
not remember my mistakes, or have an easy place to reference them :)


Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On May 7, 2009, at 5:29 PM, Jacques Le Roux wrote:

Ryan clearly expressed that BizznesTIme is a replacement for  
SmoothFeather which should be dropped, or did I miss something ?  
Will Ryan be aware of it there ?


Jacques

From: Tim Ruppert tim.rupp...@hotwaxmedia.com

+1

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

- Adrian Crum adri...@hlmksw.com wrote:


At the same time, we don't want to offend the author. If the author
wants to remove it from the web page, then he/she is free to do so.

-Adrian

Jacques Le Roux wrote:
 I think we should not bother to have it in the Visual Themes  
gallery

and
 simply drop and forget it. BizznessTime replaced it and is
apparently
 the same. Thus we will not end up with an user not aware willing  
to

use
 it as fundation.

 Jacques

 From: Tim Ruppert tim.rupp...@hotwaxmedia.com
 Apparently I can commit there :) This has been removed and is
posted
 on the page.  Thanks to everyone for helping out figure our
 deprecation path here.

 Cheers,
 Tim
 --  Tim Ruppert
 HotWax Media
 http://www.hotwaxmedia.com

 o:801.649.6594
 f:801.649.6595

 - Tim Ruppert tim.rupp...@hotwaxmedia.com wrote:

 Smooth Feather has been posted to the Visual Themes page and can
now
 be removed by anyone who has rights.  I'm not sure where I ever
 rememthemes is classified, but I'll give it a whirl and will
report
 back.

 Cheers,
 Tim
 --  Tim Ruppert
 HotWax Media
 http://www.hotwaxmedia.com

 o:801.649.6594
 f:801.649.6595

 - Tim Ruppert tim.rupp...@hotwaxmedia.com wrote:

  Yeah, I can get behind that for sure.  Btw, Jacques, I think  
we

 keep
  the Flat Grey forever - no reason to deprecate that one - just
the
  ones that aren't going to be maintained - of which the  
original

 Smooth
  Feather now stands out.
 
  Anyways, if everyone's cool with that - then we can make a  
page

in
  Confluence and keep everything there - starting with moving
Smooth
  Feather there.
 
  Cheers,
  Tim
  --
  Tim Ruppert
  HotWax Media
  http://www.hotwaxmedia.com
 
  o:801.649.6594
  f:801.649.6595
 
  - Adrian Crum adri...@hlmksw.com wrote:
 
   I like the idea of moving deprecated themes to a web page.
  
   -Adrian
  
   Jacques Le Roux wrote:
For several reason, I really appreciate sometimes to have
the
  good
   old
theme (Flat Grey) at hand.
We could keep Flat Grey and the best known at the moment
  (obviously
  
BiznessTime at the moment).
The others would stay at http://docs.ofbiz.org/x/yhQ
This would be an easy deprecation policy
   
Jacques
   
From: Adrian Crum adri...@hlmksw.com
There were differing opinions about them. I suggested
having
  only
   one
theme in OFBiz, and the other themes could be provided
outside
  the
  
project - by theme providers.
   
David thought it would be good to have several themes in
the
   project
in order to demonstrate the theme idea.
   
From my perspective, having more than one theme in the
project
   means
that much more code that has to be maintained.
   
As far as I know, no theme deprecation plan has been
  discussed.
   
-Adrian
   
   
Tim Ruppert wrote:
I may have missed this in general, but what is the plan
to
   deprecate
themes when people aren't supporting them any longer?
We've
   already
got one that we want to do this to - and there will  
surely

be
   others
as we're trying to work out these backend interfaces.
 Anyways,
  my
  
vote would be community votes and just removing them -
but
 I'd
   love
to hear what the original intention was and other good
ideas
  out
   there.
   
Cheers,
Tim
--Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
   
o:801.649.6594
f:801.649.6595

Re: Plan on deprecating old themes

2009-05-07 Thread Ryan Foster


Just playing devil's advocate here...

As we go down the road and more people in the community develop  
frontend and backend themes (which may eventually begin to happen as  
more people catch on to the theming feature), how do we determine what  
gets included in the trunk?  Do we include every theme that is  
developed? Do we include only include a certain number?  In you look  
at a project like Wordpress for example, there are literally thousands  
of free and commercial themes that have been developed, but Wordpress  
only comes with 2 basic themes OOTB.


Just something to think about.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On May 7, 2009, at 5:36 PM, Tim Ruppert wrote:

Fair - you know me ... lean and mean - I did get a little caught up  
in the cleanup.  No reason to flush the Bluelight theme.


Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

- David E Jones david.jo...@hotwaxmedia.com wrote:


No! Definitely not. Bluelight is quite different from BizznessTime/
SmoothFeather.

Let's not get lost in all this... the ONLY reason there was even a
discussion about deprecating/removing themes is because the
BizznessTime theme was added instead of updating the SmoothFeather
theme, even though it is really just a big update to the  
SmoothFeather


theme and so represents a replacement for it.

-David


On May 7, 2009, at 4:56 PM, Adrian Crum wrote:


Should we do the same for Bluelight?

-Adrian

Tim Ruppert wrote:

Smooth Feather has been posted to the Visual Themes page and can
now be removed by anyone who has rights.  I'm not sure where I ever



rememthemes is classified, but I'll give it a whirl and will report



back.
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
- Tim Ruppert tim.rupp...@hotwaxmedia.com wrote:

Yeah, I can get behind that for sure.  Btw, Jacques, I think we

keep

the Flat Grey forever - no reason to deprecate that one - just

the

ones that aren't going to be maintained - of which the original
Smooth
Feather now stands out.
Anyways, if everyone's cool with that - then we can make a page

in

Confluence and keep everything there - starting with moving

Smooth

Feather there.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

- Adrian Crum adri...@hlmksw.com wrote:


I like the idea of moving deprecated themes to a web page.

-Adrian

Jacques Le Roux wrote:

For several reason, I really appreciate sometimes to have the

good

old

theme (Flat Grey) at hand.
We could keep Flat Grey and the best known at the moment

(obviously

BiznessTime at the moment).
The others would stay at http://docs.ofbiz.org/x/yhQ
This would be an easy deprecation policy

Jacques

From: Adrian Crum adri...@hlmksw.com

There were differing opinions about them. I suggested having

only

one

theme in OFBiz, and the other themes could be provided outside

the

project - by theme providers.

David thought it would be good to have several themes in the

project

in order to demonstrate the theme idea.

From my perspective, having more than one theme in the project

means

that much more code that has to be maintained.

As far as I know, no theme deprecation plan has been

discussed.

-Adrian


Tim Ruppert wrote:

I may have missed this in general, but what is the plan to

deprecate

themes when people aren't supporting them any longer?  We've

already

got one that we want to do this to - and there will surely be

others

as we're trying to work out these backend interfaces.

Anyways,

my

vote would be community votes and just removing them - but

I'd

love

to hear what the original intention was and other good ideas

out

there.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

Re: svn commit: r771170 - /ofbiz/trunk/framework/common/data/CommonTypeData.xml

2009-05-05 Thread Ryan Foster

I think we should probably remove the Smoothfeather theme altogether,  
since it is being replaced the the Bizznesstime theme, or replace all  
of the Smoothfeather theme data/code with Bizznesstime.  That should  
alleviate  some confusion since the look and feel of both themes is  
exactly the same.


Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On May 5, 2009, at 7:39 PM, Hans Bakker wrote:


do you see a BIZZNESS_TIME in VisualThemeResource entity?
sorry i do not see that.

there is a SMOOTH_FEATHER themehowever i still think not usable  
yet.

examples:

myportal - timesheet
the screen is much to wide

party - partylist
1. the partyId is not not always clickable in firefox
2. the function keys are listed vertically

party - profile
The info blocks are not clearly separated

Regards,
Hans

On Mon, 2009-05-04 at 21:05 -0700, Adrian Crum wrote:
--- On Mon, 5/4/09, Hans Bakker mailingl...@antwebsystems.com  
wrote:

At least when i have this change in, after a
clean-all;run-install the
system cannot find ANY theme Try it yourself.


I've done that twice on two different computers. Still no problems.  
The theme works fine.


-Adrian





--
Antwebsystems.com: Quality OFBiz services for competitive rates

Re: svn commit: r770998 - in /ofbiz/branches/release09.04: ./ themes/bizznesstime/ themes/bizznesstime/data/ themes/bizznesstime/includes/ themes/bizznesstime/webapp/ themes/bizznesstime/webapp/bizzne

2009-05-03 Thread Ryan Foster

Initially, it started out as a bug fix.  We began by simply trying to  
fix all of the issues with Smoothfeather that were listed in various  
JIRA issues, but as we went along it became more and more apparent  
that although the design was good, the original markup was not.  We  
ended up having to touch so many files that it became much easier to  
simply start fresh rather than have a patch that was 2000 lines long,  
or a series of patches that were cumbersome and confusing to manage.   
So in summary:


Was a bug fix...
Now a new feature.

Ryan Foster
HotWax Media
801.671.0769
ryan.fos...@hotwaxmedia.com




On May 3, 2009, at 3:51 AM, Adrian Crum wrote:



From what I understand, the Smoothfeather theme is broken, and  
instead of fixing it, it is being replaced by a new theme. If that's  
the case, and the new theme is the default and the one that will be  
maintained, then we should probably make that change in the release  
too.


Yes, it looks like a new feature. But from another perspective it  
could be a bug fix.


-Adrian


--- On Sat, 5/2/09, David E Jones david.jo...@hotwaxmedia.com wrote:


From: David E Jones david.jo...@hotwaxmedia.com
Subject: Re: svn commit: r770998 - in /ofbiz/branches/ 
release09.04: ./ themes/bizznesstime/ themes/bizznesstime/data/  
themes/bizznesstime/includes/ themes/bizznesstime/webapp/ themes/ 
bizznesstime/webapp/bizznesstime/ themes/bizznesstime/webapp/ 
bizznesstime/WEB-INF/...

To: dev@ofbiz.apache.org
Date: Saturday, May 2, 2009, 8:50 PM
This looks a lot more like a new feature than a bug fix to
me.

I think Jacques is clearly voting for it being a bug fix.

Does anyone else have a vote/opinion?

-David


On May 2, 2009, at 5:37 PM, jler...@apache.org wrote:


Author: jleroux
Date: Sat May  2 23:08:44 2009
New Revision: 770998

URL:

http://svn.apache.org/viewvc?rev=770998view=rev

Log:
Applied fix from trunk for revision: 770997







r770997 | jleroux | 2009-05-03 01:05:29 +0200 (dim.,

03 mai 2009) | 1 line


New BizznessTime Theme which should be soon replacing

SmoothFeather. Please test, report and see more at
https://issues.apache.org/jira/browse/OFBIZ-2398







Added:
  ofbiz/branches/release09.04/themes/bizznesstime/
- copied from r770997,

ofbiz/trunk/themes/bizznesstime/



ofbiz/branches/release09.04/themes/bizznesstime/data/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/data/


ofbiz/branches/release09.04/themes/bizznesstime/data/ 
bizznessTimeThemeData.xml

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/data/bizznessTimeThemeData.xml



ofbiz/branches/release09.04/themes/bizznesstime/includes/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/includes/



ofbiz/branches/release09.04/themes/bizznesstime/includes/appbar.ftl

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/includes/appbar.ftl



ofbiz/branches/release09.04/themes/bizznesstime/includes/footer.ftl

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/includes/footer.ftl



ofbiz/branches/release09.04/themes/bizznesstime/includes/header.ftl

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/includes/header.ftl



ofbiz/branches/release09.04/themes/bizznesstime/includes/messages.ftl

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/includes/messages.ftl


ofbiz/branches/release09.04/themes/bizznesstime/includes/secondary- 
appbar.ftl

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/includes/secondary-appbar.ftl



ofbiz/branches/release09.04/themes/bizznesstime/ofbiz-component.xml

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/ofbiz-component.xml



ofbiz/branches/release09.04/themes/bizznesstime/webapp/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/



ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/bizznesstime/


ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/ 
WEB-INF/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/bizznesstime/WEB-INF/


ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/ 
WEB-INF/web.xml

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/bizznesstime/WEB-INF/web.xml


ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/ 
css/

- copied from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/bizznesstime/css/


ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/ 
css/forms.css

- copied unchanged from r770997,

ofbiz/trunk/themes/bizznesstime/webapp/bizznesstime/css/forms.css


ofbiz/branches/release09.04/themes/bizznesstime/webapp/bizznesstime/ 
css/ie.css

- copied unchanged from r770997,

ofbiz/trunk

[jira] Commented: (OFBIZ-2308) New smoothfeather style Business Area enhancement

2009-05-01 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705141#action_12705141
 ] 

Ryan Foster commented on OFBIZ-2308:


You are absolutely right.  It is annoying, and a little clumsy.  I'll get that 
fixed so that one drop down cancels out the other.  I think it might also help 
to add in a timeout feature as well so that if you do nothing at all, the 
dropdown automatically blinds back up after a set period of time.

 New  smoothfeather style Business Area enhancement
 

 Key: OFBIZ-2308
 URL: https://issues.apache.org/jira/browse/OFBIZ-2308
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Jacques Le Roux
 Fix For: SVN trunk


 We could have a title for each column of Business Area. Something like Main 
 applications Secondary applications, maybe 2 colors also ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (OFBIZ-2398) BizznessTime Theme

BizznessTime Theme
--

 Key: OFBIZ-2398
 URL: https://issues.apache.org/jira/browse/OFBIZ-2398
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
 Fix For: SVN trunk


This new theme, codename: It's Bizzness Time, addresses most if not all major 
identified issues with the new Smoothfeather theme.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2398) BizznessTime Theme


[ 
https://issues.apache.org/jira/browse/OFBIZ-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704863#action_12704863
 ] 

Ryan Foster commented on OFBIZ-2398:


This theme is identical to the Smoothfeather theme in look and feel.  However, 
the markup, stylesheets, and functions in the original Smoothfeather theme 
required a significant overhaul in order to give it the best foundation to be 
flexible enough to support all browsers.  Therefore, it was nearly impossible 
to simply patch the Smoothfeather theme.  The patch would end up being as large 
as the new theme, and a whole lot more complicated.  This revised theme 
addresses OFBIZ-2309, as well as issues linked to OFBIZ-2309.

 BizznessTime Theme
 --

 Key: OFBIZ-2398
 URL: https://issues.apache.org/jira/browse/OFBIZ-2398
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
 Fix For: SVN trunk


 This new theme, codename: It's Bizzness Time, addresses most if not all major 
 identified issues with the new Smoothfeather theme.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2398) BizznessTime Theme


[ 
https://issues.apache.org/jira/browse/OFBIZ-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704864#action_12704864
 ] 

Ryan Foster commented on OFBIZ-2398:


I knew you would appreciate that one Scott :)

 BizznessTime Theme
 --

 Key: OFBIZ-2398
 URL: https://issues.apache.org/jira/browse/OFBIZ-2398
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
 Fix For: SVN trunk


 This new theme, codename: It's Bizzness Time, addresses most if not all major 
 identified issues with the new Smoothfeather theme.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2398) BizznessTime Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2398:
---

Attachment: bizznesstime.zip

 BizznessTime Theme
 --

 Key: OFBIZ-2398
 URL: https://issues.apache.org/jira/browse/OFBIZ-2398
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
 Fix For: SVN trunk

 Attachments: bizznesstime.zip


 This new theme, codename: It's Bizzness Time, addresses most if not all major 
 identified issues with the new Smoothfeather theme.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2398) BizznessTime Theme


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2398:
---

Attachment: BizznessTime.patch

This patch incorporates OFBIZ-2306 by adding internationalized (i18n) support 
for the Applications mega-dropdown, as well as OFBIZ-2308, which adds 
Primary Apps and Secondary Apps headings to business area with i18n support.

Patch also makes new Bizznesstime theme the default theme, adds an Identifier 
to the leftbar screen definition, and cleans up the BI and Webtools application 
dashboards.

 BizznessTime Theme
 --

 Key: OFBIZ-2398
 URL: https://issues.apache.org/jira/browse/OFBIZ-2398
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Ryan Foster
 Fix For: SVN trunk

 Attachments: BizznessTime.patch, bizznesstime.zip


 This new theme, codename: It's Bizzness Time, addresses most if not all major 
 identified issues with the new Smoothfeather theme.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2341) The pages should be strechtable

2009-04-23 Thread Ryan Foster (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702148#action_12702148
 ] 

Ryan Foster commented on OFBIZ-2341:


Sorry, what I mean to say is that docs.ofbiz.org has been skinned using the 
same look and feel as the new ofbiz.apache.org.  This layout is a fixed-width 
pixel layout, so pages cannot stretch beyond their current width dimensions.  
To make pages stretchable would require a new design for the site that was 
designed to be flexible.

To solve the issue with wider code blocks, we have put an overflow:auto on all 
code and pre tags, so that you can scroll code blocks that are wider than 
the page container, and the code block doesn't break the layout.  That seems to 
be a pretty good solution so far.

 The pages should be strechtable
 ---

 Key: OFBIZ-2341
 URL: https://issues.apache.org/jira/browse/OFBIZ-2341
 Project: OFBiz
  Issue Type: Sub-task
Reporter: Jacques Le Roux

 Pages in the doc should be able to strecht. Sometimes you need a wider table 
 or \{code} block, etc.
 For instance look what happens at the [Creating Practice Application (hello 
 world) 
 page|http://docs.ofbiz.org/display/OFBIZ/OFBiz+Beginners+Development+Guide+Using+Practice+Application+(helloworld)].
  This page is a reference and often used...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2288) Update the image / content scroller on index.html


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2288:
---

Attachment: Archive.zip
indexUpdate.patch

I swear, I have the hardest time with patches.  I can never seem to get them 
right.  I checked out the repo at ttp://svn.apache.org/repos/asf/ofbiz/site 
from SVN this morning, so I don't see how I could be out of date.  It's 
probably true this patch is undoing some resent changes, but if it is anything 
related to layout and file structure, it was probably coded by me in the first 
place, and it didn't work :), so this should be an improvement.  At any rate, I 
ran an update and created a new patch.  As for the images, I made 4 additions, 
and 4 modifications.  Only the following 8 files are in the attached archive.

A  images/full-wrapper.jpg
A  images/pause.gif
A  images/start.gif
A  images/footer.jpg
M  images/wrapper.jpg
M  images/home-wrapper.jpg
M  images/header-bg.jpg
M  images/slideshow-bg.jpg


 Update the image / content scroller on index.html
 -

 Key: OFBIZ-2288
 URL: https://issues.apache.org/jira/browse/OFBIZ-2288
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Affects Versions: SVN trunk
Reporter: Tim Ruppert
Assignee: Tim Ruppert
 Fix For: SVN trunk

 Attachments: Archive.zip, images.zip, index.patch, indexUpdate.patch, 
 ofbizSiteTemplate.zip


 Currently there is a JavaScript scroller on the index.html page, but it's not 
 clear to everyone that it is there.  Let's do this:
 1. Make it so that they scroll ever 10 seconds between what is there.
 2. Put a pause on it - which will stop the scrolling, but allow you to start 
 it up again.
 3. Make it so what comes up first is totally random
 4. Make it so it scrolls around to the beginning again instead of stopping at 
 the last one (in either direction)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2288) Update the image / content scroller on index.html

[
https://issues.apache.org/jira/browse/OFBIZ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701167#action_12701167
]

Ryan Foster commented on OFBIZ-2288:

It's just a name for a zip file. On Mac in finder, if you select multiple
files, right click and choose Compress these files, it automatically names
the compressed file Archive.zip.

What Tim is saying seems to make sense. I know that I was working directly on
an up to date copy from the repository, and that the changes I made were not
massive. All that was done really was removing a couple of divs, adding a
little snippet of javascript code, and shuffled the footer.

The additional pages that were added don't need to be in this patch for sure.
That should simply things quite a bit. One thing that I am realizing in this
process is that a patch should be more singular in nature, as in, if I submit a
patch for the homepage, it should just contain the homepage and any related
files, not a bunch of extra pages, etc. Thanks for the feedback, all of you.

Update the image / content scroller on index.html
-

Key: OFBIZ-2288
URL: https://issues.apache.org/jira/browse/OFBIZ-2288
Project: OFBiz
Issue Type: Improvement
Components: site
Affects Versions: SVN trunk
Reporter: Tim Ruppert
Assignee: Tim Ruppert
Fix For: SVN trunk

Attachments: Archive.zip, images.zip, index.patch, indexUpdate.patch,
ofbizSiteTemplate.zip

Currently there is a JavaScript scroller on the index.html page, but it's not
clear to everyone that it is there. Let's do this:
1. Make it so that they scroll ever 10 seconds between what is there.
2. Put a pause on it - which will stop the scrolling, but allow you to start
it up again.
3. Make it so what comes up first is totally random
4. Make it so it scrolls around to the beginning again instead of stopping at
the last one (in either direction)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2288) Update the image / content scroller on index.html

[
https://issues.apache.org/jira/browse/OFBIZ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ryan Foster updated OFBIZ-2288:
---

Attachment: indexScroller.patch

Archive.zip attached with the modified and added images. This is the updated
patch file with the minimum contents to make the scroller work as requested.
Here is an explanation of what you'll see in this file ('ll follow up with a
comment on the full steps to install shortly and hopefully if I've done
something incorrectly, you'll let me know):

1. delete css/home.css
-- Not needed

2. Update much of global.css
-- This may seem excessive, but trust me it's needed.
-- This fixed a number of the container issues that were present before.
-- Added in the license header.
-- Brought in necessary stuff from home.css.
-- Added comments
-- Almost ready as a style guide for this look and feel.

3. index.html
-- Updated container structure to allow the footer to anchor to the bottom.
-- Updated the search to remove inline styling and added id for search hint.

4. Added slides.js

5. Removed fieldhints.js, pngFix.js, slideshow.js and global.js
-- They were no longer needed.

Update the image / content scroller on index.html
-

Attachments: Archive.zip, indexScroller.patch

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2288) Update the image / content scroller on index.html


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2288:
---

Attachment: Archive.zip

Updated archive to remove the funky Mac files that often come inside of 
Archives :)

 Update the image / content scroller on index.html
 -

 Key: OFBIZ-2288
 URL: https://issues.apache.org/jira/browse/OFBIZ-2288
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Affects Versions: SVN trunk
Reporter: Tim Ruppert
Assignee: Tim Ruppert
 Fix For: SVN trunk

 Attachments: Archive.zip, Archive.zip, indexScroller.patch


 Currently there is a JavaScript scroller on the index.html page, but it's not 
 clear to everyone that it is there.  Let's do this:
 1. Make it so that they scroll ever 10 seconds between what is there.
 2. Put a pause on it - which will stop the scrolling, but allow you to start 
 it up again.
 3. Make it so what comes up first is totally random
 4. Make it so it scrolls around to the beginning again instead of stopping at 
 the last one (in either direction)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (OFBIZ-2288) Update the image / content scroller on index.html


[ 
https://issues.apache.org/jira/browse/OFBIZ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701282#action_12701282
 ] 

Ryan Foster commented on OFBIZ-2288:


Steps for installing this patch:

1. Download patch 
2. Download Archive.zip
3. patch -p0  indexScroller.patch
4. cd images
5. unzip Archive.zip
6. cd ../
7. svn delete --force css/home.css js/fieldhints.js js/pngFix.js js/global.js 
js/slideshow.js 
-- Not sure why the patch didn't delete them, but this will do it.
8. svn add images/full-wrapper.jpg images/pause.gif images/start.gif 
images/footer.jpg js/slides.js 

That should do it - then this can be committed.  Thanks everyone.

 Update the image / content scroller on index.html
 -

 Key: OFBIZ-2288
 URL: https://issues.apache.org/jira/browse/OFBIZ-2288
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Affects Versions: SVN trunk
Reporter: Tim Ruppert
Assignee: Tim Ruppert
 Fix For: SVN trunk

 Attachments: Archive.zip, Archive.zip, indexScroller.patch


 Currently there is a JavaScript scroller on the index.html page, but it's not 
 clear to everyone that it is there.  Let's do this:
 1. Make it so that they scroll ever 10 seconds between what is there.
 2. Put a pause on it - which will stop the scrolling, but allow you to start 
 it up again.
 3. Make it so what comes up first is totally random
 4. Make it so it scrolls around to the beginning again instead of stopping at 
 the last one (in either direction)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (OFBIZ-2334) Move feature list on homepage to a more prominent location

Move feature list on homepage to a more prominent location
--

 Key: OFBIZ-2334
 URL: https://issues.apache.org/jira/browse/OFBIZ-2334
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Affects Versions: SVN trunk
Reporter: Ryan Foster
Priority: Minor
 Fix For: SVN trunk


While putting together the style guide, I moved the feature list that sites at 
the bottom of the What is Apache OFBiz? section to be a highlight inside of 
the section in order to make it stand out more.  I'll attach a patch and a 
picture so you can see the effect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2334) Move feature list on homepage to a more prominent location


 [ 
https://issues.apache.org/jira/browse/OFBIZ-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Foster updated OFBIZ-2334:
---

Attachment: featureHighlights.png
indexWithHighlights.patch

 Move feature list on homepage to a more prominent location
 --

 Key: OFBIZ-2334
 URL: https://issues.apache.org/jira/browse/OFBIZ-2334
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Affects Versions: SVN trunk
Reporter: Ryan Foster
Priority: Minor
 Fix For: SVN trunk

 Attachments: featureHighlights.png, indexWithHighlights.patch


 While putting together the style guide, I moved the feature list that sites 
 at the bottom of the What is Apache OFBiz? section to be a highlight 
 inside of the section in order to make it stand out more.  I'll attach a 
 patch and a picture so you can see the effect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (OFBIZ-2336) Add a style guide to ofbiz.apache.org so using styles are easier in the future