Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #1342 > unrolled thread

Why don't ePaper-devices do apps?

Back to article view | Back to comp.os.linux.hardware

Contents

  Why don't ePaper-devices do apps? Avoid9Pdf@gmail.com - 2012-07-23 22:34 +0000
    Re: Why don't ePaper-devices do apps? Paul <nospam@needed.com> - 2012-07-23 21:12 -0400
      Re (2): Why don't ePaper-devices do apps? Avoid9Pdf@gmail.com - 2012-07-24 08:01 +0000
      Re: Why don't ePaper-devices do apps? Michael Black <et472@ncf.ca> - 2012-07-27 15:03 -0400
        Re: Why don't ePaper-devices do apps? root <NoEMail@home.org> - 2012-07-27 20:04 +0000
          Re: Why don't ePaper-devices do apps? Michael Black <et472@ncf.ca> - 2012-07-29 20:10 -0400
    Re: Why don't ePaper-devices do apps? Charlie+ <charlie@xxx.net> - 2012-07-24 08:11 +0100
      Re (2): Why don't ePaper-devices do apps? Avoid9Pdf@gmail.com - 2012-07-26 17:58 +0000
        Re: Re (2): Why don't ePaper-devices do apps? ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2012-07-31 01:21 +0000
        Re: Re (2): Why don't ePaper-devices do apps? Charlie+ <charlie@xxx.net> - 2012-07-31 09:10 +0100
      Re: Why don't ePaper-devices do apps? ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2012-07-31 01:20 +0000
    Re: Why don't ePaper-devices do apps? John McGaw <Nobody@Nowh.ere> - 2012-07-24 07:57 -0400
      Re (2): Why don't ePaper-devices do apps? Avoid9Pdf@gmail.com - 2012-07-26 17:58 +0000

#1342 — Why don't ePaper-devices do apps?

We know that epaper takes half a second to update its
screen, so it can't keep-up with keyed input.

But can't a method be found to buffer a [selectable]
number a chars, between screen updates. Or some 
other solution.

And why shouldn't it have an email-client and a
'lynx-like' http-fetcher?

[toc] | [next] | [standalone]

#1344

Avoid9Pdf@gmail.com wrote:
> We know that epaper takes half a second to update its
> screen, so it can't keep-up with keyed input.
> 
> But can't a method be found to buffer a [selectable]
> number a chars, between screen updates. Or some 
> other solution.
> 
> And why shouldn't it have an email-client and a
> 'lynx-like' http-fetcher?
> 

Special purpose devices, don't perform general purpose functions ?

Or stated another way, things that aren't computers, aren't computers.

An epaper device, places an emphasis on saving power, so it's
not intended as a replacement for some other small-form-factor
computer-like device. And the display technology is likely
selected as the lowest possible power using type. If the display
updated more rapidly, it would be an LCD, and it would gulp down
battery juice.

    Paul

[toc] | [prev] | [next] | [standalone]

#1347 — Re (2): Why don't ePaper-devices do apps?

In article <juksql$s8r$1@dont-email.me>, Paul <nospam@needed.com> wrote: 

> Avoid9Pdf@gmail.com wrote:
> > We know that epaper takes half a second to update its
> > screen, so it can't keep-up with keyed input.
> > 
> > But can't a method be found to buffer a [selectable]
> > number a chars, between screen updates. Or some 
> > other solution.
> > 
> > And why shouldn't it have an email-client and a
> > 'lynx-like' http-fetcher?
> > 
> 
> Special purpose devices, don't perform general purpose functions ?
> 
> Or stated another way, things that aren't computers, aren't computers.
> 
That's what IBM said in the 60's before the PC hit them.
And what PC-boys said before mobile devices hit them.
I read that now more <androids> than PCs are born.

> An epaper device, places an emphasis on saving power, so it's
> not intended as a replacement for some other small-form-factor
> computer-like device. And the display technology is likely
> selected as the lowest possible power using type. If the display
> updated more rapidly, it would be an LCD, and it would gulp down
> battery juice.
> 
>     Paul
Read again slowly: <we accept the slow update rate>,
and seek INOVATIVE methods to make it usable as a writer too.

