-
Notifications
You must be signed in to change notification settings - Fork 454
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
Problems developing on Windows #45
Comments
Hey, to open dev tools properly, open the menu on the upper left and pop them out as a separate window. |
Tried that, unable to click any menu :(
…On Sat, Jan 28, 2017 at 4:47 PM Kageetai ***@***.***> wrote:
Hey, to open dev tools properly, open the menu on the upper left and pop
them out as a separate window.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGtNJQyCgOnQxM09emUJNTgks8viMnPks5rW1UbgaJpZM4Lv66G>
.
|
Oh sorry I meant the upper-right and the men with the three dots there |
I know, but on Windows, this button (...) is non-clickable.
…On Sat, Jan 28, 2017 at 5:54 PM Kageetai ***@***.***> wrote:
Oh sorry I meant the upper-right and the men with the three dots there
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGtNLr11ujFxCpCnkghCfnbEA60EGtVks5rW2S6gaJpZM4Lv66G>
.
|
@reflog yep, looks like it is a bug. To open dev-tools you can try to type something (to see some results in cerebro window), and open dev tools after that. In this window is bigger and you can resize it, so you can see dev tools (and try to detach dev tools windows from cerebro windows by clicking ... button). Also, would be cool to fix it for other users. There is an option for |
@KELiON - thanks, that worked! Managed to undock the devtools and now able to see the problems. To communicate with Everything, my plugin is using node-ffi, which is compiled natively and has problems starting under Electron. Here's the log:
Do you have any tips on how to package my module correctly so it would work under Cerebro? This is my first attempt at Electron plugin, so it's a new territory for me... Thanks in advance! |
@reflog can you check that this package installed and works? You can just run |
When I run the code with my local node it runs fine, the problem is with
electron's node runtime being different from my local one.
…On Mon, Jan 30, 2017, 14:12 Alexandr Subbotin ***@***.***> wrote:
@reflog <https://github.com/reflog> can you check that this package
installed and works? You can just run node from
d:\dev\cerebro-plugin-everything\ and try to require it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#45 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGtNI7bQynRTSg1NZA8VMq_Jb0h_VVjks5rXdOagaJpZM4Lv66G>
.
|
@reflog ok, another question: can you check that your local node/npm version are the same, that current electron version uses? Also, you can try to rebuild your native extensions for electron's node/npm by command:
|
Yea, that's the path I'm on right now, tried doing the node-gyp rebuild, but after it's done the bindings are at: And as you can see from the log I posted before, it's not where Electron is looking for them :( |
@reflog did you have any success with your plugin? Do you need any help? |
Well, I've tried following all the steps in the guide that you've referenced with no luck, same result, cannot find the bindings. |
I believe this problem has already been solved with the new version. @dubisdev |
Hi!
![image](https://cloud.githubusercontent.com/assets/109876/22377373/4f938844-e4ba-11e6-8499-33a58a6a1b51.png)
First of all - congrats on an awesome project!
I wanted to contribute a plugin to support results from Everthing by voidtools (a great file indexer on Windows) and wrote a plugin https://github.com/reflog/cerebro-plugin-everything
But I cannot test it well, since the instructions are very Mac oriented and don't work in Windows land.
Opening dev tools doesn't work, since they are shown like this:
And there is no way (that I could find) to see console output from my plugin.
What's your recommended way of debugging on Windows?
Also - how can I mark my plugin as 'windows only' so that other platform users would avoid it?
The text was updated successfully, but these errors were encountered: