On Nov 27, 2006, at 5:42 AM, Pedro Gato wrote:
> - Has anyone used dabo in a real-world app, screenshots, demos, URLs??
I know that Paul is working one one for a client, but I don't know
whether he can reveal much of it. We've been contacted for support by
several people in various industries who are using Dabo for their
businesses, but I can't give you more specifics than that. Perhaps
one or two of them may come forward and respond if they are on this
list. I'm still looking for that first paid Dabo client, but until
then I've re-written all of my internal apps for managing the MySQL
databases on my server in Dabo.
But I think that an equally good demonstration of what Dabo can do
is the fact that all of the Dabo tools, such as the Class Designer,
are written in Dabo! There are no external libraries or specialized C
code anywhere; it's 100% Dabo.
> - Can i change the default menubar??
Sure; it's as simple as myForm.MenuBar = MyCustomMenuBar. Or you
could add and remove items from the default menu bar as needed.
Right now you have to create menus in code. I'm working on a
MenuDesigner tool that will allow you to create the menus visually.
> - Is fieldspeceditor deprecated?? what replaced it??
The fieldspec format, as well as its editor, are deprecated. They
were an early attempt to come up with a standardized XML format for
storing application information, but suffered from too many
limitations. For one, it is completely dependent on the datanav
subframework used by the AppWizard, and we wanted something that was
more general-purpose.
What replaced it is twofold: for AppWizard-generated apps, it was
replaced by generated code. Still not optimal, but not as confusing
to Python developers who were new to Dabo. For the XML format used
for storing UI information, it was replaced by the .cdxml format used
by the Class Designer.
We'd eventually like to have the AppWizard create .cdxml files as
its output, so that you could use the Class Designer to edit them.
But that will require a major re-write of the datanav framework, so
it probably won't happen in the immediate future.
> - Can the Select/Edit/Browse Forms be costumized?? Using
> classDesigner??
They can be customized, but only with a text editor. They are
standard Python/Dabo .py code files, stored in the 'ui' folder of the
generated app.
> - Can we drop down to wxpython if needed?
Yes. There is nothing that would stop you from using wxPython code
and objects if needed. You would be limited to doing this in code,
since the visual tools are designed to work with Dabo objects. You
would also need to rely on wxPython events instead of the Dabo event
model.
And I would ask that if you find some place where you feel the need
to use wxPython, please post a note here explaining the problem.
Either there is a way to do it in Dabo that is just not obvious, as
we don't follow wxPython naming all the time, or perhaps it is a part
of wxPython that we have not yet wrapped. In the latter case it is
very likely that we could come up with a Dabo wrapper in a very short
period of time.
> - How mature is the framework??
Dabo is actually two distinct entities: the framework itself, and
the visual tools designed to make developing with the framework easier.
The framework is very mature, and has not changed significantly in
the last two years. Aside from a few bugfixes, most of the change has
been in the UI layer, where we have added several new controls, and
enhanced the API.
The visual tools are still a work in progress, though. I think of
them as extremely complex Dabo applications, and I'm not done
creating them yet. I still find things that I want to add to the
Class Designer, for example, or places where some features are not
fully implemented. Over the past few months I retro-fitted support
for non-sizer-based designs into what had previously been a sizer-
only tool, and there are still some kinks that need to be worked out
with that. There are also some tools that need to be created, such as
the Menu Designer mentioned above. Once they are completed, we want
to tie them all together into a single IDE that will allow you to
develop and manage all the parts of your application. That goal is
still a long ways off, but it guides the way we develop the tools today.
> requirements i'm going to use PostgreSQL, is it stable on dabo??
PostgreSQL support is very stable on Dabo. We use the psycopg2
database adapter for dbapi access to Postgres, so our stability is
basically the same as psycopg2.
> P.S: Sorry for my english, i'm portuguese...
Your English is fine. And you never have to apologize for your
English to someone who can't speak or write in anything *but*
English! ;-)
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
