anygui-users — Discussions about how to use the Anygui package

Re: [Anygui-users] Errors in __init__

[Magnus L. H. <ma...@he...>]

N. Wieland <nic...@ya...>:
>
[snip]
> Thank you very much, it works !
> I've also discovered that this version of anygui (2.0) use Tkinter
> instead of Gtk by default when the version 1.1 use Gtk (on my computer
> of course).
> I know of the wishlist thing, but maybe you want to know of this
> behaviour... 

The version in CVS isn't even at alpha level yet, so you shouldn't
count on it functioning like the final release will. The reason you
don't get GTK at the moment is that the GTK back-end currently doesn't
work (for 0.2).

> Regards,
> 	Nicholas
> 
> P.S. I've noticed the cc ... If you want I can send my questions to
> the devel ml.

Not necessary. I just cc to keep the people there updated :)

-- 
Magnus Lie Hetland        Practical Python          The Anygui Project
http://hetland.org        http://ppython.com        http://anygui.org

Re: [Anygui-users] Errors in __init__

[N. W. <nic...@ya...>]

- ma...@he... :
> > File "/usr/lib/python2.2/site-packages/anygui/__init__.py", line 9,
> > in application raise RuntimeError, 'no application exists'
> > RuntimeError: no application exists   
> 
> This error is the problem. With the current CVS version you can't
> create Windows unless there is an Application object in existence. Try
> to move
> 
>  app = Application()
> 
> to the top of your code and see if that helps.

Thank you very much, it works !
I've also discovered that this version of anygui (2.0) use Tkinter
instead of Gtk by default when the version 1.1 use Gtk (on my computer
of course).
I know of the wishlist thing, but maybe you want to know of this
behaviour... 

Regards,
	Nicholas

P.S. I've noticed the cc ... If you want I can send my questions to the
devel ml.
-- 
         (__)	      | Nicholas Wieland	    |    -     ------------
	 (oo)	      | nic...@ya...   |    -    | There's no |
   /------\/ 	      | Debian GNU/Linux / Mac OS X |    -    | place like |
  / |    ||  	       -----------------------------     -    | *GNOME(2)* |
 *  /\---/\           ...."Have you mooed today?"....    -     ------------

Re: [Anygui-users] Errors in __init__

[Magnus L. H. <ma...@he...>]

N. Wieland <nic...@ya...>:
>
> I'm using anygui from CVS on Debian SID and Gnome 2.
> Here's the simple code I've tried:
> 
> ****
> 
> from anygui import *
> 
> win = Window(title = "anyGUI !",
> 	     size = (600, 400))
> 
> editor = TextArea(size = (600, 400))
> 
> win.add(editor)
> 
> app = Application()
> app.add(win)
> app.run()
> 
> ****
> 
> File "/usr/lib/python2.2/site-packages/anygui/__init__.py", line 9,
> in application raise RuntimeError, 'no application exists'
> RuntimeError: no application exists   

This error is the problem. With the current CVS version you can't
create Windows unless there is an Application object in existence. Try
to move

 app = Application()

to the top of your code and see if that helps.

> I've tried also import anygui as gui.
> I'm just not skilled enought to understand my error, I need a hand...
> Ah, with anygui 1.1 it works !
> 
> Thanks in advance,
> Cheers,

-- 
Magnus Lie Hetland        Practical Python          The Anygui Project
http://hetland.org        http://ppython.com        http://anygui.org

[Anygui-users] Errors in __init__

[N. W. <nic...@ya...>]

I'm using anygui from CVS on Debian SID and Gnome 2.
Here's the simple code I've tried:

****

from anygui import *

win = Window(title = "anyGUI !",
	     size = (600, 400))

editor = TextArea(size = (600, 400))

win.add(editor)

app = Application()
app.add(win)
app.run()

****

