Yes. Last one was on December 13 2010.

I would love to see a new release!

Yes, let's push for a 2.1.0 release (perhaps beta?). There are enough new features for an increment in the minor version.

There are however a few more tickets I would like to close before the release. Namely:
#635, #637 - need testing
#736 - make into one unified patch (or directly commit into examples)
#714 - finish the review/test

Any help with those is really appreciated. The rest of the tickets can be pushed to the next release.

And of course I would really really like some improvements in the performance to fix the issue described in http://qcu.be/content/poor-performance

What are the new features coming up? :)

Would b glad to know as I do not get time enough to come back here :(

To full list of changes can be found here:
http://trac.qcu.be/projects/qcubed/query?status=closed&group=resolution&...

The main new features are

• Better integration of jQuery UI controls (#717)
• A new QSelect clause for picking a subset of database columns in QQuery (#79)
• Support for low priority JavaScripts (#635)
• Periodic events triggering with the new QJsTimer control (#633)
• Ability to return javascript objects from AJAX requests (#718)
• Proper Group By handling for databases other than MySQL (#270)
• Custom filters for QDataGrid (#714, not committed yet)

I'm sure I'm forgetting some.
And of course there are lots of bug fixes.

We are well on our way to being able to release. I think the only blocking piece now is the jQuery upgrade (http://trac.qcu.be/projects/qcubed/ticket/754) - I think others can wait. What do you think?

Agreed that we should call this version 2.1, the changes are too significant.

I am still on 2.0.2.

I would like to move to the new one. How can I move? There is a lot of things I have changed.

Vaibhav, we have been extra-careful about backward compatibility between 2.0.2 and 2.1, and there should not be any huge changes. The upgrade process should be pretty simple: download the new bits and overwrite the new bits on top of your old ones. We are still working on a detailed upgrade guide (as some files that typically don't change, like /includes/qcubed, have been modified) - stay with us, we'll be here to help.

You know Alex, I was actually once trying to do the documentation of QCubed. I like this framework. There simply is NO DOCUMENTATION and that means that when I have to create an image on my website, I would make a QLable, set the HtmlEntities to false and use that :(

Later I go to Controls directory and find that there is a Control for Images too and there are quite a number of arguments in there which I could have used but by then I had created a few pages in that style and I did not want to mess. I tried to understand what the Image control was trying to do and I could not figure it out properly - ended up trying that once for one of the pages and I ended up having myself recreating the page :(

Please do something to the Documentation Alex. Believe me, this gets QCubed unimaginably negative remarks in competition. I myself thought a number of times when I was in the first few steps of development to switch to Yii or Symfony but then QCubed stands way ahead in terms of simplicity and I hate getting complicated (since I know 'C' and 'C++', I can always make a page fall back to the CGI interfaceand get the performance in case I start requiring that).

Perhaps, you could do something like this to help it all out:

Write a small PHP script which can parse like the file in a similar way as 'comments' (Flex and Bison are great if you want to do that in C) and ask them to extract the info from the source files and then comment within the new files as:

/**[Doc]
[Context] Set properties of the QIntegerTextBox
[Info]
The properties available for this control to be set are:
Minimum: The minimum number you can input
Maximum: The maximum number you can input
[ImportsFrom]
QTextBox
[/Doc]
*/

and then allow the parser to parse that and read the similar comments from the file and run it on the source base. I think that will make things easy.

I have been messing around with DocBlox and am very happy with the results so far. Zend has moved to using it for their API documentation. As an experiment I pointed it at QCubed's core directory and generated API documentation. My results are uploaded at http://dev4.calyxhost.com/. I know we have been long suffering for good API documentation and I think this may be the solution.

Hi Steven, I visit the site you apoint http://dev4.calyxhost.com/ and looks really amazing the generated documentation you made with that tool.

Really useful for the API Documentation.

Great Job!!!

You know what Steven I think I have to say a word to you:

WOW!

that's all. Alex / vakopian really this is the best thing I believe for the API documentation . The current API doc site is all screwed up! This can bring about a charming change :)

Regards

Steven - it does look outright amazing. Do you want to take on the creation of a production API site for QCubed? This project really needs an owner :)

Alex, I would gladly take this on, is everyone is in agreement that Docblox is worth pursuing?

@Steven : I am.

@Steven: +1

Hello!

There's a date for the next release ?
I would like to use some new features that exists in the upcoming release, so, I like to know if exists a scheduled release date.

Thank you.

@jucope: early January is our target for the release.

@Steven: looks like we have consensus! I'm very much looking forward to your results!

Just an update on DocBlox. It looks like they are merging with PHPDocumentor. Their new interface looks really nice. I'm halting what I have done and will be setting up PHPDocumentor2. From the documentation I have read so far, generating API documentation doesn't appear to be too much different in PHPDocumentor2 than it was with DocBlox.. Will keep you updated on the progress.

Hmmm. Good move. :)