Current v3 Status

[geeffland]

I would plan on it being a while for the CBC 2.5 release. I have not started the formal code for it. It should go faster than a 3.0 release as I plan on it only being a change to work on J1.5 with no new features. So basically I am going in to do a quick surgery, replace the xAjax plugin (as that version is not J1.5 compatible), then replace database and global variable calls to the new desired calls. I will probably connect with the CB Framework variables as planned with CBC 3.0 but I plan on not doing any testing on Mambo, etc. I will mainly Test on J1.5 and may test on J1.0.

As far as J1.6 I think the core is a rewrite of J1.5 with one of the major improvements being a better ACL (still to be determined how it works). I have another project where the lacking ACL is the only issue stopping us from using Joomla so I have been keeping an eye on that one. They are also cleaning up quite a bit of the code, MVC mainly, but lots of interesting possibilities being tossed around between that and their GSoC projects.

[jazzking2001]

nice
um whats ACL?

[geeffland]

Access Control Level (i.e. who can do what)

[jazzking2001]

um
any update yet?
even a beta?
i have tried a few things to combine 1.5 and phpbb3
they are bad bad bad lol
i loved how easy CBC worked

[geeffland]

I have started to recode for J1.5 and CB 1.2.x. and rediscovered a few "issues" that I want to resolve. Likely will label as v2.5 as it won't be a full gutting as planned for v3 originally.

Those issues are:
1) xajax that is used in CBC v2 is not compatible with J1.5... So I want to replace the Ajax with something else... see below
2) To make it more likely to work with J1, J1.5, and Mambo, I will likely port the CBC Admin Control Panel to be back inside the CMS (So I don't need to load the CMS framework)
3) Need to review any changes and make sure they don't mess up any of the CBC modules or other components

Options for other Ajax:
A) Review CB v1.2.x and see what Beat uses internally and verify he doesn't have a CB native ajax routine
B) Some of the current areas already have prototype JS... possibly use its ajax features
C) Ext JS looks like a very good candidate for Ajax plus other features.

Both #1 and #2 above will take some effort. As far as the final solution on the Ajax... I think A will provide some insight on the URL to call from the Ajax but like B or C will be used to get the data from the Ajax call. Both B and C should be about the same to implement... C would be extra JS code form Ext JS but open up things for the future a bit.

[jazzking2001]

ah
i will just shake my head up and down showing that i understand all that you wrote lol
ya i dont know much >.<

anyway thanks for update