I code everything Python by hand and just don't like GUI tools for
development work – at the moment I'm working on a Delphi application
for a customer, and I hate it ;-) I get accustomed to Delphi's GUI
tools, though, but often switch to the code view of forms, e.g. I can
use search replace
Użytkownik Jeff Johnson napisał:
91). The sizers make for a very professional form, too. I would like
to know why some of you code your own forms by hand.
Because there are still plenty of bugs in it, e.g.:
Traceback (most recent call last):
File
2010/1/21 Jacek Kałucki lab...@rz.onet.pl
Użytkownik Jeff Johnson napisał:
91). The sizers make for a very professional form, too. I would like
to know why some of you code your own forms by hand.
Mostly because of the level of control. It allows dynamic and conditional
creation of
John wrote:
On Wednesday 20 January 2010 05:52:58 pm Jeff Johnson wrote:
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put together a great form in a short period of time and the
property
On Thursday 21 January 2010 06:34:01 am Jeff Johnson wrote:
John wrote:
On Wednesday 20 January 2010 05:52:58 pm Jeff Johnson wrote:
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put
On Thursday 21 January 2010 01:24:23 am Jacek Kałucki wrote:
File c:\SVN\dabodev\ide\ClassDesignerComponents.py, line 49, in
getDesignerDict
if os.path.exists(clsPath):
File C:\Python25\lib\ntpath.py, line 255, in exists
st = os.stat(path)
TypeError: coercing to Unicode: need
John wrote:
John: Can you give me some examples of the flexibility you mentioned?
Sure, I find myself using many custom controls and needing custom layouts.
And then there are the client change orders - I find it difficult to add
controls and move others around using ClassDesigner.
On Jan 21, 2010, at 11:39 AM, Jeff Johnson wrote:
I haven't looked into this deeply, but my first glance is that it is not
easy to take a cdxml form and convert it to a hand coded form.
That was never the design goal for the Class Designer. The two are not
interchangeable.
-- Ed
John wrote:
I'm not sure I'd call the traceback a ClassDesigner bug. Almost all the path
issues that have been reported turn out to be user errors - at least that's
what I recall. Such as the user does not understand the Dabo structure or
the user saves the cdxml file completely out of
-Original Message-
From: Ed Leafe e...@leafe.com
To: Dabo Users list dabo-users@leafe.com
Sent: Thu, Jan 21, 2010 11:38 am
Subject: Re: [dabo-users] cdxml vs. coding
On Jan 21, 2010, at 11:39 AM, Jeff Johnson wrote:
I haven't looked into this deeply, but my first glance
On Jan 21, 2010, at 12:21 PM, jpoorra...@aol.com wrote:
That was never the design goal for the Class Designer. The two are not
nterchangeable.
- Ed Leafe
ut how does the cdxml file run in dabo? It must be converted into python
code at some point, right? Couldn't we see that?
Ed Leafe wrote:
On Jan 21, 2010, at 11:39 AM, Jeff Johnson wrote:
I haven't looked into this deeply, but my first glance is that it is not
easy to take a cdxml form and convert it to a hand coded form.
That was never the design goal for the Class Designer. The two are not
Użytkownik John napisał:
I'm not sure I'd call the traceback a ClassDesigner bug. Almost all the path
issues that have been reported turn out to be user errors - at least that's
what I recall. Such as the user does not understand the Dabo structure or
the user saves the cdxml file completely
On Jan 21, 2010, at 1:34 PM, Jeff Johnson wrote:
I figured as much, but as a FoxPro guy the class designer is awesome.
For most people who develop desktop UIs, a WYSIWYG tool is essential;
we'll never get Dabo into general acceptance without a good one. A proper IDE
that has the
When we started Dabo, I already had projects on my plate for which I needed the
library. So initial coding of the library was refactoring pieces of this and
that I'd
saved elsewhere for specific needs.
The class designer as you see it now is at least the second complete rewrite,
and was
On Jan 21, 2010, at 2:45 PM, Paul McNett wrote:
Also, I feel at home with the toolkit I've developed over the years, and my
code/test
cycle is very fast. I never have a .py file open without saving for more than
a few
minutes, and vim keeps a backup file around in case my computer
Ed Leafe wrote:
On Jan 21, 2010, at 1:34 PM, Jeff Johnson wrote:
I figured as much, but as a FoxPro guy the class designer is awesome.
For most people who develop desktop UIs, a WYSIWYG tool is essential;
we'll never get Dabo into general acceptance without a good one. A proper
Ed Leafe wrote:
On Jan 21, 2010, at 2:45 PM, Paul McNett wrote:
Also, I feel at home with the toolkit I've developed over the years, and my
code/test
cycle is very fast. I never have a .py file open without saving for more
than a few
minutes, and vim keeps a backup file around in case
Ed Leafe wrote:
On Jan 21, 2010, at 2:45 PM, Paul McNett wrote:
Also, I feel at home with the toolkit I've developed over the years, and my
code/test
cycle is very fast. I never have a .py file open without saving for more
than a few
minutes, and vim keeps a backup file around in case
Jeff Johnson wrote:
Ed Paul: I really think that the VFP folks will love the class
designer. It is so VFP! I am maybe a little bit different then the
norm. I have a UI and then I do some things that the UI won't
necessarily support. I really like the class designer and that is what
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put together a great form in a short period of time and the
property sheet, object view, code editor are better than VFP by a long
shot (in my
On Jan 20, 2010, at 8:52 PM, Jeff Johnson wrote:
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put together a great form in a short period of time and the
property sheet, object view,
Ed Leafe wrote:
On Jan 20, 2010, at 8:52 PM, Jeff Johnson wrote:
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put together a great form in a short period of time and the
property
On Wednesday 20 January 2010 05:52:58 pm Jeff Johnson wrote:
I have heard some folks saying that they code their own forms. After
working with the class designer I feel that it is even better than VFP.
I can put together a great form in a short period of time and the
property sheet, object
On Wed, Jan 20, 2010 at 22:29, Jeff Johnson j...@dcsoftware.com wrote:
Ed: I was one of those guys. Maybe that's why I asked the question. I
am totally impressed with the job you guys have done. The class
designer is a powerful, reliable and intuitive tool to use. We won't
even mention
25 matches
Mail list logo
