Hi Armando
Thanks for the suggestions. Re" Often times I wish shared variables coudl be defined within the Init macro of classes. (sort of class variables, not only object variables)" --Does the current implementation of class variables not meet this need (see the help topic "Class Variables")? re "The GetClassMethodNames(string classname) sounds very useful It will help me document my library quickly. A GetClassFileds() or GetClassproperties(), listing all properties defined in the class Init macro would be great also. Waht about a commnd listing hieerarchically all methods, classes and so on in an .rsc file?" --There is the existing macro function GetObjectVariableNames(). You cannot get a list of variables by class name as variables only exist on objects as they are created and code gets executed, rather than the classes themselves. Maptitude Mapping Software <http://www.caliper.com/> Group Moderator --- In [email protected], Armando Scalise <armando.scal...@...> wrote: > > Polymorphism (at least based on the number of parameters, if not on > parameter type) is one single enhacement taht would highly reduce coding > complexity. > > Error bubbling is a must-have., specially when buidling an Objects library. > > Often times I wish shared variables coudl be defined within the Init macro > of classes. (sort of class variables, not only object variables) > > But one area that I think would greatly improve productivity is the > debugger. Here is my Top 10 list of wished changes (not in preference > order) > > 1) when double clicking on a string, restrict the selection to the string, > and do not includes commas, quotes, spaces or other characters (execpt for > - and _ ) > 2) when right clicking on a string, if the string is a variable, show its > current value as the first element in the pop up menu (No need to highlihgt > first) The current roollover implementaion does not always work > 3) Inlcude in the pop up menu an option to ADD the right clicked text to > the Watch list and option to go to that variable on the Variables list > (this would save a lot of time when debugging) > 4) provide optiosn for sorting the variables: by Name and By Type, > 5) let the user define background colors for the firstt and last line of > Classes Methods Macros, Dboxes and Box Items > 6) Allow editing Expressions and Values on the Watch and Variable Window, > without having to resort to a separate dialog box. > 5) Allow removing individual breakpoints , by right clicking on the > Breakpoint list > 6) Have 3 popdown menues at the top of the debugger with all macros, > dboxes, classes, and methods defined in the file. (save us long > scrollings). > 7) On the Search tool, allow wrapping searches > 8) Allow automatic highlighting of syntax > 9) on the GISDK Developers Kit tool box, provide buttons and drop down > lists to recompile the last 10 (better yet the last 100) macros and DBDs . > > 10) every time the Imediate Execution window is opened, resize it to the > last dimensions the user set. > > > The GetClassMethodNames(string classname) sounds very useful It will help > me document my library quickly. A GetClassFileds() or GetClassproperties(), > listing all properties defined in the class Init macro would be great also. > Waht about a commnd listing hieerarchically all methods, classes and so on > in an .rsc file? > > > > Another new feature is that if a method call returns another object you > can string together a call to a method on that object (or reference a > property on it) using the dot notation, e.g. > > object.GetAnotherObject().DoSomething() > > On 5.0 when you try to do something like that, it works but it returns an > error 8 message inmediately upon completion. See code below > > > > Macro "test" > > oSecondClass = CreateObject("MySecondClass") > oSecondClass.GetFirstClass().Hello() // Shows the message and then > returns an error message that can be handlded by on languageerror > > endMacro > > class "MyFirstClass" > > Init do > self.InitTime = GetDateAndTime() > enditem > > > > Macro "Hello" do > ShowMessage( "Hello from " + GetObjectClass(self) + " started at " + > self.InitTime) > endItem > > endClass > > Class "MySecondClass" > Init do > self.FirstClass = CreateObject("MyFirstClass" ) > endItem > > Macro "GetFirstClass" do > return (self.FirstClass) > endItem > > endClass > > > > On Mon, Nov 22, 2010 at 3:16 PM, [email protected] wrote: > > > > > > > There is a new macro function: > > > > array GetClassMethodNames(string classname) > > > > which returns a list of the names of the methods defined for the class (but > > not including methods inherited from other classes) > > > > Another new feature is that if a method call returns another object you can > > string together a call to a method on that object (or reference a property > > on it) using the dot notation, e.g. > > > > object.GetAnotherObject().DoSomething() > > > > We are always interested to hear any suggestions from DK users as to what > > improvements they would like to see. > > > > > > Maptitude Mapping Software <http://www.caliper.com> Group Moderator > > > > > > --- In [email protected], Armando Scalise armando.scalise@ > > wrote: > > > > > > Looks like a big overhaul. > > > > > > I would like to know if there is a 64 bit version > > > > > > Also, can we have a full list of all changes and additions to the GISDK? > > > Have ther been any improvements on the way the DK implements objects? > > > > > > -- > > > Armando Scalise > > > > > > > > > > > > > -- > Armando Scalise >
