CD's ARE IN!

[ChrisM]

All,

GDC CD's have come in and I will be sending these out ASAP to all who requested them.  Thanks!

-Chris

[endolf]

Cool, can't wait

[kul_th_las]

Whoohoo!

numPosts++;

Games published by our own members! Check 'em out!

[D.t.O]

beauty

This is what you miss if you don't visit this forum in a week
INSERT: almost miss

[ribot]

Is it at all possible to put in a order for a CD now?

[D.t.O]

We had a second batch done, so plenty to go around.  Send mailing information to chris@java-gaming.org and we'll get them out shortly.

Thanks!

-ChrisM

I know that doesn't answer the question (esp. because the post was from almost two months ago), but in case you want to give the order a try, that's how you would do it.

[cfmdobbie]

Um... has anyone received one yet?

[Herkules]

nope ... but snailmail from the US may take some days....

[endolf]

s/days/weeks

[ribot]

I know that doesn't answer the question (esp. because the post was from almost two months ago), but in case you want to give the order a try, that's how you would do it.

Thanks for the info! Will send an email straight away.

Games published by our own members! Check 'em out!

[D.t.O]

s/days/weeks

Can anyone decipher that msg?

Oh and in case anybody cares, I haven't gotten mine yet either.

[endolf]

Can anyone decipher that msg?

Oh and in case anybody cares, I haven't gotten mine yet either.

I guess you've never used vi, the one true text editor , that command would change the word days into the word weeks, making the original comment

nope ... but snailmail from the US may take some weeks....

Endolf

[swpalmer]

I guess you've never used vi, the one true text editor , that command would change the word days into the word weeks

I guess that explains why vi is obsolete
These days we have GUIs where the fields 'search for' and 'replace with' are clearly labeled  (and it would take the same number of keystrokes)

[endolf]

Right, but when accessing my boxes at remote sites, running X, or VNC, or in really bad cases, remote desktop, is an awful lot slower than running vi , I'd like to see what happens when you run one of these fancy gui things over a mobile phone link

Endolf

[cfmdobbie]

(and it would take the same number of keystrokes)

I strongly disagree!  But in the interests of not derailing the topic I'll just leave it at that!

[swpalmer]

Let me demonstrate...

jEdit:
CTRL-f  (1)
days   (4)
TAB    (1)
weeks (5)
ALT-a  (1)
Esc (1)
Total keystrokes = 13

vi:
s  (1)
/  (1)
days (4)
/   (1)
weeks (5)
<enter> (1)
Total keystrokes = 13
maybe +1 if you had to hit Esc to get into the bogus 'command mode' from insert mode or something.

So I stand by my statement.  The vi interface offers no value and only serves to obscure.  the only good thing about it is that it is still around for people that had the misfortune of memorizing the ridiculous manner in which it works - for them it is good because they know how to use it and can therefore use it faster than something that they are less familiar with.

Er.. sorry about the threadjack though.

[Herkules]

well, you could count 'ctrl-f' and 'alt-a' as 2 keystrokes each .....  

[endolf]

I agree, it' two key presses, so even with the esc key in vi, your one key press less needed , and I still think the best reason in this day and age is when using it over a remote connection, I'd never use a gui to edit the config files on the server in the US I prod at, but I use vi all the time on it .

Endolf

[Herkules]

I have two coffee mugs: one with vi and another with emacs commands

Kind of an early online help....

[cfmdobbie]

Let me demonstrate...

Since you ask...

In that specific case, jEdit and Vim require pretty much the same number of keystrokes - there are a couple of extra keys on either side, but it's pretty even.  I think there's some benefit to having everything in one place as opposed to scanning a dialogue for the options you want, but we'll ignore that.

However, how many keystrokes will it take jEdit to remove all blank lines in a file?  This is something I frequently have to do, cleaning up double-spaced text, or even just compacting code or XML down so it's easier to read.  I'm guessing it'll take more than 9 keys.

