Closed photomedia closed 6 years ago
The spec file contains mentions of folders that should be included and pathed in the executable bundle. example_data/
and www-data/dnadata
should both be their own folders separate from the executable. That way people can reference the example_data for testing their new program. Though there's also the simple solution that --runserver should just create a folder if it isn't there. It's okay for www-data/dnadata to be empty.
thanks for that, I added the empty folder to DDV/ and the www-data/dnadata reference to the spec file. That removes the error message with the reference to the missing folder, but now there is no error message but --runserver still doesn't work, and there is just no output at all. This works fine when run locally (not from the distribution) so it is something to do with the build.
If you find that you can load a page in the browser, but there's no text output on the application, then it's a problem with output flushing. I found I needed edit some print lines with print('...', flush=True) in the code in order to get it to behave properly in the GUI. These changes are in my GUI branch. Does that sound like the problem you're seeing?
I also have this open issue #54 but I haven't looked into it in more detail, so I couldn't say.
Yes, I added some more error checking, and a flush=True on the last print, and it turns out that the server was being launched. The flush=True got the output onto the GUI, and the server is actually launched. However, it looks like it is launched in a new thread, so you end up with two instances of the application running:
That leaves the GUI with no way to return/edit other than "stop", which leads to this not so friendly message:
If you click on "OK", you do get back to the GUI that allows you to Edit, Restart, Close:
So with the Flush=True, it becomes more usable, but having to go through a duplicate window that needs to Close with a warning is not user friendly.
So this looks like the threading on the httpd.serve_forever() is not working well with the Gooey?
Thanks! That looks like good progress. It shows that "Are you sure" error message on Windows too, which is annoying but sort of a side effect of translating the CTRL+C to stop the server that is the normal command line use case. It could use polish to not alarm users, but it is usable in this state. Similarly, I spent about half a day trying to work out a solution that didn't require me to put flush=True in all my print statements but I didn't find a method that worked. Editing stdout properties wasn't well supported.
Thanks for your help with this. Do you think it's ready to be pushed to the Mac GUI release?
On Thu, Sep 6, 2018 at 4:42 PM Tomasz Neugebauer notifications@github.com wrote:
I added this current version of the distributable FluentDNAgui.app here: https://github.com/josiahseaman/FluentDNA/tree/gui/dist/FluentDNAgui
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/josiahseaman/FluentDNA/issues/58#issuecomment-419142803, or mute the thread https://github.com/notifications/unsubscribe-auth/ACJtFKwfpELXL3lwORvYARDWvBFz5aAPks5uYUJ-gaJpZM4WTq7A .
Sure, I can push a "pre-release" of the MAC GUI bundled "APP", but obviously, the design/layout of the GUI still needs a lot of work and testing.
That sounds like a good plan. I think there are a fair number of users that would feel more comfortable picking through a long GUI than a long cmd --help output.
On Thu, Sep 6, 2018 at 4:55 PM Tomasz Neugebauer notifications@github.com wrote:
Sure, I can push a "pre-release" of the MAC GUI bundled "APP", but obviously, the design/layout of the GUI still needs a lot of work and testing.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/josiahseaman/FluentDNA/issues/58#issuecomment-419147095, or mute the thread https://github.com/notifications/unsubscribe-auth/ACJtFKC7wlzpdTvEFwjMYz06vTgz13dQks5uYUWEgaJpZM4WTq7A .
OK, the pre-release of the GUI for the Mac https://github.com/josiahseaman/FluentDNA/releases/tag/fluentdnagui-macos-prerelease
I ran into an issue while constructing the build (using .spec) for MAC OS for the GUI version.
I'm able to make the distribution, and the GUI launches from the dist folder and the APP bundle, but then when I try to launch --run_server from within the GUI, I get an error like this (running from dist folder):
From the APP bundle, the same folder is not found , but that runs from within a different folder if you just double click on it (running from APP bundle):
Clearly, the www-data/dnadata isn't being found, causing this issue. I pushed the in-development spec file (https://github.com/josiahseaman/FluentDNA/blob/gui/fluentdnagui.spec) for the GUI version, but this issue needs to be solved. Any suggestions or comments on this www-data/dnadata folder?