Page 1 of 1

Manialive or not?

Posted: 20 Aug 2011, 13:57
by weerwolf
Hi,

Im a little confused by the new situation. I always understood that manialive was developped in Trackmania Forever to be a base controller for that and the future. Now i see i manialive 2 (beta) has been launched, mlepp having troubles and our own (never published) plugins for manialive as well. And i see fox as a controller independant from manialive and xymph working on xaseco2 (i presume independent).

So why manialive 2 and what is the future perspective of it?

Greetz

Weerwolf

Re: Manialive or not?

Posted: 20 Aug 2011, 15:39
by w1lla
2 stands for tm2.
The following quotes are made by The Big Boo on Beta forum not accesible for member of the beta 1 and 2.
- Some classes and variables renaming to remove underscores (this shouldn't impact plugins in theory anyway but it's better if you know)
- Repository version and id has been removed in Plugin base class
- Plugin version now supports "PHP-standardized" version number strings (small explanation, you can still use float)
- Lots of methods in ManiaLive\DedicatedApi\Connection now accept a login and not only a Player structure (can't test them all so maybe some are broken)
- In Window : property isHidden and method isShown() have been removed in favor of visible and isVisible() (so maybe some of your plugins need to be updated)
- New quad styles and substyles added
- Concerning standard plugins
- WelcomeMessage and Splashscreen removed (they were used only for Freezone)
- Bill is now supposed to work (thanks to Connection modification)
- MapVote is fixed and now uses standard database configuration
First, the current version will be available very soon on the public SVN on GoogleCode . Last version here will be moved to a branch called "forever".
Then, there will be a big move in configuration system: it will be changed to work the same way than ManiaLib. What does that mean? The config.ini will stay the same (or almost) but plugins won't have anymore those nasty static public variables. Instead, you'll have to create some Config singleton classes that you can't put where you want (so for example you can have a single one for the whole MLEPP, or one for each MLEPP plugin, or a mix between those two solutions, or whatever you want ^_^). ManiaLive core and standard plugins will use the new system so there will be lots of examples.
Maybe a few other things will be broken (renaming, removals, ...) but it will be easier to follow now