[wp-hackers] GSoC 2010: Visual CSS Editor

[Beau Lebens]

Full disclosure: I was Daryl's mentor for GSoC last year, and reviewed
his proposal before he mailed it out to the group, but I'd like to add
a few comments anyway:

- This proposal has stemmed from Daryl's experience working on
Elastic, and realizing that a decent style editor is not only a big
part of a good visual theme editor, but entirely a project of it's own
- Splitting things up and making parts of the editor modular mean the
entire thing is potentially pluggable, a very cool feature (and very
"WordPressish")
- MikeS: saving to the DB by default definitely doesn't preclude from
saving out/exporting to file. There would need to be a way to get at
the CSS as raw CSS either way
- AndrewN: Absolutely, if the theme revisioning project happened this
summer, it'd be perfect to be able to just tie into whatever API that
provided and just trigger a new revision via this editor.
- There's a lot of tricky UI to be figured out here to avoid making
this just a blunt CSS tool (add selector, add attribute, select from
list, enter value, save). I think there's also some real potential for
concepts like palettes and presets and whatnot that could make this
really powerful, without being overly complex for the end user.

In summary, "I like it" :)

Cheers,
Beau


On Tue, Mar 30, 2010 at 5:29 AM, Andrew Nacin <wp at andrewnacin.com> wrote:
> "Automatic child themes" was also included in another proposal,
> http://wp.me/pQEdq-q, as an extension of a theme revisioning system. Seems
> like an interesting cross-over that both proposals could make good use of.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>