Create a custom theme
1
As development on IP.Tracker gets nearer and nearer to a release, we'd like to share with you one of the key concepts behind 1.4. As you will know, previous to 1.4 IP.Tracker had project statuses, severities, and versions. These were features that were added as the product evolved from version 1, and we expanded upon them nicely.
Unfortunately once we hit 1.3 we realised we couldn't progress any further without a severe overhaul to how these areas were handled by the system, all 3 features were hardcoded in which meant if we ever wanted to expand on one of those features, we had to release a whole IP.Tracker update. We took the decision to make fundamental changes within 1.4.
Modules
IP.Tracker's new framework splits these 3 areas off into what we call Tracker modules, these modules can add new features to your Tracker installation. Within these modules, a module can have multiple fields, and Tracker extensions. Developers will find Tracker fields near identical to how one would write an IP.Board application. Modules contain the relevant classes for the admin and public side of 'fields', an extensions folder, admin skin folder, and much more.
Modules are incredibly easy to install, simply upload the files and visit the IP.Tracker ACP (note that the default statuses, severities etc. will all be packaged with Tracker so you will not need to download these modules). The Module Installer is easy to use, with a simple progress bar indicating how installation is doing.
Fields
This is where IP.Tracker 1.4 truly shines, fields are shown on the front-end and are the main parts of any module. The severity colouring, version indicators, and statuses are all fields. IP.Tracker has a powerful Field Admin CP which integrates into several areas, today we're going to show off the main area itself.
All fields that are from installed modules will be listed here, you can reorder them around the page whilst, if that particular field allows it, providing access to a set of controls (in our case the edit icons on Status and Severity).
Statuses
Statuses have always played a big part in IP.Tracker, helping to categorise reports from 'Confirmed' to 'Not a bug' in the case of a bug tracker, or for sorting out technical parts of a car. As with most parts of IP.Tracker, and especially the modules, we've started fresh. Simply click the pencil icon for the status field to be presented with the status editor (developer documentation will be available soon!).
Now, if you can remember the 1.3 status editor, I am sure you will appreciate the amount of time we've spent on the interfaces for this release. Here is a video to showcase the new module.
As you can see, we've simplified the interface whilst making it easier than before to add new statuses to your Tracker installation.
Severity Colours
One other module I'd quickly like to go over is the Severity module and a few changes we have made. For version 1.0 of this module (see my last paragraph for version information) the module will no longer support text colours, and we have removed the ability to colour the issue when no severity is set. Text colouring will return in 1.1 of the severity module.
Why Modules?
To wrap up, we decided to go with a modular framework for 1.4 because it means we can push out new features and bug fixes to existing modules without having to update the whole Tracker application - we can also push out new features and new modules very easily, and third-party developers can make their own. IP.Tracker 1.4 truly allows you to customise it in anyway for your website, it no longer needs to be a bug tracker. If you do not need severities - don't install the module, if you don't need statuses - leave that one out. You can mix and match as much as you would like!
Our blog entries in the future will go over the front-end and also mention expected timeframes. Thanks for reading and we hope you like what you see!
Unfortunately once we hit 1.3 we realised we couldn't progress any further without a severe overhaul to how these areas were handled by the system, all 3 features were hardcoded in which meant if we ever wanted to expand on one of those features, we had to release a whole IP.Tracker update. We took the decision to make fundamental changes within 1.4.
Modules
IP.Tracker's new framework splits these 3 areas off into what we call Tracker modules, these modules can add new features to your Tracker installation. Within these modules, a module can have multiple fields, and Tracker extensions. Developers will find Tracker fields near identical to how one would write an IP.Board application. Modules contain the relevant classes for the admin and public side of 'fields', an extensions folder, admin skin folder, and much more.
Modules are incredibly easy to install, simply upload the files and visit the IP.Tracker ACP (note that the default statuses, severities etc. will all be packaged with Tracker so you will not need to download these modules). The Module Installer is easy to use, with a simple progress bar indicating how installation is doing.
Fields
This is where IP.Tracker 1.4 truly shines, fields are shown on the front-end and are the main parts of any module. The severity colouring, version indicators, and statuses are all fields. IP.Tracker has a powerful Field Admin CP which integrates into several areas, today we're going to show off the main area itself.
All fields that are from installed modules will be listed here, you can reorder them around the page whilst, if that particular field allows it, providing access to a set of controls (in our case the edit icons on Status and Severity).
Statuses
Statuses have always played a big part in IP.Tracker, helping to categorise reports from 'Confirmed' to 'Not a bug' in the case of a bug tracker, or for sorting out technical parts of a car. As with most parts of IP.Tracker, and especially the modules, we've started fresh. Simply click the pencil icon for the status field to be presented with the status editor (developer documentation will be available soon!).
Now, if you can remember the 1.3 status editor, I am sure you will appreciate the amount of time we've spent on the interfaces for this release. Here is a video to showcase the new module.
As you can see, we've simplified the interface whilst making it easier than before to add new statuses to your Tracker installation.
Severity Colours
One other module I'd quickly like to go over is the Severity module and a few changes we have made. For version 1.0 of this module (see my last paragraph for version information) the module will no longer support text colours, and we have removed the ability to colour the issue when no severity is set. Text colouring will return in 1.1 of the severity module.
Why Modules?
To wrap up, we decided to go with a modular framework for 1.4 because it means we can push out new features and bug fixes to existing modules without having to update the whole Tracker application - we can also push out new features and new modules very easily, and third-party developers can make their own. IP.Tracker 1.4 truly allows you to customise it in anyway for your website, it no longer needs to be a bug tracker. If you do not need severities - don't install the module, if you don't need statuses - leave that one out. You can mix and match as much as you would like!
Our blog entries in the future will go over the front-end and also mention expected timeframes. Thanks for reading and we hope you like what you see!
Get a beta out already.