Creating these individually would be too much I think, so here goes.
---
1) New character page should have link back to the character list and/or the group it is being created in.
2) Image uploading should have the platform stated with the game name, just so that I don't have to exert my memory on which tab/window I had which platform's version of the game :P
3) I still miss other gender options. Orks in Warhammer universe for one are practically neuter since they reproduce by spreading spores for the duration of their whole lives, that eventually evolve/grow to full grown Ork (which happens quite fast; apparently it takes only 7 hours to reach the first stage). At least add hermaphrodite (unisex, if you want to be politically correct - can't think of any instances right now), neuter/none (most robots, non-specific undead and other non-biological entities), and maybe "malleable" or some such to indicate the character can change it ( Slaanesh fits this).
4) Only display the main group title in character info page in the "belongs to" list.
5) In company info page, we only have link to list games published by the company, even if the company is listed (only) as developer. Provide links for both according to the items flagged. Developed games if it's flagged as developer, published if as publisher. Neither if neither is flagged (show warning maybe if this is so?).
6) Angels, non-demonic gods, changelings/shapeshifters, etc. all go to "other" in character class. Unless you want to call them humanoid.
7) Group updates still only show in 'all' page of /users/whatsup, they should appear in tags too.
8) New characters and their edits only show in the 'all' page as well, maybe their own category or shove them in with tags.
9) A "real" bug/issue tracker would likely make it easier to keep track of unresolved issues as many non-fatal bugs seem to linger for months :) This could be used for feature requests as well. I'd suggest some third party tool, but I don't know any lightweight ones (that have clear interface). This is probably the least important suggestion of all.
10) Reminding that many browsers and proxies do not cache URLs that have question mark (?) in them (treated as _dynamically_ created content, for obvious reasons), so the image URLs that use the showtheimage.php have high potential of increasing bandwidth usage unnecessarily. Implement some nice URL rewriting to cheat those bastards =)
11) Also, if the showtheimage.php script doesn't do it already, make it handle HEAD requests properly. This is usually used to check if a file has changed. Implement in other scripts as well if possible.
12) Suggested elsewhere, IIRC, but image descriptions _are_ missing from the regular gallery. Character lists per image as well, but that might not be as important (other than for images where they pose solo).
I think I ran out of ideas for now...  by andread# 2 months and 25 days ago (updated 2 months and 25 days ago)1 and 2, done.
That upload page really needs an update...
3 and 6, I need to read again the gender thread. Skipped for now.
4, done.
5 Companies management are waiting for a great update. Will skip for now.
7 and 8, added a link to the respective logs...
9 no experiences on bug-tracking software, so I don't know what you are missing. Perhaps some improvements to this forum could be enough. 9 no experiences on bug-tracking software, so I don't know what you are missing. Perhaps some improvements to this forum could be enough.
A lot of the bugs/suggestions seem to go unnoticed or get forgotten as soon as they leave the forum front page. Even I forget some of those that I've posted. That's the only thing.
So, this could be improved by making each thread take less vertical space and showing more threads per page.
I guess this could be partially solved if the bugs/suggestions that _have_ been solved had their titles updated with [solved], [fixed] or similar text by the person who submitted it (this is common in other forums).
The request to accomplish flag is a bit superfluous now that the sections are in, unless you have some special method of listing them in each section and remember to unflag them after you're done with them. The problem is just that if it requires manual flagging first, then new bug/suggestion threads may escape notice, so it should be automatic or people should start modifying the thread titles once the status changes.
Come to think of it, the main forum page should actually list only the sub-sections and some extra info from them, like some info of the newest post. You could do something fancy with last-visited info like how many new posts have been made in each section since last visit or just a flag that new posts have been made. The latter is less heavy on the db server, too, and quite simple to accomplish.
On the subject of issue/bug trackers...
... they have uniform format to attach a lot of metadata to the bugs/issues/tasks, and create auto-tracked milestones and sub-tasks for other tasks. On single coder projects like UVL it has less use, other than also functioning as a todo list :) Automation is the main point. It also wouldn't spam the main forum page which would be more suited for other things. With cookies you could do a lot of fancy magic, like the new posts in section since last visit. Just store the current timestamp in a cookie when the user views a section, then next time check that timestamp against the threads there and somehow mark the new ones and those with new posts as such. For the main forum page with only sections, you check the newest post for which you display some info anyway, but don't update the cookie timestamp.
Not sure if there are limits to how many cookies can be stored, but if there are none, then per-thread last visited markers could be stored as well, but that can get excessive. Not sure if there are limits to how many cookies can be stored
Each time you request a page, all the cookies are sent too, so the number (and size) of cookies impacts on the real page weight.
I've seen this problem in many popular forums: you see the flagged new threads, but if you exit and return to the forum, the cookie is cleared and it assumes that you have read all the threads. Alternative to that is that the user has to press some button to mark all as seen up to newest visible post (using current timestamp will hide posts made between page load and pressing the button). It's too much work though, and useful only for those who absolutely must read all posts.
I've seen some offline browsing data stuff mentioned elsewhere, some new web technique. That could be used here in _much_ better fashion than cookies or server-side user tracking. It just runs completely on client side, so it has the flaws inherited with that.
Edit: Oh! I just remembered, cookies had that weird path variable. If you point it to /forum/thread/{thread_id}, then it should be provided by the client only when that path is accessed on the site, and no other thread-specific cookies :D bug trackingSourceforge has bug tracking tools. You could put the source code for UVL there and use them.
:) Sourceforge tends to be slow. There are better alternatives that don't suffer from that. Also, sourceforge's issue tracker is awful, IMO.
Other alternatives:
www.berlios.de/ code.google.com/hosting/
And whatever is listed here:
en.wikipedia.org/wiki/Comparison_of_free_software_hosting_facilities
If code hosting is wanted, I'd recommend picking one that uses Git (or SVN at least).
Here's an example project using google's hosting.
code.google.com/p/gosu/
I'm pretty sure you don't have to move source hosting into any of these if you don't want to, but it would work as a backup and may help figuring out what bit of code broke what, and it would also be automatic historical record of how the code evolved :)  by andread# 2 months and 22 days ago (updated 2 months and 22 days ago)Being a google-addicted since it's first days, I've started a google-code project.
You'll not find the code there, but the wiki and issues sections will be useful.
code.google.com/p/uvl/
To add project members I have to add them manually, using a valid google account.
I managed to add Sanguine and Zerothis, but other users email were not accepted, sorry.
If you wish to join, send me an email (directly or using the contact form) with a valid email.
(You should be able to start a Google account using any email, not only the Gmail ones)
Depending on how this works, bug reports/suggestions will be handled here, but I would keep using the forum for most threads anyway.
edit
Looks like I can't delete testing issues... Maybe limit site specific issues to it, like bugs and feature requests, but leave some other stuff here (the forums) like the tag related stuff, ratings and whatever else which don't exactly fall to how the site works but more on how the people (editors) work. Although maintenance requests for tags and such could be filed to the tracker as well, since they seem to be quite low priority as well.
I wouldn't mind if some discussion was made here and then a issue submitted to the tracker with link back to the thread (and link to the issue posted to the original thread as well). It would seem then natural to get updates on the issue on the tracker instead of the forum after that, as it has proper controls for the issue status and such.
It could also be that a feature is first fleshed out in the forum before posting it to the tracker. I mean, posted in cases where the feature is thought low priority and isn't worked on immediately. And this could also work if whoever wanted to suggest it didn't have clear enough picture of the thing yet or just wanted feedback before submitting, I dunno. edit
Looks like I can't delete testing issues...
Probably can only close it with "invalid" status or something :) Well, after my membership apparently was removed, the new issue form has been stunted severely. There's only one text box with the default questions (which don't all fit with UVL), and the type and severity boxes has been hidden completely which were visible before. Seems to be enough, if you like to think suggested enhancements as defects :)
Anyway, I added one new bug and reposted two other issues (that hadn't received any feedback) there with URLs back to the original threads (I wonder how link creation works in there, would be more convenient than the plain URLs).
(Wish I could change how my name appears there like in google groups, but there's no settings for that and is outside the scope of UVL) New issuesI have to assume you (Andrea) haven't done this already, but if you go to administration tab in google code project and scroll down to activity notification, you can add your email address to the second field. Google Code doesn't automatically subscribe people (admins & project members) to receive notifications of new issues (I presume, that'd be awfully spammy for people managing large projects), so this is required(?) if you want to receive them. People can add themselves to the CC list of an issue when it's created (the star), but this is manual and obviously does not report new ones. Well, after my membership apparently was removed
I'm sorry, I saw it was showing personal data (well, the name at least) so I removed the members, and forgot to notify this on this forum.
Now I add Sanguine to the GoogleCode members list.
Anyone wishing to be included please add a comment here. it was showing personal data (well, the name at least)
Only the google account name. For non-gmail accounts it uses some strange obfuscation. |