Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #83079 > unrolled thread

[ANN] EasyGUI_Qt version 0.9

Back to article view | Back to comp.lang.python

Contents

  [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2014-12-31 14:24 -0800
    Re: [ANN] EasyGUI_Qt version 0.9 wxjmfauth@gmail.com - 2015-01-01 02:39 -0800
    Re: [ANN] EasyGUI_Qt version 0.9 wxjmfauth@gmail.com - 2015-01-02 02:29 -0800
      Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-02 11:11 -0800
        Re: [ANN] EasyGUI_Qt version 0.9 Emil Oppeln-Bronikowski <emil@fuse.pl> - 2015-01-02 20:27 +0100
          Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-02 11:53 -0800
            Re: [ANN] EasyGUI_Qt version 0.9 Emil Oppeln-Bronikowski <emil@fuse.pl> - 2015-01-02 21:21 +0100
              Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-02 13:35 -0800
        Re: [ANN] EasyGUI_Qt version 0.9 wxjmfauth@gmail.com - 2015-01-03 00:52 -0800
          Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-03 09:11 -0800
            Re: [ANN] EasyGUI_Qt version 0.9 Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-01-03 17:38 +0000
              Re: [ANN] EasyGUI_Qt version 0.9 wxjmfauth@gmail.com - 2015-01-04 01:32 -0800
            Re: [ANN] EasyGUI_Qt version 0.9 Michael Torrie <torriem@gmail.com> - 2015-01-03 16:06 -0700
            Re: [ANN] EasyGUI_Qt version 0.9 wxjmfauth@gmail.com - 2015-01-04 00:12 -0800
    Re: [ANN] EasyGUI_Qt version 0.9 stephen.boulet@gmail.com - 2015-01-09 15:08 -0800
      Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-09 16:21 -0800
      Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-09 17:02 -0800
        Re: [ANN] EasyGUI_Qt version 0.9 Chris Warrick <kwpolska@gmail.com> - 2015-01-10 10:32 +0100
        Re: [ANN] EasyGUI_Qt version 0.9 stephen.boulet@gmail.com - 2015-01-13 04:23 -0800
          Re: [ANN] EasyGUI_Qt version 0.9 André Roberge <andre.roberge@gmail.com> - 2015-01-13 12:29 -0800
            Re: [ANN] EasyGUI_Qt version 0.9 stephen.boulet@gmail.com - 2015-01-14 09:12 -0800

Page 1 of 2  [1] 2  Next page →

#83079 — [ANN] EasyGUI_Qt version 0.9

EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.

Like the original EasyGUI (which used Tkinter), 
EasyGUI_Qt seeks to provide simple GUI widgets
that can be called in a procedural program. 

EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.

The archetype is get_string(message)
which pops a box whose purpose is exactly the same as Python's input(prompt),
that is, present the user with a question/prompt, have the user enter an
answer, and return the provided answer as a string.  Thus
easygui_qt.get_string() can be used as a drop-in replacement for
input().

Similarly, instead of using a print() function to display a message,
show_message() is used which pops a message window.

EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.

More information can be found at 
http://easygui-qt.readthedocs.org/en/latest/index.html

Feedback is most welcome, including reporting bugs to 
https://github.com/aroberge/easygui_qt/issues

Happy 2015 everyone,

André Roberge

[toc] | [next] | [standalone]

#83086

Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> 
> Like the original EasyGUI (which used Tkinter), 
> EasyGUI_Qt seeks to provide simple GUI widgets
> that can be called in a procedural program. 
> 
> EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> 
> The archetype is get_string(message)
> which pops a box whose purpose is exactly the same as Python's input(prompt),
> that is, present the user with a question/prompt, have the user enter an
> answer, and return the provided answer as a string.  Thus
> easygui_qt.get_string() can be used as a drop-in replacement for
> input().
> 
> Similarly, instead of using a print() function to display a message,
> show_message() is used which pops a message window.
> 
> EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> 
> More information can be found at 
> http://easygui-qt.readthedocs.org/en/latest/index.html
> 
> Feedback is most welcome, including reporting bugs to 
> https://github.com/aroberge/easygui_qt/issues
> 
> Happy 2015 everyone,
> 
> André Roberge

If it works like eric6, I quickly tested yesterday
morning, it will not work.

jmf

[toc] | [prev] | [next] | [standalone]

#83107

Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> 
> Like the original EasyGUI (which used Tkinter), 
> EasyGUI_Qt seeks to provide simple GUI widgets
> that can be called in a procedural program. 
> 
> EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> 
> The archetype is get_string(message)
> which pops a box whose purpose is exactly the same as Python's input(prompt),
> that is, present the user with a question/prompt, have the user enter an
> answer, and return the provided answer as a string.  Thus
> easygui_qt.get_string() can be used as a drop-in replacement for
> input().
> 
> Similarly, instead of using a print() function to display a message,
> show_message() is used which pops a message window.
> 
> EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> 
> More information can be found at 
> http://easygui-qt.readthedocs.org/en/latest/index.html
> 
> Feedback is most welcome, including reporting bugs to 
> https://github.com/aroberge/easygui_qt/issues
> 
> Happy 2015 everyone,
> 
> André Roberge

I toyed and I spent a couple of hours with it.
I do not know to much what to say.

[toc] | [prev] | [next] | [standalone]

#83125

On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
> Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
snip
> I toyed and I spent a couple of hours with it.
> I do not know to much what to say.
Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!

[toc] | [prev] | [next] | [standalone]

#83126

On Fri, Jan 02, 2015 at 11:11:05AM -0800, André Roberge wrote:

Sorry if this was asked before: have you tried building a portable version using py2exe/Nuitka/etc? I always hit a wall when it comes to building against huge libraries like Python-Qt.

-- 
People are like potatos. They die when you eat them.

[toc] | [prev] | [next] | [standalone]

#83127

On Friday, 2 January 2015 15:22:22 UTC-4, Emil Oppeln-Bronikowski  wrote:
> On Fri, Jan 02, 2015 at 11:11:05AM -0800, André Roberge wrote:
> 
> Sorry if this was asked before: have you tried building a portable version using py2exe/Nuitka/etc? I always hit a wall when it comes to building against huge libraries like Python-Qt.
> 
No, this would seem really silly since the widgets created by EasyGUI_Qt need to be used within a Python program, like Python's own "input()" function.  What would happen if you took a simple module containing the following:

def get_string(prompt):
    return input(prompt)

and tried to package it into an exe?  How could it then be used?

> -- 
> People are like potatos. They die when you eat them.

[toc] | [prev] | [next] | [standalone]

#83129

On Fri, Jan 02, 2015 at 11:53:26AM -0800, André Roberge wrote:
> How could it then be used?

Maybe I failed to explain myself fully. What I meant to say is building a distribution-ready program that utilizes your library; not your library being turn into a executable.

Or maybe something is going over my head? Tell you what, once I get to some decent network I'll try it on my own. :)
-- 
People are like potatos. They die when you eat them.

[toc] | [prev] | [next] | [standalone]

#83134

On Friday, 2 January 2015 16:22:21 UTC-4, Emil Oppeln-Bronikowski  wrote:
> On Fri, Jan 02, 2015 at 11:53:26AM -0800, André Roberge wrote:
> > How could it then be used?
> 
> Maybe I failed to explain myself fully. What I meant to say is building a distribution-ready program that utilizes your library; not your library being turn into a executable.

Ah, this makes sense.  But I have not had the need to do so mysefl.
> 
> Or maybe something is going over my head? Tell you what, once I get to some decent network I'll try it on my own. :)
Please, let me know what you think - direct email is probably better.
> -- 
> People are like potatos. They die when you eat them.

[toc] | [prev] | [next] | [standalone]

#83147

Le vendredi 2 janvier 2015 20:11:25 UTC+1, André Roberge a écrit :
> On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
> > Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> > > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> snip
> > I toyed and I spent a couple of hours with it.
> > I do not know to much what to say.
> Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!

Do not get me wrong, I do not wish to be rude.
You are building a tool upon a toolkit which
simply does not work properly.

If for some reason you are not aware of this,
you are not aware of this, it is unfortunately
a simple as this.

(Not only I know why, I'm able to explain the
cause).

jmf

[toc] | [prev] | [next] | [standalone]

#83167

On Saturday, 3 January 2015 04:52:21 UTC-4, wxjm...@gmail.com  wrote:
> Le vendredi 2 janvier 2015 20:11:25 UTC+1, André Roberge a écrit :
> > On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
> > > Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> > > > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> > snip
> > > I toyed and I spent a couple of hours with it.
> > > I do not know to much what to say.
> > Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!
> 
> Do not get me wrong, I do not wish to be rude.
> You are building a tool upon a toolkit which
> simply does not work properly.
> 
> If for some reason you are not aware of this,
> you are not aware of this, it is unfortunately
> a simple as this.
> 
> (Not only I know why, I'm able to explain the
> cause).

Would you care to elaborate?  All the code I have written works correctly on all the tests I have done.  I do have reports from a user using a Mac with Python 2.7 for which some widgets did not quite work properly ... but that's all I have heard about problems with it. 

I would like to hear about the problems you know about either here, on by filing an issue at https://github.com/aroberge/easygui_qt/issues
> 
> jmf

[toc] | [prev] | [next] | [standalone]

#83169

On 03/01/2015 17:11, André Roberge wrote:
> On Saturday, 3 January 2015 04:52:21 UTC-4, wxjm...@gmail.com  wrote:
>> Le vendredi 2 janvier 2015 20:11:25 UTC+1, André Roberge a écrit :
>>> On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
>>>> Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
>>>>> EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
>>> snip
>>>> I toyed and I spent a couple of hours with it.
>>>> I do not know to much what to say.
>>> Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!
>>
>> Do not get me wrong, I do not wish to be rude.
>> You are building a tool upon a toolkit which
>> simply does not work properly.
>>
>> If for some reason you are not aware of this,
>> you are not aware of this, it is unfortunately
>> a simple as this.
>>
>> (Not only I know why, I'm able to explain the
>> cause).
>
> Would you care to elaborate?  All the code I have written works correctly on all the tests I have done.  I do have reports from a user using a Mac with Python 2.7 for which some widgets did not quite work properly ... but that's all I have heard about problems with it.
>
> I would like to hear about the problems you know about either here, on by filing an issue at https://github.com/aroberge/easygui_qt/issues
>>
>> jmf

I hope you know that you're engaging with a person who makes statements 
about the inadequacies of various tools, but when challenged to provide 
evidence to support his claims he can never do so.  He is our "Resident 
Unicode Expert", in other words when it comes to Unicode he hasn't got 
the faintest idea what he's talking about, at least with respect to PEP 
393 and the Flexible String Representation.  Please ignore him as he's 
just not worth the effort.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [prev] | [next] | [standalone]

#83192

Le samedi 3 janvier 2015 18:39:32 UTC+1, Mark Lawrence a écrit :
> On 03/01/2015 17:11, André Roberge wrote:
> > On Saturday, 3 January 2015 04:52:21 UTC-4, wxjm...@gmail.com  wrote:
> >> Le vendredi 2 janvier 2015 20:11:25 UTC+1, André Roberge a écrit :
> >>> On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
> >>>> Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> >>>>> EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> >>> snip
> >>>> I toyed and I spent a couple of hours with it.
> >>>> I do not know to much what to say.
> >>> Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!
> >>
> >> Do not get me wrong, I do not wish to be rude.
> >> You are building a tool upon a toolkit which
> >> simply does not work properly.
> >>
> >> If for some reason you are not aware of this,
> >> you are not aware of this, it is unfortunately
> >> a simple as this.
> >>
> >> (Not only I know why, I'm able to explain the
> >> cause).
> >
> > Would you care to elaborate?  All the code I have written works correctly on all the tests I have done.  I do have reports from a user using a Mac with Python 2.7 for which some widgets did not quite work properly ... but that's all I have heard about problems with it.
> >
> > I would like to hear about the problems you know about either here, on by filing an issue at https://github.com/aroberge/easygui_qt/issues
> >>
> >> jmf
> 
> I hope you know that you're engaging with a person who makes statements 
> about the inadequacies of various tools, but when challenged to provide 
> evidence to support his claims he can never do so.  He is our "Resident 
> Unicode Expert", in other words when it comes to Unicode he hasn't got 
> the faintest idea what he's talking about, at least with respect to PEP 
> 393 and the Flexible String Representation.  Please ignore him as he's 
> just not worth the effort.
> 
> -- 
> My fellow Pythonistas, ask not what our language can do for you, ask
> what you can do for our language.

Related to the subject.
I suggest you recommend "Qt" to use it. I will
certainly not do it.
At least, try to put MvL and PT in touch.

jmf

[toc] | [prev] | [next] | [standalone]

#83185

On 01/03/2015 10:11 AM, André Roberge wrote:
> Would you care to elaborate?  All the code I have written works
> correctly on all the tests I have done.  I do have reports from a
> user using a Mac with Python 2.7 for which some widgets did not quite
> work properly ... but that's all I have heard about problems with it.
> 
> 
> I would like to hear about the problems you know about either here,
> on by filing an issue at
> https://github.com/aroberge/easygui_qt/issues

It's not clear to me that jmf even understands what easygui is intended
to do.  So I wouldn't worry too much about what he says.  So I'd just
ignore what he has to say.  If someone needs a full event-driven GUI,
they can use an appropriate toolkit.  For quick and dirty little
utilities I can see how easygui fits the bill, and being Qt-based is
good news.

By the way, I'm not seeing jmf's emails; I think they are being filtered
at the mailing list level.  I think enough people got tired of his
trolling that they banned him, though on USENET he's still getting through.

[toc] | [prev] | [next] | [standalone]

#83190

Le samedi 3 janvier 2015 18:11:22 UTC+1, André Roberge a écrit :
> On Saturday, 3 January 2015 04:52:21 UTC-4, wxjm...@gmail.com  wrote:
> > Le vendredi 2 janvier 2015 20:11:25 UTC+1, André Roberge a écrit :
> > > On Friday, 2 January 2015 06:29:37 UTC-4, wxjm...@gmail.com  wrote:
> > > > Le mercredi 31 décembre 2014 23:24:50 UTC+1, André Roberge a écrit :
> > > > > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> > > snip
> > > > I toyed and I spent a couple of hours with it.
> > > > I do not know to much what to say.
> > > Well, this is more positive than your previous comment expressing doubt that it would work. ;-)   So, thank you!
> > 
> > Do not get me wrong, I do not wish to be rude.
> > You are building a tool upon a toolkit which
> > simply does not work properly.
> > 
> > If for some reason you are not aware of this,
> > you are not aware of this, it is unfortunately
> > a simple as this.
> > 
> > (Not only I know why, I'm able to explain the
> > cause).
> 
> Would you care to elaborate?  All the code I have written works correctly on all the tests I have done.  I do have reports from a user using a Mac with Python 2.7 for which some widgets did not quite work properly ... but that's all I have heard about problems with it. 
> 
> I would like to hear about the problems you know about either here, on by filing an issue at https://github.com/aroberge/easygui_qt/issues
> > 