Traceback (most recent call last):
File "any.py", line 4, in ? size = (600, 400))
File "/usr/lib/python2.2/site-packages/anygui/Windows.py", line	8, in __init__
Frame.__init__(self, *args, **kw)
File "/usr/lib/python2.2/site-packages/anygui/Frames.py", line 14, in __init__
Component.__init__(self, *args, **kw)
File "/usr/lib/python2.2/site-packages/anygui/Components.py", line 30, in __init__
Proxy.__init__(self, *args, **kw)
File "/usr/lib/python2.2/site-packages/anygui/Proxies.py", line 15, in __init__
self.rawDictSet('wrapper',self.wrapperFactory())
File "/usr/lib/python2.2/site-packages/anygui/Windows.py", line 12, in wrapperFactory
return backendModule().WindowWrapper(self)
File "/usr/lib/python2.2/site-packages/anygui/backends/tkgui.py", line 589, in __init__
ComponentWrapper.__init__(self, proxy)
File "/usr/lib/python2.2/site-packages/anygui/backends/tkgui.py", line 50, in __init__
AbstractWrapper.__init__(self, *args, **kwds)
File "/usr/lib/python2.2/site-packages/anygui/Wrappers.py", line 84, in __init__
application().manage(self)
File "/usr/lib/python2.2/site-packages/anygui/__init__.py", line 9, in application raise RuntimeError, 'no application exists'
RuntimeError: no application exists   

****

I've tried also import anygui as gui.
I'm just not skilled enought to understand my error, I need a hand...
Ah, with anygui 1.1 it works !

Thanks in advance,
Cheers,
-- 
         (__)	      | Nicholas Wieland	    |    -     ------------
	 (oo)	      | nic...@ya...   |    -    | There's no |
   /------\/ 	      | Debian GNU/Linux / Mac OS X |    -    | place like |
  / |    ||  	       -----------------------------     -    | *GNOME(2)* |
 *  /\---/\           ...."Have you mooed today?"....    -     ------------

Re: [Anygui-users] anygui installation

[Magnus L. H. <ma...@he...>]

Jim Beckstrom <jrb...@vo...>:
>
> 
>         I downloaded v 0.1.1, to install on SuSE 7.2, Python 2.0. and
> put it in the same directory as qt.py(o),
>         /usr/lib/python2.0/site-packages
>         Following the tar command, when I run python setup.py install, I
> get:
> 
>             error in setup script: invalid distribution option
> 'platforms'
[snip]

It seems maybe you have an old version of distutils. Also, Anygui
requires Python 2.1 (see FAQ). Hopefully upgrading will fix the
problem. Not sure what else might be wrong.

-- 
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] anygui installation

[Jim B. <jrb...@vo...>]

        I downloaded v 0.1.1, to install on SuSE 7.2, Python 2.0. and
put it in the same directory as qt.py(o),
        /usr/lib/python2.0/site-packages
        Following the tar command, when I run python setup.py install, I
get:

            error in setup script: invalid distribution option
'platforms'

        I still got directories anygui-0.1.1/lib/anygui, so I tried the
export PYTHONPATH=$PYTHONPATH:<directory path, both ../lib and
../lib/anygui>,
then running python to test its availability, the "from anygui import *"
results in:
            ImportError: No module named anygui.

        What am I missing?

Thanks,

Jim Beckstrom
Ann Arbor, Mich.

[Anygui-users] What happens when I freeze my app?

[Stephane J. <ak...@vi...>]

after reading the anygui snippet in the python cookbook I thought that
anygui could be for me, yet one question linguers : what happens if I make
an app, then use freeze to distribute it? clients that have a python
installation should not have to much trouble but, the ones that don't? and
if I like the look and feel on say wx and QT can I limit it to those two?

stephane

Re: [Anygui-users] Re: [Anygui-devel] Component names

[Magnus L. H. <ma...@he...>]

terry <tg...@ci...>:
>
> 
> FWIW - M$ uses TreeView.  That at least adds some length and 
> description to a tree standing alone....

