On Tue, Feb 17, 2009 at 6:14 PM, Mark Malewski <[email protected]> wrote:
> > Ok, I've been reading "both sides" of this, and I can see how Developers > want to wait till everything is 100% done, before letting anyone use it. > > Well, the problem is... just like LC has said, the "early adopters" need to > at least begin using it so that tutorials can be written, and that we can > begin to lay the "ground work" for others to follow. There may be a lot of room for misunderstanding in this thread, but let me try and make a few points. I don't think there is any case of wanting "100%" done. I have been working on open source for my entire professional career, and I understand "release early, release often". However I also understand that at this point reX is alpha software, and alpha software isn't meant for users yet. It's meant for people with the stomach for downloading from SVN, compiling it themselves, and helping with bug reports. The source is freely available, and building it isn't very difficult compared to any other project in an alpha status. What I understand you're asking is: 1. When ModreX will become beta, and thus one might presume be easier to build, and worth making a binary release of? The answer is when its roughly feature complete (not to be confused with 100% complete in every way). That means its not missing huge gaping holes of functionality. The reason why is simple: because until we have patched the all the huge gaping holes in features, we are too busy doing fundamental work of the first order, before we can work on polishing it ready for beta user consumption. Its purely a matter of limited resources. If, however, you intend to contribute resources yourself, that equation changes. Give me a precise list of what you need to start with. 2. Will ModreX support "Under the Sea" demo completely? The answer is unlikely, just yet. The reason is that the previous versions of software contained work-arounds for SL et al., we would rather make things work properly in the first place. That means that for a period of time (the duration of which is unknown), there *will* be regressions due to renovation. Precisely where those regressions are, and when they might be fixed, is only partly known. What is know is that regressions are a fact of software engineering, and pretending they don't exist is foolhardy. However, if you intend to contribute your own resources to debugging "Under the Sea", and generate a list of regressions for the community, then we would eventually know where they all are, and we would be one step closer to having them fixed. Bottom line, this is a community of open source users and developers. It only works when everyone is lending their hand. Otherwise, I am afraid you'll have to wait for our hands to become freer. Lastly, if the only issue here is getting a compiled binary in your hands, I am sure Mikko can find his latest DLL somewhere. However, don't expect it to be smooth sailing. That'd be like expecting an egg to come out of the fridge boiled. Cheers, --~--~---------~--~----~------------~-------~--~----~ this list: http://groups.google.com/group/realxtend realXtend home page: http://www.realxtend.org/ -~----------~----~----~----~------~----~------~--~---
