Your browser does not support CSS standards!
Enjoy the content, if not the layout. Or upgrade your browser. Or something.
Toolbox Dev Notes
Firebug
No telling when I'll make more time to develop here, but wanted to blog about a really useful looking tool come the day when I'm ready to do some more HTML/CSS/AJAX/Whatever testing.
Firebug looks really slick, I just finished watching a screencast demo of the features, wow. Tip of hat to mezzoblue
| Permalink | Friday, Feb 2 at 3:34 PM
Credit cards
I've been thinking a lot about how to connect credit cards to this project... my wife is signing up for a new service and came in saying, "they want the credit card information now and I don't like that" since it's a free two-week trial.
I'm not sure how I'll code mine, and doing similar is certainly an option... but indeed, people don't really like that do they?
Hmm.
| Permalink | Sunday, Sep 3 at 6:34 PM
Version control
Today I'm using CVS. I've been meaning to switch, to... what? Subversion?
Dr. Bart says the answer is git... or cogito, a nice sensible front end. I think I'll use the Featured Links feature for this.
| Permalink | Friday, May 12 at 5:13 PM
Zebra?
I wonder if Zebra and Toolbox could be made to play together properly... and do something useful?
| Permalink | Friday, May 12 at 4:04 PM
Minimum goals
My mind works best sometimes when I talk to somebody else. I found myself chatting this earlier:
If I only get the project moved to Sourceforge, get somebody else to put up a build, and get RSS implemented it'll be a fine initiative.
I hope for more, but this is a great place to start and with help should be "no problem". My friend made another great point:
My group here at work is currently working on some reuseable code stuff. We're totally convinced that getting the stuff used is largely a function of how good the documentation is, wiki, install, examples, etc. You ready to write some docs?
Yes, so ready!
| Permalink | Friday, May 5 at 11:14 AM
Woot, accepted for consideration!
I got my authorization this morning and posted my project proposal on the Google/PSU Summer of Code site!
Of course if you're reading this you probably already know that, since the linkage there is the only thing that points here. Time to do something about that, like point to it from my personal blog.
What a great idea, however without RSS I don't have many readers. I hope we can fix that problem this summer!
| Permalink | Friday, May 5 at 8:13 AM
No comment count
We got HaloScan comments working nicely once with HPTB (and then Neal forged ahead and made them really nice... now I can't replicate, the count isn't updating.
Nerts, and I'm out of time.
| Permalink | Thursday, May 4 at 9:24 AM
Before I forget
I do have a demo and some random notes if somebody was interested.
| Permalink | Thursday, May 4 at 9:00 AM
Optimistic
Wow, it's been a long time since I put this tool through the paces, and it's pretty sweet! Lots and lots of rough edges and stuff that needs to be a whole lot better, but on the other hand... it really works!
I knocked out a proposal page and started this blog (and associated links) in short order. More soon, or later since I better get cracking on the day job. Oh foo, I won't be done here until I get the comments working.
| Permalink | Thursday, May 4 at 8:46 AM
Google's Summer of Code Project
My cousin Bart Massey (herein referred to as Dr. Bart) has encouraged me to apply for Google's Summer of Code and fully release this project as open source. I'm in! This blog will track the initiative.
Right now I need to develop a list of projects. Hmm.
Left alone, the next two enhancements would be:
1. Add RSS with enclosures
2. Allow automatic creation of uploaded picture "rolls".
Really those are the only two ideas I have presently that I would code myself. For SOC, on the list might include:
A. Deploy a developer instance of HPTB, documenting each step required, as is, to get it to run elsewhere (consider this a "binary release" target).
B. Move the source from private CVS archive to a public repository (sourceforge or better)
C. Develop a process for fully downloading and building from source, based on CVS branch level, to support a "source code release" target. Document.
We could spend all summer on just those items above, plus enhancements to same. Otherwise... next blog entry.
| Permalink | Thursday, May 4 at 7:33 AM
This page is owned by
