Closed didrocks closed 6 years ago
Okay, I think I understand your position. Switching to GNOME as the primary desktop is still an ongoing change for Ubuntu and you guys are doing big things.
For design, KDE Connect behaves a lot like bluez (pairing, capabilities, icon-properties, etc), so I think that's good prior art and familiar UX for users.
Regarding gnome-control-center/ubiquity, we now use GApplication (GAction/GMenu) and DBusObjectManager (like bluez). To support GNotifications (for different devices) all device actions can actually be run from a single GAction on the GApplication interface. I hope this will make it simpler.
Mostly we want to make this easy for you, so you can drop us a list of tasks/concerns and we can work them while you guys do your high-priority stuff. So if a designer just has 15mins to take screenshots with red arrows and say "look at how GNOME Contacts does this", we're happy to do that. We already get good tips from people like Piotr Dragr and that's worked well.
Hey!
First, thanks for this extension, it's really great overall and impressive that you were able to reimplement so much of the KDEconnect stack.
I'm going to package it and we'll evaluate it for default installation in ubuntu. However, trying latest git tip, I noticed that some features doesn't seem to work, despite the switch being on on both side, and dependencies installed (contact integrations, despite having the deps + gnome-contacts showing them, but nothing in the sms dialog, same with nautilus plugin integration and so on…)
The main features are working though. However, I saw that you mention your WIP branch, and wanted to have a little bit of vision on how/when you are targetting it. I read on the other issues that you want to first release a 12 release and then merging the WIP work. Do you have a rough ideas of the timeline? I didn't open dedicated bugs yet as I see quite some stacktraces (even in widgets) and I wanted to know if you would prefer us to wait for the WIP branch to land to include it by default? Meanwhile, I'll try at least for 18.10 to package it (even if the packaging seems a bit hard from reading other issues) so that it's available in an easy form, with some dependencies installed, to most of our user base.
Let me know what you think and how we can help you :)