Maccy 1.x and towards 2.x #790
Replies: 26 comments 39 replies
-
|
Sounds great! Looking forward to the next version! |
Beta Was this translation helpful? Give feedback.
-
|
I dont know why but i am unable to download the Maccy 2.0 version. I tried to restart and redownload it, nothing works. Could someone help me with it? |
Beta Was this translation helpful? Give feedback.
-
|
same |
Beta Was this translation helpful? Give feedback.
-
|
Me too. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also a part of the consesnsu, not able to download Maccy 2.0 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, that's because I pushed the update without releasing it. Please try again tomorrow! |
Beta Was this translation helpful? Give feedback.
-
|
Sound great! As a "maccy-heavy" user, would say it helps me a lot on software development. Although it works well with new tech stack e.g. SwiftUI, the issues on new |
Beta Was this translation helpful? Give feedback.
-
What issues are you referring to? Maccy is not using any complicated data queries so I believe it should be okay. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply! Disclaimer: I didn't dive deep into the code, so my comment is just opinon. I faced some issues when getting my hands dirty on SwiftData when it was first released last year. My assumption right now is: I can't give a very subtle opinion at this moment. But I agree that it is worth trying. |
Beta Was this translation helpful? Give feedback.
-
|
It was love at first sight with Maccy. I would love to and am really excited about the intentions for the application. Congratulations. |
Beta Was this translation helpful? Give feedback.
-
|
Looking forward to the iOS version 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
That’s great news. Let me know if you need any help. I still have cursor positioning in my backlog :D |
Beta Was this translation helpful? Give feedback.
-
|
That's amazing news, go ahead! and thanks for the effort |
Beta Was this translation helpful? Give feedback.
-
|
Alright, folks, I've had some progress with 2.x and I am now convinced it's possible to migrate to App Intents + SwiftData + SwiftUI for Maccy. In anticipation of 2.x, here is the promised 1.0.0 version - https://github.com/p0deje/Maccy/releases/tag/1.0.0. It's pretty much the same old Maccy with one major storage change that prevents older versions of Maccy from working with the storage after the upgrade. I'm fairly certain that's the only breaking change I need to do before 2.x, so 1.x upgrades should be smooth further on, respecting the semantic versioning. |
Beta Was this translation helpful? Give feedback.
-
|
If I understand correctly, the point being made here is that once you have upgraded to version 1.0 and are running once, then if you downgrade to version 0.x again it will not work. If that's the case, the wording in the release may need to be more explicitly stated, as that looks more like a warning that upgrading from 0.x to 1.0 will not work properly and will require some manual handling. People are unlikely to use both version 0.x and 1.0 at the same time (hence why we call it an upgrade) and most won't be downgrading to 0.x again, so the warning's prominent placement and somewhat ambiguous wording can make it easy to misinterpret. Finally, thank you for making this open source software. |
Beta Was this translation helpful? Give feedback.
-
Is this confusing? Some people might want to revert to 0.x if there is a bug in 1.0. |
Beta Was this translation helpful? Give feedback.
-
|
This language makes sense to me and isn't confusing. Thanks for all your hard work on this, super excited and love Maccy! |
Beta Was this translation helpful? Give feedback.
-
|
Sounds great! |
Beta Was this translation helpful? Give feedback.
-
|
Any privacy concerns we should be aware of? |
Beta Was this translation helpful? Give feedback.
-
|
What kind of concerns? There would be no changes in data collection - Maccy is not collecting any data about users, all the copied items are left on your computer. Maccy is running in App Sandbox which restricts network access, so it cannot send anything by design. The only exception for communication with external networks is downloading application updates. Adopting SwiftData would likely allow using iCloud for storage and synchronization of data between multiple Macs (#182). This would still use Apple's CloudKit and be opt-in. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Thanks for clarifying. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Sounds great! Huge fan. I'm not a developer, but if I can help some other way, let me know. |
Beta Was this translation helpful? Give feedback.
-
|
I would like to contribute, big fan of the project, but I will need some guidance in the start 😃 |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to grab any interesting issue that is marked with a "help wanted" label and ask specific questions, I'll do my best to guide you. |
Beta Was this translation helpful? Give feedback.
-
|
If anyone is up to try a new re-written beta version, please take a look at #818. This version can be run side-by-side with Maccy 1.0, so you should be able to test easily. It would be great if you could share the feedback on:
|
Beta Was this translation helpful? Give feedback.
-
|
This app is very good. It is a tool I have used for a long time. Does the 2.0 version consider cross-platform support, such as linux and windows? |
Beta Was this translation helpful? Give feedback.
-
|
No, that would require rewriting Maccy to use a cross-platform UI library such as QT. That's not my plans. However, 2.0 would open a possibility of porting Maccy to other operating systems in Apple ecosystem (iOS, IPadOS, etc) |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure iOS (-Appstore) would officially allow some app like that. Article about Clip: https://www.macstories.net/reviews/altstores-clip-is-the-best-clipboard-manager-on-ios-yet/ |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks for one of the most useful app, happy user for ~5 yrs. Just wanted to let you know 2.0 is failing to start on fresh 15.0 Beta (24A5298h). Keep on working and thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, can you share the logs fron Console.app? |
Beta Was this translation helpful? Give feedback.
-
|
I get just segmentation fault( |
Beta Was this translation helpful? Give feedback.
-
|
Maccy2-0-err.txt |
Beta Was this translation helpful? Give feedback.
-
|
Please try beta 2 - https://github.com/p0deje/Maccy/releases/tag/2.0.0.beta.2 - it should be fixed there. |
Beta Was this translation helpful? Give feedback.
-
|
Yup, fixed. Thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
|
For some reason the window is too narrow. And the 1.0.0 version too. The previous version I was using is 0.29.something. I would like to share any info to research this Screenshot
|
Beta Was this translation helpful? Give feedback.
-
|
@Lui22 Can you try changing it to 51 when running Maccy 1.0? |
Beta Was this translation helpful? Give feedback.
-
|
@p0deje changed and it fixed :) |
Beta Was this translation helpful? Give feedback.
-
|
@p0deje oh but the pinned one is still collapsed |
Beta Was this translation helpful? Give feedback.
-
|
@Lui22 You'd need to edit its title via Pins settings, not sure what caused this in the first place. |
Beta Was this translation helpful? Give feedback.
-
|
But it looks like a migration problem only. I unpinned and pinned it again and now everything is ok |
Beta Was this translation helpful? Give feedback.
-
|
It’s not released yet.
|
Beta Was this translation helpful? Give feedback.
-
|
Version 2 of Maccy is saying it's available to update to via Maccy in-app update but it is not working... |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, that's because I pushed the update without releasing it. Please try again tomorrow! |
Beta Was this translation helpful? Give feedback.
-
|
Paging @p0deje Update mechanism in Maccy is broken FYI |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, that's because I pushed the update without releasing it. Please try again tomorrow! |
Beta Was this translation helpful? Give feedback.
-
Absolutely no worries. I wanted to say thank you from the bottom of my heart for maintaining and having Maccy available to all for free. When I get a job I put you on my donate list. ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
2.0.0 is finally out, you can upgrade. Please share your feedback and open issues for bugs you encounter or missing features. |
Beta Was this translation helpful? Give feedback.
-
|
While I think Maccy is a great app, I'm not a fan of using non-stable OS's (yea, I'm looking at you Sonoma), so I don't plan to move to that System for the next two years (yes, I'm really that drastic). My question is: are there any plans to update version 1.x with bug fixes, or it's the final version? |
Beta Was this translation helpful? Give feedback.
-
|
@TickDracy Do you have specific bugs you would like to be fixed? Many of them are limitations of 1.0 architecture and cannot be fixed without a rewrite such as 2.0. |
Beta Was this translation helpful? Give feedback.
-
Hi @p0deje, no, I don't have any specific bug. It was just a question to analyze the future of the app, and if I should continue using it, or find an alternative, given that I've recently moved into macOS Ventura, and I will (definitely) take a long time until I reach the version supported by Maccy 2.0. My only annoyance (not with Maccy, more of a Bitwarden issue) is that when I copy passwords from the browser extension, they get added into Maccy. While I can avoid this on the Desktop application (by adding it to the exclusion), I don't find a way to do this for the browser extensions. But like I said, I don't think this is an issue with Maccy itself... |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that last part is super annoying, but probably it can only be solved on Bitwarden side, if at all. |
Beta Was this translation helpful? Give feedback.
-
I would consider 1.0 a fairly stable release with the only issues being related to architecture (cannot popup over password fields, memory utilization is not optimal, application focus issues). Those are not going to be fixed, but I can try fixing other issues in 1.0 unless they require a lot of work.
That's a common issue for password managers used from the browser - there is no simple way to distinguish them from other copies coming from the browser itself. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @p0deje, I guess Apple's lack of quality on macOS took me by surprise. I should have waited for someone to test the latest Ventura update (I was not imaging they were breaking things on such an old system), but it messed up my system, so my only solution (aside from starting from scratch and trying to restore using Time Machine) was to update to macOS 14. I guess I have to eat my own words on the original plan of using Ventura for more than one year. The positive side is that I've got to upgrade Maccy to version 2.0. Not everything is negative in this story, I guess... |
Beta Was this translation helpful? Give feedback.
-
|
It's amazing how fast the search works. |
Beta Was this translation helpful? Give feedback.
-
|
@p0deje |
Beta Was this translation helpful? Give feedback.
-
|
This is the correct distribution team - I could not do it myself back then due to personal reasons. |
Beta Was this translation helpful? Give feedback.
-
|
Alright, thank you for confirming 👍🏻 |
Beta Was this translation helpful? Give feedback.
-
|
Dear Alex, first THAN YOU! I'm still using Maccy 0.16 with satisfaction on High Sierra; is there a following version for Mojave? |
Beta Was this translation helpful? Give feedback.
-
|
Version 1.0 requires Mojave, while 2.0 already needs Sonoma. |
Beta Was this translation helpful? Give feedback.
-
|
Dear Alex.
you are very kind as ever 🤗, not only very clever as I appreciate by years!
Thank you so much for your quick and gentle response!
GianMarco Tavazzani
via Bergamo, 10 - I-20900 Monza (MB)
whatsapp, Telegram (much better!), phone: +39 329 536 55 76
Skype: gianmarcotav, Google Chat: ***@***.*** com
… On 4 10 24, at 16:21, Alex Rodionov ***@***.***> wrote:
Version 1.0 requires Mojave, while 2.0 already needs Sonoma.
—
Reply to this email directly, view it on GitHub <#790 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAUZ3YU4D67AYVOYKNW27DZZ2QAHAVCNFSM6AAAAABJFE7FFWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBUGUYDINQ>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Alex, Does Maccy not work on macOS 15? I set the shortcut (⌥ + V) in the "General" settings to open it, but it doesn't take effect. |
Beta Was this translation helpful? Give feedback.
-
|
Apple prohibits all store apps from continuing to use |
Beta Was this translation helpful? Give feedback.
and others
-
Hello folks! 👋
Maccy was created 7 years ago as a hobby project where I attempted to learn Swift and macOS development to replace missing Parcellite clipboard manager when I moved from Linux to macOS. Since then, it has been download 600k+ times, got featured on the App Store and used by thousands of people every day. I've never thought it might become so popular. Thank you everyone for using it, it's an honor for me. 🙇
7 years is a lot of time and macOS has changed drastically since then. When I started, there were no SwiftUI, SwiftData and other modern approaches to developing AppKit applications. The way Maccy is built is based on the old NSMenu system that is used to power context menus in macOS. This allowed me to preserver plenty of backwards compatibility - Maccy still runs and works on older macOS 10.14 Mojave which was released in 2018. There are still some people downloading and using it on those versions, though it's just a fraction of usage compared to modern macOS.
The choice of NSMenu provided native UI so that Maccy is fast and feels like part of OS. However, it also caused multiple issues in the long run, some of which were worked around (e.g. support for Korean/Chinese language in search), while others are proven to be hard to work around (e.g. support for Japanese language). In summary, NSMenu were never designed to be used for such use cases and this caused plenty of problems with no straightforward way to work them around. I can elaborate more on these issues if necessary.
With all this technical debt and design limitations, I don't see a clear way forward rather than attempting to rewrite Maccy into a regular macOS application that uses regular windows and custom UI views for handling input events. In the very end, UI must remain the same so it's native and fast, but the underlying implementation must move away from NSMenu.
However, re-writing without using modern stack is quite painful so I'd like for Maccy to adopt all the recent SDKs by Apple, notably:
However, switching to these technologies comes at the price of dropping backwards compatibility. For example, SwiftData requires macOS 14 Sonoma or later. That's unavoidable even though I'd hate to do that. The installations per platform suggest that's acceptable - by the time rewrite is done the 90% of users would be using at least macOS 14. I don't have data for installations via Homebrew/GItHub, but on the App Store the downloads this year so far are the following:
With that said, my current plan is to:
I'd be happy to hear what Maccy users think about these plans!
Beta Was this translation helpful? Give feedback.
All reactions