Skip to content
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

Paths in /home/Aix are hardcoded #7

Open
probonopd opened this issue Jun 3, 2017 · 6 comments
Open

Paths in /home/Aix are hardcoded #7

probonopd opened this issue Jun 3, 2017 · 6 comments

Comments

@probonopd
Copy link

Looks like paths in /home/Aix are hardcoded, which of course cannot work.

screenshot_20170603_221747

Instead the application should load the scripts from a relative path "next to itself".

@AIIX
Copy link
Owner

AIIX commented Jun 3, 2017

Those paths are not hard coded instead those paths are editable and should be /home/probonopd/mycroft-core/mycroft.sh .. or any other location you have mycroft-core installed to and click apply that should store the location you have set.

It does not backspace when cursor is on the start point or even selecting the entire text from mouse selection does not work (working on a fix for that) just click at the end of the text selection after 'mycroft.sh' and then hit backspace.

@probonopd
Copy link
Author

any other location you have mycroft-core installed to and click apply that should store the location you have set

Are you saying users need to install mycroft-core manually before using this AppImage?

An AppImage should not require you to have anything installed. Instead it should come with mycroft-core bundled inside the AppImage, and it should launch mycroft-core as required when starting the GUI. This can be achieved by using a small bash script instead of the AppRun symlink.

@AIIX
Copy link
Owner

AIIX commented Jun 4, 2017

This is the AppImage for only the QT GUI application and expects users to have mycroft-core built before using this. I am not sure if Mycroft Core in its current complexity can even be built into the AppImage. Mycroft-Core is python based and requires a functional virtualenv including building the Mimic TTS engine and Pocket-Sphinx. Building an AppImage the size of 2gb (Approx size of Mycroft-core once built) seems like a bad idea.

Additionally users also want the ability to create their own skills, and install other users skills, and change mycroft core configuration this too requires them to have complete access to the mycroft-core folder location. I am not sure how an AppImage would allow such modification.

@probonopd
Copy link
Author

I am not sure if Mycroft Core in its current complexity can even be built into the AppImage. Mycroft-Core is python based and requires a functional virtualenv including building the Mimic TTS engine and Pocket-Sphinx.

Sure, why not. Can you point me to exact instructions on how to install it into a virtualenv?

Building an AppImage the size of 2gb (Approx size of Mycroft-core once built) seems like a bad idea.

Sounds like a great idea to me actually. Simplifies things a lot.

@AIIX
Copy link
Owner

AIIX commented Jun 4, 2017

Sure, why not. Can you point me to exact instructions on how to install it into a virtualenv?

Link to the mycroft-core repo and build instructions: https://github.com/MycroftAI/mycroft-core

@probonopd
Copy link
Author

Seems very cumbersome and involved to set up. Someone indeed should make an AppImage! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants