War3 Foundation Structs (WFS) libraries

[yxq1122]

Introduction
This is an idea or concept! What is WFS? It is a series of structs that packages all operations for all types of objects in vJass for Warcraft III. Simply you can understand it as something that is similar to Microsoft Foundation Classes (MFC) library that has packaged all operations for all types of objects in C++ for Windows platform. The relationship between WFS and Jass API natives might be similar with that between MFC and Windows SDK. Based on vJass, WFS is possible to realize, isn't it?

It is true that we now have plenty of libraries to use. However, the functionalities provided by these libraries are not complete to describe or manipulate all types of war3 objects, and they are not exported in Struct (OOP).

It would be great if someone feels interested in it, then creates and develops this project.

 

[Lizreu]

I don't understand what you're proposing here. If you want it done - go and do it yourself. Nobody is going to work on your project for you.

 

[yxq1122]

I don't understand what you're proposing here.

Again, I say again: It is just an idea in my mind!

If someone could be inspired by this idea, it would be enough.

I hope @TriggerHappy, @Retera or more others could see this thread.

 

[Pyrogasm]

I don’t understand what you’re proposing either. That we combine every library ever written into some resource? That we make oop versions of all JASS natives?

 

[yxq1122]

I don’t understand what you’re proposing either. That we combine every library ever written into some resource? That we make oop versions of all JASS natives?

Yes, package all Jass natives into Structs in different types. Then, users could choose to use member variables and methods by creating a Struct object.
Just think it as MFC of vJass version.

 

[Pyrogasm]

But... why? I fail to see how that would reduce required code or make anything simpler. You still have to type Unit.Create() instead of CreateUnit.

 

[Glint]

Standard libraries does increases productivity but at a cost of unnecessary overheads like stack traces, error handling, unnecessary loaded libraries, inefficient implementations. Creating a print("Hello World") with standard libraries will cost 1 MB map size with increased loading times while a simple BJDebugMsg("Hello World") without standard libraries cost 1 KB map size with short loading times.

Wurst is a Warcraft III scripting language with standard libraries. It supports stuff like unit.create(), unit.kill(), LinkedList<unit>. Setting it up takes time though.

Also, Nestharus has a series of interesting vJass libraries in his Github.

It is a preference if a person like to use standard libraries or not. For me, I'm fine with both.