38 replies to this topic

[Beege]

Last Update - 3/18/2012

Here are a few functions that will take any Autoit code and convert it to RTF format with AutoIt syntax highlighted.
The code can be saved or applied right to the RichEdit control you are working with.

Special thanks go to MrCreator. A good amount of ideas for different parts of the code and regular expressions came from studying his Autoit Syntax Highlight for HTML\BBCode. Viewing how he handled certain situations was very helpful. Thanks to Robjong also for feedback on some of the SRE expressions.

This latest updated was all about speed. With the previous version, it was very slow when dealing with large udfs like Winapi.au3 for example. This new version gets it done in around 13 seconds which I was very happy with. I also broke out all the colors in the RTF color table making them easy to modify if you want. Same with font and font size. One other addition is the update function which can be used to show progress as the conversion is happening.

Please let me know if you have any problems. Thanks

Update: 3/18/12

• Got more help from Robjong with some of the regular expressions. Thanks again!
• Fixed crash when loading large file.

Change Log:

Spoiler

Update: 3/18/12

• Got more help from Robjong with some of the regular expressions. Thanks again!
• Fixed crash when loading large file.

Update: 2/19/12

• Added new function _RESH_SetColorTable() that allows the user to change the color table to there own preference.

Update: 2/18/12

• Rewrote for speed. Also broke out colors and fonts from RTF header making them much easier to modify.

 RESH.zip   17.51KB   245 downloads

 RESHv2.zip   21.1KB   120 downloads

 RESHv2.1.zip   22.39KB   155 downloads

 RESHv2.2.zip   24.44KB   392 downloads

Edited by Beege, 18 March 2012 - 06:13 AM.

[Beege]

Updated this... because its so popular.

[guinness]

Very nice indeed. Have you thought about adopting the latest style? (If you don't ask you don't get!)

[Beege]

Thanks Guinness. Yes I have thought about it. I've been wonder weather I should have preset styles that the user could switch, or create a function that allows them to set the colors to whatever they want. I think just passing an array of hex color values would be easy enough but wasnt sure which route I should go. What do you think?

[CaptainClucks]

The regular expression use in this is nutz, awesome work!

[guinness]

What do you think?

An array should be fine. You've also got me hooked on using associative arrays.

[Beege]

The regular expression use in this is nutz, awesome work!

Thanks

An array should be fine.

Array it is then.

You've also got me hooked on using associative arrays.

Their addicting! It seemed the more I started using them the more situations started poping up that fit them perfectly! Plus their pretty fast!

Edited by Beege, 18 February 2012 - 01:07 PM.

[Beege]

Updated with new function to change color table to whatever you want.

[guinness]

Updated with new function to change color table to whatever you want.

Sweet!

[Beege]

Thanks!

Before I start writing something, do you have or know of any snippet that will extract the color values from the Scite User Options file?

[AZJIO]

Beege

Before I start writing something, do you have or know of any snippet that will extract the color values from the Scite User Options file?

"Case $Import" in CreationTheme

([()[]<>.*+-=&^,/]) = ([][()<>.*+=&^,/-])

[Beege]

Thanks AZJIO, I came up with the following:

#include <array.au3>

Global $aCurrentColors = _GetCurrentSciteColors()
_ArrayDisplay($aCurrentColors)

Func _GetCurrentSciteColors($sSciteUserPropPath = '')

     If Not $sSciteUserPropPath Then $sSciteUserPropPath = @UserProfileDir & 'SciteUser.properties'
     If Not FileExists($sSciteUserPropPath) Then Return SetError(1, 0, 0)

     Local $sSciteUserProps = FileRead($sSciteUserPropPath)
     If @error Then Return SetError(2,0,0)

     Local $aUserColors = StringRegExp($sSciteUserProps, '(?mi)^style.au3.(?:d|10|11|12|13|14|15)=fore:(#[0-9a-f]{6}).*$', 3)
     If @error Then Return SetError(3, @error, 0)

     Return $aUserColors

EndFunc   ;==>_GetCurrentSciteColors

([()[]<>.*+-=&^,/]) = ([][()<>.*+=&^,/-])

Thats partly true but I think some of those characters would need need to be escaped. I would surely think '^' would because thats an operorator for sets.

Edit: Changed expression to more secure version. Thanks AZJIO

Edited by Beege, 19 February 2012 - 08:48 PM.

[AZJIO]

screenshot

(?mi)^style.au3.(?|10|11|12|13|14|15)=fore:#([0-9a-f]{6}).*$

# au3
style.au3.0=fore:#72ADC0   # White space
style.au3.1=fore:#71AE71,italics   # Comment line
style.au3.2=fore:#71AE71,italics   # Comment block
style.au3.3=fore:#C738B9   # Number
style.au3.4=fore:#AAA6DB   # Function
style.au3.5=fore:#0080FF   # Keyword
style.au3.6=fore:#FF46FF   # Macro
style.au3.7=fore:#999999   # String
style.au3.8=fore:#FF8080   # Operator
style.au3.9=fore:#D29A6C   # Variable
style.au3.10=fore:#EA9515,bold   # Sent keys
style.au3.11=fore:#F000FF   # Pre-Processor
style.au3.12=fore:#0080C0   # Special
style.au3.13=fore:#7D8AE6,bold   # Abbrev-Expand
style.au3.14=fore:#0080FF,bold   # Com Objects
style.au3.15=fore:#72ADC0   # Standard UDF's

Edited by AZJIO, 19 February 2012 - 08:25 PM.

[guinness]

Beege,

I tried your version of _GetCurrentSciteColors which returned only 2 results. Then I substituted your SRE for AZJIO's and it returned 15, which looking at au3.properties is correct. Nice function by the way, I'll be saving that to my functions folder.

[Beege]

Yup that works too. Only I would need the # included for the new function.

(?mi)^style.au3.(?|10|11|12|13|14|15)=fore:(#[0-9a-f]{6}).*$

[Beege]

Beege,

I tried your version of _GetCurrentSciteColors which returned only 2 results. Then I substituted your SRE for AZJIO's and it returned 15, which looking at au3.properties is correct. Nice function by the way, I'll be saving that to my functions folder.

Ya my version is a little two specific. AZJIO's version will be more secure for property files that might have been modified or slightly different in some way. Ill update my previous post.

[Beege]

screenshot

Is that PCRE engine? I'm confused why the doc states:

 Note that special characters do not retain their special meanings inside a set, with the exception of , ^, -,[ and ] match
the escaped character inside a set.

[CaptainClucks]

I was using the new version and suddenly BAM, right when it was about to load the large UDF into the edit control it gave me this.

Spoiler

I'm on a x86 acer aspire one d250 with win xp if its of any importance.

Edited by THAT1ANONYMOUSEDUDE, 19 February 2012 - 09:56 PM.

[Beege]

The pic you posted is not visible. The code you were trying to highlight is the only thing that might help me figure out what happened..

[CaptainClucks]

Hmm, really? the image isn't visible? damn, I need to find a better site then.

Anyway, the image doesn't matter, what matters is that AutoIt is crashing on my PC when loading anything above about 2k or 3k lines of script, and aside from that, on your 3rd version, It would be nice if we could just copy and past the result as in your second version.

Also, AutoIt is crashing no matter what version I use, but I haven't tried the first file you posted, just v2 and v2.1.

Must be something that has to do with running on a crappy laptop.

Edited by THAT1ANONYMOUSEDUDE, 19 February 2012 - 10:13 PM.