2010/3/12 2:07:12
|
---|
|
Core rating feature?So we have a ratings feature in the core, there is a link but that contains no information and so questions are raised:
Quote:
And there isn't one word about the feature never mind completed. We should be careful in our wording as here we're lying. In the table for ratings you pretty much have a way to record the ratings per user and an overall average must either be stored elsewhere or calculated each time. If we look at the MyAlbum module this has two tables one for photo information which contains a column that records the average for all votes and then a whole table similar to the one in the core to record the individual user votes. So, because I haven't seen a user vote in the cores table yet, can one be deleted? If it can be deleted is there a way for it to update an average value in a module table? Or is the average to be calculated on every page load which would make a waste of resources perhaps? Can a user change his mind and thus his vote? Again how would that average be calculated? Perhaps in future a good way to tackle new features is that who ever develops them in the core also produces a tutorial ready for the release of the CMS or shortly after. That shouldn't be as time consuming if done as the feature is completed and not all in one go with a mass of things to cover, well unless its one person developing it all, lol. |
2010/3/12 5:59:36
|
---|
|
Re: Core rating feature?This feature definitly has a lack of documentation. david requested some clearing words about it a while back and I told him to use it for some rating features in the profile module. I just don't have the time to do it now.
I'm sure I can answer all of your questions afterwards. |
2010/3/12 9:19:05
|
---|
|
Re: Core rating feature?I'll have a little play with the profile module then
|
2010/3/12 9:43:22
|
---|
|
Re: Core rating feature?But it's not yet in there and it might take another little while until it will be in there
|
2010/3/12 9:56:34
|
---|
|
Re: Core rating feature?Ah, sorry, I misunderstood.
So we have no modules using this feature at the moment? So no example code.... |
2010/3/12 13:23:46
|
---|
|
Re: Core rating feature?... not yet - but it's something I'm going to add to the Module team suggestion list in a moment or two
|
2023/4/22 10:51:41
|
---|
|
Re: Core rating feature?Going through the upcoming release and making sure everything still works - it looks like we never finished this. The wiki page has moved - it's now at https://www.impresscms.org/modules/simplywiki/index.php?page=Ratings If anyone has an example of this and how it was intended to be used, that would be great! It came from SmartObject |
2023/4/26 14:08:46
|
---|
|
Re: Core rating feature?That is correct, it never got finished and as a result has never been used. I proposed a few years ago to remove it from the core until we had a working solution, but I got some resistance to that idea. The description from Tom is more or less what I would expect it to do in its basic form : you have a calculated value that is updated each time someone votes, and that value is the one that is retrieved at display time. Each user should have a list in his user profile with all the votes that he cast. Perhaps it would be a useful feature to let admins determine if votes can be changed once cast, or even removed. A rating type would be interesting to have : for example when rating a module, you can define that there are multiple ratings that you want to capture : ease of installation, feature set, compatibility with existing modules, ... That means that you need to be able to link the vote to an object, and also define for this type of object which categories of votes can be cast. A good place to integrate this would be the downloads module (which has other issues), there the voting |
_________________
|
2023/4/27 7:47:51
|
---|
|
Re: Core rating feature?Well, something to add to another release - finish this feature. For now, I'm not going to worry if it works in the new release, as it has nothing. Maybe we should add something to the page that it is under development and provide a landing page for feature discussion and development. BTW - the Preview function does not work here. The page reloads, the editor area is empty, and there is no preview. |