The Qt wrappers (PySide, PyQt4, PyQt5) for Py32 works
very smoothly. With the newer versions problems are
expected (and appear).

In a similar way, LibreOffice is also not working.

[toc] | [prev] | [next] | [standalone]

#83476

On Wednesday, December 31, 2014 at 4:24:50 PM UTC-6, André Roberge wrote:
> EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> 
> Like the original EasyGUI (which used Tkinter), 
> EasyGUI_Qt seeks to provide simple GUI widgets
> that can be called in a procedural program. 
> 
> EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> 
> The archetype is get_string(message)
> which pops a box whose purpose is exactly the same as Python's input(prompt),
> that is, present the user with a question/prompt, have the user enter an
> answer, and return the provided answer as a string.  Thus
> easygui_qt.get_string() can be used as a drop-in replacement for
> input().
> 
> Similarly, instead of using a print() function to display a message,
> show_message() is used which pops a message window.
> 
> EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> 
> More information can be found at 
> http://easygui-qt.readthedocs.org/en/latest/index.html
> 
> Feedback is most welcome, including reporting bugs to 
> https://github.com/aroberge/easygui_qt/issues
> 
> Happy 2015 everyone,
> 
> André Roberge

Very nice, thanks.

One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.

[toc] | [prev] | [next] | [standalone]

