FineLineIDE

[normnet]

FineLineIDE features include:
Brackets linking If-Endif, For-Next etc. with optional live auto indenting.
Two FineLineIDE's can be opened at once.
FL saves a recovery file every 30 seconds and prompt's to restore on restart if improper shutdown or crash.
Line step which allows stepping back and forth through previous lines without utilizing undo or redo.
Capable of programing a hex file from any FL programmer tab.
"My highlighter" enables user specified highlighting of specific text for color, bold, italic and underline.
"Projects" in Options enables grouping shortcuts of your project files and data.

v5.3.0
New BETA print screenshots w/FL brackets for overview of program flow.
New for MPLABX Sim on Positron compile FineLineIDE updates MPLABX's copy of .cof file else manual update required. 
Added optional retain non ASCII Text else converts to spaces on file save and paste text.
Added Assembly toolbar.
Added SaveAll toolbar.
All single characters now spellcheck ok.

No sign up or login required to download from Box.  Simply click download.
Download FineLineIDE v5.3.0
Change .xyz extension to .exe
Change .uvw extension to .bas

Norm

[normnet]

See above for download of FineLineIDE v4.7.0
Adds support for the new forum, Positron8 and Positron16 compilers.

Norm

[LeonJ]

Hi Norm,

Will Fineline run on XP as a VM on a Mac Mini under Parallels7 (older version)

Leon

[top204]

Many thanks Norm.

It is a lovely piece of coding.

[John Drew]

Very smooth and fast Norm. The help/fineline manual doesn't come up for me. The other help functions work fine, I especially like the fine lines for If/Endif. My most common error is messing nested If...Endif pairs.
The PDF operation is very fast too. Which programming language did you use?
Best wishes
John

[normnet]

Hi Norm,

Will Fineline run on XP as a VM on a Mac Mini under Parallels7 (older version)

Leon

I haven't yet tried FL in that method.

Norm

[normnet]

Very smooth and fast Norm. The help/fineline manual doesn't come up for me. The other help functions work fine, I especially like the fine lines for If/Endif. My most common error is messing nested If...Endif pairs.
The PDF operation is very fast too. Which programming language did you use?
Best wishes
John

Thanks for complements.  I see the error in opening FL's manual and will update after work today.  FL is written with Delphi in Pascal.

Norm

[John Drew]

Thanks Norm. Delphi is my language of choice too.
John

[See_Mos]

Hi Norm,  I have been testing your editor and have a couple of problems.

With the device name and XTAL in the main code I cannot make it display the SFR's or bitnames.  I tried looking in options > Proton IDE to get SFR's as suggested by the popup message box but cannot see anything obvious?

When the device name, XTAL (and required registers) are in the .INC file which I use for most of my projects compilation is OK but the editor does not pick up the device name

[normnet]

Hi Norm,  I have been testing your editor and have a couple of problems.

With the device name and XTAL in the main code I cannot make it display the SFR's or bitnames.  I tried looking in options > Proton IDE to get SFR's as suggested by the popup message box but cannot see anything obvious?

When the device name, XTAL (and required registers) are in the .INC file which I use for most of my projects compilation is OK but the editor does not pick up the device name

What is the device name?  Perhaps Microchip has changed its pattern of naming devices?  My tests show FL does find the device name in an include file.  Something must be different.

Having first obtained the device name FL searches the Options "ProtonIDE.exe path + PDS\Includes\PPI\P + device + .PPI" file for the SFR's.  If unsuccessful FL defaults to "C:\Program Files (x86)\ProtonIDE\PDS\Includes\PPI\P + device + .PPI" file for the SFR's.  If unsuccessful the popup message "Set in FineLineIDE > Options > Proton IDE to get SFR''s." appears.

What is the location of the .PPI files on your PC?

Norm

[See_Mos]

Hi Norm, thanks,

The file is one of Les' for the 18F25K20.  The PPI files are in the correct location.  I had not realized that you have to set up separate paths for the old IDE and also Positron.

The SFR's are now listed if the code file contains the device name but there doesn't appear a way to see the individual bits.

[Pepe]

With the device name and XTAL in the main code I cannot make it display the SFR's or bitnames.

[Pepe]

if device is in second line show sfr but not bitnames

[normnet]

I will see what I can do to display individual bits for the next release.  I don't remember being asked for the bits before.