Hm. That's a possibility. After all, with "Tree" I associate the
abstract structure itself -- while TreeView could be a "physical" GUI
component.

One drawback is that it alludes to the "view" part of the
"model-view-controller" triple, while it would actually be a
controller as well.

Hm. We've got ListBox -- how about TreeBox? Unconventional name, I
guess...

> terry 

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] Re: [Anygui-devel] Component names

[terry <tg...@ci...>]

FWIW - M$ uses TreeView.  That at least adds some length and 
description to a tree standing alone....

terry 

[Anygui-users] Release schedule

[Magnus L. H. <ma...@he...>]

Since the pace of the development in the last few months haven't been
quite as frenetic as it was before christmas, there was no release in
April, as originally planned. There may be an alpha out in May (but
don't hold your breath ;).

I've updated the schedule on the website which now says that release
0.2 will be during the early summer of 2002, and release 0.3 will be
during late summer. I think we should be able to do that -- the 0.2
architecture is starting to work properly now, after all.

So, please be patient -- it will hopefully be worth it.

And, by the way: The current CVS release isn't very usable, but that
was planned from the beginning (i.e. a major rewrite between 0.1 and
0.2). For future releases, I'll try to ensure that there is a stable
branch with a functioning version of the package.

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

Re: [Anygui-users] Modal Windows

[Magnus L. H. <ma...@he...>]

terry <tg...@ci...>:
>
> 
> Hello,
> 
> In the type of business applications I usually develop, I have 
> need to open an application (not a standard dialog type) window 
> which the user must deal with before continuing with the main 
> window.  I'm used to dealing with this in VB/Access by simply 
> stating that the second window is modal and the first window 
> becomes 'dead' to the user.
> 
> I've been playing around with AnyGUI using threads and forking, 
> but have not come across any mechanism to accomplish this other 
> than to disable all of the controls on the first window.  I've 
> also noticed that many of the X programs I use don't seem to 
> implement this concept even when I think it might be a reasonable 
> approach to control the application.
> 
> How should (will) I handle this using AnyGUI?
 
I hadn't thought about implementing this, but it seems it might be
useful. It may be that it would require some serious hacking in some
of the backends (if they don't support this sort of thing)...

Anyway, if we do implement it, I think perhaps using the "enabled"
attribute of the given window might be a natural way of doing it. I.e.

  new_win = Window(title='dialogish window thingy')
  old_win.enabled = 0
  app.add(new_win)

And then set old_win.enabled = 1 in the code dealing with the new
window. (Of course some utility class or something could be created to
deal with the normal case of "modal windows" here, perhaps.)

I can't guarantee that this will be done in release 0.2, though (and
maybe not even 0.3) since I haven't looked into how hard it would be
to implement in the various backends.

What you could do while working with 0.1 (which doesn't have anything
like this) is to create some central mechanism for all your event
handlers (i.e. an instance with lots of event-handling methods). This
mechanism could then be told which windows were allowed to perform
actions and which weren't -- or something. (Not ideal, certainly...)

Anyway, I'll add this to the TODO list :)

> Thanks,
> 
> terry 

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] Modal Windows

[terry <tg...@ci...>]

Hello,

In the type of business applications I usually develop, I have 
need to open an application (not a standard dialog type) window 
which the user must deal with before continuing with the main 
window.  I'm used to dealing with this in VB/Access by simply 
stating that the second window is modal and the first window 
becomes 'dead' to the user.

I've been playing around with AnyGUI using threads and forking, 
but have not come across any mechanism to accomplish this other 
than to disable all of the controls on the first window.  I've 
also noticed that many of the X programs I use don't seem to 
implement this concept even when I think it might be a reasonable 
approach to control the application.

How should (will) I handle this using AnyGUI?

Thanks,

terry 

[Anygui-users] Windows installer and RPMs

[Magnus L. H. <ma...@he...>]

I've added a binary installer and two RPMs to release 0.1.1. I guess
it wasn't really necessary to include both a noarch rpm and a src rpm,
but what the heck... ;)

I have tested the binary installer, but not the rpms. Please report
any problems you might have with them.

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] (no subject)

[Alejandro <ale...@gm...>]

Re: [Anygui-users] Re: Anygui-users digest, Vol 1 #13 - 1 msg

[Magnus L. H. <ma...@he...>]

Aljosa Mohorovic <ma...@ya...>:
>
> i use linux, python 2.2, anygui 0.1.1., gtk backend i need to set
> handler for button named "btn_quit" to close current window/app/?
> i do "link(btn_quit, quit_anyapp)". i don't know what to write for
> "def quit_anyapp" to close this app. how do i do this, what is to be
> written?

Ah. I see. I'm not sure how well this is supported at the moment,
actually... But try to use the destroy() method of the window. That
will close and deallocate the window (and remove it from the
application).

Actually, app.remove(win) ought to work as well (and is perhaps a more
natural reverse of the app.add(win)).

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] Re: Anygui-users digest, Vol 1 #13 - 1 msg

[Aljosa M. <ma...@ya...>]

i use linux, python 2.2, anygui 0.1.1., gtk backend i need to set
handler for button named "btn_quit" to close current window/app/?
i do "link(btn_quit, quit_anyapp)". i don't know what to write for
"def quit_anyapp" to close this app. how do i do this, what is to be
written?

> Date: Mon, 18 Feb 2002 00:13:31 +0100
> From: Magnus Lie Hetland <ma...@he...>
> To: any...@li...
> Subject: Re: [Anygui-users] app.run - how to end it?
> 
> Aljosa Mohorovic <ma...@ya...>:
> >
> > when i do all the stuff from tutorial it works, but how can i kill my
> > anygui app?
> 
> It should just be a matter of closing all the windows (in version 0.1,
> at least -- this may change in 0.2).
> 
> Which operating system are you running, and which backend are you
> using? (The backend can be found by adding "print backend()" to your
> program.)

Re: [Anygui-users] app.run - how to end it?

[Magnus L. H. <ma...@he...>]

Aljosa Mohorovic <ma...@ya...>:
>
> when i do all the stuff from tutorial it works, but how can i kill my
> anygui app?

It should just be a matter of closing all the windows (in version 0.1,
at least -- this may change in 0.2).

Which operating system are you running, and which backend are you
using? (The backend can be found by adding "print backend()" to your
program.)

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

[Anygui-users] app.run - how to end it?

[Aljosa M. <ma...@ya...>]

when i do all the stuff from tutorial it works, but how can i kill my
anygui app?

[Anygui-users] =?euc-kr?B?KluxpCCw7V0qILOqtMIgwd+xub+hvK0gucy3obimIMHYuvHH0bTZLiA=?=

[<ite...@fr...>]

