Le 26 mars 07, à 15:29, Andy Dent a écrit : >> I can imagine a possible workaround from the top of my head : to >> define classes within the script where the constructor automatically >> creates a reference to its new instance in a property of the >> application. Then, the script would include a portion of code that >> creates a new copy of these instances to make them available to the >> script. Another portion of code would 'refresh' on the app side the >> image of objects used. > > That's a very clear explanation of an approach that would work, if > you really really want to have objects in the user script :-)
Thank you for all your remarks and warnings, Andy. I realize that my project is a bit complex and not very user-friendly, but the bottomline is to let the user manipulate bits of data the way he wants. You might know R, the application for statistical analysis. There's no GUI and the interface is just a console where you type your commands in. It's definitely not user-friendly, but it's so powerful when you get used to it. I want to make a very light R for lexicography. I know that's quite audacious, but the *user* we're talking about is just me, for now, so nobody will get hurt. I'll let you know when it's finished, in a few years time ;-) Octave _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
