Community
Participate
Working Groups
I think that label decoration in package explorer should include additional functionality. 1. decorator for a JUnit test (a red or green (junit.org) T) 2. decorator for a class with a main method (a green |> 'run' icon) 3. decorator for a class implementing the Serializable interface (a line running through the class icon?) I find that 1 & 2 are must haves, and 3 is optional, but I would find it VERY helpful (especially for web apps that are being clustered and are using session replication.) I think that these would be great additions to the 'label decorations' functionality. Regards and thanks, Ray Case
we have no plans for 2. and 3. but 1. is a good idea. About 2.: 'main' is already shown on the type icon. Showing it on the Compilation unit or class file would be quit expensive as it would require to open the file what normally isn't needed when showing the file image. I don't think 'main' is that important anymore to justify the cost. For 3. we didn't have this request yet, me myself never required the 'is serializable' information that often, so I don't think it deserves the space on the image (which is already heavely used). Is ok when I rename this bug to focus on the JUnit suggestion?
Yes, you can forward this as JUnit decoration only. Hey, I am perfectly happy for any of these three features getting in there. They all have some benefit for me, although I agree with your opinions on 2 & 3. I actually have used a plugin(for about 1.5 years) that does the label decorators I suggested. I have never used the 'types' view before - is that what you mean when you say: > 'main' is already shown on the type icon Except for the 'types' view, I can't find any icon or decorator that shows that a class is 'run'able. In package explorer I see 'I', 'E', 'A' and '@' - for me, package explorer is where the decorations are the most useful. Thanks Martin! -Ray (In reply to comment #0) > I think that label decoration in package explorer should include additional > functionality. > 1. decorator for a JUnit test (a red or green (junit.org) T) > 2. decorator for a class with a main method (a green |> 'run' icon) > 3. decorator for a class implementing the Serializable interface (a line > running through the class icon?) > I find that 1 & 2 are must haves, and 3 is optional, but I would find it VERY > helpful (especially for web apps that are being clustered and are using session > replication.) > I think that these would be great additions to the 'label decorations' > functionality. > Regards and thanks, > Ray Case (In reply to comment #1) > we have no plans for 2. and 3. but 1. is a good idea. > About 2.: 'main' is already shown on the type icon. Showing it on the > Compilation unit or class file would be quit expensive as it would require to > open the file what normally isn't needed when showing the file image. I don't > think 'main' is that important anymore to justify the cost. > For 3. we didn't have this request yet, me myself never required the 'is > serializable' information that often, so I don't think it deserves the space on > the image (which is already heavely used). > Is ok when I rename this bug to focus on the JUnit suggestion? (In reply to comment #1) > we have no plans for 2. and 3. but 1. is a good idea. > About 2.: 'main' is already shown on the type icon. Showing it on the > Compilation unit or class file would be quit expensive as it would require to > open the file what normally isn't needed when showing the file image. I don't > think 'main' is that important anymore to justify the cost. > For 3. we didn't have this request yet, me myself never required the 'is > serializable' information that often, so I don't think it deserves the space on > the image (which is already heavely used). > Is ok when I rename this bug to focus on the JUnit suggestion?
