|
Hi,
OK, I think I'll call the plugin I'm writing Rockipedia for the moment - it can change in the future if required. The Rockipedia image in the thread is cool, although it may take up valuble space in the code of the plugin and load time.
I question about button mappings for H3xx...
The following buttons are required.
Click Link (Joystick in on H1xx)
Move up/down in links/document (Joystick up/down on H1xx)
Back to previous topic (Record on H1xx cause it is on the left side of player)
Forward if previously gone back (AB on H1xx cause it is on the right side of the player)
Back to list of wikis (Stop on h1xx)
Menu (Play on h1xx)
Could someone suggest mapping for the h3xx (or changes to the mappings for h1xx)?
Update so far:
In-line links work (although only to other topics and not inpage jumps yet).
I'm writing a converter that will turn any simple html file into a format that can be viewed by the plugin. This way any file format that can be turned into simple html (ie all wikis, possibly ebooks or pdfs) can be converted and viewed.
Restrictions:
So far the plugin simply acts as a viewer. I have yet to implement a proper front-end to the plugin.
Not all of the possible formatting tags have been created.
No word wrapping so far.
Current limit of 8k for file being viewed. (This will be increased. It may not seem a lot but remember that it is text only (with 1 byte formatting tags) so it is actually not as small as it appears).
No tables. Proper tables may be very difficult to implement - at least in the way that my plugin is coded - but I'll have a think about it. A quick fix I think will be to use the fixed width font and have the table pre-rendered in ascii.
Cya,
Connell
|