Hi > Would it not be much more simpler to let a server-script (php?) do this > work? Or if you don't have serverside script -- generate a javascript > file to include with constants. That whould be more portable client-wise > too. >
I 100% guess it would ;) But in that case i'm sort of frustrated to know that the client will recieve the information twice. The first time in the jpg file and the second time in the HTML. Personnaly i like the idea to have client side doing most of the job. On top of that my Internet Provider's free web site hosting solution is realy a minimalistic one. It have been a long time i stoped to wait for improvement on this side, and i don't intend to pay for a professional hosting. I prefer invest into the slow but steady increase of technology that happen time to time on the client side. But i definitly agree that it's more convegnant to have most of the code in one place and to change it once to have all the client side impacted at the same time. > Ignore this comment if you'r writing xpcom for fun :-) I'd like to learn more about xpcom and the best way to do it is to practice i guess. But i don't like to code "Hello world" like sample code. Trying to get ride of my frustrations AND learning how to code XPCOM is the best way i can imagine :) The only question pending is : where can i find a complete and up to date documentation about XPConnect methods exposed by Firefox. I tryed the Firefox version of XPCom Component viewer, but it's not magic. It's not a source of documentation, only a bunch of method names fighting the one the other. I can't guess what they are doing just with there name ;) Benoit Lefevre. _______________________________________________ Mozilla-xpcom mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-xpcom