You've got a numbered list in a text document, and want to insert a new item between 6 and 7.  And there are 400 entries.  How many keys would it take you to fix this?  With Vim it's 8 keys to set up, and then you hold down @@ until you hit the end of the file.  Sweet.

I've used so many different editors, but I keep coming back to Vim.  I'll use the Eclipse editor to edit code, but when I need a bit more power Vim is only two clicks away.

[Jens]

well, you could count 'ctrl-f' and 'alt-a' as 2 keystrokes each .....  

But then "/" counts as two keystrokes, too. Well, at least on some keyboards like mine.  

[endolf]

The way I type its a good few key strokes  

Endolf

[swpalmer]

I think there's some benefit to having everything in one place as opposed to scanning a dialogue...

I wont' ignore that one since it is really related to why vi is obsolete.  You say having everything in one place... but what is that place? Your head? The thing that is a usability issue with VI is that there is ONLY one place, no matter what you are dealing with.  If the command has 10 args you have to put them on one line, in a precisely formatted order with no assistance from the software.  That's a step backward if you ask me.  

I'm all for efficient interfaces, but they can be done without the absence of clarity and simple reminders that a proper GUI offers.  right out of the box VI fights against the non-expert usr when it doesn't have to.  Start up VI and start typing... what happens?  nothing you haven't gone into a proper editing MODE yet..  there will be no error message, just the occasional beep, and possibly a cryptic message at the bottom of the window.  That is useless and stupid to put it bluntly.  VI should be in insert mode all the time unless you have activated some other command.  Other examples.. move to the start of the line in VI - "^"  - a non-sense character that only major nerds (like us) would have any hope of coming up with.  In almost every other editor on the planet "Home" or "CTRL left arrow" or something quite intuitive gets you want you want.  VI works.. it just has an interface that was based on old tech and even then some choices seem pretty bad.  Now VIM (Vi - IMproved) has likely corrected a lot of the brain-dead issues like that, I'm just pointing out the original vi behavior for the sake of the argument .

Regular expressions and a 'repeat action' key-stroke are not exclusive to VI.  You can have the best of both worlds in this case.  That's all I'm saying.

Of course this has nothing to do with CD's being "IN"... but sometimes it's fun to rant

[erikd]

Let me demonstrate...

jEdit:
CTRL-f  (1)
days   (4)
TAB    (1)
weeks (5)
ALT-a  (1)
Esc (1)
Total keystrokes = 13

vi:
s  (1)
/  (1)
days (4)
/   (1)
weeks (5)
<enter> (1)
Total keystrokes = 13
maybe +1 if you had to hit Esc to get into the bogus 'command mode' from insert mode or something.

So I stand by my statement.  The vi interface offers no value and only serves to obscure.  the only good thing about it is that it is still around for people that had the misfortune of memorizing the ridiculous manner in which it works - for them it is good because they know how to use it and can therefore use it faster than something that they are less familiar with.

Er.. sorry about the threadjack though.

TextPad:
F8 (1)  (P.S. notice the regular expressions check box )
days (4)
TAB (1)
weeks (5)
click 'Replace All' (1)

Sorry, I couldn't resist  

[cfmdobbie]

If the command has 10 args you have to put them on one line, in a precisely formatted order with no assistance from the software.  That's a step backward if you ask me.

Off the top of my head I can't think of any 10-argument commands I'd want to issue from Vim.  But assuming such an item, yes, putting them in one line isn't a good idea.

But Vim commands generally only consist of a scope (e.g. %), an expression (e.g. /days/weeks/) and modifiers (e.g. g); three items are really easy to scan in one line.

There's a whole "GUI vs string of characters" analysis that could be covered here, but I think it would just complicate matters.  Maybe we should dedicate a thread to it?

Start up VI and start typing... what happens?  nothing you haven't gone into a proper editing MODE yet..  there will be no error message, just the occasional beep, and possibly a cryptic message at the bottom of the window.

