fef3e7542a
weechat-protocol.js: move getSlice()
2013-10-05 15:32:32 -04:00
0c02cae6a9
weechat-protocol.js: clean _uia2s()
2013-10-05 15:29:18 -04:00
df7d21f63f
weechat-protocol.js: use pointer instead of slicing
...
I don't know if this changes anything to performance, but my instinct
tells me that it's better to update a pointer within a big array to get
slices than creating a new slice each time.
Perhaps the JS engine is clever enough to not create a copy each time
and only update its internal references of the array bounds, but just
in case...
2013-10-05 15:20:42 -04:00
c12f56c614
weechat-protocol.js: uniformize code
2013-10-05 15:10:57 -04:00
7011f8f6b9
weechat-protocol.js: put similar methods nearby
2013-10-05 15:07:49 -04:00
f2b44a4e6b
weechat-protocol.js: prepend _ to private methods names
2013-10-05 15:06:30 -04:00
5a14c1a412
weechat-protocol.js: uiatos -> uia2s
2013-10-05 15:03:36 -04:00
3a9ccc4098
weechat-protocol.js: refactor with prototype
2013-10-05 15:01:51 -04:00
9bdcb814ab
weechat-protocol.js: clean code (indentation/trailing spaces)
2013-10-05 14:24:36 -04:00
a7f3412b5d
protocol.js -> weechat-protocol.js
...
This makes it more clear that this script's code parses the WeeChat
protocol specifically.
2013-10-05 14:23:18 -04:00
Philippe Proulx