So what you are saying then is that I cannot write a UI widget that
uses a table without tweaking the CSS myself. I just don't understand
how that can be the goal of the jQuery UI CSS framework. I have built
an entire SQL report writer application using the jQuery UI, including
the UI layout plugin,  a UI feedback plugin that I wrote (that
conforms to the UI CSS framework) , and the jQuery Table drag and drop
plugin.  It looks great, works great (I love the jQuery UI CSS
approach), and the only thing I had to tweak was the table CSS.
Basically, you have to add one word to the CSS specs- like this   .ui-
widget, .ui-widget table { blah... } instead of .ui-widget { blah...
Hardly bloat. Are there a lot of other circumstances were there are
generic problems not covered by the framework? I haven't encountered
any.

There is lots of discussion in the future jQuery UI dev docs about the
need to be able to have more flexible styling of form elements, etc.
Why do these get included in the goal of the project, but something as
elementary as tables don't?

Thanks for your responses!

Duncan

On Jan 13, 5:42 am, Scott González <scott.gonza...@gmail.com> wrote:
> This is not the goal of the jQuery UI CSS Framework. If you want a CSS
> framework that will solve generic problems, there are other systems
> available, such as Reset CSS and Blueprint. The goal of the jQuery UI
> CSS Framework is to build a small framework for UI plugins to be built
> on top of and then provide styles, using that framework, for all
> plugins available in the jQuery UI suite. Expanding the scope would
> create a lot of unnecessary bloat.
>
> On Jan 12, 12:41 pm, fbloggs <djken...@gmail.com> wrote:
>
>
>
> > Well, I respectfully disagree. I do agree that this is a general CSS
> > cascade issue (in fact, I scoured the W3C CSS 2 specs to find where
> > tables fit in the cascade rules, with no luck). But it seems to me
> > that the jQuery UI CSS framework should handle this inconsistency for
> > you, and that the solution is very simple (along the lines of what
> > I've shown above.) This is more 'customer-centric' thinking, rather
> > than telling the user 'oh, it's a CSS quirk, and you have to fix it
> > yourself'. You could use the same argument with cross-browser
> > compliance!!! Instead, why not just fix it (ie deal with the quirk) in
> > the first place?  It would be a very simple change to the jQuery UI
> > CSS framework.
>
> > Regards,
>
> > Duncan
>
> > On Jan 4, 5:33 am, Steven Black <ste...@stevenblack.com> wrote:
>
> > > More generally, you can solve this with
>
> > >   table  { font-family: inherit; font-size: 1em; }
>
> > > So it's not really a tabs or a jQuery-UI issue, but more generally how
> > > table styles are reset, set, and thereafter cascade.
>
> > > **--**  Steve
>
> > > On Dec 30 2009, 6:46 pm, fbloggs <djken...@gmail.com> wrote:
>
> > > > I just recently used UI tabs in an application. Within a couple of the
> > > > tabs I used tables for content (let's not have a religious debate
> > > > about  using tables for layout, please). Anyway, the font size came
> > > > out much bigger than for text in a paragraph, for example. I looked at
> > > > the custom.css file (generated by themeroller) and found this line:
>
> > > > .ui-widget input, .ui-widget select, .ui-widget textarea, .ui-widget
> > > > button { font-family: Lucida Grande, Lucida Sans, Arial, sans-serif;
> > > > font-size: 1em; }
>
> > > > - designed to handle form input types.
>
> > > > I copied this and added table as a descendant selector, like so:
>
> > > > .ui-widget table  { font-family: Lucida Grande, Lucida Sans, Arial,
> > > > sans-serif; font-size: 1em; }
>
> > > > Problem solved.
-- 
You received this message because you are subscribed to the Google Groups 
"jQuery UI" group.
To post to this group, send email to jquery...@googlegroups.com.
To unsubscribe from this group, send email to 
jquery-ui+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/jquery-ui?hl=en.


Reply via email to