Hi, I got some problems with the totally bugued Blizzard's import/export library system.
Well, let's say I have two libraries.
First of all, I want to know how to update a library by importing a new version. If I use functions of this library in custom triggers, then I REALLY don't know how to process because if I delete the old library, then it will delete all the parts of the custom triggers using functions of the library. Have you any idea on how to fix that problem, I mean upgrading the old version to a new one ?
Second thing, this is approximatively the same. If my second library uses functions of the first one, and if I import the two libraries in a new map, then the second will not recognize the functions of the first one, even if I changed the first library ID before. -_-'
I really don't understand Blizzard, they want us to use GUI instead of Galaxy (but I'll keep using pure Galaxy, be sure), and they give bad systems with so lots of bugs...
Well I hope someone will be able to answer my questions, if not I'll not keep coding with GUI anymore, I just wanted to share my systems with everyone, but with this difficulties, why should I ?
As for the bugs, the game isn't even out, let alone the map editor. They don't even have all the units in, don't judge it so fast.
Plus I doubt that they want us to STRICTLY USE THE GUI. I think its more of a tool that lets the people who don't know how to properly code work on maps as well.
Yes I hope the release will be something more... finished. :)
And I keep thinking they want us to use GUI, or at least during the BETA, because there is no easy way to code with pure Galaxy... I'm coding with Galaxy, but honnestly, it's just boring...
Plus I doubt that they want us to STRICTLY USE THE GUI. I think its more of a tool that lets the people who don't know how to properly code work on maps as well.
Not really. I don't know about you guys, but my .galaxy export is 7902 lines long already.
Writing pure code isn't a problem for me, but I find the GUI (even with bugs) to be a VERY efficient tool.
Not really. I don't know about you guys, but my .galaxy export is 7902 lines long already.
Writing pure code isn't a problem for me, but I find the GUI (even with bugs) to be a VERY efficient tool.
You like to import your file each time you wanna test ? O_O
Sorry but I don't, it's a waste of time, and it's really, realllllly boring.
... import my file? Read again, I'm only using the GUI :)
I'm just saying my raw code is huge when I look at it, and writing it the "cool" way would have taken a lifetime.
People tend to consider the GUI as a dirty/nooby way to create maps for some reason. Wrong.
It's an excellent, fast tool.
Well it's true, since StarCraft II, the GUI editor is really powerful, but some things are not included in (like some functions you can only use as an action). I don't guess the GUI is a "nooby" tool for creating map, but think that coding in pure code is not really slow, personally I write my Galaxy code 10x faster than with GUI, probably is it really faster when you use to work with one of the two. About your 7900 lines, it makes me laugh because I think that all Jass/Galaxy people know that the transformation from GUI into Jass/Galaxy is just something funny. I don't guess writing your code in GUI will increase the number of lines a lot, but the code length and number of characters is normally increased, because of the funny code lines like :
if !(!(MyBoolean == False)) {
}
else {
blabla;
}
Well that's a choice to code with Galaxy or GUI, but some good reasons to code with Galaxy are : with Galaxy, you can do everything you can do in the editor, and not be blocked by a little thing GUI doesn't allow ; and the Galaxy language will soon be "upgraded" with Andromeda, something I think the GUI-users will never be able to use (but I guess for you, I don't know the future ).
To go back to my thread subject, I've taken the choice to share my Galaxy systems with the GUI users, a thing that I think should be good for everyone. But with the problems I encountered with the libraries system, I'm not sure I'll keep to say the GUI is a good thing, if Blizzard doesn't correct what I said. ^^
I don't really care about code "condensation" or the number of lines itself, just sayin' :)
Writing pure Galaxy is generally slower, but that's really not my point. I spend most of the time planning features, not writing them, and I've always programmed like that in the past so raw code doesn't really scare me. Still, this time the GUI is extremely comfortable for a number of reasons, notably for handling variables and having a VERY clear picture of what you are looking at, while it doesn't really miss any important Galaxy feature.
Don't know what you mean with "some functions you can only use as an action" since actions ARE void functions with a different name. They compile like that. Also, everyone keeps spitting these "things that the editor doesn't allow", and I'm wondering, because I have yet to find something that couldn't be done there. Feel free to correct me, this is not my GUI crusade or anything, I'm just curious :)
For example, a day I had difficulties to use the 'CreateTrigger' function, of course you can't in GUI, but that stopped me, so I had to use custom script. ^^
That's something. Can't really picture a situation where I would need to dinamically create triggers though, what were you doing exactly? I'm pretty sure there's another easy way to achieve that in the GUI ^^
Yes it's true, in my situation I could do it in GUI, but not with the same way I had done in Galaxy, I would have to change a function and its parameters, and that was perturbing me. Anyway, I'm sure I can find other examples where GUI shows its limits. :D
But it's not the topic to speak of this, I like to discuss with you because you are not that kind of people saying "GUI IZ DA LIFEEE !!§§§11!!§", you explain why you like it, and why you don't want to use the pure Galaxy, and I understand and respect you. :)
So, if by using the GUI more than me, you find a solution to my "library problem", PLEASE TELL ME ! :D
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hi, I got some problems with the totally bugued Blizzard's import/export library system.
Well, let's say I have two libraries.
First of all, I want to know how to update a library by importing a new version. If I use functions of this library in custom triggers, then I REALLY don't know how to process because if I delete the old library, then it will delete all the parts of the custom triggers using functions of the library. Have you any idea on how to fix that problem, I mean upgrading the old version to a new one ?
Second thing, this is approximatively the same. If my second library uses functions of the first one, and if I import the two libraries in a new map, then the second will not recognize the functions of the first one, even if I changed the first library ID before. -_-'
I really don't understand Blizzard, they want us to use GUI instead of Galaxy (but I'll keep using pure Galaxy, be sure), and they give bad systems with so lots of bugs...
Well I hope someone will be able to answer my questions, if not I'll not keep coding with GUI anymore, I just wanted to share my systems with everyone, but with this difficulties, why should I ?
Bump ! :(
Bump again, please help if someone knows something ! :(
As for the bugs, the game isn't even out, let alone the map editor. They don't even have all the units in, don't judge it so fast.
Plus I doubt that they want us to STRICTLY USE THE GUI. I think its more of a tool that lets the people who don't know how to properly code work on maps as well.
tl;dr version: Bump for your cause.
Yes I hope the release will be something more... finished. :)
And I keep thinking they want us to use GUI, or at least during the BETA, because there is no easy way to code with pure Galaxy... I'm coding with Galaxy, but honnestly, it's just boring...
Not really. I don't know about you guys, but my .galaxy export is 7902 lines long already.
Writing pure code isn't a problem for me, but I find the GUI (even with bugs) to be a VERY efficient tool.
You like to import your file each time you wanna test ? O_O Sorry but I don't, it's a waste of time, and it's really, realllllly boring.
... import my file? Read again, I'm only using the GUI :)
I'm just saying my raw code is huge when I look at it, and writing it the "cool" way would have taken a lifetime.
People tend to consider the GUI as a dirty/nooby way to create maps for some reason. Wrong.
It's an excellent, fast tool.
@WhiskeeGX: Go
Sorry I've read fast.
Well it's true, since StarCraft II, the GUI editor is really powerful, but some things are not included in (like some functions you can only use as an action). I don't guess the GUI is a "nooby" tool for creating map, but think that coding in pure code is not really slow, personally I write my Galaxy code 10x faster than with GUI, probably is it really faster when you use to work with one of the two. About your 7900 lines, it makes me laugh because I think that all Jass/Galaxy people know that the transformation from GUI into Jass/Galaxy is just something funny. I don't guess writing your code in GUI will increase the number of lines a lot, but the code length and number of characters is normally increased, because of the funny code lines like :
if !(!(MyBoolean == False)) { } else { blabla; }
Well that's a choice to code with Galaxy or GUI, but some good reasons to code with Galaxy are : with Galaxy, you can do everything you can do in the editor, and not be blocked by a little thing GUI doesn't allow ; and the Galaxy language will soon be "upgraded" with Andromeda, something I think the GUI-users will never be able to use (but I guess for you, I don't know the future ).
To go back to my thread subject, I've taken the choice to share my Galaxy systems with the GUI users, a thing that I think should be good for everyone. But with the problems I encountered with the libraries system, I'm not sure I'll keep to say the GUI is a good thing, if Blizzard doesn't correct what I said. ^^
I don't really care about code "condensation" or the number of lines itself, just sayin' :)
Writing pure Galaxy is generally slower, but that's really not my point. I spend most of the time planning features, not writing them, and I've always programmed like that in the past so raw code doesn't really scare me. Still, this time the GUI is extremely comfortable for a number of reasons, notably for handling variables and having a VERY clear picture of what you are looking at, while it doesn't really miss any important Galaxy feature.
Don't know what you mean with "some functions you can only use as an action" since actions ARE void functions with a different name. They compile like that. Also, everyone keeps spitting these "things that the editor doesn't allow", and I'm wondering, because I have yet to find something that couldn't be done there. Feel free to correct me, this is not my GUI crusade or anything, I'm just curious :)
For example, a day I had difficulties to use the 'CreateTrigger' function, of course you can't in GUI, but that stopped me, so I had to use custom script. ^^
That's something. Can't really picture a situation where I would need to dinamically create triggers though, what were you doing exactly? I'm pretty sure there's another easy way to achieve that in the GUI ^^
Yes it's true, in my situation I could do it in GUI, but not with the same way I had done in Galaxy, I would have to change a function and its parameters, and that was perturbing me. Anyway, I'm sure I can find other examples where GUI shows its limits. :D But it's not the topic to speak of this, I like to discuss with you because you are not that kind of people saying "GUI IZ DA LIFEEE !!§§§11!!§", you explain why you like it, and why you don't want to use the pure Galaxy, and I understand and respect you. :)
So, if by using the GUI more than me, you find a solution to my "library problem", PLEASE TELL ME ! :D