P4UI

by David Jeske <jeske@chat.net>

Check out: software (and source) -- screenshots

Disclaimer:This project isn't genuinely useful. It's a snapshot of my ideas and progress. If you really like the idea, drop me a line, and encourage me to work on it some more.

About the Project

Back when I was working at 3dfx, I came to use the SourceSafe GUI, and found it rather nice. The trouble was, I found SourceSafe itself terribly unreliable -- My source control system of choice is Perforce. My experience with the SourceSafe GUI got me thinking how good things would be there were a similar GUI for Perforce. (Perforce GUI lovers don't be offended, it's UI seems to be an acquired taste that I care not to acquire)

At first I investigated Java. Afterall, I figured it would be the best if the effort would yeild a cross-platform GUI. However, like the last two times I tried to use Java, I found it immature, slow, and painfaul to interface external code to. The fact that Perforce's p4lib is a C++ library instead of C library makes things even harder.

After deciding once again Java/Swing wasn't ready for prime time, I decided to learn and try out Visual Basic. I've learned all I ever want to know about VB5, and can safetly say I think it's a horrible language. My biggest gripes being the lack of preinitialized data syntax, first class functions (i.e. function pointers), and general brokenness of the associative array implementation (i.e. collections).

The intent of the form based UI building stuff is interesting, but it turns out much more painful than it should be. Making forms which resize well is painful, most of the property pages are severely lacking, and the basic controls are buggy. The NEXTSTEP Interface Builder is far more powerful.

All in all, it proved a great way to get 60-70% of the idea working, and it also proved incapable of handling the other 30-40% in any decent fashion.

What works

What dosn't work

Known Issues


Check out: software -- screenshots