You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2021. It is now read-only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@RaymondLim Done with initial review. This info.plist change appears to work just fine, but I'll wait for you to respond to @eugeneo 's comment before deciding to merge this change.
in the case extensions add support to file types that are not currently supported.
Yes, my current change is exactly for file types that are not yet supported. So if an extension provides a pdf viewer or a video viewer, then the users should be able to view these file types with drag-and-drop on icon.
Thanks for pointing out "public.image" UTI. It's definitely better than listing individual image extensions, but I do have two concerns (or questions) for you.
What is the key if we switch to "public.image"? I think it has to be LSItemContentTypes instead of CFBundleTypeExtensions that I'm currently using.
"public.image" covers more extensions than we actually support in our preview image feature. Dropping an image file other than the extensions that I have will not show up in the image viewer in Brackets. So if we switch to "public.image", then users can use "Open With" in Finder for those image extensions that we don't yet supported. ( which I think is misleading)
I did not try public.image - I tried your change as is and then tried your change after removing CFBundleTypeExtensions with the list of image extensions - saw no difference. In both cases I was able to drop to Dock icon and to use Open With... and then browse to the application.
I just re-tested with @RaymondLim 's original changes and with removing individual and/or all of the CFBundleTypeExtensions. From what I can tell, you do need to enumerate specific extensions in order support Open With of those file types. Otherwise, Brackets does not appear in the Open With list.
One observation: the Finder appears to cache the file type associations, so you'll need to be sure to do the following before any changes are recognized by the system:
rebuild Brackets.app with your updated info.plist;
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Also allow user to use "Open With" for image file extensions. This fixes issue adobe/brackets#5759
@eugeneo Can you review this and comment if you see something not right?
@bchintx I think you should review this too.