chf@holin.ATT.COM (Charles Foster) (05/02/90)
In article <HPASANEN.90Apr27143244@tko-sony-15.hut.fi>, hpasanen@niksula.hut.fi (Harri Pasanen) writes: > Has anybody used the new Windows version of the Knowledge Pro? > Any experiences? I've had Knowledge Pro Windows for about a month now. If you are familiar with the Knowledge Pro product you will be very at home with the windows version. The documentation is very good and I have only reported a few problems to their CompuServe technical assistance line. With respect to creating a Windows application, the KPWIN enviroment seems to be less pain than the Windows developers here at work go through. The penalty, of course, is speed. In my first attempt, I built a very complex (7 push-buttons, 4 list boxs, 5 edit fields) screen and a main menu. To display this took about 20 seconds. I would caution anyone that this time was certainly not representative of an optimized screen and the release of KPWIN is "pre-release" version 0.9. This seems slow to me judging from other windows applications Ihave used in the past. In summary, if you are looking for to KPWIN to be a substitute for a Windows production development enviroment (ie. SDK and C-compilers), I think KPWIN is is probably not such a good choice. If you are looking for a easy to use Windowsapplication prototype enviroment or expert system shell, KPWIN is something to consider. If Knowledge Garden improves the speed of screen handling, KPWIN will be a lot easier to justify as a mainstream Windows application development tool.
patrickd@chinet.chi.il.us (Patrick Deupree) (05/04/90)
In article <955@holin.ATT.COM> chf@holin.ATT.COM (Charles Foster) writes: >In article <HPASANEN.90Apr27143244@tko-sony-15.hut.fi>, hpasanen@niksula.hut.fi (Harri Pasanen) writes: >> Has anybody used the new Windows version of the Knowledge Pro? >> Any experiences? > >With respect to creating a Windows application, the KPWIN enviroment seems to >be less pain than the Windows developers here at work go through. The >penalty, of course, is speed. In my first attempt, I built a very complex >(7 push-buttons, 4 list boxs, 5 edit fields) screen and a main menu. To >display this took about 20 seconds. I would caution anyone that this time >was certainly not representative of an optimized screen and the release of >KPWIN is "pre-release" version 0.9. This seems slow to me judging from other >windows applications Ihave used in the past. > Hmmmm. I'd say 20 seconds is a lot of time to draw such a thing. To put up a window containing three list boxes and an edit window in it's client space takes us all of a second, so one would not expect an extra list box and a few fields and buttons to take much time. I'd be interested in hearing what the size of KPWIN apps have been and what people think of the environment. I tried to latch onto a copy of the program but they turned me down when I offered a trade, so I'm relying on you folks to fill me in on what this product is really like. I have talked to them and found out they have a runtime version that you are free to distribute. Does one have to run this runtime version and have it call a file that contains their code? Another thing I'm interested in is how it handles resources. Do they distribute a resource compiler that one can use to create dialogs, menus, etc? Or do they just make you create such things dynamically? I'm really interested in this and would welcome any feedback. -- "Organized fandom is composed of a bunch of nitpickers with a thing for trivial pursuit." -Harlan Ellison Patrick Deupree -> patrickd@chinet.chi.il.us