Make it handle all the following situations

• login
• logout
• relogin
• page refresh
• change computer
  • login with the same user we are logged in at the first computer

• QUnit
  • disadvantages
    • Non-AMD-compliant
    • Has issues with assert counting: http://screencast.com/t/RbXjKPwoB
    • Not good async support
• Extend Nodeunit to be a lot more browser frendly
  • disadvantages
    • time
• Make my own (tree.js)
  • disadvantages
    • Quite a lot of time
    • and devotion
  • advantages
    • Would be awesome, and the bestest out there, etc...

Is there any else?

Those who open the page get the socket.io broadcasts from the server, even if they don't log in.

• Core actions (0.0.8)
  • Sign in
  • User register
  • Movement
    • FlatOut
      • Up
      • Down
    • DimensionAware
      • Up
      • Down
      • In
      • Out
  • expand, collapse
    • local
      • expand to x level
      • expand current level only
      • expand recursively
      • expand shallowest
      • collapse current level only
      • collapse recursively
      • collapse deepest
    • global
      • expand to x level
      • expand recursively
      • expand shallowest
      • collapse recursively
      • collapse deepest
  • Edit node
    • Line locking
      • enter edit mode
      • leave edit mode
  • Make new node
  • Delete node
    • Atomic
    • Whole tree
  • Move node
    • Atomic
    • Whole tree
  • Copy node
    • Atomic
    • Whole tree
  • Warnings
    • If there are children when you delete
  • Limit recursive functions to 100 nodes
• Level 2
  • Specify anchor point
  • Automatic scroll
  • Mark automatic changes
    • Promotion
    • Demotion
  • Search and jump to a certain location
  • Handle editing permissions
    • Lock outline
    • Unlock outline
• Level 3 (0.1.1+)
  • Clone node (make multiparent node) (synced node maybe)
  • UI
    • Mark cloned texts (eg. with tag) (that shall be general: mark with tag (Riel))
    • Menu appears for a shortcut, where all functions are reachable
    • Upper navigation bar (with numbers or colors) for positioning
    • Show the "mode" of the users
      • a. Edit or navigation mode
      • b. Read and write
    • Loading, (Wizek provides an example) (stands or moves the colored line)
  • Startpoint setting
    • Do nothing
    • collapse
    • collapse recursively
  • Endpoint setting
    • Do nothing
    • expand
    • expand recursively
  • Follow
    • Who is signed in? If I click "follow", I go wehere he is
• Copound
  • Move to child, if there isn't, create one

for refference

• #4

How to reproduce:

• Open /Backbone/index.html in 2 tabs.
• Refresh both tabs (wait till fully loads in, and establishes socketio connection) around 2-3 times.
• Server crashes with this error msg: http://screencast.com/t/sw7C4qSeSlR

Suspicion

Related to session handling, might not support multi-connection by single user.

o.O

Dependencies:

• ✔ #4 Polish model
• ✔ User connect
• ✔ User login
• ✔ User disconnect
• ✔ User logout
• ✔ User register
• ✔ User focus
• ✔ Edit node
  • ✖ Line locking
  • ✔ Edit headline
  • ✔ (Edit Body)
• ✔ Submitting enviromentID (envID) token (both new or old)
• ✔ Make new node
• ✔ Delete node
  • ✖ Atomic
  • ✔ Whole tree
• ✔ #3 Move node
  • ✖ Atomic
  • ✔ Whole tree
• ✖ Copy node
  • ✖ Atomic
  • ✖ Whole tree
• ✖ Clone node (make multiparent node) (synced node maybe)

Now the editor events are bound only after the authentication.
But no one can connect to the editor channel without authentication, so it's an unneccesary double-check.

To be placed on GitHub.

Should broadcast, should display.

Teszt - Elek

Not even at the most basic level.
Argument checking is part of BE vaidation, so therefore is to be tested for and implemented.

// Expected types: user.xyFunct(String, Object, Function)
// test for:
test.doesNotThrow(user.xyFunct)
test.doesNotThrow(function() {
  user.xyFunct(null, Object, Function)
  user.xyFunct(String, null, Function)
  user.xyFunct(String, Object, null)
})

Something like that.

Or would you rather write documentation for the API @Fodi69?
That would allow me not to check inside the code for what's required, but still doesn't replace throughout testing.

@Wizek
I'm thinking about separating the changes into 3 commits.
Or is it not necessary?

Upload Gravatar profile picture! :D

Can you think of any case where it might? E.g. very unlikely case of duplicates or something?

Consider swiching from shortcut.js to https://github.com/jeresig/jquery.hotkeys/blob/master/jquery.hotkeys.js

QUnit doesn't always count the asserts in a test if all of them were successful. But it seems to be picking up when errors happen always. Not anymore, see below.

How to fix this quirk?

Nah, I'm kiding! ;P :D

only testing issue tracker

Based on this: http://jsfiddle.net/Wizek/JPmEA/

For all the functions on the back end up until 0.0.7

git submodule add <gitub_link> <where_to_put_locally>

function(username, password, envId, socketId, cb)

Note: Major points bare emphasis.

Pros:

• Node.js-like (commonJS) file loading brought to the FE as well
  • In-file dependency handling
  • Singleton object of modules
  • Deferred script loading is an ease this way.
  • Can download text files.
    • Useful for i18n
    • Useful for HTML templating

Cons:

• Dependency on just another not-so-much-needed libray
  • Needs to be learned, mastered.
  • Errors can arise just simply because we use it.
    • Generally bad error reporting
• Slightly slower overall pageloading.

Any thoughts?

Tests are happy as hell, and I can't get it to connect in the development environment.

Here: 15c5e0d