Re: [Boa Constr] first impressions of Boa 0.1.0

[Hans-Peter J. <hp...@ur...>]

On Tuesday, 5. February 2002 18:42, Riaan Booysen wrote:
> Hello Hans-Peter,
>
[...]
> >
> > Next, I configured boa to my needs. I discovered, that boa uses DOS
> > linebreaks :-( Fortunately I found the autoReindent option, which fixed
> > this for me :-)
>
> I plan to address this with the next release.

Nice..

> > To fulfil my basic basic code form needs, I would like to see an option
> > to use tabs for indention. I found some corresponding STC options, but
> > they don't affect code generation and lead to indention errors, when
> > activated  :-(
>
> I'll look into this.
>
> > Some random findings:
> >  - X clipboard doesn't work in the editor (at least). :-(((
>
> I use wxPython's wxClipboard, it works for me. Did you try from
> the right-click menu in the Designer, or did you try some special
> keystroke?

All of them... I often select some strings somewhere (xterms, vi sessions).
The most X-like behavior have wxTextCtrls: if you select text there with
the mouse, it gets propagated to the X clipboard. Sellections in the editor
gets never there, but are available after Ctrl-C in other edit sessions or
wxTextCtrls. This is disturbing: to quote some examples (see font problem, 
below), I've to use some other tool :-( Really bad is: in the html help 
window, text isn't selectable, and you can only copy the whole help page.

> >  - when editing a string in Designer->Inspector, <Return> doesn't stop
> > that, and posting will loose it's modified content. I need to select
> > another prop to get the former prop modified.
>
> <Return> is supposed to post, but I'm still having problems with
> wxAcceleratorTable under wxGTK :(
>
> >  - Setting font properties in Designer works as expected, but font face
> > gets lost on runtime.
>
> Does the generated source dissapear, or does it not have an effect at
> runtime?

The latter:

self.staticText1 = wxStaticText(id = wxID_WXFRAME1STATICTEXT1, label = 
'Erster Test', name = 'staticText1', parent = self, pos = wxPoint(16, 24), 
size = wxSize(102, 27), style = 2)
self.staticText1.SetFont(wxFont(20, wxSWISS, wxNORMAL, wxNORMAL, false, 
'aachen bt'))

Robin, does using different fonts require a special init? (like images)

> >  - posting buttons doesn't allways work. Closing frame helps.
>
> How do you post a button?
> Only the whole session is posted or canceled.

Sorry for beeing too vague, read: posting designer sessions ... 
closing designer window helps.

> >  - grayout (aka. blueout) results in ramdom char coloring (looks very
> > strange)
>
> This should be off by default on wxGTK.
>
> >  - Modifying MajorDimension in RadioBoxes results in crash on post.
>
> I'll look into it.
>
> >  - Setting wxRA_SPECIFY_ROWS on them is ignored.
>
> Remember when setting constructor properties, the control (or the Frame)
> have to be recreated before the changes take effect (as constructors
> are only called at creation)
>
> > Some future thoughts:
> >  - STC background coloring of 'danger' and 'good' zones (It took me a
> > couple of times to find the proper place where self.timer1.Start(500)
> > didn't get lost after designer sessions)
>
> This is noted in a few place in the help files, please read thru them.
> Quick rule: Leave _init_* methods alone!

I red them. I wouldn't had come so far without. It's just an idea.

> >  - Real i18n support
>
> Yip, I am planning some, for now see Examples/il8n.py

I have, and that was the reason for writing this.

AFAICS, it takes some initialisation stuff, and enclosing strings with 
i18n(). I would vote for a new wxI18nApp model.

> >  - Some grid helpers (generic database interface)
> >
> > Last thing points you in the direction, I have to go now for my next
> > project, and I'm willing to give boa a try for that.
> >
> > I would love to see the boa CVS activity rising.
>
> Don't worry it's usually not this quiet, hopefully I'll get round to
> updating CVS this week, after that fixes and changes should go in
> regularly.

Cheers,
  Hans-Peter