[wp-hackers] WP Theme Directory Submission Restrictions

[Ptah Dunbar]

Otto, to each his own, but I think that requirement should be handled
differently.

Perhaps have it where the uploader script just warns theme authors in
advance that they should include those extra alignment styles instead?
For the most part, theme authors initially start their themes from the
default theme anyway (which includes those css classes) so it really
shouldn't be a problem right?

Including everything under one css file is probably the best
way--performance wise.. but I think the trade off for being able to modularize
stylesheets and simply organize them are much better alternatives.

Ptah Dunbar — Web Developer
http://ptahdunbar.com


On Mon, Oct 6, 2008 at 10:00 AM, Doug Stewart <zamoose at gmail.com> wrote:

> On Mon, Oct 6, 2008 at 9:56 AM, Otto <otto at ottodestruct.com> wrote:
>
> > It also makes things super slow as the browser now has to individually
> > load every one of those files when the page is loaded.
> >
> > Please, stop doing this. It's not clever, and it's a little bit
> > annoying. A well designed theme should have one and only one CSS file.
> > It's acceptable to have extra files like that only when you're doing
> > advanced theme control, like changing header colors and such via the
> > theme's administration page.
> >
> > -Otto
>
> I don't agree, just as I don't agree that all proper C programs ought
> to have all of their code in a single .c file with nary a #include to
> be found.  CSS is coding, thus modularization and code reuse are just
> as valid in its context as they are in Java, PHP, C, et al.
>
> I don't want to include the contents of my reset.css in every stinking
> CSS doc that I author.  It's inefficient, it's messy and it leads to
> all sorts of nastiness down the road.
> --
> -Doug
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>