After using Trac for sometime now in our production environment, I have come across quite a few things that I like about it and several things that I dislike about it. This being the case, I decided that I would take it upon myself to write my own issue tracker. I am not very good with Python so I could probably rewrite a system in ColdFusion twice as fast as I could modify Trac to do what I want. So the Trac_Fu project has been born. Trac as in “Trac” obviously and Fu as in “coldFUsion
“. So Im not the most creative namer in the world!
Sticking true to my roots, I am developing it in Fusebox. Im currently using the newly released Fusebox 5 and as of today, Im using Reactor for the back-end model. Progress is pretty good. The stylesheets are mostly done. I have several of the list pages done, most of the database is ready. Speaking of the database, its basically modeled after the Trac database so that I can entertain the idea of porting existing items from Trac to Trac_Fu.
Im using the JavaSVN libraries to hook into subversion as well. Im only going to concentrate on getting the changesets pulled into Trac_fu for the first release. Then the source browser features will follow.
I hope to have some screenshots for you by the first of the week.
Im a recent CFEclipse convert. I have tried to make myself use it many times before but after a few days I didnt feel like I was being very productive so I would always go back to either Homesite+ or DreamWeaverMX and never look back. Over the last 2 weeks I installed CFEclipse and removed DreamweaverMX and Homesite from my box completely in an attempt to “make” myself get used to coding in it.
At first it was a little rough as usual, but once I started playing with all of the settings and tweaking things the way I want it, I really found myself enoying using it. I have found a few plugins that make it easier to do some development and discovered a few tweaks that really helped me to get over the “hump”.
I will be doing a few entries of some of the things that I have found to make my life a little easier with Eclipse.
Today after talking with a few guys on the Fusebox 5 mailing list and playing with the code coloring options, I finally found a way to get my fusebox.xml.cfm and circuit.xml.cfm files to use syntax highlighting. By default Eclipse just uses the CFEclipse editor for them since there is a file type of *.cfm in the file associations preferences. So I thought that I could just add a new file association called *.xml.cfm and point it to my xmlbuddy plugin editor. Well that didnt work. So after maybe 30 minutes of digging through settings, I realized that you could put a whole filename into the file associations and assign an editor to it. So I added both of those file names and assigned xmlbuddy as the editor. Now my xml configs in fusebox are all syntax highlighted!
Stay tuned for more.
Sean Corfield has just released the first “official” build of the brand spanking new Fusebox 5 core files. You can download them at Fusebox.org. There is also a skeleton application offered up for download on the same page to help kick start your first FB5 project.
I have been working behind the scenes on a Bug/Issue tracking system written in ColdFusion that is basically a port of Trac and its using FB5 as the framework. All the development so far was based on a general release candidate build that Sean sent me a few weeks ago and so far it has been rock solid. I really like some of the new features that were added and the cool thing is that FB 4.1 apps are completely backwards compatible!!
What are you still doing here??? Go grab the files and start coding something!!
The ever-expanding Google Empire has moved into a new space with the release of Google Code. Its akin to SourceForge and Tigris in that it provides services for opensource projects. You get a built-in Issue Tracker, Subversion repositories, and all kinds of neat little tools. I setup a project on there to see what the interface was like and I was quite impressed with its simplicity.
Even though Im a contributor to 4 different projects on SourceForge, it has always been a bit “overcomplicated” to me. At first there was a HUGE learning curve and tons of documentation to read on trying to get the CVS access setup and the file upload setup to release builds. After 4 or 5 years now it seems like second nature but I remember being very frustrated with it for weeks when I first got started.
The Google Code project is MUCH simpler. Its interface like all things Google is very clean and uncluttered. The management interface has a vew options that provide most all the functionality you will need without over-compicating things.
One caveat is that you must have a gmail account in order to setup a project but I would assume that most people have at least one now.
Head over to the Google Code page and get your OpenSource projects setup now and remember to always, “Release Early, Release Often”!!
I just finished sitting in on the Breeze presenation that Ray Camden gave to the Detroit Users Group on SPRY and ColdFusion. I have to admit, I have always been a little hesitant to mess with AJAX at all. Mainly due to the complexity of some of the implementations that I looked at early on in its release.
I must say that Ray’s presentation really showed how simple the SPRY framework is to use. I was actually excited to download it and try it out for myself.
The Breeze presentation was recorded so it should surface on Rays blog within a day or two. Definately worth the hour and a half that it will take to watch it! Ray gives a ton of examples during the presentation and show how he integrated it with ColdFusion in BlogCFC as well.
Was doing my daily rounds of the CF Blogs and came accross a nice piece of information that I thought I would share. Ray Camden has written a great post about the ways to battle the dreaded whitespace generated by ColdFusion.
Im probably as guilty as the next guy about not thinking about doing some of these things in my coding. I guess I’ve got something else to start working on.
Just wanted to take a minute a give credit to Tim Kimberl for the Aqua Styled WordPress theme he created. I have had this WordPress theme sitting on my harddrive for quite some time and I have no idea how to reach Tim.
All of the styles and images with the exception of my little angry fly image were created by Tim. I tweaked the styles a little to work with BlogCFC but for the most part, its what Tim layed out.
I am going to finish packaging the theme and making a few tweaks to work with my BlogCFC theme engine and then release it here for anyone to use.
I decided that after making a living coding ColdFusion for almost 8 years now, I should be blogging on a CF based blog vs. the WordPress PHP based software that I had been using. WordPress was simple to setup and it was just plain easy. I didnt want to have to deal with ‘more’ CF stuff than I was already dealing with at work.
But, I started a new job last week with a small company that uses CF extensively in all of its web-based payment products and something about the change has renewed my vigor when it comes to ColdFusion. I admit I was getting stale, bored with it. I had been using Fusebox for over 6 years and was kind of excited to try Model-Glue and some of the new stuff around but I still didnt have the interest to sit here night after night working CF code.
I have been playing with Fusebox 5 alot lately and ColdSpring as well and I am really enjoying working on CF stuff again. So I decided to take the plunge and setup Ray Camdens latest version of BlogCFC. The setup was really quite simple and as you can see, I have strayed quite far from the default look-n-feel by modifying all of the layout files. I am working on a themeing engine now that will make it much easier to create themes for the blog since I like to change my theme quite frequently. If you have a CF host and havent tried BlogCFC, head over to Ray’s site and check it out!