Re: [Haskell-cafe] Re: Haskell Logo Voting has started!
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this: "Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have: (105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: ) moving down X will result in either (105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: ) or equivalently (105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D) of course, maybe you already know that but you're saying that it is doing this wrongly ;) Btw, I really think the logos should be on the same page as the voting form. Hotkeys for the buttons would be good too. It's usable though if you (incorrectly) consider the numbers as a sort of reverse "star rating" to make a O(n) pass, possibly finetuning later. Greetings, Daniel
(correction of the example) (105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: ) moving down X will result in either (105: A) (106: B) (107: X ) (108: C,D) (109: E ) (110: ) or equivalently (105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: E)
QED
2009/3/17 Daniel Schüssler
(correction of the example)
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: E ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: E) _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
-- We can't solve problems by using the same kind of thinking we used when we created them. - A. Einstein
On Tuesday 17 March 2009 21:03:21 Rick R wrote:
QED
Hmm? Maybe if confusingness was to be demonstrated, but not bugginess. Both possibilities will result in the same total preordering (defined by (x `betterThanOrEq` y) iff (numberInCombobox x <= numberInCombobox y)), and (AFAIK) only this ordering matters for condorcet. Greetings, Daniel
On Tue, Mar 17, 2009 at 04:03:21PM -0400, Rick R wrote:
QED
Only relative ordering matters for condorcet, not the absolute rank. e.g., ranking A, B and C rank 1, and D, E and F rank 6 is exactly the same as ranking e.g., ranking A, B and C rank 2, and D, E and F rank 3. In both cases below, moving X down is moving X from the same rank as B to a new rank between B and C,D. Presumably moving it down a second time would merge the X and C,D ranks. Personally, I found assigning ranks with the dropdown list to be easiest. I first sorted them into approx 8 buckets (using ranks like 10,20,40,60,80,100 as buckets, although some ended up between two buckets), and then sorted my highly ranked buckets (where "high" is the end near 10).
2009/3/17 Daniel Schüssler
(correction of the example)
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: E ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: E)
Thanks Ian
On Tue, 17 Mar 2009 20:34:12 +0100
Daniel Schüssler
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this:
"Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have:
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D)
of course, maybe you already know that but you're saying that it is doing this wrongly ;)
Yes, I am saying that. To be more specific: I saw the current Haskell logo get put back in the top position even though I had pushed it down, and I saw three of my choices which I ranked quite highly, pushed down to the bottom. Scarily bad. However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up. -- Robin
Am Dienstag, 17. März 2009 21:08 schrieb Robin Green:
However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up.
If you announce it on the mailing list, I might use it. By the way, when will the voting period be over? Best wishes, Wolfgang
Firstly, apologies to everyone for sending the same message to the list
five times, yesterday! The mailserver I use kept timing out, and I had
thought that my mail client would handle attempts to resend an email
appropriately, but apparently not. Time to put a paper bag over my head!
On Wed, 18 Mar 2009 11:43:26 +0100
Wolfgang Jeltsch
If you announce it on the mailing list, I might use it.
I'm afraid it is entirely terminal-based (i.e. text only), so it doesn't show the pictures. Someone could try and convert it into a web app and display the pictures, but I have no plans to do that. It is not working at the moment, but I hope to get it working and announce it later this week.
By the way, when will the voting period be over?
The polling page says "The poll ends March 24, 2009 at 12:00 UTC". -- Robin
Am Mittwoch, 18. März 2009 03:22 schrieb Robin Green:
I'm afraid it is entirely terminal-based (i.e. text only), so it doesn't show the pictures.
Hmm, this doesn’t help me since I’ve already written a terminal-based app. See attachement. However, no guarantees that this app works as intended. The preferences shown by the app are currently meant to stand for better logos if they are lower. So 1 is the winner, not 113. Well, the terminal-based app is still not enough for me since it’s way too time-consuming to always lookup the pictures. You should have a GUI showing the pictures and allowing you to select the better one of a pair by a single click. Best wishes, Wolfgang
On Tue, 17 Mar 2009 20:34:12 +0100
Daniel Schüssler
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this:
"Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have:
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D)
of course, maybe you already know that but you're saying that it is doing this wrongly ;)
Yes, I am saying that. To be more specific: I saw the current Haskell logo get put back in the top position even though I had pushed it down, and I saw three of my choices which I ranked quite highly, pushed down to the bottom. Scarily bad. However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up. -- Robin
On Tue, 17 Mar 2009 20:34:12 +0100
Daniel Schüssler
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this:
"Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have:
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D)
of course, maybe you already know that but you're saying that it is doing this wrongly ;)
Yes, I am saying that. To be more specific: I saw the current Haskell logo get put back in the top position even though I had pushed it down, and I saw three of my choices which I ranked quite highly, pushed down to the bottom. Scarily bad. However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up. -- Robin
On Tue, 17 Mar 2009 20:34:12 +0100
Daniel Schüssler
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this:
"Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have:
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D)
of course, maybe you already know that but you're saying that it is doing this wrongly ;)
Yes, I am saying that. To be more specific: I saw the current Haskell logo get put back in the top position even though I had pushed it down, and I saw three of my choices which I ranked quite highly, pushed down to the bottom. Scarily bad. However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up. -- Robin
On Tue, 17 Mar 2009 20:34:12 +0100
Daniel Schüssler
Hi,
Even worse, the buttons for moving items up and down are buggy - at least on my browser (Firefox 3.1 beta 2 on Linux). They sometimes reorder my other votes! Even assuming that the list box code is not buggy (which I now doubt), not being able to use the buttons makes this form almost unusable!
I guess it works like this:
"Move down" on an element X will make the /smallest/ change (with respect to the abstract ordering) that makes X worse than it's current value. This may require changing more than one number, for example if we have:
(105: ) (106: A) (107: X,B) (108: C,D) (109: E ) (110: )
moving down X will result in either
(105: A) (106: B) (107: X ) (108: C,D) (109: D ) (110: )
or equivalently
(105: ) (106: A) (107: B ) (108: X ) (109: C,D) (110: D)
of course, maybe you already know that but you're saying that it is doing this wrongly ;)
Yes, I am saying that. To be more specific: I saw the current Haskell logo get put back in the top position even though I had pushed it down, and I saw three of my choices which I ranked quite highly, pushed down to the bottom. Scarily bad. However, I am now hacking together a quick-and-dirty utility for ranking things which I will put on hackage. I'm not sure that anyone other than myself will use it, but it's fun hacking it up. -- Robin
participants (5)
-
Daniel Schüssler -
Ian Lynagh -
Rick R -
Robin Green -
Wolfgang Jeltsch