Seeking API feedback re: vectorized annotations

Luke_Canavan1Mar 28, 2016 #1

In course of adding a Label annotation (the current PR is at: Add label annotation by canavandl · Pull Request #3956 · bokeh/bokeh · GitHub), I generated a couple of questions about the current annotations implementation. Note: the distinction between glyphs and annotations is that annotations don’t support hit-testing and aren’t selectable.

Namely, is it worth vectorizing the implementations of the current Box and Span annotations?

Currently, each annotation is individually created (here’s an example from the User Guide: Plotting with basic glyphs — Bokeh 2.4.2 Documentation). Are there cases and/or visualizations where the user would want to create and manage such a large number of annotations that the non-vectorized implementation would be a problem?

If box and span annotations are acceptable as is, would having vectorized Label annotations be a confusing api difference?

⌁ Link to post

birdsarah_continuumApr 27, 2016 #2

I think having the
option for vectorized would be great.

    M            aybe we

could consider the vectorized a special case and require
the explicit use of “field”
from properties? And if you don’t use “field” your input is always
considered a value?

                    Best,

                      Bird

···

On 3/28/16 10:04 AM,
wrote:

lcanavan@continuum.io

    In course of adding a Label annotation (the current
PR is at: ), I generated
a couple of questions about the current annotations
implementation. Note: the distinction between glyphs and
annotations is that annotations don’t support hit-testing and
aren’t selectable.

–

  You received this message because you are subscribed to the Google

Groups “Bokeh Discussion - Public” group.

  To unsubscribe from this group and stop receiving emails from it,

send an email to bokeh+unsubscribe@continuum.io.

  To post to this group, send email to bokeh@continuum.io.

  To view this discussion on the web visit [](https://groups.google.com/a/continuum.io/d/msgid/bokeh/2dbbd068-d64f-4b57-b297-9510d7bae64a%40continuum.io?utm_medium=email&utm_source=footer)      .

For more options, visit .

–
Sarah Bird
Developer, Bokeh

    [
      ![Continuum Analytics](http://docs.continuum.io/_static/img/ContinuumWordmark.png)
    ](http://continuum.io)

https://github.com/bokeh/bokeh/pull/3956

      Namely, is it worth vectorizing the implementations of the

current Box and Span annotations?

      Currently, each annotation is individually created (here's

an example from the User
Guide: ).
Are there cases and/or visualizations where the user would
want to create and manage such a large number of annotations
that the non-vectorized implementation would be a problem?

http://bokeh.pydata.org/en/latest/docs/user_guide/plotting.html#box-annotations

      If box and span annotations are acceptable as is, would

having vectorized Label annotations be a confusing api
difference?

https://groups.google.com/a/continuum.io/d/msgid/bokeh/2dbbd068-d64f-4b57-b297-9510d7bae64a%40continuum.io
https://groups.google.com/a/continuum.io/d/optout

⌁ Link to post