Multiple third-party macOS apps now have a feature to edit photos, and the UI looks exactly the same as in Preview. How do we implement this functionality? Has a new framework been released?
Including links to screenshots for comparison. Some buttons are not included in the third-party app, but the UI and the behaviour is exactly the same in both apps.
Shotty (3rd party app) image editing controls
Apple Preview image editing controls
Your help would be greatly appreciated, a link to Apple documentation would already be helpful.
Related
I have a legacy safari extension which I need to convert into Safari App Extension to submit into Extension Gallery. I am new to Xcode therefore, not familiar with it's build and run process. I tried looking into official documentation from developer.apple.com but it is so abstract.
Why do we need to create a parent app in Xcode before creating a
safari extension target?
If so what parent app template should I
choose? Cocoa App?
Where I can find starter tutorials on Xcode?
What is the submission process to Extension Gallery?
How can add the extension under development to my safari through xcode for testing?
I heard they need the URL for extension to approval, when we are submitting extension through developer account why to host it on URL?
Any documentation or answers to the above questions would be very helpful. Thank you.
On 2. and 3, I had the same struggles - I wrote up a tutorial on basic style sheet injection in Safari App Extensions here: https://ulyngs.github.io/blog/posts/2018-11-02-how-to-build-safari-app-extensions/
I'm converting the legacy safari extension to safari app extension too and have some answers for your questions:
Because app extension is more as functional extension then safari browser extension and could bring more features to you. And as per Apple says: safari app extension gives more communication and data exchange between Safari and your native app, docs.
But I have no more ideas if you only want an extension for safari why this is only way to do extensions.
Yes, you should use the Cocoa App template. If you don't need the window for your app, you can remove it simply in Main.storyboard or make app as a "service".
A lot of docs from Apple I've read but understood a bit then expected. So I found some youtube channels (they are 2 or more years old but some things seems don't changed) Some vieos here and the Osx Dev Daily playlist on this channel. And of course official swift docs if you select swift for your app as PL.
I haven't read about this, but think it must be submitted with your Cocoa App.
First of all you should to run your app target and only after this you should run your extension target and choose "Safari" in showed window to run in. If you have no the signing at the moment so ensure to enable "Allow unsigned extensions" in Development > Allow unsigned extensions in Safari app.
Don't meet this info, could you share it, pls? (sry, don't have enough knowledges)
Hope, it helps to you!
P.S. also recomend to see the converting docs, but it may be insufficient for converting :)
EDIT: it's seems to be incorrect to remove app window or change the default menus created by Cocoa App template for app submit for App Store. Some people got negative decision of app submit because of menus changes of redundant items or app have poor functionality or has not it at all. So consider to read the submit docs.
Please, share your experience when you'll have success app submit!
EDIT 2: Today I found template in Xcode 10.1 that can be used for Safari Extensions directly. It is as previous workflow (template Cocoa App + add extension target) but there is safari extension target already included
The app window and menu is simplified for developers:
So you don't need work with your app and you can concentrate on extension only.
macOS apps, e.g. Photos.app, provide a help panel to the user
Is there a way to author such a Help Book in your own macOS app?
Is there a way to at least provide a toolbar to be used for a table of contents?
I am asking specifically about the UI and all the user interactions. Not how to generally create and register a helpbook.
Update
Here is what I’ve been able to find/gather/learn from others. A Help Book appears to run on a separate app/process called “HelpViewer”. Any Apple macOS app displaying a help makes use of a DDMViewerController that isn’t public.
There is an “app.css” and an “app.js” being used by the Apple macOS app “index.html” of the Apple Help Book. The Javascript one manipulates the DOM to create the “show-hide” link that toggles the Sidebar. Haven’t been able to find how to instruct HelpViewer to use a sidebar.
There is a WWDC talk from back in 2014, “Introducing the Modern WebKit API” that talks about “User Scripts” and “Script Messages” which allow communication between a Webview and Cocoa. https://developer.apple.com/videos/play/wwdc2014/206/
AFAICS, there is no way to have HelpViewer display a custom view or have a sidebar. My guess is that you would have to implement everything yourself. That is an NSSplitViewController, NSToolbar, NSOutlineView, any Javascript alongside the “app.css” to get the look and feel.
Currently it's not possible to implement the sidebar as shown in the Maps and other built-in macOS applications from 10.13 onward.
Versions of macOS from 10.10 (built-in applications) implement sidebar navigation with HTML and JavaScript, and Apple Help Viewer itself offers a window.HelpViewer object with some hooks that enable/disable the Help Viewer's table of contents button. Once enabled, it will callback into your own JavaScript where you can show/hide TOC via CSS or JS.
From approximately 10.10, Apple's non-built-in applications have also been using this technique. For example, iTunes and Xcode help both do this.
From 10.13, macOS has a newer version of Help Viewer that provides an actual Cocoa-native table of contents and windows splitter, as well as some new properties on window.HelpViewer; presumably these can be used to enable/disable the Cocoa sidebar and populate the TOC, but these are undocumented and I'm not sure anyone outside of Apple has been able to reverse-engineer this functionality yet.
And in any case, it wouldn't work if you offer Help Books to pre-10.13 users, and the use of undocumented API's restricts applications from the App Store (although, I'm not certain that Apple scans Help Book JavaScripts for API usage as part of their review).
(There are also a lot of other changes to how Apple's built-in application Help works now, too, but that's another topic entirely.)
Thus the answer for now is we can't, or shouldn't, or just don't know how. Alternatives include using something like using jekyll-apple-help (no affiliation) or Middlemac 3 (my project), or just rolling your own.
For those interested in knowing how Apple does it, I've documented a lot of it here (disclosure: link to my own website).
I'm not sure whether Apple's current applications still use it, but there is a very old API on macOS for Help Books. Apple has documentation on how to create them and some introduction. In short: Help books are standard HTML files with additional proprietary anchors. Those anchors are accessible via the class NSHelpManager, e.g. to open the help book at a specific page.
See also this question.
I've been working recently with Telerik UI for UWP on a personal app with a RadDataGrid component, but I can not find a method of exporting data to Excel format. Is this implemented the extension methods or the fuctionality was dropped? Could you please guide me about it? Thank you so much!
Currently, the UWP DataGrid doesn't have built-in exporting. We do have it logged in the Feedback Portal, you can add your "upvote" by clicking the Like button.
Side-note:
If you are using the open source version of UI for UWP (i.e. the nuget packages vs the Extensions SDK), StackOverflow is the correct place to ask questions.
If you have a licensed version (trial or paid), then you can submit a support ticket here (directly from the engineering team).
See here for the official support options.
Custom Color action buttons, transparent card background,full screen custom layout notifications.Changing card color,ttf fonts for texts. changing text color . placing on different areas.
are these things possible ??
if its , why we cant use .
if its not how these peoples used these things
I really wanted to develop apps with these features. but current public api is really bad.
it provides nothing at all.but when we see screenshots new beautiful features exists.
I liked google wear and i see future about it . but when we compare with samsung galaxy gear or sony smartwatch, development in public goes slow.Maybe google devs doing things at the background,but if we don't have resources,how can developers can build apps for it.
I shared a basic app with my wishes and ideas.nobody answered about 2 days on google+ no one cares about posts on google+.public support of google wear for developers is sucks at the moment.
I need more customizable things for android wear to build apps.
but in current stage,i can't do much things with it.
i wish we had these features in screenshots below..
Those things are still not possible with the current preview release of AndroidWear.
If you look closely, you'll see that they've been using photoshop (or some other photo editing software)
Using these templates to design an app for Android Wear.
And for testing the design on the watch they used Android Design Preview which is a tool that lets you mirror a portion of your desktop to your device:
Is there a framework, or are there some good tutorials that can help me to work with the home icons in iOS? I need to make an app that can group all the applications I have made.
Apple doesn't allow developers any access to the home screen, icons, icon positions or anything like that. Unless you're talking about on a jailbroken device, there is no way to do what you're asking.