| T4 | <m_aurel> Will Nemo Mobile be continued after the announcement of Jolla? https://blog.jolla.com/message-in-a-bottle/ | 07:59 |
|---|---|---|
| T4 | <akaWolf> why not | 08:00 |
| T4 | <m_aurel> Because Mer won't exist any more, but it would be migrated to Sailfish core. won't it? | 08:01 |
| r0kk3rz | it wont have any affect | 08:01 |
| r0kk3rz | the changes have already been done | 08:02 |
| T4 | <abranson> @m_aurel [Because Mer won't exist any more, but it would …], if anything, Nemo should get a boost. | 08:04 |
| T4 | <m_aurel> Ok. Sounds good. | 08:04 |
| T4 | <abranson> there's an opportunity to promote nemo within sailfish core as a fully open source alternative to silica and jolla's homescreen. i don't think there's much competition between the two as they attract very different audiences, and there's plenty of potential for benefit on both sides. if anyone has suggestions on how that might work, then | 08:10 |
| T4 | let me know. | 08:10 |
| T4 | <akaWolf> the main goal is the ability to seamlessly switch from Silica to Glacier | 08:13 |
| T4 | <m_aurel> We still think about shipping our device with Nemo Mobile. I hope to discuss this on our community event. | 08:13 |
| T4 | <akaWolf> and back | 08:13 |
| T4 | <akaWolf> using open core | 08:15 |
| T4 | <m_aurel> @akaWolf I thought Silica is on a different level. You mean a switch between the Glacier UX and the Sailfish UX? | 08:15 |
| T4 | <akaWolf> yep | 08:15 |
| T4 | <m_aurel> Because Silica is missing in Nemo Mobile, all Sailfish apps won't run. This is an issue for pushing NEmo Mobile as an alternative. | 08:16 |
| T4 | <akaWolf> fragmentation of the application market is a major issue | 08:17 |
| T4 | <m_aurel> I agree. | 08:17 |
| T4 | <akaWolf> which is going with the support of Jolla unfortunately | 08:17 |
| T4 | <akaWolf> stick with our own Silica without ability to switch to another one | 08:18 |
| T4 | <akaWolf> I'm not surprised why there are so little application developers | 08:19 |
| T4 | <akaWolf> so few* | 08:19 |
| T4 | <m_aurel> This is the "Nemo-Silica", isn't it? https://wiki.merproject.org/wiki/Qtquickcontrols-nemo | 08:19 |
| r0kk3rz | ish | 08:20 |
| r0kk3rz | that and the glacier ux homescreen | 08:21 |
| T4 | <akaWolf> something like so | 08:21 |
| T4 | <m_aurel> One of the suggested topics at our community event is to discuss a mapping library (maybe it's the wrong wording), a library, that ensures the compatibility. | 08:22 |
| T4 | <neochapay> What will be better use https://bugs.nemomobile.org/ or github issues ? | 08:24 |
| T4 | <akaWolf> @m_aurel [One of the suggested topics at our community e …], nice idea. but you need to support it, handle all changes in Silica. a lot of effort | 08:24 |
| T4 | <abranson> it would do everyone good to be able to support apps written with standard qtquick2 controls | 08:25 |
| T4 | <akaWolf> yep | 08:25 |
| T4 | <m_aurel> I'm afraid you are right. So we think, that we just offer an upgrade of the device to a community port of Sailfish. This should be feasable, shouldn't it? | 08:25 |
| T4 | <akaWolf> the best thing is to use standard controls | 08:25 |
| T4 | <m_aurel> @abranson So UBports apps should work, correct? | 08:26 |
| T4 | <akaWolf> with upstream what is lacked | 08:26 |
| T4 | <abranson> @m_aurel [@abranson So UBports apps should work, correct …], i think they have their own ubuntu components, don't they? | 08:26 |
| T4 | <neochapay> I want more and more often delete from that chat becouse on it we have only idle talk.... | 08:26 |
| T4 | <akaWolf> up to you | 08:27 |
| T4 | <akaWolf> @m_aurel [I'm afraid you are right. So we think, that we …], looks like | 08:27 |
| T4 | <minlexx> @abranson [i think they have their own ubuntu components, …], https://api-docs.ubports.com/sdk/apps/qml/index.html | 08:50 |
| T4 | <abranson> yeah I remember seeing them in ub qml | 08:52 |
| r0kk3rz | @abranson, the issue is that developers will likely choose to use silica anyway | 08:52 |
| r0kk3rz | @neochapay, do you need a nemo-developers channel ;) | 08:53 |
| T4 | <abranson> for sailfish apps, sure. but we already have apps such as fahrplan that support both, albeit not with common code | 08:55 |
| T4 | <abranson> i just see two separate domains. polished, productized, commercial sailfish, and standards focused, open source, hackable but a bit bleeding edge nemo. | 08:56 |
| T4 | <m_aurel> What's about the Sailfish community ports. They are something in between? | 08:58 |
| r0kk3rz | community rnd mostly | 08:58 |
| T4 | <neochapay> @r0kk3rz [@neochapay, do you need a nemo-developers chan …], yea.... | 09:00 |
| T4 | Dex Info (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) was added by: Dex Info (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) | 10:57 |
| T4 | <Dex Info (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me)> (Photo, 1280x615) http://3das7vpgt73yxclb6agz4sz2a2bt7bqqfjucjhhbb5jnndxcd4o4lfid.onion/346KAcio1D.png ✅ Good news guys! … ✅ We have announced the launch-testnet! … ✅ Our team announces AIRDROP 5,000 BTС and 20000 ETH … ✅ All info is here https://dex-testnet.net … ✅ Official group | 10:57 |
| T4 | t.me/joinchat/LD1AOlMv6gI7ArluU7XXnA | 10:57 |
| T4 | <Chipiguay> @eekkelund @toxip spam | 10:58 |
| T4 | <K31j0> Sometimes I want to purge the planet off people that create these freaking bots... | 10:58 |
| T4 | shieldy_bot was added by: toxip | 10:59 |
| T4 | <toxip> That should keep them at bay | 11:02 |
| T4 | <toxip> @eekkelund you need to give the bot admin permissions | 11:03 |
| T4 | <eekkelund> @toxip [@eekkelund you need to give the bot admin perm …], 👍 | 11:04 |
| T4 | <Chipiguay> Thank you guys | 11:05 |
| T4 | <toxip> Fwd from m_aurel: Hello Sailfish developers. Maybe someone is interested in our community event with a hackathon. http://volla.online/blog/files/community-days.html | 11:09 |
| T4 | <meierrom> @neochapay [I want more and more often delete from that ch …], I think it's important as well, sometimes. :)) | 11:55 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
