Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Feature Requests

Members drop list - various improvements

You must be registered to post a reply.
Click here to register.

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

[quote][i]Originally posted by Uniwares[/i]
[br]The members list was always helpful but at the same time never useful enough (for me at least). There are several things that I would like to see in it:

1) grouping of members with region support
2) removal of repeating namespace/classnames

Let me explain:
It would be great to group the members the same way as they are grouped/sorted in the class view. Group by access, type, name, etc. If there are regions, split the members in subgroups by regions with the same sorting as in the class view. The current, alphabetic sort is nice but not very helpful in larger or organized files, since it destroys whatever order the programmer has put the content.

The removal of repeating namespace/classnames is simply a way to make the list more readable. For example:
The list shows now
[code]
[blue]MyNameSpace.MyClass[/blue]
[blue]MyNameSpace.MyClass[/blue].aPropertyX
[blue]MyNameSpace.MyClass[/blue].[maroon]function1[/maroon](...)
[blue]MyNameSpace.MyClass[/blue].[maroon]function2[/maroon](...)
[blue]MyNameSpace.MyClass[/blue].[maroon]function3[/maroon](...)
[blue]MyNameSpace.MyClass[/blue].[maroon]function4[/maroon](...)
[blue]MyNameSpace.MyClass[/blue].[maroon]function5[/maroon](...)
[blue]MyNameSpace.MyClass[/blue].[maroon]function6[/maroon](...)
[blue]MyNameSpace.MyClass.MySubClass[/blue]
[blue]MyNameSpace.MyClass.MySubClass[/blue].[maroon]MySubClass[/maroon](int)
[blue]MyNameSpace.MyClass.MySubClass[/blue].[maroon]~MySubClass[/maroon]()
[blue]MyNameSpace.MyClass[/blue].PropertyY
[blue]MyNameSpace.MyClass[/blue].zProperty
[blue]MyNameSpace[/blue]
[/code]

By putting it into the right hierarchy and removing the redundant information, it looks like that:

[code]
[blue]MyNameSpace[/blue]
[blue]MyNameSpace.MyClass[/blue]
[blue]                   [/blue].[maroon]function1[/maroon](...)
[blue]                   [/blue].[maroon]function2[/maroon](...)
[blue]                   [/blue].[maroon]function3[/maroon](...)
[blue]                   [/blue].[maroon]function4[/maroon](...)
[blue]                   [/blue].[maroon]function5[/maroon](...)
[blue]                   [/blue].[maroon]function6[/maroon](...)
[blue]                   [/blue].aPropertyX
[blue]                   [/blue].PropertyY
[blue]                   [/blue].zProperty
[blue]MyNameSpace.MyClass.MySubClass[/blue]
[blue]                              [/blue].[maroon]MySubClass[/maroon](int)
[blue]                              [/blue].[maroon]~MySubClass[/maroon]()
[blue]                              [/blue].otherProperty
[/code]

And with regions:

[code]
[blue]MyNameSpace[/blue]
[blue]MyNameSpace.MyClass[/blue]
[blue]                   [/blue].[maroon]function1[/maroon](...)
[blue]                   [/blue].zProperty
[black]#superduperregion1[/black]
[blue]                   [/blue].[maroon]function6[/maroon](...)
[black]#whocaresaboutthose[/black]
[blue]                   [/blue].[maroon]function3[/maroon](...)
[blue]                   [/blue].[maroon]function5[/maroon](...)
[black]#maintenancehell-dontopen[/black]
[blue]                   [/blue].[maroon]function2[/maroon](...)
[blue]                   [/blue].[maroon]function4[/maroon](...)
[blue]                   [/blue].aPropertyX
[blue]                   [/blue].PropertyY
[blue]MyNameSpace.MyClass.MySubClass[/blue]
[blue]                              [/blue].[maroon]MySubClass[/maroon](int)
[blue]                              [/blue].[maroon]~MySubClass[/maroon]()
[blue]                              [/blue].otherProperty
[/code]

Maybe even color the background of the regions so they look even more grouped.

Isnt that much easier to read than the current way?
[/quote]

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
Uniwares	Posted - May 30 2006 : 2:07:28 PM The members list was always helpful but at the same time never useful enough (for me at least). There are several things that I would like to see in it: 1) grouping of members with region support 2) removal of repeating namespace/classnames Let me explain: It would be great to group the members the same way as they are grouped/sorted in the class view. Group by access, type, name, etc. If there are regions, split the members in subgroups by regions with the same sorting as in the class view. The current, alphabetic sort is nice but not very helpful in larger or organized files, since it destroys whatever order the programmer has put the content. The removal of repeating namespace/classnames is simply a way to make the list more readable. For example: The list shows now MyNameSpace.MyClass MyNameSpace.MyClass.aPropertyX MyNameSpace.MyClass.function1(...) MyNameSpace.MyClass.function2(...) MyNameSpace.MyClass.function3(...) MyNameSpace.MyClass.function4(...) MyNameSpace.MyClass.function5(...) MyNameSpace.MyClass.function6(...) MyNameSpace.MyClass.MySubClass MyNameSpace.MyClass.MySubClass.MySubClass(int) MyNameSpace.MyClass.MySubClass.~MySubClass() MyNameSpace.MyClass.PropertyY MyNameSpace.MyClass.zProperty MyNameSpace By putting it into the right hierarchy and removing the redundant information, it looks like that: MyNameSpace MyNameSpace.MyClass .function1(...) .function2(...) .function3(...) .function4(...) .function5(...) .function6(...) .aPropertyX .PropertyY .zProperty MyNameSpace.MyClass.MySubClass .MySubClass(int) .~MySubClass() .otherProperty And with regions: MyNameSpace MyNameSpace.MyClass .function1(...) .zProperty #superduperregion1 .function6(...) #whocaresaboutthose .function3(...) .function5(...) #maintenancehell-dontopen .function2(...) .function4(...) .aPropertyX .PropertyY MyNameSpace.MyClass.MySubClass .MySubClass(int) .~MySubClass() .otherProperty Maybe even color the background of the regions so they look even more grouped. Isnt that much easier to read than the current way?
6 L A T E S T R E P L I E S (Newest First)
support	Posted - Jan 24 2011 : 4:05:49 PM case=1232 is implemented in build 1840
support	Posted - Jul 14 2008 : 2:40:30 PM case=808 is implemented in build 1645
feline	Posted - Jun 01 2006 : 5:43:12 PM this makes sense. it has just occurred to me that using a different colour could cause some problems if the user has a non white global windows background colour. it will depend on how this is done. i have put in a request so we can see what the developers make of this. case=1232
Uniwares	Posted - May 31 2006 : 6:05:58 PM quote: Originally posted by feline what happens when you have a lot of items, so the list is much taller than the screen. then you can have this cascading blank space the whole height of the screen. Good question. I would suggest in such cases to put the last valid full name grayed out (or, correctly colored but lighter) at the first line.
feline	Posted - May 31 2006 : 2:45:07 PM putting the region's into the list has been suggested before case=808 your examples do make it a lot easier to read the display my main concern is the cases where i have more than one class in the same file, and want to use the class name as part of the filter, e.g. "SubClass" in your examples. however if the "invisible" part of the text was still able to filter, then that might not cause to many problems. considers what happens when you have a lot of items, so the list is much taller than the screen. then you can have this cascading blank space the whole height of the screen.
support	Posted - May 30 2006 : 11:14:38 PM You make some good suggestions. If you haven't tried already, you might order the Alt+M list by occurrence in file. Find the option on the "Text Editor\|General" node of our options dialog.

Snitz Forums 2000