WebMonkey R9 - 2006/03/28

[Lowlander]

Also, since I made that change with adsutil to 40, it works great (no more missing pictures or frames).

I don't know what you mean with this.

Please do share more ideas with us. It seems that the new version is running stable, but there would be some things I'd like to add before releasing the next version. This might still be a few weeks before I'll release the next version.

[Nautme]

I was referring to my earlier post about increasing the connection limit to 40 (C:\Inetpub\AdminScripts\adsutil set w3svc/MaxConections 40).

I had a couple suggestions for you earlier today, but my brain has already gone to bed. I'll make some notes tomorrow and get back to you.

[Lowlander]

Ah, stupid of me, forgot all about that, hehe. Guess my brain was in bed too, lol.

[Lowlander]

You might also want to check out http://www.kavasoft.com/iTunesCatalog/. Seems interesting, basically webmonkey for iTunes.

[Nautme]

Interesting. I'm guessing it's php with some sort of built-in server. At first glance, I don't think I'd like it. I tried their demo, but it didn't really work. I like WebMonke for one reason that others might not- it's ASP. Just means I can do whatever I want with it.

[Nautme]

It's been a busy week (with taxes and all), but here are some more suggestions for the next release (or a future release)-

1. Who is currently logged on in Statistics.

2. A way to limit the number of current connections for a user (so someone doesn't give their ID away to 50 people).

3. A way to limit the overall number of concurrent connections so the site doesn't get overwhelmed.

4. Logon history in Statistics (need a History table and Username, IP, Time, etc.).

5. Maybe add some rights fields to the WebMonkey database to allow for access to certian features (such as add/edit users or download).

6. Add an Active field to the User table so that you don't have to delete a user to deactivate them.

7. A better way to handle settings. Maybe a VB app or ASP page that stores values to an INI and would give an easier to understand GUI.

8. I've got a lot of songs in my collection. Clicking on Title takes an eternity to load. Maybe add an option to load the first letter of each song like MediaMonkey does it. Or maybe something like 0-9, A-F, G-L, M-R, S-Z.

9. Kind of the same as number 6, but change the Year to show Decades. I'm usually less interested in hearing a specify year, but sometimes I'm in the mood for 80s music.

10. If you implement 6 or 7, you may want to consider adding sub-trees for more detailed information (ie +Year then +Decades which gives you the Years in the Decade). I'm not sure if this is how MediaMonkey does it as I don't use it much.

11. Some of the pages can take a while to load (like preparing a TAR or loading alot of results). It would be nice to have some sort of loading graphic that goes away when the results are done. I can give you some tips if you aren't sure how to do this.

12. User level ratings. They could rate their favorite songs and you could store them to the WebMonkey database. This would allow them to listen to their more or less favorites.


Hopefully these are good suggestions. Let me know if you'd like me to clarify or help with anything.

[Lowlander]

1) would require the global.asa which I'm trying to stay away from so that WebMonkey is understandable for novice users

2) Should be possible, not sure if and when I will implement

3) Should be possible thru webserver settings, not planning to implement

4) Is already available in yet to be release r10, allthough in a different form

5) Editing is not yet available, but is considered in combination with rights

6) Need to see about that

7) This has been considered, not yet implemented

I assume you mean the node titles in the explorer tree. This currently not planned as this would make navigation more work (user).

9) Same

10) Same

11) Not sure as I would like to stay away from JavaScript as much as possible, you can send my a concept for consideration

12) This will probably not be added as I would like to keep the WebMonkey DB clean from song information. If you modify remove/add songs the relationship between mediamonkey.mdb and webmonkey.mdb might end up being broken. There is no guarantee that a song webmonkey references to would still be the same song.

All these ideas will probably be considered for r11 at the earliest.

[Lowlander]

2) Actually the logs will show this as user and IP are logged. If you see that a user logs from various IP's at the same time you could ban them (disable their account).

[Lowlander]

A new version has been released.