[Project_owners] Extension Debuggin

Niko Berger niko.berger at corinis.com
Fri Mar 18 22:51:24 EST 2005


Actually I never delete anything. i just keep a winzip window with the 
jar file open, and just drag the changed files into winzip... winzip 
then updates the files in the jar, and when i start firefox, it has 
loads the new files out of the jar.
Niko
Eric Jung wrote:

>Niko,
>I've also been debugging the hard way (re-installing the XPI for each
>and every build) on Windows. I just tried your first suggestion:
>create and install the XPI, then unzip and delete the jar. Now when I
>start Firefox, Firefox hangs with this message in the console:
>
>*** Failed to load overlay
>chrome://passwdmaker/content/passwdmakerOverlay.xul
>
>The directory I have after unzipping is:
>
>c:\Documents and Settings\User1\Application
>Data\Mozilla\Firefox\Profiles\ifk9k760.dev9\extensions\{5872365e-67d1-4afd-9480-fd293bebd20d}\chrome\content\passwdmaker
>
>and
>
>c:\Documents and Settings\User1\Application
>Data\Mozilla\Firefox\Profiles\ifk9k760.dev9\extensions\{5872365e-67d1-4afd-9480-fd293bebd20d}\chrome\skin\classic\passwdmaker
>
>Any ideas what might be wrong?
>
>Thank you,
>Eric Jung
>
>--- Niko Berger <niko.berger at corinis.com> wrote:
>  
>
>>When I write extensions I first create an xpi then install it. Then
>>(using 
>>windows) I open the jar of the extension which resides in the
>>profile 
>>directory under the uid with f.e. winrar and when I update
>>something i just 
>>drag the new file directly in the jar (firefox/tbird/...) closed.
>>When I 
>>start the prog again, the new files are used.
>>
>>Using linux I basically do the same thing, but I write a small
>>script that 
>>recreates the jar.
>>
>>Maybe there is a better way of testing/coding, but it works ok for
>>me. I only 
>>have to stop the program, drag the new files, start again -
>>alltogether only 
>>takes a few secs.
>>
>>Niko
>>
>>On Friday 18 March 2005 17:55, Roman Mironenko wrote:
>>    
>>
>>>Hello everyone.  I am working on my first extension (I am testing
>>>      
>>>
>>it in
>>    
>>
>>>FireFox but eventually I would like to make sure it also runs in
>>>      
>>>
>>the
>>    
>>
>>>Mozilla browser too.)
>>>
>>>My question is this: how do you guys test your extensions?  I got
>>>      
>>>
>>myself
>>    
>>
>>>the JavaScript Debugger (Venkman) and that is good.  But what
>>>      
>>>
>>about XULs?
>>    
>>
>>>Currently I test my extension by installing it and then making
>>>      
>>>
>>some
>>    
>>
>>>changes, rebuilding, reinstalling it.  This is a serious
>>>      
>>>
>>impediment to my
>>    
>>
>>>productivity here.  Even Javascript became impossible to test by
>>>      
>>>
>>itself,
>>    
>>
>>>once I started adding lines like this:
>>>
>>>var russkeyPrefs =
>>>
>>>      
>>>
>Components.classes["@mozilla.org/preferences-service;1"].getService(Compone
>  
>
>>>nts.interfaces.nsIPrefService).getBranch("russkey.");
>>>
>>>
>>>Any suggestions to ease my suffering?
>>>
>>>Thank you.
>>>
>>>
>>>_______________________________________________
>>>Project_owners mailing list
>>>Project_owners at mozdev.org
>>>http://mozdev.org/mailman/listinfo/project_owners
>>>      
>>>
>>-- 
>>Niko Berger
>>niko.berger at corinis.com
>>
>>Corinis
>>NPS Berger KEG
>>Mariahilferstr. 99
>>A-1060 Wien
>>Tel.:+43/1/9415566
>>_______________________________________________
>>Project_owners mailing list
>>Project_owners at mozdev.org
>>http://mozdev.org/mailman/listinfo/project_owners
>>
>>    
>>
>
>  
>



More information about the Project_owners mailing list