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
Does NIM adaptable to other application than Node #79
Comments
I think so. If you could explain your current debugging workflow that
would help better determine if so or not.
…On Mon, May 18, 2020, 7:38 AM daduroy ***@***.***> wrote:
Hello
I'm currently integrating V8Inspector in my company application that
already embeds V8.
I'm currently facing the issue your plugin NIM has already solved for Node
: how to simplify the start of a debug session ?
Do you think it's possible to use NIM to automate the launching of CDT in
my application?
Thanks and regards
Aligre
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#79>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACWT35VYZFBQADJUH74UGRDRSFB53ANCNFSM4NEEPQXQ>
.
|
Yes of course.
|
So my answer to your original question is a more solid yes in this case. |
good news. I haven't tested but I guess NIM wont work without any customization. |
Yes some customization may be needed. |
OK. I'm starting to test NIM. If you have any hints that may help dont hesitate |
I've understood how NIM connect to Node or other process, it's sending http request Get JSON on the specified port. Then to be NIM compatible I think I have only to fix the port number, as in node, and implements the JSON http answer. |
Hello
I'm currently integrating V8Inspector in my company application that already embeds V8.
I'm currently facing the issue your plugin NIM has already solved for Node : how to simplify the start of a debug session ?
Do you think it's possible to use NIM to automate the launching of CDT in my application?
Thanks and regards
Aligre
The text was updated successfully, but these errors were encountered: