comp.lang.idl-pvwave archive: archive » Re: large info structure?

Home » Public Forums » archive » Re: large info structure?

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

Re: large info structure? [message #56120 is a reply to message #56119]

Tue, 02 October 2007 09:56

Paul Van Delst[1]
Messages: 1157
Registered: April 2002

Senior Member

David Fanning wrote:
> markb77@gmail.com writes:
>
>> I'm writing a widget application which will serve as a data analysis
>> platform for scientific image data. The idea is that after loading
>> the image, there are many different types of analysis that the user
>> may wish to run on it, and this application will support them all.
>> There will be an 'Analysis' dropdown menu, for instance, with several
>> options. I also want to make it easy to add new analysis methods to
>> the program.
>>
>> I've finished writing the front end and now I'm in the process of
>> adding some analysis. What I'm noticing is that the info structure
>> that gets passed around between event handlers is getting to be very
>> large. Mine is up to 130 variables, at the moment.
>>
>> Does anyone have a strategy to suggest for dealing with this type of
>> situation?
>
> Ahhmumm, may I suggest writing your widget program as an object? :-)
>
> It doesn't solve the "lots of info" problem, but it
> does mean you don't have to pass anything around anymore.
> It is ALL built right into the fabric of the program.
>
> And the "lots of info" problem eventually gets sorted out
> into a "several objects" solution, which tends to compartmentalize
> the functionality and keep things from breaking when adding new
> functionality.
>
> There is a danger to this kind of programming, however. It is
> easy (WAY too easy!) to make your objects "clever". Which is
> good, don't get me wrong. But clever objects make it almost
> impossible to follow the programming flow.

Huh. I read something similar about ruby code the other day also. The real cleverly
written ruby codes tends to have many methods that don't seem to actually *do* anything -
they just call other methods, which call others, etc..

Of course, I'm mostly still in the monolithic block-o-code stage wrt ruby. :o(

cheers,

paulv

Report message to a moderator

[Message index]

		Re: large info structure? By: Wox on Wed, 03 October 2007 01:06
		Re: large info structure? By: David Fanning on Tue, 02 October 2007 14:35
		Re: large info structure? By: markb77 on Tue, 02 October 2007 14:16
		Re: large info structure? By: Paul Van Delst[1] on Tue, 02 October 2007 14:08
		Re: large info structure? By: David Fanning on Tue, 02 October 2007 13:48
		Re: large info structure? By: markb77 on Tue, 02 October 2007 13:25
		Re: large info structure? By: Michael Galloy on Tue, 02 October 2007 10:52
		Re: large info structure? By: Paul Van Delst[1] on Tue, 02 October 2007 09:56
		Re: large info structure? By: David Fanning on Tue, 02 October 2007 08:42
		Re: large info structure? By: Mike[2] on Fri, 05 October 2007 08:01
		Re: large info structure? By: JD Smith on Thu, 04 October 2007 15:40

Previous Topic:	envi_setup_head for TIFF
Next Topic:	What is the main difference between a script and a procedure?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 02:29:16 PDT 2025

Total time taken to generate the page: 2.32105 seconds