[dev] design goals for 1.3/2.3

[Anil Madhavapeddy]

Chuck Hagenbuch wrote:
> 
> 2. let's wrap every function that doesn't live inside a single page 
> inside one class or another. we don't need a seperate file for 
> every single class, but encapsulation is good - it keeps our 
> namespace small, and it makes it easier to figure out where things 
> live/what they are associated with/what they do.

I'm not sure I understand the first bit - do you mean wrap every
function inside the main .php files that are duplicated across more
than one page, or every function in there ?

> 
> 3. modify the files that use javascript to include their javascript 
> first. right now, if you interrupt a page like the compose window 
> from loading, you might get all the html, but the javascript won't 
> have finished, resulting in errors.

Sounds good, that annoys me no end when I'm on a modem!

> 
> 4. Comments! Cleanup! Documentation! =)
> 

Eek! ;)

> That's all that's coming to mind right now. Anyone have other suggestions?
> 

Would it be an idea to really separate Horde and IMP this time around?
Given that we could potentially make new releases of Kronolith, WHUPS, etc
in the lifecycle of 1.3.x/2.3.x, it may be good to separate them a bit more
discretely than they are at the moment.

This might only be a release control and versioning thing, but it would
still be helpful for the other modules.

--
Anil Madhavapeddy, <anil@recoil.org>
"Quidquid latine dictum sit, altum viditur"