I'm looking to add the availability to my application to receive content through share option from Note native apple application. I want my application appear in the list below.
Thanks, Robin.
You need to add the new project with the share extension and reference it in the main project.
One more critical part is that you need to declare in extension's info.plist which content you want to import.
Also of note, you indicated by the tag that you use Xamarin.Forms. It might be complicated to use Xamarin.Forms for the user interface in the Mac share extension. I would believe it is possible, but I don't think anyone did that and published info on how to do it.
I am looking for a resource (link, website, document, another stackoverflow thread etc.) which can tell me how to set up the Portable Class Library targets so that it can be compatible with specific version of NuGet Package of Microsoft.IdentityModel.Clients.ActiveDirectory.
Just in case whoever stumbling upon same issue, found a good link describing the fix.
http://www.appzinside.com/2016/08/12/installing-adal-nuget-package-for-portable-xamarin-project-causes-an-error/
A client of mine who has a Mail plugin ("unofficial" of course since Apple does not provide support for mail plugin) wants me to update its pluginto Sierra.
When I look at the code swizzled, I see that one of the main classes he used is the SignatureBundle, which inherits from MVMailBundle. In this class, we can find many signature related functions like addSIgnature, signatureWithId and accountsEmails.
My problem is that this class no longer exists on Sierra, and I can't find any other class that I can use.
Do you have any clue that would help me figure out who to update his plugin? I know it is not official SDK, but who knows, maybe one of you already tried to update a mail plugin
Thanks for your help
As you rightly say, the SignatureBundle class is no longer present inside Mail's main executable. Such is life when you are using undocumented classes. :-)
Best advice I can give you is to take a look at the Mail-related frameworks inside /System/Library/PrivateFrameworks. If you are lucky, Apple may have simply moved this class into one of the private frameworks. However, if you are using NSClassFromString to find the class and getting nil back, then you're probably out of luck.
In which case, it's a long, tedious trawl around in the innards looking for the exact functionality you want. Your best bet in this case is Mail.framework itself. It contains a couple of hopeful-looking classes called MFSignature and MFSignatureManager. Some disassembly required...
I develop with Visual Studio. I have a class library that contains code common to many products I develop, and is now in use by 15+ solutions. I do LOB apps for my non-software company.
I've been adding this class library project directly to the solutions of all the solutions that need to use it. But I've been using NuGet to pull in many 3rd party packages and I really like its way of doings things. I'm thinking about adding this utility library as a NuGet package in our own repository rather than adding it directly as a project reference in the solution.
Is this a good idea? What criteria should I use to determine when to use NuGet vs when not to for internal class libraries? I realize that some might think this is an opinion based question, but I'm looking for specifically what criteria you'd use to decide rather than opinions about which is better.
Internal libraries that used and worked on by multiple teams can be exposed as Nuget packages. This way, multiple teams can work on the library, and each of them can update to a version as and when needed by that particular team.
Someone on here recently recommended BWToolkit, and it really impressed me, so I started googling for more IB plug-ins. I've found a couple on random blogs, but haven't been able to find any kind of repository/aggregator for them. Anyone know where I can find more of these?
Thanks.
I just created a page on CocoaDev to list them [edit: question originally just said “Interface Builder plug-ins”, did not mention Cocoa frameworks], with the two I know of listed.
Well that's a good start. I guess that wiki page is the de-facto repository, for now. Seems like there's not much out there.
You are not looking for Interface Builder plug-ins. You think you are, but you aren't. BWToolkit, the example you use in your question, is not an Inteface Builder plug-in. Brandon bills it as an Interface Builder plug-in but it is actually a framework and a plug-in. The framework contains the actual controls. The plug-in contains the integration with Interface Builder.
So really, what you are looking for are frameworks that contain or provide Interface Builder plug-ins. I have changed your question to reflect that, so it is more likely to be found by people using Google to search for similar things in the future.
I know what I am looking for. Not all frameworks contain IB plugins. I am looking for a specific subset of frameworks, those which contain IB plugins. An IB-plugin without a framework is useless, therefore the framework part is assumed. I am NOT looking for regular old frameworks, so stop trying to change my question to that. Your additions only seem to be confusing people.
I have reported your post, hopefully moderators will be able to stop your obnoxious behavior.
"Without a framework, what would you have to plug in to IB?"
Your words, not mine. Anyways, I'm done arguing this with you. Just remember that I can roll back for every time that you edit.
It's clear you have a lot of experience in this field, but instead of offering answers you decided to nitpick where there are no nits to pick.
Additionally, you have not "changed the question to refelct that," you have changed the question to a completely different question. I would have though that after four rollbacks you would relaize that you're doing more harm than good. Just stop, okay?
Of course, Chris Hanson is absolutely correct when he says that an Interface Builder plugin is useless without an accompanying framework. Interface Builder merely provides a graphical way to manage objects in a framework; without the framework itself, Interface Builder has nothing to manage.
However, I do think that there is a completely valid sort of Interface Builder plugin that wouldn't necessitate the installation of an accompanying framework, and that would be one that provides Interface Builder integration features for objects in Cocoa/Cocoa Touch which would otherwise appear as just generic objects.
For those of you who come to this page Google, please recognise the difference between Interface Builder plugins and frameworks: even the examples mentioned above work on frameworks (they could be Foundation, AppKit, UIKIt, etc.)