Rockbox

This looks really nice. Have a look at the output_dyn_value() function in apps/misc.c, I believe you can use that to output a nice Kb/Gb display.

Updated version using the output_dyn_value() that Linus suggested - rockbox.iriver file dropped a few hundred bytes in size, and the code looks a lot cleaner too, while retaining the same functionality.

Thanks for the tip! :)

   properties.patch (5.1 KiB)

Would it not make sense to implement this as a viewer plugin instead to save on binary size?

I initially created this as a plugin which would be accessed by the “open with” menu. The reason I went against this was mainly a matter of accessibility, it’s easier to find this way, and you have to do less looking (it’s also more intuitive).

Perhaps I could make a dedicated menu item to launch the it as a plugin, keeping the best of both worlds. Does this sound like a good idea?

Making it a plugin, and adding it to the menu seems ideal to me. There’s going to be a HDD spinup anyway, isn’t there, so having it as a plugin just adds a tiny fraction of time (plugin loading) if I understand correctly?

I think it would be nice if this can be bundled with the ID3-Screen.
For example pressing LEFT or RIGHT toggles between file info and id3 info.
Bitrate, Frequency and Path could be moved to the file info “tab” then.

A few requests for what it could do:
When you view the file’s properties, show a list of viewers associated with it (viewers.config), and what the default action for that file type is (whether it’s a viewer, or whether the Rockbox binary has reserved it, such as music etc).

This version of the patch just turns it into the plugin based system - it doesn’t add any new features.

Unfortunately there are some side effects of using the plugin approach:
- No .lang file support - this means:
– No support for other languages
– No voicing

- No statusbar
- No background image support
- Scrolling doesn’t work properly any more (probably due to my incompetence rather than any programming limitation)
- Properties plugin is visible from the plugins menu

However, it isn’t all bad news. The addition of this featuer only adds 88 bytes to the rockbox binary.

   properties_plugin.patch (2.3 KiB)
   properties.c (5.9 KiB)

Also note that the language system is meant to one day get expanded to allow for both translated text and voicing:

http://daniel.haxx.se/rockbox/langv2

Updated the plugin, and synced the patch to CVS.
The plugin now uses the button action system, and the scrolling is working fine now.

The patch also adds gui_synclist_set_title to the Plugin API.

   properties_take2.patch (3.5 KiB)
   properties.c (5.2 KiB)

How about this implementation? (sorry to drop above ones completely)

I’ve added it to Rockbox context menu when browsing, and it works on files and directories. Uses direntry and as such doesn’t try to open the file. Translatable. Does its own value formatting (in only 17 lines!) because output_dyn_value() can’t handle big values and isn’t easily adapted (first try resulted in a bigger binary then my implementation in parallel).
Adds 1680 bytes to the binary….

   props.patch (7.7 KiB)

slightly optimized (size-wise), still adds 1596 bytes to the binary. If anybody knows why this bit of code takes so much space, do tell….

also synced to latest cvs changes

   props.patch (7.5 KiB)

switched to using dircache

   props.patch (7.6 KiB)

Scrolls long lines and faster exit from screen.
Size increase now at 1576 ;)

   props.patch (7.7 KiB)

FYI: I’m also moving this to a plugin (a viewer, that is), based on the initial work of aliask. May need to extend the pluging api even more :/

plugin version, just needs a bit cleaning but should be ok

   props.patch (6.2 KiB)
   properties.c (10.1 KiB)