On 1/4/10, Kreuvf wrote:
> Per Inge Mathisen wrote:
> > So here is my suggestion: We pick one branch as the final campaign
> > release tree, and at some point branch it to become an "original
> > campaign only" branch, removing anything other than campaign from it
> > (ie no skirmish, multipla
On Mon, Jan 4, 2010 at 4:33 AM, Per Inge Mathisen
wrote:
> Campaign always being a low priority item on everyone's agenda,
> throwing a near total rewrite of that code up in the air as an idea
> gives us very little. In fact, it would be much easier to rewrite it
> if we can remove the burden of h
Per Inge Mathisen wrote:
> So here is my suggestion: We pick one branch as the final campaign
> release tree, and at some point branch it to become an "original
> campaign only" branch, removing anything other than campaign from it
> (ie no skirmish, multiplayer, etc). Starting the executable built
Per makes a strong case, especially given the long term plan for moving to
lua scripting, the continuing divergence between campaign and skirmish and
the difficulty of testing the campaign.
I think it is worth doing.
--
Stephen Swaney
sswa...@centurytel.net
__
On Mon, Jan 4, 2010 at 10:10 AM, Guangcong Luo wrote:
> As the branches diverge, they won't be so easily backported.
>
> And having to have two games that are effectively the same thing, but
> one for campaign and one for skirmish, as they diverge... It'd just be
> a nightmare for users as well as
On Sun, Jan 3, 2010 at 3:34 PM, Per Inge Mathisen
wrote:
> Most of the patches that benefit campaign are small and easily
> backported (terrain renderer notably excepted - but I'm not sure it
> should be backported).
As the branches diverge, they won't be so easily backported.
And having to have
On Sun, Jan 3, 2010 at 10:14 PM, Guangcong Luo wrote:
> I really dislike this idea, because there are many upgrades that
> campaign does benefit from, as much as skirmish - the new keyboard
> shortcuts, such as 's', alt+click, etc, for example. The build
> previews, for another. The terrain render
On Sun, Jan 3, 2010 at 8:55 AM, Per Inge Mathisen
wrote:
> So here is my suggestion: We pick one branch as the final campaign
> release tree, and at some point branch it to become an "original
> campaign only" branch, removing anything other than campaign from it
> (ie no skirmish, multiplayer, et
It sounds reasonable to me; who knows someone might even rewrite the original
campaign for it.
--
My Web Sites:
http://dak180.users.sourceforge.net/
On Jan 3, 2010, at 9:55 AM, Per Inge Mathisen wrote:
> So here is my sugge
Hello,
We keep breaking campaign again and again. Unfortunately, none of the
core developers seem to play it, at least not anymore, and we have no
automatic or easy way of testing it. The campaign code is a horrible
collection of truly horrendous hacks that nobody has of yet dared or
wished to imp
10 matches
Mail list logo
