Hi.
Is there a way to include only a specific library File instead of the entire Directory?
This is extremely useful. As an example. I have all libraries in a same directory, but inside that directory I also have a main.lua file (that I use to debug the libs). So, when LuaGlider includes the whole directory, it overwrite my project main.lua with the main.lua from my Lib Directory.
Renato
Is there a way to include only a specific library File instead of the entire Directory?
This should not be too hard to do, will try to incorporate it in next update.
but inside that directory I also have a main.lua file (that I use to debug the libs)
If the only thing different between the two main.lua files is a flag (ie debug = true), you might want to create 2 different configurations and use the “Code insertion” feature to insert the flag.
So, when LuaGlider includes the whole directory, it overwrite my project main.lua with the main.lua from my Lib Directory.
Yes currently the main project folder is copied first and then the other libraries are copied on top of it. Glad it is useful to you. We should probably add a way option to reverse this behavior.
How is the user interface for the whole project manager features?
Regards,
M.Y. Developers
Thanks for the reply.
The two main.lua files are totally different. (The main.lua in my lib directory is only used to debug and improve my libs).
Yes, it would be really great if you could add the lib file inclusion in a future update.
About the rest, being honesty, I just went back to the v1.7.
I was really expecting for some time the v1.9 due to the lib feature and also debug improvements (like seeing variable value with only the cursor) that I liked very much. But, I noticed that the v1.9 has changed the default editor visual configurations (font style and size - although v1.9 & v1.7 are with the same configuration - , color of the comment line - that was green in the v1.7 and now are gray)… I spent some time trying to make it look equal to v1.7 but I was not successful, so I gave up.
Hello Renato,
I spent some time trying to make it look equal to v1.7 but I was not successful, so I gave up.
Is it just a fonts and colors issue? We can release a 1.7 theme for 1.9 if this is the case.
Regards,
M.Y. Developers
Wow. That would be awesome.
I really don’t understand why there is that difference because I checked everything: font type, size, … and they are all the same as in my v1.7 config, but the v1.9 keeps being different. That must be theme thing so…
Hello Renato,
For the font size you may want to change the zoom level via alt-scroll up/down.
I remember now why the themes were changed. In 1.7 all of our fonts and colors overrode the “All Languages” settings making it impossible to use other pre-existing netbeans themes. In 1.9 we made it inherit from the global fonts and color scheme as much as possible, and this resulted in the comments being gray for instance. That is very easy to fix though, please see the screenshot: Note that you cannot change the default themes as they are read only, you must first duplicate it and give it a name.
http://view.xscreenshot.com/69040cc4aa98b98a576ba22b63ecd0c4
Regards,
M.Y. Developers
Is there a way to include only a specific library File instead of the entire Directory?
This should not be too hard to do, will try to incorporate it in next update.
but inside that directory I also have a main.lua file (that I use to debug the libs)
If the only thing different between the two main.lua files is a flag (ie debug = true), you might want to create 2 different configurations and use the “Code insertion” feature to insert the flag.
So, when LuaGlider includes the whole directory, it overwrite my project main.lua with the main.lua from my Lib Directory.
Yes currently the main project folder is copied first and then the other libraries are copied on top of it. Glad it is useful to you. We should probably add a way option to reverse this behavior.
How is the user interface for the whole project manager features?
Regards,
M.Y. Developers
Thanks for the reply.
The two main.lua files are totally different. (The main.lua in my lib directory is only used to debug and improve my libs).
Yes, it would be really great if you could add the lib file inclusion in a future update.
About the rest, being honesty, I just went back to the v1.7.
I was really expecting for some time the v1.9 due to the lib feature and also debug improvements (like seeing variable value with only the cursor) that I liked very much. But, I noticed that the v1.9 has changed the default editor visual configurations (font style and size - although v1.9 & v1.7 are with the same configuration - , color of the comment line - that was green in the v1.7 and now are gray)… I spent some time trying to make it look equal to v1.7 but I was not successful, so I gave up.
Hello Renato,
I spent some time trying to make it look equal to v1.7 but I was not successful, so I gave up.
Is it just a fonts and colors issue? We can release a 1.7 theme for 1.9 if this is the case.
Regards,
M.Y. Developers
Wow. That would be awesome.
I really don’t understand why there is that difference because I checked everything: font type, size, … and they are all the same as in my v1.7 config, but the v1.9 keeps being different. That must be theme thing so…
Hello Renato,
For the font size you may want to change the zoom level via alt-scroll up/down.
I remember now why the themes were changed. In 1.7 all of our fonts and colors overrode the “All Languages” settings making it impossible to use other pre-existing netbeans themes. In 1.9 we made it inherit from the global fonts and color scheme as much as possible, and this resulted in the comments being gray for instance. That is very easy to fix though, please see the screenshot: Note that you cannot change the default themes as they are read only, you must first duplicate it and give it a name.
http://view.xscreenshot.com/69040cc4aa98b98a576ba22b63ecd0c4
Regards,
M.Y. Developers