From philip at aleytys.pc.my Thu Jan 1 01:05:03 2009 From: philip at aleytys.pc.my (Philip Chee) Date: Thu, 01 Jan 2009 17:05:03 +0800 Subject: [Project_owners] problem with z-order of windows/dialogs on OS X In-Reply-To: References: Message-ID: On Thu, 1 Jan 2009 04:25:15 +0530, Mrinal Kant wrote: > I use window.open to open a modal dialog (say, D1) from my extension. From > D1, another modal dialog D2 is opened in a similar way. On Windows, I get D2 > on top of D1 on top of the original extension window. On Mac OS X, however, > D2 hides behind D1. > How can this be fixed? OSX doesn't do modal/dependent windows very well. That's why the Firefox customizeToolbars "window" on OSX is a sheet instead (implemented using a panel+iframe). Perhaps you could do the same. Phil -- Philip Chee , http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. From mrinal.kant at gmail.com Thu Jan 1 10:17:11 2009 From: mrinal.kant at gmail.com (Mrinal Kant) Date: Thu, 1 Jan 2009 23:47:11 +0530 Subject: [Project_owners] problem with z-order of windows/dialogs on OS X In-Reply-To: References: Message-ID: <7a9c88660901011017i1fdf8867v9f503efe048e1cdc@mail.gmail.com> Thanks Philip. But that looks like a different implementation for OSX. Is there no uniform way for all platforms? AFAIK, XUL is supposed to be platform independent. Mrinal. On Thu, Jan 1, 2009 at 2:35 PM, Philip Chee wrote: > OSX doesn't do modal/dependent windows very well. That's why the Firefox > customizeToolbars "window" on OSX is a sheet instead (implemented using > a panel+iframe). Perhaps you could do the same. > > Phil > > -- > Philip Chee , > http://flashblock.mozdev.org/ http://xsidebar.mozdev.org > Guard us from the she-wolf and the wolf, and guard us from the thief, > oh Night, and so be good for us to pass. > > _______________________________________________ > Project_owners mailing list > Project_owners at mozdev.org > https://www.mozdev.org/mailman/listinfo/project_owners > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmbrochu at yahoo.com Mon Jan 12 15:54:23 2009 From: jmbrochu at yahoo.com (Joe Brochu) Date: Tue, 13 Jan 2009 10:24:23 +1030 Subject: [Project_owners] update.rdf Questions Message-ID: <496BD82F.8080804@yahoo.com> An HTML attachment was scrubbed... URL: From stevel at songbirdnest.com Mon Jan 12 15:57:08 2009 From: stevel at songbirdnest.com (Stephen Lau) Date: Mon, 12 Jan 2009 15:57:08 -0800 Subject: [Project_owners] update.rdf Questions In-Reply-To: <496BD82F.8080804@yahoo.com> References: <496BD82F.8080804@yahoo.com> Message-ID: <496BD8D4.6020004@songbirdnest.com> Joe Brochu wrote: > I'm ready for my first release, and I'm confused about the update.rdf > process described here > . > > In particular, where does the update.rdf file go? It doesn't seem > like it would go inside the xpi (e.g. next to install.rdf) because it > can contain a hash of the xpi. > > However, it also seems like it should be included with the xpi so that > the user has access to the update info. I guess I don't understand > how the whole update process works. > > Is any of this even necessary if the xpi is hosted on addons.mozilla.org? > Nope - it's not necessary if you host on AMO. It's only needed if you want to host your own updates on your own server. -- stephen lau | stevel at songbirdnest.com | www.whacked.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmbrochu at yahoo.com Mon Jan 12 16:09:16 2009 From: jmbrochu at yahoo.com (Joe Brochu) Date: Tue, 13 Jan 2009 10:39:16 +1030 Subject: [Project_owners] update.rdf Questions In-Reply-To: <496BD8D4.6020004@songbirdnest.com> References: <496BD82F.8080804@yahoo.com> <496BD8D4.6020004@songbirdnest.com> Message-ID: <496BDBAC.4010904@yahoo.com> An HTML attachment was scrubbed... URL: From eric.jung at yahoo.com Mon Jan 12 17:17:54 2009 From: eric.jung at yahoo.com (Eric H. Jung) Date: Mon, 12 Jan 2009 17:17:54 -0800 (PST) Subject: [Project_owners] update.rdf Questions References: <496BD82F.8080804@yahoo.com> Message-ID: <764333.70998.qm@web30301.mail.mud.yahoo.com> You shouldn't include update.rdf in the XPI. In install.rdf in the XPI, you should include this element: whose content is a URL where the update.rdf can be found. For example: http://myproject.mozdev.org/update.rdf https://developer.mozilla.org/en/Extension_Versioning%2c_Update_and_Compatibility#Update_RDF_Format is an example of the contents of an update.rdf. Eric ________________________________ From: Joe Brochu To: project_owners at mozdev.org Sent: Monday, January 12, 2009 6:54:23 PM Subject: [Project_owners] update.rdf Questions I'm ready for my first release, and I'm confused about the update.rdf process described here. In particular, where does the update.rdf file go? It doesn't seem like it would go inside the xpi (e.g. next to install.rdf) because it can contain a hash of the xpi. However, it also seems like it should be included with the xpi so that the user has access to the update info. I guess I don't understand how the whole update process works. Is any of this even necessary if the xpi is hosted on addons.mozilla.org? Thanks, Joe Brochu http://ganttview.mozdev.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From silfreed at silfreed.net Mon Jan 12 18:42:08 2009 From: silfreed at silfreed.net (Douglas E. Warner) Date: Mon, 12 Jan 2009 21:42:08 -0500 Subject: [Project_owners] update.rdf Questions In-Reply-To: <496BDBAC.4010904@yahoo.com> References: <496BD82F.8080804@yahoo.com> <496BD8D4.6020004@songbirdnest.com> <496BDBAC.4010904@yahoo.com> Message-ID: <496BFF80.9020403@silfreed.net> Joe Brochu wrote: > Thanks. What about hosting the xpi on mozdev > (https://downloads.mozdev.org/...)? > > I'll probably just put it on AMO, since I'll be putting it there > anyways, but it would be good to know. Mozdev provides its own generation of update.rdf files for you and is documented here [1]. One of the biggest differences between Mozdev's release update system and AMO's is that you will need to provide the URL to the update.rdf file in your install.rdf before you upload your .xpi file to us. Let me know if the instructions aren't clear enough. -Doug [1] http://www.mozdev.org/drupal/wiki/MozdevDownloadReleases -- Douglas E. Warner Site Developer Mozdev.org http://www.mozdev.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From belaviyo at gmail.com Fri Jan 30 12:22:22 2009 From: belaviyo at gmail.com (joe ertaba) Date: Fri, 30 Jan 2009 23:52:22 +0330 Subject: [Project_owners] XPCOM call local function Message-ID: <23d9f6b20901301222o42bdd6b2rc480276ac3303afe@mail.gmail.com> Hi I have a XPCOM Component in my extension for observing a process, it can detect process, now my question is how to call extension functions from XPCOM Component ? example: MyExtension -component -chrome --content ---a_js_file.js function foo(var1){ ..... } ---a_xul_file.xul what I want to do is to call foo(...) from XPCOM can somebody help? -------------- next part -------------- An HTML attachment was scrubbed... URL: From silfreed at silfreed.net Fri Jan 30 12:43:33 2009 From: silfreed at silfreed.net (Douglas E. Warner) Date: Fri, 30 Jan 2009 15:43:33 -0500 Subject: [Project_owners] Updated project membership pages and new user overview page Message-ID: <49836675.1070409@silfreed.net> I've been working on bug#19757 [1] and bug#19258 [2] to provide some more member information and protect our users' emails a little better. To that end we now have a user overview page that shows what projects a user is a member of, when they last committed, and how to contact the user; for example: https://www.mozdev.org/profile/overview/silfreed/ Our project overview pages have also been updated to contain a member list with links to the user overview page so it's easier for people to find out what other projects someone works on: https://www.mozdev.org/projects/overview/www/ And finally the pre-existing member page has been updated so the username links to the user overview page as well: http://www.mozdev.org/members.html Feel free to send any comments about the new features/changes my way. -Doug [1] https://www.mozdev.org/bugs/show_bug.cgi?id=19757 [2] https://www.mozdev.org/bugs/show_bug.cgi?id=19258 -- Douglas E. Warner Site Developer Mozdev.org http://www.mozdev.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: OpenPGP digital signature URL: From antonglv at gmail.com Sat Jan 31 10:30:33 2009 From: antonglv at gmail.com (Anton Glazatov) Date: Sun, 01 Feb 2009 01:30:33 +0700 Subject: [Project_owners] XPCOM call local function In-Reply-To: <23d9f6b20901301222o42bdd6b2rc480276ac3303afe@mail.gmail.com> References: <23d9f6b20901301222o42bdd6b2rc480276ac3303afe@mail.gmail.com> Message-ID: <498498C9.6080005@gmail.com> *joe*, you may use code like this: var windowService = Components. classes ["@mozilla.org/appshell/window-mediator;1"]. getService (Components. interfaces. nsIWindowMediator); var mrWindow = windowService. getMostRecentWindow ("navigator:browser"); mrWindow. foo (); or you may implement any interface in your extension's object, it may be somethink like // xpcom .idl ... interface YourComponent: nsISupports { ... void init (in YourComponentCallback obj); ... }; interface YourComponentCallback: nsISupports { ... void foo (); ... }; // xpcom ... extobject: null, ... init: function (obj) { this. extobject = obj; }, ... bar: function () { this. extobject. foo (); }, // call extension's function ... // extension var yourextensionobject = { ... init: function () { var mycomponent = Components. classes ["@yourcomponent.cid"]. createInstance (Components. interfaces. YourComponent); mycomponent. init (this); }, ... foo: function () { ... }, ... QueryIntrface: function (iid) { if ((!iid. equals (Components. interfaces. nsISupprots) && (!iid. equals (Components. interfaces. nsIYourComponentCallback)) Components. results. NS_ERROR_NO_INTERFACE; return this; } }; joe ertaba wrote: > Hi > > I have a XPCOM Component in my extension for observing a process, it > can detect process, now my question is how to call extension functions > from XPCOM Component ? > > example: > > MyExtension > -component > -chrome > --content > ---a_js_file.js > function foo(var1){ > ..... > } > ---a_xul_file.xul > > what I want to do is to call foo(...) from XPCOM > > can somebody help? > ------------------------------------------------------------------------ > > _______________________________________________ > Project_owners mailing list > Project_owners at mozdev.org > https://www.mozdev.org/mailman/listinfo/project_owners > From wallace.jvm at gmail.com Sat Jan 31 21:33:37 2009 From: wallace.jvm at gmail.com (Wallace Araujo) Date: Sun, 1 Feb 2009 03:33:37 -0200 Subject: [Project_owners] Updated project membership pages and new user overview page In-Reply-To: <49836675.1070409@silfreed.net> References: <49836675.1070409@silfreed.net> Message-ID: <92c3c29d0901312133g57b6aff4v95fb37eff762ae97@mail.gmail.com> when I can work in the project? 2009/1/30 Douglas E. Warner > I've been working on bug#19757 [1] and bug#19258 [2] to provide some more > member information and protect our users' emails a little better. > > To that end we now have a user overview page that shows what projects a > user > is a member of, when they last committed, and how to contact the user; for > example: > > https://www.mozdev.org/profile/overview/silfreed/ > > Our project overview pages have also been updated to contain a member list > with links to the user overview page so it's easier for people to find out > what other projects someone works on: > https://www.mozdev.org/projects/overview/www/ > > And finally the pre-existing member page has been updated so the username > links to the user overview page as well: > > http://www.mozdev.org/members.html > > Feel free to send any comments about the new features/changes my way. > > -Doug > > [1] https://www.mozdev.org/bugs/show_bug.cgi?id=19757 > [2] https://www.mozdev.org/bugs/show_bug.cgi?id=19258 > > -- > Douglas E. Warner Site Developer > Mozdev.org http://www.mozdev.org > > > _______________________________________________ > Project_owners mailing list > Project_owners at mozdev.org > https://www.mozdev.org/mailman/listinfo/project_owners > > -- Wallace Araujo -------------- next part -------------- An HTML attachment was scrubbed... URL: