You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 22, 2025. It is now read-only.
This will need some re-engineering to work I think.
Currently the Python scans the local files to discover exposed methods, and dynamically inserts it's own exposed methods in the /eel.js file that it hosts.
Both of these happen during startup, before any communication happens.
I think it would require a different method of recreating the exposed methods dynamically.
@ChrisKnott What I am thinking of doing is building the UI locally (using Create React APP, Webpack etc), along with the server. Once complete the UI will be then put up onto my own server and then I package the python server as normal and give this to users. Once it starts, it will go to my server and launch the UI from there.
This kind of already works as is, BUT it only looks at HTTP and I need it to also look at HTTPS. I could fork it and the logic to use HTTPS, but as it's pretty simple enough perhaps you could add it and then I just re-install it ala PIP ?
I am just testing things out at moment but already loving the light bulb moments this is giving me :)
Activity
Mohamad1994HD commentedon Mar 2, 2018
I believe, you may have a remote api, and make api calls from the eel server, fetch them in the customized desktop view.
Or it doesn't seem logical ?
AnthoniG commentedon Mar 2, 2018
@Mohamad1994HD Yea, that's definately one way to go and is the more traditional way of building things.
However there is a major benefit IMO of opening a hosted eel Application
Auto-Update is less painless as everyone is using the same GUI.
Probably more but that's the major one I can think of.
So far I can kinda get it working, but looking into the source it seems it uses http by default (makes sense as that's what
localhostis)ChrisKnott commentedon Mar 2, 2018
This will need some re-engineering to work I think.
Currently the Python scans the local files to discover exposed methods, and dynamically inserts it's own exposed methods in the /eel.js file that it hosts.
Both of these happen during startup, before any communication happens.
I think it would require a different method of recreating the exposed methods dynamically.
AnthoniG commentedon Mar 3, 2018
@ChrisKnott What I am thinking of doing is building the UI locally (using Create React APP, Webpack etc), along with the server. Once complete the UI will be then put up onto my own server and then I package the python server as normal and give this to users. Once it starts, it will go to my server and launch the UI from there.
This kind of already works as is, BUT it only looks at HTTP and I need it to also look at HTTPS. I could fork it and the logic to use HTTPS, but as it's pretty simple enough perhaps you could add it and then I just re-install it ala PIP ?
I am just testing things out at moment but already loving the light bulb moments this is giving me :)
ahopkins commentedon Mar 8, 2018
@AnthoniG Checkout my PR #33 and Issue #30.
I basically added this, and have it up and running with a webpack served dev environment.
ahopkins commentedon Mar 8, 2018
@AnthoniG If you want to see the project I am using it on right now: https://github.com/sockpuppetapp/sockpuppet
AnthoniG commentedon Mar 12, 2018
Closing as this is covered in another threa