| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2080.1 | No numbers, but a rationale | DECWIN::KLEIN | | Fri Jan 19 1990 09:30 | 21 |
| >> I s there any information concerning the performance of UIL/DRM user
>> interface creating and managing versus using the toolkit routines ?
>> I talk with a customer who refuses to use UIL/DRM because of the low
>> performance of this method.
>> He agrees to use toolkit routines.
>> I like him to force UIL/DRM because of time constraints.
I don't have any numbers, but I think that the customer is 180 degrees wrong.
I would say that UIL/DRM is faster at runtime than directly using the toolkit
routines. The reason for this is that they are probably using a .DAT in
conjunction with the toolkit routines to set x, y, width, height, etc resources.
This requires "compiling" the .DAT file everytime the program is run.
UIL/DRM, on the other hand, builds a resource argument list at the time
that the UIL file is compiled and it is more efficient to create the widget
at runtime from a pre-built argument list than from a .DAT file.
By ALL means, they should be using UIL.
-steve-
|
| 2080.2 | Not using UIL/DRM is faster, but not terribly so | OPHION::MIKEY | Mike Yang | Fri Jan 19 1990 19:03 | 16 |
| Just using the Xt library does not require the use of a .DAT file (I've
not even sure what you mean here). In C, you can just have a static
structure and "hardwire" the resource arguments into the program. Of
course, this makes changing any resource values more difficult because
you then have to recompile the C program.
With UIL and DRM, the user interface part is separated from the C
source and can be regenerated separately. But the tradeoff is that the
corresponding UID file has to be loaded at runtime, and the DRM
hierarchy has to be initialized/loaded. Therefore, using UIL/DRM
causes a startup delay. When someone asked how much this was at the
Motif tutorial at the X Conference (UIL/MRM), Ellis Cohen didn't
quantify it, but did acknowledge that there was one. He suggested that
you could load only the parts of the widget tree that were immediately
necessary, and thereby spread the delay out.
|
| 2080.3 | Winning time by using UIL/DRM ? | IJSAPL::BROUWERS | | Wed Jan 24 1990 09:49 | 9 |
| Thanks, everybody for your replys.
if somebody has more information about this subject, and specially
information about gaining time in a given project when uil/drm is used
i'm very interested.
I know this is very hard, but may somebody did a project and has some
guesses from that project.
gerard brouwers
|