Version Control

[sougata]

Hi,

Thanks for the good job. It is really great.

Regards

Sougata

[picnaut]

Hi Guys,

I'm working on something that's PBP specific and it's going to be great (if I can find time to do it).

On my lunch hour I whipped up a little application that is able to extract the name and file path of the .BAS (or .PBP) file that is passed to the compiler by Microcode Studio.

Basically, I created and executable called "PBPW.exe".
I then renamed the "PBPW.exe" in the PBP folder to "PBPW_Real.exe".
Then, when you compile, "my" PBPW.exe is launched.
All my program does is grab the parameters (which includes the file name and file path of the source code) and then launches "PBPW_Real.exe" (which is the authentic PBPW.exe).

That's the hardest part. The rest is easy.
I think what I'll do with my program is get it to make a copy of the source code and slap on a date and time stamp.
It will then put it in a folder called "PROGRAMNAME_Backup" (PROGRAMNAME being the actual name of the source code).
It will create the folder if it doesn't already exist.

Alternatively, I could configure it to place all backups in a central location but grouped into their respective "PROGRAMNAME_Backup" folders (as mentioned above).

If anybody else has some ideas about this, let me know.

If think it would be really cool because you wouldn't even need to configure it.
It would just run each time the compiler was run and continually create backups at each compile.

Cheers!

[Darrel Taylor]

That would be a great addition!

Anyway you can do that comparison highlighting? so you can tell what the differences are between the versions. Having 40 or 50 backup files in a folder will make it hard to tell what the changes were, and when they were made. And, if you revert back to an older file, how many recent changes will you lose.

Sometimes, just seeing what you changed will remind you enough to fix the problem, without having to revert to a previous version.
<br>

[btaylor]

I think Picnaut is on the right track here.

I have used a system similar to the checkin/checkout version control systems proposed by Michael St. Pierre before but they need personal discipline to make sure every change gets checked back in then out again so it gets its own version. For example you can check out a working version, spend days making many revisions (but not checking the file back) and then crash and lose several days work. The CVS has the 'official' version of days ago and all the subsequent steps are lost.

What I need is an AUTOMATED way of making a separately named backup EVERY time a compile is done. That way there is always a short path back to the previous state. Picnaut seems to be near to this.

I don't think it needs to highlight what the changes were, I usually write in the comments at the top of the file what I am attempting with each version. Yes there will be massive file expansion but these can be easily cleaned up at the end of the development session.

Keep it up Picnaut!!

Cheers
Brian

[mytekcontrols]

Hello Picnaut, Darrel, Brian, and Sougata!

On my lunch hour I whipped up a little application that is able to extract the name and file path of the .BAS (or .PBP) file that is passed to the compiler by Microcode Studio.

Sigh... If only my lunch hours proved as fruitfull <img src="http://www.picbasic.co.uk/forum/images/icons/icon7.gif">

If Picnaut is willing to do it. Then I'll certainly give it a whirl. I like keeping things backed-up in multiple ways, so having Picnaut's application running along side the version control system works for me. Like Brian, I've used Version Control systems at places I've worked for, so I'm rather used to using them. And by having to make it a habit, I have no problem keeping things up-to-date. However, I also run an automatic back-up app in the background, which insures that I always have a copy of my work that is no older then about 10 minutes. It doesn't do version control, but it only backs-up something that has actually changed, thereby not consuming much processing power or time.

Each method has its own benefits or strong points. It would be nice to have everything in one package, but then look what we do with PicBasic. We add some assembly code snippets, and some macros, all in an effort to make the best of all worlds.

Hey Picnaut, if you don't mind me asking, what kind of work do you do for a living? It sounds like you are very well versed in the programming world.

Oh and before I forget. Thank you Sougata for your kind words. It is appreciatted. It was rather interesting to figure out how to post the info, so that I could get the layout that was as presented (I'm sure Darrel can appreciate this aspect).

[Darrel Taylor]

Yes I can. And I must say, that's the best looking post I've seen around here. The images offset to either side, and the way the text flowed around them, very nice. You have definately "raised the bar". Which of course means, I'll have to jump over it.
<br>

[picnaut]

Hey Picnaut, if you don't mind me asking, what kind of work do you do for a living? It sounds like you are very well versed in the programming world.

Hi,

In regards to your question, I'm a hardware engineer.
I'm actually just about to jump feet first into PCB layout. I'm taking a course in Philly in November.

As for programming, from October 2001 to November 2004 I wrote automated test apps. That was a lot of fun! I got to write PC software that interfaced to a lot of other equipment (including PICs). I was able to do some embedded with that as well.

Eventually I want to work for myself full-time, but that's a little way off yet. I need to get my skill set stronger. Currently, I'm reasonably good at several things, but, unfortunately, not great at any one thing.

I see you're in California. I'm just north of the US border in Vancouver, BC, Canada.

Anyway, take it easy and keep on Pic'n!

[mytekcontrols]

Yes I can. And I must say, that's the best looking post I've seen around here. The images offset to either side, and the way the text flowed around them, very nice. You have definately "raised the bar". Which of course means, I'll have to jump over it.

Darrel,
I think you already jumped over it with some of your posts, like the LCD character generator for instance. But you did give me an idea. The only problem will be finding time to do it. Wouldn't it be cool to have a WYSIWG offline program tailored to this forum that would make creating better layouts an easy job, and not an exercise in embedding html and css via the text only editor provided. Something to think about <img src="http://www.picbasic.co.uk/forum/images/icons/icon12.gif">.

[picnaut]

What I need is an AUTOMATED way of making a separately named backup EVERY time a compile is done. That way there is always a short path back to the previous state. Picnaut seems to be near to this.

Yep!

I've actually totally changed my approach.
The program I have now simply runs in the background and checks every half second to see if something is being compiled. If it is, then the .BAS file or .PBP file get's saved in the associated backup folder with a date and time stamp as part of the file name.

There will be absolutely no interfering with the PBP software files.

I'm going to limit configuring options at first, but it will be really easy to use.

With the executable file (which I hope to attach in the next day or two) you will only have to launch it once, and then it will run every time you start Windows. It will truly be set and forget software.

Stay tuned!