Re. inet facilities: I spend an hour studying the text which
uses a 1 minute power-consumption-burst to d/l.

[toc] | [prev] | [next] | [standalone]

#1377

On Mon, 23 Jul 2012, Paul wrote:

> Avoid9Pdf@gmail.com wrote:
>> We know that epaper takes half a second to update its
>> screen, so it can't keep-up with keyed input.
>> 
>> But can't a method be found to buffer a [selectable]
>> number a chars, between screen updates. Or some other solution.
>> 
>> And why shouldn't it have an email-client and a
>> 'lynx-like' http-fetcher?
>> 
>
> Special purpose devices, don't perform general purpose functions ?
>
> Or stated another way, things that aren't computers, aren't computers.
>
> An epaper device, places an emphasis on saving power, so it's
> not intended as a replacement for some other small-form-factor
> computer-like device. And the display technology is likely
> selected as the lowest possible power using type. If the display
> updated more rapidly, it would be an LCD, and it would gulp down
> battery juice.
>
Yes.

I suddenly decided the price of ebook readers had dropped enough, to where 
I was willing to spend the money.  But then wham, they introduce ereaders 
that are tablets.  For less than a hundred dollars more, I can get a 
tablet.  I don't even know which function I want more, tablet or ereader, 
but it makes sense to buy one that does both.

I ended up buying a Blackberry Playbook, just after they dropped to 199 
here in Canada back in February.  I would have bought an HP the summer 
before, but I missed the 99.00 clearout.

Yes, it's a nice tablet.  And unlike netbooks, it's a more practical 
format for light work, for work away from a table.  And it's decent as an 
ereader, though I have read a relative few books, all out of copyright 
books.

But the battery doesnt' last long between charges.  Or rather, it takes 
its time to reboot, so I leave it on standby, which gives a continuous 
drain.  Even under use, the battery needs relatively frequent charges, not 
something you want with a book.  It has everything, nice and bright and I 
can do the internet so long as I find a wifi connection, but if I fall 
asleep with it on, I'll have to recharge.

I'm not disappointed that I bought it, I'm glad to have the tablet.

But, if ebooks are really the future, I figure having the tablet out of my 
ssytem, I will get an e-ink ereader at some point, specifically for books. 
The more I would use an ereader, the more I'd want an e-ink reader.

   Michael

[toc] | [prev] | [next] | [standalone]

#1378

Michael Black <et472@ncf.ca> wrote:
> 
> But, if ebooks are really the future, I figure having the tablet out of my 
> ssytem, I will get an e-ink ereader at some point, specifically for books. 
> The more I would use an ereader, the more I'd want an e-ink reader.
> 
>    Michael
> 

I have several ereaders, both e-ink and backlit. For regular reading
the e-ink is far preferable, not the least for battery life. You
should know that most pdf files cannot be read on a 7" display.
epub and mobi files are fine because they can adjust the display.

For epub files I like my Kobo touch. For pdf files I use the
(no longer available) Kindle DX and my favorite reader the
Pocketbook Pro. It has a 10" display and reads all formats. The
contrast on the Pocketbook is less than that of the DX or Kobo,
but in every other respect the Pocketbook is better.

[toc] | [prev] | [next] | [standalone]

#1386

On Fri, 27 Jul 2012, root wrote:

> Michael Black <et472@ncf.ca> wrote:
>>
>> But, if ebooks are really the future, I figure having the tablet out of my
>> ssytem, I will get an e-ink ereader at some point, specifically for books.
>> The more I would use an ereader, the more I'd want an e-ink reader.
>>
>>    Michael
>>
>
> I have several ereaders, both e-ink and backlit. For regular reading
> the e-ink is far preferable, not the least for battery life. You
> should know that most pdf files cannot be read on a 7" display.
> epub and mobi files are fine because they can adjust the display.
>
So I noticed.  I wsa reading one book as a pdf and with the tablet held 
like a book, the text was a tad fine.  I could enlarge it, but it wasn't 
readjusted to fit into the screen, so I'd have to scroll.  Flipping the 
tablet to "landscape", I didn't ahve to scroll sideways, but I had to 
scroll as I read down the page.

