For 3 years now the "official" development of LTool has been pretty much dead.
Im glad to see that people have keept using it and making there own hacks on it.
I have now began to redesign LTool, not in anyway that would change its usage or purpose.
But rather a well needed rewrite of the code. Aswell as a new design of the GUI.
I have read about improvements other people have done. Some was features that was meant to get in to LTool eventualy anyway,
but some is very nice inovative ideas that I will carefully consider.
The new LTool will be much easyer for non-coders to use, as well as offering more powerful utilitys to coders.
What i have in mind is such a big change / improvement that it will be very unpractical, if not imposible to keep backwards compability with plugins and in some cases macros. when it comes to the plugins I have made most of them so it mostly just create work for me.
But I dont mind as I had plaining on rewriting most of the plugins anyway :)
As for the macros for LtMacroPlugin thay will be very easy to port as it is only the process managment part of them that will change.
(a plugin is in general a standalone scropt)
If this sparks an idea blizzard for you, feel free to mail me with your ideas / feature requests.
Regards / Lejoni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For 3 years now the "official" development of LTool has been pretty much dead.
Im glad to see that people have keept using it and making there own hacks on it.
I have now began to redesign LTool, not in anyway that would change its usage or purpose.
But rather a well needed rewrite of the code. Aswell as a new design of the GUI.
I have read about improvements other people have done. Some was features that was meant to get in to LTool eventualy anyway,
but some is very nice inovative ideas that I will carefully consider.
The new LTool will be much easyer for non-coders to use, as well as offering more powerful utilitys to coders.
What i have in mind is such a big change / improvement that it will be very unpractical, if not imposible to keep backwards compability with plugins and in some cases macros. when it comes to the plugins I have made most of them so it mostly just create work for me.
But I dont mind as I had plaining on rewriting most of the plugins anyway :)
As for the macros for LtMacroPlugin thay will be very easy to port as it is only the process managment part of them that will change.
(a plugin is in general a standalone scropt)
If this sparks an idea blizzard for you, feel free to mail me with your ideas / feature requests.
Regards / Lejoni