| This 38 message thread spans 2 pages: < < 38 ( 1  ) || |
|New colors for your posts|
colours and posts
| 3:25 pm on May 10, 2010 (gmt 0)|
Hi there people of the forum!
I have just noticed that there are some new colours associated with the post that you participate in, as well as new colours for new users (I think).
Also, whilst I type, could anyone answer my question about the # number that every user has as the last bit of info on their user stats? Just wondering, I assume as it's member number or something similar.
| 8:41 pm on May 16, 2010 (gmt 0)|
They already have new markers, don't they?
I would think the same data could probably be used if I was a coder or something along those lines...
| 8:43 pm on May 16, 2010 (gmt 0)|
That "new" marker never works for me.
Every post always seems to have one, even when I return.
| 8:46 pm on May 16, 2010 (gmt 0)|
Try clicking 'reset last read pointers' next to forum options some time.
Your experience might change a bit.
It's on the top right of the screen below the ads.
They already have a system in place that could be adapted to do it...
Besides, data storage isn't a big deal... It's accessing the data quickly that's more difficult, but I'm sure the people coding WebmasterWorld could come up with something because they do a great job with things like the search, which must require quite a bit more processing and data storage than knowing what time I last visited a thread would, wouldn't it?
| 9:22 pm on May 16, 2010 (gmt 0)|
I might be missing something, but all I can think of they would really have to store is thread number, post number, and my user-name or ip address (IOW: whatever unique identifier they use) and time of access on a visit.
IMO It might be some work, but working out the logistics would take more time than actually coding it, and quite a bit of it would depend on how the information is currently stored, but my guess is my user name = id number, so In 'Incorrect PHP' it could be simple:
DB -> || id | my_id | thread_number | post_number ||
If there was an index say 'id' on my_id, thread_number it would probably be screaming fast...
$s="SELECT post_number FROM last_viewed USE INDEX (id) WHERE my_id = $my_id AND thread_number = 'current thread' AND post_number = ANY ('currently viewing posts') ORDER BY post_number DESC LIMIT 1";
while looping through posts to display:
/* change the bg to yellow */
Edited: you actually don't need the time if you store it correctly...
##### Getting the Info In #####
$u="UPDATE last_viewed SET post_number = $LastCurrentPost WHERE id='my id' AND thread_number=$CurrentThreadNumber";
$i="INSERT INTO last_viewed SET id=$my_id, thread_number = $CurrentThreadNumber, post_number = $LastCurrentPost ";
Anyway, g1smd, something like the above is really close to what it would take to do it IMO. There's probably a couple of refinements to make to be sure you didn't overwrite a higher post number with a lower one, unless you wanted to have it as a traveling marker, but it's fairly simple compared to the search they wrote.
| 1:16 am on May 17, 2010 (gmt 0)|
> Try clicking 'reset last read pointers' next to forum options some time.
@TheMadScientist lol - look at Ian's join date ;-) consider your leg fully pulled.
We are not using a squeamish (sql) db here.
> what it would take to do it IMO
think in terms of 450-550k flat files ;-) Then in terms of about 3.5m live msgs. It would take some significant processor time to do a compare on all those. Sure, we could cut some corners (like only look at msgs within the last 90 days or so... which is what we are looking at. It is a moot point at the current time, we are transitioning to a new db type...self managed. Flat files were awesome for speed, but faster processors and near unlimited ram have superseded their need. We are still going to use a type of flat file, but only 1 per forum with a series of fast index pointers into the flat file dbs.
- It shouldn't be any slower
- It will address our 'bloated file system' issue
- It will be negelible faster than sql (certainly less bloated and no 3rd party software/riskware)
- no scale issues
- it will make load sharing cake
- it will easily live in "ram disk"
- and make backups much easer.
It should also make the current 'msg read' system much more robust. I have looked at all the major bbs software and no one has figured out how to do a good 'last read' pointer that is real workable yet. VBulletin 4 is close, but 95% of the users don't use it because it is unintelligible.
> The color-coding is fine but FYI now threads no
> longer fit horizontally on the screen on a Netbook.
We have not changed anything in the template in the last 5 years, that would effect that. The only time we do anything that might impact that is during conference runs when we give exhibitors some logo play in the upper right corner (their logos can be a bit wide at times).
Was not about the current first and user msg color test. This was for pure usability.
> I'd rather have only my post/replies colorized....
One of the biggest issues we face is topic drift. It is nice in some threads, but a nightmare in others. To fight that, we are going to start to print the original message as the first message on every page of a thread. We want people to refer back to that starting message. Forums that I have participated in with this feature see a siginifcant number of more ontopic threads. It really helps keep things sane. So by colorizing the first message with the same color, people will learn that is what they are looking at instead of thinking they are looking at a dupe.
> I don't remember when they discontinued the
> personalized templates or if you remember 'em,
Interesting you should mention that. It was before your join date. hmmm.
> Getting back the customization which was dropped
Ya, you will be able to install and run your CSS files. We will give you the default ones to toy with and good luck from there. You will probably need to run those from your own server.
| 2:43 am on May 17, 2010 (gmt 0)|
|We are not using a squeamish (sql) db here. |
Come on, don't make me say 'duh' but I think what I said could be interpreted, in fact, I think you did... Something about the last 90 days or something? How about even threads that are longer than one page? It's fairly easy to tell where I am when they're not...
The flat-file DB system you've been running is not Berkley compatible or something like that if I remember correctly... (You said that in 2005 I think? Fascinating, because I think I remember reading it when it was posted.)
Didn't I also say it would depend on exactly how the information was stored? Yeah, but... LOL. And BTW thanks for sharing because it's good to know how the big kids do it, so thanks for sharing the info. :) I've got a lil project I'm working on and your post gives me an idea or two I think I might look into.
|Interesting you should mention that. It was before your join date. hmmm. |
Yeah, it seems like I've been here for years to me too, go figure... ;)
| 10:17 pm on May 17, 2010 (gmt 0)|
@Brette... thanks for update.
@MadScientist... the color code does give us "last read" (see my previous above).
There's a bit of a tempest in a teapot, head bangin', and wishful thinking. WW works great as is, and is getting better in speed/response.
I'd like to see user defined width and font size for text, but I'm not holding my breath on that one.
What I'd really like to see is memory of my choice of 100 "recent posts" because my broadband works that fast and WW can serve it that fast. Minor irritation, of course, but something I'd like to see user set.
| 2:31 pm on May 20, 2010 (gmt 0)|
Hi there people,
One of the biggest issues we face is topic drift. It is nice in some threads, but a nightmare in others. To fight that, we are going to start to print the original message as the first message on every page of a thread.
Ahem, considering I started this thread after noticing the colours had changed in a post, I wouldn't say as this is too much of a drift ;)
Nice touch, when will this be brought in?
Keep up the good work!
| This 38 message thread spans 2 pages: < < 38 ( 1  ) |