QUOTE(hunted @ Aug 25 2004, 12:11 AM)
This is very cool. Looks really good.
I would add this myself, but I currently don't have VC++ so I'd like to add that there should be an option on what playlist the database view goes to
I added it for the next version of that plugin, which I will probably upload later.
QUOTE(Melomane @ Aug 25 2004, 01:36 PM)
wonderfull work musicmusic!
one ergonomical feature request in database panel:
"view" dialog box and "refresh" button same in albumlist

I will consider adding buttons/dropdown myself, but hopefully someone else will develop it further.. I have fixed it for the next build so that "refresh" shows up in the context menu when you dont right click on an item.
QUOTE(jkwarras @ Aug 25 2004, 04:36 PM)
Thanks a lot!
Works fine here

Some little suggestions:
- Side-bar: Auto-hide sidebar (or any toolbar i.e. Database explorer) when multiple playlists (right now, when more than one playlist it doesn't hide).
- Database Explorer: It makes more sens (to me) to have the database explorer in horizontal, I mean i.e. on top (or down) the playlist. Right now, in vertical (sidebar), you have to resize it a lot to view everything without having to use the arrows.
I guess that just having the possibility to resize it vertically when including it on the 'Default toolbar' (where Menu, Playback buttons, seekbar is by default), would do the trick (right now you just can see a line).
Some little configuration colors/columns etc... would be extra-cool stuff
Thanks again for your work, much appreciated

1. Why do you want it to hide with more than one playlist? I could reimplement the old auto-hide if that is what you want, but for the whole sidebar.
2. I could make the height configurable, but I cant really make it resizable via the UI with the rebar control. Would that do? (I.e. setting the height in preferences)
3. Colours for the database explorer is done for next version. Where do you want columns? Im not going to use a listview control and Im not writing a custom control for it so no I guess..
QUOTE(upNorth @ Aug 25 2004, 06:30 PM)
Nice work, musicmusic!

My first thoughts:
The way
Database Explorer currently works, makes it pretty much unusable to me.
The problem:All "views" available are generated at startup. This makes it a pain to load this panel if you have a large database (thousands of tracks). It also makes foobar's load time ridiculous if this panel is enabled. To add to the problem, my own "views" are even more resource hungry than the default ones.
My ideas for improvements:1) Use the same drop down list as seen in "Album list", to generate one "view" at a time.
2) Make it optional to populate the list/tree even though the panel is active. A refresh button could be used to populate it, as well as adding a needed refresh feature.
3) I'm not sure how good this last idea is, but I've been thinking about it for a while. Would it be feasible to use saved "views", to avoid generating them in real time over and over for the same database? If so, you could refresh only when you have gotten new tracks or have done changes, and enjoy faster load time the rest of the time. This would probably consume disk space, but at least to me, that isn't an issue.
Edit: I see one really positive effect of the current behaviour though. Once you have this panel loaded, you can browse through all views without delay. That's very convenient, and it would probably be nice to have this as an option in the future too.
A hope for the future:
A dead simple panel would be great to have as a template, for less skilled programmers attempting to create a panel.

My plugin development consists mostly of reverse engineering, so one button, one text, one listbox or so would really help alot. Something along the lines of foosion's tutorial plugins is what I'm thinking of. Then my prealpha foo_navigator plugin might turn into a panel one day.
Thanks for all your efforts. Really appreciate it!

To be honest, it doesn't have much slow down here with database with ~2400 files x 4 hierarchies. What kind of delay are you seeing?
1. I will consider it. What about choosing a view by context menu? Dropdown list is fine though.
2. Ok it should be fairly easy to implement.
3. I dont think its worth it, and I dont know how much time it would actually save.
4. I know it isn't particulary simple, but well you could use one of the above panels as a base (maybe foo_history_panel), or I will consider releasing the source to some of the panels/toolbars in foo_ui_columns if you are particulary interesting in any of them. I'm happy to awswer any questions you may have, if I know the answer anyway.. Would some comments in e.g. foo_history panel help you?