don't show widgets on array or code blocs

[patriciogonzalezvivo]

[louh]

@patriciogonzalezvivo Do you remember what this was about?

[patriciogonzalezvivo]

Yes... prevent widgets to mess with arrays like color: [[15,[0.,0,0]], [20,[1.,1.,1.]]] or JS blocks like color: function() {return [1.,0,0]}

[louh]

Got it - do we have an idea of how we want to address this? Should a color picker mark never appear if the value string is not actually parseable by the color picker? This is similar to how Chrome's inspector works.

[bcamper]

In the first case the ideal would be to create a color picker for each of the inner color values... But that obviously requires a lot more parsing.

For JS functions, makes sense to show nothing I think.

On Saturday, September 10, 2016, Lou Huang [email protected] wrote:

Got it - do we have an idea of how we want to address this? Should a color picker mark never appear if the value string is not actually parseable by the color picker? This is similar to how Chrome's inspector works.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tangrams/tangram-play/issues/211#issuecomment-246118570, or mute the thread https://github.com/notifications/unsubscribe-auth/AABBXeOVtzACzLG1ksn4P-Z-Nz2xuJDTks5qos8-gaJpZM4GTK3s .

[louh]

What does it actually mean when a color value is [[15,[0.,0,0]], [20,[1.,1.,1.]]]? Is this documented anywhere?

Also would it be equal to expressing this in YAML's sequence notation?

color:
  -
    - 15
    -
      - 0.
      - 0
      - 0
  -
    - 20
    -
      - 1
      - 1
      - 1

On Sat, Sep 10, 2016 at 11:53 AM Brett Camper [email protected] wrote:

In the first case the ideal would be to create a color picker for each of the inner color values... But that obviously requires a lot more parsing.

For JS functions, makes sense to show nothing I think.

On Saturday, September 10, 2016, Lou Huang [email protected] wrote:

Got it - do we have an idea of how we want to address this? Should a color picker mark never appear if the value string is not actually parseable by the color picker? This is similar to how Chrome's inspector works.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/tangrams/tangram-play/issues/211#issuecomment-246118570 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AABBXeOVtzACzLG1ksn4P-Z-Nz2xuJDTks5qos8-gaJpZM4GTK3s

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tangrams/tangram-play/issues/211#issuecomment-246119297, or mute the thread https://github.com/notifications/unsubscribe-auth/ACb1tHUIO4Jrvhl6H-SHXWqivIrVFzS3ks5qotJqgaJpZM4GTK3s .

[bcamper]

It means it has multiple values interpolated by zoom:

https://mapzen.com/documentation/tangram/yaml/#stops

On Saturday, September 10, 2016, Lou Huang [email protected] wrote:

What does it actually mean when a color value is [[15,[0.,0,0]], [20,[1.,1.,1.]]]? Is this documented anywhere?

Also would it be equal to expressing this in YAML's sequence notation?

color:
-
- 15
-
- 0.
- 0
- 0
-
- 20
-
- 1
- 1
- 1

On Sat, Sep 10, 2016 at 11:53 AM Brett Camper <[email protected] javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

In the first case the ideal would be to create a color picker for each of the inner color values... But that obviously requires a lot more parsing.

For JS functions, makes sense to show nothing I think.

On Saturday, September 10, 2016, Lou Huang <[email protected] javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Got it - do we have an idea of how we want to address this? Should a color picker mark never appear if the value string is not actually parseable by the color picker? This is similar to how Chrome's inspector works.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/tangrams/tangram-play/issues/211# issuecomment-246118570 , or mute the thread < https://github.com/notifications/unsubscribe- auth/AABBXeOVtzACzLG1ksn4P-Z-Nz2xuJDTks5qos8-gaJpZM4GTK3s

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/tangrams/tangram-play/issues/211# issuecomment-246119297>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACb1tHUIO4Jrvhl6H- SHXWqivIrVFzS3ks5qotJqgaJpZM4GTK3s> .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tangrams/tangram-play/issues/211#issuecomment-246124035, or mute the thread https://github.com/notifications/unsubscribe-auth/AABBXabABP2O-3F1BOgKhC7p7jCK7jTGks5qoudngaJpZM4GTK3s .