I was wondering if there was any movement on these bugs? I noticed all of the
bugs have been mostly untouched since being reported. Is the plan just to be
inconsistent with Silverlight on OSX?
--
View this message in context:
Hello,
I was wondering if there was any movement on these bugs? I noticed all of
the
bugs have been mostly untouched since being reported. Is the plan just to
be
inconsistent with Silverlight on OSX?
Mono existed before Silverlight for OSX existed, and unlike Silverlight for
OSX, it has no
So is there a way to get a path to the Documents folder in OSX symbolically
without hard-coding it?
Looking briefly at the bug reports, it appears that the original .NET
specification intended for that special folder enum to point to the
Documents directory, not the user's home folder. So, and
I understand your points, Miguel, but it sucks not to be able to be
consistent / compatible with .NET here.
I know it's not possible to get numbers, but how many Mono OSX apps do you
think currently rely on this feature vs how many Silverlight / .NET apps
could benefit from this change? And it's
F_script (http://www.fscript.org/) has a rather clever class browser
that lists classes, methods etc via the Objective-C runtime. Might it
possible to use the same approach to automate the generation of MONO
Cocoa bindings using the same technique? The runtime has a C API, is
well documented*,