mattdesl

71 ms·

1. 721.▲
   JS Workflow: Faster and Cleaner Modules(mattdesl.svbtle.com)

   2 points by mattdesl 12y ago|0 comments
2. 722.▲
   by mattdesl 12y ago

   Nice!
3. 723.▲
   by mattdesl 12y ago

   Wow, looks great. I had a strong feeling that even a "really simple SVG editor" is an incredibly huge task for a single developer. Your app helps put things in perspective. :) I always find "monolithic remakes" to be doo
4. 724.▲
   by mattdesl 12y ago

   How could I find out more?
5. 725.▲
   by mattdesl 12y ago

   Nice! I've also been working on some vector tools in the browser: http://mattdesl.github.io/path-illustrator/demo/advanced.htm... I think dev-centric vector tools present a really good opportunity to improve
6. 726.▲
   Show HN: Path/Curve Editing in the Browser(mattdesl.github.io)

   4 points by mattdesl 12y ago|1 comments
7. 727.▲
   by mattdesl 12y ago

   If you're looking at WebGL, check out StackGL. It's pretty much intended as a low level WebGL wrapper with a modular codebase, and lots of high level modules built on top of it.
8. 728.▲
   by mattdesl 12y ago

   Thanks for testing. Anything in console? What about FireFox?
9. 729.▲
   Show HN: Whistleblower – Whistle-Activated WebAudio Game(mattdesl.github.io)

   14 points by mattdesl 12y ago|7 comments
10. 730.▲
    by mattdesl 12y ago

    Polluting global scope and a hard dependency on jQuery.. :(
11. 731.▲
    by mattdesl 12y ago

    npm init should really use 1.0.0 as default, and I agree 0.x.x should be dropped. It causes a lot of problems since most people publishing packages don't know what 0.x.x means, and they just end up leaving their (stable) modules at 0.0
12. 732.▲
    by mattdesl 12y ago

    I'd love to hear a bit more about how you handle thick lines and anti-aliasing in WebGL. Currently my approach is to make the line a little thicker and then apply the anti-aliasing in the frag shader. Similar to GPU Gems "Fast Pre
13. 733.▲
    by mattdesl 12y ago

    Npm run should work fine on windows. Make is another story.
14. 734.▲
    by mattdesl 12y ago

    Because it's been around for longer; new devs are more likely to be familiar with it, easier to find tutorials/docs on the web, better stability, more tasks to choose from, etc. They are both good though... it won't make a bi
15. 735.▲
    by mattdesl 12y ago

    Sounds like Make. You can also use npm-scripts for basic shell commands. You can rely on NPM-authored tasks and have them listed as a devDependency, so that users don't need to install anything manually. //create a UMD bu
16. 736.▲
    by mattdesl 12y ago

    I'm a big fan of npm and modular code. - npm to manage dependencies and versions - npm-scripts to handle basic build tasks - beefy during module development (when a bundle isn't necessary) - watchify & browseri
17. 737.▲
    by mattdesl 12y ago

    I would say it depends. brfs is perfect since you don't change any node source to support the browser. glslify is another useful one if you're authoring WebGL modules. Not only does it statically analyze the uniforms/attribut
18. 738.▲
    by mattdesl 12y ago

    The issue is twofold: - It shows Node compatibility is not a primary concern of Webpack. - It is not a default feature of Webpack. Pretty much every Webpack project will need to include this loader config if you want to (safely) start consu
19. 739.▲
    by mattdesl 12y ago

    The gist is that Webpack is diverging from Node, has difficulty consuming node/browserify modules, and encourages non-compatible syntax through its require() overloads (which are encouraged all over the docs). Browserify also decouples
20. 740.▲
    Browserify vs. Webpack(mattdesl.svbtle.com)

    22 points by mattdesl 12y ago|10 comments
21. 741.▲
    by mattdesl 12y ago

    Cool hack, but a cleaner solution would be to just use fs.readFileSync if you really want long strings, and let browserify/brfs to inline it for you in the browser. Using this in a library would be pretty unsafe, given how it's br
22. 742.▲
    by mattdesl 12y ago

    Cool, I'll check it out. I don't think it supports anything like that yet. There is some talk about using glslify at runtime, to build "uber shaders" depending on particular needs, and it seems like this kind of feature
23. 743.▲
    by mattdesl 12y ago

    Thanks, fixed.
24. 744.▲
    Writing Modular and Versioned GLSL(mattdesl.svbtle.com)

    28 points by mattdesl 12y ago|4 comments
25. 745.▲
    by mattdesl 12y ago

    We must be doing different things. If I start getting relative paths like that, I usually pull it out into a separate module. I can understand bundling a bunch of modules together for UMD builds, but if you need to bundle all of your NPM&#x
26. 746.▲
    by mattdesl 12y ago

    Why compile the module? Browserify lets you use a module's CommonJS export, so the only build step is at the application level. Utils etc should not be built except for non-node users (umd).
27. 747.▲
    by mattdesl 12y ago

    I use beefy for almost all my modules, demos, and protoypes. For websites, I usually go with gulp watch since I need LESS anyways.
28. 748.▲
    by mattdesl 13y ago

    Nice! Does Canvas+ support WebGL? What about video and device camera processing, i.e. through a custom shader?
29. 749.▲
    by mattdesl 13y ago

    Thanks for the tips. I'm new here; would it be a faux-pas to re-post the app URL with the same "Show HN" title?
30. 750.▲
    Show HN: Interactive and Generative Impressionist Paintings

    4 points by mattdesl 13y ago|3 comments