Change output file when packaging a chrome extension - google-chrome-extension

When I package my extension folder it outputs with the same name and in the same directory
In the terminal:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --pack-extension=./extension
My project folder:
root/
extension/
manifest.json
...
extension.crx
extension.pem
How can I change the name of the .crx and .pem files and also their destination?
Thanks.

There is no built-in option in Chrome to change the name or destination. You can either add a command to your build process to move the generated files or use the CRX building scripts published here to directly build the files as you please. The one in Ruby already has the options you need. The bash one would require some modification.

Related

How to set RubyMine's default working directory to the executing .rb program's subdirectory?

In RubyMine, I have a project with many subfolders, each of which contains:
One or more standalone single-file executable Ruby programs (.rb files);
An input text file.
In older versions of RubyMine, when running one of the standalone executable programs (via Cmd+Shift+R on my Mac), the default folder in which RubyMine would look for the input file would be the same directory as the .rb file currently being executed -- which worked great.
The code used to read the file is something like:
data = File.readlines('input.txt')
However, after recently updating RubyMine to v2022.3.1, the behavior has changed, such that RubyMines now seems to be looking in the project's root directory for the file, instead of the same subdirectory as the .rb file currently being run. This produces the error:
in `readlines': No such file or directory # rb_sysopen - input.txt (Errno::ENOENT)
To correct this, I've been going into Run (menu) > Edit Configurations; and in the Edit Configurations dialog, in the configuration that RubyMine auto-created for the current executable file, changing the Working Directory value from the default of the project's root directory, to the subfolder of the current .rb file.
However, this above workaround is annoying, since I need to do it once each for every individual one of the many individual .rb executable files in my project.
My question: How can I configure my project and/or RubyMine itself to go back to the older behavior of defaulting a given .rb file to use its own directory as the default Working Directory, instead of the project's root directory?
(This question and/or its solution might also apply to other JetBrains IDEs such as IntelliJ, since they all seem to work similarly.)
The previous behaviour has been changed with https://youtrack.jetbrains.com/issue/RUBY-29236. So now yes, the logic is the following:
in case of no Ruby module, project's root will be used
in case of Rails, its home folder
otherwise the module's root
There is no option to change it in RubyMine but you can configure the configuration template using some variable there as Working directory.

Pack file to user Dekstop from deb archive

Is there a way to set the unpacking destination a single file to user Desktop folder?
To set Something like home\$user\Desktop structure in the package folder.
I know I can set unpacking directory with --root option for the whole package, but I need only part of the archive to be unpacked to the Desktop
You need to write a postinst script. Check out the debian website for details:
https://wiki.debian.org/DebianEdu/HowTo/DistributeFilesToUserDesktops
If your not bothered about having a desktop icon; then I would recommend that you create a path for the launcher. Normal launchers are really .desktop files in /usr/share/applications/

Where are installed Google Chrome extensions stored locally?

I have installed Google Chrome's extension Chrome Office Viewer (Beta) for open Excel, Word and Power Point documents in browser. And now I need to install this extension to others computers in local network.
The problem is that the computers is not connected to the Internet.
How can I extricate (get) installed Google Chrome's extension for installing to others computers (offline)?
Chrome extensions are stored in your filesystem, under the Extensions folder, inside Chrome's user data directory.
Windows XP: C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default\Extensions\<Extension ID>
Windows 10/8/7/Vista: C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\Extensions\<Extension ID>
macOS: ~/Library/Application Support/Google/Chrome/Default/Extensions/<Extension ID>
Linux: ~/.config/google-chrome/Default/Extensions/<Extension ID>
Chrome OS: /home/chronos/Extensions/<Extension ID>
You can copy the extension folder and drop it on a USB or in a network drive.
To install
Open Chrome and go to chrome://extensions.
Make sure Developer Mode is checked.
Click Load Unpacked Extension....
Find your copied directory and click Open.
The extension should install locally.
Rename the file extension .crx to .zip , like ( example.crx to example.zip )
Extract the zip file using Winrar or similar software
and Enjoy :)
To download the crx without store access, use this url.
https://clients2.google.com/service/update2/crx?response=redirect&x=id%3D~~~~%26uc
//replace the ~~~~ characters with the id of extension :
https://chrome.google.com/webstore/detail/ultimate-user-agent-switc/ljfpjnehmoiabkefmnjegmpdddgcdnpo?hl=fr
To install an extension from a crx file, open Extension page and drag and drop the crx inside.
in window you should first enable hidden file and then go to this directory :
Windows 10/8/7/Vista: C:\Users\%USERNAME%\AppData\Local\Google\Chrome\UserData\Default\Extensions\<Extension ID>
in above directory you will see extentions by id
For Ubuntu, now its in path: ~/.config/google-chrome/Profile\ 1/Extensions/ due to introduction of Profiles

TYPO3 Dumy package does not show installation screen

I am trying to install the Dummy package to my laptop.
I have installed WAMP and i have placed the dummy package into the WWW directory.
However when i go to my Localhost from WAMP and click on the dummy page, instead of showing me the installation screen it shows my the directory index.
to create ENABLE_INSTALL_TOOL just use command line
win+r -> type cmd -> navigate to directory -> type: echo > ENABLE_INSTALL_TOOL
Dummy package has no sources inside, you can see, there's no even index.php file.
Use Source + Dummy which will give you an empty TYPO3 system or even better Introduction Package for learning purposes - working and containing lot of samples.
To create ENABLE_INSTALL_TOOL make sure that your system displays files' names with extension ie: open with the Windows Explorer folder where you unziped the package and make sure that it can see filenames as INSTALL.txt (not only INSTALL) if it doesn't you need to search in options of Windows Explorer...)
Then go to folder typo3conf and create just common, empty file ENABLE_INSTALL_TOOL.txt and finally chane it's name and remove .txt extension.
TYPOe install tool will be satisfied.

phonegap Blackberry webworks plugin

I am trying to create a BlackBerry Webworks plugin using Phone gap. I am trying to follow the instructions given in this link:
http://wiki.phonegap.com/w/page/35799737/How%20To%20Create%20a%20PhoneGap%20Plugin%20for%20BlackBerry%20WebWorks
however, the directory structure mentioned in the link and mine vary significantly, also there is no build.xml in the root directory to run the
ant create-plugin command,
Since Phonegap being converted to Cordova Project, has something changed in the process to be followed?
Thanks in advance.
Currently the way plugin is added is different:
Add customplugin.js to your project's www folder and include a reference to it in your html file after cordova.js.
Add the plugin source to your cordova.jar in your projects ext folder. Open cordova.jar with your favorite archive manager or use the jar to copy the CustomPlugin.java file into org/apache/cordova/plugins directory.
In your projects plugins.xml file add the following line:
ref:
https://github.com/phonegap/phonegap-plugins/tree/master/BlackBerry/ChildBrowser

Resources