What is Beta Widget? And when is it planned to be used?

[bornemix]

No, this is in branches/qt/.

...and I just realised that Per has rerouted the function calls to iVis and that they must be implemented. THAT is the issue at hand. (is this correct?)

[Buginator]

There is no working project file / makefile for the Qt branch for mingw or MSVC at this time. I haven't had time to fix this.
The mac build is broken as well (as in, it doesn't work correctly).

If you want to fix this...be my guest.

[bornemix]

I will do my best, but right now I'm working on my zero-dependency mingw script for trunk... I'll be back on this one right after.

[Per]

...and I just realised that Per has rerouted the function calls to iVis and that they must be implemented. THAT is the issue at hand. (is this correct?)

I don't understand. Rerouted what function calls?

[bornemix]

...and I just realised that Per has rerouted the function calls to iVis and that they must be implemented. THAT is the issue at hand. (is this correct?)

I don't understand. Rerouted what function calls?

Per. Please work with me here

You said: "we would want to rebase betawidget on top of that to get rid of all the annoying extra dependencies"

And: "To merge the Qt branch, all we need is for it to build and run properly on Mac and Windows".

I d/l:ed it and compiled it, and got errors of missing function declarations in _iV_SetTextColour, _iV etc etc.

So I think for myself: iVis must be the library that is deprecated, and needs to go.

So it's the two iVis libraries that needs to go?

There is only one ivis library, and it has nothing to do with this.

What we need help with, is getting the Qt branch working on Mac and Windows. When this is done, we can merge it into trunk, and the biggest obstacle to betawidget is gone.

(why does it complain about it, then? )

Also, I see no other dependencies than iVis for betawidget.

I think for myself: Per has already removed that deprecated library and rerouted those calls to iVis, for someone to implement.

...and I just realised that Per has rerouted the function calls to iVis and that they must be implemented. THAT is the issue at hand. (is this correct?)

I don't understand. Rerouted what function calls?

Could you help me understand this? Is the SVN in a bad state? Why can't it find the functions in iVis?

[cybersphinx]

Could you help me understand this? Is the SVN in a bad state? Why can't it find the functions in iVis?

Because you're not linking some necessary files? It compiles fine on Linux, look at the Makefile.ams to see what's necessary.

[Per]

The ivis library is not deprecated, and I have no idea why it won't link for you. Only calls to SDL, if any remain, should generate linker errors in the qt branch. It works fine on Linux, but I do not have access to a Windows box to check there.

[andron]

this should be on the prioritylist on second place (on the first should be to build in the general texture graphic) when you want to draw people to the project - and get new developers here - , but i have somehow the feeling that this will never finish...

[Crymson]

this should be on the prioritylist on second place (on the first should be to build in the general texture graphic) when you want to draw people to the project - and get new developers here - , but i have somehow the feeling that this will never finish...

First should be stability, the game still does crash sometimes, but doesn't happen that much anymore.
I don't see why this should be in the top 5 things to fix.

[Rman Virgil]

.

this should be on the prioritylist on second place (on the first should be to build in the general texture graphic) when you want to draw people to the project - and get new developers here - , but i have somehow the feeling that this will never finish...

I don't see why this should be in the top 5 things to fix.

From my PoV Art Revolution will majorly advance the games visual appeal and immersion from 1999 closer to present day standards. I think that is obvious. This will also serve to broaden the games active fan base & also interest potential new source code devs.

Beta Widget/LUA is essential to advance the game's GPM evolution from its 1999 stasis. Some think that the 1999 GPMs are already perfect, unique and sacrosanct - in need of no further evolution. I have never been of that camp (neither were WZ Creators, Pumpkin, truth be told) and would also posit that while the 1999 GPMs were novel in some respects, that novelty soon wears thin and once that happens the 1999 GPM's limited & predictable nature is exposed. Outta that (& familiarity with the source) the unfulfilled GPM promise becomes clearer & that this was a direct consequence of Eidos aborting Pumpkin's continued development cannot be gainsayed if you were witness to Pumpkin's fostered community for the game in 1999.

- RV
.

[andron]

is the beta widget not also about rearrange the build menu and group builds to as example defense, basic buildings, and so on? I think on the menu is this even more important than the graphical change...

There was a thread about the ground textures it changed the look much the screenshots are from it:

http://developer.wz2100.net/attachment/ ... errain.jpg

this is posted 16 month ago! And its still not in the game and i ask myself why i did play the trunk with it and it was very stable half a year ago.... please my you say me where the thread is i cannot find it anymore

[macuser]

Are there any screenshots of betawidget or plans for what it will look like? I think we are all curios about what it will be like.

-regards macuser

[andron]

a year and two days ago:

viewtopic.php?f=6&t=2886&p=27898&hilit=beta+widget#p27898

[macuser]

Screenshots:



Hope to see this developed!!

-regards macuser

[Zarel]

Those aren't screenshots, those are mockups.