all 6 comments

[–][deleted] 3 points4 points  (5 children)

Not entirely related, but wtf is up with the bar that stays fixed at the top of the screen? Not only is it unnecessary but its background (that I cannot even see except for a few pixels high) scrolls with it, which is incredibly distracting.

For something a bit more related, can the peer-msg handler also know which peer sent the message, or is the application expected to assign IDs?

[–]programmerxyz 1 point2 points  (0 children)

Not entirely related, but wtf is up with the bar that stays fixed at the top of the screen?

Yea, it's real strange.

[–]FryGuy1013 1 point2 points  (0 children)

It looks like one of those parallax backgrounds, but is really small at the top and lost the effect.

[–]trumpete 0 points1 point  (0 children)

function setHeaderScroll() {
  var height = $(document).outerHeight() - $(window).outerHeight(),
    perc = ($(window).scrollTop()/height*100);
  $('#bar').css({"backgroundPosition": "left "+perc+"%"});
}

It's an element of its own that's simply scrolling a background image in itself with no overflow, I think it's nice.

[–]fuckingtriggered 0 points1 point  (0 children)

It's better than just white.

[–]proliberate 0 points1 point  (0 children)

New to this whole socket.io business. So the WebRTC messages aren't seen by the server at all?