Norm

[normnet]

See first post for download of FineLineIDE v4.7.1
Corrected broken FL manual link.

Norm

[See_Mos]

SFR's or bit names I found very useful in the original compiler.  It save a lot of time searching through the data sheets.

clicking on a register in the Code Explorer pane brings up the SFR viewer and then you can paste the bit names directly into the code.

[normnet]

SFR's or bit names I found very useful in the original compiler.  It save a lot of time searching through the data sheets.

clicking on a register in the Code Explorer pane brings up the SFR viewer and then you can paste the bit names directly into the code.

Looks cool!  I'm not exactly sure how to source all the data.  Perhaps its derived from the data sheets?

Norm

[Stephen Moss]

Looks cool!  I'm not exactly sure how to source all the data.  Perhaps its derived from the data sheets?

The bit names are stored in .BNF files, for Proton they are stored in C:\Program Files (x86)\ProtonIDE\Plugin\CompilerBitnames but there are only 154 so not all devices are covered. For Positron I guess it would be something like C:\Program Files (x86)\Positron\Plugin\CompilerBitnames.

There was an application written by Harm DeVeres (not sure about the spelling) that would extract BNF data from device PDF data sheet and I am currently re-writing my own BNF file generator that uses the MPLABX files as a source. The BNF files supplied with the compiler and those generated by Harm' application generally provide a description of each bit name (hover mouse over the bit name in the viewer it to see it).
 
My application will only include bit name (and register) descriptions if Microchip have included it in the source files, so most files will not have that data but if it is only the Bit Names that are of primary interest then it is not an issue.
Despite the lack of Bit descriptions my BNF files have other potential advantages...
1) Not having to download the datasheet for each device mean it would take about 90 minutes to generate a BNF file for all of the supported devices, less it if does not process device that already have BNF files. So is much faster than downloading and processing the datasheets would be.
2) My BNF files have extra data that indicate the number of bits to display in the register rows for the current device (Mechanique IDE only shows 8 regardless of register size) and how many rows to display for the register. Normally that would be 1 for a stand alone register but could be 2 or 3 for joined registers of 16, 24, 32 or 48 bits, i.e.
A 16 bit timer value in an 8 bit device uses two registers TMR1L & TMR1H but if a joined equivalent exists can be access as 16 bit register called TMR1, therefore the BNF viewer should show two 8 bit rows for register TMR1 (one row for TMR1L & one for TMR1H) whereas in a 16 bit device it would display one 16 bit row.

[normnet]

The bit names are stored in .BNF files, for Proton they are stored in C:\Program Files (x86)\ProtonIDE\Plugin\CompilerBitnames but there are only 154 so not all devices are covered. For Positron I guess it would be something like C:\Program Files (x86)\Positron\Plugin\CompilerBitnames.

There was an application written by Harm DeVeres (not sure about the spelling) that would extract BNF data from device PDF data sheet and I am currently re-writing my own BNF file generator that uses the MPLABX files as a source. The BNF files supplied with the compiler and those generated by Harm' application generally provide a description of each bit name (hover mouse over the bit name in the viewer it to see it).
 
My application will only include bit name (and register) descriptions if Microchip have included it in the source files, so most files will not have that data but if it is only the Bit Names that are of primary interest then it is not an issue.
Despite the lack of Bit descriptions my BNF files have other potential advantages...
1) Not having to download the datasheet for each device mean it would take about 90 minutes to generate a BNF file for all of the supported devices, less it if does not process device that already have BNF files. So is much faster than downloading and processing the datasheets would be.
2) My BNF files have extra data that indicate the number of bits to display in the register rows for the current device (Mechanique IDE only shows 8 regardless of register size) and how many rows to display for the register. Normally that would be 1 for a stand alone register but could be 2 or 3 for joined registers of 16, 24, 32 or 48 bits, i.e.
A 16 bit timer value in an 8 bit device uses two registers TMR1L & TMR1H but if a joined equivalent exists can be access as 16 bit register called TMR1, therefore the BNF viewer should show two 8 bit rows for register TMR1 (one row for TMR1L & one for TMR1H) whereas in a 16 bit device it would display one 16 bit row.

Good information, thanks!

[normnet]

See first post for download of FineLineIDE v4.7.2
Added bit viewer of SFR's by request.

Norm