Main Page | File List | Related Pages

Frequently Asked Questions (FAQs) [Updated: 2004-04-17]

Q1: Why has development slowed down this much suddenly? [Updated: 2004-04-17]

In some classes I have some potentially substantial catching up to do and in others (two out of four), it is a matter of targetting perfection... and a tradition of being first-of-class in any class related to digital stuff. And this time, it also is a matter of making up for the horrible summer classes results last year. Aiming for all A(+) means I should have far less spare time.

Note:
I should probably stop studying... when I know too much, I feel compelled to recreate every formula from base principles, waste too much time doing this and come out short on time to finish the exam. I should learn to be lazy and just use whatever textbook and sheet notes are allowed for the exam then do like every one else seems to be doing, match sets of unknowns to equation sets and apply the calculator's all-mighty "solve".

On the plus side, exams are over now so I can go back to MT full-time for a while.

Q2: Why is it still labelled as "alpha"? Isn't MT stable enough to be a Beta? [Updated: 2004-04-17]

I will upgrade the label to beta after all the GUI elements I wanted to implement since the begining will be in there. So, MT still being an alpha has more to do with me thinking it is not yet complete enough to be a Beta than a stability-related thing. At this point, if 0.1.0.1-alpha4 goes as far as I initially hoped that it will, alpha4 should be the last alpha, meaning MT will have acquired all the stuff I consider essential. Then again, I should probably be more liberal with version bumps and since I did increase the version number when I changed the piece request handling so all the changes since, by that 'standard' would deserve at least a build if not revision number bump.

After writing this, I feel like changing 0.1.0.1-alpha4 to 0.1.0.2-alpha1 and given the pace at which I plan to add stuff, possibly drop WIP builds and start pushing "Alpha du Jour" or drop the alpha and go plain WIP since MT's only major shortcoming is only that it is underfeatured, not that it is hopelessly broken, notoriously unstable or highly experimental. It is that underfeatureness that the next build series, whatever the enumeration will start from, will be meant to remedy.

Q3: Where can I get the source code? [Updated: 2004-04-17]

Nowhere. At the moment, I have no plan to release any MT code... certainly not until the code has reached a certain maturity, certainly not until I am happy with it and its general coding style, certainly not until MT has become sufficiently well known to ensure there will be no confusion about its origins. (Right now, I think I would be somewhat embarassed if a competent outsider saw some of my worst code bits.)

Q4: How large is MoonlightTorrent's source code and how much time did it take to get there? [Updated: 2004-04-17]

There is about 9000 lines worth of original code in MT, around 1000 of which is auto-generated stuff and another 600 is copy-pasting from other sources such as MSDN, coded across about 500h worth of coding/debugging as of 0.1.0.1-alpha3. So, MT gained about 1000 lines in the alpha3 series and I am pretty sure alpha4-wip1 alone will contain nearly that many new lines since I will be working on it full-time for the next couple of days.

Q5: Where is the rest of the FAQ? [Updated: 2004-04-17]

This is all for now since I have more important things to do than invent more FAQs. I will add more if people actually start asking questions. I suppose there will be more questions if I get a forum hosted somewhere and I was thinking of hosting one on my spare P233/128MB to see how popular it might be and determine wether or not it would be worth considering some more proper hosting for it.



Hits since December 5, 2003:

Generated on Tue Aug 24 23:57:31 2004 for MoonlightTorrent(.com) by doxygen 1.3.8