flow-typed
Scrawl-canvas
flow-typed | Scrawl-canvas | |
---|---|---|
3 | 38 | |
3,765 | 311 | |
0.1% | - | |
8.2 | 8.5 | |
about 2 months ago | 6 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flow-typed
-
TypeScript is terrible for library developers
I'm very curious, which "Redux code" are you referring to here?
I don't think the `redux` core lib ever shipped any Flow types itself. Looking at the FlowTyped repo, I see community typedefs at https://github.com/flow-typed/flow-typed/tree/master/definit... , and the Git history suggests those were indeed written by community members.
(of course on the flip side, _I_ didn't even start learning TS myself until 2019, and goodness knows _that_ has been a lot of trial and error over time :) )
-
Is Flow moving away from (or toward) broader community relevance?
As for configurability of whether casts should error, in my experience with flow it's paradoxically riskier to rely on a type nag when refactoring an unknown "offending" type casts. I've ran into cases where upgrading flow raised a cast issue, it got "fixed" it in a way that made the type system happy, but inadvertently broke tests because falsy values are tricky like that. Here's an example where a type nag showed up for someone refactoring, they did what they thought was reasonable to silence it, and proceeded to accidentally break the entire tool (slipping through tests and code review, to boot). This happened in the flow-typed tool of all places.
-
Creating a modern JS library: TypeScript and Flow
The process of supporting Flow users is extremely similar to that of TypeScript. Instead of adding the definition file to "types" in package.json, make a .js.flow file alongside every .js file that is being exported (for example, if you export lib/index.js, make sure to create lib/index.js.flow with the definitions). See the docs on how to create such a definition. If you want to support Flow yourself, don't publish to flow-typed; it's mainly meant for community members to create their own types for third-party packages and publish them there.
Scrawl-canvas
-
Figma's Journey to TypeScript
I don't like Typescript because it forces me to think about types and data structures and stuff. Which is a Good Thing because I absolutely have to think about that stuff when working on large codebases with a team of colleagues: without the inline documentation and text editor help TS gives me when working on those codebases I'd be (at least!) 10x slower when refactoring old code or adding new code. And nobody wants to pay a slow developer!
However ... the one place I refuse to use Typescript is in my side project - a JS canvas library. I can justify this because: 1. it's a big codebase, but I know every line of it intimately having spent the last 10 years (re-)writing it; 2. nobody else contributes (and I kinda like it that way); and 3. I keep a close eye on competing canvas libraries and I've watched several of them go through the immense (frustrating!) work of converting their codebases to TS over the past few years and, seriously, I don't need that pain in my not-paid-for life.
Even so, I do maintain a .d.ts file for the library's 'API' (the functions devs would use when building a canvas using my library) because the testing, documentation and autocompletion help it offers is too useful to ignore. It is additional work, but it's just one file[1] and I can live with that.
[1] https://github.com/KaliedaRik/Scrawl-canvas/blob/v8/source/s...
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
> working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place
I can confirm this. I've been working on a (much simpler!) text layout engine for my canvas library over the past couple of months and the amount of complexity associated with just stamping some glyphs onto a canvas has left me screaming at my laptop on an almost daily basis. Getting a decent underline was a proud moment!
Question: did you ever find out what algorithm the various browsers are using to calculate how many words can fit on a given line? I'm almost there, except words will occasionally jump between lines when I scale the text. Really annoying!
The PR's still a work in progress, but I've got all the functionality I want in there (shaping lines to fit in non-rectangular containers, styling text, text along a non-straight line, dynamic updates, etc). Just need to test and document it all now ... https://github.com/KaliedaRik/Scrawl-canvas/pull/75
-
Ask HN: What are you working on this year?
I've got myself organised and prepared a List Of Things To Do[1] to make my 2D Javascript library even better than it already is. Given that I've been working on the library for over 10 years now, and have never before set out such a list, I call this Progress!
[1] https://github.com/KaliedaRik/Scrawl-canvas/discussions/cate...
-
Pixelating Live with SVG
'Kay, I don't know if this anywhere close to what the OP wants, but this sort of live browser tab manipulation is possible to do using a mix of a a canvas element and the browser's Screen Capture API[1] (plus my JS canvas library, once I merge and publish the changes into its next release[2]).
This solution[3] shows the modified browser tab in a separate browser tab. I've got no idea whether it's possible to do the same sort of trick in the same tab (but probably not). I also have no idea how secure the Screen Capture API is - I'd get very nervous about doing this sort of thing when looking at my bank's online portal!
[1] https://developer.mozilla.org/en-US/docs/Web/API/Screen_Capt...
[2] https://github.com/KaliedaRik/Scrawl-canvas/pull/57
[3] Youtube video of the effect: https://www.youtube.com/watch?v=hCi6LmKMAo0
- Scrawl-canvas 2D canvas library ā proposed roadmap
- Scrawl-canvas - a Javascript library for working with the HTML5 <canvas> element
-
Motion Canvas ā Visualize complex ideas programmatically
My canvas library's README[1] has a video embedded in it. FWIW I'm not convinced it adds anything to the library's sales pitch.
[1] https://github.com/KaliedaRik/Scrawl-canvas
-
Egui commit: Implement accessibility APIs via AccessKit
> And Iām just mentioning some of the unfixable problems with this approach
I agree that using a canvas instead of leveraging existing accessibility supplied by HTML/CSS/JS and the DOM is an accessibility nightmare.
However, I disagree that canvas accessibility issues are "unfixable". Difficult? Yes. But not unfixable. In my view, the element works best in partnership with its wider environment (HTML/CSS/JS and the DOM), not as a replacement for it. With that in mind, we can start to tackle the accessibility issues you raise - fonts, links, interactions, etc.[1][2]
I have an ambition to one day become intelligent enough to understand/code in Rust, and I'm really glad to see that people are thinking about accessibility as a fundamental part of UIs being developed in Rust.
[1] - Which is what my JS 2d canvas library tries to do: https://scrawl-v8.rikweb.org.uk/
[2] - My thoughts on accessibility, and how I try to fix them using my library: https://scrawl-v8.rikweb.org.uk/learn/eleventh-lesson/
-
[AskJS] Why do my coworkers not see the value in frameworks?
If, however, your company is set on this course, I very strongly suggest you use a canvas library - if only for the MVP. Here's my canvas library (spam alert!) ... even if you don't use it in your product, the library might help give you some ideas on how to overcome some of the responsive, interactive and accessibility issues you'll be facing.
-
which technology or framework is used to create geometry-draggable canvas like this?
Scrawl-canvas - example and another example (links to code at bottom of each page)
What are some alternatives?
flowgen - Generate flowtype definition files from TypeScript
tsParticles - tsParticles - Easily create highly customizable JavaScript particles effects, confetti explosions and fireworks animations and use them as animated backgrounds for your website. Ready to use components available for React.js, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, Inferno, Solid, Riot and Web Components.
typegoose - Typegoose - Define Mongoose models using TypeScript classes.
particles-bg - React particles animation background component
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
fabric.js - Javascript Canvas Library, SVG-to-Canvas (& canvas-to-SVG) Parser
node-app-store-connect-api - A library to support Apple's App Store Connect API
Mo.js - The motion graphics toolbelt for the web
hacktoberfest-hunt - Find projects that participate in Hacktoberfest within your starred repositories.
particles.js - A lightweight JavaScript library for creating particles
awesome-typescript - A collection of awesome TypeScript resources for client-side and server-side development. Write your awesome JavaScript in TypeScript
GreenSock-JS - GSAP (GreenSock Animation Platform), a JavaScript animation library for the modern web