I had been thinking about this too, to get rid of the Profile class and make everything Lua.
There is the point that kaputtnik raised though - we have binary packets that can't be manipulated. Map compatibility is another issue - we would end up with 2 code paths. We already have 2 code paths for loading bobs, for example. We shouldn't add a third.
I had been thinking about this too, to get rid of the Profile class and make everything Lua.
There is the point that kaputtnik raised though - we have binary packets that can't be manipulated. Map compatibility is another issue - we would end up with 2 code paths. We already have 2 code paths for loading bobs, for example. We shouldn't add a third.
What we could indeed still convert to Lua is:
1. campaigns.conf and tutorials.conf. Already done: https:/ /code.launchpad .net/~widelands -dev/widelands/ campaignselect_ box
2. The user options (.widelands/config)