ICAKWyDBpjKx4iDB37G5IMf2wfYgwd+xub7uICYgSVQgtb+9wyCxs8CwsPrBpCC/rLz2u/0gvLG5
3yBdIAoKwd+xuSC/5LPnvLogwaS6ziDIxL/4wLi3ziDHwbfQxry+7r3DvbrF2yjB1im0wiDB37G5
IL3Jvue068fQsbO/zSDH1LKyIMHfsblJVMD8ua6woSCw+sGkwLsguPDB/cfVtM+02S4gCiAKu+fB
+MDat+EssPy3w7Hiu+cgudcgwNq8vMfRIMDat+G0wiBodHRwOi8vd3d3LmZyb250aWVyLmNvLmty
IMC7IML8sO3Hz73KvcO/wC4KIAoKuPDB/cDOv/ggCgk4MLjtICgyMLjtwMwgMbCzud3AuLfOveEg
NLCzud0gvLHC+Lz4ILjwwf0pICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAq/rLz2
seKwoyAKCTaws7/5ICgyMDAys+IgMr/5IDI4wM+6zsXNIDIwMDKz4iA4v/kgMjnAz7HuwfYpIAoK
v6y89rD6uPEgCgnB37G5vu4sIMHfsbm+7iDIuMitLCDB37G5x9AsIMTEx7vFzSCx4sPKLCBKYXZh
IMfBt86x17ehudYgIAoKv6y89rO7v+sgCqGhCTIwMDIuIDIuIDI4fjIwMDIuIDguIDI5IC0gwd+x
ub7uILHiw8p+wd+x3rD6waQgCgkJCQktIL3Hv+sgx6XB2MHfsbm+7iwgyLjIrSwgua65/SwgwNu5
riAKCQkJCS0gSFNLvcPH6Cjx6c/Q+dPl3uKp+MHNxePLKSAxwM8gNL3DsKMgKL/AwPwpIAoKCTIw
MDIuIDIuIDI4fjIwMDIuIDUuIDMwIC0gwd+xucfQILCtwMcov6q75ywgwfa4riwgsObBpiwgua7I
rSwguf23/CwgsbPAsLXuKSAKCQkJCS0gvcm+57Trx9CxsyDD38O1ILTrx9C7/bD6IEZyZWUgVGFs
a2luZyAxwM8gMr3DsKMgKL/AyMQpIAoKCTIwMDIuIDUuIDMxfjIwMDIuIDguIDMwIC0gxMTHu8XN
ILHiw8qxs8CwICjB37G5IMTEx7vFzSDIr7DmvPfB9ikgCgkJCQktIEpBVkEgUHJvZ3JhbW1pbmcg
KFNDSlCw+sGkKSAxwM8gMr3DsKMgKL/AyMQpIAoKoaEJMjAwMi4gNyAtIMHfsbm5rsitIMCvwPvB
9iDFvbnmICg0udo1wM8pILnos7a/qcfgKLGzxessILz3vcTBprD4KSAKIAq/rLz2sd2+1yAKCTQy
MLi4v/ggKL3EuvEsILHivPe757rxLCC68cfgseLHpSAsILrxwNosIL3Fw7ywy7vnLCCw+MfXwMy/
67fhLCBIU0vAwL3Dt+EsIMHfsbm5rsitIMW9uea/qcfgILDmuvEgwM/DvCDG98fULgoJurvAzsDM
ILrxwNosIL3Fw7ywy7vnvK24piDB2Lrxx9IgsOa/7L+htMIgMTW4uL/4wLsgwabHz7+pILXluLO0
z7TZLikgIAoKwabD4rytt/kgCgm/qbHHKLrxwNq537HevcMgx8q/5CksIMHWuc617rfPte66uyAz
xessIL+psce758H4IDXA5SAKCr+svPa9xcO7ILnXIL+svPa68SCzs7rOIAoJMjAwMrPiIDG/+SAz
wM+6zsXNIDIwMDKz4iAyv/kgMjDAz7HuwfYgPLDowcK5+MijIDogx9G6+8C6x+AgMTY5LTE0ODQy
OS0xMy0xMDEgv7mx3cHWOiDHwbfQxry+7r3DvbrF26LfPiAKCrHixbggCgktILnmsPrIxCC9yb7n
tOvH0LGzIMfQu/2w+iAywM4xwbYgtOvIrbimIMXrx9EgvcfB+sD7ILGzwLCx4si4IMGmsPgovcm+
57Trx9Agw/i/obytIMPfw7XH0SC538C9wMwgwaTIrsfPsO0gx6XB2L7uuKYgsbi758fPtMIgvcm+
57TrIMfQu/2w+iDH1LKyILvsvsbA1rTCIMf2wfYgwd+xub7uILnXIMHfsbkgua7IrbimIL3AtebH
0iC89iDA1rTCIMHBwLogseLIuMDUtM+02S4pCgktIMD8v/ggseK897vnv6G8rSC8973EICgyMDAx
s+IxMb/5v6Egwdiw+MfRIMPWvcW9xCC+xsbExq7H/MC4t84gMsDOMb3HKSAKCS0gNrCzv/kgv6y8
9iDIxCC9yb7ntOvH0LGzv6G8rSC89rfhwfUgud+x3goJLSDB37G5ua7IrSDAr8D7wfYgxb255iA0
udo1wM8gv6nH4CDBprD4CgktIEhTSyC9w8foKPHpz9D50+Xe4qn4wc3F48spIMHfsbnH9sH2v6G8
rSDAwL3DCgktIEphdmEgx8G3zrHXt6Ugv6y89iDIxCBTdW4gQ2VydGlmaWVkIEphdmEgUHJvZ3Jh
bW1lciDA2rDdvcPH6MDAvcOwobTJIAoJLSC/rLi7v6y9wyC/rMjeILD8sOi3ziC68cDaILnfsd4g
te6/oSC4uMD8wLsgseLHz7HiIMCnx9ggyPG4wcDatMIgucy4riC9xcO7x8+/qSDB1r3DseIgudm2
+LTPtNkuIAoJLSC68cDaILnfsd4sIL3Fw7ywy7vnIMD9wvcgtOvH4MfULiAKCS0gsbPAsCC89rfh
yMQgtOux4r73LMHfvNKx4r73ILnXILqlw7Ox4r73IMHfsbkgtOO058Dat84gw+u+9yDD38O1IAoK
wda/5LGzwLC067vzIAoJLSDB37G5wK/H0MC7IMHYuvHHz7TCILz2x+i7/SAowd+xub7uIMPKurjA
2iCwobTJKSAKCS0gwd+xub7uIL7ux9C/rLz2IMjxuMEgtOvH0Lv9IAoJLSDB37G5sPy3wyC75773
sOjIucHfwM4gseK+98O8IMDTwfe/+CAgCgrAz8GksOjIuSAKCTIwMDKz4iAyv/kgMjDAzyDBorz2
uLawqCAov6y89rHdLCDB1rnOte63z7XuursgM8XrLCC53bjtx9TGxyC758H4NbjFLCC1tcDlKQoJ
MjAwMrPiIDK/+SAyNcDPILrxwNq537HeLCC9xcO8sMu75yC/z7fhCgkyMDAys+IgMr/5IDI2wM8g
w+KxuSC/ubrxvNLB/SAotOe75yDIuMDHvce/obytIL+psccvuvHA2iC15biyKQoJMjAwMrPiIDK/
+SAyOMDPIDEyOjMwIMDOw7WxucGmsPjH17+hvK0gwd+xuSC9yb7nwLi3ziDD4rG5ICjB37G5us+5
5sfXsPgpCgkJCTE0OjMwIL3Jvue068fQsbMgseK897vnIMDUvNIgudcgv8C4rr+jxdfAzLzHCgky
MDAys+IgN7/5IMHfsbm5rsitIMCvwPvB9iDFvbnmICg0udo1wM8pCgkyMDAys+IgOL/5IEhTSyC9
w8foKPHpz9D50+Xe4qn4wc3F48spIMDAvcMKCTIwMDKz4iA4v/kyOMDPIMG+sK0gudcgvPa34b3E
CgkyMDAys+IgOL/5MjnAzyDB37G5IL3Jvue/obytIMDOw7WxucGmsPjH18C4t84gsc2xuQogCrmu
wMfDsyAJCgktIMfBt9DGvL7uvcO9usXbKMHWKSC8rb/vvcMgvK3DyrG4ILytw8q1vyAxNTU0LTEg
KLDmwd+69LX5M8P+KSAKCQkowPzIrSA6IDAyLTM0NzMtMzkxMCwgxtG9uiA6IDAyLTM0NzMtMzk5
MCwgyKjG5MDMwfY6IHd3dy5mcm9udGllci5jby5rcikKCS0gwd+xub3Jvue068fQsbMgOiC9yb7n
vcMgtOu1v7G4IL+sx9W3ziA1NMijIL3Jvue068fQsbMgv9y758OzCgkJKMD8yK0gOiAwMjQtODg1
MC02NjA3LCDG0b26IDogMDI0LTg4NTItMzM2MykgCgktIMHWw9Y6x8G30Ma8vu69w726xdsowdYp
ICDB1rD8OiDB37G5IL3Jvue068fQsbMgICAKCS0gyMS/+Dogwd+xuSDBpLrOseKw/Ci/5LfJvLop
ICjB1inEt8bbvbqz3SB3d3cuY2FtcHVzLmNvLmtyICAKIAogCg==

