CompuServe Thread

>>Nix on programing languages, long live the scripts… Hey Nik! I like the script idea, however I'd vote for including the capability of accessing a powerful programming language. (and not just because I write software) With a scripting language, you are limited by what function the designers decided to add. I haven't seen the Autosketch macros, but if it's like others I have seen, it may be very limiting. Full access to a programming language, on the other hand, opens up a world of possiblities, such as what you see happening with IPAS. If that power were integrated into the body of 3DS, along with hooks into the GUI (things like programmable button and menus, etc.), some very tightly integrated addons would result. Another point about a full language: It is a relatively simple task to WRITE a scripting language interpreter with a real programming language. I've done this a number of times for applications ranging from a 3D wire-frame morpher (written in BASIC) to a complete control language interpreter for a military mobile data acquisition van (written in C). I'll make you a deal – you talk'm into adding a real language, and I'll WRITE an interpretive scripter for you! (In my spare time…) If the powers decide to add programmibility integrated to the core of 3DS, I vote for a real language. If 3DS for Windows or NT or SomeSuchGUI comes our way, something like Visual Basic would be perfect: easy to do simple things, powerful enough for the complex, and capable of calling C or assembler when necessary for speed. This is the way we do much of our work in my day job. >>AutoLisp version of IPAS… IMHO, limiting programmability to ANY interpretive language or scripter would be so slow it would make much IPAS-like functionality impossible. A true compiled language would be required for image processing functions, for example. (At least those you wanted to finish this week. <g>) After saying all this, I'd still be happy with a simple script language, or even a real macro recorder (complete with top menu picks, etc.). This would be a HUGE improvement over what we have now. J K J

Nik, >> scripting Well … the problem typically with scripting is that you have a hard time saving variables and values … also .. doing calculations. Scripting is fine for repetative tasks .. but to automate design .. flexible variables and calculations _are_a_must_. I guess that is what separates a scripting language from a programming language … the ability to define variables, store values and calulate others. Without these features .. I wouldn't say it would be useless to have .. but sure would be frustrating for the things you "can't do". Ang