Moving to the preprocessor world

With the news that I am planning to make everything I develop from now to require a preprocessor, the minimum requirement would be: http://www.wc3campaigns.net/showthread.php?t=88142 , but the people could use wewarlock as well (once it is ready with grimoire) which should have the features I am gonna use.

The pros are easy to see:
- Things will be much easier to implement (most of the times a single copy paste of a trigger category will suffice)
- Since I will have less problems to use globals, some stuff will be faster (I for example won't have to use gamecache for a lot of things)
- In overall the preprocessor gives a free advantage to the user, and it is that even pjass+ my preprocessor compile the script faster than World editor's normal compiler so the save process takes less time.
- PJASS has better error messages and is not bugged like hell so people will have less trouble recognizing the errors they might have when implementing my systems.


But of course, there are cons:
- GUI people won't be able to access my global variables.
- Third party stuff instead of normal world editor required.


--
So I was wondering what people think about this decition?

So, basically you want the preprocessor to get rid of GetCache() ?

Can you explain the other benefits a bit more?
- What things will be easier to implement and why?
- Can I too define globals in the scripted way?

Not just CSCache() , but a lot of things.

The biggest benefit is that the implementation of caster system in your map would be:
- Paste CSCache Trigger
- Paste CasterSystem Trigger
- Paste Ability
- Import model
- go to CasterSystem Trigger and update rawcode

Thanks for the blazing fast reply

Pasting triggers containing script does work, it's just that it gives an error before the world editor is restarted. I can clearly see the advantage of preventing this though.

Import model!?

Because the rawcode is stored as globals? Or do you just mean that you can go to the trigger instead of the cscript section?

It works, but you can't be sure that it would be added before other triggers so it doesn't work for triggers that contains functions to be used by other triggers.

We already need to import the model anyways.


And the copy variables part of it is gone as well.

..
It is hard to manage scripts when all of them are in the custom script section.

Now I think I got it all.

I noticed that there was room for more libraries in the helper program. Additioal modules planned?

And now I intend to silently slip back to the subject...


For beginners the caster system is much like a mod anyway; I don't think they'll be scared away by this sweet little program. I mean, after all, the caster system will be easier to install...

Experienced users should see the usability in this and shouldn't complain.

This is where I should point out that I find it silly to make people use a mini-preprocessor when the same people could have been persuaded to use a more powerful preprocessor.

So, when will this Caster System upgrade be published?

when I finish it?

*sigh*

If I really expressed myself that bad, let me explain myself.

If I intend to start working on a map in, let's say a week, should I delay it waiting for the new CS? Or is this just a thought you've just got, which you'll implement within the next year? Upgrading will perhaps be easy, but still, it doesn't feel quite right to me implementing something I know I might have to replace within a day.

You didn't express bad, just that I don't really know when I'll finish the new CS, I'll also want a better version of WEHelper to be available.

I actually probably finished the script part, but I noticed the samples are outdated and full with issues, so I am remaking most of the samples in pure JASS, the reason is mostly that I now am unable to use cs's globals in GUI

I guess, nobody who is limited to GUI will ever be able use it as it is supposed to be used. He will be always limited with thelimitations of GUI, which means, that there will be no big diffrence if you use cs_ as prefix or the udg_, nor you need a third party tool to import. 2mbs and you are fine.

Will the Caster System be usable for mapmaking on a Macintosh when you "move to the preprocessor world"?

That's a really good question and the answer is no, well, not directly, there will be ways to use it but won't be easy.

Did not thought of mac, maybe make one oldstyle for mac and a easy import one for PC.