| Having used TeleUSE for a product, I would recommend that
it be avoided. A selection of complaints:
Generated code cannot be maintained independent of the tool.
"Object-oriented" features do not work as advertised.
Very difficult to integrate third-party widgets.
I18N is broken.
The tool has many nice features, especially for prototyping,
but I'd never use it for a product again.
Steph
|
| There are other notes in this confernce about BX and I think TeleUse. Our team
used bx 3.1 extensively for the gui system managment tools that shipped with
Digital UNIX V4.0. It has many rough edges and LOTS of bugs but most were
workaroundable. I filed about 100 bugs reports on various aspects of the
product.
Miscellaneous notes:
- The version of the license manger (flexlm) that they were using was
completely broken and a constant source of system management problems.
- It's definitely one of the best products for dealing with UIL files.
- 3.1 was pre-CDE so you have to add/define the new CDE widgets
(combobox, spinbox, etc) yourself. This works but it poorly
documented and very tricky to get right.
- 3.1 had no provision for dealing with comments. Any comments
in the UIL are dumped on the floor.
- One good trick is to write protect certain UIL files. BX realizes
that it can't write back to that file and behaves properly
for all the other files it can write. This is how I managed
the files that needed comments (specifically the files
that are targeted for translation).
- Bx is very stupid about widths/heights if you ever resize anything,
it writes a hardwired width/height for a bazillion widgets into the
UIL file. I fixed this with post-processing steps that strip
every single XmNheight and XmNwidth from all the UIL files.
I have not used the later versions of bx (v4.0) so it's possible
that many of the bugs are fixed. You should be able to get eval
copies from ICS.
pete
|