Joining this group

[Don Syme]

Hi all,

I've just joined this group... I should have joined when it
started :-). Thanks to everyone for setting up the F# community on
GitHub.

The main role of the F# team at Microsoft for the F# community on
GitHub will of course be to prepare open source code drops of F#
compiler/library releases. As part of this, I just wanted to mention
that we are in the beginnings of preparing the F# 2.0 compiler+library
open source code drop updates matching VS2010 SP1. This sort of work
tends to happen somewhat erratically in-between the strict deadlines
of the Microsoft product cycle.

One thing I've done today is to adjust the brief information on the F#
PowerPack site to mention that that site really acts as a staging
point for the open source code drops before they are transferred into
GitHub.

If you get a chance, please take a peek at what is now here:
http://fsharppowerpack.codeplex.com/

BTW, can I ask how many of the F# community on GitHub are members of
this Google group, i.e. is this the best way to communicate with the
members of the F# community on GitHub? Or communication best done via
email?

thanks
Don Syme
Microsoft Research

[Michael P]

I prefer github

[Funnel Web]

I'd like to help out. Am mostly after the MonoDevelop bindings, but have been compiling fsharp too.

Ben

[panesofglass]

Given the number of responses thus far and knowing a large number of F#-ists are on github, I think github is probably better.

[Michael P]

Don,

I think that the most immediate improvement of what F# Open Source has right now can be achieved if two following DLLs were made open source or at least their API shall be exposed using MEF or something similar.

FSharp.LanguageService, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

FSharp.LanguageService.Base, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

They are using internal and not documented language services of f# compiler.

Tomas already wrote about fun things that can be easily done with this code http://tomasp.net/blog/fswebsnippets-intro.aspx

The benefits for both sides are too obvious to enumerate.

Regards

Michael

 

[Tomas Petricek]

Hi,

the API that is used in F# WebSnippets and in MonoDevelop IDE is some internal functionality from FSharp.Compiler.dll (which is already open-sourced). The reason why the plugin still uses internal API (via Reflection) is to make it work with a standard installation, but it could equally use a modified version of F# sources (with the required API made public).

 

The DLLs that you mentioned are F# integration for Visual Studio. Open-sourcing these would be nice (as the community could extend the Visual Studio integration for F#), but it is not needed for MonoDevelop or other cool projects. (It would be nice as a reference.)

 

I think some documentation for the services exposed by the F# compiler (that I’m using) would be invaluable though.

 

Tomas

--
You received this message because you are subscribed to the Google
Groups "FSharp Open Source Community" group.
To post to this group, send email to fsharp-o...@googlegroups.com
To unsubscribe from this group, send email to
fsharp-opensou...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/fsharp-opensource?hl=en

[Michael]

Tomas,

I thought of using 

* line oriented parser and tokenizer from those dlls.

* Intellisence Providers

* Scanner class

* Typed compilation unit information and  some other things

Frankly, I think that i could find a great use for most of the classes in those dlls. 

Visual Studio Interfaces are well documented therefore i thought that making the code MEFable would be a good half step.

There other things except MonodDevelop that could enjoy good integration and already written and tested language service. 

Regards,

Michael

--

Michael Pavlovsky