View Single Post
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#10
Originally Posted by Modulebaan View Post
I understand your concerns but I want to keep Transponder separated from the integrated Telepathy stuff for several reasons:
  • Telepathy integration doesn't play well with Harbour and I really require this.
  • Depending on Telepathy implementation in SFOS, porting to UT, Plasma, ... is more difficult

Jolla's Telepathy doesn't support properly group chats, files sending like it should. Transponder should reach the state of Sailorgram (in the future)
According to Plasma Mobile page they also use Telepathy. From some old docs, looks like Ubuntu Touch used Telepathy.

I don't know about the differences in implementation between Plasma/SFOS/UT. Are there any examples?

What looks to me as a main advantage is that you can hook yourself to the existing components and expand as you progress. As for Store, I would suggest to be more critical in having it and not to spend too much time in playing by its rules. They are quite limiting and should not lead to bad design.

Originally Posted by MartinK View Post
Also if I remember correctly, there is still the closed source UI layer, so even if community implemented all the backend stuff, someone from Jolla would have to do the UI bits to actually make it useful, which is unfortunately very unlikely to happen given similar cases in the past.
This proposed messaging client will have to implement UI for messaging, UI for accounts, API to link multiple backends with the frontend, and battery-efficient backends. In that sense, using existing API and having to work with "just" UI is a simple undertaking, isn't it?

I agree with @Modulebaan in terms of keeping development easily relocatable - with significant closed source components we should be ready to move out from SFOS as a platform. So, having functional alternative UI would be handy.

Originally Posted by taixzo View Post
One of the features I've been trying to integrate into Saera is the ability to read texts aloud as they come in, or to send them with dictation. Will Transponder have a method to allow other apps to communicate with it?
@taixzo, what was the stumbling block? From all the overviews of Telepathy API it seems that it was designed to have multiple components interacting and it should support such feature out of the box.

As always, its up to the main dev to choose the direction and there are many factors in the equation, including learning-by-doing component. One aspect that I would like to bring out is that its a lot you could learn when working on bigger project that has its Q&A for the code and contributions well developed. Don't know much about telepathy, but I surely did learn much by working with the others and contributing to larger projects.

Whatever way you choose, good luck!
 

The Following 2 Users Say Thank You to rinigus For This Useful Post: