Is there a way to make Galaxy scripts converted to Triggers. Easier way to read that scripting..
Or just its possible from Triggers to Galaxy scripts.?
GUI works differently in some aspects which would make it hell already, but given the fact the Galaxy can just do more things than GUI it's basically impossible.
Even if it were possible it would be extremely difficult as everyone scripts differently. IMO, it wouldn't be very feasible even if they could do it. Trigger > Galaxy script has a certain structure to it, the way the functions are ordered and such, but very often it is not generated in the most elegant manner. Galaxy script would likely be far more complex, thus it would be difficult to accurately parse it to trigger form.
@HellGateSc2: Go
It's not possible because reverse compilation is an almost impossible problem, Blizzard being lazy or not.
GUI triggers are compiled to Galaxy. Decompiling the Galaxy source to triggers (essentially another programming language) is extremely hard and would be too naive if implemented.
It's definitely possible to do Galaxy -> Triggers, that's how the Trigger Editor works. It converts the GUI Triggers to Galaxy when you save your map. When you come back and load your map, it has to convert that Galaxy to Triggers. However, it works a little different than just a straight conversion, there are two extra files: Triggers and Triggers.version files. They store the references to triggers within the games libraries and I believe the editor/map version.
Actually, the XML files define a syntax/grammar tree which is fed into the generator.
The only parsing done from this file is for UI initialization.
The code itself is just generated everytime you save the document.
Although I think Sixen's premise is wrong, I do think it's theoretically possible to convert Galaxy to triggers.
It wouldn't be a perfect 1:1 conversion but you could easily make valid GUI triggers that did the same thing in a lot of cases.
It's also theoretically possible to convert Assembler into Common English. However, I believe the issue is that in both cases, it would require much more effort to create a program that does the conversion automatically than to simply manually recreate/convert specific code from galaxy to GUI (or assembler to english) whenever it's really needed.
Then again, a good AI program could solve the issue entirely. Hmm.
On-topic: It's not impossible, but definitely not practical, and for the reasons stated above will probably never be done.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Is there a way to make Galaxy scripts converted to Triggers. Easier way to read that scripting..
Or just its possible from Triggers to Galaxy scripts.?
not possible...
may there would be a way but blizzard is lazy :P
GUI works differently in some aspects which would make it hell already, but given the fact the Galaxy can just do more things than GUI it's basically impossible.
@TwoDie: Go
Even if it were possible it would be extremely difficult as everyone scripts differently. IMO, it wouldn't be very feasible even if they could do it. Trigger > Galaxy script has a certain structure to it, the way the functions are ordered and such, but very often it is not generated in the most elegant manner. Galaxy script would likely be far more complex, thus it would be difficult to accurately parse it to trigger form.
@HellGateSc2: Go It's not possible because reverse compilation is an almost impossible problem, Blizzard being lazy or not. GUI triggers are compiled to Galaxy. Decompiling the Galaxy source to triggers (essentially another programming language) is extremely hard and would be too naive if implemented.
-
View User Profile
-
View Posts
-
Send Message
ModeratorsIt's definitely possible to do Galaxy -> Triggers, that's how the Trigger Editor works. It converts the GUI Triggers to Galaxy when you save your map. When you come back and load your map, it has to convert that Galaxy to Triggers. However, it works a little different than just a straight conversion, there are two extra files: Triggers and Triggers.version files. They store the references to triggers within the games libraries and I believe the editor/map version.
@Sixen: Go
Actually, the XML files define a syntax/grammar tree which is fed into the generator. The only parsing done from this file is for UI initialization. The code itself is just generated everytime you save the document.
@caspersc: Go
Although I think Sixen's premise is wrong, I do think it's theoretically possible to convert Galaxy to triggers.
It wouldn't be a perfect 1:1 conversion but you could easily make valid GUI triggers that did the same thing in a lot of cases.
@MotiveMe: Go
It's also theoretically possible to convert Assembler into Common English. However, I believe the issue is that in both cases, it would require much more effort to create a program that does the conversion automatically than to simply manually recreate/convert specific code from galaxy to GUI (or assembler to english) whenever it's really needed.
Then again, a good AI program could solve the issue entirely. Hmm.
On-topic: It's not impossible, but definitely not practical, and for the reasons stated above will probably never be done.