boa-constructor-users

[Boa Constr] Latest CVS Boa and Linux.

[Michal K. <mi...@fr...>]

Hi, Boa fans,

   currently I have big troubles with running CVS Boa on Linux
(Python 2.2.2, wxWindows 2.3.3.1). After splash screen and 
importing lot of things:

...
importing Explorers.DAVExplorer
importing Explorers.SSHExplorer
attaching wxPython doc strings
showing main frames 

there is a momentary flash of some windows and Boa dies with:

Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 12256 error_code 3 request_code 2 minor_code 0
Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 12257 error_code 3 request_code 2 minor_code 0

  Last time I run Boa successfully it was with old 0.1.alpha and older wxWindows, but I want to see
the new improvements :-)  There is something weird, maybe, on our server, but I cannot figure what...

  Someone have seen something similar? What may be the case of troubles? 


                                                       Mike.





  

                             

Re[2]: [Boa Constr] Db>

[Paolo I. <pao...@dm...>]

Hello Riaan,

Thursday, December 12, 2002, 2:20:43 AM, you wrote:

RB> Basically no, as you might guess it's eval'ed on the DebuggerServer side
RB> so statements aren't allowed, only expressions.

RB> I'd like to improve this at at some stage. It's a todo.

Thanks for the reply! Tomorrow morning I've given a **fast** look to
IsolatedDebugger...

What's the problem with that diff? It seems quite painless at a first
look...

Index: IsolatedDebugger.py
===================================================================
RCS file: /cvsroot/boa-constructor/boa/Debugger/IsolatedDebugger.py,v
retrieving revision 1.22
diff -u -r1.22 IsolatedDebugger.py
--- IsolatedDebugger.py 26 Apr 2002 16:11:26 -0000      1.22
+++ IsolatedDebugger.py 12 Dec 2002 11:06:16 -0000
@@ -1090,7 +1090,11 @@
         else:
             try:
                 globalsDict, localsDict = self.getFrameNamespaces(frame)
-                v = eval(expr, globalsDict, localsDict)
+                if expr.startswith("!"):
+                    exec expr[1:] in globalsDict, localsDict
+                    v="Exec Done!"
+                else:
+                    v = eval(expr, globalsDict, localsDict)
                 return pprint.pformat(v)
             except:
                 t, v = sys.exc_info()[:2]

-- 
Best regards,
 Paolo                            mailto:pao...@dm...

[Boa Constr] wxGrid problem

[Marius T. <ma...@it...>]

Hi!

I am using Boa to develop a medical management GUI and it's a great 
tool, big thanks Riaan and all other guys that developed it! I am hoping 
for a beta version:)

Just to share experience, I am using sizers to encapsulate controls. As 
I understand there is no plan to add sizers to Boa, but I could add all 
controls to sizers in a separate method which I call on 
 wxFrame.__init__  right after _init_ctrls(). There is no conflict with 
the code generated by Boa.

I am running Boa 0.1.4 on both Linux and Windows. There is a misterious 
problem with wxGrid on Linux/Mandrake. After adding a wxGrid on a panel, 
closing the Designer and opening it again, the wxGrid object cannot be 
selected any more. On Windows there is no problem selecting it again.

Thanks,

-- 
Marius Trestioreanu
ITCNETWORKS SRL
Phone:(401)2036640; ESN: 6-786-6640; Fax:(401)2036666

[Boa Constr] Re: RFE

[Yuppie <yu...@ze...>]

Riaan Booysen wrote:
> Updated. (And fixed another SSHExplorer bug ;)