#83478

On Friday, 9 January 2015 19:09:15 UTC-4, stephen...@gmail.com  wrote:

> Very nice, thanks.
> 
> One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.

Unfortunately, this is the default calendar widget from Qt - I just use the default:
 ...     def confirm(self):
        self.date = self.cal.selectedDate()

Perhaps I can find something in the docs to see if I could have the format configurable.

[toc] | [prev] | [next] | [standalone]

#83479

On Friday, 9 January 2015 19:09:15 UTC-4, stephen...@gmail.com  wrote:
> On Wednesday, December 31, 2014 at 4:24:50 PM UTC-6, André Roberge wrote:
> > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> > 
> > Like the original EasyGUI (which used Tkinter), 
> > EasyGUI_Qt seeks to provide simple GUI widgets
> > that can be called in a procedural program. 
> > 
> > EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> > 
> > The archetype is get_string(message)
> > which pops a box whose purpose is exactly the same as Python's input(prompt),
> > that is, present the user with a question/prompt, have the user enter an
> > answer, and return the provided answer as a string.  Thus
> > easygui_qt.get_string() can be used as a drop-in replacement for
> > input().
> > 
> > Similarly, instead of using a print() function to display a message,
> > show_message() is used which pops a message window.
> > 
> > EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> > 
> > More information can be found at 
> > http://easygui-qt.readthedocs.org/en/latest/index.html
> > 
> > Feedback is most welcome, including reporting bugs to 
> > https://github.com/aroberge/easygui_qt/issues
> > 
> > Happy 2015 everyone,
> > 
> > André Roberge
> 
> Very nice, thanks.
> 
> One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.

