=== asac_ is now known as asac [00:27] looks like ff3 doesn't support glyph-orientation-vertical="0" in SVG :( === asac_ is now known as asac [00:47] mozilla bug 319163 [00:47] Mozilla bug 319163 in SVG "vertical writing does not work in SVG" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=319163 [00:48] damn, no fix [00:48] not nominated either [02:14] Jazzva: asac are either around i have a stupid question about a extension [02:15] gnomefreak, I'm here... [02:16] (sorry ... still haven't look at the firegpg. was working on this school project :)) [02:16] im looking at linkwidgets [02:17] and i cant find just that source upstream its almost like they packaged all exteniosn in one [02:17] see http://clav.mozdev.org/source.html [02:18] should i grab all re remove the one i want to new dir and start there? [02:18] and hope it has all files needed [02:19] gnomefreak, the source is there... [02:20] http://www.mozdev.org/source/browse/clav/source/linkwidget/ [02:20] i can't understand your question :)... [02:20] when i tried to grab it it grabed all of thier extensions [02:20] from this link how do i use cvs? [02:23] gnomefreak, dunno... [02:23] try following the instructions provided there [02:23] cvs -d :pserver:guest@mozdev.org:/cvs login [02:24] cvs -d :pserver:guest@mozdev.org:/cvs co clav [02:24] the second one might checkout all extensions [02:24] i haven't used cvs much, but maybe something like this might work (based on intuition) [02:24] cvs -d :pserver:guest@mozdev.org:/cvs co clav/source/linkwidget [02:30] ok will try and yes second one does give all of them [02:32] Jazzva: loosk like it worked [02:32] Jazzva: thanks again ;) [02:32] gnomefreak, no problem :) [02:33] Jazzva: some think bothers me about this mainly the CVS dir. [02:33] gnomefreak@Development:~/linkwidgets$ ls [02:33] clav [02:33] gnomefreak@Development:~/linkwidgets$ cd clav/ [02:33] gnomefreak@Development:~/linkwidgets/clav$ ls [02:33] CVS source [02:33] gnomefreak@Development:~/linkwidgets/clav$ cd CVS/ [02:34] gnomefreak@Development:~/linkwidgets/clav/CVS$ ls [02:34] Entries Entries.Log Entries.Static Repository Root [02:34] gnomefreak@Development:~/linkwidgets/clav/CVS$ cd .. [02:34] gnomefreak@Development:~/linkwidgets/clav$ cd source/ [02:34] gnomefreak@Development:~/linkwidgets/clav/source$ ls [02:34] CVS linkwidget [02:34] just mv linkwidget dir... i think that's the one you need :) [02:34] i guess i should us sources/CVS/linkwideits [02:34] and if you find any CVS dirs inside linkwidget, delete them [02:34] something like [02:35] $ cd linkwidget; find . -name CVS -exec 'rm -rf {}' [02:35] (I think) [02:35] it should work [02:36] from what dir? [02:36] execute that find from linkwidget dir [02:37] so from ~/linkwidgits or ~/linkwidgets/clav/source/? [02:38] im thinking top level since CVS is in top level of both dir [02:39] ~/linkwidgets/clav/source/linkwidgets [02:39] since you need only that one [02:39] the rest are useless for packaging :) [02:41] thats usless as well [02:42] why is it useless? doesn't it contain the source? [02:42] i removed CVS all around the source including in *source/kinkwidgits [02:42] Jazzva: there isnt a copyright file [02:42] bug upstream :) [02:43] gnomefreak@Development:~/linkwidgets/clav/source/linkwidget$ ls [02:43] chrome.manifest content defaults install.rdf lang makexpi tests theme [02:45] there was one i could swear [02:45] is it maybe just in xpi (though it should be in source too, if that's the case) [02:47] i think it was in the full pull from cvs intead of using link... directly [02:47] that isnt so great IMHO [02:48] i might leave this one for tomorrow or next day until i can decide what i want to do with it [02:49] ok [02:50] maybe ill email him in morning about how to grab just thid one extenion ewithcopy* and frieds [02:55] flashgot looks like its windows app and they state for linux/bxd you need wine to run it. is this really one we want to work with? [02:56] http://www.hixie.ch/tests/evil/acid/004/ [02:56] * fta applauds in anticipation [02:56] !info foxmarks hardy [02:56] Package foxmarks does not exist in hardy [03:04] thats 3 i cant find cvs or svn for soure nor anyother mention of source code [03:06] make that 4 [03:18] Jazzva: im heading for bed now. if you want i can tak some of yours while im waiing for replies, but i will look after i sleep [03:19] some of mine? extensions? [03:20] gnomefreak ^ [03:28] fta: ok, I'll look (sorry, travelling for work lately) [03:29] fta: are there binary packages built for 8.04, too? [03:29] crimsun, yes [03:29] ok [03:30] crimsun, and there's a test page too: http://www.double.co.nz/video_test/ [03:34] ok, thanks [03:47] http://mozillalinks.org/wp/2008/07/native-ogg-vorbis-and-theora-support-added-for-firefox-31/ [03:47] going to bed. cu [04:05] * gnomefreak wishes they would put contact on one of their pages [04:14] they said ff acid wont work correct until ff 4.0 [04:35] Jazzva: i know your gone and im headin to bed. can we use bugzilla as Extension developer contact i cant find a devs email address or i gues we could use bugzilla please ping me when your around i might be sleeping but ill have away up so i will dee it if my nick is used ;) [04:36] gnomefreak, you can, I suppose... I usually leave it blank if that's the case :) [04:36] i see there are 4 devs on the pluging page but after reading FAQ it says dont bother them (psrsphrded) [04:37] ill use bugzilla i think [04:37] s/psrsphrded/paraphrased/? [04:39] yep [04:48] ok thats fixed im going to bed. see you in morning [04:48] see you :) [04:49] i'm off too... [09:11] hi ! [09:17] hi XioNoX [09:18] ready to work ! [09:18] I'm just listening to the new queen song [09:28] hehe [09:41] http://mxr.mozilla.org/mozilla/source/browser/base/content/browser.js#5874 [09:41] and line 850 [09:48] XioNoX: ok. what we want something similar like the "missingPluginInstaller.prototype.newMissingPlugin" [09:49] newMissingPlugin or installSinglePlugin ? [09:49] XioNoX: for now "newMissingPlugin" [09:49] ok [09:50] that is the function that accumulates a list of plugins used on a tabbrowser instance [09:50] instead of displaying the notification box, we want to activate the menu entry [09:50] ok [09:50] a big and hard function :D [09:50] (ad the status bar icon) [09:50] XioNoX: well ... its almost exactly how we want it [09:50] ok nice [09:51] it gets the event (which we still need to emit) [09:51] associated is with the right tabbrowser tab [09:52] event.preventDefault(); [09:52] // Fire a PluginNotFound event to trigger the infobar [09:52] var ev = document.createEvent("Events"); [09:52] ev.initEvent("PLUGIN_DETECTED", true, true); [09:52] this.dispatchEvent(ev); [09:52] e.g. browser.missingPlugins[...] = pluginInfo [09:52] add something like that in the xbl ? [09:53] XioNoX: yes. maybe use "PluginUsed" [09:53] as ivent name [09:53] ok [10:11] asac, i use the overlay.js of ubufox or I create a new one ? [10:11] XioNoX: for what? [10:12] to put the modified version of "missingPluginInstaller.prototype.newMissingPlugin" [10:12] i think you should do a separate one ... since the overlay will be a separate as well [10:12] ok [10:29] hi bdrung [10:30] hi [10:30] bdrung: i think i uploaded your extension right? [10:31] yes [10:31] bdrung: i think next step is to normalize the .upstream branch, by using med-xpi-unpack/-pack [10:31] e.g. med-xpi-unpack my.xpi [10:31] bdrung: or are you using upstream sources (e.g. not .xpi)? [10:32] for packaging i used the upstream source package [10:32] bdrung: ok. does your extension have "native" components? [10:32] no [10:32] e.g. .so libraries [10:33] bdrung: how do the yrelease their source packages? [10:33] if we can use a "watch" file, then that would be fine as well [10:33] otherwise its often easier to directly use the .xpi, unpack that with med-xpi-unpack in the .upstream tree [10:33] as tar.gz file. i have added a watch file [10:33] as we can then do auto-syncs [10:34] bdrung: ok cool [10:34] bdrung: is there a way i can automatically download the latest source release? [10:34] (e.g. based on the watch file rule)? [10:35] yes, should be done with wget or something else. watches line: http://crypto.stanford.edu/PwdHash/ stanford-pwdhash-(.*)\.tar.gz [10:35] currently http://crypto.stanford.edu/PwdHash/stanford-pwdhash-1.6.tar.gz [10:36] bdrung: so how would i automize that? [10:36] i want a script that automatically updates the .upstream branch [10:36] ;) [10:36] when there is a new release available [10:36] asac, all extentions can be included in ubuntu or there are a particular policy ? [10:37] how does the scripts work that uses the watches file? [10:37] XioNoX: https://wiki.ubuntu.com/MozillaTeam/Extensions/List [10:37] XioNoX: good licenses is important requirement [10:37] XioNoX: another requirement is "active upstream" ... and at best a "responsive upstream contact" [10:38] bdrung: i think they use uscan [10:38] ok [10:39] XioNoX: and of course a ubuntu QA contact [10:39] ok ;) [10:39] who takes care that we update the package regularaly, and who feels responsible in doing the bug work of that extension [10:40] XioNoX: on that extension list page there is a table that has extensions that are ready for the archive [10:41] there appear to be a bunch of extensions that could be packaged ;) [10:41] but better check with Jazzva who has a better overview [10:41] ;) [10:41] asac: so we should use uscan for detection of new version, compare this with the version in the upstream branch and if newer we should download the new package and extract it [10:42] bdrung: not sure ;) .... if you could figure out how we can best deal with watch file driven extesions i would appreciate it [10:42] asac, It is just to know, I've never pakaged extentions, I could maybe do it after my internship [10:43] bdrung: what we want is a script that looks at .ubuntu branch and if there is a new upstream release, updates the .upstream branch [10:43] XioNoX: sure. nothing to hurry ;) ... packaging extensions is easy and a good starter for packaging [10:44] (well ... can be hard, but usually the complexity should be managable) [10:44] I've already done pakaging "just for fun" few months ago [10:44] oh [10:44] cool [10:45] XioNoX: how long is your internship to continue? [10:45] one more week [10:45] ? [10:45] My last day (for debriefing) is monday 25 [10:45] so yes, 1 more week [10:46] ok cool [10:46] next week we should go through your work and integrate that in ubufox - eventually fixing any bugs/glitches [10:46] so there are final things [10:46] asac: in which language? [10:47] ok, nice and hoping that lobbying make some progress [10:47] hopefully [10:48] bdrung: programming language? [10:48] asac: yes [10:48] bdrung: doesnt matter ;) [10:48] we just need to agree on arguments for that script/program [10:49] bdrung: which language would you prefer? [10:49] asac: ok. i will try to write a script. if shell script is not powerfull enough i prefer to use python [10:49] bdrung: thats fine [10:49] for now use the following contract (if possible): [10:50] because it is easier to use python than shell [10:50] script [10:51] ok [10:53] asac, if I do something like : alert('test1'); [10:53] gBrowser.addEventListener("PluginUsed", gMissingPluginInstaller.PluginUsed, true, true); [10:53] alert('test2'); , I see the test1 but not the test2 [10:53] XioNoX: any error in the error console [10:54] gMissingPluginInstaller.PluginUsed exist, it is the modified version of gMissingPluginInstaller.newMissingPlugin [10:54] nothing [10:54] can you give me the url of the page where there are the about:confing stuff to modify to have more error log ? [10:54] just to check [10:54] XioNoX: instead of alert('test1') do a alert('test1 ' + gBrowser) [10:55] if that isnt null [10:55] check if gMissingPluginInstaller.PluginUsed is really defined [10:55] XioNoX: btw, please name that gAltPluginWizard.pluginsUsed [10:55] r something [10:56] ok [10:56] test1 [object XULElement] [10:57] XioNoX: http://developer.mozilla.org/en/docs/Debugging_JavaScript [10:57] javascript.options.strict = true [10:57] ? [10:57] but I haved to add gBrowser = document.getElementById("content"); begore [10:57] (under Strict code checking ) [10:57] XioNoX: ok. [10:58] XioNoX: see if gBrowser.addEventListener is defined at all [10:58] (with alert) [10:58] Erreur : uncaught exception: [Exception... "Could not convert JavaScript argument" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://ubufox/content/alternatePlugins.js :: :: line 7" data: no] [10:59] whats at that line? [10:59] gBrowser.addEventListener("PluginUsed", gMissingPluginInstaller.PluginUsed, true, true); :) [10:59] XioNoX: i am sure that gMissingPluginInstaller.PluginUsed is wrong there [11:00] I get : function addEventListener() { [11:00] [native code] [11:00] } with alert(gBrowser.addEventListener) [11:00] Ok i'll check that [11:00] ok [11:00] just check that you pass the right arguments to the addEventListener function [11:00] should work [11:18] asac, I4ve try to recode the related function like on the browser.js but I still get the same error :( [11:18] see http://pastebin.mozilla.org/513470 [11:28] XioNoX: why is line 5 after line 3? [11:28] is that correct? [11:28] and you have: gAltPluginWizard.pluginsUsed [11:28] vs. [11:28] altPluginWizard.prototype.PluginUsed [11:29] which cant be right [11:29] right, but I have te same error if I switch them [11:31] test if gAltPluginWizard.pluginsUsed is defined [11:31] most likely thats the problem [11:32] if I do that, i see test 4 : [11:32] gBrowser.addEventListener("PluginUsed", test(), true, true); [11:32] function test(){ [11:32] [11:32] alert('test4'); [11:32] [11:32] } [11:33] but I don't understand how works altPluginWizard.prototype.PluginUsed = function(aEvent) [11:39] XioNoX: well... test() will call the alert even before you get the event [11:39] just "test" would be the equivalent [11:40] so is gAltPluginWizard.pluginsUsed defined? [11:40] test that with an alert [11:41] undefined [11:42] so how does i defined this kind of element ? [11:53] the prototype thing is the right approach from what i can tell [11:59] I go to eat ;) [13:06] back [13:21] XioNoX: any progress? [13:23] I don't understant how works the .prototype. thing :( [13:30] XioNoX: please paste your current diff against ubufox.main [13:33] http://pastebin.mozilla.org/513530 [13:33] I don't know if it is exaclty what you can [13:47] XioNoX: the new .js file is not in the diff [13:47] you have to bzr add filepath [13:47] in order to make it appear in bzr diff [13:48] here : http://pastebin.mozilla.org/513532 [13:49] asac [13:49] yep [13:49] XioNoX: the name is still differnt [13:50] ? [13:51] ok [13:51] fix [13:51] ed [13:53] XioNoX: the altpluginsoverlay xml is not in diff either [13:53] xul [13:54] XioNoX: give me an updated patch with the latest please ;) [13:54] sorry :) [13:57] XioNoX: let me know when you have a fixed diff ;) [13:58] http://pastebin.mozilla.org/513537 [14:10] http://maps.google.com/help/maps/2008summergames/ [14:12] still unsure how we managed to get 4 ;) [14:13] eheh [14:13] asac,it is working [14:13] XioNoX: there still is not the overlay xul file in it [14:13] XioNoX: please look at what you post before you post ;) [14:13] XioNoX: good. at least that [14:13] XioNoX: try to remove all those .css things [14:14] ah you did [14:14] good [14:14] ok [14:14] well ... commit and push up [14:14] ;) [14:15] Maybe It is too fast, when I say it is working, i mean I have no more error message [14:15] but I still don't see test3, even on flash page [14:16] I thinks it is because the event is loaded (by the contructor thing) only once [14:18] is it pushed? [14:19] XioNoX: ? [14:19] the diff : http://pastebin.mozilla.org/513552 [14:19] with everything :D [14:20] yay ;) [14:22] Pushed up to revision 97 [14:22] https://code.launchpad.net/~xionox/ubufox/ubufox.altplugins [14:33] event.preventDefault(); [14:33] that most likely fails [14:34] XioNoX: if you remove that line it works for me [14:36] cool [14:36] I have 4 test3 but it is cool [14:37] XioNoX: well. there are multiple flash files on that page maybe? [14:38] 2 [14:38] so twice ;) [14:39] yep [14:40] So now when we go on e page who have flash content, it show the statusbar idem & menu item [14:41] yes [14:41] but how do I do to remove it if there are no flash content ? [14:45] XioNoX: first question is: where to store the used mime-types [14:45] that should be done per-tab [14:45] if we can access that we would monitor for change in active tab [14:45] and flip the menu state accordingly [15:11] back [15:11] sorry, conexion problem [15:19] u === XioNoX- is now known as XioNoX [16:01] asac, how do you manage by tab things ? [16:09] XioNoX: look at tabbrowser.xml [16:09] there is mCurrentBrowser for instance [16:10] you can listen for changes to that field [16:11] if this field change we run the event thing ? [16:11] to find flash [16:11] ? [16:12] XioNoX: no if this field changes, we look if there are any "usedplugins" stored [16:12] usedplugins is a field where we add the plugins identified by those events [16:13] what you want to do during event is to add the "usedplugins" to a field of the mCurrentBrowser (however get that) [16:14] when mCurrentBrowser changes you look if there are any usedplugins for that browser [16:14] and if so, display the menu/icon [16:14] otherwise hide it [16:14] okay! [16:14] all of this is into the altPluginWizard.prototype.PluginUsed = function(aEvent){ ? [16:15] and is run each time the event thing do something ? [16:15] XioNoX: in that function you want to find the currentbrowser and add the plugin to a array [16:15] or something [16:15] the menu itself listens for changes to currentbrowser and does the hide/show logic [16:19] Hi asac :) I have a couple of general questions, if you are not busy ;) [16:23] 1) have you planned to use the new launchpadlib for the automatic management of the extensions? [16:23] 2) whit this new automatic system what will be the version number policy for the extensions? (in particular for backports) [16:28] Volans: launchpadlib ... not sure. what benefit does it give us? [16:28] anyway ... i am off to sport now ... will be back in 2-3 h [16:28] (sorry) [16:28] ok, we can speak after, no problem === Moot2 is now known as MootBot [19:22] back [19:55] asac: having more fun with branding and langpacks. The issue is my branding changes only have en-US locale so branding changes not picked up in different langs.. [19:56] bfiller: why do your branding changes only have en-US locale? [19:56] asac: was an oversight, I'm trying to add other locales to the branding subdir but they are not getting created [19:57] bfiller: how are you trying to do that? [19:59] bfiller: what you need to do is to modify the .manifest [19:59] and add all the locales you want there [19:59] (given that the branding should be identical for every locale) [20:00] asac: one sec [20:04] asac: which .manifest do I modify? in mozilla/browser/branding/locales there is currently an en-US dir, so I added other local dirs at that level [20:04] asac: s/local/locale [20:05] bfiller: hmm [20:05] bfiller: lets try something different ;) [20:05] asac: I think the bigger problem is the mozilla-langpack packages install a language extension that has it's own branding [20:05] bfiller: locales/jar.mn [20:06] try to duplicate the %locale line ... and replace @AB_CD@ with whatever locale you want to support [20:06] i hope that this will create the proper .manifest lines [20:06] that map the branding for the named locale to en-US brnading [20:06] asac: ok, I'll try that [20:07] % locale branding @AB_CD@ %locale/branding/ [20:07] % locale branding fi %locale/branding/ [20:07] bfiller: ^^ [20:07] if you want to support fi [20:07] keep the AB_CD thing as that will be en-US in the end [20:07] i hope that just works (TM) [20:07] asac: do you think these jars will take precedence to the ones that get installed by mozilla-langpack xpis? [20:10] bfiller: good point [20:10] bfiller: let me think ;) [20:10] bfiller: do you have a install that exposes this behaviour? [20:10] so we can hack around directly in the .manifest? [20:11] asac: don't have an install yet, but I think a way to test.. [20:12] ok. my idea is to add override entries to .manifest [20:12] like: [20:12] override chrome://branding/locale/brand.dtd chrome/mybranding/locale/brand.dtd [20:12] err [20:12] override chrome://branding/locale/brand.dtd chrome://mybranding/locale/brand.dtd [20:13] hopefully that will redirect the chrome resolver to the chrome://mybranding/locale/brand.dtd [20:13] so you can just ship your branding for all locales you support and for the rest it hopefully auto falls back [20:13] to the "mybranding" en-US one [20:15] asac: I will try both of these approaches, thanks for the help [20:15] cp [20:15] np [20:15] ;) [22:03]