xaml typeprovider component restriction about fsharpx.extras HOT 13 CLOSED

can you please send a pull request?

from fsharpx.extras.

Is there a reason why XamlTypeProvider is not using System.Windows.Markup.XamlReader instead of XmlReader?
XamlReader has already solved the issue of resolving Xaml Node names to the correct types, no need to do it again?

from fsharpx.extras.

@nrolland As I understand the code (haven't verified yet), you can have members in the generated type outside of System.Windows.Controls, but they will be of type Object. Xaml documents do list their dependencies, so we can do a better job here.
If I get some free time I'll look into it.

from fsharpx.extras.

Argh, I wanted my pull req to be part of this issue instead of creating a new one, #160. I'm not used to GH.

from fsharpx.extras.

Do you have a doc mentioning this resolution of Xaml nodes to the correct types? This is interesting.

from fsharpx.extras.

Ok I see what you mean, i was out of it, Yeah so the types will be resolved, but the assembly referenced that contain those types might not be loaded I guess. (Not sure I remember everything) So that is why you say it will be of type object, which kind of spoils the typeprovider fun

from fsharpx.extras.

My commit fixes this for external controls, i.e. controls not defined in the current assembly.
If you create a custom control inside the same assembly that is being 'TypeProvided' it is always going to be of type object, simply because the type doesn't exist yet, so we can't resolve it. :)

from fsharpx.extras.

Got it. Ahh.... Multistage execution + a proper composable dependency
model... Life would be good...

On Tuesday, November 27, 2012, Robert Jeppesen wrote:

My commit fixes this for external controls, i.e. controls not defined in
the current assembly.
If you create a custom control inside the same assembly that is being
'TypeProvided' it is always going to be of type object, simply because the
type doesn't exist yet, so we can't resolve it. :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/87#issuecomment-10738457.

Nicolas Rolland
mobile : +33 6 62 88 42 92

from fsharpx.extras.

This is a brilliant change..

from fsharpx.extras.

Thanks! :)

from fsharpx.extras.

Can I close this?

from fsharpx.extras.

Works for me, but @nrolland should weigh in.

from fsharpx.extras.

sure ! thank you robert. it gives me a pretext to look into the specifics of the xamlreader!

from fsharpx.extras.