Ereaders and updates

I haven't been blogging recently because I've been too busy coding. My major project has been a lightweight php e-reader that takes Smashwords samples and displays them.

It's now up and running and I've got feedback, ranging from " cool!" to "I can't fault this."

The tricky bit was the launcher - since I wanted it to open from a link and run whethre or not the user had javascript, be useable by Wordpress users and others whose hosts were locked down, and run at a reasonable speed. And it had to be code easily used by non-coders. Let's just say there's a lot that goes on in the background, and leave it at that.

The real problem, and the reason another coder is building a java version is bandwidth. Parsing and sending the sample is almost 250K or our bandwidth each time it is hit - careful coding reduces the impact on the viewer, and the host offering it uses virtually none - but it's still costly. We've got the affiliate link hard coded in, which should help to offset the costs.

On the other hand I mght try and convert it to a desktop app which can read in files. It is already capable of reading in full (free) ebooks from Smashwords, the bandwidth becomes prohibitive. If it's a desktop app then anyone who wants to can run DRM-free epubs in it. It just wouldn't have a library or anything like that.

Right now I'm working on another coding project, this one at the exciting stage where all the variables are being written out on screen when it runs so I can see what the program is doing - or isn't. The problem for that project is going to be artwork and design - I can code and write, but my drawing? Not so good.