Re: [Anygui-users] anygui.backend()

[Magnus L. H. <ma...@he...>]

Stephen Boulet <st...@th...>:
>
[...]
> 
> Magnus, but it _does_ seem to work, at least on windows. Each time I try it, 
> I get a different window (the little tk decoration in the window bar, etc.)
 
I see. But if you import a backend, you won't get the functions
defined in the anygui/__init__.py, right? (anygui/backends/__init__.py
doesn't import that stuff.) So to get things working properly, you'd
have to import anygui separately, which will foul up things like
backend()...

Anyway, the import part will probably be rewritten/fixed up quite a
bit in 0.2.

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

Re: [Anygui-users] anygui.backend()

[Stephen B. <st...@th...>]

On Friday 08 February 2002 01:45 am, you wrote:
> Boulet Stephen-CSB046 <Ste...@mo...>:
> > Is the anygui.backend() function supposed to report all available
> > backends or just a default one?
> >
> > I have tk, wx, and msw available, and msw is the only one reported
> > reported (anygui 0.1; python 2.2).
>
> Hi!
>
> The backend function simply tells you which backend is currently in
> use. msw is the default whenever it is available. If you want
> something else, use ANYGUI_WISHLIST.
>
> The way you're doing things in the code example won't really work.

Magnus, but it _does_ seem to work, at least on windows. Each time I try it, 
I get a different window (the little tk decoration in the window bar, etc.)

On linux, I get:

'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "<stdin>", line 8, in ?
ImportError: No module named anygui.backends.tkgui

___________
Stephen      
                   From here to there
                     and there to here,
      funny things are everywhere.  -- Dr Seuss


> Importing the backend directly is necessary to tell wrappers (like
> py2exe) which modules they need to include, but won't override the
> automatic backend selection (unfortunately). To do that, you'll have
> to set ANYGUI_WISHLIST (as an environment variable) to the backend you
> wish to use. This is considered a flaw (noted briefly in KNOWN_BUGS)
> and will be fixed in release 0.2, where you won't need environment
> variables at all.
>
> > Thanks.
> >
> > -- Stephen

[Anygui-users] Re: Import error on widget use - fixed...

[Terry <tg...@ci...>]

> How odd... And you're sure you used 2.1? (That they weren't installed
> in parallell, and the 2.0 version was used instead?)

