[MonoDevelop] WelcomePageView - the 'Save As...' problem

Matej Urbas matej.urbas at gmail.com
Wed Jun 7 08:46:22 EDT 2006


Michael Hutchinson wrote:
> On 6/7/06, Pascal Fresnay <pascalfresnay at free.fr> wrote:
>> Juste click on interface name, a small inline help menu (a small
>> rectangle under the first letter) provides you two commands : "implement
>> interface 'foo'" and "explicitly implement inteface 'foo'". Prototypes
>> for all methods and properties are generated.
>> When you type an unaccessible type (missing using), you can find another
>> small inline help menu that allows you to insert "using System.Thing" or
>> to replace type reference by "System.Thing.Class".
>> Another very cool feature of Visual Studio is auto-completion of adding
>> delegate to event. If you write :
>
> Yeah, I was just about to point those exact same things out before I
> read your email :-) Great features, I'd love to have them. The little
> drop-down menus are called "Smart tags".
>
> Another one I miss is autocompletion after the "new" keyword, based on
> the declared type. It would also be nice to have a listing of the
> constructor overloads.
Sounds like there is a lot of interest in this topic.

I will start with C# 2.0 code completion support and new features as 
soon as I get a grip of monodevelop's code completion engine. Well, I 
hope gtksourceview has some native support for things like snippets (for 
the way they work in VS.NET 2005).

Code folding is just another thing I miss in monodevelop...

So here's my TODO list:
- get C# 2.0 code completion support working
- add interface/abstract classes stubs implementation support
- snippets
- autocompletion for the 'new' keyword (classes and delegates)
- autocompletion for the 'override' keyword (methods and properties)
- list of overloaded constructors
- list of parameters of a function and current position in the parameter 
list
- fix some code completion misbehaviour (code gets overwritten if you 
use code completion in middle of a line , nested classes make 
monodevelop confuse their host classes with namespaces etc.)
- Optional: perhaps displaying documentation for members (in the 
autocomplete box) wouldn't be a bad idea, ha?
- Optional: add support for code folding - regions (seems like changes 
in gtksourceview will be needed :) )
- if needed: revamp graphical controls that are behind code completion
- if needed: make the code completion engine more flexible (so that 
additional changes in languages could easily be added)
- if possible: try to improve the overall performance of code completion 
if possible

Phew, that's a loooong TODO. I guess it will take a long time to finish 
those.

Have I missed anything? You are welcome to add your wishes :)


More information about the Monodevelop-list mailing list