On Feb 26, 2007, at 1:05 AM, Jacopo Cappellato wrote:
David,
David E. Jones wrote:
...
On the issue of eventually removing these... even if we come up
with a good way of creating defaults in CSS (which I'm sure will
work out fine) I don't think we'll want to remove these. Cases
may, or
Comments inline...
--- Jacopo Cappellato <[EMAIL PROTECTED]> wrote:
> Chris,
>
> before we go too far with the implementation effort I think that we
> should refine the
> But again, I don't see this as a major improvement because:
>
> 1) it is a bit subjective to say if it easier for users to h
Chris,
before we go too far with the implementation effort I think that we
should refine the
But again, I don't see this as a major improvement because:
1) it is a bit subjective to say if it easier for users to have many
attributes in the form element or less attributes in a more complex
st
David,
David E. Jones wrote:
...
On the issue of eventually removing these... even if we come up with a
good way of creating defaults in CSS (which I'm sure will work out fine)
I don't think we'll want to remove these. Cases may, or are likely to,
arise where these will be of value.
-David
entence "unless you need a non specific style for the
> > single form"). So why not tackle this right now and create forms
> > sub-elements as Chris proposed ? For the moment, this is more a
> > question than a vote for... though a little inclination for...
> &
riginal Message -
From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 24, 2007 6:23 PM
Subject: Re: [RFC] Form Widget Stylings element || attribute
Chris,
I understand what you mean, but I don't know, I don't really have a
strong opinion
From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 24, 2007 6:23 PM
Subject: Re: [RFC] Form Widget Stylings element || attribute
> Chris,
>
> I understand what you mean, but I don't know, I don't really have a
> strong opinion on this so
From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 24, 2007 6:23 PM
Subject: Re: [RFC] Form Widget Stylings element || attribute
> Chris,
>
> I understand what you mean, but I don't know, I don't really have a
> strong opinion on this so
Chris,
I understand what you mean, but I don't know, I don't really have a
strong opinion on this so I'd like to get also feedback from others.
Jacopo
Chris Howe wrote:
Jacopo,
I completely agree with the direction or the refactoring and have no
doubt that the definitions in the project wil
Jacopo,
I completely agree with the direction or the refactoring and have no
doubt that the definitions in the project will benefit from leveraging
the technique that refactoring would support. But, when all the dust
settles on that refactoring, is it the goal to deprecate those 12
attributes fro
Chris,
Chris Howe wrote:
For me the one thing that is holding me back the most from using form
widgets more pervasively is that there are 40+ attributes for the form
element.
Request for comment:
1. Would the form widget be better off with moving the styling
attributes into a subelement as
I don't know the answer to that. I'm not arguing against your idea. On the
contrary, I think it's a great idea. Here's my vote:
+1
I guess I was just saying in the short term (after the patch is committed) you
won't have to specify as many things as before.
Chris Howe wrote:
Would OFBIZ-6
Would OFBIZ-671 eventually deprecate many of the attributes or simply
make for an additional option when defining the form definition?
I can certainly see OFBIZ-671 being a "best practice" of sorts, but the
current attributes would likely still be supported and the need for
organization would sti
We're on the same page. If you specify a form style element, that style could
style all of the elements contained in the form. Therefore most of those
elements you listed aren't needed.
Chris Howe wrote:
Just to make sure we're on the same page... These are the attributes
that I would like c
Just to make sure we're on the same page... These are the attributes
that I would like comment on moving into a element
form-title-area-style
form-widget-area-style
default-title-area-style
default-widget-area-style
default-title-style
default-widget-style
default-tooltip-style
default-required-f
+1
The same can be said for attributes:
- service-name, etc
- title-area-style, etc
- tooltip, header-link, etc
Although this would clutter the field element.
On Fri, 2007-02-23 at 16:05 -0800, Chris Howe wrote:
> For me the one thing that is holding me back the most fr
Chris,
I just refactored the form widget. Take a look:
https://issues.apache.org/jira/browse/OFBIZ-671
This will eliminate a lot of property assignments.
Chris Howe wrote:
For me the one thing that is holding me back the most from using form
widgets more pervasively is that there are 40+ at
For me the one thing that is holding me back the most from using form
widgets more pervasively is that there are 40+ attributes for the form
element.
Request for comment:
1. Would the form widget be better off with moving the styling
attributes into a subelement as opposed to being attributes
18 matches
Mail list logo
