Re: [binarycloud-dev] r1 -> r2 and r2 development

[Alex B. <en...@tu...>]

> i've talked on this list about a community driven site i'm going to
> build, and i wondered what you guys think i should start with. i've
> taken a look at *a lot* of cms/web driven frameworks now, believe me,
> and i keep on coming back to either binarycloud or horde. horde is
> pretty mature, but it hasn't got a framework nicely structured and layed
> out such as binarycloud has (at least r2, don't know about r1).
> 
> that's why i'd want to start building with binarycloud. r2 still being
> in its infancy (although basic page rendering works, i admit ;)), is it
> a good idea to start doing the work with r1 and then try to convert it
> all to r2? 
> or just go along, start doing work with r2, and start helping and coding
> the bc backend if somethings missing? ;)

I would start working with r2.

for a couple reasons:
    -the page render pipeline is _far_ more mature than binarycloud r1's,
I've tested it a bit and I'm happy with the code.

    -no, auth and perm aren't done, but they will be fairly soon, and they
will both be more powerful and better structured than in r1.

    -I'll be publishing another shell revision soon that includes
XSLT_TemplateManager as an extension to TemplateManager (which other ware
invited to extend to support Smarty, FastTemplates, etc.

    -You will be building modules as classes, not as groups of functions as
in r1.
 

    -r2 is not in its infancy, it's the build effort from lessons learned in
r21. I.e. the code is better and more mature :)

> especially auth and perm classes are something i will need really soon.

ah, how soon?

> i am prepared to help anywhere i can, but someone (alex?) should give me
> advice as where to move in.

A caching class would help a great deal, as that is on my list for the r2
core classes.

You could also take the existing Lang class, and write the methods necessary
to have it set BC_LANG corrected (based on accept-language)

I will be publishing templateManager quite soon, so you should be able to
start building pages fairly quickly.

Auth/Perm is a major revision, I'll look into it and see where you can help
most.

> btw, is the sourceforge cvs depository the main r2 cvs depository?

no, the main cvs is internal at turing, I am happy to change that to be
binarycloud.com, so you can get access.

I update sourceforge every so often, but I dislike the way their cvs is run
(I can't get access to my own cvsroot!) so I don't run it there.

_alex


--
alex black, ceo
en...@tu...

the turing studio, inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093