Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/items/model/_itemquery.class.php on line 628
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/items/model/_itemquery.class.php on line 628
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/_core/_misc.funcs.php on line 870
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/_core/_misc.funcs.php on line 981
| [plugin] jQuery Imagefit plugin » |
Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/_core/_misc.funcs.php on line 870
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/_core/_misc.funcs.php on line 981
Userlist widget
Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /home/hemmi3/public_html/blog/inc/sessions/model/_hit.class.php on line 901
<fplanque> afwas: one where you can decide how challenging it is:
<fplanque> start with a widget that lists users
<fplanque> the add options like
<fplanque> restrict to the ones who commented
<fplanque> restrict to the ones who posted in this blog
<fplanque> order by # of posts
<fplanque> order by last commented date etc
<fplanque> put in as many or as little filters / sortings as you want
<fplanque> someone else will add the missing ones
<Afwas> OK will do that
<fplanque> another option: what to do when you click on a username:
<fplanque> 1) see posts
<fplanque> 2) see comments
<fplanque> or
<fplanque> 3) see profile
<fplanque> or 4) send message
<fplanque> again optional
<Afwas> That would be a widget that can be added multiple times
<fplanque> yes
<fplanque> use the universal item list widget as an example
<Afwas> OK will take a note
<fplanque> that one even has "dumbed down" versions for specific lists
<Afwas> Haven't seen that one yet, but you wrote about it.
<fplanque> this would be the "universal user list" with tons of options to be added over time
<Afwas> I get the idea.
<fplanque> it's in 3,1,0 and can be used standalone but also as a base class for "simplified item list widgets"
<fplanque> ok food now
<Afwas> (me to)
<fplanque> another filter possibility: restrict to users currently online
<fplanque> and we actually had code for displaying who's online at some point. I don't know what happened. Prolly blueyed knows.
<Afwas> online widget
<Afwas> That one exists as plugin IIRC (If I Recall Correctly)
<fplanque> ok, makes sense that we moved it to a plugin
<Afwas> It's a class, so I'd be able to call it independently
<Afwas> So an idea would be a list (post, comments whatever) with a small icon for users who are online
<fplanque> no the idea would be a list of users
<fplanque> a list of usernames
<Afwas> yes
<fplanque> not a list of posts
<fplanque> for example it would be teh list of users who have posted recently
<Afwas> and an icon for the users that happen to be onine
<fplanque> yes, why not
<fplanque> I was thinking about just a list of users who are online
<fplanque> but having an icon for online status in front of every user in any user list can be a useful option
<Afwas> That one exists. But because it's an independent class it could be an option in a user list widget.
<fplanque> I just looked at the code for the who's online widget
<fplanque> it is extremely poor
<Afwas> The class is fine
<fplanque> it fires one query per user
<fplanque> don't use that
<Afwas> I used it in the chat widget
<fplanque> the OnlineSessions class?
<Afwas> The chat widget presented a list with online users to chat with
<Afwas> I need to rewrite parts of it because it took to much recources. But the problem was not the online users.
<Afwas> But it's possible that is a problem if there are to many users ('it doesn't scale well')
<fplanque> that class is loading a User object per online user. that is no good.
<Afwas> I see
<fplanque> I think it's much better if you do the generic user list
<fplanque> and then add some SQL to determine who's online
<fplanque> to the query you'll already have
<Afwas> ok
<Afwas> That doesn't sound complicated.
<fplanque> it's always easier when you go one step at a time 
TO BE CONTINUED
Trackback address for this post
Feedback awaiting moderation
This post has 1 feedback awaiting moderation...
Comment feed for this post