Syntax Highlighting

[hutch--]

Coercion by wish list is never going to get anywhere, QE is a tool, not a toy. If you want technicolor, use something else.

[Ravi Kiran]

Coercion by wish list is never going to get anywhere, QE is a tool, not a toy. If you want technicolor, use something else.

I'll use np++ for enough syntax highlighting sir . Default status of QE
is enough for me and it is nice.

[daydreamer]

Ravi I suggest you open and read help files from QE,there is lot of help,about the basic opcodes/mnemonics,but also much macro help,so you easily can do much things without need to code bare metal style
invoke ,string macros,conversion macros,file read/write,memory alloc,.IF,.switch,.while,.repeat
QE also have prostart =like wizard that get you started with a skeleton program fast
 

[jj2007]

Long ago when I coded a technicolor version of a much earlier version of QE using Iczelion's technique, you had to have large word lookup tables to support the word selection and it killed exactly what I designed QE to do, be FAST.

I have asked for syntax highlighting in QE only as an option. But default status of QE is nice.

Hutch is not a friend of technicolor, and that's ok - it's a matter of taste. But qEditor does have a plugin interface, so if you can convince somebody else to give you a helping hand (HSE made already an attempt some time ago), you could add that functionality to QE. Why not?

Personally, I have enjoyed syntax highlighting for my (many) years with GfaBasic, and I appreciated that. But for me, Assembly is different. You can do all kinds of weird things when touching the bare metal, and if you want to understand later what you did a year ago, you need 1. very detailed comments and 2. individual highlighting. And no Iczelion-style automatic highlighting can do that...

[HSE]

Where did you find that one???

QE_with_colours.  A 2012 code that still is in old forum. Of course you only show the idea, it took me hours to develop something from there (mostly because I don't knew nothing of RTF).

[Ravi Kiran]

Long ago when I coded a technicolor version of a much earlier version of QE using Iczelion's technique, you had to have large word lookup tables to support the word selection and it killed exactly what I designed QE to do, be FAST.

I have asked for syntax highlighting in QE only as an option. But default status of QE is nice.

Hutch is not a friend of technicolor, and that's ok - it's a matter of taste. But qEditor does have a plugin interface, so if you can convince somebody else to give you a helping hand (HSE made already an attempt some time ago), you could add that functionality to QE. Why not?

Personally, I have enjoyed syntax highlighting for my (many) years with GfaBasic, and I appreciated that. But for me, Assembly is different. You can do all kinds of weird things when touching the bare metal, and if you want to understand later what you did a year ago, you need 1. very detailed comments and 2. individual highlighting. And no Iczelion-style automatic highlighting can do that...

Notepad++ has excellent syntax highlighting support as far as I have seen. QE is fast and simple and that's the way it has to be. Sorry for
Disturbing others about syntax highlighting in QE. But I'm expecting a
64-bit version of masm32 SDK in future.

[hutch--]

Ravi,

There IS a 64 bit version of the masm32 sdk but it is not a turnkey project as it requires the Microsoft binaries which Microsoft OWN and make available through VS2019. I have already told you that coercion by wish list will never get off the ground but it IS of continued annoyance that you keep harping on. Give it a rest or we will give you a rest.

[Ravi Kiran]

Ravi,

There IS a 64 bit version of the masm32 sdk but it is not a turnkey project as it requires the Microsoft binaries which Microsoft OWN and make available through VS2019. I have already told you that coercion by wish list will never get off the ground but it IS of continued annoyance that you keep harping on. Give it a rest or we will give you a rest.

Ok sir whenever you want .

[jj2007]

QE_with_colours.  A 2012 code that still is in old forum.

Yep, found it

However, that one used the character formatting of the RichEdit control. i.e. the same approach as RichMasm. That is fine for my taste, but OP wants something completely different: automatic syntax highlighting à la Iczelion.

In order to achieve that, you need the QE plugin interface, i.e. write a DLL that does the highlighting using the hRichEdit in-process. Quite a different story.

[Ravi Kiran]

Ravi,

There IS a 64 bit version of the masm32 sdk but it is not a turnkey project as it requires the Microsoft binaries which Microsoft OWN and make available through VS2019. I have already told you that coercion by wish list will never get off the ground but it IS of continued annoyance that you keep harping on. Give it a rest or we will give you a rest.

Nothing's wrong with QE sir. It's crystal clear.
NP++ is supporting syntax highlighting even for 64-bit instructions
and register set. I'll use it if wanted to. Sorry for disturbing you

[hutch--]

This is what Iczelion's technique looks like. Unfortunately I broke the working example about 10 years ago and could not be bothered fixing it but the basics were it used a greater than 1 meg file for all of the words to highlight which made it a lot slower than the non technicolor version. The guts of the code is a nightmare to trace and while it originally worked OK, I just did not like the effect. This is a task for someone who really wants syntax colouring, I could not be bothered as I have many other coding things to do than try and make eye candy.

[jj2007]

1 meg file for all of the words to highlight

Is that file still around? Would be very interesting...

[hutch--]

I have scoured every archive on every machine and the only version I have is the broken one. It would not be much use to you as its written in PowerBASIC. The way I did it was with a very fast hash table for the words but the file load time really slowed up the editor's load time. Copied the client area text, fed it through the colour processing and used DrawText() to display the result.

If I ever took on a task like this again, I would use a DLL that contained a tree based finite state machine which would load faster than the text file and would read faster than the hash table. The virtue of Iczelion's technique was that it did not slow up or limit the file size and the load and save text was pure ascii.

[jj2007]

C'mon Hutch, the times are changing, a 1MB file loads in less than a millisecond now. Just post it... ;-)

[HSE]

Hi Hutch!!

If I ever took on a task like this again, I would use a DLL that contained a tree based finite state machine which would load faster than the text file and would read faster than the hash table.

Sound impressive. What you are talking about?