I've been helping a local company maintain a dBase III Plus program for quite some time now. Every year it needs maintenance because it was badly configured. That's job security, sure, but the programmer in me wants to turn 'updating this' into aproject.
....like PyQt... or I can just leave it as it is.
My question is... really, where should I start? I have several options. One is trying to use the existing code but modernize it with something like xHarbour - if I can figure out just how to do that. Another is to code up a facsimile using something
I've been helping a local company maintain a
dBase III Plus program for quite some time now.
Every year it needs maintenance because it was
badly configured. That's job security, sure, but
the programmer in me wants to turn 'updating this'
into a project.
The version of clipper this is working with is...
old. Specifically, "The Clipper Compiler, Summer
'87". So before CA even got a hold of it, or it got
a version number.
Although I attempted to peruse through Harbor and
xHarbour documentation, the clipper language has
clearly evolved heavily from what this was written
in and I don't know where to start.
I've been looking for an IRC channel or any kind of
chat room where Clipper devs hang out... and all I've
found is this forum.
My question is... really, where should I start?
Another is to code up a facsimile using something like
PyQt... or I can just leave it as it is.
But not understanding all of my options really
frustrates me. Just how spectacularly different is a
'modern' Clipper program from one written in the 80s?
My question is... really, where should I start? I have several options. One is trying to use the existing code but modernize it with something like xHarbour - if I can figure out just how to do that. Another is to code up a facsimile using somethinglike PyQt... or I can just leave it as it is.
But not understanding all of my options really frustrates me. Just how spectacularly different is a 'modern' Clipper program from one written in the 80s?
BTW, whatever you wanna do next, BACKUP the original source codes!That's the least. Should use a Source Code Control program, whatever you do. What system do you use?
On Tuesday, April 11, 2017 at 9:46:32 AM UTC+2, Mr. Man-wai Chang wrote:
BTW, whatever you wanna do next, BACKUP the original source codes!That's the least. Should use a Source Code Control program, whatever you do. What system do you use?
On 11/04/2017 5:56 PM, Otto Christiaanse wrote:
On Tuesday, April 11, 2017 at 9:46:32 AM UTC+2, Mr. Man-wai Chang wrote:
BTW, whatever you wanna do next, BACKUP the original source codes!That's the least. Should use a Source Code Control program, whatever you do.
What system do you use?
I have never needed any source code control programs. Just plain simple
data compression tools and drag-and-drop. :)
On Wednesday, April 12, 2017 at 5:28:39 PM UTC+2, Mr. Man-wai Chang wrote:...
I have never needed any source code control
programs. Just plain simple data compression
tools and drag-and-drop. :)
We did that for a while but when our team got
bigger (>2 on the same product) and the
requirements for tracking and tracing of our
changes grew, that wasn't enough for us.
Especially as the request for changes got
numerous.
Oh, sure! Get professional and everything!
We did that for a while but when our team got bigger (>2 on the same product) and the requirements for tracking and tracing of our changes grew, that wasn't enough for us. Especially as the request for changes got numerous.
On 18/4/2017 10:04 PM, dlzc wrote:
Oh, sure! Get professional and everything!
It's not about professionalism. It's how you
divide the work.
Oh, sure! Get professional and everything!
The OP is maintaining an old Clipper S'87 (or dBase III+) program suite. Likely by him/herself.
Keeping the originals in one directory / zip file, backed up, should be the minimum requirement.
Then a separate directory, with extensive notes as to what the changes are, for each version you end up pushing out to the field.
But frankly, the OP needs to go to a different programming platform, something that will get him current, salable experience. Have you ever heard of "PyQt" (what he/she mentioned), or seen it on resumes you might have reviewed?
I don't know where to start.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 241:30:07 |
Calls: | 6,624 |
Files: | 12,173 |
Messages: | 5,320,139 |