boa-constructor-users

[Boa Constr] Error when bookmarking a package

[Patrick K. O'B. <po...@or...>]

I get an error when I try to bookmark a directory that is also a Python
package.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

[Boa Constr] Re: Boa files modified to support -s command line switch

[Riaan B. <riaan@e.co.za>]

Hi Patrick, the changes are booked into CVS go get them ;)

"Patrick K. O'Brien" wrote:
> 
> Attached are three modified files. (I'm pretty sure I started with the
> latest versions - Boa 0.0.9) The files have been changed to allow the
> command line switch -s to execute the PYTHONSTARTUP (or BOASTARTUP) script
> when Boa starts, just like IDLE. The key thing is that the startup scripts
> need to execute in the shell interpreter's namespace. I borrowed the basic
> technique from IDLE and modified it to fit the coding conventions used in
> Boa.

Thanks for the fix!

> 
> These changes were tested with a good startup script as well as one that had
> an error. Boa loads gracefully in either case and reports the error if there
> is one. I also tried it with the -D filename debugging option and the
> startup stuff was ignored. I'm not sure why. I'll leave it up to Riaan to
> decide if that is appropriate behavior or not. I did NOT test it with the -T
> option.

It now works.

> 
> One difference that I found between my implementation and IDLE's concerns
> print statements within the startup script. In IDLE, print statements in the
> startup script appear in the shell itself, whereas in Boa the same print
> statements appear in the Python console. Again, I'll defer to Riaan on this
> issue.

This was fixed neatly, see the source ;)

> 
> Here is an example of running Boa with the -s switch:
> 
> C:\Python21\python.exe C:\Code\boa\Boa.py -s
> 
> You can also run it from a Windows shortcut or menu (but not from a DOS
> prompt) with just the following:
> 
> C:\Code\boa\Boa.py -s
> 
> If there is a better way to submit patches like this, please let me know. If

The best place would be here (SF submit new patch):
http://sourceforge.net/tracker/?func=add&group_id=1909&atid=301909
and a message to the mailing list with a link of the new patch url.

Direct to me is also fine.

The mailing list is not the ideal place for attaching patches, but 
MUCH better than not sending them at all ;)

> you think my code sucks, let me know that as well. <grin>

Not at all! Although I did change it a little.
Thanks for the patch and the suggestion, I'm using it now too :)
 
> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
>   ------------------------------------------------------------------------
>                        Name: CommandLine.html
>    CommandLine.html    Type: Hypertext Markup Language (text/html)
>                    Encoding: quoted-printable
> 
>                      Name: ShellEditor.py
>    ShellEditor.py    Type: Plain Text (text/plain)
>                  Encoding: quoted-printable
> 
>              Name: Boa.py
>    Boa.py    Type: Plain Text (text/plain)
>          Encoding: quoted-printable

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Boa files modified to support -s command line switch

