MozillaZine

Where did our files go?

Discuss application theming and theme development.
mcdavis

User avatar
 
Posts: 3195
Joined: December 9th, 2005, 5:51 am

Post Posted September 16th, 2010, 6:05 pm

Yeah. Here's the command I'm using (obviously, with my own paths in there):

Code: Select all
cd d:\mcd\dvl\moztheme\
rem "change date for nightly version "
mkdir fx3.7nightly-0915
cd fx3.7nightly-0915
rem "extracts to current directory"
c:\mozilla-build\info-zip\unzip d:\app\fx3.7nightly\omni.jar chrome\*


Or just leave off the chrome\* bit to get it all.
Last edited by mcdavis on September 20th, 2010, 2:19 am, edited 1 time in total.
Theme Development is Radical Participation.
NNL Beta Builds for Current and Up-coming Firefox
Dear User: Your Help is Needed

mcdavis

User avatar
 
Posts: 3195
Joined: December 9th, 2005, 5:51 am

Post Posted September 19th, 2010, 9:21 pm

Sometimes installed add-ons get repacked as XPIs in the profile/extensions directory. Only a couple, though ... most are in directories of their own. Which ones get repacked and which ones stay in their own directories?

(This is about Bug 533038, the extensions side of omnijar work.)

My own add-on was one of those getting repacked, making it hard to edit the chrome.manifest after install to point to my working files, so I've gone with em:unpacked=true for now. I'd rather just keep doing it the old way if I can figure out how.
Theme Development is Radical Participation.
NNL Beta Builds for Current and Up-coming Firefox
Dear User: Your Help is Needed

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted September 19th, 2010, 10:30 pm

This is probably one of those cases where it's good to have a separate developing install.rdf. In my main theme directory I put in an extra folder called "test". In there I put reference files like notes on things I am working on and various things from the default theme I'm working on including as well as a special chrome.manifest and install.rdf. Then I have two separate xpi's/jar's as well. myaddon.jar and myaddon-test.jar. The first one is for the release version and the second one is for my development version. The development version uses beta version numbers, the single-jar file structure and unpack=true. The release version has the jar-within-a-jar structure, and skips the other two.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

ShareBird

User avatar
 
Posts: 2740
Joined: December 8th, 2004, 7:09 am
Location: Berlin | Made in Brasil

Post Posted September 20th, 2010, 1:49 am

Hmmm.... I don't how you guys have your workbenchs organized. For me, my extension is only packaged when I ship it. The most time it is just a folder named "myExtensionID" with all my files inside it organized according chrome manifest as showed below:

Image

So, I only have to copy and paste this folder inside the extensions folder in my workbench profile. The next time I restart Firefox, the extension will be installed.
Silvermel - A Theme for Firefox and Thunderbird
YATT - Yet Another Theme Tutorial
Don't give a man a fish. Teach him how to fish instead.

CatThief

User avatar
 
Posts: 1854
Joined: January 19th, 2004, 12:19 am
Location: Northeast USA

Post Posted September 20th, 2010, 12:37 pm

ShareBird wrote:Hmmm.... I don't how you guys have your workbenchs organized. For me, my extension is only packaged when I ship it. The most time it is just a folder named "myExtensionID" with all my files inside it organized according chrome manifest as showed below:

Image

So, I only have to copy and paste this folder inside the extensions folder in my workbench profile. The next time I restart Firefox, the extension will be installed.


If the theme or extension is already installed, the old directory structure remains intact. It's the installer that creates the repacked xpi whether it is a new add-on or an update to an existing add-on.

Something I tested and found that works is this: If you are installing something for the first time or updating something that already exists don't use the installer. Instead create a subdirectory with the add-on's GUID. Unpack the theme.jar or extension.xpi and copy the files into that subdirectory just like it appears in your screenshot, then edit the extension.ini file with the path. Start up Firefox and the add-on will be installed without that blasted repacked xpi.
Still passionate for Mozilla themes and extensions, just not actively developing them for public release anymore.

ehume

User avatar
 
Posts: 6743
Joined: November 17th, 2002, 12:33 pm
Location: Princeton, NJ, USA

Post Posted September 20th, 2010, 6:08 pm

CatThief wrote:If the theme or extension is already installed, the old directory structure remains intact. It's the installer that creates the repacked xpi whether it is a new add-on or an update to an existing add-on.

Something I tested and found that works is this: If you are installing something for the first time or updating something that already exists don't use the installer. Instead create a subdirectory with the add-on's GUID. Unpack the theme.jar or extension.xpi and copy the files into that subdirectory just like it appears in your screenshot, then edit the extension.ini file with the path. Start up Firefox and the add-on will be installed without that blasted repacked xpi.


