[crossfire] renaming binaries (was: Moving server towards a modularized system?)

Yann Chachkoff yann.chachkoff at myrealbox.com
Sun Jan 29 03:02:00 CST 2006


> I am not opposed to porting crossedit to gtk however.
>
The current difficulty I see with crossedit is that it is rather heavily dependent on the server code. I think that the best would be at some point to get the editor - being GTK, Athena or whatever else - get its own codebase, alongside the client and the server.

This, however, would require significant work. The question being: do we really need to maintain two editors ? When the Java Editor was introduced, my answer to that question was "yes", because a lot of machines were a little too tight to run the Java Editor comfortably. But nowadays, my answer would be "no" - most not-too-ancient computers can run it, and it offers more functionalities (I think) than the old Athena Editor.

> But if my favorite editor is removed outright... java is not an option. 

Well, it would be interesting to understand why Java isn't an option for you - did you have issues with the Java Editor when trying it ? If so, report those on the ML, so work can be done on it to try to solve them.

> However crossedit works great (IMHO) now, so there really is no reason to change it.

But it definitely wouldn't work anymore if significant changes occur in the server code - in particular, getting rid of the Athena Editor would allow to remove the separation between the "common" and "server" subdirectories - something that makes the code structure more complex with no real benefit (other than allowing the Athena Editor to exist in the first place). 

> All this constant talk of removing things is
displeasurable, thus my retirement for a time.

Notice that it was never suggested to remove game functionalities, but obsolete protocol commands, pieces of code not used anymore, or tools that got outdated by (supposedly) better ones.

It may mean that some low-end computers that were previously able to run cfclient/crossedit will not be able to run their replacements with the same level of comfort, yes. But are we targetting the game at computers manufactured ten years ago ? I agree that not limiting Crossfire to the most modern machines is very important - but I am not convinced that we should extend support *that* far in the past.

> If the things I like are not removed I'll come back, if the things I like are removed I won't come back. 

I'm immune to that kind of childish ultimatum, and I hope other developers are as well.

> I am also waiting on some new features aswell.

Nobody prevents you to code them and submit a patch on the ML if you want them. If no coder wants (or has time) to code your suggestions, it is their choice and you have to deal with it.

> I trust all notice the drop in cvs commits? That is because I am uninspired as I watch the CF dev team discuss the most effective way of canning the whole project.

And now, we're responsible of your lack of inspiration... Given that inspiration is something often driven by an unknown and highly complex mental process that science still fails to properly understand, I suggest that the discussion about possible future changes continues, as we're absolutely unsure that stopping it would solve your imagination issue.

Now, I could suggest you various things to get inspiration back, like reading books, have a walk outside, listen to music, or spend less time ranting (which definitely can have a negative impact on imagination).

> How about not removing things from the game, a novel idea, no?

How about proposing an alternative to "let's keep everything unchanged forever" - a novel idea for you, wouldn't it ?




More information about the crossfire mailing list