Re: [Boa Constr] ZOA.zexp can't be imported?

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

Hello Hans-Peter,

Hans-Peter Jansen wrote:
> 
> On Tuesday, 5. March 2002 19:48, Riaan Booysen wrote:
> > Hi Brian,
> >
> > Brian Wisti wrote:
> > > Hi all,
> > >
> > > I just installed Boa 0.1.0 yesterday, and I must say that I am _very_
> > > impressed.  This is one awesome development environment, and I can't
> > > wait to see it develop further!
> >
> > Thanks!
> > Which areas would you like to see developing further?
> 
> Let me jump into this question. By now, I'm using boa on a daily basis:
> 
> One of my most missing functions is moving a group of selected objects
> by an numeric offset.

Currently you can move around a group of selected objects in 1 pixel
increments by holding down control and using the cursor keys.
There is a bug with wxAcceleratorTables on wxGTK which breaks this
for you, but it works on Windows.
Try rebinding the keys under Preferences-Key bindings-Designer-Move*

You may also set the Designer grid to a lower granularity for
moving multiple selected objects with higher precision.
See Preferences-General-Designer-dsGridSize.

> 
> BTW: Right now, after selecting multiple objects and deselecting them
> in a designer session, the handles of single selected objects are drawn
> in background color thereafter. See attached screen shot. The first
> control is selected. Disturbing...

This is probably a repaint problem. Try to determine if the tags 
are actually the wrong colour or if they are just not updated properly.

> Source formatting: Breaking long lines into a more editor friendly
> format (say 100 columns).

It's on the todo (properly handling multiple lines)
For me the priority is not that high as I see the generated code almost
as a resource, something you *usually* don't maintain manually.

> 
> I18n: the possibility to wrap all strings in i18n().

Maybe support for the gettext.py convention of using _(string) 
would be simplest (I think this has been suggested before)

However there is a more general issue involved; Giving property editors
more state, and how to manage it through the Inspector.
Already property editors support the additional state of being linked
to special frame attributes.

A more specific solution would be to add a new specialised property 
editor dialog for strings with a checkbox for when the string should
be _(gettext) wrapped. It could even possibly add the gettext import
statement and _ binding when it's checked.

> 
> Riaan, if you can give me some hints & thoughts, where to start,
> I'm going to look into them...
> 
> > HTH,
> > Riaan.
> 
> Cheers,
>   Hans-Peter
> 

Riaan.