Thank you. Crucial info, this.
Firefox: Sic transit gloria mundi.

ShareBird

User avatar
 
Posts: 2740
Joined: December 8th, 2004, 7:09 am
Location: Berlin | Made in Brasil

Post Posted September 20th, 2010, 6:26 pm

CatThief wrote:
ShareBird wrote:Something I tested and found that works is this: If you are installing something for the first time or updating something that already exists don't use the installer. Instead create a subdirectory with the add-on's GUID. Unpack the theme.jar or extension.xpi and copy the files into that subdirectory just like it appears in your screenshot, then edit the extension.ini file with the path. Start up Firefox and the add-on will be installed without that blasted repacked xpi.

I don't think it's necessary to edit the extensions.ini file. Just placing this subdirectory inside the extensions folder is enough to install the extension. Actually this is what I do and have described above :-)
Silvermel - A Theme for Firefox and Thunderbird
YATT - Yet Another Theme Tutorial
Don't give a man a fish. Teach him how to fish instead.

CatThief

User avatar
 
Posts: 1854
Joined: January 19th, 2004, 12:19 am
Location: Northeast USA

Post Posted September 20th, 2010, 10:51 pm

ShareBird wrote:I don't think it's necessary to edit the extensions.ini file. Just placing this subdirectory inside the extensions folder is enough to install the extension. Actually this is what I do and have described above :-)

Ahhh, so you did, ShareBird. My apologies for reading your post too quickly.
Still passionate for Mozilla themes and extensions, just not actively developing them for public release anymore.

mcdavis

User avatar
 
Posts: 3195
Joined: December 9th, 2005, 5:51 am

Post Posted September 21st, 2010, 5:38 pm

Thanks for the information, everybody. It's nice to know what some of the options are as we live on the bleeding edge yet again.

It turns out I am able to edit the renamed xpi after installing to make the chrome.manifest point to my local files, just like before. For some reason I thought you couldn't, but it's working fine now.
Theme Development is Radical Participation.
NNL Beta Builds for Current and Up-coming Firefox
Dear User: Your Help is Needed

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted September 24th, 2010, 9:44 am

Edit: sorry, I posted in the wrong thread.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

CatThief

User avatar
 
Posts: 1854
Joined: January 19th, 2004, 12:19 am
Location: Northeast USA

Post Posted September 24th, 2010, 6:43 pm

Forgive me if this is old news, but I found something on this blog that will allow us to install our themes without having them converted into the packed xpi file. It's as simple as adding <em:unpack>true</em:unpack> to install.rdf. :D
Still passionate for Mozilla themes and extensions, just not actively developing them for public release anymore.

KLB

User avatar
 
Posts: 2282
Joined: December 21st, 2003, 9:25 am
Location: Saco Maine

Post Posted March 22nd, 2011, 5:47 am

In case someone comes along trying to figure out what is needed from the omni.jar file to build a theme, I was able to build a working default theme by copying the following folders to a separate theme folder:

chrome\browser\skin\classic\aero\
chrome\browser\skin\classic\browser\
chrome\browser\skin\classic\communicator\
chrome\toolkit\content\global\
chrome\toolkit\content\mozapps\

I don't know if there are other folders, but so far all seems to be working just fine for me.
Ken Barbalace - AMO Editor (I focus on reviewing themes)
I maintain Classic Compact, a very compact yet clean Firefox theme.
EnvironmentalChemistry.com (Periodic Table)

patrickjdempsey

User avatar
 
Posts: 23734
Joined: October 23rd, 2008, 11:43 am
Location: Asheville NC

Post Posted March 22nd, 2011, 3:13 pm

I noticed that there were also aero folders in toolkit, but I didn't keep in them to see what was there.
Tip of the day: If it has "toolbar" in the name, it's crap.
What my avatar is about: https://addons.mozilla.org/en-US/seamonkey/addon/sea-fox/

KLB

User avatar
 
Posts: 2282
Joined: December 21st, 2003, 9:25 am
Location: Saco Maine

Post Posted March 22nd, 2011, 4:10 pm

I'm still running on WinXP so I don't currently support aero in my theme and left them out of my theme. Once I get a new machine I'll add in aero support for my theme.
Ken Barbalace - AMO Editor (I focus on reviewing themes)
I maintain Classic Compact, a very compact yet clean Firefox theme.
EnvironmentalChemistry.com (Periodic Table)

ehume

User avatar
 
Posts: 6743
Joined: November 17th, 2002, 12:33 pm
Location: Princeton, NJ, USA

Post Posted March 26th, 2011, 11:07 am

Do they still have a chrome.manifest file?
Firefox: Sic transit gloria mundi.

Return to Theme Development


Who is online

Users browsing this forum: No registered users and 3 guests