almarklein

9 ms·

1. 1.▲
   by almarklein 2y ago

   I don't know Datashader that well, but from what I understand, it generates an image from a set of primitives (e.g. points), and then allows you to interactively inspect that image. It does not re-render the points on every frame like
2. 2.▲
   by almarklein 2y ago

   All true, except the bit that wgpu-py compiles to WASM. It's all desktop. In the plans that we do have for running the browser, Fastplotlib, Pygfx and wgpy-py will still be Python, running on CPython that is compiled to WASM (via Pyodi
3. 3.▲
   by almarklein 2y ago

   That's because WebGPU is still experimental. This will change, as it's set to replace WebGL. Fastplotlib / pygfx are primarily meant to run on desktop. When using it via the notebook the server does the rendering. As Ivo said
4. 4.▲
   by almarklein 2y ago

   I have a feeling there's room for improvement for importing Pygfx as well. I think we should indeed strive that simple plots load super-quick.
5. 5.▲
   by almarklein 2y ago

   To clarify this a bit, wgpu is a Rust implementation of WebGPU, just like Dawn is a C++ implementation of WebGPU (by Google). Both projects expose a C-api following webgpu.h. wgpu-py Should eventually be able to work with both. (Disclaimer:
6. 6.▲
   by almarklein 2y ago

   One big difference is that Fastplotlib is based on GPU tech, so its capable of rendering much larger datasets interactively.
7. 7.▲
   by almarklein 2y ago

   Not sure if this is what you're asking :) but the UI framework will somehow provide access to the OS-level surface object, so that the GPU API can render directly to the screen.
8. 8.▲
   by almarklein 2y ago

   Yeah, sounds like QRhi is about at the level of WebGPU/wgpu-py. It sounds to me that Qt created their own abstraction over Vulkan and co, because wgpu did not exist yet. I can't really compare them from a technical pov, because I&
9. 9.▲
   by almarklein 2y ago

   Apart from being based on wgpu, Pygfx also has a better design IMO. Korijn deserves the credit for this. It's inspired by ThreeJS, based on the idea to keep things modular. We deliberately don't try to create an API that allows yo
10. 10.▲
    by almarklein 2y ago

    I wish. The revenue from the ads goes to readthedocs, AFAIK nothing is paid to the maintainers of the project. That said, readthedocs is a pretty nice platform to host your docs in a simple way. Plus users are not tracked. So personally I d
11. 11.▲
    by almarklein 2y ago

    From what I understand, QRhi has a very different purpose then Pygfx, so I'm not sure how to answer this question.
12. 12.▲
    by almarklein 2y ago

    This is indeed one of the major differences. Many of the problems that are plaguing Vispy are related to OpenGL. The use of wgpu solves many of them. Also, wgpu forces you to prepare visualizations in pipeline objects, which at drawtime req
13. 13.▲
    by almarklein 2y ago

    It's definitely still our intention to make it run in the browser. We're not actively working on that yet, but we've recently been able to remove some hurdles on that path, in particular the issue related to Webgpu being asyn
14. 14.▲
    by almarklein 4y ago

    As a contractor I would never install spyware on my machine for a client. That's not a healthy professional relationship. I do see the problem that some people pretend to be more experienced than they are, or worst case are scamming cl
15. 15.▲
    by almarklein 4y ago

    I'm generally eager to share what I make, and have written quite a few open source tools. It's gratifying to polish up a piece of software to a high standard ... But deliberately not sharing your creation, keeping things idiosyncr
16. 16.▲
    by almarklein 6y ago

    Improved support for using the keyboard, including keyboard shortcuts.
17. 17.▲
    by almarklein 6y ago

    This has been fixed now.
18. 18.▲
    by almarklein 6y ago

    This has been fixed!
19. 19.▲
    by almarklein 6y ago

    Good point. I guess I just defaulted to GPL. At first glance, I think it does not matter since Aferro protects code that runs serverside, and the TimeTagger library is both server and client side code. Edit: but it would not hurt to consid
20. 20.▲
    by almarklein 6y ago

    Thanks, good point!
21. 21.▲
    by almarklein 6y ago

    Thanks for the clarification! I see what you mean now. 1. I think I'd go with graying-out records that do not match the selected tags. 2. The tags are part of the description, but indeed this is hard to process further. We should add a
22. 22.▲
    by almarklein 6y ago

    Thanks for the feedback! Your suggestion about tag colors is interesting - my earlier timetracker (timeturtle.app) does exactly this, but I felt the colors were too distracting. Will think about how to bring back some of the info in the ove
23. 23.▲
    by almarklein 6y ago

    Thanks for the constructive feedback!
24. 24.▲
    by almarklein 6y ago

    Will check it out, and am looking forward to your writeup!
25. 25.▲
    by almarklein 6y ago

    I figured I'd want to make it cheaper than Toggl et al., because people might feel they'd get less features. Plus there is no free plan, so the paid plans don't have to pay for the free users ;) - Anyway, I'm kinda done
26. 26.▲
    by almarklein 6y ago

    Thanks, I'm glad someone actually takes notice. I really care about this, and would love more people to do too :)
27. 27.▲
    by almarklein 6y ago

    Thanks for the feedback! The blocks on the left (in the timeline) represent the individual time records. These are indeed "glued together" when a new record starts right after another stops. You can only drag a record in the timel
28. 28.▲
    by almarklein 6y ago

    Sounds like a cool project, but I think I'll focus on my Python scrips for now :)
29. 29.▲
    by almarklein 6y ago

    That sounds cool!
30. 30.▲
    by almarklein 6y ago

    Thanks for the great feedback, very valuable indeed! At the moment, deleting a record is not implemented yet, but it's somewhere near the top of the todo list :)