Re: Manipulate and Module
- To: mathgroup at smc.vnet.net
- Subject: [mg132105] Re: Manipulate and Module
- From: "Nasser M. Abbasi" <nma at 12000.org>
- Date: Fri, 6 Dec 2013 02:16:26 -0500 (EST)
- Delivered-to: l-mathgroup@mail-archive0.wolfram.com
- Delivered-to: l-mathgroup@wolfram.com
- Delivered-to: mathgroup-outx@smc.vnet.net
- Delivered-to: mathgroup-newsendx@smc.vnet.net
- References: <l7pc1c$gc6$1@smc.vnet.net>
- Reply-to: nma at 12000.org
On 12/5/2013 2:03 AM, Sergio Miguel Terrazas Porras wrote: > I modified many of my notebooks, putting a Manipulate inside the Module, Why? You should think of Manipulate as the main front GUI to the app or the computation engine. A GUI is always the most front end. GUI takes input from user, and call the back-end functions for computation, and then send the result back to the user via the GUI windows or by other means such as to database, files, etc.. Putting the GUI inside a function makes little sense to me. functions do not call the GUI. The GUI calls other functions. --Nasser