On Feb 25, 2016, at 3:48 AM, Artjom Kossow <[email protected]> wrote:
thanks for replies. Sorry for such a harsh comment before, I guess I should have just "bumped" the question and thats it
Now to the issue with datetime:
I guess, it must not be a datetime after all, as I just want to display a value (seconds) with a proper scaling of its 10th power (n,µ,m, k, M, G), so that 0.0003123 is formatted to 3.1 µs or maybe even 3123 ns, depending on resolution. I tried NumeralTickFormatter, with "0.0a" but it does not seem to work (it only scales to kilo and mega), and also I can't output "s" to that.
PrintfTickFormatter can output any additional characters you want, but has no scaling options, only option of scientific notation.
So I thought I could try and write my own formatter, but I couldn't find any extensive documentation on your JS api and object model, and examples were not enough. Is there a tutorial for your JS client api?
Which leads us to interactive widgets: there is not much documentation on how to use customJS, only few examples, which give you no idea what is available to you at "js run time", which objects are there, what properties do they have and how to manipulate them.
So, I went the other way and start a python server now, but there is, again, not enough docs to make it clear what you need to do to trigger updates. Code snippet:
p.quad(name="main", top="tops", bottom="bottoms", left="lefts",right="rights", color="colors", alpha=0.8, source=msource)
print("TEST",active) #just to see if it works
p.select(name="main").glyph.visible = False
This code tries to select a quad group named "main" and hide it. If you run the "..glyph.visibble = False" before you make your first draw, the object will not be drawn. So, there should be some way to either trigger a full redraw, or an update... Again, no luck in docs for me
On Wednesday, February 24, 2016 at 6:01:37 PM UTC+1, Bryan Van de ven wrote:
I'm sorry that you have not gotten a timely response to your question, and I empathize with how that can be frustrating. I very much want that every user gets their questions answered. But the reality right now is that sometimes there are more new users and questions than there are people and time to answer all of them. The Bokeh community is still fairly young, after all. But there are more and more people participating and answering questions now, though, so my hope is that we are nearing a "critical mass" where the number of people who feel confident enough to offer answers and support rises dramatically.
All that said, I'd just like to echo what Dennis said. The number one things that help me decide to jump in to a question are:
* detailed description of what is desired
* detailed description of what has been tried
* example code to get me started
And the reason is this: Even answering "quick" question can take 10 or 15 minutes (it takes time to go look through source code or docs to make sure I am speaking correctly, e.g.), If I have to try and create example code from scratch, that number can go up dramatically. There's only so many hours in the day. But the main dis-incentive is if the problem is not fully specified. If I would have to guess at what you really want and need, then I risk being wrong, and going to all that time and effort to answer the wrong question!
For instance in your case, do you only need labels "around" the nanosecond scale, or do you need the entire current large scale set of tick labels PLUS nanosecond labels in addition? There are different possibilities depending on these kinds of details. In the former case, you might get away easily with by pre-scaling your data and using PrintfTickFormatter. In the latter case, we'd probably need to look at extending the existing DatetimeTickFormatter here:
Or equivalently (and probably more quickly for a general user) creating a custom TickFormatter model to suit your needs. There are already some examples of custom TickFormatters that you could look at immediately to get you started, for example:
> On Feb 24, 2016, at 2:16 AM, Artjom Kossow <[email protected]> wrote:
> I guess a "community" support means no support at all Okay then.
> On Friday, February 5, 2016 at 10:03:54 AM UTC+1, Artjom Kossow wrote:
> first of all, a big chunk of gratitude from my side for creating such awesome tool! Thanks
> Now to the question: I am plotting a profiling data of a program with a nanosecond tick resolution. Is it possible to modify datetime x axis scaling in such a way, so that nanoseconds are also supported? I really want to see some meaningful labels (like x µs, y ms) on bigger zoom levels, and not e.g 5.0e+6
> Btw, is there a way to add interactive widgets (like checkboxes) without starting a server?
> Thanks for the help!
> Best Regards,
> 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 [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/2050b214-8714-4e46-bbaf-4555517b4a50%40continuum.io.
> For more options, visit https://groups.google.com/a/continuum.io/d/optout.
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/1265c362-a547-4f17-8c85-12c7bd3434ce%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.