Short description
User photograph is more well-marked than literal username. it's sign of user, especially when user sign or comment in some pages. By now, in moin, users sign with their username, if we read through pages in ThreadMode, the user literal signature is submerged in their words. but if a foto is displayed instead of username or with username, it's more clear to follow who is talking about what.
I think this feature can be implemented by upload a foto to user homepage with certain name, say "foto.jpg". When user sign in wiki pages, moin try to find the foto and display it.
Have you figured out yet how big a photo must be, so that a person could still be recognised well? I like the idea, but displaying a photo could also waste a lot of space and spoil the layout when used in the wrong places... Why don't you provide a macro [[ImageSig(UserName)]] for that? UserName normally points also to the users wikihomepage and there you can fetch the photo..
The size of photo may be commonly used 48x48 or so. It can be decided by the wiki admin. See http://www.communitywiki.org/en/CwbTotal for example. The ImageSig idea is cool. Let's go even further, the userfoto feature can be implemented in UserPreferences pages, provided as optional choice of signature. -- ZhangYunfeng 2006-10-09 01:39:21
This is a good idea. But integrating this in the users preference menue is an integration as deep in the Moin code as the SIG-solution. This might be also the better solution, but in the meantime you could provide some macro ImageSig(UserName) for that just in simply rewriting a bit of code of the Image Macro or ImageLink Macro (see MacroMarket). All the macro has to do is to look on the users homepage for an attachment photo.png. Users then could sign like this -- 84.161.163.117 [[DateTime(2006-10-10T13:46:43Z)]] or [[Date(2006-10-10T13:46:43Z)]]-[[DateTime(2006-10-10T13:46:43Z)]] ImageSig(UserName) . This is not the best solution, but must work..
You can do that by Include(!UserName/Photo) now. May be we can add the behaviour of the NewPage extension @ME to use it like Include(@ME/Photo) or by an own var in your MyDict. For adding an own var see HelpOnVariables. I would prefer a solution like this, so we don't extend the amount of macros too much. You can have a look at ReimarBauer/MyDict. -- ReimarBauer 2006-10-10 15:11:44
Everywhere where I do set @ IMG @ without the blanks I got the image. It's intresting to use variable instead of macro, since @ SIG @ has been an intrinsic variable. And it's ok to use @ IMG @ for display a user photo. How about put it into moin code?
Moreover, just displaying a photo is not enough. In my origional idea, when signing, the username and user photo which links to user homepage should display together (just like what the CommunityWiki does)
It's not difficult to put it in the Moin code. But we should first find the best var name for this feature. @ IMG @ is may be to generic for an user image. So we are looking now for two vars one for the combination of @ SIG @ and @ IMG @ and one to replace the IMG name. If we do have them I can add a patch for 1.6 dev. But it needs to be discussed too where we store the image data. -- ReimarBauer 2006-10-11 06:48:13
Why don't we call the var @ IMAGESIG @ and @ USERPHOTO @. Maybe we could provide in the user preferences an extra input box under "User CSS", where one could upload his image.
both are long words. so what is with @ ISIG @ and @ IAM @? The upload box in preferences is not the problem, it must be discussed if the photo is stored in wiki or mywiki and how the sizing is done. At first it could be in that way implemented that only sizes below and equal 48x48 are accepted. I don't want to have on default PIL needed to get the wiki working.
Must the variable name be uppercase or not? Here's mine: @UserFoto@, @MyFoto@. I think, the size is not a problem. The size hint can be displayed to tell what is accepted. Even if the photo size is too large, it can be modified later by the user or admin. I'm not familiar with the storage scheme, shouldn't the photo store in the user homepage as a attachment, so it can be manipulated easily?