Skip to content

Conversation

@AMPITUP
Copy link
Member

@AMPITUP AMPITUP commented Mar 29, 2014

I'm making this out of digi's code from CC. I'll merge the pull when I finish.

Nota Bene: Please do not click 'merge' or delete any branches or anything!!! Thanks!

@DigiWongaDude
Copy link
Contributor

I've noticed 2 problems with 'my' console code. 1) A double space (or more) at the end of any "sentence" results in 1 extra blank word. 2) We'll probably want to use a special character at some point for switches (usually "" or "/") but the replace() function is stripping those out right now. We'll fix these as we need to.

@DigiWongaDude
Copy link
Contributor

[FIXED] Issue: placing the cursor anywhere except at the end of the line affects what is "read" as a command.

@AMPITUP
Copy link
Member Author

AMPITUP commented Mar 30, 2014

ok, sweet!

@DigiWongaDude
Copy link
Contributor

added this to the textarea CSS (in my server sample):

outline: none;
resize: none;
border: none;

P.S. (had to move it because of the slowdown and pain of use in codebit - the codebit is still there though)

This prevents the focus "hightlighting", and removes the default resize and border that comes with a textarea (now it looks and behaves much nicer). The dialog box itself is still resizable, and thus the textarea resizes with THAT. At the moment it resizes using fixed aspect ratio, which is not ideal, I'll have that sorted in a little while, using a technique called "9 grid scaling" (look it up if it's a curious mystery).

An interesting feature, that I hadn't planned (aka "a ghost in the machine") is that the console KEEPS focus even if you click on the other video window. I would expect the focus to be passed to THAT window, but no... click or drag the video window (giving it focus), try typing... the console picks up the keystokes and processes the commands even though the video is classed as the "active" window. Bonus! I couldn't have programmed that if I tried! Er, but I did. :-)

Also added a wicked little particle animation in the lower corner.

@AMPITUP
Copy link
Member Author

AMPITUP commented Mar 31, 2014

Ok, cool! I'm a little slow and wary of adding anything to other files in pull requests because I'm the only one who understands the pull-request collaboration set-up (no offense to anyone else), so ppl can easily mess up the pull request accidentally. So, I'm trying to only change the console.js code. I will post a page on the wiki later about how to use pull-requests to better collaborate with each other.

@DigiWongaDude
Copy link
Contributor

Your post will be much appreciated! (I'm also keeping stuff back and not sure what to do.)

@AMPITUP
Copy link
Member Author

AMPITUP commented Apr 1, 2014

Ok, great! I'll start typing!

@jak6jak
Copy link
Contributor

jak6jak commented Apr 3, 2014

There is a bug if you hold down the enter key you get this:

@AMPITUP
Copy link
Member Author

AMPITUP commented Apr 3, 2014

woah, that's weird. easter egg! xD

@DigiWongaDude
Copy link
Contributor

:-O ! I'll have a look now... awesome... MATRIX eat your heart out :) Nice find Jacob.

[Fixed] - There is a bug if you hold down the enter key.

[Bug] - I'll need to prevent placing the caret on other lines too, but haven't worked that out yet.

  • ... I'll have to force the caret to the end if the user clicks another line with the mouse, and disable the up key. That should do it?

@DigiWongaDude
Copy link
Contributor

I'd like you guys to notice the amount of loose ends that are potentially generated from such small beginnings. This is par for the course. The trick is to build solid foundations so that we don't have to deal with countless loose ends later with beta testers. So thanks again Jacob, nice find. Keep that up! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants