Probably those in school are dealing with finals.  But hey, stuff goes in
fits and starts!  One day nothing the next day BAM VOIP, so who knows.

As for will anyone do anything, who knows.  I'm only hoping for stuff like
Ben's comments about why a certain approach might not work and an
alternative approach that might work, how much of a pain it would be to
implement, etc.

That's why I threw it on the ioq3 wiki.  So people could freely edit and
clarify and add ideas and comment, etc.  All I'm hoping for at this point
is some type of plan that would make sense in the context of ioq3 and
address some of the compatibility objections that have popped up from time
to time.  Something that some of the prime committers like angst, timbo,
thilo, etc. would find acceptable enough to want to include in the main
source.  Otherwise, there's no point since the effort would just be
another source fork to wither and die.

I figure a solid plan in place with the blessing of the committers would
at least improve the odds of someone wanting to try implementation at some
point in the future.  So the more comments on the technical feasibility,
the better!


> ok, will anyone do anything, practically? 'cause the project seems
> inactive lately.
>
> On Sun, May 2, 2010 at 12:54 PM, Zachary <[email protected]> wrote:
>>
>> On May 2, 2010, at 1:01 AM, [email protected] wrote:
>>> ioq3 should be the one-stop shop for most projects starting off.
>>
>> Yep.

_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to