At this point in my knowledge level I can't be certain, however I got 
thousands of mail messages from a cron type program in which python was 
complaining about a depreciated function.  These went away after I 
reinstalled 2.0 via yast. (I'm using several machines, all SuSE 7.2)

> Have you tried to just start the interactive interpreter (in 2.1) and
> import weakref? It works for me...

Did exactly that.  The version number reported was 2.1.1 just as what I 
installed, but no weakref.  I'll go throught it again to check....

> What do you mean? It will move along, yes -- but that might mean some
> re-work, since the API might change still (as the warning in the
> documentation says)... No extreme changes, but changes nonetheless.
> (Of course we're happy to help you fix things related to these
> changes, though :)

I knew that, I've been lurking on the developer list for a few months.

Thanks,

Terry

[Anygui-users] 0.1.1

[Magnus L. H. <ma...@he...>]

Already a bug has surfaced... In the released version 0.1, the real
backend-list was commented out and a shorter one was used. This was a
remnant from the beta release. It has been fixed, and the correct
version has been released as 0.1.1.

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

Re: [Anygui-users] Re: Import error on widget use - fixed...

[Magnus L. H. <ma...@he...>]

Terry <tg...@ci...>:
>
> 
> 
> > Yep. You don't have the module named weakref, as the error says.
> > You should upgrade to Python 2.1 (as pointed out by the FAQ at
> > anygui.org/faq).
> 
> I first installed Python 2.1.1 from an rpm at Python.org that I had 
> previously downloaded.  Got exactly the same 'weakref' error as with 
> the 2.0 that came with SuSE 7.2.

How odd... And you're sure you used 2.1? (That they weren't installed
in parallell, and the 2.0 version was used instead?)

