What will be the next server version? 1.7.1 or 1.8.0?
If no one object, i'll put a tag for the release candidate tomorrow or
friday, so people can again break cvs with commits :)
Nicolas
___
crossfire mailing list
crossfire@metalforge.org
http://mailman
Hi,
I submitted a patch to the tracker (1255825) adding a basement map to
the potionshop in scorn. It is an alchemy classroom map, and costs
2000 platinum to enter.
___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailma
Joining thread a bit late, trolling a bit perhaps :)
I personnaly would enjoy a branch policy on crossfire cvs (whatever it is, a
bad decision is always better than no decision).
I don't think we need branching at each release (unless we
want to keep a few weeks after release a bugfixing branch w
On Monday 08 Aug 2005 07:49, Mark Wedel wrote:
> If other people want to help with releases, that would be great. Having
> a more frequent (quarterly) release schedule would also be good.
>
> Even people taking some portiosn of the release (maps, archs) reduces the
> effort a bit on my side -
I'm interested in porting Crossfire to MacOS.
I know that the existing client can be made to run on MacOS - I am
using it myself. However, it requires Apple's development tools to be
installed, an X server running and a lot more technical knowledge
than most users possess. If we had a nativ
Amorya North wrote:
I'm interested in porting Crossfire to MacOS.
I know that the existing client can be made to run on MacOS - I am
using it myself. However, it requires Apple's development tools to be
installed, an X server running and a lot more technical knowledge than
most users possess
On Thursday 11 Aug 2005 00:25, Amorya North wrote:
> I'm interested in porting Crossfire to MacOS.
> If I go ahead with this, I'll write the client in Objective-C using
> the Cocoa API. Hopefully I'll be able to reuse some of the backend
> code (such as packet parsing) by wrapping it in an objecti
On 11 Aug 2005, at 01:24, Brendan Lally wrote:
In theory all C code compiles to objective C as well. (I say in
theory, I have
never tried it in practise).
If this is so, it should be sufficiant to take the common/
directory, and
compile the C files there as if they were objective C and the
On 11 Aug 2005, at 01:00, Alex Schultz wrote:
Another option is that someone could build the existing GTK client
with gtk-cocoa (http://gtk-cocoa.sourceforge.net/), which would
allow it to run without the X server running and such.
It's worth looking into.
I don't know specifics about gtk
Amorya North wrote:
You may want to build it within the existing framework and link
directly to the C code in the common directory, because that way this
native MacOS client could eventually become an official part of the
source tree, and one advantage of that is that many protocol changes
wo
10 matches
Mail list logo