[Patrick K. O'B. <po...@or...>]

Attached are three modified files. (I'm pretty sure I started with the
latest versions - Boa 0.0.9) The files have been changed to allow the
command line switch -s to execute the PYTHONSTARTUP (or BOASTARTUP) script
when Boa starts, just like IDLE. The key thing is that the startup scripts
need to execute in the shell interpreter's namespace. I borrowed the basic
technique from IDLE and modified it to fit the coding conventions used in
Boa.

These changes were tested with a good startup script as well as one that had
an error. Boa loads gracefully in either case and reports the error if there
is one. I also tried it with the -D filename debugging option and the
startup stuff was ignored. I'm not sure why. I'll leave it up to Riaan to
decide if that is appropriate behavior or not. I did NOT test it with the -T
option.

One difference that I found between my implementation and IDLE's concerns
print statements within the startup script. In IDLE, print statements in the
startup script appear in the shell itself, whereas in Boa the same print
statements appear in the Python console. Again, I'll defer to Riaan on this
issue.

Here is an example of running Boa with the -s switch:

C:\Python21\python.exe C:\Code\boa\Boa.py -s

You can also run it from a Windows shortcut or menu (but not from a DOS
prompt) with just the following:

C:\Code\boa\Boa.py -s

If there is a better way to submit patches like this, please let me know. If
you think my code sucks, let me know that as well. <grin>

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

RE: [Boa Constr] CVS issues

[Patrick K. O'B. <po...@or...>]

I was going to use it, then I chickened out and went with WinCVS. Now that
I've had success with WinCVS I will try the CVS feature in Boa ... I
promise. <wink>

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of Riaan
Booysen
Sent: Wednesday, June 27, 2001 2:14 PM
To: Boa list
Subject: [Boa Constr] CVS issues

There has been a few questions regarding CVS access recently.

I do not use WinCVS anymore and exclusively use Boa's built in CVS
support. I strongly recommend at least trying it out!

If you have problems getting it going, ask and I will assist (and
update the docs)

I really like this feature in Boa, but it does not seem as though
anyone is using it.

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

[Boa Constr] CVS updated, more fixes for 2.3.0

[Riaan B. <riaan@e.co.za>]

Hi everybody,

CVS has been updated, major changes:
* Fixes for 2.3.0. No more crashes!
* Source generation:
  * The code will only be marked modified if there *were* changes.
  * Code generated from dictionaries are now exported in sorted order
    so that there are unecessary code changes (like the order of 
    parameters shuffling around) This makes the output rom the 
    designer much more CVS friendly.

  * Any code (e.g. code you added by hand) left unparsed in the 
    generated _init_* methods will be shown in a warning box.
  * Any exception during the parsing and creation of the Designer
    will rollback and Cancel the designer session, saving you the
    temptation to post possibly broken code ;)
    I should have done this a long time ago.

  I hope these changes curb the occurences of the Designer 
  corrupting your source.

  If after this you still have reproduceable steps to let the 
  Designer break the source, please mail them to me and I will try
  to fix it.

  You must however realise that editing _init_* methods is dangerous 
  and done at your own risk, no guarantees.

  One important note on _init_* methods (I will add it to the docs).
  Boa owns the entire code block between the start of one method
  and the start of the following method.
  This means that class variables between methods will be eaten.
  At least now you will be warned about it.

  I plan on collapsing _init_* methods with Scintilla's code folding
  after posting a Designer session.

* Shell improvements (Auto complete and call tips) and bug fixes
* Improved status display
* Boa is now scriptable (sort of) ;)
  There is now a special name added to sys: sys.boa_ide
  It's a reference to the Editor object. Almost everything in Boa
  can be reached thru the Editor.
  e.g.  
  >>> sys.boa_ide.openOrGotoModule('wxFrame1.py')
  or
  >>> sys.boa_ide.addNewModulePage()
  etc.
  
  Obviously scripts imported in the Boa shell can also access this
  object by importing sys.

Enjoy!
-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] CVS issues

[Riaan B. <riaan@e.co.za>]

There has been a few questions regarding CVS access recently.

I do not use WinCVS anymore and exclusively use Boa's built in CVS
support. I strongly recommend at least trying it out!

If you have problems getting it going, ask and I will assist (and 
update the docs)

I really like this feature in Boa, but it does not seem as though
anyone is using it.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Support for Win32all

[Riaan B. <riaan@e.co.za>]

Hi,

"Patrick K. O'Brien" wrote:
> 
> Will boa ever be able to work on an app that makes use of the win32all
> extensions, or am I stuck using PythonWin? For example, I am building an app
> that uses DDE. In boa, "import dde" returns an error.
> 

dde requires win32ui.pyd which is in your pythonwin directory.
If you put it somewhere accessible to python e.g. python20/win32
you should be able to import it. First import win32ui though.

I don't know if this 'works', but at least it imports successfully.

> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Problems with latest CVS version

[Riaan B. <riaan@e.co.za>]

Hi Gordon, get the latest from CVS to address some of these issues,

Gordon Williams wrote:
> 
> Hi,
> 
> I downloaded Boa yesterday June 18th and I am having a couple of problems
> with errors being created.
> 
> I'm using W2000, python 2.0, wxPython 2.2.5, if that makes any difference.
> 
> 1)    Boa copies some stuff to my wxPython directory bcrtl but this was
> disallowed.  I think it is because they are read-only files.  I changed the
> name of the existing bcrtl directory and then the new stuff was copied
> properly.

I'm not sure how to handle this installing issue (especially on Linux)
I also could not reproduce this by making the files read only.

> 
> 2)  When the designer panel is open and I click on a panel I get the
> following error:
> 
> 10:48:49: ClassLinkPropEdit: :
> <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
> 10:48:49: <C wxButton instance at None> :
> <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
> 10:48:49: not found : <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py,
> 829>>

This has always been there (it was just a print to stdout before)
It is actually partially fixed by 2.3.0 :)

If you staying with 2.2.5, feel free to remove the offending print;
PropertyEditors.py, line 829

> 
> I think that there may be other widgets that also produce this error.

Not that I know of...

> 
> Question:
> Is there a way that I can pass a list to a wxChoice widget (eg. choices=
> mychoices).  I tried this with mychoice both as a module variable (boa
> complained about unkown variable) and as a class variable (defined above def
> _init_utils(self): at the start of the class).  Now all hell has broken
> loose and my source code looks like:

Yeah ugly :(

I cannot reproduce generating repeating code like this so if you can 
still do this with the lastest sources, send me the instructions on how.

Having references to variables outside what is defined in the Designer
is not supported yet. It's a tricky problem.
Just having access to globals does not win you much. Any static data
can be stored in the code. But it would be nice.
If you intend to change the values of globals before constructing
the frame, this is not an approach I want to encourage.

Also there is no natural way to put a variable name into e.g. a 
string property editor or a colour property editor.
Most property editors will therefor need another mode where
variables can be entered.

I've been considering the following, it's similar to what you guessed
should happen, so it's a good sign:
Attributes defined in __init__() above the call to _init_ctrls()
will be available to the Designer.

This still leaves the question of nice property editor integration,
but I will think about this more as I also really want this feature.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

RE: [Boa Constr] PYTHONSTARTUP

[Patrick K. O'B. <po...@or...>]

I got the latest CVS and this feature isn't working quite right for me. I've
looked at the IDLE source to see how Guido handled this and I see where the
problem lies. As soon as I have a chance I'll go through the boa code and
submit a patch to handle PYTHONSTARTUP the same way IDLE does. IDLE also
allows for an IDLESTARTUP so I'll look at adding a BOASTARTUP capability
while I'm at it.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of Riaan
Booysen
Sent: Friday, June 08, 2001 11:51 PM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] PYTHONSTARTUP

Hi Patrick,

Ok, this is now added to Boa, like IDLE, use the commandline switch -s
to run it.

Thanks.

"Patrick K. O'Brien" wrote:
>
> Might be better to do something like:
>
> import os
> filename = os.environ.get('PYTHONSTARTUP')
> try:
>     execfile(filename)
> except:
>     print "Unable to load startup script", filename
> del os  # Unless you want to leave os in the namespace.
>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."

RE: [Boa Constr] CVS problem

[Patrick K. O'B. <po...@or...>]

I got CVS to work by copying the login line off the boa page on sourceforge.
The only difference is in the case. So it must be case sensitive and an
older instruction that had been sent to this list won't work.

NEW CVSROOT:
ano...@cv...:/cvsroot/boa-constructor
(password authentication)
cvs login
(Logging in to ano...@cv...)

*****CVS exited normally with code 0*****

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of
Patrick K. O'Brien
Sent: Wednesday, June 27, 2001 11:02 AM
To: Boa Constructor Users
Subject: [Boa Constr] CVS problem

This is my first time using WinCVS and I can't seem to log in to the Boa CVS
server. I get the following error. Any suggestions?

cvs -z9 login
(Logging in to ano...@cv...)
Fatal error, aborting.
anonymous: no such user
cvs login: authorization failed: server cvs.boa-constructor.sourceforge.net
rejected access to /cvsroot/Boa-Constructor for user anonymous

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."



_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

[Boa Constr] CVS problem

[Patrick K. O'B. <po...@or...>]

This is my first time using WinCVS and I can't seem to log in to the Boa CVS
server. I get the following error. Any suggestions?

cvs -z9 login
(Logging in to ano...@cv...)
Fatal error, aborting.
anonymous: no such user
cvs login: authorization failed: server cvs.boa-constructor.sourceforge.net
rejected access to /cvsroot/Boa-Constructor for user anonymous

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

[Boa Constr] Support for Win32all

[Patrick K. O'B. <po...@or...>]

Will boa ever be able to work on an app that makes use of the win32all
extensions, or am I stuck using PythonWin? For example, I am building an app
that uses DDE. In boa, "import dde" returns an error.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

[Boa Constr] Python Shell - was: RE: IDLE's save-before-run r equirement

[Patrick K. O'B. <po...@or...>]

Thank you, Guido, for bearing with me on this whole issue. I think we are
getting to the heart of the matter. Because I, too, am an instant
gratification person. So let's just talk about the Python Shell
(interactive) capabilities as they exist in the various IDEs. I will attempt
to explain my take on this situation, what bothers me, and what I'd like to
see happen.

The four tools under discussion. IDLE, Boa, PythonWin and VPython all have a
Python Shell capability. But they all vary in their support of keybindings,
coloring, indenting, etc. When someone uses all of these tools and makes use
of each Shell, they have to keep in mind all the variations that exist. This
is counter-productive and takes away from what should be "instant
gratification at all times." I would rather have a common feature set within
all Shells, even if it meant giving up features, rather than have the
variations that exist now. I would like to see the Python Shell exist as
some kind of plug-in or shared code base that all the IDEs could use so that
the Python Shell was uniform in all tools on all platforms. I think this
fits the Python philosophy and would make life a lot easier for beginners as
well as experts. It would also make the Shell available for new,
special-case tools that have been discussed, such as a Python Tutor or
Python Trivial Pursuit game, where the variations would be solely within the
value-add portions and not the fundamental Shell capability (and without
creating yet more forks).

Here are some specific examples of the variations that bother me (Please
don't anyone take offense at these comparisons. I believe they are all
objective, demonstrable differences and not just my opinion, though I am
clearly opinionated. And if I'm wrong about any of this please let me
know.):

PYTHONSTARTUP: IDLE and VPython support it with the -s command line switch.
Boa will have this feature in the next release (because I asked for it).
PythonWin has no support whatsoever for PYTHONSTARTUP to my knowledge.

Home key: Type a line of code at the shell prompt (>>>) and then hit the
Home key. PythonWin puts the cursor in front of your code (very nice). IDLE
and VPython put the cursor in front of the prompt and then beep when you try
to continue typing (yuck). Boa puts the cursor in front of the prompt and
lets you type over the prompt. When you hit enter it truncates the first
four characters from what you typed and tries to execute that (big yuck). I
use this feature a lot in PythonWin when I'm copying previous lines down and
want to get to the beginning of the line to add more code, like assigning to
a variable or some such. When I switch to one of the other tools I have to
do Home, Right, Right, Right, Right - way too many keystrokes.

Command history: IDLE and VPython have Alt-P (previous) and Alt-N (next),
which is very nice. PythonWin has a way to add these bindings, but by
default has Ctrl-Up and Ctrl-Down (just to be different?). I don't know how
to add the PythonWin bindings to IDLE or VPython. Boa has no command
history.

Call tips: PythonWin has the best as far as showing what is in a module.
IDLE/VPython have the best as far as showing function parameters and
docstrings. Boa is way behind.

Win32All: PythonWin is the only tool that can deal with the win extensions,
like dde or com. This is a major pain. There are times when I'd love to use
IDLE but since I'm developing a Windows app that requires DDE I can only use
PythonWin. (And I don't really understand why this is but it definitely
irritates me to no end.)

I'm sure there are other differences, but these are good enough to get my
point across. So I will finish with a question - What, if anything, can be
done about this situation, or am I barking up the wrong tree?

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: gu...@cj...
[mailto:gu...@cj...]On Behalf Of Guido van Rossum
Sent: Thursday, June 21, 2001 7:41 AM
To: ala...@bt...
Cc: is...@li...; po...@or...; ma...@la...;
idl...@py...; Ed...@py...; tu...@py...
Subject: Re: [Tutor] Re: [Edu-sig] RE: [Idle-dev] IDLE's save-before-run r
equirement

> > What would switching over to using Scintilla accomplish that
> > sticking with IDLE and continuing it's development wouldn't?
>
> In a word "Reuse". That means one editor to maintain for most
> of the Python IDEs. Add a feature to Scintilla and its pretty
> trivial for all the IDEs to pick up the new feature without
> having to reimplemnent it from scratch. Effort gets concentrated
> on the value add bits rather than the nitty gritty of text editing.

But IDLE has a bunch of requirements that I don't think Scintilla can
provide.  IDLE has really two editing modes: the regular module/file
editor, and the "Python Shell".  IDLE's most redeeming feature, IMO,
is the Python Shell.  Compare editing an interactive session in
PythonWin's console window with IDLE's Python Shell.  IMO again, IDLE
is infinitely better, because it uses the exact same editing features
as the module/file editor, meaning you get proper syntax coloring,
automatic indentation, call tips, magic expansion; and on top of that
you get per-line syntax checking, whole-command editing, and history
recall.  In PythonWin's much more primitive console, it's very easy to
mess up the input or the output or confuse the auto-indenter.

(I'm an instant gratification person, so Python's interactive mode is
very important to me.)

I could be wrong about Scintilla not supporting this, but if it did,
why would PythonWin not use it for *its* console?

--Guido van Rossum (home page: http://www.python.org/~guido/)

[Boa Constr] Problems with latest CVS version

[Gordon W. <g_...@cy...>]

Hi,

I downloaded Boa yesterday June 18th and I am having a couple of problems
with errors being created.

I'm using W2000, python 2.0, wxPython 2.2.5, if that makes any difference.

1)    Boa copies some stuff to my wxPython directory bcrtl but this was
disallowed.  I think it is because they are read-only files.  I changed the
name of the existing bcrtl directory and then the new stuff was copied
properly.

2)  When the designer panel is open and I click on a panel I get the
following error:

10:48:49: ClassLinkPropEdit: :
<<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
10:48:49: <C wxButton instance at None> :
<<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py, 829>>
10:48:49: not found : <<G:\CVSFIL~1\Boa\boa\PropEdit\PropertyEditors.py,
829>>

I think that there may be other widgets that also produce this error.


Question:
Is there a way that I can pass a list to a wxChoice widget (eg. choices=
mychoices).  I tried this with mychoice both as a module variable (boa
complained about unkown variable) and as a class variable (defined above def
_init_utils(self): at the start of the class).  Now all hell has broken
loose and my source code looks like:


        self.button2_Cancel = wxButton(label = 'Cancel', id =
wxID_WXDIALOG2BUTTON2_CANCEL, parent = self.panel1, name = 'button2_Cancel',
size = wxSize(87, 28), style = 0, pos = wxPoint(280, 232))
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)
        EVT_BUTTON(self.button2_Cancel, wxID_WXDIALOG2BUTTON2_CANCEL,
self.OnButton2_cancelButton)

        self.radioBox1 = wxRadioBox(label = 'Individual Trace Display', id =
wxID_WXDIALOG2RADIOBOX1, choices =
['1','2','3','4','5','6','7','8','9','10','ALL'], validator =
wxDefaultValidator, majorDimension = 3, point = wxPoint(168, 88), parent =
self.panel1, name = 'radioBox1', size = wxSize(192, 120), style =
wxRA_SPECIFY_COLS)
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        self.radioBox1.SetStringSelection('ALL')
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)
        EVT_RADIOBOX(self.radioBox1, wxID_WXDIALOG2RADIOBOX1,
self.OnRadiobox1Radiobox)


and so on.  I lost a few widgets as well.  My guess is that I should put it
under __init__ with the variable defined as self.mychoices but I havent
tried it yet.

Aside from these problems, boa look very good.  Thanks.

Regards,

Gordon Williams

[Boa Constr] CVS problems

[Antoni A. <al...@ct...>]

Hi!

I'm trying to connect to Boa Cvs using wincvs, what I have done is:

a) Create/New Repository
I have written in the general init settings
pserver:ano...@cv...:/cvsroot/boa-construct
or
and I have choosen
Authentification
passwd

b) When connecting I get the following message:

"
cvs -z9 -d
:pserver:pserver:ano...@cv...:/cvsroot/boa-
cons... init
Fatal error, aborting.
pserver:anonymous: no such user
cvs init: authorization failed: server cvs.Boa-Constructor.sourceforge.net
rejected access
cvs init: used empty password; try "cvs login" with a real password
*****CVS exited normally with code 1*****
"
I don't know what I'm doing wrong, so any help would be greatly appreciated.

Best regards,
Antoni Aloy

RE: [Boa Constr] Windows SendTo

[Mike C. F. <mcf...@ho...>]

You should find the code to do this stuff somewhere in PythonWin (which does
support such second-click reuse of the app).  If I'm not mistaken it's
implemented using some kind of DDE conversation going on between the app and
the system.  Since Pythonwin is BSD licensed, you should be able to pull the
code out and wrap it into a module.  I'd suggest doing that instead of just
grafting it into Boa because then you could let any python app use the
mechanism.  I suspect what happens is that the PythonWin executable checks
for other running PythonWin executables then opens an RPC/DDE channel to
pass the arguments if they exist.

HTH,
Mike

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of
Riaan Booysen
Sent: June 14, 2001 13:32
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Windows SendTo




"Patrick K. O'Brien" wrote:
>
> I tried your suggestion and it works great on the first file when boa is
not
> already running. But then if you try it on a second file it load a
> completely new instance of boa, rather than opening up in the existing boa
> application. Anyone know a way around this?

No simple ideas.

Boa supports drag-drop from the filemanager so just drag subsequent
files onto the Editor.

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

Re: [Boa Constr] Windows SendTo

[Riaan B. <riaan@e.co.za>]

"Patrick K. O'Brien" wrote:
> 
> I tried your suggestion and it works great on the first file when boa is not
> already running. But then if you try it on a second file it load a
> completely new instance of boa, rather than opening up in the existing boa
> application. Anyone know a way around this?

No simple ideas.

Boa supports drag-drop from the filemanager so just drag subsequent
files onto the Editor.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

[Boa Constr] Boa directory - Was: Windows SendTo

[Patrick K. O'B. <po...@or...>]

Never mind, that was my decision. I just moved boa to python21\tools\boa and
changed all my shortcuts. Personally, I think the instructions should
recommend a standard location for the boa files.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of
Patrick K. O'Brien
Sent: Thursday, June 14, 2001 9:58 AM
To: Boa Constructor Users
Subject: RE: [Boa Constr] Windows SendTo

<snip>

Which now has me wondering whether having the Boa version number in the
directory name is going to be more trouble than its worth. I'd be curious to
know what you folks recommend. I'm pretty sure I just let the installer do
its thing. But if 0.0.6 gets installed in a separate directory then all my
links and shortcuts will still be pointing to 0.0.5. I guess you could call
it a feature or a hassle, depending on how you look at it. But I'm starting
to think it might be a hassle.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

RE: [Boa Constr] Windows SendTo

[Patrick K. O'B. <po...@or...>]

I tried your suggestion and it works great on the first file when boa is not
already running. But then if you try it on a second file it load a
completely new instance of boa, rather than opening up in the existing boa
application. Anyone know a way around this?

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: boa...@li...
[mailto:boa...@li...]On Behalf Of Riaan
Booysen
Sent: Thursday, June 14, 2001 9:26 AM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Windows SendTo

Hi Patrick,

"Patrick K. O'Brien" wrote:
>
> I'd like to be able to add boa to my SendTo list under windows so I can
> right click on a .py file, select SendTo, Boa and have Boa open the file
up
> in its editor window. I can add notepad, excel, PFE and so forth to my
> SendTo list but I can't get it to work with Boa. Is this possible?

I can't get it going either. I think the problem is the limited way
that SendTo works. Seems it can only handle executables.

Another alternative is to define an action associated with .py files;

On a folder choose View->Options->File Types or
Tools->Folder Options->File Types

Select Python File in the list (if you have win32all installed)
otherwise a add a new type with extension .py

Now add an action to the type called 'Edit in Boa'
and as application add e.g.
c:\python20\python.exe c:\python20\tools\boa\boa.py

Now you'll have it as an option if you right click on .py files.

>
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
>
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

_______________________________________________
Boa-constructor-users mailing list
Boa...@li...
http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

Re: [Boa Constr] Windows SendTo

[Riaan B. <riaan@e.co.za>]

Hi Patrick,

"Patrick K. O'Brien" wrote:
> 
> I'd like to be able to add boa to my SendTo list under windows so I can
> right click on a .py file, select SendTo, Boa and have Boa open the file up
> in its editor window. I can add notepad, excel, PFE and so forth to my
> SendTo list but I can't get it to work with Boa. Is this possible?

I can't get it going either. I think the problem is the limited way
that SendTo works. Seems it can only handle executables.

Another alternative is to define an action associated with .py files;

On a folder choose View->Options->File Types or
Tools->Folder Options->File Types

Select Python File in the list (if you have win32all installed)
otherwise a add a new type with extension .py

Now add an action to the type called 'Edit in Boa'
and as application add e.g.
c:\python20\python.exe c:\python20\tools\boa\boa.py

Now you'll have it as an option if you right click on .py files.

> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] Shell enhancements part 2

[Riaan B. <riaan@e.co.za>]

Hi,

"Patrick K. O'Brien" wrote:
> 
> I dug a little more into PythonWin because they are also using Scintilla,
> and I found that they use a configuration file with the excerpts I've pasted
> below. Then I looked for something similar in boa and couldn't find
> anything. I looked at PrefsKeys.py, PrefsMSW.py and ShellEditor.py but
> didn't see anything that stood out as relevant. I think a keybinding
> configuration file would be nice. PythonWin lets you have a configuration
> file that is based on another and overrides it (kind of like inheritance).
> That way you leave the default bindings file alone. I like that approach. An
> example of that is included below as well. Is any of this doable?
> Reasonable? Desireable (to anyone else)?

They use a configuration file Boa uses a source file.

In PrefsKeys.py every configurable keybinding used in Boa is listed
in the keyDefs dictionary.

I have just added the following snippet to the end of PrefsKeys.py:

try:
    from PrefsCustomKeys import overrideKeyDefs
except ImportError:
    pass
else:
    keyDefs.update(overrideKeyDefs)

Now add your own CustomPrefsKeys.py defining overrideKeyDefs with all 
the keys you want to redefine.

If anybody has redefined PrefsKeys.py to match other editors, 
please mail it to me.

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Re: [Boa Constr] calltips and autocompletion

[Riaan B. <riaan@e.co.za>]

Hello Patrick O'Many questions ;)

"Patrick K. O'Brien" wrote:
> 
> What is the process for expanding the calltips and autocompletion
> capabilities of the boa editor and shell so that it is on par with IDLE and
> PythonWin? (And if you want to respond by saying "feel free to modify the
> source and make this work" I can only say that I fully intend to help out as
> I get up to speed. In the mean time I'm just looking for some basic
> background info and hoping that you've already finished this. <grin>

Ctrl-Space brings up code completion, Ctrl-Shft-Space next to a 
bracket brings up calltips (not much calltip support yet)

I've now made these bindings configureable.

At the moment the code completion reflects the information Boa has
available after parsing the file.

One big difference between Boa and IDLE/PythonWin is that Boa works
on one module at a time while IDLE/PythonWin also include the modules
that are imported in the module.
I went this route to cut down on the time required for parsing.

I definately intend to improve the situation.

IDLE and PythonWin share a code base called the IDLE Extensions. 
This includes keybindings, code completion, block manipulations
on the source like indent and other operations.
I have considered also using it but so far I have not had the time.
It will require a lot of changes.

If anybody has time to look into this I would really appreciate it.

If you want to look at the source for code completion check out:
Views.PySourceView.checkCodeComp()

CallTips really needs attention; things like activating anywhere
inside the bracket (instead of just next to one), bolding the
current item in the parameter list etc are still missing.

Look at:
Views.PySourceView.checkCallTip()


> 
> ---
> Patrick K. O'Brien
> Orbtech
> "I am, therefore I think."
> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

RE: [Boa Constr] Windows SendTo

[Patrick K. O'B. <po...@or...>]

Excellent. I forgot about that approach. Works like a charm, though I did
have to change things for my setup. I used:

c:\python21\python.exe C:\Python21\Boa-0.0.5\Boa.py

Which now has me wondering whether having the Boa version number in the
directory name is going to be more trouble than its worth. I'd be curious to
know what you folks recommend. I'm pretty sure I just let the installer do
its thing. But if 0.0.6 gets installed in a separate directory then all my
links and shortcuts will still be pointing to 0.0.5. I guess you could call
it a feature or a hassle, depending on how you look at it. But I'm starting
to think it might be a hassle.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: Riaan Booysen [mailto:riaan@e.co.za]
Sent: Thursday, June 14, 2001 9:26 AM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Windows SendTo

Hi Patrick,

"Patrick K. O'Brien" wrote:
>
> I'd like to be able to add boa to my SendTo list under windows so I can
> right click on a .py file, select SendTo, Boa and have Boa open the file
up
> in its editor window. I can add notepad, excel, PFE and so forth to my
> SendTo list but I can't get it to work with Boa. Is this possible?

I can't get it going either. I think the problem is the limited way
that SendTo works. Seems it can only handle executables.

Another alternative is to define an action associated with .py files;

On a folder choose View->Options->File Types or
Tools->Folder Options->File Types

Select Python File in the list (if you have win32all installed)
otherwise a add a new type with extension .py

Now add an action to the type called 'Edit in Boa'
and as application add e.g.
c:\python20\python.exe c:\python20\tools\boa\boa.py

Now you'll have it as an option if you right click on .py files.

RE: [Boa Constr] Shell enhancements

[Patrick K. O'B. <po...@or...>]

Excellent. I sure needed that one. Thanks.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: Riaan Booysen [mailto:riaan@e.co.za]
Sent: Thursday, June 14, 2001 9:25 AM
To: po...@or...
Cc: Boa Constructor Users
Subject: Re: [Boa Constr] Shell enhancements

Hello Patrick,

"Patrick K. O'Brien" wrote:
>
> When I am in the shell, how do I reexecute a previous command? In other
> shells you can go to a previous line and hit return and that line gets
> copied down to the lowest prompt, then you can hit return again and it is
> executed. I'm rather in the habit of doing this while experimenting with
> things interactively. Is there a way to get the same behavior with boa? In
> addition, IDLE has Alt-p and Alt-n to retrieve commands and Alt-/ to
expand
> words. PythonWin shares some of these same conventions. While it doesn't
> have Alt-p or Alt-n it does allow you to hit return on previous lines and
do
> Alt-/ to expand words.

Luckily I've added one of these sorely missing features a little while
ago (now in CVS)

You can now go up and down in your history of commands with ctrl and
up and down cursors (Like in PythonWin ;)

--
Riaan Booysen

Re: [Boa Constr] Shell enhancements

[Riaan B. <riaan@e.co.za>]

Hello Patrick,

"Patrick K. O'Brien" wrote:
> 
> When I am in the shell, how do I reexecute a previous command? In other
> shells you can go to a previous line and hit return and that line gets
> copied down to the lowest prompt, then you can hit return again and it is
> executed. I'm rather in the habit of doing this while experimenting with
> things interactively. Is there a way to get the same behavior with boa? In
> addition, IDLE has Alt-p and Alt-n to retrieve commands and Alt-/ to expand
> words. PythonWin shares some of these same conventions. While it doesn't
> have Alt-p or Alt-n it does allow you to hit return on previous lines and do
> Alt-/ to expand words.

Luckily I've added one of these sorely missing features a little while
ago (now in CVS)

You can now go up and down in your history of commands with ctrl and 
up and down cursors (Like in PythonWin ;)

> 
> _______________________________________________
> Boa-constructor-users mailing list
> Boa...@li...
> http://lists.sourceforge.net/lists/listinfo/boa-constructor-users

-- 
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net