🚀 go-pugleaf

In article <1992Nov15.022508.252@panix.com> rryan@panix.com (Rob Ryan) writes:

| In <BxoA25.KrJ@usenet.ucs.indiana.edu> ezachris@cochiti.ucs.indiana.edu writes:
| 
| >I have Turbo C++ 3.1 for Windows with OWL and the Resource Workshop.
| >
| >Borland's offering the ProtoGen code generator for $49.90.
| >Does anybody know anything about this?
| >Is it worth the fifty bucks?
| 
| Not in my opinion.  It lets you connect menus w/ dialogs, but that's
| about it.  I have v2.0 (I ordered it when I got tcwin v3.0) and it
| only does the rudimentary processing that's easy to do anyway.
| Perhaps the latest version (if v2.0 isn't the latest version) added
| lots of functionality, but v2.0 isn't worth it.  And it definitely
| isn't worth the $495 that they claim it it's worth.

I have just begun using it and I find that it does one thing well,
which is to set up a framework for you. But an experienced C++
programmer probably already has several applications to provide the
framework for the next application.

I found what may be a bug (but still might be my misuse of the
package.) I painted a dialog to serve as the main window for a small
test application and the application code that Protogen generated did
not successfully run. I received the classic error -5 indicating that
the dialog window could not be created.

After much fumbling around I looked at the calc sample application
that comes with application frameworks and found that Protogen does
not appear to use the dialog name correctly in the handling of the
dialog window.

Anyway, I changed the code by hand to match calc's mechanism, which
only took a couple of minutes, and everything worked fine. I went into
a second directory and, using everything I had learned about the
naming conventions to use for the icon and dialog, I regenerated a
fresh application. It still failed, so I don't think Protogen (version
2.2) handles dialog boxes as main windows all that well.

That said, I think it is a decent tool for those who are brand new to
C++ and need a frame work to get over the learning hump for those
first few apps. It may be worth the $49 in saved time alone. It may
also help for those apps which have a huge number of linked dialogs.
It will generate all the useful routines to handle the controls and
that can be pretty useful.
--
Kim Letkeman	kim@Software.Mitel.COM

In article <KIM.92Nov16092705@kim.Software.Mitel.COM> kim@Software.Mitel.COM (Kim Letkeman) writes:
>In article <1992Nov15.022508.252@panix.com> rryan@panix.com (Rob Ryan) writes:
>
>| In <BxoA25.KrJ@usenet.ucs.indiana.edu> ezachris@cochiti.ucs.indiana.edu writes:

	[stuff discussing Protogen pros & cons deleted]

>I found what may be a bug (but still might be my misuse of the
>package.) I painted a dialog to serve as the main window for a small
>test application and the application code that Protogen generated did
>not successfully run. I received the classic error -5 indicating that
>the dialog window could not be created.
	I suspect that this error is created by not being able to load
	BWCC.DLL for some reason.  Did you generate code for OWL?

>After much fumbling around I looked at the calc sample application
>that comes with application frameworks and found that Protogen does
>not appear to use the dialog name correctly in the handling of the
>dialog window.
>
>Anyway, I changed the code by hand to match calc's mechanism, which
>only took a couple of minutes, and everything worked fine. I went into
>a second directory and, using everything I had learned about the
>naming conventions to use for the icon and dialog, I regenerated a
>fresh application. It still failed, so I don't think Protogen (version
>2.2) handles dialog boxes as main windows all that well.

	Try it again, and make sure it can find BWCC.DLL
-- 
John A. Grant						jagrant@emr1.emr.ca
Airborne Geophysics
Geological Survey of Canada, Ottawa