On Dec 16, 2007, at 8:01 PM, Adrian Klaver wrote:
>> Maybe if Paul is reading this we might reopen the question of
>> automatically adding a panel to forms in either Dabo itself, or just
>> in the Class Designer. Thoughts?
>
> My vote is to add the panel, on the principal of least surprise. I
> think most
> folks assume a form will allow tabbing between fields by default.
Yes, but there is the alternate "surprise" of adding a control
directly to a form, but having the actual path at runtime be
form.panel.control. That was the main objection at the time, as I
recall.
> Is there a way to slide a Panel in under the existing controls by
> modifying
> the *.cdxml file?
It's not just a panel; it's a panel and a sizer. And sure, if you
can keep the XML straight, you can certainly do that manually.
> Another question.
> While investigating Panel behavior I ran across something I have
> yet to figure
> out. I used Johns bizobj app to do some testing. In order to make
> it work on
> my machine I changed the *.cnxml file. I found if I ran the app
> from the same
> directory (~/some_dir/python app.py) as the cnxml file the
> directory path was
> added to the the database name and the connection failed. If I did
> cd .. and
> then ran the app (~/higher_dir/python some_dir/app.py) everything
> worked.
> Suggestions are welcome.
Paths are stored relative to the home directory of the app.
Apparently the demo .cnxml was created one level down from the main
app. That is one of the reasons we stress using a standard directory
structure for Dabo apps, such as the one that is created for you when
you run dabo.quickStart().
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