I was sitting in the sun yesterday reading with it, and again noticed how 
warm the back was getting.  That's another minus thing of a tablet.  2 
1GHz cores are nice for  the things people do with computers, but it's 
overkill for reading a book, which is so static.  It's more than just 
battery drain, it just seems overkill.

> For epub files I like my Kobo touch. For pdf files I use the
> (no longer available) Kindle DX and my favorite reader the
> Pocketbook Pro. It has a 10" display and reads all formats. The
> contrast on the Pocketbook is less than that of the DX or Kobo,
> but in every other respect the Pocketbook is better.
>
If ebooks are going to replace books, I'm sure the prices of ereaders will 
have to drop.  So in the long run, I expect to get an erreader with eink 
in a relatively short time that is only for books, but no more than fifty 
dollars, and hopefully less.

Once I got the tablet, a lot of the "extras" are no longer needed in an 
ereader, so they can be cheap, low power, and still good.

   Michael

[toc] | [prev] | [next] | [standalone]

#1346

On Mon, 23 Jul 2012 22:34:04 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
underneath  :

>We know that epaper takes half a second to update its
>screen, so it can't keep-up with keyed input.
>
>But can't a method be found to buffer a [selectable]
>number a chars, between screen updates. Or some 
>other solution.
>
>And why shouldn't it have an email-client and a
>'lynx-like' http-fetcher?

I assume ePaper is the same as eInk? my Kindle does webpages etc -slowly
and small-ly  but you can use it at a push!
C+

[toc] | [prev] | [next] | [standalone]

#1373 — Re (2): Why don't ePaper-devices do apps?

In article <lbis0816q0tooem97juruu10ce1oaj1uq1@4ax.com>, Charlie+ <charlie@xxx.net> wrote: 

> On Mon, 23 Jul 2012 22:34:04 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
> underneath  :
> 
> >We know that epaper takes half a second to update its
> >screen, so it can't keep-up with keyed input.
> >
> >But can't a method be found to buffer a [selectable]
> >number a chars, between screen updates. Or some 
> >other solution.
> >
> >And why shouldn't it have an email-client and a
> >'lynx-like' http-fetcher?
> 
> I assume ePaper is the same as eInk? my Kindle does 
> webpages etc -slowly and small-ly  but you can use 
> it at a push!
> C+
But can you write and edit text?

==TIA.

[toc] | [prev] | [next] | [standalone]

#1397 — Re: Re (2): Why don't ePaper-devices do apps?

In article <jus0ge$2o6$1@dont-email.me>,  <Avoid9Pdf@gmail.com> wrote:
>In article <lbis0816q0tooem97juruu10ce1oaj1uq1@4ax.com>, Charlie+
><charlie@xxx.net> wrote: 
>
>> On Mon, 23 Jul 2012 22:34:04 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
>> underneath  :
>> 
>> >We know that epaper takes half a second to update its
>> >screen, so it can't keep-up with keyed input.
>> >
>> >But can't a method be found to buffer a [selectable]
>> >number a chars, between screen updates. Or some 
>> >other solution.
>> >
>> >And why shouldn't it have an email-client and a
>> >'lynx-like' http-fetcher?
>> 
>> I assume ePaper is the same as eInk? my Kindle does 
>> webpages etc -slowly and small-ly  but you can use 
>> it at a push!
>> C+
>But can you write and edit text?
>
>==TIA.
>
>

Sure.  It helps if you have one of the models with an actual keyboard, of
course.
-- 
------
columbiaclosings.com
What's not in Columbia anymore..

[toc] | [prev] | [next] | [standalone]

#1398 — Re: Re (2): Why don't ePaper-devices do apps?

On Thu, 26 Jul 2012 17:58:42 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
underneath:

