CSS extension for Nvu
By glazou on Thursday 11 March 2004, 10:38 - Nvu - Permalink
I have just started working on a new CSS feature for Nvu:
Next events
- 9-11 may-2012, CSS WG meeting, Hamburg, Germany
- 29 oct-2 nov 2012, W3C Technical Plenary Meeting, Lyon, France
Comments
Sounds great. Unfortunately my computer is too small to build mozilla (or too buisy with other things), so I'm hopefully waiting for someone who builds it for MacOS X. But it looks like you are doing great work.
Best. Feature. Ever.
(possibly. I haven't really thought about it yet, but it seems good. I suppose I shouls have a play with Nvu sometime. How much of cascades is integrated? Can one select an element and see all the CSS selectors that apply to that element (and adjust the style rules for those selectors)?)
(x)all elements
[x] of class [FOO]
This would result in a .FOO rule? An option for generating tagname.FOO would also be nice - so if I selected an input element, it would generate an input.FOO rule.
Come to think of it, offering "hovered by the pointer" only to "all elements" seems too restrictive either... What about:
-------------------------------------
( ) only the current element
( ) all elements of type [type of selected element]
(x) all elements
-------------------------------------
..."when"...
-------------------------------------
(x) of class [textbox for class name]
( ) hovered by the pointer
-------------------------------------
Whereas the second box is disabled when the first option "only the current element" is selected.
Jens: the choices are [ ], these are non-exclusive checkboxes, not exclusive radiobuttons...
Okay, I thought you switched to square brackets to show it's another radiogroup... Those ASCII forms are not always intuitive
Another, unrelated question about Nvu (several questions, actually): I was wondering whether Standalone Composer will be continued (as a mozilla.org product), or are those plans superseded by Nvu? If not, what will be the difference between Nvu and Standalone Composer, besides branding? Given that Nvu's additions are fully MPL tri-licensed (unlike Netscape 6/7 which added proprietary stuff on top of Mozilla 1.x), Composer could have absolute feature parity right? In short: are there any features you want to have in Nvu, but not in Composer? [Could be answered as a blog entry, might be of general interest]
Are those choices inclusive or exclusive? IOW, if I was to select 'of class foo' and 'of type H1' would it create a rule for 'h1.foo' or a rule for 'h1' and a rule for '.foo'?
Perhaps the wording should read 'all elements that satify (any|all) of the following conditions:'? (depending on which one you meant).
Great - inline styles should be discouraged in favour of global rules (i.e. stop thinking like it's 1990)
Malcolm, the sentence "create *a* CSS style rule" at the beginning implies it will generate one rule.
Excellent
Wooohoooooo !
Do you really need three exclamation marks? It looks really unprofessional. A period should do just fine.