Is it too much to ask that the user knows how to use their software?  You don't move a cursor by tipping the screen, you don't use network shares under Windows 98 for a few minutes after boot, you don't assume that someone got your email just because the mail program said "mail sent sucessfully".  Being a competent user of your computer you know how to make it work.  Is pressing "i" before typing really that much hassle for you?  It's really second nature on starting Vim - after the first week or so of using it, I've never made that mistake again.  I suppose I could put it in an autocommand when the editor boots, but it's only one keypress. *shrug*

Other examples.. move to the start of the line in VI - "^"  - a non-sense character that only major nerds (like us) would have any hope of coming up with.  In almost every other editor on the planet "Home" or "CTRL left arrow" or something quite intuitive gets you want you want.

I press Home, and it works for me.  Yes, could also press "^" to go to the first non-whitespace character, or "0" to go to the first character of any kind.  But Home works as well.  I think you'd be surprised how Vim works out of the box these days - it works pretty much like every other editor.  CTRL-C, CTRL-Z, Home, SHIFT+DOWN - it's all there.

And anyway, your example of CTRL-Left being a "quite intuitive" way of going to the start of the line is an odd one - I expect you'll find that will actually go to the start of the previous word.  Which also works in Vim, by the way.

Now VIM (Vi - IMproved) has likely corrected a lot of the brain-dead issues like that, I'm just pointing out the original vi behavior for the sake of the argument .

Ah, now I see!  Then for the sake of the argument I request that you base your examples on a 30 year old GUI text editor.  


But I see you haven't made the mistake of claiming that you don't need the power that Vim provides!  A pity, it's always so amusing to argue that point...

[cfmdobbie]

weeks (5)
click 'Replace All' (1)

Whoops!  Did you remove your right hand from the keyboard and grope blindly for the mouse in the middle there?

[swpalmer]

Well let's assume he can replace that with TAB TAB TAB.... SPACE if he had to.

oh, and people are still using the original VI and spouting off how wonderful it is.   The whole point of me saying it is obsolete IS based on it being 30 years old with no GUI.  But it is the MODAL nature of it that I find unnecessary and counter intuitive.

[cfmdobbie]

Well let's assume he can replace that with TAB TAB TAB.... SPACE if he had to.

Whoops, there goes the key count...

But it is the MODAL nature of it that I find unnecessary and counter intuitive.

Well, I've got no problem with it at all.  Riding a bike is counter-intuitive at first, but then you get used to it and never have a problem again.  Vim uses the modal system to allow much more flexibility in commands - i.e. you aren't restricted to using combinations of keys to perform actions.  After the first couple of days of using it, it becomes second nature, and you'll never have a problem again.

Many things in computer interface design only seem intuitive because that's the way everyone does it.  Take a look at the desktop metaphor - it's horribly broken in myriad ways.  If anyone approached it as a desktop, they'd quickly lose all their data and get totally confused.  It's only because people approach the desktop metaphor as the desktop metaphor that they can get things done.

If you approach Vim as Vim, i.e. as a mode-based text processing tool, you'll have no problems with it.

[erikd]

Whoops!  Did you remove your right hand from the keyboard and grope blindly for the mouse in the middle there?

Well, yeah! I kinda got used to using the mouse these days you know
Alt-A works too though.

[swpalmer]

 Vim uses the modal system to allow much more flexibility in commands - i.e. you aren't restricted to using combinations of keys to perform actions.  After the first couple of days of using it, it becomes second nature, and you'll never have a problem again.

Many things in computer interface design only seem intuitive because that's the way everyone does it.

Using a "key combination", i.e. a simply qualifier key like CTRL to start an action and have it automatically fall back into insert mode when that action is over, to me is far LESS restrictive than the current way command vs. insert mode works.

There is also something to be said for familiarity.  Yes it IS intuitive because what you have learned for one tool you can apply to another.  There is no need to learn more, and that makes things easier.

You are correct that you can get used to anything.  But why should you have to.  VI is like a bicycle that works different from all the others.  Sure learning to use the bicycle was a little awkward at first.  Once you learn how, you can hop on your friends bike and ride it just as well.  So I DO find fault with VI for being different without any benefit.