| chatzilla-service.js |
nsICommandLineHandler |
9192 |
- |
| chatzilla-service.manifest |
|
506 |
- |
| command-manager.js |
@internal
Scans the argument spec, in the format "<a1> <a2> [<o1> <o2>]", into an
array of strings.
|
23431 |
- |
| connection-xpcom.js |
This object implements nsIBadCertListener2
The idea is to suppress the default UI's alert box
and allow the exception to propagate normally
|
14558 |
- |
| dcc.js |
We pick a random start ID, from 0 to DCC_ID_MAX inclusive, then go through
the IDs one at a time, in sequence. We wrap when we get to DCC_ID_MAX. No
uniqueness checking is done, but it takes DCC_ID_MAX connections before we
hit the start ID again. 65,536 IDs ought to be enough for now. :)
|
28437 |
- |
| events.js |
matches a real object against one or more pattern objects.
if you pass an array of pattern objects, |negate| controls whether to check
if the object matches ANY of the patterns, or NONE of the patterns.
|
10766 |
- |
| ident.js |
|
4976 |
- |
| irc-debug.js |
Hook used to trace events.
|
2164 |
- |
| irc.js |
Attached to event objects in onRawData
|
110504 |
- |
| json-serializer.js |
This is a simple set of functions for serializing and parsing JS objects
to and from files.
|
2673 |
- |
| message-manager.js |
strip leading and trailing quote characters, see comment at the
top of venkman.properties.
|
5195 |
- |
| pref-manager.js |
The timer is reset for each change. Only reset if it hasn't been delayed by
this much already, or we could put off a save indefinitely.
|
9994 |
- |
| sts.js |
The base CIRCSTS object.
|
4871 |
- |
| text-logger.js |
Serializer for lists of data that can be printed line-by-line.
If you pass an autoLimit, it will automatically call limit() once the number
of appended items exceeds the limit (so the number of items will never
exceed limit*2).
|
3572 |
- |
| text-serializer.js |
The serialized file format is pretty generic... each line (using any line
separator, so we don't mind being moved between platforms) consists of
a command name, and some parameters (optionally). The commands 'start'
and 'end' mark the chunks of properties for each object - in this case
motifs. Every command inside a start/end block is considered a property
for the object. There are some rules, but we are generally pretty flexible.
Example file:
START <Array>
START 0
"message" "Food%3a%20Mmm...%20food..."
END
START 1
"message" "Busy%3a%20Working."
END
START 2
"message" "Not%20here."
END
END
The whitespace at the start of the inner lines is generated by the
serialisation process, but is ignored when parsing - it is only to make
the file more readable.
The START command may be followed by one or both of a class name (enclosed
in angle brackets, as above) and a property name (the first non-<>-enclosed
word). Top-level START commands must not have a property name, although a
class name is fine. Only the following class names are supported:
- Object (the default)
- Array
For arrays, there are some limitations; saving an array cannot save any
properties that are not numerics, due to limitations in JS' for...in
enumeration. Thus, for loading, only items with numeric property names are
allowed. If an item is STARTed inside an array, and specifies no property
name, it will be push()ed into the array instead.
|
7792 |
- |
| tree-utils.js |
An implemention of |nsITreeView| for a tree whose elements have no children.
Code using BasicOView can override |getRowProperties|, |getColumnProperties|,
|getCellProperties|, etc., as needed.
Code using |BasicOView| will need to make the appropriate |myTree.tree
.invalidate| calls when |myTree.data| changes.
@syntax
var myTree = new BasicOView()
myTree.setColumnNames(["col 1", "col 2"]);
myTree.data = [["row 1, col 1", "row 1, col 2"],
["row 2, col 1", "row 2, col 2"]];
treeBoxObject.view = myTree;
|
38653 |
- |
| utils.js |
Dumps an object in tree format. A sample dumpObjectTree(o) is shown below.
+ parent (object)
+ users (object)
+ bans (object)
+ topic (string) 'ircclient.js:59: nothing is not defined'
+ getUsersLength (function) 9 lines
*
|
27209 |
- |