Would today's date be represented as the string "09.01.2015" useful to you? (I found out how to do this.)  If so, I could perhaps add an argument like numeric_format = True.

André

[toc] | [prev] | [next] | [standalone]

#83495

On Sat, Jan 10, 2015 at 2:02 AM, André Roberge <andre.roberge@gmail.com> wrote:
> On Friday, 9 January 2015 19:09:15 UTC-4, stephen...@gmail.com  wrote:
>> One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.
>
> Would today's date be represented as the string "09.01.2015" useful to you? (I found out how to do this.)  If so, I could perhaps add an argument like numeric_format = True.

The correct way to handle this is to use cal.date.toPyDate(), which
helpfully returns a datetime.date object — and make this the default
output of the calendar function, because that’s the only useful output
for anyone asking for a date.

>>> date
'Sat Jan 10 2015'
>>> cal.date
PyQt4.QtCore.QDate(2015, 1, 10)
>>> cal.date.toPyDate()
datetime.date(2015, 1, 10)

-- 
Chris Warrick <https://chriswarrick.com/>
PGP: 5EAAEA16

[toc] | [prev] | [next] | [standalone]

#83686

I found a solution that I'm happy with.

from datetime import datetime
from easygui_qt import *

datestring = get_date()
mydate = datetime.strptime(datestring, '%b %d %Y')

