#appkit — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #appkit, aggregated by home.social.
-
I want `allowsDuplicatesInToolbar` and `NSToolbarItem.Identifier.separator` and `NSToolbarItem.Identifier. customizeToolbar` to not be deprecated anymore for NSToolbar :(
-
I want `allowsDuplicatesInToolbar` and `NSToolbarItem.Identifier.separator` and `NSToolbarItem.Identifier. customizeToolbar` to not be deprecated anymore for NSToolbar :(
-
I want `allowsDuplicatesInToolbar` and `NSToolbarItem.Identifier.separator` and `NSToolbarItem.Identifier. customizeToolbar` to not be deprecated anymore for NSToolbar :(
-
I want `allowsDuplicatesInToolbar` and `NSToolbarItem.Identifier.separator` and `NSToolbarItem.Identifier. customizeToolbar` to not be deprecated anymore for NSToolbar :(
-
I want `allowsDuplicatesInToolbar` and `NSToolbarItem.Identifier.separator` and `NSToolbarItem.Identifier. customizeToolbar` to not be deprecated anymore for NSToolbar :(
-
Thank god for this archaic 20+ year old API on NSSearchField… however... the position of the menu is questionable. 😅 Oh well, I don't have control over that part.
-
Thank god for this archaic 20+ year old API on NSSearchField… however... the position of the menu is questionable. 😅 Oh well, I don't have control over that part.
-
Thank god for this archaic 20+ year old API on NSSearchField… however... the position of the menu is questionable. 😅 Oh well, I don't have control over that part.
-
Thank god for this archaic 20+ year old API on NSSearchField… however... the position of the menu is questionable. 😅 Oh well, I don't have control over that part.
-
Thank god for this archaic 20+ year old API on NSSearchField… however... the position of the menu is questionable. 😅 Oh well, I don't have control over that part.
-
I was doing a Recent Searches menu for my AppKit Search Field... The API is a bit odd... very un-AppKit... but I found this super helpful doc. Of course it is the Documentation Archive Apple still has up...
See: “Configuring a Menu Template”
But this was initially published in 2003!!! The API is pretty much the same for at least 23 years now!!! 🤯
Anyway, it was to add this menu when you click on the Magnifying Glass icon.
-
I was doing a Recent Searches menu for my AppKit Search Field... The API is a bit odd... very un-AppKit... but I found this super helpful doc. Of course it is the Documentation Archive Apple still has up...
See: “Configuring a Menu Template”
But this was initially published in 2003!!! The API is pretty much the same for at least 23 years now!!! 🤯
Anyway, it was to add this menu when you click on the Magnifying Glass icon.
-
I was doing a Recent Searches menu for my AppKit Search Field... The API is a bit odd... very un-AppKit... but I found this super helpful doc. Of course it is the Documentation Archive Apple still has up...
See: “Configuring a Menu Template”
But this was initially published in 2003!!! The API is pretty much the same for at least 23 years now!!! 🤯
Anyway, it was to add this menu when you click on the Magnifying Glass icon.
-
I was doing a Recent Searches menu for my AppKit Search Field... The API is a bit odd... very un-AppKit... but I found this super helpful doc. Of course it is the Documentation Archive Apple still has up...
See: “Configuring a Menu Template”
But this was initially published in 2003!!! The API is pretty much the same for at least 23 years now!!! 🤯
Anyway, it was to add this menu when you click on the Magnifying Glass icon.
-
I was doing a Recent Searches menu for my AppKit Search Field... The API is a bit odd... very un-AppKit... but I found this super helpful doc. Of course it is the Documentation Archive Apple still has up...
See: “Configuring a Menu Template”
But this was initially published in 2003!!! The API is pretty much the same for at least 23 years now!!! 🤯
Anyway, it was to add this menu when you click on the Magnifying Glass icon.
-
Another HacKit detail I’ve wanted to improve for years is finally done.
The Appearance pane used to hide the author badge colours inside a pop-up button. I’ve replaced it with coloured radio buttons, so the whole palette is visible at a glance and changing colour is immediate.
A small change, but exactly the kind of detail I care about in a native Mac app.
Coming in the next major HacKit update.
-
Another HacKit detail I’ve wanted to improve for years is finally done.
The Appearance pane used to hide the author badge colours inside a pop-up button. I’ve replaced it with coloured radio buttons, so the whole palette is visible at a glance and changing colour is immediate.
A small change, but exactly the kind of detail I care about in a native Mac app.
Coming in the next major HacKit update.
-
Another HacKit detail I’ve wanted to improve for years is finally done.
The Appearance pane used to hide the author badge colours inside a pop-up button. I’ve replaced it with coloured radio buttons, so the whole palette is visible at a glance and changing colour is immediate.
A small change, but exactly the kind of detail I care about in a native Mac app.
Coming in the next major HacKit update.
-
Another HacKit detail I’ve wanted to improve for years is finally done.
The Appearance pane used to hide the author badge colours inside a pop-up button. I’ve replaced it with coloured radio buttons, so the whole palette is visible at a glance and changing colour is immediate.
A small change, but exactly the kind of detail I care about in a native Mac app.
Coming in the next major HacKit update.
-
Another HacKit detail I’ve wanted to improve for years is finally done.
The Appearance pane used to hide the author badge colours inside a pop-up button. I’ve replaced it with coloured radio buttons, so the whole palette is visible at a glance and changing colour is immediate.
A small change, but exactly the kind of detail I care about in a native Mac app.
Coming in the next major HacKit update.
-
One feature I’ve wanted to add to HacKit for years is finally done.
The next major update introduces the Find Bar, so finding text in stories works just as you expect.
Getting NSTextFinder working outside of NSTextView was a challenge, but I’m delighted with the result.
#HacKit #AppKit #Cocoa #Swift #NSTextFinder #MacDev #macOSDev
-
One feature I’ve wanted to add to HacKit for years is finally done.
The next major update introduces the Find Bar, so finding text in stories works just as you expect.
Getting NSTextFinder working outside of NSTextView was a challenge, but I’m delighted with the result.
#HacKit #AppKit #Cocoa #Swift #NSTextFinder #MacDev #macOSDev
-
One feature I’ve wanted to add to HacKit for years is finally done.
The next major update introduces the Find Bar, so finding text in stories works just as you expect.
Getting NSTextFinder working outside of NSTextView was a challenge, but I’m delighted with the result.
#HacKit #AppKit #Cocoa #Swift #NSTextFinder #MacDev #macOSDev
-
One feature I’ve wanted to add to HacKit for years is finally done.
The next major update introduces the Find Bar, so finding text in stories works just as you expect.
Getting NSTextFinder working outside of NSTextView was a challenge, but I’m delighted with the result.
#HacKit #AppKit #Cocoa #Swift #NSTextFinder #MacDev #macOSDev
-
One feature I’ve wanted to add to HacKit for years is finally done.
The next major update introduces the Find Bar, so finding text in stories works just as you expect.
Getting NSTextFinder working outside of NSTextView was a challenge, but I’m delighted with the result.
#HacKit #AppKit #Cocoa #Swift #NSTextFinder #MacDev #macOSDev
-
I wish Apple would still provide documentation with this level of detail... I mean, look at the start of this index page...
• Advantages of using bindings
• A simple example
• Why are NSControllers useful?
• Real-world example
• How do Bindings work?
• Bindings in more detail
...
• Troubleshooting (WHAAAT?!)etc etc.
Just imagine if we had documentation like this today for all of Apple's technologies. Would be so amazing.
#macOS #MacOSX #MacDev #AppKit #CocoaBindings
https://leopard-adc.pepas.com/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.pdf
-
I wish Apple would still provide documentation with this level of detail... I mean, look at the start of this index page...
• Advantages of using bindings
• A simple example
• Why are NSControllers useful?
• Real-world example
• How do Bindings work?
• Bindings in more detail
...
• Troubleshooting (WHAAAT?!)etc etc.
Just imagine if we had documentation like this today for all of Apple's technologies. Would be so amazing.
#macOS #MacOSX #MacDev #AppKit #CocoaBindings
https://leopard-adc.pepas.com/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.pdf
-
I wish Apple would still provide documentation with this level of detail... I mean, look at the start of this index page...
• Advantages of using bindings
• A simple example
• Why are NSControllers useful?
• Real-world example
• How do Bindings work?
• Bindings in more detail
...
• Troubleshooting (WHAAAT?!)etc etc.
Just imagine if we had documentation like this today for all of Apple's technologies. Would be so amazing.
#macOS #MacOSX #MacDev #AppKit #CocoaBindings
https://leopard-adc.pepas.com/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.pdf
-
I wish Apple would still provide documentation with this level of detail... I mean, look at the start of this index page...
• Advantages of using bindings
• A simple example
• Why are NSControllers useful?
• Real-world example
• How do Bindings work?
• Bindings in more detail
...
• Troubleshooting (WHAAAT?!)etc etc.
Just imagine if we had documentation like this today for all of Apple's technologies. Would be so amazing.
#macOS #MacOSX #MacDev #AppKit #CocoaBindings
https://leopard-adc.pepas.com/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.pdf
-
I wish Apple would still provide documentation with this level of detail... I mean, look at the start of this index page...
• Advantages of using bindings
• A simple example
• Why are NSControllers useful?
• Real-world example
• How do Bindings work?
• Bindings in more detail
...
• Troubleshooting (WHAAAT?!)etc etc.
Just imagine if we had documentation like this today for all of Apple's technologies. Would be so amazing.
#macOS #MacOSX #MacDev #AppKit #CocoaBindings
https://leopard-adc.pepas.com/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.pdf
-
RE: https://mastodon.social/@marioguzman/116950572824369906
I have fully refactored my upcoming app's sidebar to use NSTreeController + Cocoa Bindings to my NSOutlineView.
A bit of a learning curve but I do think my code is cleaner and I have all my functions like drag + drop, inserting + deleting rows, preserving collapsed state, contextual menus per item type all still working as before. Tested across Sequoia, Tahoe, and Golden Gate and the UI just updates "auto-magically" 😄.
Totally worth reading all I could find on NSTreeController.
#macOS #AppKit -
RE: https://mastodon.social/@marioguzman/116950572824369906
I have fully refactored my upcoming app's sidebar to use NSTreeController + Cocoa Bindings to my NSOutlineView.
A bit of a learning curve but I do think my code is cleaner and I have all my functions like drag + drop, inserting + deleting rows, preserving collapsed state, contextual menus per item type all still working as before. Tested across Sequoia, Tahoe, and Golden Gate and the UI just updates "auto-magically" 😄.
Totally worth reading all I could find on NSTreeController.
#macOS #AppKit -
RE: https://mastodon.social/@marioguzman/116950572824369906
I have fully refactored my upcoming app's sidebar to use NSTreeController + Cocoa Bindings to my NSOutlineView.
A bit of a learning curve but I do think my code is cleaner and I have all my functions like drag + drop, inserting + deleting rows, preserving collapsed state, contextual menus per item type all still working as before. Tested across Sequoia, Tahoe, and Golden Gate and the UI just updates "auto-magically" 😄.
Totally worth reading all I could find on NSTreeController.
#macOS #AppKit -
RE: https://mastodon.social/@marioguzman/116950572824369906
I have fully refactored my upcoming app's sidebar to use NSTreeController + Cocoa Bindings to my NSOutlineView.
A bit of a learning curve but I do think my code is cleaner and I have all my functions like drag + drop, inserting + deleting rows, preserving collapsed state, contextual menus per item type all still working as before. Tested across Sequoia, Tahoe, and Golden Gate and the UI just updates "auto-magically" 😄.
Totally worth reading all I could find on NSTreeController.
#macOS #AppKit -
RE: https://mastodon.social/@marioguzman/116950572824369906
I have fully refactored my upcoming app's sidebar to use NSTreeController + Cocoa Bindings to my NSOutlineView.
A bit of a learning curve but I do think my code is cleaner and I have all my functions like drag + drop, inserting + deleting rows, preserving collapsed state, contextual menus per item type all still working as before. Tested across Sequoia, Tahoe, and Golden Gate and the UI just updates "auto-magically" 😄.
Totally worth reading all I could find on NSTreeController.
#macOS #AppKit -
@DebianAstro To tag it for better availability: This is a #Cocoa and #GNUstep application.
-
@DebianAstro To tag it for better availability: This is a #Cocoa and #GNUstep application.
-
@DebianAstro To tag it for better availability: This is a #Cocoa and #GNUstep application.
-
@DebianAstro To tag it for better availability: This is a #Cocoa and #GNUstep application.
-
@DebianAstro To tag it for better availability: This is a #Cocoa and #GNUstep application.
-
@bwebster @mjtsai – So far getting exactly what I need using bindings and NSTreeController just fine. I can add to my backing tree and have it just do its thing to update the UI for me. Menus works perfectly… Collapsed state persisting between app launches is working as expected... The last thing I need is to check if drag and drop into a leaf node works. If it does, I am all set. But so far, it's working nicely! :)
-
@bwebster @mjtsai – So far getting exactly what I need using bindings and NSTreeController just fine. I can add to my backing tree and have it just do its thing to update the UI for me. Menus works perfectly… Collapsed state persisting between app launches is working as expected... The last thing I need is to check if drag and drop into a leaf node works. If it does, I am all set. But so far, it's working nicely! :)
-
@bwebster @mjtsai – So far getting exactly what I need using bindings and NSTreeController just fine. I can add to my backing tree and have it just do its thing to update the UI for me. Menus works perfectly… Collapsed state persisting between app launches is working as expected... The last thing I need is to check if drag and drop into a leaf node works. If it does, I am all set. But so far, it's working nicely! :)
-
@bwebster @mjtsai – So far getting exactly what I need using bindings and NSTreeController just fine. I can add to my backing tree and have it just do its thing to update the UI for me. Menus works perfectly… Collapsed state persisting between app launches is working as expected... The last thing I need is to check if drag and drop into a leaf node works. If it does, I am all set. But so far, it's working nicely! :)
-
@bwebster @mjtsai – So far getting exactly what I need using bindings and NSTreeController just fine. I can add to my backing tree and have it just do its thing to update the UI for me. Menus works perfectly… Collapsed state persisting between app launches is working as expected... The last thing I need is to check if drag and drop into a leaf node works. If it does, I am all set. But so far, it's working nicely! :)
-
I read somewhere (forget where), that if you use NSOutlineView w/ NSTreeController, that the collapsed state for groups would be persisted for you if you only set `autosaveExpandedItems` + `autosaveName`.
Except I haven't found this to be the case and I have to manually override the persistent for id/object data source functions myself. Which is fine; very straightforward.
But just wondering if this is correct/incorrect... it works; but it goes against what I previously read.
-
I read somewhere (forget where), that if you use NSOutlineView w/ NSTreeController, that the collapsed state for groups would be persisted for you if you only set `autosaveExpandedItems` + `autosaveName`.
Except I haven't found this to be the case and I have to manually override the persistent for id/object data source functions myself. Which is fine; very straightforward.
But just wondering if this is correct/incorrect... it works; but it goes against what I previously read.
-
I read somewhere (forget where), that if you use NSOutlineView w/ NSTreeController, that the collapsed state for groups would be persisted for you if you only set `autosaveExpandedItems` + `autosaveName`.
Except I haven't found this to be the case and I have to manually override the persistent for id/object data source functions myself. Which is fine; very straightforward.
But just wondering if this is correct/incorrect... it works; but it goes against what I previously read.
-
I read somewhere (forget where), that if you use NSOutlineView w/ NSTreeController, that the collapsed state for groups would be persisted for you if you only set `autosaveExpandedItems` + `autosaveName`.
Except I haven't found this to be the case and I have to manually override the persistent for id/object data source functions myself. Which is fine; very straightforward.
But just wondering if this is correct/incorrect... it works; but it goes against what I previously read.
-
I read somewhere (forget where), that if you use NSOutlineView w/ NSTreeController, that the collapsed state for groups would be persisted for you if you only set `autosaveExpandedItems` + `autosaveName`.
Except I haven't found this to be the case and I have to manually override the persistent for id/object data source functions myself. Which is fine; very straightforward.
But just wondering if this is correct/incorrect... it works; but it goes against what I previously read.
-
-
-
-
-