Roadmap: widget to implement (and other added functionality) about easygui_qt HOT 6 OPEN

Possible widget:
15. An "About" box, for ease of nicely displaying standard info about a program: name, version, license, homepage, list of developers, documentation writers, translators, etc. An option for an icon background would be nice. wx widgets splits this into two functions: AboutInfo (gather the content) and AboutBox (actual display of the info). It can have toggle-able sections, e.g., to show / hide the actual license.

I could see some people wanting a buttonbox even though get_list_of_choices is available. Maybe it would fit better with their porgram's aesthetics.

I agree that multpasswordbox seems low priority. My guess is that it is intended for changing passwords: one prompt for the old password, and two for the new one, all within the same dialog and all of which should be masked. Or maybe credit card plus security code. So I do think its useful if somewhat specialized (= low priority for 1.0 release?)

from easygui_qt.

yes, an about dialog seems like a good idea. Qt already provides some examples of that.

Edit: this can be done by using show_file with a carefully crafted html file.

from easygui_qt.

started One more idea: implement a "wizard" (apparently known as an "Assistant" on Mac) which could be called show_guide() or show_instructions() show_story(); this would be implemented using QtGui.QWizard() behind the scene.

There would be a few different options for the window shown at each "step":

• include a message (as string)
• show an image (from file name)
• show a formatted file (from file name)

from easygui_qt.

I will remove the validation from the change_password() function; this is something that can be done by the calling program without depending of knowing the internal details of the implementation (which is the case now). Done

I also plan to add a help() function: this function would open a browser window pointing at the url of the api documentation (on the ReadTheDocs site) corresponding to the version being used. This will require not forgetting to update the version number in the module (and move it from __init__.py to easygui_qt.py itself Done added find_help(). Without explicit tagging, we could not retrieve a given version on ReadTheDocs - so it will always go to the latest available information. Since this project is likely to soon reach version 1.0 and very little development is expected afterwards, this should not be a problem.

from easygui_qt.

You write: "Similarly, instead of using a print() function to display a message, show_message() is used which pops a message window."
But with print() the user don't need to do any action and with show_message() the user need to click on OK for the script continue to running.... (and Qt don't support window as thread)
I think you need to mention this

from easygui_qt.

@ttv20 Thanks for your input; I updated the readme file (but do not mention threads).

from easygui_qt.