Mike Lobanovsky wrote:Codeman wrote:another cool thing i am working on is to externalise the compilation part using my 2exe.fbs (i am adding gui part) to compil scripts allowing the user to choose some compilation options like exe name, compression, code optimisations (using apurate), and so on..)
another advantage of doing this s that we could update the res of the compiled exe , changing the exe icon,version infos ,descriptions ect...
(mimics a real compiler )
Very interesting! That's not mimicking, that's real resource handling, but only not at a pre- but at a post-compilation stage. I personally don't care if I handle the resources this or that way.
I'm only doubtful about compression: AFAIR the script stud is inserted already compressed so is there any way to re-compress it EXCEPT that you know the decompilation password or if the source is not password-protected?
If you go onto that way, please wire your idea with mine that simply wants to make 'real' FBSL resource objects files with the use of XML!
An XML file will contain the main script + other resource files : icon, declares, classes...
I think we should merge our ideas to make a first attempt that will 'build' FBO (FBSL Object files) thanks to XML.
Once this step OK and correctly working, I'll port this idea into FBSL.EXE and then compress, crypt & co to have a 'compiled' executable containing more than an actual and unique script file!