[Monodevelop-devel] Google Summer of Code - Razor and MVC 3

sparek sparekd at gmail.com
Wed Mar 28 21:09:04 UTC 2012

2012/3/28 Michael Hutchinson <m.j.hutchinson at gmail.com>

> On 23 March 2012 19:35, Michael Hutchinson <m.j.hutchinson at gmail.com>
> wrote:
> > It is a challenging project, but I believe it's doable in the GSoC
> > timeframe. The main challenge is in building a Razor parser. Then you
> > should integrate with the existing HTML and C# completion engines.
> Update - Microsoft open-sourced their Razor parser yesterday, and it
> has an incremental parser for use in editors:
> http://aspnetwebstack.codeplex.com/SourceControl/changeset/view/c5fcf6b687f0#src%2fSystem.Web.Razor%2fRazorEditorParser.cs
> This is great - not only do we not have to write a parser, we can be
> sure it will behave correctly. There will still be challenges plugging
> this incremental parser into MD's syntax highlighting engine and
> background parser system, and making it hand off regions to C# and
> HMTL highlighting and completion engines. But hopefully this will free
> up some time to work on more advanced editing features such as source
> tooltips, or maybe even rename refactoring support.
> --
> Michael Hutchinson
> http://mjhutchinson.com

This is really good news. I'll have to make some changes to my application
to take this fact into account. I’m  really grateful for all the provided
answers, because they helped me understand better which features are of
paramount importance. I have one more question related to GSoC. I was told
that it’s always better to send proposals as early as possible. Does it
mean that I should expect some feedback even before the application
deadline, e.g. some hints or changes proposition? Or do you check all the
applications only after deadline, so it’s better to tinker with the details
till the very last day of application period?

 Piotr Dowgiallo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20120328/d5df46c9/attachment.html>

More information about the Monodevelop-devel-list mailing list