>
> I created a tarball of the latest Zoop code (revision 243). I haven't
> tested any of the examples yet, but I did generate new API. I couldn't
> attach to this email, so I stuck it up on Google Code. Will you guys
> review it quickly to make sure it's all good from your end? Are there
> any bugs in Zoop right now that should held back this tarball release?
There might be a thing or two that I want to get in there before you
release it. I will check it out.
> Version number: I put version 1.90.00 on the tarball for a couple
> reasons:
> 1. This version is significantly different / enhanced over the current
> 1.50.01 (from a year ago).
> 2. If we're getting ready to move everything over to 2.0, this will
> help people realize that it's getting close. All other updates before
> the move will stay within 1.9x.
The plan was to use 1.51.00. If our version number is x.y.z then
bumping up the z signifies and incremental update. Bumping y
indicates a major update. We won't bump x until we jump to 2.0 so
there no reason to hurry towards it. Users just need to know if it is
a major or minor update.
I created this file: http://code.google.com/p/zoop/source/browse/trunk/todo/roadmap.todo
as a tentative sort of roadmap for the project. It will probably
change significantly but it gives you an idea of how I intend for the
versioning to work.
> Let me know if this meets your approval and I'll go ahead and stick it
> up. And I'll send out an official announcement to the list when it's
> done. Shall I put the official announcement on ZoopFramework.com?
Test the examples, let me get a few extra things committed, and then
we should be ready to roll a new tarball and release it as 1.51.00.
Sorry for not detailing this somewhere earlier.
Thanks,
Rick
I'm checking this out and fixing a few things. I'll let you know what
I find.
Rick
I just fixed a problem with the DbFunctions example and cleaned up a
little in some of the other ones. Some didn't work but are based on
experimental stuff anyway so I just put a die at the start of them
with a message. Do you think that's worth rolling 1.51.01? If not we
can announce right away.
One thing we need to figure out at some point is how to set the
permissions in svn so when you do an export or checkout from
subversion the sqlite files are immediately writable. Do you have any
idea how to do that?
Rick
I just fixed a problem with the DbFunctions example and cleaned up a
little in some of the other ones. Some didn't work but are based on
experimental stuff anyway so I just put a die at the start of them
with a message. Do you think that's worth rolling 1.51.01? If not we
can announce right away.
One thing we need to figure out at some point is how to set the
permissions in svn so when you do an export or checkout from
subversion the sqlite files are immediately writable. Do you have any
idea how to do that?
On Mon, May 26, 2008 at 10:23 PM, Rick Gigger <rgi...@gmail.com> wroteI just fixed a problem with the DbFunctions example and cleaned up a
little in some of the other ones. Some didn't work but are based on
experimental stuff anyway so I just put a die at the start of them
with a message. Do you think that's worth rolling 1.51.01? If not we
can announce right away.It would be nice if examples contained a short README of how to implement. I ran into some problems trying to implement "graphic", "ZendPDF" and some others. I'll post them in another email right now.
One thing we need to figure out at some point is how to set the
permissions in svn so when you do an export or checkout from
subversion the sqlite files are immediately writable. Do you have any
idea how to do that?I'm looking into how to do this. Hopefully there is a way. The perms might not hold on a Windows box, though. We'll see.