A header wizard

[mackrackit]

Hello Dave,

I certainly have no objections to sharing the code for this but I haven't a clue about how to explicitly "open source" a project. I'm open to suggestions.

I'm writing the application in Delphi v4, mostly because I've been writing in various flavors of C/C++ for the past several months and I wanted (needed!) a change...8^)

Best Regards,
Paul

Not sure how the big open projects work...
I guess to do it right a license needs to be decided on, GNU?
Other than that jut make the code available someplace for folks to play with. If someone adds a function/fix then they let you know. You then work their code into a version if possible then release the updated version.
If you do not want to incorporate code from others just make yours available someplace.

If we can find others using Delphi or Python that want to help with this we could give out parts that need worked on. The "J" chip problem comes to mind.

[cncmachineguy]

It is so much fun to see such intrest in this. And to think, I started it. Its about time I had a useful idea - lol.

I am working on working on learning python so I can help somehow. Don't know if I will be up to speed in time for first rev's, but at least I may be able to help maintain it.

As for the 18xxJxx problem, my first question is how would we go about programing it without the wizard? When we know the answer to that, the wizard will just do the writing for us. I do like the idea of having the wizard "fix" the .inc file for us. That really seems like the most seemless solution. But that may be another chunk of code.

@Dave and Paul, are your programs looking at the dir to find all the available *.inc files? So updates will just automaticlly be added?

@Dave, If I am reading your code right, did you have to hard code all the cases for the config options?

[mackrackit]

@Dave and Paul, are your programs looking at the dir to find all the available *.inc files? So updates will just automaticlly be added?

Mine is. The dir is copied to the server.

@Dave, If I am reading your code right, did you have to hard code all the cases for the config options?

Nope.

file = open("%s" % subject,"r")
text = file.readlines()
file.close()

for line in text:
    m = re.match(r"_", line)   # Looks for everything starting with "_"
    if m: print line, "<br>"

So because of the "J" chips a second pass will be needed.

[cncmachineguy]

So because of the "J" chips a second pass will be needed.

Maybe better to trigger off the "J" and have seperate routines? Or is the differance not that clear in the parts?

[mackrackit]

Separate routines might be best.
Split it up between
16F
18F
18F__J

Unless I am forgetting something that should be the three basic configs.

[prstein]

It is so much fun to see such intrest in this. And to think, I started it. Its about time I had a useful idea - lol.

With great power comes great responsibility! Hope you hang in long enough to put it through thorough testing...

As for the 18xxJxx problem, my first question is how would we go about programing it without the wizard? When we know the answer to that, the wizard will just do the writing for us. I do like the idea of having the wizard "fix" the .inc file for us. That really seems like the most seemless solution. But that may be another chunk of code.

I think that has now been resolved. Thanks, scalerobotics!

@Dave and Paul, are your programs looking at the dir to find all the available *.inc files? So updates will just automaticlly be added?

Yes, that it exactly.

For fun I've attached a screenshot of the application's current status...

Best Regards,
Paul

[cncmachineguy]

With great power comes great responsibility! Hope you hang in long enough to put it through thorough testing...

I'm here for a good while. I've been coding with just assy for about 10 years as a hobby, nothing big. Finally took the plunge to do things a bit easier and buy PBP. Enrolled in a python class starts on 9/15. Decided not to go the self taught route on this one. Too many times I start to learn a new language and quit cuz something doesn't make sense to me.

As for the "thorough" testing, I will put it through all I can.

Thanks for jumping on board. Looks like a nice start you have!

[prstein]

Not sure how the big open projects work...
I guess to do it right a license needs to be decided on, GNU?
Other than that jut make the code available someplace for folks to play with. If someone adds a function/fix then they let you know. You then work their code into a version if possible then release the updated version.
If you do not want to incorporate code from others just make yours available someplace.

If we can find others using Delphi or Python that want to help with this we could give out parts that need worked on. The "J" chip problem comes to mind.

Very good, Dave.

As soon as I have the code actually doing something beyond parsing the files (shouldn't be more than a few days) I'll set up two files on a server, one of just the executable and the another including all the source. I'll administer the overall "broad release" version and incorporate any improvements/fixes created by others.

Best Regards,
Paul