зеркало из https://github.com/mono/mail-archives.git
150 строки
8.0 KiB
HTML
150 строки
8.0 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE> [Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac
|
|
</TITLE>
|
|
<LINK REL="Index" HREF="index.html" >
|
|
<LINK REL="made" HREF="mailto:mono-osx%40lists.ximian.com?Subject=%5BMono-osx%5D%20Introducing%20MacHint%20MonoDevelop%20addin%20-%20developed%0A%09with%20MonoMac&In-Reply-To=AANLkTikxoLymkgfZowPUcMTBBk55Gg%2BK1AFFsw1122kr%40mail.gmail.com">
|
|
<META NAME="robots" CONTENT="index,nofollow">
|
|
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
|
|
<LINK REL="Previous" HREF="003982.html">
|
|
<LINK REL="Next" HREF="004048.html">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#ffffff">
|
|
<H1>[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac</H1>
|
|
<B>frederic forjan</B>
|
|
<A HREF="mailto:mono-osx%40lists.ximian.com?Subject=%5BMono-osx%5D%20Introducing%20MacHint%20MonoDevelop%20addin%20-%20developed%0A%09with%20MonoMac&In-Reply-To=AANLkTikxoLymkgfZowPUcMTBBk55Gg%2BK1AFFsw1122kr%40mail.gmail.com"
|
|
TITLE="[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac">fforjan at free.fr
|
|
</A><BR>
|
|
<I>Tue Feb 8 03:18:02 EST 2011</I>
|
|
<P><UL>
|
|
<LI>Previous message: <A HREF="003982.html">[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac
|
|
</A></li>
|
|
<LI>Next message: <A HREF="004048.html">[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#3986">[ date ]</a>
|
|
<a href="thread.html#3986">[ thread ]</a>
|
|
<a href="subject.html#3986">[ subject ]</a>
|
|
<a href="author.html#3986">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
<HR>
|
|
<!--beginarticle-->
|
|
<PRE>Hello !
|
|
|
|
Thanks for your answers !
|
|
|
|
For the monomac dll, i already tried what you said but it seems the MonoMac.dll is not loaded... How to ensure that this dll is already loaded ?
|
|
I'm currently on the alpha channel to monodevelop, but maybe these modifications are not part of this channel ? If it's the case I will have to recompile or way to see them in the alpha channel.
|
|
|
|
Regarding the NSApplication.Init , it's because Growl must be configure -i.e. calling Dlfcn.dlopen (path_to_growl_bin, 0); BEFORE the NSApplication.Init - see <A HREF="http://cocoa-mono.org/archives/254/growl-my-monomac-application-says/">http://cocoa-mono.org/archives/254/growl-my-monomac-application-says/</A> : "we load the framework BEFORE the NSApplication.Init(). I tried multiple places with no success until I finally had to ask on the MonoMac IRC channel to find the answer for this. "
|
|
This is why I'm calling it.
|
|
I'm sure I can remove it but i think it will need to extension point from the monomac addin to be called before the NSApplication.Init()
|
|
|
|
Regards,
|
|
Frederic
|
|
|
|
|
|
On 08/02/2011, at 6:21 AM, Michael Hutchinson wrote:
|
|
|
|
><i> On Mon, Feb 7, 2011 at 8:09 AM, frederic forjan <<A HREF="http://lists.ximian.com/mailman/listinfo/mono-osx">fforjan at free.fr</A>> wrote:
|
|
</I>>><i> * saving document is done by AppleScript. I've discovered and do my first
|
|
</I>>><i> AppleScript for this usage. And at the same start I've done a very basic
|
|
</I>>><i> binding for the NSAppleScript object.
|
|
</I>>><i> There is a bug in my binding, if the script running an error, it will
|
|
</I>>><i> crashed. This is due of my NSAppleScript binding, I didn't find how to bind
|
|
</I>>><i> a pointer of pointer of NSDictionary - means ref NSDictionary in C# ?
|
|
</I>><i>
|
|
</I>><i> FWIW, you can find a more direct AppleScript binding here:
|
|
</I>><i> <A HREF="https://github.com/mono/monodevelop/blob/master/main/src/addins/MacPlatform/Framework/AppleScript.cs">https://github.com/mono/monodevelop/blob/master/main/src/addins/MacPlatform/Framework/AppleScript.cs</A>
|
|
</I>><i>
|
|
</I>>><i> Some remarks :
|
|
</I>>><i> -----
|
|
</I>>><i> * Since the monomac dll is delivered with the addin, What happens if two
|
|
</I>>><i> addins use two differents monomac (or the same) dll ? Are they shared ?
|
|
</I>>><i> Should it be installed in the GAC ?
|
|
</I>><i>
|
|
</I>><i> Ideally, you should not bundle MonoMac. You should instead depend on
|
|
</I>><i> an addin that includes MonoMac.dll. When that addin is loaded, its
|
|
</I>><i> MonoMac.dll will also be loaded. Then, your addin will resolve that
|
|
</I>><i> MonoMac dll.
|
|
</I>><i>
|
|
</I>><i> In MD master, MacPlatform addin references MonoMac.dll, for native
|
|
</I>><i> dialogs. Since MD master will soon become MD 2.6, I recommend you
|
|
</I>><i> target that.
|
|
</I>><i>
|
|
</I>>><i> * There is a NSApplication.Init call also in my addin. How is it working
|
|
</I>>><i> with the NSApplication from the Mac platform ? Is there any conflict ?
|
|
</I>><i>
|
|
</I>><i> In MD master, the MacPlatform addin calls NSApplication.Init at the
|
|
</I>><i> appropriate point, so it should not be necessary for you to call it
|
|
</I>><i> again.
|
|
</I>><i>
|
|
</I>>><i> I'm thinking it's linked but I was not able to use the shared NSWorkspace or
|
|
</I>>><i> the shared NSPasteBoard, MonoDevelop seems to wait indefinitely.
|
|
</I>><i>
|
|
</I>><i> This might be due to the fact that MD is built on GTK#, which uses
|
|
</I>><i> some Cocoa API internally but is not a true Cocoa app. Some things
|
|
</I>><i> work, some things don't. You'll need to investigate the hangs by
|
|
</I>><i> getting stack traces:
|
|
</I>><i> <A HREF="http://monodevelop.com/Developers/Reporting_Bugs#Debugging_Hangs_on_Mac_and_Linux">http://monodevelop.com/Developers/Reporting_Bugs#Debugging_Hangs_on_Mac_and_Linux</A>
|
|
</I>><i>
|
|
</I>>><i> I've mainly starting development on this platform - MonoDevelop, mono and
|
|
</I>>><i> mac ! so i'm happy to any feedback, positive or not.
|
|
</I>>><i> One of my question is, Is it a supported architecture ? Writting a plugin to
|
|
</I>>><i> an existing application to provide feature to the mac platform using monomac
|
|
</I>>><i> ?
|
|
</I>><i>
|
|
</I>><i> Yes, it is. Just beware that using Cocoa & Carbon APIs from a GTK# app
|
|
</I>><i> is not always easy.
|
|
</I>><i>
|
|
</I>>><i> Do you think it's useful ? Do you have any feedback on the feature, on the
|
|
</I>>><i> implementation ? Or any idea for new features ?
|
|
</I>>><i> I was thinking to be able to use the service menu like to send the currently
|
|
</I>>><i> selected text in email or the currently selected solution item as a mail
|
|
</I>>><i> with attachments, use the dock icon to display number of error from the last
|
|
</I>>><i> build.
|
|
</I>><i>
|
|
</I>><i> For "core" features that would be useful to everyone, like displaying
|
|
</I>><i> the number of build errors on the Dock Icon, or adding commands to the
|
|
</I>><i> dock icon's context menu, I would recommend contributing such features
|
|
</I>><i> to the MacPlatform addin so these features can ship with MD core.
|
|
</I>><i>
|
|
</I>><i> I don't want to ship Growl with MD though, so anything depending on
|
|
</I>><i> Growl would have to go in a separate addin, along with "powertoy"
|
|
</I>><i> features like send as email.
|
|
</I>><i>
|
|
</I>><i> --
|
|
</I>><i> Michael Hutchinson
|
|
</I>><i> <A HREF="http://mjhutchinson.com">http://mjhutchinson.com</A>
|
|
</I>
|
|
</PRE>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!--endarticle-->
|
|
<HR>
|
|
<P><UL>
|
|
<!--threads-->
|
|
<LI>Previous message: <A HREF="003982.html">[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac
|
|
</A></li>
|
|
<LI>Next message: <A HREF="004048.html">[Mono-osx] Introducing MacHint MonoDevelop addin - developed with MonoMac
|
|
</A></li>
|
|
<LI> <B>Messages sorted by:</B>
|
|
<a href="date.html#3986">[ date ]</a>
|
|
<a href="thread.html#3986">[ thread ]</a>
|
|
<a href="subject.html#3986">[ subject ]</a>
|
|
<a href="author.html#3986">[ author ]</a>
|
|
</LI>
|
|
</UL>
|
|
|
|
<hr>
|
|
<a href="http://lists.ximian.com/mailman/listinfo/mono-osx">More information about the Mono-osx
|
|
mailing list</a><br>
|
|
</body></html>
|