Site Network:

raoul's blog

Considerable Upgrade Ahead

An interesting thing has happened recently in the Pylons world (Pylons is the web framework that Project HQ is built on); Pylons has been "merged" with Repoze.BFG, another web framework, and the Pylons framework itself has been discontinued. Together they now form the Pyramid framework.

Unfortunately, this means that all Pylons projects are somewhat left up in the air, and will need to be redeveloped in Pyramid. I am currently evaluating Repoze.BFG to see how much code can be migrated, and how much will need to be totally rewritten.

 

Project HQ 0.1.4 Released

That's right, I've finally released Project HQ 0.1.4!

There are no major features introduced into this version, but a lot of the backend has been reworked, providing developers with a framework which makes it easier to do the repetitive things. The URLs have also been changed slightly, they now no longer end in a "/".

 

Pylons upgraded, release coming soon...

Hi folks,

Well, I'm proud to announce that I've upgraded Pylons in Project HQ, and that I'm close to another release. I've got some tidying up to do, and I need to track down any bugs I might have introduced.

The Subversion repository at SourceForge.net is up to date with the latest code, but when I release version 0.1.4, I will move Project HQ's code over to Bazaar at Launchpad.net.

 

Version Problems with Pylons and SQLAlchemy

At the time that I was originally writing Project HQ, the latest versions of Pylons (the web application framework Project HQ is written on) and SQLAlchemy (the database abstraction layer) were 0.9.7 and 0.5.5, respectively. Unfortunately, while these two projects have continued forward, and released later versions, I haven't had the time to go back and take care of installation problems with Project HQ.

 

Christmas Greetings

To those folks who celebrate Christmas, I'd like to wish you a merry Christmas. To my fellow Christians, I hope that you remember the real reason for Christmas, and I wish you a blessed day.

 

Things are plodding along

Just a quick update for those folks visiting the site and wondering if the project is dead, the good news is that it isn't. The bad news, however, is that with the arrival of my son at the end of July, I haven't had as much chance to work on Project HQ as I'd like.

 

Some Internal Re-architecture...

As someone pointed out in the IRC channel, there have been no apparent updates to Project HQ in a while. Unfortunately I haven't been able to devote as much time to Project HQ recently as I have been before, but I am still working on it!

Currently I'm busy doing some minor internal re-architecture, changing the way things work a little, to make it easier and faster to work with. It also provides a nice validation framework for both client side (JavaScript) and server side (Python) validation.

 

Version 0.1.3 released.

I've just released version 0.1.3 of Project HQ, with the new ticketing feature!

Please note that you will need to download TurboMail 3.0b2 and install it via easy_install.

 

Attachments working now!

Well, I've successfully added uploading of attachments to tickets. You can even add additional attachments by updating the ticket. In addition to that, if you upload source code, it is viewable and it's syntax is even highlighted.

At the moment only HTML, PHP, CSS, Python, Perl, Ruby, Javascript and Pascal are supported, but I'm busy working on supporting more languages.

I've updated the demo for those who want to play around with it, and I'll release an egg file once I've done a little more testing and bug fixing.

 

Ticketing almost done!

Well, after a weekend of hacking, I have some basic ticketing working. You can see what I've done on the demo site.

At this stage you can't upload attachments, but that's the next step. After I've sorted that out, I'll be implementing the e-mail notification system, which will notify you of anything assigned to you, or anything you create or edit.

I've also "wikified" a number of the text fields, so you can put wiki text into some of the description fields, and it will be rendered correctly.