[wp-hackers] 1.3a2 CVS

[David House]

A worthy ammendment. I'm with the ayes.

To all those saying this makes it harder work for a dev, tell me: which is
harder -- finding where a different section starts amongst a huge file, or
simply opening another file? I'd say splitting dev files actually makes it
easier to find that specific section of code you're trying to find, and as long
as we provide adequate descriptions of what each file does, there shouldn't be a
problem here.

Besides, this makes it much easier on the user's part, and therefore there
shouldn't be any argument here at all.

Quoting Kitty <kitty at mookitty.co.uk>:

> After Matt's spamming of the CVS list last night ;) I've been looking
> over some of the changes. One thing that jumps out that could be real
> confusing is footer.php.
> 
> It includes the sidebar/footer/everything not in the main loop. I agree
> that separating the files is good, the sidebar stuff probably shouldn't
> be in a "footer" file. (I would think that most people think of stuff at
> the bottom of the page when they hear "footer," and having the sidebar
> there is misleading.)
> 
> Also with a separate file some of the more elaborate themes could
> include a replacement sidebar file for easy drop in replacement
> 
> I think that under this schema, we should have a sidebar.php in addition
> to footer.php to account for this.
> 
> Pros: More segregation of functions; easier customisation; user changes
> will only bork the sidebar, if something borks; would move towards
> making WP skinable (e.g. have a stylesheet included by the sidebar file,
> etc.).
> 
> Cons: Another file to manage; might increase package size.
> 
> Discussion?
> 
> Attached files:
> sidebar.diff - changes needed to existing files.
> wp-sidebar.php - the new sidebar file.
> -- 
> Cheers!
> Kitty
> http://blog.mookitty.co.uk/
> http://mookitty.co.uk/devblog/
> 
> 




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.