When one uses code completion via the emonicinformator, he is not informed if the members/properties etc. are public/private/protected.
It would be helpful, if the access modifier are presented additionally to allow an intended usage of the items.
Added information within the completion window. Now, the completion proposal is structured like the following: <completion.name> : <access-modifier> <type>; included in cvs (sorry Bernhard, it has been finished before 0.3 is released)
Plz try (should work for static and non-static members/fields)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it is a good start but still feel that images should be used to indicate the visibility of the methods like what we do in the Outline view and like what JDT does. Also, there is no information offered about methods extracted from DLLs.
However, let's just leave it be for now and tackle it after we release 0.3.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For external dll-types (e.g. System.xxx), there are (as Remy said) no access identifiers and values shown. Additionally, the pictures are always showing private access, which is an erroneus presentation. Both malfunctions suffer from a "null" entry within the CodeElement attribute access identifier. I am working on it...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dominik, it is looking a lot better than before now. :) We still have a long way to go but the changes you've made are a considerable improvement to what we originally had, thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems to be one has done this for me:) Question: Updating the html-file should occur with the apache forrester, doesnt it? Or is manually editing allowed, to?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1299552
Originator: NO
Having an image set for the completion proposals would be a good start I think.
Logged In: YES
user_id=1245734
Originator: NO
To be implemented after publishing the 0.3-release
Logged In: YES
user_id=1858080
Originator: YES
Added information within the completion window. Now, the completion proposal is structured like the following: <completion.name> : <access-modifier> <type>; included in cvs (sorry Bernhard, it has been finished before 0.3 is released)
Plz try (should work for static and non-static members/fields)
Logged In: YES
user_id=1299552
Originator: NO
I think it is a good start but still feel that images should be used to indicate the visibility of the methods like what we do in the Outline view and like what JDT does. Also, there is no information offered about methods extracted from DLLs.
However, let's just leave it be for now and tackle it after we release 0.3.
Logged In: YES
user_id=1858080
Originator: YES
Added images to existing code completion. Missing information still an issue.
Logged In: YES
user_id=1858080
Originator: YES
For external dll-types (e.g. System.xxx), there are (as Remy said) no access identifiers and values shown. Additionally, the pictures are always showing private access, which is an erroneus presentation. Both malfunctions suffer from a "null" entry within the CodeElement attribute access identifier. I am working on it...
Logged In: YES
user_id=1299552
Originator: NO
Could we also not show the access type? The image in the completion proposal should be self-explanatory.
Logged In: YES
user_id=1858080
Originator: YES
Added changes to the cvs. Please try if it fits your needs (for static and non-static elements). Remy, your suggestions are integrated as well.
Logged In: YES
user_id=1299552
Originator: NO
Dominik, it is looking a lot better than before now. :) We still have a long way to go but the changes you've made are a considerable improvement to what we originally had, thanks!
Logged In: YES
user_id=1299552
Originator: NO
Dominik, please update the change log file in the emonichomepage module for this feature request.
Logged In: YES
user_id=1858080
Originator: YES
Seems to be one has done this for me:) Question: Updating the html-file should occur with the apache forrester, doesnt it? Or is manually editing allowed, to?
Logged In: YES
user_id=1299552
Originator: NO
You should be manually updating the changelog.html file in the emonichomepage CVS module whenever you implement a new feature or fix a bug.