If you are having performance issues

Glider (IDE)
#1

@Everyone,

For those experiencing performance issues please help us by answering these 2 questions:

  1. How large are your lua files (in lines of code)? 
  2. What platform are you running?

We need to know because the fix for this issue is non-trivial but will allow Glider to edit very large files (>2000 lines.) 

Regards,

M.Y. Developers

#2

  1. my main lua files usually have 2-3k lines of code, other lua files in my projects have 300-1000 lines of code

  2. I’m using Glider on a “Early 2011” MacBook

#3

Hello Canupa,

Thanks for the info. When we were at the drawing board with Glider 1.9 we realized there was a tradeoff between IDE features and maximum lua script size. We figured that there already exist excellent text editors to edit really large files if you need to. We set a target maximum operable file length of around 2k lines of code. This limit is much higher in windows btw because of the Java situation. We figured that any file larger than 2k lines should be refactored into more manageable modules, but this is our opinion and is up for debate. If large file support is really required and justifiable then we will implement the incremental parsing feature we were talking about. This will slow us down from getting ot other features such as integrated profiler, unit test runner, etc. 

Please note that your overall project can be as long as you like, just the current file you are actively editing should be under a said limit. This is because parsing through a file and analyzing the code is a O(n) problem and the delay becomes noticeable after about 2k lines.

Regards,

M.Y. Developers

#4

  1. my main lua files usually have 2-3k lines of code, other lua files in my projects have 300-1000 lines of code

  2. I’m using Glider on a “Early 2011” MacBook

#5

Hello Canupa,

Thanks for the info. When we were at the drawing board with Glider 1.9 we realized there was a tradeoff between IDE features and maximum lua script size. We figured that there already exist excellent text editors to edit really large files if you need to. We set a target maximum operable file length of around 2k lines of code. This limit is much higher in windows btw because of the Java situation. We figured that any file larger than 2k lines should be refactored into more manageable modules, but this is our opinion and is up for debate. If large file support is really required and justifiable then we will implement the incremental parsing feature we were talking about. This will slow us down from getting ot other features such as integrated profiler, unit test runner, etc. 

Please note that your overall project can be as long as you like, just the current file you are actively editing should be under a said limit. This is because parsing through a file and analyzing the code is a O(n) problem and the delay becomes noticeable after about 2k lines.

Regards,

M.Y. Developers