Talk:PyXPCOM

From MDC

MozillaZine has some content on the topic: [1], [2]. I'm not familiar with the topic, so I can't judge how good/useful those pages are. --Nickolay 01:42, 2 January 2006 (PST)

Sorry for my late reply. The first link is actually already linked to as Creating a simple Python XPCOM component (external). I'll create an appropriate external link for the second article as well. -- Andreas Wuest 02:48, 9 January 2006 (PST) Update: second link MDCfied as Building standalone PyXPCOM (external). -- Andreas Wuest 09:21, 14 January 2006 (PST)

I think I convinced dria and others to link to the pages directly when possible instead of using external redirects. --Nickolay 19:49, 14 January 2006 (PST)

Hmmm. Although it seems to be easier to link to external resources directly, the downside is that they can not be categorised! There are lots of categories consisting primarily of external articles (e.g. Category:XULRunner:Examples or Category:Canvas examples), which then couldn't be found by readers using the category system to look for certain articles. -- Andreas Wuest 04:30, 15 January 2006 (PST)

The idea would be to have the external redirects still (this enables categorization), but instead of linking to the external redirect page, Nickolay suggested that we link directly to the source. If the link changes, of course, this will require that it be fixed in multiple locations, but, on the other hand, doesn't require any fancy markup to indicate that links are actually external. There are advantages and disadvantages to both methods. For consistency's sake we should have external redirect pages with categories, but when linking, link directly to the source rather than to the external redirect page. If you feel strongly that this is the wrong way to do this, let me know. I'm not particularly attached to either method, personally. -- dria 07:25, 15 January 2006 (PST)

A possible solution to the "edit everywhere" part could be a (new?) extension which can do the dirty work for us, but I am unsure if that would be too complex for our needs here. In the meantime, while other priorities prevail, I suggest using current syntax as dria suggests. --Callek 10:04, 15 January 2006 (PST)

Speaking of disadvantages of linking to external redirects, that was the reason I missed the fact that the first link on the page. Its name was not 100% perfect ("Creating a simple Python XPCOM component", when the page also deals with things like building PyXPCOM) and the domain name was not easily visible because of the use of external redirect. --Nickolay 13:59, 15 January 2006 (PST)

I stumbled across this PyXPCOM page today -- someone should find a place for it, make a redirecting page for it, and link to it in current PyXPCOM documentation. --Waldo 21:07, 7 January 2007 (PST)

Ahem, WHICH page exactly? You may want to provide a link, which would make the whole process of linking against it much easier... ;) --Andreas Wuest 09:52, 8 January 2007 (PST)

Hmm, that was a rather impressive omission, wasn't it? http://public.activestate.com/pyxpcom/tutorial.html -- basically the 5-minute introduction to using XPCOM in Python for someone already familiar with it, especially from JavaScript. --Waldo 01:16, 9 January 2007 (PST)