German keyboard trouble

Hello,

there are limitations when using a german keyboard as discussed for instance on https://github.com/spark/particle-dev/issues/13 (and other places). There is a workaround but not a real solution. However, the actual version of atom seems to not exhibit the bug. So my question is: Will particle provide an actual software, and when this will be?

Alternatively, will it work if we add the particle packages manually to an actual atom installation? If possible: 32 or 64bit atom? In which order we should install the packages?

Best regards

Uli

Hello,

Let me ping someone that might be able to help, @ScruffR are you able to assist?

Kyle

@KyleG, unfortunately not.
I had a duscussion with Wojtek ages ago about this issue (even before my comment on the github issue), but this didn’t lead to a satisfying solution, hence the issue is still open on github.

1 Like

Hello,

I think for Atom 1.18.0 (x64) this issue is solved. I just confirmed it again: @ and backslash are OK. ParticleDev is based on Atom 1.8 (32bit), so the question still remains: Is it possible to import the different Particle packages into Atom 1.18 and what has to be observed?

Uli

Hi Uli, yes it is possible to use Particle Dev packages in Atom by installing particle-dev-complete package. It does require node-gyp dependencies which on Windows are best installed with npm install --global --production windows-build-tools command.

We’re going to update Particle Dev App to the newer version of Atom but we’re currently focused on improvements to the cloud compiler. We’ll circle back asap.

1 Like

@suda, thanks for the explanation.

I installed the node-gyp dependencies as described (no error messages). Then I installed the particle-dev-complete package without error message. And I can find it in the list of installed packages. However, on every restart of Atom I see only a blue message on the top right corner:

“Installing particle-dev-complete dependencies
Installing particle-dev, particle-dev-cloud-functions, particle-dev-cloud-variables, particle-dev-profiles, particle-dev-libraries”.

I assume I should see a new menu entry “Particle Dev” (or similiar) as in the Particle Dev application. But nothing is there.

Sorry, I’m new to Atom and so possibly I did something wrong…

Uli

Oh maybe one of the packages didn’t install correctly. When you go to the installed packages list and search for particle-dev how many packages do you see being installed?

There is only particle-dev-complete shown as installed.

I did some additional search. Looking at https://atom.io/packages/particle-dev and according to the procedure described there I did the following:

Again, when trying to install the particle-dev-complete package I got the same blue message in the top right corner.

After deinstalling the particle-dev-complete package I tried to install particle-dev alone and got the following error message:

npm WARN deprecated spark@0.5.10: Use particle-api-js instead
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-suda-node-serialport-git-release-4-0-1-46edaa09 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a: Cloning into ‘C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a’…
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-suda-node-serialport-git-release-4-0-1-46edaa09 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a: error: cannot spawn sh: No such file or directory
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-suda-node-serialport-git-release-4-0-1-46edaa09 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a: fatal: unable to fork
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-suda-node-serialport-git-release-4-0-1-46edaa09 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a:
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-spec-stubs-git-v0-0-2-4e445e78 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-00f096a7\9a38178961ec6958311156b4bc5193c003c45d5b: Cloning into ‘C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-00f096a7\9a38178961ec6958311156b4bc5193c003c45d5b’…
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-spec-stubs-git-v0-0-2-4e445e78 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-00f096a7\9a38178961ec6958311156b4bc5193c003c45d5b: error: cannot spawn sh: No such file or directory
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-spec-stubs-git-v0-0-2-4e445e78 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-00f096a7\9a38178961ec6958311156b4bc5193c003c45d5b: fatal: unable to fork
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-spec-stubs-git-v0-0-2-4e445e78 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-00f096a7\9a38178961ec6958311156b4bc5193c003c45d5b:
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-views-git-v0-1-0-d5b9fd6e C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-b48319de\53c615628a635c895e0413acda0e5dff3b5a5a9d: Cloning into ‘C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-b48319de\53c615628a635c895e0413acda0e5dff3b5a5a9d’…
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-views-git-v0-1-0-d5b9fd6e C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-b48319de\53c615628a635c895e0413acda0e5dff3b5a5a9d: error: cannot spawn sh: No such file or directory
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-views-git-v0-1-0-d5b9fd6e C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-b48319de\53c615628a635c895e0413acda0e5dff3b5a5a9d: fatal: unable to fork
npm ERR! git clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-spark-particle-dev-views-git-v0-1-0-d5b9fd6e C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-b48319de\53c615628a635c895e0413acda0e5dff3b5a5a9d:
npm ERR! Windows_NT 6.1.7601
npm ERR! argv “C:\Users\XXXXXX\AppData\Local\atom\app-1.18.0\resources\app\apm\bin\node.exe” “C:\Users\XXXXXX\AppData\Local\atom\app-1.18.0\resources\app\apm\node_modules\npm\bin\npm-cli.js” “–globalconfig” “C:\Users\XXXXXX\.atom\.apm\.apmrc” “–userconfig” “C:\Users\XXXXXX\.atom\.apmrc” “install” “C:\Users\XXXXXX\AppData\Local\Temp\d-117523-8800-hyyqth.revky2pgb9\package.tgz” “–runtime=electron” “–target=1.3.15” “–arch=x64” “–global-style” "–msvs_version=2015"
npm ERR! node v6.9.5
npm ERR! npm v3.10.10
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true clone C:\Users\XXXXXX.atom.apm_git-remotes\git-github-com-suda-node-serialport-git-release-4-0-1-46edaa09 C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a
npm ERR! Cloning into ‘C:\Users\XXXXXX\AppData\Local\Temp\npm-5124-4cdbfc99\git-cache-3943db8d\65a9ad6308bb70caccc494bca3fbb9ffd34f0b1a’…
npm ERR! error: cannot spawn sh: No such file or directory
npm ERR! fatal: unable to fork
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\XXXXXX\AppData\Local\Temp\apm-install-dir-117523-8800-1fje0i1.9zaoe6ogvi\npm-debug.log

Uli