Re: MG Features

[silnarm]

There is no such policy,but code changes and stuff becomes incompatible, but you know this,
again, it all depends on how you do it.

There is absolutely no reason for certain incompatibilities that have been introduced. If they don't want to use our code, fine.  But they introduce 'new' features that are identical to GAE features, and give them a completely different XML setup, or in the case of Lua different function names, even command queuing is different (Shift Vs Ctrl)!

The only reason I can see for this is either ignorance or arrogance.

[Omega]

There is no such policy,but code changes and stuff becomes incompatible, but you know this,
again, it all depends on how you do it.

There is absolutely no reason for certain incompatibilities that have been introduced. If they don't want to use our code, fine.  But they introduce 'new' features that are identical to GAE features, and give them a completely different XML setup, or in the case of Lua different function names, even command queuing is different (Shift Vs Ctrl)!

The only reason I can see for this is either ignorance or arrogance.

^This, nuf said.

[ElimiNator]

There is no such policy,but code changes and stuff becomes incompatible, but you know this,
again, it all depends on how you do it.

There is absolutely no reason for certain incompatibilities that have been introduced. If they don't want to use our code, fine.  But they introduce 'new' features that are identical to GAE features, and give them a completely different XML setup, or in the case of Lua different function names, even command queuing is different (Shift Vs Ctrl)!

The only reason I can see for this is either ignorance or arrogance.

Nobody knows what  GAE has so they add it thinking GAE dose not have it (Which is  ignorance sort of).

[John.d.h]

Nobody knows what  GAE has so they add it thinking GAE dose not have it (Which is  ignorance sort of).

Has anyone considered asking?

[titi]

 

[Zoythrus]

Nobody knows what  GAE has so they add it thinking GAE dose not have it (Which is  ignorance sort of).

Has anyone considered asking?

this^

[ElimiNator]

Nobody knows what  GAE has so they add it thinking GAE dose not have it (Which is  ignorance sort of).

Has anyone considered asking?

I did but I was pointed to a page that doesn't have every thing I don't think

[Omega]

Well, you did ask a one line topic about where to find a full list of features, which does not exist! Try asking for individual features before implementing. For example, "I am going to implement the ability to load and save games." ... "Oh, we already have that."

[titi]

OK this all is a problem, but you always said we would look at your code and steal everything from you and so on ....
In fact we (especially I ) didn't looked at the GAE code for such a long time that this might happen.
Beside of this I only use MG to play everyday, so I am really not used to already existing GAE features.

I think we both seriously need a list in the wiki where we describe all new features we have ( if needed a bit more detailed ).
This might help.

For a concrete problem where I see upcoming incompatibility is the current map format. Please look at my thread about cliffs.

[Omega]

I think we both seriously need a list in the wiki where we describe all new features we have ( if needed a bit more detailed ).
This might help.

Agreed. A seperate page linked from both engine's main wiki pages with the full list would be nice, along with short explainations on how to use them (with complex ideas having the potential to link to a page specifically for that).

[ElimiNator]

Well, you did ask a one line topic about where to find a full list of features, which does not exist! Try asking for individual features before implementing. For example, "I am going to implement the ability to load and save games." ... "Oh, we already have that."

Last time I talked to silnarm he said the "Save Game" feature gets broken in every release.
Also I downloaded GAE and it didn't work...

[ultifd]

I think we both seriously need a list in the wiki where we describe all new features we have ( if needed a bit more detailed ).
This might help.

Agreed. A seperate page linked from both engine's main wiki pages with the full list would be nice, along with short explainations on how to use them (with complex ideas having the potential to link to a page specifically for that).

[silnarm]

OK this all is a problem, but you always said we would look at your code and steal everything from you and so on ....

I did ?  I believe all I ever said was that you know where to find our code and to help yourselves, whether you do or not doesn't concern me.

For the record, softcoder clearly does look at GAE, and is quiet adept at taking other peoples code and adding it to MG. Obviously I have no problem with this... except when shiny new features we developed end up in a MG release before a GAE release, this unfortunate state affairs has sadly seen me take several new developments 'underground'

Well, you did ask a one line topic about where to find a full list of features, which does not exist! Try asking for individual features before implementing. For example, "I am going to implement the ability to load and save games." ... "Oh, we already have that."

Last time I talked to silnarm he said the "Save Game" feature gets broken in every release.
Also I downloaded GAE and it didn't work...

I never said anything of the sort, I assume you are referring to this post where I tried to explain that in-between releases things may well be broken.  If you download a released version, I think you will find save game works... if it doesn't please sent us a bug report! (and not one those useless 'x doesn't work' one liners you like to post, please read this first).

GAE and MG have very different development philosophies, and even though MG uses a purely linear development model and tries very hard never to have anything broken, things are occasionally broken in trunk... that's software development.

[titi]

ok whatever, back to topic compatibility:

I don't think a common page is a good idea! But both sould have a page that they try to keep up to date.
We already try to do this in the wiki here:
https://docs.megaglest.org/MG
with subpages here:
https://docs.megaglest.org/MG/XML_Definitions
https://docs.megaglest.org/MG/Scripted_Scenarios

[John.d.h]

Ditto for GAE, but I don't know how up-to-date it is (currently missing things about bump maps, for example).
https://docs.megaglest.org/GAE

[titi]

I know   , the real problem for both of us is to keep it up to date!

Look at the GAE lua reference and you know what i mean! But to say the truth we have the same problems to keep things up to date, but we try .....

[Omega]

Oh, I didn't mean one page for both GAE and MG's features, but one page for each engine (eg: "GAE/Feature list" and "MG/Feature list").

Looking at the editing history, GAE and MG associated pages are the most edited (and among the most viewed) on the wiki.

[will]

except when shiny new features we developed end up in a MG release before a GAE release, this unfortunate state affairs has sadly seen me take several new developments 'underground'

indeed

Can't you keep pushing everything "early and often" to sf.net where I and others can contribute if only by reading it, please?