| |
|
Please facilitate us become cucumis-millionaires :-)Improvement
Results 1 - 5 of about 5 | | | 17 September 2006 02:19 | | The requested translations page lists all translations in source/ target pair in some order, probably in the order of date they were requested.
Well, there could be some more materialistic, "points-earned" oriented persons like me who wish to become cucumis millionaires. :-) I want to earn as many points as I can.
I was thinking if there could be a method of getting the "requested translation" list in the decreasing/ increasing order of POINTS-VALUE OF A TRANSLATION. That is, showing high value translation first (250, 150, 75, etc.) and showing low-points translations (7, 5, 4 etc.) at the end.
then, I can do high-points translations first and quickly become a millionaire. :-)
When I have less time, or am feeling not like putting too much efforts, I can go to the other end of the list and start doing least-value translations first, that will be mostly single words or small phrases.
Thanks.
| | 17 September 2006 07:53 | | That sounds possible.
Another option would be to keep the date order and adding a new condition on the translation value.
For example, only kep in the list the translation that costs over 50 points, over 100 points etc...
Points > 50
Points > 100
Points > 200
Points > 400
Points > 800
The second solution seems to be easier to implement. But maybe your solution is more efficient. | | 17 September 2006 08:19 | | It will serve the purpose.
And it seems simpler to code as it will not necessitate keeping a separate index on point-values.
For that matter, a From:, Upto: RANGE of point-values can be presented for the user to fill in, and all requests in that range can be displayed.
say:
display Requested translation having value points
from: ____ upto: ______
The default values could "From: 0 Upto: Max", that will give us entire list as is presently displayed.
Someone might give some specific range say
"From: 100 Upto: Max" or
"From: 0 Upto: 25"
and translations having only those value-points become visible.
Whichever is the simplest to implement. | | 3 May 2007 14:47 | nava91Number of messages: 1268 | Yes, for me, the VSRawat's idea is good... | | 3 May 2007 19:05 | | It's in the todolist, but there are more important thigns to do first |
|
| |
|