Well, I've racked my brains to think of a better, quicker way to do the initial install but I've come back to downloading an install script. Linux is just too good at protecting users from downloading executable code.

I can follow my feisty fawn guide (changing a couple of lines when they error but nothing drastic) and have ubuntu up from a new install to playing EL in a matter of minutes. It's even easier with Hardy Heron's "Want to install the restricted drivers for your graphics card?" popup.

I may just sacrifice a spare drive (I have a 200GB sat on top of my computer case) and do a full install so I can post the hardy heron guide.

Thanks for providing absolutely no insight or relevant input to the topic at hand.

bluap, I think it's a good idea as there will always be people who are not ofey with building from CVS, and even those who have difficulty with extracting & running EL from its current packaging methods.

Basically, it can't hurt at all. I'm inclined to say .debs at least - bearing in mind that it may be beneficial to make them compatible with both Debian and Ubuntu - and similarly for the rpm-based distributions.

Yes, we had to change some things on the startup process and some changes in the scene drawing (and more), which if included right now would break the client. So branching makes a lot of sense while we don't have this thing stable enough to merge in the main trunk. We also need to share code very periodically, even if that code does not compile at all.

I added a patch to add the 1400x1050 resolution to the client (it's the one I use in my laptop).

I added the patch to BerliOS. It should apply cleanly with -p0.

The patch looks fine and applies and builds cleanly. I can confirm the window mode works but my monitor is not up to running this in full screen and I get the "Stop playing with the configuration file and select valid modes!" error; that's OK I'm sure.

So, anyone object if I (or someone else) go right ahead and commit this change?

Yeah, I like the idea of being able to move things around in Storages, would also be cool if we could create other parts, for example, we have 'Armours', insted we could make something like 'PK Armours' in there we could put all the things for PK, so everything is much easier to get to and used.

This has got nothing to do with changing the overall functionality of the storage window. It's purely to do with the category ordering.

And as I stated, the client has pretty much no code documentation at all. If there is an issue with the eye candy and karen is not about the problem stays until he fixes it. I have intimate knowledge of parts of the code and only a passing acquaintance with the code as a whole.

Right, so if everyone else is doing it that makes it alright? I see this excuse so often with people who don't document their code yet write stuff that's unreadable. It is not an excuse. Use decent programming practices whatever you're coding!

Edit: Karen produced an entire HTML file explaining the majority of her code.

Parts of the code I wrote were deliberately obtuse to prevent the possibility of macroing using it (the quickspell code is rife with exploitation possibilities. Should I hold macroers hands while they use the code I wrote to break the rules?)

Jesus. It's an open source client, people are gonna see what you write anyway. The job of macro-prevention is largely the responsibility of the server. There is very little the client can do to prevent macroing. Anyway, WTF does macroing have to do with custom clothing mirror?

I did not document the code as there is no requirement to document the code. The general rule appears to be "if it works it's in, we will fix any issues it causes later" which I accepted when I decided to become a client developer.

Again, no excuse. That approach to a programming project is like building a dam and saying "oh sod it, we'll patch the cracks later".

If someone comes along and expects support when Entropy himself told him he was having none, why shouldn't my support come at a price?

Why SHOULD it? You're not Entropy. What's it costing you to share?

And then to ask the devs to document the code that he needed information about smacks of insolence. Why not ask for documentation for the whole code instead of one single part - where the documentation of the code he asked for would not have solved the problem for him anyway?

What you're doing is also somewhat insolent, too.

I could have given him his answer in 2 lines had he decided it was worth contributing to the game. Now I guess I'll just forget what those 2 lines were.

I'm all for the encouragement and support to help Ent. and Roja get some cash for their hard work, but that doesn't warrant bribing people. I donate GBs of bandwidth a month to EL, without expectation of recompense whatsoever. Do you see me saying "oh hihi, I'm holier than thou"? No.

The information is freely available in the client for anyone to study. Should the fact that it is not documented be held against me because I was the developer of it and therefore have an intimate knowledge of its workings? Possibly, but I am not the only client dev that relies on others having a level of expertise in the subject rather than spending 5 lines explaining each line of code I write.

I can't believe I'm reading this.

You didn't document your code, or write it in a manner that's easy to read and maintain, and after stating this publicly you then give someone who's asking for help demands?!

I looked a bit at the protocol code, and it really seems to be impossible with current protocol.

[edit: Finished last sentence properly ]

The movement system you talk of is not 'WoW-like', games have been doing it for years. WoW did not create this, nor should it be credited thus.

Our protocol relies on the fact that the client only send the destination, and the server sends the steps. So far, there are no plans to change that, I think it's the best system in terms of simplicity and bandwidth.

If a system were to allow keyboard movement and a client were to only send a 'pulse' of its location say, every 5 steps, surely you would equal or even save bandwidth usage?