Hi there-

here's my current list/notes of issues/bugs/oddities/misunderstandings 
I've come across so far.

Let me know what are misunderstandings, and the rest I'll add to the bug 
tracker over the weekend.

Regards

Julian

* CnxEditor fails to start if connection created in ClassEditor has ' in 
description
* dshell on mac- ctrl c/v for paste
* mac: object properties (and/or other windows?) don't honour display bounds
   eg after being displayed on a bigger display, then restart on smaller 
display, object window
   started at last co-ordinates, which are off-screen on smaller display.
   Work-around: from menu, maximise (which honours current display 
bounds), then resize.
* can't delete grid sizer via rmb on form mock-up pane.
   Workaround: delete via object properties window
* When nothing selected, outline of latest widget redraws like mad with 
a black box,
   slowing everything down.
   Workaround: click on any widget in form mock-up
* wxPython 2.8.8.0- code editor crashes on startup
* Error messages- go to stdout/stderr of terminal, rather than being 
displayed in a form.
   This is confusing:
   - is it my app, or the tool that's having problems
   - different than when you 'run' your form and bring up the dShell, 
where errors/output, etc
     are displayed as part of the dShell form.
* Autoadds KeyField definition for bizObj even if no PK in table (good),
   but should add a comment that this needs to be defined.
   (I'm no db expert, but even I recognise it's better to have a PK... 
but I didn't design the
   db I have to work with ;-) )
* Suggestion: run should really run the form as a new subprocess/clean 
interpreter.
   Some initial confusion (and I'm sure later bugs) were caused/hidden 
because things were
   defined/created by the ClassEditor in the running interpreter instance.
   These errors would be clear if 'run' used a clean/new interpreter 
instance
* ClassEditor: if you select a method, it adds "def xxxx(self):" in the 
editor; if you
   change the text in anyway (even delete everything except the def 
line, ie return it
   back to what it started with) it will cause the code autogenerator to 
include the text.
   This leads to 'invalid indentation' errors when you run the form, 
which are not at all
   clear to understand where they're coming from to start with.
   I think on save/run, any methods that are flagged as user edited, but 
contain only the
   auto-generated 'def xxxx(self):' line + whitespace should be 
automatically removed.
* form.showmodal()
   -should throw exception until supported by underlying wxPython
   -currently 'looks like' it's working, but doesn't stop event 
processing for the rest
    of the app; now know this is documented on the wiki, but it's not 
obvious when
    you're in an editor ;-)
* Help/documentation
   -could include static copy of wiki docs (e.g. captured via wget)
   -api doc generated with something like epydoc with graphviz
   -in ClassEditor help- introspect dabo libraries and present doc 
strings in a tree
    widget-like thing?
* Better code round-trip support with external editors
   -include needed/used imports in the generated code (so editors can 
auto-complete
    based on imports.)
   -would be useful if generated code from form was runnable, without 
needing extra
    wrapper script.  e.g. dApp instance is in wrapper, so again, editors 
can't do
    full autocompletion
   -dabo editor should detect when the code file has been changed by an 
external editor,
    and ask the user if it should be reloaded.  Also, should be possible 
to save class ui
    data seperately from code.  Eg so class editor can be used to tweak 
ui positioning, labels,
    etc, and an external editor can be more easily integrated.
* Some documentation re what can be saved as a re-useable custom class, 
what can't
   (eg forms can't, panels can,...), and if the custom class is created 
with code, if
   that code will be also be imported when inserted into another form (I 
believe not?),
   and if it is, wheiter edits are local to this instance, or affect all 
instances in
   the application into which it's inserted.
* Insert from DE in Class Editor- would be nice to have an 'insert in 
table order'
   option, not just alpha-order
* dialog classes- confusing to have both show and Show methods
* Sizers in class editor- after deleting content from a slot, keeps size 
of last
   contents.  Might be better if it repacked/redistributed the sizes.


_______________________________________________
Post Messages to: Dabo-users@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users

Reply via email to