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

2006-01-29 Thread Yann Chachkoff
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

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

2006-01-29 Thread Brendan Lally
On 1/29/06, Yann Chachkoff [EMAIL PROTECTED] wrote: 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

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

2006-01-29 Thread Brendan Lally
On 1/29/06, Mark Wedel [EMAIL PROTECTED] wrote: I would suggest the following mappings (for both binaries and package names) crossedit - crossedit Arguably, crossedit should just disappear. This, however, may become more or less an issue depending on other changes (if a code

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

2006-01-29 Thread Miguel Ghobangieno
Understand this Yann. IF crossedit is removed I remove myself. Do you want to lose your biggest current media contributor? If so then remove crossedit. I think you need to fork off crossfire and make your own project where you can do whatever you want. Perhapse crossfire-awsome.sf.net? --- Yann

Re: [crossfire] renaming binaries

2006-01-29 Thread Mark Wedel
Miguel Ghobangieno wrote: Understand this Yann. IF crossedit is removed I remove myself. Do you want to lose your biggest current media contributor? If so then remove crossedit. I seem to see this ultimatum almost once a week now (do this or I leave) This carries no weight for me. I'm

Re: [crossfire] renaming binaries

2006-01-29 Thread Mark Wedel
Brendan Lally wrote: On 1/29/06, Mark Wedel [EMAIL PROTECTED] wrote: I would suggest the following mappings (for both binaries and package names) crossedit - crossedit Arguably, crossedit should just disappear. This, however, may become more or less an issue depending on other changes

Re: [crossfire] renaming binaries

2006-01-29 Thread Miguel Ghobangieno
Check the CVS logs. I have stopped committing about a week ago. If you remove crossedit I will not restart. --- Mark Wedel [EMAIL PROTECTED] wrote: Miguel Ghobangieno wrote: Understand this Yann. IF crossedit is removed I remove myself. Do you want to lose your biggest current media

Re: [crossfire] renaming binaries

2006-01-29 Thread Miguel Ghobangieno
Lol. --- todd [EMAIL PROTECTED] wrote: I suppose this would be a nice perk and a big incentive to remove crossedit, but you've quit so many times before that it just isn't a reliable enough promise to base a decision like this on ;) Miguel Ghobangieno wrote: Understand this

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

2006-01-28 Thread Miguel Ghobangieno
I am not opposed to porting crossedit to gtk however. But if my favorite editor is removed outright... java is not an option. However crossedit works great (IMHO) now, so there really is no reason to change it. All this constant talk of removing things is displeasurable, thus my retirement for a

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

2006-01-28 Thread Miguel Ghobangieno
If crossedit dissappears then I dissapear. I guess that is what you all want though. Should CF fork? --- Mark Wedel [EMAIL PROTECTED] wrote: Arguably, crossedit should just disappear. This, however, may become more or less an issue depending on other changes (if a code restructuring

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

2006-01-27 Thread Brendan Lally
On 1/28/06, Brendan Lally [EMAIL PROTECTED] wrote: I'd be inclined to say that the quickest way to do that would be to have a deliberate compatibility break, oh, one other thing which is vaguely related to that, a 2.0 release would also seem to be a good time to rename some binaries. Currently