BLIde Plus SP1 Release Candidate available

BlitzMax Forums/BlitzMax Programming/BLIde Plus SP1 Release Candidate available

ziggy(Posted 2011) [#1]
As some of you already know, BLIde is going to get a massive update in the form of a "service pack". This big update will be available to all BLIde Plus users at the beginning of February using the regular BLIde Plus update mechanism. This will be the first major BLIde update since 2007. That’s why I've considered this update a ‘service pack’.

This first service pack will update several areas of the BLIde interface, will improve accessibility, will fix completely all the CSC errors that are seen randomly on some computers after a regular update, and will also benefit of some of the new developments we have done for the new Jungle Ide engine.

This service pack will also make BLIde use several threads to separate lexical and syntactical parsing on several supported languages such as C#, ANSI C, BLIde SDK, etc. Obviously this service pack will also include all the accumulated updates and fixes. Additionally, the updating system will be completely renew to a faster, smaller and more reliable system we’ve been developing using Inno Setup.

Also, some improvements and fixes to intellisense and other areas have been put into this big update.

The news is that this service pack is available in the form of a Release Candidate to all BLIde Plus users here:

http://www.blide.org/plus/blide-sp1-installer.exe

You'll have to provide your registration email and password to get the installer.

As this is a Release Candidate, plese provide feedback of any issue (if any) you may find in the update process.

Hope you find it useful!


SpaceAce(Posted 2011) [#2]
Edit: Nevermind, I got into the customer area.

Last edited 2011


Tim(Posted 2011) [#3]
hey man, just bought it 2 weeks ago,
its an incredible sweet and beautiful solution, just like visual studio.
thumbs up!


beanage(Posted 2011) [#4]
Thanks man!

Does this also fix the Xor-Intellisense bug?


ziggy(Posted 2011) [#5]
Does this also fix the Xor-Intellisense bug?
Wich Xor bug?


Htbaa(Posted 2011) [#6]
How is this really different from the latest version? Or are these all new fixes and features?

Also, didn't BLIde get a major update somewhere last year with some big engine rewrites?

Anyway, good work. BLIde sure is the way to go for BlitzMax coding.


ziggy(Posted 2011) [#7]
Hdidn't BLIde get a major update somewhere last year with some big engine rewrites?

No, or not at this level. You can see here the complete changelogs for official releases: http://www.blide.org/updates/oldchangelog.html
There have been some engine updates, but not at this level.

One of the biggest changes is related to how BLIde handles its internal parsing. It's now parallelizing several task using threads. Also, the whole renderer system has been upgraded to the QWhale engine 1.6.1 which introduces several improvements in performance.
Then, all the layout system has been updated too to take into account several accessibility settings in the user system, and also looks much more native on modern windows (Uses native fonts when possible, takes into account DPI scalling, etc).
Also, some issues related to text being overwritten by Autolists have been ironed out a lot (I think completely). Additionally, the search & replace algorithms is now context based, so it plays nicer and avoid unneeded cursor "jumps" between operators.
Additionally, all the setup and auto-update system BLIde Plus uses has been completely replaced by a new one and now BLIde does not rely any more in the Windows Installer Framework.
Also, a bug known as the "CSC.EXE" bug that was making BLIde work wrong sometimes when serializing data after an update,has been also fixed.
This new update will also facilitate a lot the transition of BLIde from .net 2.0 to .net 4.0, which is something that will come very soon.


ziggy(Posted 2011) [#8]
Small update commited to the users of the Service Pack 1 RC. this update should improve rendering of autolist and quickinfo tips. Now those popup windows are also compatible with accesibility and GDI scaling, as the rest of the IDE. They also render faster and nicer with ClearType fonts in windows 7 and vista. This update also fixes a very small memory leak on the JavaScript parser.
All users of the SP1 RC1 will get the update automatically.


beanage(Posted 2011) [#9]
Thanks!


Tommo(Posted 2011) [#10]
"Fold at defination level" not working since 10.12.12A.
Please fix it. Thanks!


ziggy(Posted 2011) [#11]
"Fold at definition level" not working since 10.12.12A.
Please fix it. Thanks!

Fixed for the next update, wich will come in some days time with some additional fixes/improvements. Thanks for the bug report!


ziggy(Posted 2011) [#12]
BLIde Plus update available (11.03.0501 SP1)
This is the changelog:
BLIde version 11.03.0501 SP1

[*] Fixed an ussue with the Find&Replace dialog that was causing a major slowdown on complete Find & Replace operations on big files.

[*] A "Replace all" operation is now consuming a single "undo" step

[*] The close button of each document is now placed at each tab, instead of being located at the top right corner. This is cutomizable on the preferences dialog.

[*] Added a context menu on each tabbed document that allows the user to close the document easilly.

[*] Improved the fade in/out effect used to prevent flickering, so it is faster and uses less GDI resources

[*] Fixed an issue that was making the "Jump to definition" not work properly for local variables that had unary operations with the ":" symbol.

[*] Fixed an issue that was making BLIde consider the XOR token as a valid logical operator

[*] Fixed an issue that was making BLIde show folding nodes, after a document reload, when the outlining property was set to False

[*] Modified internal text parser to use new optimized string manipulation system (originally developed for Jungle Ide). Modules parsing is a bit faster now.


The update is available using the regular updates system.

In case you're not too busy with Monkey, enjoy it!

Last edited 2011


GfK(Posted 2011) [#13]
The close button of each document is now placed at each tab, instead of being located at the top right corner
YAY! :D


Czar Flavius(Posted 2011) [#14]
If I put this
Local t:TTerrain
and jump to definition of TTerrain, it is still taking me back to the same line I just clicked on and not TTerrain.