I use only GUI! I can do everything I want by using only GUI, GUI is easily to learn and very useful! I don't know use JASS, but, I think that I'll try to learn any day because everyone is using JASS today.
@Blade Sure. As I said, I use JASS for everything that requires JASS. But because I don't know JASS THAT well, I don't know why I should use JASS in simple triggers like:
Event Any Condition Any Actions Set Gold of Player1 to [value]
It's just faster for me setting up such a function using the GUI.
DarkShadow@Blade Sure. As I said, I use JASS for everything that requires JASS. But because I don't know JASS THAT well, I don't know why I should use JASS in simple triggers like:
Event Any Condition Any Actions Set Gold of Player1 to [value]
It's just faster for me setting up such a function using the GUI.
I'm quite sure the topic was pointed to spell making.
You can easier look over bugs in GUI, because obviously that was its meaning. For cinematics and map triggers I use GUI. For spellmaking, I use JASS. Spellmaking consumes a lot of memory in GUI, and is the most complex area in the means of triggering.
Oh, and I checked Darky's RotD and he does the same. It's the best way to combine them. Trust me, if you want to change something in a cinematic or find something you don't like, GUI is much better. For spellmaking, you can get confused even in GUI since the code is extremely big for big spells.
Oh, and yes, JASS can sometimes be much faster, until I have to debug the code. When I start doing that, I wonder why I didn't use GUI from the beginning. I also want to mention that lately, thanks to Vicky2004 and Nantuko Husk I can now detect BJ functions much easier (that JASS tool is awsome) and no more locations for me. It's indeed annoying that JASS is a programming language FULL OF BUGS!!! It has a lot of problems, such as the stupid nullifications, the many leaks, and its limits.
Oh, and afterall, GUI is also JASS in its core, just that it looks... hmm, easier for the user (cause somebody using GUI is not really a programmer).
Oh, and ragingspeedhorn, what was with that senseless comment?
DaelinYou can easier look over bugs in GUI, because obviously that was its meaning. For cinematics and map triggers I use GUI. For spellmaking, I use JASS. Spellmaking consumes a lot of memory in GUI, and is the most complex area in the means of triggering.
Oh, and I checked Darky's RotD and he does the same. It's the best way to combine them. Trust me, if you want to change something in a cinematic or find something you don't like, GUI is much better. For spellmaking, you can get confused even in GUI since the code is extremely big for big spells.
Oh, and yes, JASS can sometimes be much faster, until I have to debug the code. When I start doing that, I wonder why I didn't use GUI from the beginning. I also want to mention that lately, thanks to Vicky2004 and Nantuko Husk I can now detect BJ functions much easier (that JASS tool is awsome) and no more locations for me. It's indeed annoying that JASS is a programming language FULL OF BUGS!!! It has a lot of problems, such as the stupid nullifications, the many leaks, and its limits.
Oh, and afterall, GUI is also JASS in its core, just that it looks... hmm, easier for the user (cause somebody using GUI is not really a programmer).
Oh, and ragingspeedhorn, what was with that senseless comment?
~Daelin
Don't generalize, please, I hate it so much. It depends on practice. I am making everything faster in JASS today, simple triggers aswell and cinematic stuff, only JASS. And it is obviously best to do because it's directly, but I agree GUI can be easier to use.
What awesome JASS tool are you talking about, by the way?
Those things are not bugs in JASS, leaks are just the mappers fault, variable nullification might be a bug, as Blizzard doesn't use it themself and because it in very rare situation can lead to bugs.
Waldbaer
#25
I use JASS only for spells and to Destroy Triggers. I don't think it's very useful for other things and I'm too lazy to work more with it and learn it in all its details!
Blade.dk2Those things are not bugs in JASS, leaks are just the mappers fault, variable nullification might be a bug, as Blizzard doesn't use it themself and because it in very rare situation can lead to bugs.
Actually, they are not. A good programming language should automatically nullify variables once they are no longer used, and, excuse me, but why should locations leak and cause problems? If they were created, why don't we use them? Because they are slow? WHY are they slow? They should just store an X and Y value. Reals don't leak, but locations do, and this is pretty stupid. Locations store nothing else but two reals, or atleast, that's what they should.
ragingspeedhornKAPOW and Daminions smartass comment was instantly shot down by blade, 10 points! xD
I connect JASS to spell making. Then I saw DarkShadow's example which wasn't a spell so I thought that this was not a valid example to compare GUI to JASS since it was just a map trigger.
And it seems to be really hard to spell my name. People seem to imagine that there is an extra "i".
Using locations IS faster than using reals, if you doesn't take the painful cleanup's duration in consideration.
I already said in my previous post that I agreed that the nullifying thing is a bug.
The reason locations leaks while reals don't, is that a real always exists and is the same thing, while locations are created and when you create something you have to remove it again, like in rl.
Anyway, I've been doing fine till now with WE, sometimes Notepad (for huge searches that WE is not capable of, it can not search all the text, and for replacing everything in JESP spells), and PitzerMike's JASSParse when something is seriously wrong, but I guess I'll check that tool.
It's indeed annoying that JASS is a programming language FULL OF BUGS!!! It has a lot of problems, such as the stupid nullifications, the many leaks, and its limits.
