[ashkulz]

Ha, I love it when someone asks "what features can i add?" And I love it even more that I know that you're the kind of guy to actually implement them.

Bring 'em on!

Working with images as input (something I never got around to doing myself):
Lots of people have folders of images of scanned books or comics they'd like to collate. Part of this feature is the ability to process double-page scans. Ie, you first split the scan down the middle (down a user-adjustable line) and then again if you're converting into landscape mode. This was one of the most popular feature requests I received.

Hmm, there's already a fantastic (but a tad intimidating) tool called unpaper which does all of that and more. As it has quite a few options to tweak the way it works, I'll have to see how to integrate it into the current pipeline (don't want to add too many options to PDFRead).

A quick and easy-to-implement way would be to write a wrapper GUI for unpaper, combine the unpaper output to a multi-page TIFF and then add TIFF support to PDFRead. That would solve most people's needs, and yet keep the complex unpaper configuration out of PDFRead.

Some minor stuff:
When a user selects a file, the format (pdf/djvu) can be selected automatically based on the extension. Also, when a user selects a profile, the file extension (eg .lrf) MUST be added automatically. (Otherwise the device won't open the file and the user won't know why.)

That's going to be a bit tough, as the Windows GUI isn't really a GUI. I've actually hijacked an installer (based on NSIS) to provide GUI-like features. Main reason: small code (~60kB) which works on all Windows versions with zero dependencies. I don't really want to get into the GUI thing for now, I want to focus on features (If someone does write a GUI, I'd be happy to include it -- all the current GUI does is build a command line and then execute it).

Some more minor stuff:
Try to add explanations for your options, particularly on the "customize" page. Even I am not sure what some of the things mean, and you're really robbing your users by taking away configurability (either completely or just in practice). A good way to add explanations is a box at the bottom whose contents change depending on where the mouse points.

You're right, some of the options will not make sense unless you know what is actually happening during all the various stages. I'll make a document about it and post it on the website sometime tomorrow.

Some more minor stuff, continued:
When you give people configuration options, and even if you add good explanations, there should be a way to preview the result.

The best way I can think of is to allow a page spec for conversion and convert for those pages only. ie. that way, you can convert a single page and see how it looks finally. Don't know how it will integrate with the windows GUI, though.