(if CGI, preferably in Perl) …interfacing with a mysql db? anyone?
… in perl or php, interfacing with a mysql db? anyone?
I have no idea what you just said, but if you going to build this training log tell me now because I am about to switch to BT’s version. If there is going to be one on here I will wait 
chris
“if you going to build this training log tell me now”
there’s going to be one here.
Any idea on time line?
chris
Hi,
I’m building one right now. In PHP with Polar HRM-format support. I have also done a little standalone java app that searches the harddrive for HRM files and uploads them to the server. Polars HRM format is quite good to use since most application can export to it.
BR David
I don’t think it should take more than a couple of weeks full time for somebody to get a basic log up in perl + mysql, the guts are not that hard, the issue is more what kind of interface you want: if you want something 2.0ish with ajax etc on the client side to make it look nice (say, ‘draw’ traning blocks instead of typing in the numbers etc.) it will take a bit longer. Fortunately nowadays there are decent frameworks for perl for this (say, mason)
(this is my qualified professional opinion of course, been doing perl/db stuff, among other things of course, since 1998 here… also as everything the devil is in the details, so if you’re going to hire somebody to do this make sure you have a very firm idea in terms of features and functionality, given how high profile ST is I assume you’re going to want something good from the beginning, otoh maybe it’d make sense to do something a bit more off the cuff in a couple of weeks and go by the feedback users provide)
Most online logs are far, far too complex for my needs, so I figured I’d whip up my own in Django . I planned on it taking about 1 or 2 hours to actually build and then another few hours for me to tweak the design to my liking.
People still write CGI programs? Is this 1996?
Much better off with PHP or ASP.
“Much better off with PHP or ASP”
php works for me, asp does not. it’s got to integrate with what we’re already doing.
People still write CGI programs? Is this 1996?
Much better off with PHP or ASP.
you’re kidding right? sometimes the best tool for the job is still perl+cgi (especially if updated with a decent framework), just because it’s not sexy and the latest buzzword doesn’t mean it’s not good… and believe me, I still see a lot of perl (and C) in my professional life even nowadays (along with python, java, etc. of course)
PHP can be ok as well, but I don’t think it’s as flexible personally.
Any idea on time line?
chris
Days, months, years from now? Throw me a bone so that I don’t have to switch all my stuff over to BT only to find out you started one here the next week
chris
I’ve debated building one and started and stopped building it a couple of times.
I’ve got a DB schema aroudn someplace - some basic code and lots of concepts in my head.
Php based to a mysql backend - not CGI though, just straight up PHp with smarty is my experience and plans.
Done several similar projects.
The building part is the easiest part, though it requires some programing ability. Throwing in some AJAX, getting some device data uploaded and analyzed, doing charts - no problem.
The hardest part, however, is putting together the design document and actually requires no programing ability, just a lot of sense and knowing what you want. Do you have this yet?
Actually the design document isn’t too bad IMO - just standard PM stuff - it’s the freaking interface/frontend that always drives me to give up when i undertake projects like this for myself.
PITA
I actually think it would be cool if we organized a sourceforge type project for this. Throw up a subversion server and start handing out assignments, cross checking work etc.
I’ve got a couple heavier duty servers on a big pipe that I’d volunteer to host a development/testing version of this as well as the subversion repository.
I disagree pretty strongly about the design document being easy. It is critically important and too often people get busy building before knowing exactly what they wanted when they started - or even having a good idea.
A proper design document has diagrams of what the screens will look like, discuss every feature, and have an idea about keeping things flexible for unknown unknowns.
I don’t know how ambitious Mr. Empfield wants to be with this project. If he wants to clone coolrunnings - that would be pretty easy since you just look at what they have and copy it.
Regarding staffing, I’ve done a few projects like this and it requires two teams: art and developers. Both get started with the design document and then merge their work together. At least for me, this is very easy once the design doc goes gold.
Dan - take a look at what the guys have done over at Buckeye Outdoors. Jodi turned me on (to it, ;-)) and I’ve really liked it. And I believe they might have what you’re looking for. A lot of the folks in my tri club are now using this as it is both SIMPLE, but does some very nice things.
imagine the timing… i started working on a personal one for access 2003 just this morning (before i saw dan’s post).
i’d be happy to nitpick whatever someone else puts together though.
People still write CGI programs? Is this 1996?
Much better off with PHP or ASP.
.
I’m old school still write my cgi’s in 8080 assembly…TAKES a long time to punch in the hex codes on the front panel switchs
and it all fits in 1024 bytes of core memory…
php can still run as cgi… cgi is just a program it can be in c,c++,java,php,perl heck even fortran if your really good.
OF course NEver NEver use COBOL…
I disagree pretty strongly about the design document being easy. It is critically important and too often people get busy building before knowing exactly what they wanted when they started - or even having a good idea.
A proper design document has diagrams of what the screens will look like, discuss every feature, and have an idea about keeping things flexible for unknown unknowns.
I don’t know how ambitious Mr. Empfield wants to be with this project. If he wants to clone coolrunnings - that would be pretty easy since you just look at what they have and copy it.
Regarding staffing, I’ve done a few projects like this and it requires two teams: art and developers. Both get started with the design document and then merge their work together. At least for me, this is very easy once the design doc goes gold.
Agree 100%.
Yes, someone can hack something together in a few hours/days for their own use. But when you start having 100’s of people banging away, using it in ways you’d never image, all hell WILL break loose.
Slowtwitch is a slick, professional looking site. Building an online log from scratch will require 100’s of man hours, not 10 or 20.
Stop talking about CGI (or not). Get the requirements doc down 100% before allowing or paying a penny for any programming.
Contract out and spend a grand or 2 getting the requirements right. You will be rewarded many times over before the project is done.
I just checked out the Buckeye Outdoors log…very slick. All the info you need and nothing you don’t. I would love to have something similar to this here on ST.