Your website deskshell.org is offline... about appjs-deskshell HOT 6 CLOSED

I had to move the server once, but I havent heared any news from the original owner of the domain, so I can not change it myself. His domain still runs on my old IP, therefore invalidated itself. Sorry, but I have no options here...

Am 15.11.2014 um 10:40 schrieb IGitSylvia [email protected]:

I am not sure if you guys have noticed, but your website is offline. I'll come back later to try deskshell.

—
Reply to this email directly or view it on GitHub #52.

from appjs-deskshell.

Is it maybe possible to use a github pages site as website? :) I think that would at least help a little bit :)

from appjs-deskshell.

deskshell.org is now online again :-)

from appjs-deskshell.

Great, you da man!

from appjs-deskshell.

I downloaded Deskshell and I installed your experimental portable version in a none-"C:" partition and it worked flawlessly!

In case you are curious, I used portableapps.com bult-in installer in my in Win8.1 (Update 3) 64bit machine.

:) Now, I have a few questions, I am trying to get my head around what you guys did:

1- Is your windows portable version lacking any features of your other "full" installation?

2- Your demos seem quite adequate in terms of speed, what did you guys use as a server to serve the static files? Is it Node that is serving the static content?

3- I noticed in chrome://chrome/ you guys used Chrome "Version 30.0.1599.69", was this on purpose? Can I carefully replace the binaries in "X:\PortableApps\DeskshellPortable\App\bin\win\DeskshellChrome\App\Chrome-bin\30.0.1599.69" from the more recent version Chrome from portableapps.com?

4- Also there in chrome://chrome/ it says "Update failed (error: 1)". Is updating automatically by design and therefore out of the question?

5- What is actually running Deskhell, is it Chromium or Chrome?

6- I noticed your demos were running on port "61935", is this port number fixed?

7- I really thought I had read some where that php and node were good to go in Deskshell (which was the main reason that attracted me to Deskshell in the first place)... so how do we get php running in there?

8- Is there any performance gains by using your nsis compilation of apps into executables?

9- And my lastly... Is it me, or is your Deskshell running faster than my installed Chrome because it is not using Chrome's sandboxing?

I am very excited I am already thinking on certain php applications I would love to package... 👍

from appjs-deskshell.

1. The "full" installation only adds some windows integration points, so it adds a start menu entry and globally registers *.desk files with deskshell.exe, so you are missing nothing.
2. The architecture is nodejs reads the .desk file and then runs portable chrome as a packaged app pointing to a port that nodejs has opened.
3. DeskshellChrome is the chrome portable application from PortableApps.com (http://portableapps.com/apps/internet/google_chrome_portable) the executable is renamed to DeskshellChrome.exe so that you can more easily see what is running in windows task manager. So yes you can just rename the directory and then install a new portable apps version of chrome and if the new version works ok then delete the old folder. Nodejs launches the chrome binary from the command line so there are no dependencies on the version of chrome you are using.
4. I think this was done by portable apps due to legal issues after repackaging chrome to be portable, basically since this will be running your own locally developed app you don't actually want it to be updated automatically -- what if chrome depreciates an api that your application relies on (remember google gears for example), well then your app would break, however you can have your own updater for the whole application (including your parts) and simply update the directory as needed.
5. Deskshell is "virtual" so it is the combination of having nodejs + chrome together. The exe is a very simple binary (built using NSIS Portable), all it does is start off nodejs with the deskshell.js script and suppresses the console window that nodejs wants to open.
6. Deskshell should find a free port and use that (if I remember correctly), I think there is an option to set a fixed port somewhere as well.
7. We have tried a couple of experiments with php running in deskshell and also with replacing nodejs with a php implementation. Can you file a separate issue for php and I will create a plugin to add that functionality and add it to the documentation as well.
8. performance will be slightly slower, the main reason for bundling into an app is so that all of the files are not exposed on disk enabling users to edit or rename or delete them hence breaking the app. The exe compilation is still experimental at this point and needs more work.
9. Deskshell launches chrome in the packaged apps mode, but pointing to a nodejs port instead of at the disk, therefore depending on your chrome profile/ installed extensions etc it could load faster.

from appjs-deskshell.