???
Couldn't find any updates. Not of
<http://boa-constructor.sourceforge.net/Download.html>
and not of SSHExplorer :-(

Cheers,

Yuppie

[Boa Constr] Re: Zope Support

[Yuppie <yu...@ze...>]

Hi Riaan!


Riaan Booysen wrote:
> From my investigations into this it looks like CMF objects can be wrapped 
> just like all the other Zope objects currently supported.

There's on thing that could cause trouble:
Some meta types (e.g. 'Document') have a different text format ('html', 
'structured-text' or 'plain') depending on their text_format attribute. 
How would I implement different editing views for one Node class 
depending on an attribute? Or how would I get different Node classes for 
instances of one meta type?

>>The Zope plug-ins are very different to the other plug-ins. Looks like a 
>>unified plug-in interface would be very helpful for updating the 
>>ZopeExplorer to Zope 2.6 or writing a CMF plug-in.
> 
> 
> No. Those comments aren't that accurate anymore.
> It has already been unified in the sense that 
> Editor.openOrGotoModule('zope://Connection/<meta>/path/obj')
> works correctly and that Zope items can be bookmarked.

One thing that confused me was this:

Views are defined
- for Zope in the node as defaultViews / additionalViews
- for the rest in the controller as DefaultViews / AdditionalViews

> Nevermind the differences between Zope transports and the simple
> transports, just use the current Zope support as examples,
> they all follow basically the same model.

Maybe you could give me some hints. I quote ZopePTHTMLView because I 
have some questions about it.

class ZopePTHTMLView(ZopeViews.ZopeHTMLView):
     viewName = 'Source.html'
     def generatePage(self):
         props = self.model.zopeObj.properties
         url = 'http://%s:%s@%s:%d/%s/source.html'%(props['username'],
               props['passwd'], props['host'], props['httpport'],
               self.model.zopeObj.whole_name())
         import urllib
         f = urllib.urlopen(url)
         return f.read()

Q1) zopeObj doesn't work. Should be 'self.model.transport'. Right?

Q2) generatePage() is used by additional read only views. For editable 
data I have to use load() / save(). Right?

Q3) urllib.urlopen() is a workaround. I should better use getResource() 
if possible. Right?

> Please go ahead and implement CMF support! 
> Even just a (working!) prototype would be great.
> 
> If I ever refactor the Zope support further, I promise to also update 
> the CMF support if its there ;)

Thanks. I'll see what I can do.


Cheers,

Yuppie

RE: [Boa Constr] Db>

[Riaan B. <ri...@tb...>]

Hi Paolo,

> 
> Hello boa-constructor-users,
> 
> Maybe it's a stupid question... I'm missing something...
> 
> How to change a local variable value from the shell while debugging
> (aka Db> prompt)?
> 
> In the standard debugger, pdb, casted with pdb.set_trace(), I use the
> !, like !var1=1... with boa I've a Syntax Error...
> 
> Db> debug=1
> 
>   File "<string>", line 1
>     debug=1
>          ^
> SyntaxError: invalid syntax
> 
> Db> !debug=1
> 
>   File "<string>", line 1
>     !debug=1
>     ^
> SyntaxError: invalid syntax
> 
> When I can I use some function (like setattr) or work in the __dict__,
> but I wonder if where is some other easy way...

I've done that too :)

Basically no, as you might guess it's eval'ed on the DebuggerServer side
so statements aren't allowed, only expressions.

I'd like to improve this at at some stage. It's a todo.

Cheers,
Riaan.

RE: [Boa Constr] Zope Support

[Riaan B. <ri...@tb...>]

Hi Yuppie,

> 
> Hi!
> 
> 
> Is anybody currently working on the Zope Support? 
I do now and again when time permits.

> Did anybody try to write a CMF plug-in?

I have not used CMF in a project, so learning the whole framework 
plus wrapping the whole CMF framework will take too much time.

It's definitely one of those things I want but just don't have time for :(

From my investigations into this it looks like CMF objects can be wrapped 
just like all the other Zope objects currently supported.
 
> Does it make sense to write a CMF plug-in right now? I had a look at the 
> code and found todo comments like that in Editor.py:
> 
>      # XXX Unify with the rest of the explorers
>      def openOrGotoZopeDocument(self, zopeObj):
> 
>      # XXX Unify with the rest of the explorers
>      def openZopeDocument(self, zopeObj, wholename):
> 
> The Zope plug-ins are very different to the other plug-ins. Looks like a 
> unified plug-in interface would be very helpful for updating the 
> ZopeExplorer to Zope 2.6 or writing a CMF plug-in.

No. Those comments aren't that accurate anymore.
It has already been unified in the sense that 
Editor.openOrGotoModule('zope://Connection/<meta>/path/obj')
works correctly and that Zope items can be bookmarked.

Zope support as a transport plug-in will probably always remain 
different than other transports (e.g. ftp, ssh, etc) in the sense that 
different Zope uris can return different types of zope transports
while other transports only return a single type.

Nevermind the differences between Zope transports and the simple
transports, just use the current Zope support as examples,
they all follow basically the same model.

Please go ahead and implement CMF support! 
Even just a (working!) prototype would be great.

If I ever refactor the Zope support further, I promise to also update 
the CMF support if its there ;)

Cheers,
Riaan.

RE: [Boa Constr] RFE

[Riaan B. <ri...@tb...>]

Hi Yuppie,

> 
> Hi Riaan!
> 
> 
> David LeBlanc wrote:
> > It would also be nice if there was an updated .zip for the poor 
> folks who
> > come along and innocently d/l 0.1.0 and have it crash on them!
> 
> Please update at least this page:
> <http://boa-constructor.sourceforge.net/Download.html>
> 

Updated. (And fixed another SSHExplorer bug ;)

Cheers,
Riaan.

[Boa Constr] Db>

[Paolo I. <pao...@dm...>]

Hello boa-constructor-users,

Maybe it's a stupid question... I'm missing something...

How to change a local variable value from the shell while debugging
(aka Db> prompt)?

In the standard debugger, pdb, casted with pdb.set_trace(), I use the
!, like !var1=1... with boa I've a Syntax Error...

Db> debug=1

  File "<string>", line 1
    debug=1
         ^
SyntaxError: invalid syntax

Db> !debug=1

  File "<string>", line 1
    !debug=1
    ^
SyntaxError: invalid syntax

When I can I use some function (like setattr) or work in the __dict__,
but I wonder if where is some other easy way...

;( Any advice?

-- 
Best regards,
 Paolo                          mailto:pao...@dm...

[Boa Constr] Zope Support

[Yuppie <yu...@ze...>]

Hi!


Is anybody currently working on the Zope Support? Did anybody try to 
write a CMF plug-in?

Does it make sense to write a CMF plug-in right now? I had a look at the 
code and found todo comments like that in Editor.py:

     # XXX Unify with the rest of the explorers
     def openOrGotoZopeDocument(self, zopeObj):

     # XXX Unify with the rest of the explorers
     def openZopeDocument(self, zopeObj, wholename):

The Zope plug-ins are very different to the other plug-ins. Looks like a 
unified plug-in interface would be very helpful for updating the 
ZopeExplorer to Zope 2.6 or writing a CMF plug-in.

I'm afraid the unifying needs a lot of refactoring that only Riaan could 
do. So one question would be:

Is refactoring of ZopeExplorer something scheduled for the next months?

I know that other people like Robert also worked on the Zope Support. 
What are the future plans they have?

I don't want to hurry anybody. Just want to know if it makes sense to 
dig into the old code and write something on my own.


Cheers,

Yuppie

Re: [Boa Constr] RFE

[Yuppie <yu...@ze...>]

Hi Riaan!


David LeBlanc wrote:
> It would also be nice if there was an updated .zip for the poor folks who
> come along and innocently d/l 0.1.0 and have it crash on them!

Please update at least this page:
<http://boa-constructor.sourceforge.net/Download.html>

If you don't want to make release packages, why not guiding people to 
the cvs?

You did a great job improving Boa Constructor, why should people still 
download version 0.1.0?


Cheers,

Yuppie

RE: [Boa Constr] RFE

[Riaan B. <ri...@tb...>]

Hi David,

> I have two requests for feature enhancements:
>
> 1. I would like to have a dialog pop up inviting me to give my own name to
> an app or control when it's created. It's a lot easier to figure
> out what's
> going on if I can call something nameLstBox instead of wxlstbox3 (or
> whatever: not a real world example).

Just making sure, you know about the Name property you should
set in the Inspector? Is this really that bad?

> I would prefer this to renaming the
> control after I have created it! For those who either don't mind
> it or don't
> want it, either a suggested default name could be in the dialog name edit
> control when the dialog control comes up so that the user can just hit
> "enter" or it could be a preferences option. It looks as though
> it would be
> a simple matter of modifying DesignerView.newControl(), at least
> for having
> the dialog all the time. No idea of how to make it a user preference.

As the current practice is the same as Delphi and other GUI builders,
it will stay the default behaviour.
We could have a 'dsPromptForNameAtCreate' preference setting.
But I'm not convinced yet.

> 2. Please, please, PLEASE update the documentation!!!!!

The 0.1.0 docs are accurate for 0.1.0.

For the next release I've already updated some of the application docs.
I haven't touched the tutorial as it needs a thorough rework, a more
maintanable format and more time than I have.

I do intend to put the core Boa docs back into the CVS repository
before the release.

Boa 0.2.0 will be released after the next version (2.3.4) of wxPython.
Hopefully soon!

Cheers,
Riaan.

RE: [Boa Constr] Boa CVS will not run

[Riaan B. <ri...@tb...>]

Hi David,

> Due to bogus lines in Preferences.py @ line 182 and below.

My file is the same as the CVS current and has no problem.

I suspect there was a CVS conflict with your checkout.
"Views->CVS Conflicts" are useful to resolve this (If you have
a running Boa that is ;)

> 
> David LeBlanc
> Seattle, WA USA 

Cheers,
Riaan.

[Boa Constr] RFE

[David L. <wh...@oz...>]

I have two requests for feature enhancements:

1. I would like to have a dialog pop up inviting me to give my own name to
an app or control when it's created. It's a lot easier to figure out what's
going on if I can call something nameLstBox instead of wxlstbox3 (or
whatever: not a real world example). I would prefer this to renaming the
control after I have created it! For those who either don't mind it or don't
want it, either a suggested default name could be in the dialog name edit
control when the dialog control comes up so that the user can just hit
"enter" or it could be a preferences option. It looks as though it would be
a simple matter of modifying DesignerView.newControl(), at least for having
the dialog all the time. No idea of how to make it a user preference.

2. Please, please, PLEASE update the documentation!!!!!

It would also be nice if there was an updated .zip for the poor folks who
come along and innocently d/l 0.1.0 and have it crash on them!

Sincerely,

David LeBlanc
Seattle, WA USA

[Boa Constr] Boa CVS will not run

[David L. <wh...@oz...>]

Due to bogus lines in Preferences.py @ line 182 and below.

David LeBlanc
Seattle, WA USA 

RE: [Boa Constr] boa crashes

[David L. <wh...@oz...>]

You probably downloaded the zip (tar.gz) which is ancient history. You need
to get the latest CVS. However, the tutorial and docs in 0.1.0-alpha are all
there are.

HTH,

David LeBlanc
Seattle, WA USA

> -----Original Message-----
> From: boa...@li...
> [mailto:boa...@li...]On Behalf Of
> D. Rick Anderson
> Sent: Wednesday, December 04, 2002 9:43
> To: boa...@li...
> Subject: [Boa Constr] boa crashes
>
>
> Hi there. I'm trying to find an IDE to build GUI Python apps with and
> BOA looked like it was the right one to use, but I can't get it to run.
> I'm using:
>
> RedHat 8.0
> python 2.2.1-17
> wxPythonGTK-py2.2-2.3.3.1-1
>
> and when I run Boa.py I get:
>
> Starting Boa Constructor v0.1.0-alpha
> importing wxPython
> setting user preferences
> running main...
> Traceback (most recent call last):
>   File "Boa.py", line 495, in ?
>     main()
>   File "Boa.py", line 475, in main
>     app = BoaApp()
>   File "Boa.py", line 310, in __init__
>     wxApp.__init__(self, false)
>   File "/usr/lib/python2.2/site-packages/wxPython/wx.py", line 1705, in
> __init__    _wxStart(self.OnInit)
>   File "Boa.py", line 321, in OnInit
>     abt = About.createSplash(None, modTot, fileTot)
>   File "About.py", line 132, in createSplash
>     return AboutBoxSplash(parent, modTot, fileTot)
>   File "About.py", line 151, in __init__
>     self.html = Utils.wxUrlClickHtmlWindow(self.blackback, -1,
> flags=wxCLIP_CHILDREN)
>   File "/usr/lib/python2.2/site-packages/wxPython/html.py", line 609, in
> __init__
>     self.this = apply(htmlc.new_wxHtmlWindow,_args,_kwargs)
> TypeError: 'flags' is an invalid keyword argument for this function
> Exception exceptions.TypeError: "'NoneType' object is not callable" in
> ignored
>
> help?
>
> TIA
>
> Rick
>
>
>
>

[Boa Constr] boa crashes

[D. R. A. <ru...@co...>]

Hi there. I'm trying to find an IDE to build GUI Python apps with and 
BOA looked like it was the right one to use, but I can't get it to run. 
I'm using:

RedHat 8.0
python 2.2.1-17
wxPythonGTK-py2.2-2.3.3.1-1

and when I run Boa.py I get:

Starting Boa Constructor v0.1.0-alpha
importing wxPython
setting user preferences
running main...
Traceback (most recent call last):
  File "Boa.py", line 495, in ?
    main()
  File "Boa.py", line 475, in main
    app = BoaApp()
  File "Boa.py", line 310, in __init__
    wxApp.__init__(self, false)
  File "/usr/lib/python2.2/site-packages/wxPython/wx.py", line 1705, in 
__init__    _wxStart(self.OnInit)
  File "Boa.py", line 321, in OnInit
    abt = About.createSplash(None, modTot, fileTot)
  File "About.py", line 132, in createSplash
    return AboutBoxSplash(parent, modTot, fileTot)
  File "About.py", line 151, in __init__
    self.html = Utils.wxUrlClickHtmlWindow(self.blackback, -1, 
flags=wxCLIP_CHILDREN)
  File "/usr/lib/python2.2/site-packages/wxPython/html.py", line 609, in 
__init__
    self.this = apply(htmlc.new_wxHtmlWindow,_args,_kwargs)
TypeError: 'flags' is an invalid keyword argument for this function
Exception exceptions.TypeError: "'NoneType' object is not callable" in  
ignored

help?

TIA

Rick

RE: [Boa Constr] Boa: first impressions

[Riaan B. <ri...@tb...>]

Hi Carlos,

>
> Well, I've just downloaded a CVS snapshot of Boa (version 0.1.3,
> I think). I
> would like to contribute with my first impressions. Some personal info
> first... I have a *lot* of experience with Delphi (since the first betas,
> pre-1.0).
>
> - Boa is really nice and well structured. But documentation is lacking; I
> could not access any help information. I assume some doc is already
> available, but I don't know how to download it from CVS.

As Chris said, the docs are part of the 0.1.0 release.

>
> - For people used to popular two-way RAD GUI tools (such as
> Delphi and VB),
> the 'commit'/'cancel' nature of the Frame Designer looks strange
> at first.
> [In Delphi, the source code is automatically updated when you drop a
> component on the designer view]. But it works nicely, and it does not
> seriously affect productivity - it's just a matter of adaptation.
>
> - The Frame Designer has a few problems, though. Some components proved
> difficult to select once put onto the designer., specially static
> text boxes.
> I tried clicking the mouse on some locations, but could not
> select it. Moving
> an edit box (the one called 'wxTextBox') was also difficult, but
> I managed to
> make it.

The Frame Designer is at the mercy of how well controls behave
to the standard mouse click/motion events.

When a control passes the event through to it's parent, Boa also
detects this and selects/moves such children automatically.

Unfortunately some control don't generate these events and don't
pass the unhandled events to their parents, so there is nothing more
I can do.

To select such controls, select them in the Inspector's 'Objs' page.

>
> - I could not select more than one component at a time. Is it a
> 'feature', or
> is it going to be fixed?

Should work the same as in Delphi, hold down shift and click on the
controls. Like in Delphi, only controls on the same containment level
can be multi selected.

> - Changing the structure of the form also proved to be a little
> bit difficult.
> For example, I would like to put some components that were
> designed into the
> form inside a panel (I forgot to add the panel first :-) I know how to
> convince Delphi to let me do just that; not only cut & paste
> works fine in
> Delphi for multiple component selection, you can easily edit the form
> description, which sometimes is better than the visual form
> designer for some
> changes.

Should be a breeze with multi-select.

> - I took a look at the code generated by Boa. I guess that the code was
> intended for processing by Boa alone, but it would not hurt if
> the code was
> formatted a little bit better. Breaking the long lines would help
> a lot for
> us to read and understand what's going on.

It's on the todo list.

> - Probably, my main gripe is with the lack of online
> documentation for the
> wxWindows library. I have heard how good wxWindows is, but a better
> documentation is really needed. I sincerely don't know where to
> start, and
> please bear in mind that I'm no novice in this stuff.

Same as the Boa core docs, it's part of the 0.1.0 download.

> - Last but not least, I could not debug my first app and I have
> no idea why. I
> just clicked on the 'debug app' button, the mouse cursor went
> clocking, and
> Boa just froze - no redraws, no response to any command. Had to
> kill -9 it.

There is a problem with wxPython 2.3.3's process stream reading.

I think this has already been fixed in the CVS version of wxPython.

>
> - Back to the textual description of the form, as available in
> Delphi... and
> to the code generated by Boa. I think that it would be interesting to
> describe the components using a dictionary, and then feeding this
> dictionary
> to a initialization procedure that would create the window using the
> information. It would make reading/editing the properties of the visual
> components a little bit easier. Form creation could be slowed
> down a little
> bit though. I assume that this topic was already discussed on the list
> before, could someone give me a few pointers?

Sorry code generation was chosen and so it will stay.
Read the Philosophy page in the Boa documentation.

> - Back to the wxWindows documentations issues: one of the main
> problems with
> GUI libraries is that it's not enough to know the library
> functions; one has
> to understand how things do fit together, how do they interact.
> I'll give one
> example.
>
> I know that wxWindows has some layout classes. The application that I am
> designing now calls for relatively complex windows, with panels
> with grids
> and buttons to act on particular records shown on those grids. The basic
> point here is that the window has to be structured the right way.
> In Delphi,
> I developed my own way to make it work - I make extensive use of
> panels as
> containers for rows of buttons, pseudo-title-bars for sections of
> the form,
> etc. The question is, is this the correct technique for wxWindows?

Probably not. I also missed the *simple* panel alignment layout of delphi.

Boa does not support Sizers yet, but it does support Anchors which work
almost like in Delphi.

> Many thanks for the dev guys for Boa - it's already in a pretty
> usable state,
> and it will help me to write my new Python app very, very quickly.

Great!

>
> Carlos Ribeiro
> InfTec

Cheers,
Riaan.

RE: [Boa Constr] cvs version not working:

[Riaan B. <ri...@tb...>]

Hi Chris,

Thanks, this image slipped past me when I did the checkin.

It's now fixed.

> The latest (10.30pm Adelaide, Aust time) cvs version is not happy 
> on Windows Me, python 2.2.2, wxPython 2.3.3.1
>
>
> Error message: Images/Modules/wxFramePanel_s.png not found in image paths
>
> I copied & renamed one of the other png files to wxFramePanel_s.png, 
> and its happy again, so there's either a missing file or ...
>
> Chris.

Cheers,
Riaan.

RE: [Boa Constr] Boa: first impressions, part II

[Riaan B. <ri...@tb...>]

Hi Carlos,

> I forgot to talk about one issue: 
> 
> - I could not change the default directory of Boa to point to my 
> project's 
> directory. It would always offer me the boa directory as a 
> default to save 
> files. It seems a minor problem, but it is one that does cause 
> unnecessary 
> loss of productivity, not to mention that it makes mistakes 
> easier - 'where 
> did I save that file' comes to mind. Am I missing something?

Firstly the recommended practice for this is to add a bookmark
to you project folder. This will then be accessible from the 
Explorer's Bookmarks node.

You may also set the startup current working directory under
Preferences->General->Explorer->exWorkingDirectory

The process' current working directory is available in the 
explorer from the 'os.cwd' node.

> Carlos Ribeiro
> InfTec

Cheers,
Riaan.

[Boa Constr] CVS checked in

[Riaan B. <ri...@tb...>]

Hi everyone,

I recently returned from holiday and then lost the harddrive which
had my mail on it. 
If you are waiting for a reply from me, you should probably resend
the message, sorry.

I've updated the CVS repository with the latest changes.

It was a rather big checkin with the most of changes being
bug fixes, cleanups and refactorings.

Biggest visible changes:
* wxFramePanels
  This allows you derive from wxPanel and visually design 
  a container that can be used in frames or dialogs.
  Note that it's a simple implementation with a few limitations.
  For use, see examples/advanced/FramePanels.
* Plug-in management in the Explorer under Preferences.
* Improved code browsing.
* Pyrex file type support (under Plug-ins).
* more wxPython 2.3.3 updates.

Could anyone on Linux who has CVS access to both wxPython and Boa 
please test the Debugger.

Enjoy!

Riaan.

[Boa Constr] Re : Boa: first impressions, part II

[Krzysztof G. <go...@ch...>]

Sorry, I forgot about one (very good) helpfull source to learn wxPython :

wxPython demo - it's nice couple of examples of using many features of 
wxPython.

You may download it from http://wxpython.org/download.php#sources - 
unpack it and run demo.py


Chris

[Boa Constr] Re : Boa: first impressions

[Krzysztof G. <go...@ch...>]

Hello,

You may try to download docs from boa-constructor-0.1.0-alpha.docs.zip 
and unzip it into boa directory (Python, wxWindows-wxPython docs).
Boa Help and Getting Started You will find in Docs subbdir of 
boa-constructor-0.1.0-alpha.src.zip - simply copy boa dir into Your Boa 
0.1.3a (or 0.1.4) Docs subdir.
It was quite enough for me to start using wxPython and Boa.

Theese Docs are not too up-to-date but they are usefull to learn much, 
more up-to-date sources You may find in www.wxPython.org .
wxPython cookbook is fine, but using Boa and reading wxWindows docs from 
Boa ide is a good method too.

I think that documentation will be updated in the stable version of boa 
- a few weeks (days) after wxWindows 2.4 - I hope :-)

You are right, Boa is great and nice :-)


Cheers,

Chris

[Boa Constr] cvs version not working:

[Chris M. <cj...@av...>]

The latest (10.30pm Adelaide, Aust time) cvs version is not happy on =
Windows Me, python 2.2.2, wxPython 2.3.3.1


Error message: Images/Modules/wxFramePanel_s.png not found in image =
paths

I copied & renamed one of the other png files to wxFramePanel_s.png, and =
its happy again, so there's either a missing file or ...

Chris.

[Boa Constr] Boa: first impressions, part II

[Carlos R. <cri...@ma...>]

I forgot to talk about one issue: 

- I could not change the default directory of Boa to point to my project's 
directory. It would always offer me the boa directory as a default to save 
files. It seems a minor problem, but it is one that does cause unnecessary 
loss of productivity, not to mention that it makes mistakes easier - 'where 
did I save that file' comes to mind. Am I missing something?

Carlos Ribeiro
InfTec