A header wizard

[cncmachineguy]

I'm not sure how the parsing of the files will work, but it would for sure eliminate the need for the database. then we would have a stand alone app using the *.inc provided by microchip.

Do the inc files have all the data to do as I have "wished" for? I assume they do, but just don't know.

I will have a go at python. I would love to learn a language to write stuff for windows. I have been using ruby (very little) to write a plugin for sketchup. but at this point, i am not set on anything.

python 2.7?

Have any thoughts on work flow as I posted?

[mackrackit]

I am not so sure about a stand alone app. If it were web based then updates would be easier.

Pretty much everything about the chip is in the inc.

Python 2.6 or 2.7. Not 3.xx Many web servers have not went with 3 yet and there are just enough changes that I am aware of to cause problems. There are some app to convert 2.xx to 3.xx but I have not used them.

Work flow...
I am still thinking how to go about it.
Something like...
A script to parse the inc to place the data we want in a "standard" format for each series. Figure the configs would be a good starting/testing app at first. Take a look at the differences in the configs between a random 16F and 18F.

A new file would be created for each chip? Or a data base entry made? Or just work this into the main app directly from the inc, but that might slow things down some.

Then when a chip is selected the file is read to see if MCLR has an option (example) or internal OSC. The config select part of the app would then be populated with radio buttons to turn MCLR ON/OFF, another option for the OSC speed and type...

The app would then run through the file, with a little logic, for things like PLL USB DIV.

The completed configs would then be printed ready to copy paste.

Something like that...

[cncmachineguy]

Thanks for the python info, i will download and install tonight. I was running out of new things to learn, down to only 4 or 5.

I agree with the updating and the web access.

I also agree starting with the configs will be a great start and instantly useful.(always a good thing)

new file vs database vs direct read on the fly. hmm, I am not sure about the extra time for the direct read. do you think we are talking seconds, minutes? big pro to me for the direct read would be the .inc files are maintained by microchip, so in theory they will always be up to date.

sounds to me like the operation and use is the same as I was thinking, so I second that.

instead of copy and paste, I was thinking the file itself would just be opened and start coding from there.

[Ioannis]

Sorry if this is a stupid question,but how a web based app will find those *.inc files?

Aren't they stored locally in he MPLAB folder?

Ioannis

[mackrackit]

Sorry if this is a stupid question,but how a web based app will find those *.inc files?

Aren't they stored locally in he MPLAB folder?

Ioannis

They would have to be uploaded.

[Ioannis]

OK. I feel very stupid... Thank you!

Ioannis

[mackrackit]

OK. I feel very stupid... Thank you!

Ioannis

No reason to feel that way.
I tried finding them on MicrChip's website with the idea of scraping from there. Looks like the only place to find them is on our hard drives.

I wonder how often they are updated?