I have been trying to install a CRX of a program that I have developed and I want to be able to install it by dragging and dropping it into chrome://extentions to make it easier for the people I am sharing it with. I do not want to load it or unpack it because I will most likely have to explain it to everyone.
I have searched multiple threads and forums researching how to do this, but have found none.
One app I used called moonlight allows you to drag and drop it to install it
(find it here https://github.com/moonlight-stream/moonlight-chrome/releases)
and I am wondering if there is any files I can replicate to make it possible for my program too.
On rockstar55's website (rockstar55.tk) on the school chromebook page, all the crx files he provides are able to be dragged and dropped into chrome://extentions
Related
Actually there i have a html, CSS and java script based app and i created build of it using nw.js technology using build command. The problem is i want the application in dmg format. please help me finding way.
thank you.
There are many different ways to package your app. You should read the documentation:
https://nwjs.readthedocs.io/en/latest/For%20Users/Package%20and%20Distribute/
I do not know of any tutorials for creating an NW.js package as a DMG. Because the final dist is a single .app file, you could distribute that directly, or compressed in a Zip file or something similar. You may be able to look up instructions around DMG packaging that is not specific to NW.js and apply the concepts. If so, and you get it to work, you should write a blog post or tutorial about it.
You can use https://www.npmjs.com/package/appdmg to create an installer for your NW App on macOS platforms.
In my ongoing development for the same i found the making a .pkg installer is better than making .dmg with reasons you can search for.
so i found two solutions for the same.
packages(an application you can package anything with signed developer id)
buildPkg(a command line process to make package)
in both you just need to add your application.app as mentioned in documentation and follow the steps.
I have a bunch of applications that run fine using node-webkit on Macs and Windows.
(They mostly live on shared Dropbox folders. They read and write to data files in the folder).
I gather node-webkit will not run on Mac Catalina.
So I am trying to figure out how to install and use nw.js
I need the Mac and Win versions of the app to be in the same directory. Multiple users will run their local Dropbox version of the app, and read/write to the shared data folders.
I cannot figure out how to get convert the app from node-webkit to nw.js
I've been unable to find an "idiot's guide" to this.
Any suggestions, or pointers to resources, would be most helpful.
Thanks in advance.
And apologies for posting what is probably a dumb question for most users of this site....
You have to run your app's old source code (node-webkit) with NW.js and fix all the exceptions thrown. You can find the migration guide here.
I'm testing a desktop app being built in Electron. Since the app’s layout is CSS/HTML based, I was hoping to do simple layout modifications without access to the source material. Even if I can't see my mods in the running app, it would be useful to extract HTML/CSS/JavaScript templates, modify these and see the results in a browser.
Question 1: Is the above possible?
Based on this question I'm assuming app.asar could be what I'm looking for, but being on Windows 10, it seems that installing asar (and Node, NPM, Python and Visual Studio) just to unarchive files is discouraged.
Question 2: Can I access the files presumed to be inside app.asar without installing all the stuff mentioned above?
I recently finished an application based on Titanium, Javascript, HTML, CSS. I have only been a web designer to date so I have little experience in distributing applications. I was accustomed to the TiDev Community deploying app, which prepared the app for download and made it available for download at a given link.
But tidev community is no longer supported, so I use TideSDK Developer to package the app, which doesnt do all the hard work the other one did so nicely.
I am obviously a complete rookie to this.
Could anyone outline the steps I would need to take to go from the bundled application folder I have now (put together by TideSDK Developer), to a link that will allow customers to download and install the app or online? I know there is an issue with packaoging the app for platforms other than your own, and that appcelerator is working on a solution to this I think. I also realise I would probably have to pay to host the download online. Any guidance would be greatly appreciated.
You must use the tidebuilder.py script. to compile a installation package. To compile a binary for a Mac, you must run the script on a Mac, to compile a binary for windows, you must be on a windows box etc.
There is some documentation on how to use it here per platform. The command is very simple and works.
Once you have your application file (DMG for OSX or a MSI for Windows) then just distribute it however you see fit, email, putting it on your web server, whatever works for you.
I have a Windows CE device that we are deploying, but we have complete control of the software installed on it.
This is not a typical Windows Mobile device, this is a headless device that the user will not interact with. I know that on PDA-style WinCE devices, the .cab file is the preferred application distribution method.
However, on a headless device, we will be writing some type of upgrade/patch server that will ping a server for updates, download them, and auto-install when they are available.
Do I still want a .cab file, or is a .zip (or even something else) better?
What are the requirements for a .cab file - what kind of restrictions / requirements might get in the way and be an annoyance? What are the benefits?
I'd stick with CAB as a package since even headless devices can use the CAB extraction tool. If you ZIP it, then you have to add a ZIP support library and app. CAB also has the ability to add registry entries and define far more disparate target locations than a zip (I want x.dll in \Windows but prog.exe in my program folder - try that with a ZIP).
One thing to keep in mind is that wceload (the CAB extractor) uses a UI by default, so you're going to want to use things like the /noui switch for it.
If you're true headless this may not be an issue (not done that in a long while) but a fairly common "headless" configuration has display support and either the display simply isn't hooked up or is something like a NOP VGAFLAT driver. This allows you to run a shell and have access to all the nice shell APIs, but adds to the challenge that GWES will render dialogs onto the non-existent display.
OpenNETCF also has a CAB Installer SDK that you can use to completely remove any UI with by creating your own installer app. This may or may not be useful depending on the how and when the install happens (through HKLM\Init or otehr for example).