On Feb 27, 2007, at 7:02 PM, Michael Hipp wrote:
> Questions:
>
> - How difficult will it be to begin using Dabo incrementally in my
> existing
> wxPython/Psycopg/PostgreSQL application? Or am I facing a "whole
> hog" rewrite?
As others have noted, you don't need to scrap everything. You will
need to use Dabo's dApp class for your application object, since that
is used as a mediator of a lot of other events, but since that is a
subclass of the wxPython app object, the rest of your stuff should
work fine.
Dabo supports PostgreSQL/psycopg, so that should be no problem at all.
> - What does Dabo use to do printing? I know it uses ReportLab for
> "reports",
> but what about single sheet receipts and things that need to
> automatically
> print under program control (hopefully with no help from Adobe
> Reader)?
This is still uncharted territory, mainly because nobody has looked
into it yet. I suppose we would take what wxPython uses and perhaps
clean it up a bit, but until then, you still have the full wxPython
printing mechanism available to you.
> - Is Dabo MVC? Any thoughts on how hard it might be to wedge Dabo
> into my
> MVCish layout?
Dabo is a 3-tier design, but is *not* strict MVC. In our design, the
UI talks to the bizobj, period. It never addresses the data tier
(model) directly. The data tier likewise only 'talks' to the business
logic layer; it never addresses the UI layer directly. If you were to
diagram the two:
Dabo:
User --> UI <--> bizobj <--> data
MVC:
I can't draw it in text, but this image shows the difference:
http://osteele.com/images/mvc/mvc.png
The main difference is that in MVC, the model can talk directly to
the view without going through the controller. This is not the way 3-
tier design works. It shouldn't be too much of a stretch to switch
between the two, but they aren't 1:1 interchangeable.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
