So we're really close to 1.1, and most of the open tickets have patches available, but it seems we're in sore need of some people to actually test out these patches.

So, if any of you out there would like to contribute to the framework, this is a great opportunity!

If you've got a test environment where you can duplicate the issue, please post back and let us know if the patch fixes it, and if there's any problems caused by it.

You can see the full list of open tickets at:
http://trac.qcu.be/projects/qcubed/report/9

So there's work ongoing throughout the day, and you're all still encouraged to come to the chatroom and say hi, but here's a brief rundown of the high-level things we talked about already.

Version 1.1

We're keeping 1.1 in the picture, and releasing it asap (though maybe later than originally planned), with all the new features and things you've already heard of.

Version 2.0

Afterwards, we're going to work on a v2.0 that includes a full re-write of the Javascript side of things to solely use jQuery (in noConflict mode), and remove any legacy QCodo Javascript, much of which seems incomplete, buggy, slow, and/or lacking in cross-browser support.

Versioning System

Starting right after 1.1.0 we're going to adopt a versioning system where any non-backwards compatible changes introduce a major version change (eg: 2.0.0), backwards compatible new features introduce a minor version change (eg: 2.1.0), and bug fixes or improvements that maintain compatibility introduce a build version change (eg: 2.0.1)

1.1.0 is a slight exception since the directory structure introduces a minor amount of work needed to move from 1.0.0, but we're not versioning it as if it were backward compatibility breaking.

So there's a lot of us core developers in the IRC chat right now, but this isn't meant to be some sort of closed meeting. If you want some insight into how things work, or want to help out, or make your voice heard, or just to hear what's coming up in version 2.0 (we're discussing skipping 1.1) now's your chance! Just click on Chat at the top of the window here, and you too can be part of the discussions! :)

There's a lot of cool stuff coming out in v1.1, but I'm just going to talk about the stuff I've had my hand in. This includes adding filters to datagrids (without a plugin), bringing back formbase, adding js actions for QHtml controls, updating the way MetaDataGrid controls display some values, PHP based templates, and Magic Quote support.

Filtering DataGrids

Most of you are familiar with my QFilteredDataGrid control, and you will be pleased with how similar the new feature will be in core. One of the benefits of having it part of core is that now metadatagrids will be filtered automatically, and you will be more easily able to set up filters for QQNodes. The examples will walk you through exactly what is needed to use them. :)

Formbase

Formbase is something that was lost when metacontrols were introduced, and a good chunk of interface code moved to them. Unfortunately, that still left a lot of code in the new form draft classes that was no longer simply overridable or updatable with just another codegen.

The re-introduction of form base classes means that a change to your database now just requires a codegen and all your GUIs will be updated, without the need for any hand-coding or re-copying of files.

Javascript Actions for QHtml Controls

This may not actually survive to see the light of day, since the new jQuery code may replace it, but there is now support to do basic javascript actions (such as QToggleDisplay) on QHtml controls as well as the normal server-side QControls.

Updated MetaDataGrid Controls

Nothing terribly exciting here, but now Time and Boolean types will display nicely in datagrids.

PHP based templates

We haven't thrown out the old templates (yet), but we've added support for PHP based templates. The basic system is the same, but now, if the filename ends in .tpl.php instead of just .tpl, the template file (and any includes it uses) is interpreted using the PHP language itself instead of QCodo's custom template language.

Over time, we will be re-writing the existing templates to use pure PHP templates, to promote the ability for normal developers to modify them with ease, and the support of their favorite IDE.

Magic Quote Support

Hopefully you're not one of the poor developers relegated to a shared hosting or other setup where Magic Quotes are forced on, but if you are, we have good news.

Version 1.1 will automatically detect if this is the case, and reverse all the bad effects that it causes. You can write your code as if it were turned off, and QCubed itself will operate without any changes.

Well we haven't been doing so hot on having each core developer post a blog entry every week... But the good news is we're on fire when it comes to finishing tickets.

Now that 1.0.0 RC2 is out, and 1.0.0 is looking pretty much solved, we've begun work on the exciting new features and approaches planned for 1.1.0. We're all pretty excited about this, and are interested in hearing your ideas as well! What already exists that should be added to QCubed? What is it missing that we should create?

Now's the time to let us know!

All the core contributers have been incredibly busy this holiday. Unfortunately, on matters unrelated to QCubed.

We're sorry we haven't had any updates in some time, but we expect them to pick up again in the new year. In fact, it sounds as though there will be some major effort put into QCubed in the next few months, so expect some big things. :)

As always, if you have the inclination to help out, we would welcome your contributions, and the framework can move ahead even while we're all swamped.

So I've been busy with non-QCubed related stuff lately, but there seems to be a lot of work going on without me.

A few more tickets have been closed this last week, but most of the effort around here seems to be going towards documentation.

Basically, there's two forms. API documentation that is more reference-manual type stuff and user manuals that are meant to be helpful guides on using QCubed.

You may notice posts like this on the front page once in a while. This is the first (unless I'm slow) of the blog posts we plan to make (we're hoping for 2-3 a week) just letting you guys know what's going on in the lives of the core contributers.

One of the goals of these posts is to remind you all that we're still here, and still working on things (or if we're not, then why, and that we haven't forgotten about it).

So anyhow, on to my actual blog post.