Hello, to remove the home screen widgets, press options on the home screen
and select edit home screen item. You will have a screen similar to the home
screen. press left and right arrow, or up or down, and try options and see
if there is an option called remove. If so, select remove and that widget
will be removed from the home screen. Talks reads names of some of these
widgets, some it does not read. So, you will just go left-right-up-down
randomly and check by pressing options if the remove option is available. At
least i did so on my e6 and there remained only a few items on my home
screen. the only 3 things i could not remove are, the missed events widget,
the profiles and clock widget. others can be removed as i described above.
and, one thing i could not solve about home screen, changing the assignment
of key2 shortcut. the key2 has been assigned as menu shortcut, since my
phone has a physical menu key, i wanted to assign to another application but
could not figure out how to do it. the phone user guide also did not help. I
will check the phone manual and search for this if a solution is available.
----- Original Message -----
From: "Brad Keller" <keller...@gmail.com>
To: "Talks Mailing List" <talks@talksusers.com>
Sent: Saturday, September 10, 2011 8:01 PM
Subject: Re: [Talks] question about talks and over all
applicationaccessibility
With the extremely small number of developers that Talks has it would be
difficult for them to make sure that Talks will work on the phones as well
as with every application. Also who would be the one to decide which
application is ggoing to be made accessible? There are so many apps out
there and only a few people may actually want to use it. No I think it is
better to keep the developers focused on what they are doing right now,
especially with the new versions of symbian.
----- Original Message -----
From: "alex wallis" <alexwallis...@googlemail.com>
To: <talks@talksusers.com>
Sent: Saturday, September 10, 2011 10:13 AM
Subject: [Talks] question about talks and over all application
accessibility
Hi list.
I am still experimenting with my e7,
and a thought occurred to me about application accessibility in general.
I am still having problems removing widgits from my e7 home screen, I am
beginning to think it might be time to ask a set of eyes.
but I went on a hunt through google to see if there are any apps that
might make the touch screen more accessible to use.
I came across one called spb mobile shell which is a total interface
replacement, though of course it can be removed to get back to the old
interface.
I was interested in this app, because I believe it has a dedicated menu
button for functions to do with adding, and removing widgits.
Unfortunately I installed this application, and it took over the
interface, of course this now means talks won't read anything on the
phone, apart from its own functions and the menu for turning the phone
off, so I am going to have to get some eyes to help with removing it.
but this got me thinking and wondering, is it possible for a developer to
adapt there application for it to be accessible, or does talks have to be
adapted as well some times. is there any documentation out there
explaining what is needed in an application for it to be accessible with
talks?
as I have never heard of any such documentation, and it seems to me that
we are dependent on the talks developers to decide what applications they
want to be accessible with talks, for example, there are much better web
browsers out there than the ordinary symbian one, but none are accessible
with talks, and obviously that's either down to the applications not
having accessibility stuff in to start with, or because talks has to be
adapted to support them.
It would be good if there was some sort of documentation out there we
could point developers to and say this is what we need for an application
to be useable.
Of course its not likely any of them would make use of it, but I think it
would still be good if there was something we could give to developers.
as at the moment, we can complain all we like about accessibility, but
that's no good if you can't say hears some documentation explaining about
talks, and what is technically needed in software for accessibility. At
the moment, developers can try talking to nuance, but why should they put
all that effort in, making contact etc, and then probably end up getting
told that nuance has never heard of talks which I believe happens to a
lot of people because its such a small product compared to the other
software nuance sells.
_______________________________________________
Talks mailing list
Talks@talksusers.com
http://lists.talksusers.com/mailman/listinfo/talks
Hosting of this list provided courtesy of:
eHosting Limited: http://www.ehosting.com/
and
Talknav Inc. http://www.talknav.net/
_______________________________________________
Talks mailing list
Talks@talksusers.com
http://lists.talksusers.com/mailman/listinfo/talks
Hosting of this list provided courtesy of:
eHosting Limited: http://www.ehosting.com/
and
Talknav Inc. http://www.talknav.net/
_______________________________________________
Talks mailing list
Talks@talksusers.com
http://lists.talksusers.com/mailman/listinfo/talks
Hosting of this list provided courtesy of:
eHosting Limited: http://www.ehosting.com/
and
Talknav Inc. http://www.talknav.net/
