>>>>> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Why? Why would we want all Unicode insets to connect to a signal?
>> Why would we want all insets connecting to signals?
Asger> Aside: Even with many Unicode insets, this is not too bad. I
Asger> think Emacs uses around 22 bytes for every single character in
Asger> a document, so LyX should be able to handle the same order
Asger> pretty well.
Arghh, do you mean we are heading to a emacs-weighted program?? I'd
rather avoid that.
Asger> I strongly feel it's necessary to have intraspection in all
Asger> insets: Each inset should be able to identify itself to the
Asger> world (even if we don't adopt this apply-scheme). Maybe the
Asger> enum-scheme was bad because of the administration involved in
Asger> the source files, but we need to come up with something. A raw
Asger> string interface will be fine with me, and useful in other
Asger> situations...
And why not a registering mechanism, where each inset registers
himself and gets an unique identifier? Each Inset could have a
id member that contains that. Something like the following (not
tested, and not really well thought...):
class Inset {
static Identifier id;
}
class Identifier {
static int current_id;
int value;
Identifier() {
value = current_id++
}
}
JMarc
