I agree with Andy here.
But I think the tabstyles stuff needs to be clearly marked and separated
within the merged file. So if anyone wants to implement a new set there
is a clearly marked set of classes.
- Andrew
On Thu, 2007-01-11 at 08:15 -0800, Adrian Crum wrote:
> Andrew Zeneski wrote:
> >
Andrew Zeneski wrote:
I'm not too sure about combining all styles into one css file. Cleaning
them up surely would be a good thing, but tabstyles.css was designed to
handle the tab sections of screens. Only needed to be included in
screens which use the top level tabs.
That's not true. The
quot;Andrew Zeneski" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 11, 2007 7:08 AM
Subject: Re: CSS Layout and Other Cleanups in the Manager
Applications
> I'm not too sure about combining all styles into one css file.
> Cleaning them up surely would be a good thing, but t
that is a nice approach, +1
On 1/11/07, Jacques Le Roux <[EMAIL PROTECTED]> wrote:
I agree, +1
Jacques
- Original Message -
From: "Andrew Zeneski" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 11, 2007 7:08 AM
Subject: Re: CSS Layout and Other Cleanups in th
I agree, +1
Jacques
- Original Message -
From: "Andrew Zeneski" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 11, 2007 7:08 AM
Subject: Re: CSS Layout and Other Cleanups in the Manager Applications
> I'm not too sure about combining all styles into one css
One way to go about it is create a one stylesheet for each application
and let this stylesheet import other required stylesheets. This way only
one stylesheet will be linked into the web page.
Thanks,
Raj
Andrew Zeneski wrote:
I'm not too sure about combining all styles into one css file.
Cl
I'm not too sure about combining all styles into one css file.
Cleaning them up surely would be a good thing, but tabstyles.css was
designed to handle the tab sections of screens. Only needed to be
included in screens which use the top level tabs.
Keeping this separate IMO would make changi
I'd like to help with that effort. From my perspective, I see it happening kinda
like this:
1. Combine maincss.css and tabstyles.css files into one file.
2. Test css classes on a single component (what Jacopo is doing now), tweak css
class settings.
3. Once css class settings are finalized, go
I have a good start on cleaning up the backend to look just like the
existing site as an intermediate solution. I'll do my best to clean
it up a bit and get that out, but I'm swamped at the moment.
I had also identified a LARGE number of places where styles were
embedded in the code. This
Yeah, ecommerce has always been the highest priority in my mind but
improving styling and L&F in general on the back-end would also be
great.
-David
On Jan 3, 2007, at 1:05 PM, Adrian Crum wrote:
Thanks David.
I remember you mentioning some time ago your desire for the UI to
be "more
Thanks David.
I remember you mentioning some time ago your desire for the UI to be "more Zen
Garden-esque." More than likely you were referring to the eCommerce component,
but I don't see why the same can't be true for the rest of OFBiz. At the time
you suggested it, I pictured these two files
arker (for example, class="${class}", class="<#if ..."), but it
should catch most of them.
> CSS Layout and Other Cleanups in the Manager Applications
> -
>
> Key: OFBIZ-241
>
[
https://issues.apache.org/jira/browse/OFBIZ-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Eckard updated OFBIZ-241:
-
Attachment: style-info.txt
> CSS Layout and Other Cleanups in the Manager Applicati
On Jan 3, 2007, at 12:36 PM, Chris Howe wrote:
Having them separated allows the flexibility to use a
different style sheet if desired without needing to
assign properties for everything that the stylesheet
being replaced has declared for a particular class or
id.
All back end components utiliz
Having them separated allows the flexibility to use a
different style sheet if desired without needing to
assign properties for everything that the stylesheet
being replaced has declared for a particular class or
id.
All back end components utilize both because most were
developed by copying ano
Maintaining a single css file instead of two. All components reference both
files, so there's no sense to keep them separate.
Chris Howe wrote:
What benefit do you see in doing this?
--- Adrian Crum <[EMAIL PROTECTED]> wrote:
Jacopo,
While we're on the subject, could we also discuss
th
What benefit do you see in doing this?
--- Adrian Crum <[EMAIL PROTECTED]> wrote:
> Jacopo,
>
> While we're on the subject, could we also discuss
> the possibility of combining
> the maincss.css and tabstyles.css files into one
> file?
>
>
> Jacopo Cappellato wrote:
> > Following the great
This is a vague recollection of things read/done on
css. Instead of setting the font size in pixels, you
"should" use em units. The most common approach is
the following:
BODY {
font-size: 62.5%;
}
This makes 16px = 10px and so now:
0.8 em = 8 px
1 em = 10px
1.2 em = 12 px
1.4 em = 14 px
and so
Jacopo,
While we're on the subject, could we also discuss the possibility of combining
the maincss.css and tabstyles.css files into one file?
Jacopo Cappellato wrote:
Following the great advices in
https://issues.apache.org/jira/browse/OFBIZ-241 I've started to play
with the styles in mainc
Following the great advices in
https://issues.apache.org/jira/browse/OFBIZ-241 I've started to play
with the styles in maincss.css file and apply the mods to the
manufacturing application.
I've noticed some minor side effects (for example the texts in the main
webtools page are smaller now) a
I have no
real need to go to a higher standard of CSS yet until it is supported by more
browsers.
As soon as I get an SVN up and running well, I'll likely start working on this
anyways. Just let me know. [EMAIL PROTECTED
[ http://jira.undersunconsulting.com/browse/OFBIZ-202?page=all ]
David E. Jones closed OFBIZ-202:
Resolution: Duplicate
Fix Version: (was: 3.6.0)
This has been moved to the new Jira server.
> CSS Layout and Other Cleanups in the Mana
CSS Layout and Other Cleanups in the Manager Applications
-
Key: OFBIZ-241
URL: http://issues.apache.org/jira/browse/OFBIZ-241
Project: OFBiz (The Open for Business Project)
Issue Type
interest (ie outside of me...).
> CSS Layout and Other Cleanups in the Manager Applications
> -
>
> Key: OFBIZ-202
> URL: http://jira.undersunconsulting.com/browse/OFBIZ-202
> Project: [OFBiz] Open For Busin
Marco
> CSS Layout and Other Cleanups in the Manager Applications
> -
>
> Key: OFBIZ-202
> URL: http://jira.undersunconsulting.com/browse/OFBIZ-202
> Project: [OFBiz] Open For Business
>
25 matches
Mail list logo
