comp.lang.idl-pvwave archive: archive » Re: GUI and non-GUI objects in Catalyst

Home » Public Forums » archive » Re: GUI and non-GUI objects in Catalyst

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: GUI and non-GUI objects in Catalyst [message #68769]

Fri, 04 December 2009 15:49

Jean-Paul Davis
Messages: 17
Registered: March 1998

Junior Member

David,

Thanks for the thoughts... It does sound like the easiest way to build
an object that doesn't necessarily need a GUI when used by other
applications, but that can be used by itself as a GUI application, and
that takes full advantage of the Catalyst object heirarchy, is to go
ahead and follow the Catalyst application template (wherein my object
is derived from the Catalyst top-level base widget class), and don't
worry about carrying around extra data and methods that don't matter
unless a GUI is generated.

If I understand your last sentence, an alternative is to NOT derive my
application from a widget class, but instead have it contain
individual objects for all the needed widgets (including a TLB). I'll
probably go with the first approach to learn Catalyst faster/better.

Jean-Paul

Report message to a moderator

[Message index]

		Re: GUI and non-GUI objects in Catalyst By: Jean-Paul Davis on Fri, 04 December 2009 15:49
		Re: GUI and non-GUI objects in Catalyst By: David Fanning on Wed, 02 December 2009 16:00
		Catalyst Object Widget Hierarchy By: Jean-Paul Davis on Wed, 16 December 2009 15:38

Previous Topic:	Export Bridge Assistant Warning - routine could not be resolved
Next Topic:	Need to use GRIDDATA instead of CONGRID?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 02:06:15 PDT 2025

Total time taken to generate the page: 1.27842 seconds