1. Re: win32lib: IDE bug fix
Judith Evans wrote:
> David, would you clime in with your preferences
> on the one-screen, full-screen approach? I know
> you want one-screen, but would you like full-screen
> or something like you used before I got my hands on it?
I think the closer it is to VB (within reason), the better.
Imitating removes a lot of questions, like how controls should behave during
design mode. Is there and issue about how a TabControl should work? Look at
VB. Need an icon for the control palette? Snag one from VB. That means that
you can concentrate on the code.
People looking for a replacement for VB will obviously be happy with the
choice, since it presents one less hurdle on the learning curve to get
master. And it answers 'What real applications have been written in VB?',
because you can just point to the IDE.
Like it or not, the VB interface is standard, copied widely, and considered
what a 'professional' interface is supposed to look like. Why go a different
direction if you are only going to get flack on every point you differ from
VB?
OK, end of sidebar. If you don't have a copy of VB, I can probably find some
screenshots on the internet to point you to. I don't have a copy of VB, but
I have a couple of books on the latest release, and I can always refer to VB
for Word for some look and feel issues. I'm sure some other people could
also help with questions.
Writing a complete VB IDE clone is a lot of work! If you can get the tasks
split up (for example, one person working on the Design window, another
working on the Code Edit window) would be great. I think that a control with
auto-complete, code hints and syntax coloring would be a *great* as a
stand-alone project, which is why I had written the editor section to be
stand-alone. It sounds like people are exploring using the Rich Text control
to do just that, which would be great - the less 'custom' controls there
are, the better.
Finally, a direct answer to the question. The latest version of VB puts
everything into a single window, which *optionally* can be maximized to fill
the screen. Real estate is divided into sections. On the left hand side is
the toolbar palette. In the middle is the design window. The right hand side
is divided into three parts. On the top is the 'Project' tree control, which
lists the components, starting from the project, and going down to the
controls in each form. In the middle is the 'Properties' list, which lists
the properties for the control that has current focus. It's placed in a tab
control, so you can see properties grouped by function, or in alpha order.
On the bottom is a monitor visualizer, so you can see how your window will
look in a full-screen.
Did this answer the question?
-- David Cuny
