Active Topics
-
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 15 hrs, 11 mins ago -
Porting apps to Leste (43)
to Maemo 7 / Leste by teroyk - 21 hrs, 33 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 1 day, 13 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 1 day, 13 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 1 day, 18 hrs ago -
Maemo repository (5)
to Community by dredlok706 - 4 days, 13 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 4 days, 16 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 6 days, 22 hrs ago - more...
 |
|
2009-05-14
, 20:12
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#2
|
Selling a device with some of these packages pre-installed might be tricky for a company...
The OS2008 Instant Messaging Upgrades had mixed results, some positive and so... so-la-la. How would you do it better in Fremantle? How a community project could integrate these protocols as add-ons?
Is it there enough developer energy to back this project? What are the obstacles that need to be removed in the RTComm framework and applications (if any)? What is the specific work that would be required in the related upstream projects (if any)?
One of the lessons learned with the RTComm is that there is indeed a user demand and the Telepathy ramifications have most of the elements to satisfy them. Maemo is a good customer of Telepathy and it makes sense to try out and experiment things here.
The OS2008 Instant Messaging Upgrades had mixed results, some positive and so... so-la-la. How would you do it better in Fremantle? How a community project could integrate these protocols as add-ons?
Is it there enough developer energy to back this project? What are the obstacles that need to be removed in the RTComm framework and applications (if any)? What is the specific work that would be required in the related upstream projects (if any)?
One of the lessons learned with the RTComm is that there is indeed a user demand and the Telepathy ramifications have most of the elements to satisfy them. Maemo is a good customer of Telepathy and it makes sense to try out and experiment things here.
| The Following 4 Users Say Thank You to qgil For This Useful Post: | ||
|
|
2009-05-14
, 21:03
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#3
|
I think there is certainly demand, developers just don't/(well didn't I suppose is better) know what will come on the device so can't really do anything.
So yes, we have the SDKs now, but there's still stuff which hasn't been released, if you can say that there's nothing else related to the messengering system to come then people will see that it's worth putting the time into it.
So yes, we have the SDKs now, but there's still stuff which hasn't been released, if you can say that there's nothing else related to the messengering system to come then people will see that it's worth putting the time into it.
| The Following 8 Users Say Thank You to lardman For This Useful Post: | ||
|
|
2009-05-14
, 21:12
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#4
|
In Fremantle the game hasn't changed much around these protocols discussed. The complementarity of -haze or -purple with the stock RTComm framework is the same.
The beta in OS2008 was useful to see not only that there was a user demand but also that the execution could not be done with Nokia alone (the protocols are many and the support of the original features is variable, while the user expectations are just as high than with the originals - supporting them officially is technically complex and also tricky business-wise). The question is whether the community alone can do it in Fremantle or there is anything the RTComm team needs to address or help with.
The beta in OS2008 was useful to see not only that there was a user demand but also that the execution could not be done with Nokia alone (the protocols are many and the support of the original features is variable, while the user expectations are just as high than with the originals - supporting them officially is technically complex and also tricky business-wise). The question is whether the community alone can do it in Fremantle or there is anything the RTComm team needs to address or help with.
 |
|
2009-05-14
, 21:24
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#5
|
Originally Posted by qgil
I think the Nokia response to problems with the OS2008 Instant Messaging Upgrades was fairly "so-la-la". The project started to "go stale" after the Diablo upgrade, with crucial small failures accumulating over the months, and like everything else pre-Fremantle, it has been completely abandoned now.
The OS2008 Instant Messaging Upgrades had mixed results, some positive and so... so-la-la. How would you do it better in Fremantle? How a community project could integrate these protocols as add-ons?
I'm very sad that there's no official plans to integrate any of these telepathy / pidgin features into Fremantle.
I guess we can always try to get the Empathy client integrated into the Maemo framework. This integration would centre around the address book, the A/V streaming, and the notification system...
EDIT: Hey, it looks like they're already using Nokia technology, in the form of Mission Control, to do the contacts management. Maybe not so hard to make it all work, after all!
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
Last edited by qole; 2009-05-14 at 21:32.
 |
|
2009-05-14
, 21:32
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#6
|
Empathy is still too basic to be any real good, but hey, RTComm beta was basic too.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
 |
|
2009-05-14
, 21:39
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#7
|
i really don't cary much for msn and stuff, but i loved having IRC in the telepathy framework. at least that should be considered. that and maybe telepathy-salut.
|
|
2009-05-14
, 21:57
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#8
|
Originally Posted by qole
Quoting myself in that bug report: As we can see with the history of this bug, it is better to leave to the community anything that is not part of the official product. Releases in the grey are problematic.
I think the Nokia response to problems with the OS2008 Instant Messaging Upgrades was fairly "so-la-la". The project started to "go stale" after the Diablo upgrade, with crucial small failures accumulating over the months, and like everything else pre-Fremantle, it has been completely abandoned now.
Specially the platform teams live most of the time in the future release compared to what users have. There are resources for maintenance but they focus on bugfixing the pre-installed/official packages.
See also that some of the answers in that bug come from a Collabora/upstream developer. They also need to focus in the bleeding edge, being less able to deal with maintenance. Still, I wonder if the Maemo community could have a more direct contact with the developers upstream without needing to knock Nokia's door (asking in practice to fix bugs that require to knock upstream's door).
I'm very sad that there's no official plans to integrate any of these telepathy / pidgin features into Fremantle.
I guess we can always try to get the Empathy client integrated into the Maemo framework. This integration would centre around the address book, the A/V streaming, and the notification system...
EDIT: Hey, it looks like they're already using Nokia technology, in the form of Mission Control, to do the contacts management. Maybe not so hard to make it all work, after all!
| The Following 3 Users Say Thank You to qgil For This Useful Post: | ||
|
|
2009-05-14
, 22:45
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#9
|
Originally Posted by qgil
Well, if you're asking me to limit myself, we're already starting to have problems. The point of the telepathy framework is the ability to provide a wide variety of clients to a single sign-in. So I would want the extra VoIP functionality provided with the Beta (Sofia-SIP), full Farsight (video/audio streaming) capability, plus the Haze plugins (ICQ, MSN, AIM, etc), and of course, link local (I think it is called "salut" in Telepathy). You should be able to scan the local WiFi network and see other people in your "neighbourhood" on your chat service...
Can you be more specific? Like sorting the features you would like to have best (like benny1967 is doing). I'm curious whether the priorities are the same or similar for everybody.
But just because I didn't mention one of the Telepathy-supported components doesn't mean it shouldn't be included. I guarantee there will be lots of people who would want the IRC plugin, "idle," included too.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2009-05-14
, 23:38
|
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#10
|
Originally Posted by qole
That's was only in beta around the the time of Bora actually (released at GUADEC 2007). It was officially included in OS2008, and works remarkably well :-)
So I would want the extra VoIP functionality provided with the Beta (Sofia-SIP)
All the current beta adds are a few pre-configured provider-specific profiles, and this teaser:
TLS - Use TLS SIP transport (Not supported yet)
TCP via HTTP proxy - Use TCP via HTTP proxy (Not supported yet)
TLS via HTTP proxy - Use TLS via HTTP proxy (Not supported yet)
I had even hoped for these components to be part of OS2008 some day (you know, them being released as "beta" suggested there'd be the day when they're considered stable and move into the core OS), but not finding them in what's known about Fremantle is a bit disappointing.