I am using GraphDB 9.1.1, and I am speaking about my experiences with the web-based Workbench.
I have a folder of .brf binary RDF files on my Mac. Some are .zip compressed, some are .gz compressed, and some are uncompressed.
From Chrome or Firefox under macOS Catalina 10.15.7:
When I click on Import (in the Workbench's left-hand menu) -> RDF -> Upload RDF Files, I can upload the .brf.zip files and the uncompressed files, but not the .brf.gz files. They are greyed out.
Loading one of the .brf.gz files from Chrome in Windows 10 is successful. With some little effort, I could do the whole thing from Windows or Ubuntu Linux, but my team hasn't planned on switching to a newer GraphDB version yet.
The Upload RDF Files hover-over help says
The supported RDF formats are ... .brf ..., as well as their .gz versions and .zip archives
It looks like there is some MacOS issue that won't accept the .gz variants of file extensions (e.g. .brf.gz, .ttl.gz etc) even though they are correctly listed by GraphDB as accepted for the file dialog. There is no workaround in Safari but there is one in Chrome and Firefox:
Click the Options button in the lower left corner.
Choose "All files" instead of "Customised Files".
Please see the attached screenshots.
Note that in the filename should present format or:
if you have file with name movieDB.gz, it won't be available for import, but if the filename is movieDB.brf.gz import will be available and successful.
Related
It might be hard to relate to but VSCode (a code editor) saves all the installed extensions locally in Users folder with the name of .vscode/extensions. Any one can copy the folder and paste it on other system with VSCode installed to have the same extensions (on Windows).
Is there such a folder for Firefox browser add-ons?
I have found the path on windows. [User]\AppData\Roaming\Mozilla\Firefox. There should be three folders each having two extensions related folders where all the extensions are saved.
I am developing a Chrome extension and sharing it with colleagues to test/use. It turns out that if I share my extension as a zipped file and send it to them for testing, those using Windows OS and who uncompress the file there where they got it (Downloads folder) can't see it listed in the file explorer dialog after clicking the "Load unpacked extension..." under chrome//extensions. If they move the extracted folder elsewhere (i.e. Desktop) they can see it without problem.
Is this normal? I haven't been found any reference to such problem anywhere.
Thanks!
How can I permanently install my (toy) WebExtension without having to publish it via Mozilla Addons (AMO), when my extension is just a small group of CSS hacks not meant to be published.
The other option, installing it only permanently would be cumbersome to do everytime I need the extension.
EDIT:
To add further input, the page I've linked to says
Zip up your extension's files Edit
At this point your extension will consist of a directory containing a
manifest.json and any other files it needs - scripts, icons, HTML
documents, and so on. You'll need to zip these into a single file for
uploading to AMO.
One trick is that the ZIP file must be a ZIP of the extension's files
themselves, not of the containing directory.
and also
Packaged extensions in Firefox are called "XPI files", which are just
ZIP files with a different extension.
You don't have to use the XPI extension when uploading to AMO.
In about:addons you can install from file, but whatever way I try to package my extension I get:
even after observing and trying the quoted passage above.
The temporary installation works fine.
You can get your extension signed by AMO but leave it unlisted or you can use one of the Firefox builds that allow signing to be disabled (Nightly or unbranded builds)
You can sign your extension by AMO without publish it.
Then just put an xpi file into
%appdata%\Mozilla\Extensions{ec8030f7-c20a-464f-9b0e-13a3a9e97384}
the browser will accept it.
I would like to force the compatibility of FastDial for the new Firefox 4.5.0.1, and other extensions.
I did this in the past for a lot of addons, I know the procediment... the xpi is just a zip file, that when extracted their contents, you will find a file with name Install.rdf, containing this line:
<em:maxVersion>X.0</em:maxVersion>
Then the desired version is set, and recompress the Zip, and change the .zip extension to .xpi.
However, that methodology is not working for Firefox 45.0.1 (x86).
This is what always happens when trying to install a rebuilt xpi using the known methodology:
The Spanish error-message of the image above says:
This addon cannot be installed because seems damaged.
So... what changed in this damn Firefox 4.5.0.1 that does not accept our rebuilt addons?.
UPDATE
I noted that the problem is with the Install.rdf file, If I do not change the <em:maxVersion>...</em:maxVersion>, then I can recompress properlly the package and it is recognized by this new Firefox.
Then how I need to edit the Install.rdf file to avoid "corrupting" the xpi package for this new Firefox?.
I tried using Wordpard to edit the rdf file, I also tried Sublime Text, saving the file with and without BOM (UTF-8), and for re-compressing the package I used WinRar (I always used WinRar to do it), saving it as Zip, not RAR, of course.
All extensions distributed by Mozilla for Firefox are signed by Mozilla. The files containing the signatures are in the META-INF directory within the extension's top level directory. These signature files are what are used to verify that the extension has not been modified from what has been reviewed and distributed by Mozilla.
To get past the error you are seeing, you will need to remove that directory and its contents.
You will then have an issue that the extension is not signed. Firefox will then refuse to load it for that reason. The quick solution to that is to set xpinstall.signatures.required to false in about:config. However, that will only be effective in release and beta versions of Firefox until the next version update, or so. When exactly changing that option will no longer work is not clear. Turning off the availability of that option in the release and beta versions of Firefox has been a moving target, but the change is coming very soon. The option should continue to work in the Developer Edition of Firefox.
Beyond those options, you will need to have the new extension, which you created by making any changes, signed by Mozilla. You will have to treat it as a new extension (i.e. you will have to create a new ID for it). Some resources which will help in figuring extension signing out (it would be a different question) are:
Signing and distributing your add-on
Add-ons/Extension Signing
Is there any way to change Firefox system icon (the one on the left top of the window)?
Precision : I want to change the icon of a bundled version of Firefox with apache/php and my application. So manual operation on each computer is not a solution.
I try Resource Hacker and it's the good solution. The add ons one is good too.
Resource hacker does the job of swapping application icons in Windows (up to XP, not tested with Vista yet).
Available at:
http://www.angusj.com/resourcehacker/
#phloopy's good suggestion to use http://iconpacks.mozdev.org/ unfortunately doesn't work with newer versions of Firefox (I think to the omni.jar change). You can still use their ICO files (or your own), but you now need to do the following manual steps...
Unzip omni.ja in your Firefox application directory.
Delete omni.ja or rename it (e.g. omni.ja.off).
Create directories icons/default in the Firefox chrome application directory.
Copy the icon file you want to chrome/icons/default/main-window.ico
Start Firefox and enjoy your new icon
Notes:
There are other ICO file names you can use for other windows. The ones I have personally seen work are:
main-window.ico for browser windows and Scratchpad
downloadManager.ico for Downloads
If you know others please comment so I can add them. I personally would love one for Firebug and the Error Console. One for Library (Bookmarks) would be nice also (bookmark-window.ico does not work).
Your start time will be a little slower (due to the unzipping of omni.ja). In theory you can jar it up again, but I am not 100% sure that will work once they get the omni.ja optimization working again (it's "broken" in Firefox 10 so omni.ja is actually normal JAR/ZIP file).
If you let Firefox update you will need to do this again
Note many zip tools cannot read Firefox’s variation on the JAR format (see https://bugzilla.mozilla.org/show_bug.cgi?id=605524).
More info is available at http://iconpacks.mozdev.org/docs/faq.html
There are icon packs available at http://iconpacks.mozdev.org/ that work by installing an extension. If you want to use your own icon, extensions are just zipped files so change the extension from xpi to zip and examine the source code and images it contains to customize it. If you do customize it, I suggest changing the GUID that so it doesn't auto-update and overwrite your customizations.
I think you mean the system icon, not the site icon as someone else thought. On a Mac, you can hold-Click -> Get Info on Firefox.app, then drag or paste an image on top of the icon.
I'm not sure about Windows, but I think you may need to compile from source to change it.
If you're talking about the application icon (which under Windows is typically located in the top-left corner of the application's window), then... no... and yes.
Like most windows apps, the icon you see there is probably a resource compiled into the application itself, so you can't change it.
There may be add-ins to Firefox that let you do this, but I doubt it - that icon is trademarked and "identifies" the Firefox "brand" (if you will). So it's unlikely that you could change it at run-time.
Firefox is open-source; you could always just download & compile your own version, replacing the icon resource with your own. A bit dramatic, but possible.