CompilerOptions Suggestions

Forum for suggestions and new feature requests for SDStudio Design Environment
Post Reply
User avatar
Louise
Registered User
Posts: 15
Joined: Thu Dec 14, 2017 4:53 pm
Location: SDS-LUA-PB

CompilerOptions Suggestions

Post by Louise »

Hi dear Serkan,
A few ideas for compiler settings :

1- Ability to Create and run Executable with command-line

2-Ability to choose the engine features
for Example :
How to link the engine to the program ( use Static or Dynamic Lua engine)
Select the type of Lua engine (Standard, Luajit and more ...)

3-Ability to Enable modern theme support.(Adds support for skinned windows on any windows version.)

4-Ability to ON/OFF Unicode and RTL Support.
User avatar
Serkan
Developer
Developer
Posts: 214
Joined: Thu Jul 04, 2013 8:44 pm
Location: Windows.h
Contact:

Post by Serkan »

Louise wrote: Tue Dec 19, 2017 7:05 pm Hi dear Serkan,
A few ideas for compiler settings :

1- Ability to Create and run Executable with command-line

2-Ability to choose the engine features
for Example :
How to link the engine to the program ( use Static or Dynamic Lua engine)
Select the type of Lua engine (Standard, Luajit and more ...)

3-Ability to Enable modern theme support.(Adds support for skinned windows on any windows version.)

4-Ability to ON/OFF Unicode and RTL Support.
Hi Louise
First of all ,Thanks for your interest and participation.

1: We can add a field to project settings dialog to pass preview exe on debug/previewSD Studio creates different executables in debug/preview and publish modes, it adds debugger, code to exe to interact with the IDE when something went wrong, for example, when an error occurs in test application, an error message appears in debug window of the IDE and when you double click on an error message, you will be navigated to the line of code which has caused that error ,

In addition, you can send Trace messages to IDE, to print value of a variable to debug window, or just to indicate an event has occurred

Note : follwing is just an idea and does not exist ,but can be implemented later
since the test application can send info to IDE, this can be implemented to opposite direction, so you can change the value of a variable or call a function from within the test application to gain more control over test application, this can also be used to stress test preview application or maybe automate some tests to avoid manually doing that
2: You can select both static or dynamic linking with Lua (this is optional) but you can only use official Lua libraries shipped with SDStudio

3: SDStudio will provide Windows common controls with native windows theme , in addition extended controls
but this extended controls will mostly use native theme with some customization options

End user can use a third party theme library to apply desired look,

Or you can create your own extended controls with desired look , SDStudio will provide tools to create your own custom controls

4: At first stepts ANSI/Unicode was optional ,but this is no longer available ,SDStudio will build Unicode applications always
SDStudio will use UTF-8 therefore this can easily be transferred among Lua and Runtime ,
SDStudio will provide a rich string class and ,when you need an ANSI version of a string ,you can easily convert it and then pass to where you want
this can be a third party dll , or lua module

Application wide RTL support will be available , and maybe this can also be available in runtime , switching between RTL / LTR
User avatar
Louise
Registered User
Posts: 15
Joined: Thu Dec 14, 2017 4:53 pm
Location: SDS-LUA-PB

Post by Louise »

You've already thought about everything. Is admirable.
Post Reply