Re: Send-Only Accounts in Modest
On Sun, Jul 6, 2008 at 12:48 PM, Mike Lococo <[EMAIL PROTECTED]> wrote: >> For just a send-only account setting the incoming server to 127.0.0.1 >> seems to work fine for me. If you open up the main application you get >> the annoying popups but there isn't much need to do that. If you just >> compose and send email it stays quiet about it. > > I should have been more clear in the message that started this thread. I > did try using bogus mailserver information, and confirm that it does > "work" inasmuch as you can send and receive messages. However, Modest > throws two popups on startup/new-mail-check per bogus account, which are > very annoying and not possible for an end-user to disable. You were clear. I was just trying to point out that those popups can be avoided if you just choose the compose email option from the menu. That doesn't help folks who want to read mail also but makes them not annoying to those of us who just occasionally send mail from the tablet. John ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Send-Only Accounts in Modest
> For just a send-only account setting the incoming server to 127.0.0.1 > seems to work fine for me. If you open up the main application you get > the annoying popups but there isn't much need to do that. If you just > compose and send email it stays quiet about it. I should have been more clear in the message that started this thread. I did try using bogus mailserver information, and confirm that it does "work" inasmuch as you can send and receive messages. However, Modest throws two popups on startup/new-mail-check per bogus account, which are very annoying and not possible for an end-user to disable. I think there's a valid RFE here to provide either true sender identities, or the ability to disable automatic checking (both on startup and for the check new messages button). The latter would be a fairly trivial fix, although the former is probably the "right thing to do" in the long-run. Thanks, Mike Lococo ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Send-Only Accounts in Modest
On Sun, Jul 6, 2008 at 4:44 AM, Tony Green <[EMAIL PROTECTED]> wrote: > On Sunday 06 Jul 2008, [EMAIL PROTECTED] wrote: > >> Back on topic, am I really the only one with a mail setup like this? I >> thought it was a moderately common arrangement. Or do other folks have >> the same issue and are just being quiet because they don't have a solution? >> > Keeping quiet because I don't have a solution, but watching in case someone > has one :-) > > For me, the ideal is to have a send-only account on the N800 so I can generate > messages when I'm out and about that will be sent when I connect to a > network. But I don't normally want to collect incoming messages as I prefer > to leave that to my desktop machine. Though it would be useful to be able to > enable/disable receiving so that when I'm on holiday I can pick messages up > when I find a network I can use. For just a send-only account setting the incoming server to 127.0.0.1 seems to work fine for me. If you open up the main application you get the annoying popups but there isn't much need to do that. If you just compose and send email it stays quiet about it. John ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Send-Only Accounts in Modest
>> Back on topic, am I really the only one with a mail setup like this? I >> thought it was a moderately common arrangement. Or do other folks have >> the same issue and are just being quiet because they don't have a solution? >> > Keeping quiet because I don't have a solution, but watching in case someone > has one :-) OK, I was hoping I was just being dense and that a solution/workaround was available that I wasn't finding. I've filed a request for enhancement bug in bugzilla. Go vote for it if you'd like to see this issue resolved. https://bugs.maemo.org/show_bug.cgi?id=3409 Thanks, Mike Lococo ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
[Announce] Release of the DCCP Plugin 0.6 for GStreamer
Hello list! I'm pleased to announce the version v0.6 of the DCCP GStreamer Plugin. Please, let me know if you have any problem on running the plugin, suggestions and improvements that you provided for it. The main news for this release is that the plugin can now support multiple connection in the server element and share the same sockid between to GStreamer elements. What is GStreamer? == GStreamer [1] is a library that allows the construction of graphs of media-handling components, ranging from simple Ogg/Vorbis playback to complex audio (mixing) and video (non-linear editing) processing. Applications can take advantage of advances in codec and filter technology transparently. Developers can add new codecs and filters by writing a simple plugin with a clean, generic interface. GStreamer is released under the LGPL. What is DCCP? = The Datagram Congestion Control Protocol (DCCP) [2] is a transport protocol that provides bidirectional unicast connections of congestion-controlled unreliable datagrams. DCCP is suitable for applications that transfer fairly large amounts of data and that can benefit from control over the tradeoff between timeliness and reliability. It is a message-oriented transport layer protocol that implements reliable connection setup, teardown, ECN, congestion control, and feature negotiation. It was published as RFC 4340 by IETF in March, 2006. Linux had an implementation of DCCP since version 2.6.14 and this continues to improve with each release. The latest official version of the DCCP code can be found at [3] and at [4]. What is DCCP Plugin for GStreamer? == It is a plugin that allows transfer data over the network via DCCP for GStreamer. According to all the tests that we proceeded, the plugin is able to stream audio files, such as mp3, audio captured from the microphone and raw data files. CHANGELOG = - Adding support to many client connections to dccpserversink. new property: wait-connections - Wait for many client connections flags: readable, writable Boolean. Default: false Current: false - Adding sample for sharing socket id between two instances of an element See folder examples/call - Adding sample of send MP3 stream. See folder examples/mp3Stream - Changing the name of the property sock-fd to sockfd. - More code refactoring and some internal fixes to remove some warnings TODO List = - Improve the implementation of the send mechanism adding the Paraslash solution based on queue How to contribute? == Please, contact me at leandroal [at] gmail [dot] com Where is DCCP Plugin? = The DCCP plugin for GStreamer is under version control of the E-Phone. The E-Phone (Embedded-Phone) project aims to develop a VoIP client for Maemo platform based on DCCP transport protocol. In this project we are also implementing the CCID-4 [5] IETF drafts on the linux kernel. Development: http://garage.maemo.org/projects/ephone Mailing list: http://garage.maemo.org/pipermail/ephone-discuss/ Download: https://garage.maemo.org/frs/?group_id=297 or directly from https://garage.maemo.org/frs/download.php/4252/gst-dccp-0.6.tar.bz2 How to use it with gst-launch command line? = A basic example to stream a multimedia file using ccid-3: * Server: gst-launch -v filesrc location=music.mp3 ! mp3parse ! dccpserversink port=9011 ccid=2 * Client: gst-launch -v dccpclientsrc host=localhost port=9011 ! decodebin ! alsasink -- We also tested with mpg123, to use it: mpg123 dccp://localhost:9011 Please, refer to the src/examples_app/README file for more examples. Is there any application examples? == Yes, refer to the examples_app directory of the source file. Requirements - Linux Kernel with DCCP enabled - GStreamer - Additional GStreamer Plugins to make the example app works Best regards, Leandro. References: [1] http://gstreamer.freedesktop.org/ [2] http://www.read.cs.ucla.edu/dccp/ [3] git://git.kernel.org/pub/scm/linux/kernel/git/acme/net-2.6.25.git [4] git://eden-feed.erg.abdn.ac.uk/dccp_exp [5] http://tools.ietf.org/html/draft-ietf-dccp-ccid4-01 -- Leandro Melo de Sales Pervasive and Embedded Computing Laboratory Computer Science MSc. BRisa and E-Phone Projects Manager Network Admin @ http://embedded.ufcg.edu.br/indexen.html +55 83 3310-1404 (extension 208) http://www.leandrosales.com/ ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Send-Only Accounts in Modest
On Sunday 06 Jul 2008, [EMAIL PROTECTED] wrote: > Back on topic, am I really the only one with a mail setup like this? I > thought it was a moderately common arrangement. Or do other folks have > the same issue and are just being quiet because they don't have a solution? > Keeping quiet because I don't have a solution, but watching in case someone has one :-) For me, the ideal is to have a send-only account on the N800 so I can generate messages when I'm out and about that will be sent when I connect to a network. But I don't normally want to collect incoming messages as I prefer to leave that to my desktop machine. Though it would be useful to be able to enable/disable receiving so that when I'm on holiday I can pick messages up when I find a network I can use. -- Tony Green Ipswich, Suffolk, England http://www.beermad.org.uk http://no2id-ip.web-brewer.co.uk ** This message is digitally signed. If your email client is unable to read digital signatures, you may see an attachment that you cannot open. See http://www.gnupg.org/documentation/faqs.en.html for more information. You can validate my PGP key from my website: http://www.beermad.org.uk/ * No Micro$oft products were used in the generation of this communication signature.asc Description: This is a digitally signed message part. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
