Q-Mobile / QGrid

🎛 QGrid: The missing SwiftUI collection view.
MIT License
1.64k stars 104 forks source link

Cocoapods support? #9

Closed plivesey closed 4 years ago

plivesey commented 4 years ago

This library looks awesome, but probably not going to use it without cocoapods support. For me, it's probably not worth using two dependency managers in the same project (especially with SPM being such a new technology).

I totally understand if you don't want to support multiple dependency managers, but if you did, you'd probably get more traction, usage, and PRs.

karolkulesza commented 4 years ago

Hi there,

SwiftUI is equally new technology as SPM 😆 Feel free to contribute to this project by creating a PR, if you see there is any issue. I'm currently focused on QDesigner Beta (https://Q-Mobile.IT/Q-Designer).

Best, Karol

plivesey commented 4 years ago

👍 true. And thanks. Good luck with q designer.

On Thu, Oct 3 2019 at 12:53 PM, < notifications@github.com > wrote:

Hi there,

SwiftUI is equally new technology as SPM 😆 Feel free to contribute to this project by creating a PR, if you see there is any issue. I'm currently focused on QDesigner Beta ( https://Q-Mobile.IT/Q-Designer ).

Best, Karol

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub ( https://github.com/Q-Mobile/QGrid/issues/9?email_source=notifications&email_token=AAJQ2TOGOZE5U6PAYX4EXDDQMZEUZA5CNFSM4IXDHHZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAJMRQQ#issuecomment-538101954 ) , or mute the thread ( https://github.com/notifications/unsubscribe-auth/AAJQ2TPDQ7BNCO47366FYZ3QMZEUZANCNFSM4IXDHHZA ).

fbartho commented 4 years ago

As a counterpoint, while I'm thrilled that cocoapods existed in a time before SPM, I really think it has aged out. Cocoapods caused/causes so much maintenance and weirdness that I'd really prefer to avoid it in all my projects.

Anyhow, just putting a different thought out there -- not trying to start a flamewar!

karolkulesza commented 4 years ago

Closing, as this is not an issue, but a feature request (to be potentially implemented by the community in the future).