BlueWater ETA

Hi Everyone,

Just want to let you know that I’m estimating the ETA for bluewater to be around 3 months from now. I’m committed to getting this project out ASAP due to the power that it will contain for building web apps.

I’ll be spending more time working on it to ensure that it either complete or nearing completion in the time specified.

So far I’ve started working on a structure that’s nearing 100% Ajax for the manager but as you know Ajax is only good for some things it’s not good for everything.

Speaking of which, what’s the difference between the ’bluewater’ and ’bluewater-dev’ branches on the SVN server? Just curious. Also, do these branches show an updated theme with a new color scheme and layout? I wouldn’t mind seeing where we’re at with that and add my 2 cents as well as additional layout/color scheme proposals.

bluewater will be deleted, as it’s got an extra layer of the /trunk/ in it

was demonstrating a copy in an existing branch vs a copy to a new branch

Actually Ryan, I think the one without the trunk needs to be removed. Without the trunk, we do not have proper revision history of the root of the site in the bluewater-dev branch.

But I could be wrong, I’m no SVN expert for sure

The bluewater-dev is an SVN copy of trunk, named conveniently "bluewater-dev". It’s the same exact thing, made in the same exact way, as the copy of trunk made via SVN copy in bluewater/trunk/.

It should be the same, anyway, as far as I understand how it works.

Raymond and Jason,

Is there any chance you folks would both use SVN as you make progress. It would allow us all to follow the progress rather than waiting for large monolithic commits. I don’t see how there’s any other way to have a collaborative project otherwise.

Thanks!

Indeed, thanks for reminding us that we are a team; I will be checking in a preliminary version of the Propel-powered MODx preview (PHP 5/new install only) to my branch once I get all the demo site content working 100% (hopefully today). Then once I am satisfied with the performance, we can review and decide to merge into BlueWater or remove it altogether

The version I have is not even close to functional. It’s still under going some restructing. Things will change drastically so I don’t know if it is the right think to add to the bluewater-dev at this time. For examplethe Page structure and event flow has change serval times in one week.

At some point in time (after restructuring) the code will have to merge with Jason’s propel screens but I would rather continue as is until Jason has finished off with the propel merge.

I have a preliminary merge with the PHP 5 Propel runtime completed locally with revision 604 and am finishing some final tweaks in the Propel PHP 5 runtime to respect our table prefixes and database configuration. Once I complete that and have it working, I will check this into a branch in SVN so you all can have a look. Just note, this is not yet optimized, nor anything but the basic API defined, and is for PHP 5/MySQL 4.x+ only (I opted for defining the new MySQL schema with InnoDB tables, in order to support the transaction capabilities in the framework). More very soon...

I will be working on a PHP 4 runtime version as well, once I am satisfied with the performance on PHP 5. This will involve having two versions of our core persistent object classes to match the Propel/Creole runtime packages; this is so that we can take advantage of PHP 5 exception handling when used with PHP5; the PHP 4 exception handling used by both Propel and Creole returns Exception classes from the functions. This will mean a little more maintenance work, but gives us the flexibility to optimize, and isolate functionality for, version 4 and 5.

Jason,

Question ...

Isn’t that InnoDB Tables are larger and slower than MyISAM tables? Do we need transactions on all the tables?