Have you tried to just start the interactive interpreter (in 2.1) and
import weakref? It works for me...

> Undaunted, I got Python 2.2 and installed it - and the error went
> away. :-)

That's nice :)

> (Using the just released 
> AnyGUI 0.1!)  I don't know why since all the docs say weakref is in 
> 2.1, but maybe the FAQ should read 2.2?
 
Hm. We have (for now) decided to support 2.1, so if that's not working
I'd consider it a problem... On the other hand, only supporting 2.2
would give us lots of neat opportunities in other areas ;)

(Not really an option for a while, though, I think.)

> I'm a newbe to Python (but have been programming since ENIAC II times), 
> so bear with me.  I'm starting a medium sized business app development 
> (Python, Postgres, AnyGUI), and am hoping that AnyGUI will move along 
> enough to keep me from too much re-work.

What do you mean? It will move along, yes -- but that might mean some
re-work, since the API might change still (as the warning in the
documentation says)... No extreme changes, but changes nonetheless.

(Of course we're happy to help you fix things related to these
changes, though :)

> I'll just be building 
> prototype screens for a while, but I will be 'user-developer' testing 
> AnyGUI quite a lot.
 
Very good! We need testers/users to make things more stable.

> I would like to put in a small request for some mega-widgets - Combo 
> Box and Notebook are the most prominent by far as they are heavily used 
> in business apps.  I could deal with only a Tkinter backend for 3-6 
> months....

We'll get combo box and notebook, and mega-widgets. They're in the
TODO file (found in the distribution). But first we need to
re-implement a big chunk of the internals -- adding features before
we've done that will only mean re-adding them afterwards... But by
release 0.2 (and certainly 0.3) Anygui will be much more complete than
it is now. (0.1 is more of a prototype/proof-of-concept.)

> Thanks,
>  
> Terry

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

Re: [Anygui-users] anygui.backend()

[Magnus L. H. <ma...@he...>]

Boulet Stephen-CSB046 <Ste...@mo...>:
>
> Is the anygui.backend() function supposed to report all available backends or just a default one?
> 
> I have tk, wx, and msw available, and msw is the only one reported reported (anygui 0.1; python 2.2).
 
Hi!

The backend function simply tells you which backend is currently in
use. msw is the default whenever it is available. If you want
something else, use ANYGUI_WISHLIST.

The way you're doing things in the code example won't really work.
Importing the backend directly is necessary to tell wrappers (like
py2exe) which modules they need to include, but won't override the
automatic backend selection (unfortunately). To do that, you'll have
to set ANYGUI_WISHLIST (as an environment variable) to the backend you
wish to use. This is considered a flaw (noted briefly in KNOWN_BUGS)
and will be fixed in release 0.2, where you won't need environment
variables at all.

> Thanks.
> 
> -- Stephen

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org