Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MSPaint in JavaScript

jspaint.app

Post reply on HN
Print view View original

61–70 of 129 posts

Re: MSPaint in JavaScript

#61

Post by tomcam »

tomtheelder wrote: post #54
AdmiralAsshat wrote: post #30

This is totally something that I could live with being an Electron app on Linux. Yes, I should be using GIMP/Krita/Other community FOSS solution, but gosh darnit, sometimes I just wanna make a 20-second markup on a screenshot, and I wanna use the friggin' program that I have a 20-year muscle memory for!

This app has really noticeable and irritating latency vs. native paint that would make it a pain for me to actually use. If we are being honest that's probably an implementation thing, and not just a function of it being JS, but once gain performance problems in a JS app damage the experience for me.

Not on my $300 iPad

Re: MSPaint in JavaScript

#62

Post by yoavm »

what strikes me the most is that the "modern" theme (from the "extras" menu) feels so much less user friendly than the "classic" one. where did it all go wrong?..

Re: MSPaint in JavaScript

#63

Post by ftio »

rubyn00bie wrote: post #57
aikah wrote: post #55

Earlier quoted context omitted.

Nice. Although one of the hidden power of Photoshop is the ability to open ridiculous large image files without any hurdle whatsoever. The other day a client sent a 5GB comp we had to open to modify some text, I was surprised how well Photoshop handled it, on a relatively cheap laptop. Not sure how it would fair in the browser.

If you don't mind me asking, what's some like meta data you could share on what makes for a 5GB photoshop file? I'm just really curious at how a single photoshop file gets that large. Does it contain a bunch of workflows and auxiliary assets or something?

I’m sure there are many ways, but I’ve done it by stitching together dozens of photos to create a panorama.

Re: MSPaint in JavaScript

#64

Post by therein »

rubyn00bie wrote: post #57
aikah wrote: post #55

Earlier quoted context omitted.

Nice. Although one of the hidden power of Photoshop is the ability to open ridiculous large image files without any hurdle whatsoever. The other day a client sent a 5GB comp we had to open to modify some text, I was surprised how well Photoshop handled it, on a relatively cheap laptop. Not sure how it would fair in the browser.

If you don't mind me asking, what's some like meta data you could share on what makes for a 5GB photoshop file? I'm just really curious at how a single photoshop file gets that large. Does it contain a bunch of workflows and auxiliary assets or something?

It could be a really large render of a `dot` graph. That's the only kind of 5GB PNGs I've had to work with.

While on that topic, anyone have any good ideas in situations like that? Rendering a really large SVG from scratch is not feasible, also most SVG renderers actually fail on really large SVGs in my experience. I've always had to export as PS or just direct render into PNG.

Re: MSPaint in JavaScript

#65

Post by rubyn00bie »

ftio wrote: post #63
rubyn00bie wrote: post #57

Earlier quoted context omitted.

If you don't mind me asking, what's some like meta data you could share on what makes for a 5GB photoshop file? I'm just really curious at how a single photoshop file gets that large. Does it contain a bunch of workflows and auxiliary assets or something?

I’m sure there are many ways, but I’ve done it by stitching together dozens of photos to create a panorama.

That makes sense I need to go look up how big photo files are now I guess.. It has been many years since I used photoshop for editing photos (or at all I suppose); my last camera (excluding my phone) was a Nikon D70 (only 6 megapixels).

Re: MSPaint in JavaScript

#67

Post by themodelplumber »

Nux wrote: post #36
dansman805 wrote: post #33

Earlier quoted context omitted.

Specifically for screenshot markup, I recommend using flameshot ( https://flameshot.js.org/#/ ). It allows you to markup the screenshot right as you take it.

Flameshot is sluggish and bloated. If you want the same functionality and more, but fast, try Shutter.

Shutter is fast now? Awesome. I remember when I had to stop using it for a while because it was somehow really unresponsive.

Re: MSPaint in JavaScript

#68

Post by Nux »

ForHackernews wrote: post #43
Nux wrote: post #36

Earlier quoted context omitted.

Flameshot is sluggish and bloated. If you want the same functionality and more, but fast, try Shutter.

Do either of those work under Wayland? Or only X11?

Not sure tbh. I use it with latest Fedora+MATE at work.

Re: MSPaint in JavaScript

#69

Post by bjornsteffanson »

AdmiralAsshat wrote: post #30

This is totally something that I could live with being an Electron app on Linux. Yes, I should be using GIMP/Krita/Other community FOSS solution, but gosh darnit, sometimes I just wanna make a 20-second markup on a screenshot, and I wanna use the friggin' program that I have a 20-year muscle memory for!

Shortcut to the Electron app: https://github.com/1j01/jspaint#desktop-app-electron

Re: MSPaint in JavaScript

#70

Post by gfosco »

rubyn00bie wrote: post #57
aikah wrote: post #55

Earlier quoted context omitted.

Nice. Although one of the hidden power of Photoshop is the ability to open ridiculous large image files without any hurdle whatsoever. The other day a client sent a 5GB comp we had to open to modify some text, I was surprised how well Photoshop handled it, on a relatively cheap laptop. Not sure how it would fair in the browser.

If you don't mind me asking, what's some like meta data you could share on what makes for a 5GB photoshop file? I'm just really curious at how a single photoshop file gets that large. Does it contain a bunch of workflows and auxiliary assets or something?

My wife creates prints for our fabric printer, and the PSD files are often larger than 2GB, containing for example a 55" wide image that is 6+ yards long, at 150-300 dpi with a bunch of layers. Somehow her low-specced 2015 Macbook Pro 13" has handled this type of work just fine, as long as there's enough free space for the scratch disk.
Post reply on HN