From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 4/4] Dummy example GPRS context provisioning driver
Date: Sat, 15 Jan 2011 02:30:10 +0100 [thread overview]
Message-ID: <1295055010.3873.155.camel@aeonflux> (raw)
In-Reply-To: <201101141642.01738.remi.denis-courmont@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi Remi,
> > > Yes, that is how our previous UIs have done it, and I guess our UX
> > > designers like it in the future too.
> >
> > I would advise the UI against using the name from the context
> > information and better using the one from the network registration
> > instead.
>
> Well that would make sense... Therefore the operators don't do it ;-)
>
> For instance my provider shows as "Elisa" in the network registration but the
> access points are expected to be shown as "Elisa Internet" and "Elisa MMS WAP"
> if I recall correctly.
>
> It only makes sense to have this data in the provisioning plugin. It would be
> silly to have to provision just the names in a different component.
just to make this clear, oFono takes care of potential operator renames
and displays them accordingly, but the provision names would stay the
same.
So if Elisa renames themselves into "Gwendula", the context names would
still say "Elisa Internet" etc. Has anybody thought about this part?
Regards
Marcel
next prev parent reply other threads:[~2011-01-15 1:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 13:11 [RFC PATCHv3 0/4] Plugin API for provisioning of GPRS context settings Jukka Saunamaki
2011-01-10 13:11 ` [RFC PATCH 1/4] Added GPRS context provisioning driver API sources Jukka Saunamaki
2011-01-12 6:43 ` Marcel Holtmann
2011-01-12 16:43 ` Denis Kenzior
2011-01-10 13:11 ` [RFC PATCH 2/4] gprs: add automatic context settings provisioning Jukka Saunamaki
2011-01-12 6:51 ` Marcel Holtmann
2011-01-12 7:26 ` Jukka Saunamaki
2011-01-12 16:37 ` Marcel Holtmann
2011-01-10 13:11 ` [RFC PATCH 3/4] sim: add ofono_sim_get_mnc_length Jukka Saunamaki
2011-01-11 0:40 ` Marcel Holtmann
2011-01-11 15:03 ` Denis Kenzior
2011-01-10 13:11 ` [RFC PATCH 4/4] Dummy example GPRS context provisioning driver Jukka Saunamaki
2011-01-12 6:48 ` Marcel Holtmann
2011-01-12 7:41 ` Jukka Saunamaki
2011-01-12 16:46 ` Denis Kenzior
2011-01-13 6:36 ` Jukka Saunamaki
2011-01-13 15:57 ` Denis Kenzior
2011-01-14 6:53 ` Jukka Saunamaki
2011-01-14 7:47 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-14 10:37 ` Marcel Holtmann
2011-01-14 10:46 ` Jukka Saunamaki
2011-01-14 13:44 ` Marcel Holtmann
2011-01-14 13:58 ` Jukka Saunamaki
2011-01-14 14:10 ` Marcel Holtmann
2011-01-14 14:42 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-15 1:30 ` Marcel Holtmann [this message]
2011-01-17 6:20 ` Jukka Saunamaki
2011-01-14 15:07 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295055010.3873.155.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox