Ubuntu UI Toolkit - who would join me if I tried to move it to QQC?
-
@advocatux Nah. That is too picky. I've never heard of «suru» to reference «zurullo».
Another planet, another time, another universe!
-
I'm in. If I can help
-
@CiberSheep, maybe is not slang in the whole country but I've heard it in certain places like Andalusia.
-
@advocatux I would not worry at all. Not even a second about being «missunderstood» or laught at
Another planet, another time, another universe!
-
@Mitu said in Ubuntu UI Toolkit - who would join me if I tried to move it to QQC?:
Qt Quick Controls should be took as a base.
Why not kirigami?
https://techbase.kde.org/Kirigami
I was actually hoping to investigate that option in Yunit sometime in the future.
-
Yes, I know about Kirigami, haven't investigated it though. It raises a few questions:
- How themable is it? Would it be possible to style it to look exactly like Ubuntu UI toolkit looks now?
- Does it depend on KDE libraries? I'd like to avoid it with Suru Controls and depend only on pure Qt.
- How are its concepts close to Ubuntu's UI Toolkit? On the screenshots I can see headers, something that seems to look like adaptive page layout... would it be possible to add bottom edge components, list items swipable to both directions (left & right), context menus etc.? How extendable would Kirigami be?
If Kirigami could let achieve the goals I mentioned above, it could make a good base - however I'm not convinced yet. It's like extending an extension and it would make Suru dependent on yet another project. Some of the Kirigami navigaion concepts differ from UITK - could those moved from UITK coexist with them or replace them in those places where you used Suru's components instead of Kirigami's and blend well with the rest? Personally I prefer to depend on as little things as possible (and reasonable).
Sure, there is a possibility to use Kirigami as is or just create a Suru style for it - but this is not the goal I described and would like to achieve - to fulfill not only the Suru visuals, but also its design language and navigation concepts.
-
@CiberSheep, yeah it's definitely better "grief" in Finnish than "turd" in Spanish hahaha
-
@advocatux XD
I'm afraid that now we re the official «offtopic-ers»
-
@jsalatas I can really see the reasons why you're interested in Kirigami, it's a fast evolving project and embraces convergence. Since - that's what I understood - they will keep the same public APIs between version 1.0 and 2.0, Kirigami could make your life easier, since you could start using it now and be confident that your shell will support QQC2 in future (Kirigami 2 is based on QQC2 as well).
Anyway, I guess what @Mitu proposed here is in no way affiliated to UBports. I've been trying to port the Suru design to QQC2, and I'd honestly prefer as well to be fully indipendent on this, at least at first.
I don't know how Kirigami 2 will actually work but, if it will support the QQC2 styling framework, there might be some chance that a Suru theme would be equally supported.
-
i stumbled over this topic again after reading it with great interest when it was opened and now the team has forked UITK-1 (for documenting purposes i think) so i thought maybe it is time to talk about it again?
As far as i have seen it (yes i was stalking your github stefano ;-P) stefano has already begun with the project here, if you are still interested Mitu, maybe you can participate in the effort? I would like to help but cannot do much except perhaps gather info and trying to bring people with skills together (qed ;-)).
I also don't know whether this is old news for you but Canonical seems to have been working on the UITK-2, based on QQC2, maybe there are some things there that can be recycled?
BR, erik
-
Hello guys,
Any news about this thread?
Thanks.
-
I think @sverzegnassi has been working on the Suru style for QQC for some time. Would you share some information on what the status is and if anything has been done not only to style, but also SDK components (bottom edge, headers, swipeable list items etc.)?
I decided not to take up any work in it currently and focus on an idea that might someday evolve into a decent app. I'll not shere more information though, as there is still a long way ahead and the entire thing is uncertain.
But if the app will approach to materialization, I'll definitely consider implementing in QQC2 (if Suru style and component set is in good shape enough by this time), and maybe help out with the SDK in that time.
