Quote:
Scrolling through lists, in my experience, is wonky at best with a touchscreen. Would it be possible to add a scroll bar? Or perhaps some other method for quickly jumping around a large list?
I updated the tips section of the users guide with how to enable scroll bars. I will look into creating some customized scroll bars that will be optional.
Quote:
On a personal note, I've been tinkering in Quartz Composer for the past few days to create my own Visualizer...if I can get it to the point where I won't be embarrassed, I may submit it to you.
just make sure when you use the "music visualizer" template in QC since that is what v1.1 will use. I updated the visualizer creation guide as well.
Quote:
While thinking about visualizers, since modules are now a "simple" install, perhaps a feature request might be a simple visualizer install method. Maybe something even as simple as an "Import visualizer" option in NBB, with a basic finder browser to select it from.
yeah the way I will do this in the short term is allow NBB to accept opening files of all types then for non .module files lookup each installed modules info dictionary to see if a module will handle the file type. if it finds more than one module that will handle it it can present a dialog to allow you to choose which module to use...
Quote:
Also..and this may sound silly...
What about an "About" entry? Something to show the current version and loaded modules. As this gains steam, it seems like something that will become helpful when troubleshooting versions..
that doesn't sound silly at all. I agree completely and will have it in 1.1 as a new "page" in the main app prefs.
Quote:
Jumping back a few posts...would it be possible to adapt the theme to allow for a "select logo" option, and the selected image is a simple overlay? That way people could create/share easily...
the themes are just a precursor to a much more robust and extensible skinning engine. I will post a mock XML file that will be used to specify to the skinning engine what images to override since I am moving all my custom controls to use [NSImage imageNamed:] that will make it easy for the skinning engine to simply explicitly set the specified image to override the one in the bundle.
I will try my best to have this image substitution ability in the skinning engine for v1.1 since it is not that difficult (in theory)
on a side note a while back I was playing with leopards objc garbage collection but went back to manually managing memory because of stability and performance issues when using garbage collection. It seems that i forgot to "autorelease" some table view data when I went back and 1.0 has many small memory leaks that will add up quite a bit over time. these among others have been patched in v1.1 and as such NBB now uses about 10% less memory.