@congzhangzh Quick update. The work being done by @rreusser is almost ready for use. We are just working on a few final edge cases.
Tks for you both works, it's great to hear you are near to finish, I will wait for your guys finish es module support, and focus on other side of my project first.
Hey, just a quick introduction based on my talk with @mootari. We talked a bit about ES module distribution, which I think pretty quickly led to a focus on messaging. Perhaps to the extent that if some reasonable ESM solution can be achieved (or is already achieved via jsdelivr?), then the real question is: who is the target audience and what is being done to help them understand stdlib.
To me, it seems that there are at least three fronts the project can move forward on: 1) functionality, 2) documentation (tutorials, motivation, examples, API docs), and 3) actually enabling the target audience to use it
I think 1) is where the majority of the effort has gone (apart from API docs, which are comprehensive if not yet ideal to navigate), and I'm a little hesitant to push too far forward on 3) before taking a stab at 2) and better outlining the motivation, getting started guides, etc.
And there were some good points like: what is the use-case for node+native modules if one could simply use python/etc in that environment? Does this push toward really emphasizing web/interactivity since that's the particular value that stdlib is in unique a position to offer?
Anyway, it was a good conversation which I think pretty quickly got to the root of some issues and questions. I don't want to monopolize the discussion but just wanted to give some context around @mootari 's interest. :wave:
Hate to put you on the spot, but @mootari, are there particular areas/questions around some of these things which you're interested in exploring?
Not yet. I'm planning to start with a survey: look for public mentions of stdlib and accompanying discussions, try to extract the key expectations and pain points, as well as reservations and misconceptions. I then want to compile and condense the results and see "what sticks".
I think I'll start by reviewing what stdlib has, by reviewing what comparable libraries have, and then by just writing some raw markdown content and we can worry about interactivity or website organization later.
@mootari You may also want to chat with @Planeshifter who has been using
stdlib in an e-learning platform deployed at Carnegie Mellon University since the early days of stdlib development.
I can also provide more insight into other usage of the project, such as on-line spreadsheets, calculator apps, etc.
@kgryte do you still remember the context of https://medium.com/@kgryte/hey-maintainer-of-stdlib-here-e1ec7434575f ?
I forget what the name is now, but you can still get there via stdlib.com, a domain which we unfortunately do not own.
@kgryte On stdlib.io, the documentation link for "Data visualization" leads to a 404: https://stdlib.io/docs/api/v0.0.90/@stdlib/plot
@mootari Thanks for reminding me! Yeah, we need to add a README to https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/plot so that documentation renders there.
@kgryte May I also suggest to move the Resources section in the project readme to the top, above Features?
@trevnorris Would LOWESS work for you? https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/stats/lowess
What is your use case?
Hey guys, I'm checking out your project. Clicking on the Data Visualization link on your home page leads to an error:
{"message":"Route GET:/docs/api/v0.0.90/@stdlib/plot not found","error":"Not Found","statusCode":404}
https://stdlib.io/docs/api/v0.0.90/@stdlib/plot
This error also appears in the docs.
Cool library, I'd love to see what the plotting is like.
@lindseymysse Sorry about that! We have yet to push the change which fixes that 404. You can find the plot constructor docs here: https://stdlib.io/docs/api/v0.0.90/@stdlib/plot/ctor
Note that plotting is somewhat limited atm. Depending on your needs, for more complex chart types, will probably need something else.
@lindseymysse I agree; that would be great! Building a WebGL backend to the plotter would be awesome. But also requires a significant amount of work which I am not sure we have the bandwidth at the moment to expend. regl would be a good candidate to build upon, but this would definitely be a more distant future feature.
@kgryte Totally understand. I've been working on some 3D stuff lately, which is why I ask. For me, I've been using attributes set on aframe.io objects. So, the rendering engine doesn't quite matter, what matters is a good way of reasoning about plotting in 3D. I will probably keep using the stuff I've put together with D3.
Thanks for answering my questions!
@ChrisH2727 The project README has some basic instructions: https://github.com/stdlib-js/stdlib#installation
Do you have a particular use case in mind?
@castarco Heya! Thanks for reaching out. The project does have TypeScript declarations, with about about 98% types coverages. To my knowledge, there is nothing special you need to do use them. The project includes a root
tsconfig.json (https://github.com/stdlib-js/stdlib/blob/develop/tsconfig.json) which should pick up all the declarations. In VS Code, these are automatically picked up and display appropriately in the editor.
Have you already tried using the project in a TypeScript project? And, if so, are the declarations not being picked up?
Maybe the one small caveat is that you may need to use
require rather than import when importing stdlib packages into your project.
@castarco If you encounter any issues, let me know, and I’ll try and reproduce on my end. :)