>In article <lbis0816q0tooem97juruu10ce1oaj1uq1@4ax.com>, Charlie+ <charlie@xxx.net> wrote: 
>
>> On Mon, 23 Jul 2012 22:34:04 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
>> underneath  :
>> 
>> >We know that epaper takes half a second to update its
>> >screen, so it can't keep-up with keyed input.
>> >
>> >But can't a method be found to buffer a [selectable]
>> >number a chars, between screen updates. Or some 
>> >other solution.
>> >
>> >And why shouldn't it have an email-client and a
>> >'lynx-like' http-fetcher?
>> 
>> I assume ePaper is the same as eInk? my Kindle does 
>> webpages etc -slowly and small-ly  but you can use 
>> it at a push!
>> C+
>But can you write and edit text?
>
Yes but slowly, login to email, eBay etc is quite possible but v.
slowly!    You wouldnt' use it if you had a faster option available -
mine is a Kindle 3 which also plays MP3 files for audiobooks etc. - a
facility I use really a lot.  I Believe the later cheaper  Kindles
perhaps dont do as much or have so much memory, but have advantage of
touch screen whereas mine has keypad.  C+

[toc] | [prev] | [next] | [standalone]

#1396

In article <lbis0816q0tooem97juruu10ce1oaj1uq1@4ax.com>,
Charlie+  <chasg> wrote:
>On Mon, 23 Jul 2012 22:34:04 +0000 (UTC), Avoid9Pdf@gmail.com wrote as
>underneath  :
>
>>We know that epaper takes half a second to update its
>>screen, so it can't keep-up with keyed input.
>>
>>But can't a method be found to buffer a [selectable]
>>number a chars, between screen updates. Or some 
>>other solution.
>>
>>And why shouldn't it have an email-client and a
>>'lynx-like' http-fetcher?
>
>I assume ePaper is the same as eInk? my Kindle does webpages etc -slowly
>and small-ly  but you can use it at a push!
>C+

The Kindle browser is certainly not perfect, but is useful for things like
bringing up google maps in a pinch, checking things you should have looked
up before you left the house and killing spam comments on your blog.

The kindle (not kindle fire, but regular kindles) is a linux device
and there are plenty of jailbreaks out there to get you into it.  It's
easy to develop/port Linux API  programs for it with Scratchbox or other
ARM linux cross compilers..
-- 
------
columbiaclosings.com
What's not in Columbia anymore..

[toc] | [prev] | [next] | [standalone]

#1349

On 7/23/2012 6:34 PM, Avoid9Pdf@gmail.com wrote:
> We know that epaper takes half a second to update its
> screen, so it can't keep-up with keyed input.
>
> But can't a method be found to buffer a [selectable]
> number a chars, between screen updates. Or some
> other solution.
>
> And why shouldn't it have an email-client and a
> 'lynx-like' http-fetcher?
>

They simply don't work well, or at least up to the standards that users 
have come to expect. But that doesn't mean that is can't or hasn't been done.

http://lifehacker.com/5889158/turn-a-99-nook-into-a-fully-fledged-android-tablet-in-four-easy-steps

[toc] | [prev] | [next] | [standalone]

#1372 — Re (2): Why don't ePaper-devices do apps?

In article <o5wPr.438300$%Q3.6425@en-nntp-15.dc1.easynews.com>, John McGaw <Nobody@Nowh.ere> wrote: 

> On 7/23/2012 6:34 PM, Avoid9Pdf@gmail.com wrote:
> > We know that epaper takes half a second to update its
> > screen, so it can't keep-up with keyed input.
> >
> > But can't a method be found to buffer a [selectable]
> > number a chars, between screen updates. Or some
> > other solution.
> >
> > And why shouldn't it have an email-client and a
> > 'lynx-like' http-fetcher?
> >
> 
> They simply don't work well, or at least up to the
> standards that users have come to expect. 
> But that doesn't mean that is can't or hasn't been done.
> 
> http://lifehacker.com/5889158/
> turn-a-99-nook-into-a-fully-fledged-android-tablet-in-four-easy-steps
> 
Wow! That 'reads' fantastic.
So then, why don't the manufacturers sell it in
an 'opened-form'; if it's got an android-engine?

The low-power to read, with short periods to inet,
makes it meet the OLPC's original intentions.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.hardware

csiph-web