On Saturday, January 10, 2015 at 1:02:30 AM UTC, André Roberge wrote:
> On Friday, 9 January 2015 19:09:15 UTC-4, stephen...@gmail.com  wrote:
> > On Wednesday, December 31, 2014 at 4:24:50 PM UTC-6, André Roberge wrote:
> > > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> > > 
> > > Like the original EasyGUI (which used Tkinter), 
> > > EasyGUI_Qt seeks to provide simple GUI widgets
> > > that can be called in a procedural program. 
> > > 
> > > EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> > > 
> > > The archetype is get_string(message)
> > > which pops a box whose purpose is exactly the same as Python's input(prompt),
> > > that is, present the user with a question/prompt, have the user enter an
> > > answer, and return the provided answer as a string.  Thus
> > > easygui_qt.get_string() can be used as a drop-in replacement for
> > > input().
> > > 
> > > Similarly, instead of using a print() function to display a message,
> > > show_message() is used which pops a message window.
> > > 
> > > EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> > > 
> > > More information can be found at 
> > > http://easygui-qt.readthedocs.org/en/latest/index.html
> > > 
> > > Feedback is most welcome, including reporting bugs to 
> > > https://github.com/aroberge/easygui_qt/issues
> > > 
> > > Happy 2015 everyone,
> > > 
> > > André Roberge
> > 
> > Very nice, thanks.
> > 
> > One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.
> 
> Would today's date be represented as the string "09.01.2015" useful to you? (I found out how to do this.)  If so, I could perhaps add an argument like numeric_format = True.
> 
> André

[toc] | [prev] | [next] | [standalone]

#83723

On Tuesday, 13 January 2015 08:23:30 UTC-4, stephen...@gmail.com  wrote:
> I found a solution that I'm happy with.
> 
> from datetime import datetime
> from easygui_qt import *
> 
> datestring = get_date()
> mydate = datetime.strptime(datestring, '%b %d %Y')

I'm thinking of having the new version return a datetime object automatically.

André

> 
> On Saturday, January 10, 2015 at 1:02:30 AM UTC, André Roberge wrote:
> > On Friday, 9 January 2015 19:09:15 UTC-4, stephen...@gmail.com  wrote:
> > > On Wednesday, December 31, 2014 at 4:24:50 PM UTC-6, André Roberge wrote:
> > > > EasyGUI_Qt version 0.9 has been released.  This is the first announcement about EasyGUI_Qt on this list.
> > > > 
> > > > Like the original EasyGUI (which used Tkinter), 
> > > > EasyGUI_Qt seeks to provide simple GUI widgets
> > > > that can be called in a procedural program. 
> > > > 
> > > > EasyGUI_Qt is NOT event-driven: all GUI interactions are invoked by simple function calls.
> > > > 
> > > > The archetype is get_string(message)
> > > > which pops a box whose purpose is exactly the same as Python's input(prompt),
> > > > that is, present the user with a question/prompt, have the user enter an
> > > > answer, and return the provided answer as a string.  Thus
> > > > easygui_qt.get_string() can be used as a drop-in replacement for
> > > > input().
> > > > 
> > > > Similarly, instead of using a print() function to display a message,
> > > > show_message() is used which pops a message window.
> > > > 
> > > > EasyGUI_Qt requires PyQt4 and is really targeted for Python 3.3+ - although it can work (possibly with some unicode problems ...) using Python 2.7.
> > > > 
> > > > More information can be found at 
> > > > http://easygui-qt.readthedocs.org/en/latest/index.html
> > > > 
> > > > Feedback is most welcome, including reporting bugs to 
> > > > https://github.com/aroberge/easygui_qt/issues
> > > > 
> > > > Happy 2015 everyone,
> > > > 
> > > > André Roberge
> > > 
> > > Very nice, thanks.
> > > 
> > > One issue is the format returned for the calendar selection. For today, the string returned is "Fri Jan 9 2015". My script needs to convert the date to a datetime.date, and having the month returned as a string instead of an integer makes this harder.
> > 
> > Would today's date be represented as the string "09.01.2015" useful to you? (I found out how to do this.)  If so, I could perhaps add an argument like numeric_format = True.
> > 
> > André

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.python

csiph-web