new component
Joe Edelman
I changed agent_on_map again. I'm introducing a new concept which seems
to be necessary: the viewer looks at what each agent is "up for" and
makes a custom list of assignment suggestions and puts it right in the
agent mapwindow.
Currently this code is at app/ideas_app/ideas_widget, but this is
clearly the wrong place for it.
I think I will do the same thing for landmarks, so that a landmark will
analyze the agents that are available in the area, and what they are up
for, and make some suggestions about what they would enjoy.
The UI is kind of groovy. I'd appreciate if you all would git pull,
make, go look at an agent mapwindow, and tell me what you think of the
colored tags, the dropdowns, etc.
Note also that I made a really powerful, crazy javascript method called
String.to_color(). It picks a pleasing color to go with any short
string, and these are persistent and always the same. So "connection"
will always be a medium blue, and "adventure" will always be a light
green. This is to help dispatchers scan for just the ideas or agents
they're looking for, by color. The function uses some super-intense
math involving hash functions and color spaces.
--Joe
--
J.E. -- http://nxhx.org -- 413.250.8007
agent marmorkuchen
* Joe Edelman <joe.e...@gmail.com> [2009-03-20 16:37 -0400]:
>
> I changed agent_on_map again. I'm introducing a new concept which seems
> to be necessary: the viewer looks at what each agent is "up for" and
> makes a custom list of assignment suggestions and puts it right in the
> agent mapwindow.
>
> Currently this code is at app/ideas_app/ideas_widget, but this is
> clearly the wrong place for it.
yeah, especially as the HTML template is to be found in
components/organize_app/agent_on_map.html. :)
> I think I will do the same thing for landmarks, so that a landmark will
> analyze the agents that are available in the area, and what they are up
> for, and make some suggestions about what they would enjoy.
>
> The UI is kind of groovy. I'd appreciate if you all would git pull,
> make, go look at an agent mapwindow, and tell me what you think of the
> colored tags, the dropdowns, etc.
indeed, it is groovy. a few suggestions:
the menus should receive a mouseover effect (e.g. cursor: pointer), to
support the arrow. and the arrow should point to the right when the menu
is opened.
> Note also that I made a really powerful, crazy javascript method called
> String.to_color(). It picks a pleasing color to go with any short
> string, and these are persistent and always the same. So "connection"
> will always be a medium blue, and "adventure" will always be a light
> green. This is to help dispatchers scan for just the ideas or agents
> they're looking for, by color. The function uses some super-intense
> math involving hash functions and color spaces.
you mean that an idea of type 'adventure' will always be a light green?
why do we need super-intense math for that? something tells me, it might
have something to do with n-to-n mappings of upfors to atags and i
haven't fully grasped the concept yet.
cheers,
Sebastian
--
_ ascii ribbon campaign .oOo. GCSd-s:+aC++ULB+++W++M+PS+++Y+
( )
X Es ist mein fester Glauben, dass es falsch ist, einen festen
/ \ Glauben zu haben.
Joe Edelman
>the menus should receive a mouseover effect (e.g. cursor: pointer), to
>support the arrow. and the arrow should point to the right when the menu
>is opened.
If you want to move the positioning of the popup menu that appears (in
case the downward pointing arrow suggests a different position), that's
in jquery_plus#position().
>you mean that an idea of type 'adventure' will always be a light green?
>why do we need super-intense math for that? something tells me, it might
>have something to do with n-to-n mappings of upfors to atags and i
>haven't fully grasped the concept yet.
could be a hashmap from tags to colors. But I want it to work for any
short string. So I have a perfect hash function that generally produces
very different numbers from very different short strings, and then that
maps to a spot on a brightness/hue cylinder.
>
>* Joe Edelman <joe.e...@gmail.com> [2009-03-20 16:37 -0400]:
>>
>> I changed agent_on_map again. I'm introducing a new concept which seems
>> to be necessary: the viewer looks at what each agent is "up for" and
>> makes a custom list of assignment suggestions and puts it right in the
>> agent mapwindow.
>>
>> Currently this code is at app/ideas_app/ideas_widget, but this is
>> clearly the wrong place for it.
>
>yeah, especially as the HTML template is to be found in
>components/organize_app/agent_on_map.html. :)
>
>
>> I think I will do the same thing for landmarks, so that a landmark will
>> analyze the agents that are available in the area, and what they are up
>> for, and make some suggestions about what they would enjoy.
>>
>> The UI is kind of groovy. I'd appreciate if you all would git pull,
>> make, go look at an agent mapwindow, and tell me what you think of the
>> colored tags, the dropdowns, etc.
>
>
>
>> String.to_color(). It picks a pleasing color to go with any short
>> string, and these are persistent and always the same. So "connection"
>> will always be a medium blue, and "adventure" will always be a light
>> green. This is to help dispatchers scan for just the ideas or agents
>> they're looking for, by color. The function uses some super-intense
>> math involving hash functions and color spaces.
>
>