-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caption for Windows and Linux #10
Comments
Great! Will follow this =) |
@gielcobben let me know if you need any help. |
Thank you for Windows version |
Thanks I am interested un the Linux version. |
Can you create a new branch for it ? So i can assist you on the linux version port |
Why not just let users on other platforms use current version until redesign is done? The functionality will be identical on all platforms anyway and you don't even need to touch the code. All that needs to be changed are some sass rules so it looks more native but I'm pretty sure that even people who don't use OS X will survive the app's design for while. |
@LosEagle Well in that case just clone the repository modify |
Looking forward to a linux release for this! I'd like to try running it locally but I'm unsure which bits to edit in
|
@macjabeth What if you try running |
@gielcobben Thanks for the quick reply! ^_^ It doesn't fail to run, but nothing comes up after webpack is built. Here's the output: https://pastebin.com/raw/TkuesQ7S Opening localhost:3000 also gives a "Cannot GET /" message. |
@macjabeth Hmm.. weird. What node/npm and electron version are you using? |
node v7.9.0 |
@macjabeth you have the right versions. I think it has something to do with the |
Sorry for the delayed response - my connection is very slow. I seem to be having trouble during the initial setup now.
Possibly an issue on my end so I'll try and fix this error and give an update after everything installs correctly. :) |
What am I doing wrong ? |
I've managed to run [0] webpack: Compiled successfully.
[1] npm run start-hot exited with code 0
--> Sending SIGTERM to other processes..
[0] Stopping dev server
[0] npm run hot-server exited with code null
npm ERR! Linux 4.4.0-89-generic
npm ERR! argv "/home/ivan/.nvm/versions/node/v6.11.2/bin/node" "/home/ivan/.nvm/versions/node/v6.11.2/bin/npm" "run" "dev"
npm ERR! node v6.11.2
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! caption@1.3.0 dev: `concurrently --kill-others "npm run hot-server" "npm run start-hot"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the caption@1.3.0 dev script 'concurrently --kill-others "npm run hot-server" "npm run start-hot"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the caption package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! concurrently --kill-others "npm run hot-server" "npm run start-hot"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs caption
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls caption
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ivan/repos/Caption/npm-debug.log
|
Any luck running it on a Windows? |
Windows Please! |
We're working on Caption V2. This version will be available on all platforms (Mac, Linux and Windows). |
Caption is already non-native with the modified title bar. |
Hi! We launched Caption 2.0 for macOS, Windows and Linux yesterday. Download it here: https://getcaption.co |
For those who may find |
I am currently working on making Caption for Windows and Linux. But because design is an important part of the end product, and I want Caption to be native in Windows and Linux as well, this will take a little time.
The text was updated successfully, but these errors were encountered: