boa-constructor-users

[Boa Constr] Boa doesn't run for me...

[Albert W. <alw...@tc...>]

Suse-7.1, KDE2.1.1, Python-2.1, GTK-1.2.8, wxGTK-2.2.6, wxPython-2.2.5

I can find little documentation to help with installation.  Surely I've done 
something wrong.  Attempts to run Boa yield:

$ ~/pkg/language/python/Boa
$ Boa.py
: command not foundpy:
: command not foundpy:
 
$ ~/pkg/language/python/Boa
$ python Boa.py
importing Prefs
importing wxPython...
Traceback (most recent call last):
  File "Boa.py", line 62, in ?
    import About
  File "About.py", line 7, in ?
    import Preferences, Utils
  File "Utils.py", line 16, in ?
    from ExternalLib.ConfigParser import ConfigParser
ImportError: No module named ExternalLib.ConfigParser

Any help appreciated. Thanks ahead.

Re: Re:[Boa Constr] I:What's next?

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

Hello Umberto,

----- Original Message -----
From: "Barbini Uberto" <Ube...@ce...>
To: <boa...@li...>
Sent: Thursday, May 17, 2001 10:29 AM
Subject: Re:[Boa Constr] I:What's next?


> There are some plans for streaming forms?

The current policy is still code generation/code parsing. I do plan to add
some XML support when wxPython supports it (next release I think)

>
> Where can I contribute? A simple item please! ;)

The best places to contribute are always the areas you are interested in.
How about a proper find/replace dialog for the editor?

Riaan

Re: [Boa Constr] Re:What's next?

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

Hi Umberto,

----- Original Message -----
From: "Barbini Uberto" <Ube...@ce...>
To: <boa...@li...>
Sent: Friday, May 11, 2001 9:39 AM
Subject: [Boa Constr] Re:What's next?


> > > > I'm very impressed of current boa features.
> >
> > Thank you,
> >
> I remember a boa version last summer.
>
> > > >
> > > > Where are you going? Can I join? ;)
> >
> > Everywhere!
> > Can you contribute? ;)
> >
> I hope so.

Me too!

> I'm a Delphi consultant. I've worked in many Open Source projects.
> I've learned Python recentely but I've used only for some cgi.
> Python is by far the best language I've heard of.

Yeah!

>
> And IMHO Borland did choose a wrong way with high prices and poor
products.

Let me come to their defence. They have emloyees, not volunteers and in a M$
brainwashed marketplace, I don't think they've had much choice.
Personally I've never worked with a poor Borland product. (Ok, maybe the BDE
had some a slight deployment pains ;)
Anyway Delphi rocks! It is after all the inspiration behind Boa.

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

Re:[Boa Constr] I:What's next?

[Barbini U. <Ube...@ce...>]

There are some plans for streaming forms?

Where can I contribute? A simple item please! ;)

Bye Uberto

> > > Where are you going? Can I join? ;)
> 
> Everywhere!
> Can you contribute? ;)
> 

[Boa Constr] Re:What's next?

[Barbini U. <Ube...@ce...>]

> > > I'm very impressed of current boa features.
> 
> Thank you,
> 
I remember a boa version last summer.

> > > 
> > > Where are you going? Can I join? ;)
> 
> Everywhere!
> Can you contribute? ;)
> 
I hope so.
I'm a Delphi consultant. I've worked in many Open Source projects.
I've learned Python recentely but I've used only for some cgi.
Python is by far the best language I've heard of.

And IMHO Borland did choose a wrong way with high prices and poor products.

	Bye Uberto

Re: [Boa Constr] Python 2.1

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

----- Original Message ----- 
From: "Patrick K. O'Brien" <po...@or...>
To: <boa...@li...>
Sent: Thursday, May 10, 2001 5:18 PM
Subject: [Boa Constr] Python 2.1


> Has Boa been tested with Python 2.1 yet? Is anyone using it with 2.1 or
> should I hold back and use it with 2.0? Thanks.

There has been (and should be) no incompatible language changes.
Please change over and tell me if something breaks.

Riaan

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

Re: [Boa Constr] I:What's next?

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

----- Original Message ----- 
From: "Barbini Uberto" <Ube...@ce...>
To: <boa...@li...>
Sent: Thursday, May 10, 2001 12:00 PM
Subject: [Boa Constr] I:What's next?


> 
> > I'm very impressed of current boa features.

Thank you,

> > 
> > Where are you going? Can I join? ;)

Everywhere!
Can you contribute? ;)

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

Riaan

[Boa Constr] Python 2.1

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

Has Boa been tested with Python 2.1 yet? Is anyone using it with 2.1 or
should I hold back and use it with 2.0? Thanks.

---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."

[Boa Constr] I:What's next?

[Barbini U. <Ube...@ce...>]

> I'm very impressed of current boa features.
> 
> Where are you going? Can I join? ;)
> 
> 
> Bye Uberto
> 

Re: [Boa Constr] Fw: need help with Boa Constructor

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

Hello Nick,

Nick Perkins wrote:
> 
> > I can run Boa Constructor, but the
> > 'Frame Designer' will not run.
> > I press the button, and nothing happens.
> > Has anyone else had this happen?
> > Any suggestions?
> > ( i am using:
> >   Boa 0.0.5
> >   Python 2.0
> >   wxPython 2.2.5
> >   Win NT 4.0
> > )

Did you modify any of the _init_* methods that Boa generates?
See Docs/MixingSource.html for details.

If this does not sort out the problem, please email me the generated 
source file and I'll have a look.

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

[Boa Constr] Fw: need help with Boa Constructor

[Nick P. <npe...@ho...>]

> I can run Boa Constructor, but the
> 'Frame Designer' will not run.
> I press the button, and nothing happens.
> Has anyone else had this happen?
> Any suggestions?
> ( i am using:
>   Boa 0.0.5
>   Python 2.0
>   wxPython 2.2.5
>   Win NT 4.0
> )

[Boa Constr] position of containers in design view

[Bakki K. <ba...@na...>]

I see that the container (tool bar) ends up in a different position than
where its contents (tool buttons). For example I created a frame, a
menubar and then a tool bar. WHile the visible tool bar and its buttons
end up at the expected postion just under the menubar, I don't see it in
the Inspector until I click in the invisible tool bar somewhere else in
the window. Once I hit the toolbar it appears with its border handles
which I can use to resize and move but it never stays where I put it nor
exactly coincide with the visible tool bar.

After adding a splitter window beneath the toolbar is inaccessible for
editing.

Has anyone seen this sort of behavior?

-bakki

-- 
  .-.    | Bakki Kudva__________________Open Source EDMS______
  oo|    | Navaco                       ph:  814-833-2592
 /`'\    | 420 Pasadena Drive           fax: 603-947-5747
(\_;/)   | Erie, PA 16505               http://www.navaco.com/

Re: [Boa Constr] Contrib: makepy dialog for Boa

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

Hi Mike, thanks for the contribution, it's now integrated with Boa
and accesible from the 'New' palette page.

To expand the COM support in Boa I've added Acrobat and IE as examples.
I have not automated the process and there is some manual work to get 
a COM control integrated in Boa.

Like other controls you have to write a Companions class for the
COM control. See Companions.ComCompanions for examples. Additionally
you have to write a thin wrapper for the ActiveX control itself, this
makes it look more like a normal control to Boa and allows it better
integrate with current machinery. This could be automated.
See bcrtl.activex.acrobat and bcrtl.activex.IE for details.

Note that for IE I have added code which translate the Python COM
events to wxWindows events so that they may be defined in the Inspector.
This was a mechanical process and could definitely be automated as well.

This is a first draft at COM support and everything may still change.

COM properties aren't supported yet.

Note that now for the first time Boa needs to have a run time library.
Before, all code was generated to run on wxPython libraries but the
extra COM control layer needs to be accessible to your generated source.

For now I've decided to place this run time library under wxPython.lib.
If you wrap a COM control, the new module must be placed under here.
e.g. wxPython.lib.bcrtl.activex.acrobat.

This will also apply to any new control you wish to add to Boa which
is not part of the wxPython distribution. Place these controls modules
under wxPython.lib.bcrtl.user.

One problem may me wxPython's very aggresive uninstaller which 
deletes everything under the wxPython directory.

For deployment I think Boa should also be able to generate source that
uses components defined in the application's own directory.
Also in this direction, Boa should make it much easier to to use
visual objects defined in an application, but for which there is no
associated Companion (defining design time logic).
Boa should simply handle such objects as their base classes, e.g
wxListCtrl or wxStaticText or whatever.

I've put in a check so that Boa automatically creates/copies these 
files if they do not exist on startup.

There is also an option in Preferences.py, blockCOM which is on by
default (because of the crasing under win9x). Turn off the block to
enable COM.

"Mike C. Fletcher" wrote:
> 
> I wanted to play around with Boa as an IDE a little more, so I decided I'd
> make a MakePy dialog for it (a Win32COM thing that lets you auto-generate
> wrappers for COM controls).  It's slightly more advanced than the dialog in
> PythonWin, as it lets you search for libraries.  This isn't particularly
> beautiful, but it does seem to work.  Eventually you'd want to create
> Design-time controls and options on the design palette for each wrapped
> control (maybe even scanning the gen_py directory for controls generated by
> other systems), but for now it's just a "tell it to generate a wrapper"
> dialog.

One problem at the moment is that it generates different type libraries
than the EnsureModule call that is used when ActiveX controls are used
in wxPython. If the library is generated from the Dialog, the controls
no longer work in wxPython. (Test this with the demo).
I believe that the EnsureModule behavior should be the default
behaviour. It also generates the methods which it useful.
Can you change your dialog to work like this?

> 
> Thoughts that have arisen as I worked:
>         An option for PythonWin key bindings would be nice (is there a way to
> plug-in whole key-binding sets with minimal fuss?).

See PrefsKeys, I believes this meets your requirements.

>                 Block indent/dedent mapped to tab/shift-tab is very useful

To use Tab for indent dedent was one of the few keys that could not
be mapped from PrefsKeys because the keys in PrefsKeys are bound with
an accelerator table and when a key is bound in a table, it does not 
generate key events in the control anymore (which I needed)
I've duplicated the logic in the Indent/Dedent methods so the key
tab is no longer needed and tab/shift tab indenting now works.
I'm not convinced this should be default tho.

>                 Block-comment/uncomment mapped to Alt-3, Alt-4 is nice
>                 Ctrl-G mapped to Goto

Goto what? Line number?

>         Option for tab-preservation/conversion wasn't immediately obvious in the
> interface, possibly in the preferences.

Boa is rather harsh in this respect. No tabs preserved. As the style 
guide says 4 space tab levels, this is enforced.

>         Tools to tabify/untabify source are needed.

Running Edit->Reindent whole file will remove all tabs and correct
a few other things, this is non reversable.

>         Auto-complete windows a-la PythonWin are very helpful (for me anyway).

There is limited auto-complete support, pressing control space after
'self.' will bring up a list of all methods/attribute for that object 
defined in the current module. wxPython object decendants brings
up a list of all methods in the wxPython libraries.
Ctrl-Space without 'self.' in a class will bring up the entire wxPython
namespace.
Shift-Space for parameter tips, but there is very little support here.
Note that sometimes you'll have to refresh your code (Ctrl-R) 
(so the source is reparsed) before the code completion box will appear.

>         Might be nice to have an option that makes the "interface" text get wrapped
> in _( ) for internationalisation (or whatever the standard is), with the
> files generated for translators on the side.

Yes this seems like a good idea, I have no experience with this and
if someone gives me the exact requiremnets I'll look into implementing
it.

>         The trace/error window doesn't appear until the client process completes
> and doesn't seem to update if I have to kill the client process.  Makes it
> hard to use with mis-behaving apps.

I'm at the mercy of popen2 here, sometimes you get output when you nuke 
an app or it crashes, sometimes you don't, suggestions would be welcome. 

Another painful fact is that both wxProcess and popen blocks if they
run a GUI application and only writes to their output and error streams
after the app terminates, I know of no workarounds. wxProcess also has
other problems when spawning GUI applications.

>         Option in the inspector to auto-generate shortcuts would be cool.
>         Would be good to have option to auto-generate a test-harness application
> for dialogs/frames.  See the attached for a simplistic harness.

Such a feature is already part of Boa. On the Source View select
Edit -> Add simple app. Not this this applies only to wxFrames at the
moment, for Dialogs the code has to be a little different. I will
still fix this.

This is the code that should be added for Dialogs:

if __name__ == '__main__':
    app = wxPySimpleApp()
    dlg = create(None)
    try:
        dlg.ShowModal()
    finally:
        dlg.Destroy()

Destoying the dialog is not strictly necessary as the process will
always terminate after ShowModal...

Ok, I've just fixed it so that Dialogs get the above code.
Model.getSimpleRunnerSrc() now returns the runner code for the
module type.

Intersting question is what should a normal python module get here?
For now the following lines are added to plain python scripts:

if __name__ == '__main__':
    pass # add a call to your main function here

> 
> Module attached, enjoy yourselves,
> Mike

Thanks for the code and feedback,

> 
> __________________________________
>  Mike C. Fletcher
>  Designer, VR Plumber
>  http://members.home.com/mcfletch
> 
>   ------------------------------------------------------------------------
>                       Name: makepydialog.py
>    makepydialog.py    Type: Plain Text (text/plain)
>                   Encoding: quoted-printable

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

Re: [Boa Constr] Impressions and comments...

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

Hi Mike, thanks for the comments,

"Mike C. Fletcher" wrote:
> 
> Hi all,
> 
> I've been playing with Boa (from the CVS) for a few days now, working on
> building a whole slew of dialogues for a wxPython app I'm behind on.
> Overall I'm impressed.  The dialogue building is going well, and it's saving
> me some serious time.  The following is a list of the nits I've run across
> so far.  I'm using Boa primarily as a GUI layout system, rather than as an
> actual IDE, so most comments will focus on the design window.
> 
> 1) Need a way to specify a particular ID for a given button (particularly
> need wxID_OK and wxID_CANCEL so that we can get automatic OK/Cancel
> behaviour in dialogues.  Potentially include OK/Cancel buttons explicitly in
> the buttons toolbar as well (still need the ability to specify).

I was not aware (or have forgotten) about this behaviour of buttons. 
Boa should support it. It might be a little tricky because the parent 
and id parameters are automatically managed internally by Boa and 
regenerated the whole time. I will look into this.

> 
> 2) Inspector's Event Handler Definition needs ability to specify a
> non-default name for the method

Yes, I intend to do this soon. The wxChoice in the Inspector will change
to a wxComboBox where you may edit the method name.

Note that you can change the name at the moment by just renaming it in
the source in 2 places, the EVT_* binding and the method name in the 
class. Boa will respect such changes.

> 
> 3) Inspector's "checkmark to expand options" is not intuitive, possibly use
> an owner-drawn icon instead?

How intuitive does a boolean control need to be ? ;)
I would prefer an small white boxed image of a + and - like in Delphi, 
but this is low priority for me at the moment.

> 
> 4) Option for auto-expansion of the editing window when not showing the
> designer would help with editing.  Would likely require adding the "new"
> toolbar as a menu in the editor.  Alternate window layouts with, for
> instance, a "design window" set and a "code editing" set might be useful.

The problem with this is that Boa is not in just one state at any given
time. You may have 5 frame modules of which 2 have Designers open.
Best you would probably be to have the editor window at full width and
to show and hide the inspector when needed. There are shortcut keys
which will save you time, F11 brings up the Inspector, F12 switches
between the Designer and the Editor. This works quite well.

> 
> 5) Would be nice to have drag-and-drop functionality for the widgets.  (i.e.
> drag from the toolbar to the design window).
	
I prefer the Delphi way, so this is very low priority for me. Patches
are welcome to make this an optional feature.

> 
> 6) How do you add new items to the list of available widgets (sub-classes,
> entirely new classes, etceteras)?

There are many many examples ;)

I will add an 'Extending Boa Constructor' section to the Help when I
have time.

Basically you need to do the following:

* Define a Companion class that mirrors the component that you want to
  wrap; Constructor, events, extra properties, style flags, etc.
  See code for details.

* Define new Property Editors if necessary.

* Register the component and companion with the Palette. See bottom of
  Companion modules for examples

* Add a 24x24 bitmap for the component to the Images/Palette and 
  Images/Palette/Gray directories. The one in the Gray dir should have
  a gray background while the other should have a magenta background.

* Restart Boa

I've just refactored the Palette code a bit so that registering should
be simpler. I've also added the module Companions.UserCompanions to
which you should add your own companions.
As another self contained example I've wrapped wxCalendarCtrl, 
but it's not yet on the Palette by default as there are still some
problems.
To enable it remove the comment in line 78 in Companions.UserCompanions.
Please take a look at the calendar code in Companions.UserCompanions.
There is also a Property Editor example.

> 
> 7) For a text control, altering "label" in the properties panel changes the
> control value, but doesn't alter the "value" attribute in the construction
> panel. (Reverse does work).

It's a more general problem where changing one property affects another
but Boa can not know this unless it is explicitly coded. I do handle
some
properties and will cover them all as time goes by.

> 
> 8) I couldn't find a "test dialog" function anywhere, i.e. run the dialog
> using run-time controls and report each event/call/etceteras generated by
> user interactions.  Not sure if I just missed it, but it's a really useful
> feature for figuring out what's going on.

There is no test dialog function as such, but "Edit -> Add simple app" 
comes close. It adds a code to the module which creates the frame and
a wxPySimpleApp(). Now run the module with the Blue arrow (F10/Run
module)

> 
> 9) Events panel of the inspector should likely use something other than
> "small list" style.  Because the names are touching the edges it looks as
> though scrolling only lets you see the "Event" text rather than showing
> entirely new event classes.  A downward-scrolling list gives a better "feel"
> that there's more items to see.

The scrollbar which appears on downward scrolling list controls took
too much horizontal space on lower resolutions for my taste, that's why
it's small list style. Maybe I should make this a preference?

> 
> 10) Default editor font for windows is very large on my machine, not sure
> why that is, I'm running a 1152x864 resolution, font looks to be about 15 or
> 16 point.  It's changeable, of course, but a smaller default might be
> reasonable.

Seems fine to me. Can you look at the screenshots on the boa web 
site and tell me if your font is bigger than what I see?

> 
> 11) A wxWindow option should be available in the Containers/Layout toolbar.
> (Or see #6)

Ok, I've added it.

> 
> 12) Could really use "nudge" key bindings for the design window.  i.e. the
> arrow keys nudge the selection 1 pixel or grid-point in their appropriate
> direction.

This is already done. Ctrl-Cursor keys moves the current selection in 
the Designer in 1 pixel increments. Shift-Cursor sizes it.

> 
> 13) Would suggest that when grid mode is on that new items be sized in
> increments of the grid

Grid mode is purely a visual setting. You can set the size in
Views.SelectionTags.screenGran.

Controls are already sized in the increments of the grid.

> 
> 14) Sequence: Create dialog, Add Button, Add Button, Delete Button, Delete
> Button --> crashes (consistently)

Not for me.
You may try to identify where it happens. Run Boa with command-line 
param -T until it crashes (try crash it as soon as possible as this 
trace file grows VERY quickly. After crashing restart Boa normally
and while on the Application view of the Boa.py file, select
"Edit -> View tracelog as traceback". This may churn for quite a while
(there are limits you can set in ErrorStack.py for the impatient) and
will then show a traceback of where Boa crashed. 

> 
> 16) Having menus on a "nested" window (i.e. the edit window) instead of at
> the top of the screen is "counter-experiential" (unfamiliar/breaks habits)
> for most GUI users.

That is the way it works ;)
The Editor is the IDE (all menu/toolbar actions apply to the Editor, 
not the Palette). The Palette could conceivably be optionally 
hidden when Boa is used more as an IDE than a GUI builder.
All I can say is please get used to it.

> 
> 17) Having an option to use a single top-level window which always restores
> a "window set" of the IDE would be useful (versus having to click 3 separate
> windows to get "back to Boa").

On windows I think this is possible to do with Activate events. Would
it suffice if the Palette raised the Editor and Inspector when it's
activated?

> 
> 18) Sizer support would be a nice feature.  wxDesigner is cool, but still
> awkward for doing lots of dialogues.

When I can figure out how to integrate Sizers into the current 
architechture I will. In the meanwhile Anchors can cover some of your
layout needs.

> 
> 19) Icon editor or file drag-and-drop or image cut-and-paste would be useful
> for editing icon attributes.

Open for patches/contributions.

> 
> 20) Colour editor should use the "full dialogue" to allow for defining
> non-16-colour palette colours.

Ok done, this was just a setting on the ColourDialog I had to set.
Docs says it should be on by default.

> 
> 21) Colour fields in the inspector should paint themselves the appropriate
> colour or contain the "text" of the colour e.g. FFFFFF or 255,255,255 or
> 1.0,1.0,1.0  (preferably a standardised representation, of course) on the
> colour (text colour = (255 & (colour.Red()+128)), (255 &
> (colour.Green()+128)), (255 & (colour.Blue()+128))).

I agree and have wanted to do this, and in general improve 
property editors, but have not had time yet.

> 
> Okay, must be off now. Keep up the good work and enjoy yourselves,
> Mike

Thanks again for all the feedback!

> 
> __________________________________
>  Mike C. Fletcher
>  Designer, VR Plumber
>  http://members.home.com/mcfletch
> 
> _______________________________________________
> 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] Tab-key in PySourceView

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

Hi Riaan,

Thanks for the reassurance (and the work) :) .

I didn't realise there was a requirement to bind it in PrefsKeys.

As for the long file comment, it was more a "Oh my God, I'll never figure it
out" comment, not a "don't do that" comment.  I'm not a programmer by
profession, so big blocks of code written by someone else always seem
daunting to me :) .  I wanted to know if there's more dragons waiting in the
wings to make me feel inadequate :o) .

Enjoy,
Mike



-----Original Message-----
From: Riaan Booysen [mailto:riaan@e.co.za]
Sent: Saturday, April 07, 2001 16:00
To: Mike C. Fletcher
Cc: Boa Constructor (E-mail)
Subject: Re: [Boa Constr] Tab-key in PySourceView
...
Did you also binf it in PrefsKeys.py ?
I've explained this in my other message, in short; If a key is bound to
an accelerator table, it does not generate further events for the
control.
...
Be fair, it's a 1280 line file (50k), and there 7 source files in the
distribution bigger than 45k.
My usual rule of thumb is to not let a file get longer than 1000 lines,
although there are a few.
...

Re: [Boa Constr] Tab-key in PySourceView

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

Hi Mike, this is a quick note just to let you know I am here but still
busy with the replies to your (and others') previous messages.
I've addressed some of your issues and fixed bugs that have been
reported since the release and hope to post the replies (and CVS)
tonight. I've added tab, shift-tab/indent, dedent support.

"Mike C. Fletcher" wrote:
> 
> Hi all,  looking at the tab-key handler in PySourceView (line 984), it could
> use some enhancements.  These are patterned after the PythonWin interactions
> (IDLE too if I recall), and make the indent/dedent operations with the tab

Idle uses Ctrl-] and Ctrl-[ (Which can't be bound to an accelerator 
table)

> key much more natural feeling.
> 
> My attempts to integrate the changes have failed. I can't seem to get the
> PySourceView to actually use my modified function (so I haven't actually
> tested it to see if it works).  Although the OnKeyDown method appears like
> the correct customisation point, it doesn't actually seem to get called.

Did you also binf it in PrefsKeys.py ?
I've explained this in my other message, in short; If a key is bound to
an accelerator table, it does not generate further events for the
control.

> 
>         tab -- should be translated to an indent command if within the leading
> whitespace of the line and there's no selection
>         shift-tab -- should be translated to a dedent command if within the leading
> whitespace of the line and there's no selection
>         if there is a multi-line selection, then both indent and dedent (tab and
> shift-tab) should operate on the selection.
> 
> Are there a lot of these 2600 line files around?
> Mike

Be fair, it's a 1280 line file (50k), and there 7 source files in the 
distribution bigger than 45k.
My usual rule of thumb is to not let a file get longer than 1000 lines,
although there are a few.

> 
> 8<___________ PySourceView line 984 +
>         # Tabbed indent
>         elif key == 9:
>             print 'tab key'
>             # revised tab semantics mcfletch 2001
>             if event.ShiftDown():
>                 print 'shift down'
>                 # is a dedent request
>                 self.OnDedent(event)
>             else:
>                 # is likely an indent request
>                 # will consider it an ident request if we're actually
>                 # in the indentation section or we have a non-null selection
>                 # set...
>                 # selection set?
>                 start, stop = self.GetSelection()
>                 pos = self.GetCurrentPos()
>                 startPosition =
> self.GetLineStartPos(self.GetLineFromPos(pos))
>                 line = self.GetLineFromPos(pos)
>                 prefix = string.strip(line[:(pos-startPosition)])
>                 def updatePosition( self, position ):
>                     if old_stc:
>                         self.SetCurrentPosition(position)
>                     else:
>                         self.SetSelectionStart(pos + indentLevel)
>                 if (start == stop):
>                     # is a tab-key in the indentation section,
>                     # update the indentation to be one level deeper...
>                     if prefix:
>                         # there is a non-whitespace character in front of
> position,
>                         # insert an actual tab character
>                         self.InsertText(pos, '\t')
>                         updatePosition( self, pos + 1 )
>                     else:
>                         # do an indent by inserting some whitespace
>                         self.InsertText(pos, indentLevel*' ')
>                         updatePosition( self, pos + indentLevel )
>                 else:
>                     # non-null selection set...
>                     self.OnIndent(event)
>             if not self.AutoCompActive(): return
> 
> __________________________________
>  Mike C. Fletcher
>  Designer, VR Plumber
>  http://members.home.com/mcfletch
> 
> _______________________________________________
> 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 Constr] Tab-key in PySourceView

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

Hi all,  looking at the tab-key handler in PySourceView (line 984), it could
use some enhancements.  These are patterned after the PythonWin interactions
(IDLE too if I recall), and make the indent/dedent operations with the tab
key much more natural feeling.

My attempts to integrate the changes have failed. I can't seem to get the
PySourceView to actually use my modified function (so I haven't actually
tested it to see if it works).  Although the OnKeyDown method appears like
the correct customisation point, it doesn't actually seem to get called.

	tab -- should be translated to an indent command if within the leading
whitespace of the line and there's no selection
	shift-tab -- should be translated to a dedent command if within the leading
whitespace of the line and there's no selection
	if there is a multi-line selection, then both indent and dedent (tab and
shift-tab) should operate on the selection.

Are there a lot of these 2600 line files around?
Mike

8<___________ PySourceView line 984 +
        # Tabbed indent
        elif key == 9:
            print 'tab key'
            # revised tab semantics mcfletch 2001
            if event.ShiftDown():
                print 'shift down'
                # is a dedent request
                self.OnDedent(event)
            else:
                # is likely an indent request
                # will consider it an ident request if we're actually
                # in the indentation section or we have a non-null selection
                # set...
                # selection set?
                start, stop = self.GetSelection()
                pos = self.GetCurrentPos()
                startPosition =
self.GetLineStartPos(self.GetLineFromPos(pos))
                line = self.GetLineFromPos(pos)
                prefix = string.strip(line[:(pos-startPosition)])
                def updatePosition( self, position ):
                    if old_stc:
                        self.SetCurrentPosition(position)
                    else:
                        self.SetSelectionStart(pos + indentLevel)
                if (start == stop):
                    # is a tab-key in the indentation section,
                    # update the indentation to be one level deeper...
                    if prefix:
                        # there is a non-whitespace character in front of
position,
                        # insert an actual tab character
                        self.InsertText(pos, '\t')
                        updatePosition( self, pos + 1 )
                    else:
                        # do an indent by inserting some whitespace
                        self.InsertText(pos, indentLevel*' ')
                        updatePosition( self, pos + indentLevel )
                else:
                    # non-null selection set...
                    self.OnIndent(event)
            if not self.AutoCompActive(): return

__________________________________
 Mike C. Fletcher
 Designer, VR Plumber
 http://members.home.com/mcfletch

[Boa Constr] Contrib: makepy dialog for Boa

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

I wanted to play around with Boa as an IDE a little more, so I decided I'd
make a MakePy dialog for it (a Win32COM thing that lets you auto-generate
wrappers for COM controls).  It's slightly more advanced than the dialog in
PythonWin, as it lets you search for libraries.  This isn't particularly
beautiful, but it does seem to work.  Eventually you'd want to create
Design-time controls and options on the design palette for each wrapped
control (maybe even scanning the gen_py directory for controls generated by
other systems), but for now it's just a "tell it to generate a wrapper"
dialog.

Thoughts that have arisen as I worked:
	An option for PythonWin key bindings would be nice (is there a way to
plug-in whole key-binding sets with minimal fuss?).
		Block indent/dedent mapped to tab/shift-tab is very useful
		Block-comment/uncomment mapped to Alt-3, Alt-4 is nice
		Ctrl-G mapped to Goto
	Option for tab-preservation/conversion wasn't immediately obvious in the
interface, possibly in the preferences.
	Tools to tabify/untabify source are needed.
	Auto-complete windows a-la PythonWin are very helpful (for me anyway).
	Might be nice to have an option that makes the "interface" text get wrapped
in _( ) for internationalisation (or whatever the standard is), with the
files generated for translators on the side.
	The trace/error window doesn't appear until the client process completes
and doesn't seem to update if I have to kill the client process.  Makes it
hard to use with mis-behaving apps.
	Option in the inspector to auto-generate shortcuts would be cool.
	Would be good to have option to auto-generate a test-harness application
for dialogs/frames.  See the attached for a simplistic harness.

Module attached, enjoy yourselves,
Mike

__________________________________
 Mike C. Fletcher
 Designer, VR Plumber
 http://members.home.com/mcfletch

[Boa Constr] Impressions and comments...

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

Hi all,

I've been playing with Boa (from the CVS) for a few days now, working on
building a whole slew of dialogues for a wxPython app I'm behind on.
Overall I'm impressed.  The dialogue building is going well, and it's saving
me some serious time.  The following is a list of the nits I've run across
so far.  I'm using Boa primarily as a GUI layout system, rather than as an
actual IDE, so most comments will focus on the design window.

1) Need a way to specify a particular ID for a given button (particularly
need wxID_OK and wxID_CANCEL so that we can get automatic OK/Cancel
behaviour in dialogues.  Potentially include OK/Cancel buttons explicitly in
the buttons toolbar as well (still need the ability to specify).

2) Inspector's Event Handler Definition needs ability to specify a
non-default name for the method

3) Inspector's "checkmark to expand options" is not intuitive, possibly use
an owner-drawn icon instead?

4) Option for auto-expansion of the editing window when not showing the
designer would help with editing.  Would likely require adding the "new"
toolbar as a menu in the editor.  Alternate window layouts with, for
instance, a "design window" set and a "code editing" set might be useful.

5) Would be nice to have drag-and-drop functionality for the widgets.  (i.e.
drag from the toolbar to the design window).

6) How do you add new items to the list of available widgets (sub-classes,
entirely new classes, etceteras)?

7) For a text control, altering "label" in the properties panel changes the
control value, but doesn't alter the "value" attribute in the construction
panel. (Reverse does work).

8) I couldn't find a "test dialog" function anywhere, i.e. run the dialog
using run-time controls and report each event/call/etceteras generated by
user interactions.  Not sure if I just missed it, but it's a really useful
feature for figuring out what's going on.

9) Events panel of the inspector should likely use something other than
"small list" style.  Because the names are touching the edges it looks as
though scrolling only lets you see the "Event" text rather than showing
entirely new event classes.  A downward-scrolling list gives a better "feel"
that there's more items to see.

10) Default editor font for windows is very large on my machine, not sure
why that is, I'm running a 1152x864 resolution, font looks to be about 15 or
16 point.  It's changeable, of course, but a smaller default might be
reasonable.

11) A wxWindow option should be available in the Containers/Layout toolbar.
(Or see #6)

12) Could really use "nudge" key bindings for the design window.  i.e. the
arrow keys nudge the selection 1 pixel or grid-point in their appropriate
direction.

13) Would suggest that when grid mode is on that new items be sized in
increments of the grid

14) Sequence: Create dialog, Add Button, Add Button, Delete Button, Delete
Button --> crashes (consistently)

16) Having menus on a "nested" window (i.e. the edit window) instead of at
the top of the screen is "counter-experiential" (unfamiliar/breaks habits)
for most GUI users.

17) Having an option to use a single top-level window which always restores
a "window set" of the IDE would be useful (versus having to click 3 separate
windows to get "back to Boa").

18) Sizer support would be a nice feature.  wxDesigner is cool, but still
awkward for doing lots of dialogues.

19) Icon editor or file drag-and-drop or image cut-and-paste would be useful
for editing icon attributes.

20) Colour editor should use the "full dialogue" to allow for defining
non-16-colour palette colours.

21) Colour fields in the inspector should paint themselves the appropriate
colour or contain the "text" of the colour e.g. FFFFFF or 255,255,255 or
1.0,1.0,1.0  (preferably a standardised representation, of course) on the
colour (text colour = (255 & (colour.Red()+128)), (255 &
(colour.Green()+128)), (255 & (colour.Blue()+128))).

Okay, must be off now. Keep up the good work and enjoy yourselves,
Mike

__________________________________
 Mike C. Fletcher
 Designer, VR Plumber
 http://members.home.com/mcfletch

[Boa Constr] Re: [wxpython-users] ANNOUNCE: Boa Constructor 0.0.5 (Corrupt zip file?)

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

Hi Rob, 

Thanks making this accesible, luckily I checked my email before leaving, 
I've uploaded the Zip file again and tested it this time.

Rob Cakebread wrote:
> 
>  It appears that the zip file on the official Boa site is corrupt.
>  Since the author is gone for two weeks, I went to CVS and
> made a tar.gz of it.
> 
>  You can get it at http://wxpython-pit.sourceforge.net

Could you point your link point back to 
http://sourceforge.net/project/showfiles.php?group_id=1909

> 
>   Rob Cakebread
> 
> On Monday 19 March 2001 09:41 am, you wrote:
> > Hello everybody,
> >
> > Boa Constructor 0.0.5 is ready for download.
> > Major changes:
> > * New Explorer supporting many 'data sources' (File, FTP, CVS, Zope,
> > SSH)
> >   * Better Zope support including Cut, copy, paste, rename, delete,
> >     import, export, creation and property management
> > * Many Frame Designer and Object Inspector improvements
> >   * Multiple select
> >   * Cut, copy & paste of controls
> >   * Anchors for window layout
> > * Detailed getting started guide and tutorial
> > * Loads of bug fixes
> >
> > Needs wxPython 2.2.5
> >
> > Thanks to the following people who have helped out since the previous
> > release: Kevin Gill, Shane Hathaway, Robert Boulanger and Kevin Light.
> >
> > Get it from http://boa-constructor.sourceforge.net
> >
> > I will be back in two weeks, in the meanwhile please direct bug reports
> > to the SourceForge facilities or email me directy.
> > If you get an error or a crash please report it.
> >
> > Enjoy!
> 
> _______________________________________________
> wxpython-users mailing list
> wxp...@li...
> http://lists.wxwindows.org/mailman/listinfo/wxpython-users

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

[Boa Constr] ANNOUNCE: Boa Constructor 0.0.5 - GUI building IDE for wxPython

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

Hello everybody,

Boa Constructor 0.0.5 is ready for download.
Major changes:
* New Explorer supporting many 'data sources' (File, FTP, CVS, Zope,
SSH)
  * Better Zope support including Cut, copy, paste, rename, delete, 
    import, export, creation and property management
* Many Frame Designer and Object Inspector improvements
  * Multiple select
  * Cut, copy & paste of controls
  * Anchors for window layout
* Detailed getting started guide and tutorial
* Loads of bug fixes

Needs wxPython 2.2.5

Thanks to the following people who have helped out since the previous
release: Kevin Gill, Shane Hathaway, Robert Boulanger and Kevin Light.

Get it from http://boa-constructor.sourceforge.net

I will be back in two weeks, in the meanwhile please direct bug reports
to the SourceForge facilities or email me directy.
If you get an error or a crash please report it.

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

Re: [Boa Constr] Getting started

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

Hello,

"C. Porter Bassett" wrote:
> 
> Does the release version of Boa work with wxPython 2.2.5, or just the CVS
> version?
> 

Just the CVS version, the release version needs 2.2.1, Python 1.5.2.

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

[Boa Constr] Email problems

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

Hello everybody, 

I'm having trouble receiving email from some places on the net. 
DNS problems. SourceForge can deliver mail to me so if you need to
reach me, send to ri...@us... for now.

This should be cleared up soon.

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

RE: [Boa Constr] Getting started

[C. P. B. <po...@et...>]

Does the release version of Boa work with wxPython 2.2.5, or just the CVS
version?

--------------------------------------------------------------------------
C. Porter Bassett     po...@et...   http://www.cporterbassett.com
--------------------------------------------------------------------------
"Pretend like this is a really witty saying." - Anonymous
--------------------------------------------------------------------------

On Thu, 15 Feb 2001, Charlie Derr wrote:

> 
> 
> |-----Original Message-----
> |From: boa...@li...
> |[mailto:boa...@li...]On Behalf Of
> |C. Porter Bassett
> |Sent: Thursday, February 15, 2001 11:23 AM
> |To: boa...@li...
> |Subject: [Boa Constr] Getting started
> |
> |
> |Boa constructor looks interesting, and I would like to check it out.  I
> |couldn't get it working with python 2.0 and wxPython 2.2.2.  I tried to
> |get wxPython 2.2.1 working with python 2.0, but I didn't get that
> |working either.  I he latest version of Boa from the CVS.  Yet again, I
> |failed.
> |
> |Could you help me get the latest from CVS?  This is what I type:
> |cvs
> |-d:pserver:ano...@cv...:/cvsroot/b
> |oa-constructor login
> |
> |When it asks for a password, I hit Enter, just like the instructions
> |say.  When I do that, I am immediately booted back to the command prompt.
> 
> 
> That's fine.   This is what is supposed to happen.  After being booted back
> to the command prompt, simply enter the next instruction and your checkout
> should begin:
> 
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/bo
> a-constructor co boa
> 
> 
> If after getting the cvs version, you still don't have success running boa,
> I would recommend getting wxPython 2.2.5
> 
> 	good luck,
> 		~c
> 
> 
> 
> 
> |--------------------------------------------------------------------------
> |C. Porter Bassett     po...@et...   http://www.cporterbassett.com
> |--------------------------------------------------------------------------
> |"Pretend like this is a really witty saying." - Anonymous
> |--------------------------------------------------------------------------
> |
> |
> |
> |_______________________________________________
> |Boa-constructor-users mailing list
> |Boa...@li...
> |http://lists.sourceforge.net/lists/listinfo/boa-constructor-users
> 

RE: [Boa Constr] Getting started

[Charlie D. <ch...@we...>]

|-----Original Message-----
|From: boa...@li...
|[mailto:boa...@li...]On Behalf Of
|C. Porter Bassett
|Sent: Thursday, February 15, 2001 11:23 AM
|To: boa...@li...
|Subject: [Boa Constr] Getting started
|
|
|Boa constructor looks interesting, and I would like to check it out.  I
|couldn't get it working with python 2.0 and wxPython 2.2.2.  I tried to
|get wxPython 2.2.1 working with python 2.0, but I didn't get that
|working either.  I he latest version of Boa from the CVS.  Yet again, I
|failed.
|
|Could you help me get the latest from CVS?  This is what I type:
|cvs
|-d:pserver:ano...@cv...:/cvsroot/b
|oa-constructor login
|
|When it asks for a password, I hit Enter, just like the instructions
|say.  When I do that, I am immediately booted back to the command prompt.


That's fine.   This is what is supposed to happen.  After being booted back
to the command prompt, simply enter the next instruction and your checkout
should begin:

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/bo
a-constructor co boa


If after getting the cvs version, you still don't have success running boa,
I would recommend getting wxPython 2.2.5

	good luck,
		~c




|--------------------------------------------------------------------------
|C. Porter Bassett     po...@et...   http://www.cporterbassett.com
|--------------------------------------------------------------------------
|"Pretend like this is a really witty saying." - Anonymous
|--------------------------------------------------------------------------
|
|
|
|_______________________________________________
|Boa-constructor-users mailing list
|Boa...@li...
|http://lists.sourceforge.net/lists/listinfo/boa-constructor-users