Apologies if this has been asked, but after researching I couldn't find an answer to my question.
I am working on a desktop electron app that runs selenium scripts for the purpose of automating tedious/repetitive tasks. I know how to bundle and distribute my source code, but I want to package the chromedriver.exe to C:\Windows with the installation and to change the system environment variable to reference that on windows.
The people who will be using the program are very tech illiterate, so I want to make this very seamless. Any ideas on how this can be accomplished?
Related
I try some platform to create Linux Desktop application with Blazor (Including ElectronNET), but in most case its empty self advertising without really opportunity to do even simplest task.
Therefore I'm still in searching a good platform to make desktop apps in Linux with Blazor.
Is neutralinojs good fit to this task including development in VS CODE and deployment to end-user?
Neutralinojs is a lot like Electron. The main difference being that Neutralinojs does not use npm or is based on chromium.
This makes Neutralinojs faster than Electron. If you desire to make desktop apps with HTML, CSS, or JS then Neutralinojs would be a good fit for you!
I have tried both and I can tell you that Neutralinojs is the best at a quick startup.
Neutralinojs will work great with any code editor. You can even use the terminal that VS Code provides.
After you finish writing the code for your project, you can run the build command. This command will make executables for any OS including Linux.
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 see there is a project named spark, which is a Chrome app based development environment.
It seems interesting, and I want to run it my own computer(mac os), expected to see a chrome-based IDE for dart. But I can't find any document to tell me how to run it. There are just some pages for how to develop and test, but how to run it?
I tried with the grind shell with all kinds of options, but no lucky :(
Thanks for the question! The Spark effort is still spinning up, and we're not yet ready for a public release. All the source code is available publicly, so it is possible for people to build it for themselves. Once we're further along we'll put a developer preview release up on the chrome web store.
The steps to build & run Spark IDE on Windows are:
Install Dart SDK to e.g. C:\dart-sdk
Download the Spark source code to e.g. C:\spark
Open cmd and type: cd C:\Spark
set PATH=%PATH%;C:\dart-sdk\bin
set DART_SDK=C:\dart-sdk
pub get
grind.cmd deploy
Load the upacked extension from C:\Spark\ide\build\deploy-out\web in Chrome Dev.
Alternatively, you can download Chrome Dev Editor packaged app, based on Spark 0.13,
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 xul app that I think would be useful, and I want to deploy it. The target platform is Linux; I believe it will work on Windows/OSX as well but haven't tested. What is the best way to deploy this app?
Is using xpi packages and requiring the user to install xulrunner separately the way to go?
If I bundle xulrunner, should I keep it local in my program's directory or should I install it in /usr/bin or wherever?
I realize this is two questions, but I think they're related...
Thanks,
Nathan
I deployed an XULRunner based application during the 1.8 to 1.9 transition on Windows. It used XUL, and had some DLL based XPCOM components. The best way for making sure that you have something which will work 'out the box' is to bundle everything - the runtime and the application - into one install. There might be some duplication, but it's probably not worth the effort of sorting it out given the number of people who will already have XULRunner installed on their machine. It certainly wasn't for us (we were the first XULRunner app on BOWMAN kit). But you can also provide the xpi as a courtesy for advanced users, if you feel like it.
Bundle it - that's the recommended method from Mozilla (for now) - and you can make it more user-friendly.
Perhaps someday there will be a great tie with Firefox's xulrunner executable, and you can piggy back off of it. But that day is not today.