DR800 sources posted

[Mackx]

Thanks for the info.

[badbob001]

Well, hopefully the code differences between the dr1000 and the dr800 are small enough so dr800 users can easily 'turn back on' the hidden dr1000 features. I'm thinking of zoom and document tabs.

A while back in another thread, irex mentioned that the poor grayscale dithering on the dr1000 was all due to the software. Does it look like the image viewer component got updated?

[Mackx]

There is only a very small change in the dithering code, it has to do with the calculation of the error per pixel. The implementation for 24to8 is now equal to 32to8 (w.r.t. propagating pixel error). My expertise w.r.t. dithering is not good enough to judge what the improvement will be for the resulting images.

[wallcraft]

Originally Posted by Matthijs

We kept it in there so the (old) UDS PDF plugin still compiles and can be used as a reference for people who want to create their own UDS plugin.

Does this mean that this plugin could be used for PDFs instead of ADE? This would give up reflow (and DRM) but gain back everything that the DR1000S currently has for PDFs (perhaps including annotations?).

[Matthijs]

Originally Posted by wallcraft

Does this mean that this plugin could be used for PDFs instead of ADE? This would give up reflow (and DRM) but gain back everything that the DR1000S currently has for PDFs (perhaps including annotations?).

No. GUI features are enabled/disabled inside UDS itself, not inside the plugin. The Adobe plugin also supports zooming, etc.

[badbob001]

Not sure if this means anything but:

\kbdupgrade-3.0+svnr5493\src\kbdupgrade.c

static char *device_types[] = {
    "DR1000",
    "DR1000S",
    "DR1000SW",
    "DR800",
    "DR800S",
    "DR800SG",
    "DR800SW",
    NULL
};

Given the obvious nature of their naming scheme, this may not indicate any future products. I would be more excited if there were a DR800SGW.

[Kolenka]

Originally Posted by Matthijs

Hi all,

I've just put up the DR800S(G) SDK and Source packages on our developer website.

You'll need to look in the version 3.0 folders.

For those of you who are missing folder browsing, I would suggest to have a look at the ctb sources, filetypes.c around line 273...

Happy hacking!

Regards,

Matthijs

So, getting back to the topic of the thread: I'm assuming the development process (and deploying apps to a live DR800) is pretty similar to the DR1000?

So assuming I have something whipped up in the emulator by the time I get one, I'd pretty much be ready to drop it on and go?

[badbob001]

From looking at ereader.schemas, it looks like adding:
/apps/er/sys/power/min_standby=30

to the dr.ini may allow one to control the standby time, which defaults to 30 minutes. Setting it to -1 disables standby.

[badbob001]

From popupmenu.schemas, this may control the menu items that appear when viewing a document. Some try it in the dr.ini.

/schemas/apps/er/popupmenu/toolbar/toolsets=??

where ?? is listed to have a default value of:
[ctb_menu_content,settings_menu,uds_menu_reading,ud s_menu_dictionary,uds_menu_thumbnail,uds_menu_toc]

The interesting part is the uds_menu_dictionary.

[m-reader]

Originally Posted by cmdahler

And which means effectively nothing at this point. The iPad announcement has wrapped up, and with it is the end of any sort of speculation on the future of most e-ink business. I'm beginning to think this is why iRex put the delivery of the DR800SG in the U.S. on hold for a while: just to see what Apple had up its sleeve. Now that it is out in the open, I'd be willing to bet good money that iRex won't even bother releasing the device in the U.S. now. What's the point? They wouldn't even sell a thousand units over here with a price so near what everyone can get an iPad for. Skiff and Plastic Logic basically just went out of business today, and a huge, wide swath of e-ink business was just vaporized by Apple in one 90 minute announcement. The DR800SG is DOA in the U.S.

It's really no wonder iRex released their source code: what's the point in keeping it under wraps any longer? Their business model effectively no longer exists, so they might as well let the few people who have already bought the thing to tinker with it.

You forgot to mention how iPad will solve world hunger problem, fix the Middle East mess and find the cure for common cold!

[Mackx]

badbob001: These entries determine on the DR1000, which menu items will appear in the 'toolbar' and are thus available via one click when the application is running. I do not see any toolbar on the DR800, so I guess that these entries will not have any effect on the DR800.
Lets hope that the toolbar will still be available on the DR1000 in the new firmware (the code is removed from the R3.0 sources), it gives a boost in usability of the DR1000.

[Kolenka]

I have a feeling the DR1000 software update is taking so long because it is a merger of the DR1000 and DR800 software. They obviously can't ship the ADE update for the DR1000 with a bunch of features missing that were there before, so they are working to port them back into the 3.x branch. At least that's my best guess, and it also would explain why the ADE software for the 1000, and the annotation update for the 800 are planned to release close together.

That said, I'm playing with the DR800 SDK, and it looks like the general assumption is that we have to use a set of button widgets to create a toolbar on the screen if we want them.

I'm a bit confused how developers are expected to ship full apps for the DR800 though. It looks like plugins will work easily enough, but unless the documentation is incomplete (which it is), there doesn't appear to be a way to get these to appear in any sort of programs list or on the home screen.

[Matthijs]

Originally Posted by Kolenka

So, getting back to the topic of the thread: I'm assuming the development process (and deploying apps to a live DR800) is pretty similar to the DR1000?

So assuming I have something whipped up in the emulator by the time I get one, I'd pretty much be ready to drop it on and go?

Yes, if you have it working on the emulator deployment to the real device is very easy (especially if you enable the SD card browsing). Shortcuts (.desktop) are supported similarly to the DR1000.

[Matthijs]

Originally Posted by Kolenka

I'm a bit confused how developers are expected to ship full apps for the DR800 though. It looks like plugins will work easily enough, but unless the documentation is incomplete (which it is), there doesn't appear to be a way to get these to appear in any sort of programs list or on the home screen.

Adding something to the Home screen is indeed only supported if you change CTB. But starting apps with .desktop files works the same as on DR1000. Hint: enable the SD Card browsing (folder structure), that will help.

[Kolenka]

Which means that to distribute apps to users, we are expected to have them edit their dr.ini. Hopefully there will be a cleaner solution so we aren't expected to have techies as an app's sole userbase.