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

Rx v0.3 Released, a modern and minimalist pixel editor in Rust

rx.cloudhead.io

Post reply on HN
Print view View original

11–20 of 69 posts

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#11

Post by cloudhead »

billfruit wrote: post #8

Does it support an isometric grid? What about drawing shapes like circles, rectangles? Also curious on what toolkit/library was used for building the UI using rust.

It doesn't, but that would be an interesting feature to develop. Is this something you've used in another editor (iso grid)?

Rust doesn't really have anything super mature in terms of UI, though druid[0] is the one I'm keeping an eye on. Since there's very little "UI" per se in rx, it's currently built directly on top of the graphics layer[1].

[0]: https://github.com/xi-editor/druid

[1]: https://github.com/cloudhead/rgx

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#12

Post by fnord123 »

tomashubelbauer wrote: post #5
kerkeslager wrote: post #2

Gah, please type the names of your projects into the search engine of your choice before polluting everyone's search results with a new project. There are already a few programming projects which go by "rx". I'll boost the one I care about by linking it: http://reactivex.io/

There's a very little overlap between the purpose and use case of the two projects. There's not that many good, short names. I personally wouldn't worry about naming conflicts with another project, unless it was a similar project in more than a name.

https://github.com/rxRust/rxRust

Many Rust projects are blah-rs where the rs is dropped in the crate name. So it would be normal to be confused and think Rx == RxRust. e.g. https://github.com/rust-lang/futures-rs has crate name "futures".

>There's not that many good, short names.

There'd be loads if the Rust community (or.. the 'rust parliamentary community' (people who actually get involved in the RFC processes and see things through to the end (heroes, imo)) (cf PLP[0])) elected to use namespaces for crates.

[0] https://en.wikipedia.org/wiki/Parliamentary_Labour_Party

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#13

Post by billfruit »

cloudhead wrote: post #11
billfruit wrote: post #8

Does it support an isometric grid? What about drawing shapes like circles, rectangles? Also curious on what toolkit/library was used for building the UI using rust.

It doesn't, but that would be an interesting feature to develop. Is this something you've used in another editor (iso grid)? Rust doesn't really have anything super mature in terms of UI, though druid[0] is the one I'm keeping an eye on. Since there's very little "UI" per se in rx, it's currently built directly on top of the graphics layer[1]. [0]: https://github.com/xi-editor/druid [1]: https://github.com/cloudhead/…

I think marmoset hexels[0] has an isometric grid, haven't used it myself. I have used the iso(axonometric) grid in Inkscape.

[0]:https://marmoset.co/hexels/

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#14

Post by thesuperbigfrog »

kerkeslager wrote: post #2

Gah, please type the names of your projects into the search engine of your choice before polluting everyone's search results with a new project. There are already a few programming projects which go by "rx". I'll boost the one I care about by linking it: http://reactivex.io/

"Rx" already has a history of use as medical shorthand for "prescription". See https://en.wikipedia.org/wiki/Medical_prescription

I would also recommend choosing a less overloaded name. Searching for "rx" in Google brings up prescription-related results.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#15

Post by tomashubelbauer »

fnord123 wrote: post #12
tomashubelbauer wrote: post #5

Earlier quoted context omitted.

There's a very little overlap between the purpose and use case of the two projects. There's not that many good, short names. I personally wouldn't worry about naming conflicts with another project, unless it was a similar project in more than a name.

https://github.com/rxRust/rxRust Many Rust projects are blah-rs where the rs is dropped in the crate name. So it would be normal to be confused and think Rx == RxRust. e.g. https://github.com/rust-lang/futures-rs has crate name "futures". >There's not that many good, short names. There'd be loads if the Rust community (or.. the 'rust parliamentary community' (people who actually get involved in the RFC processes and…

Namespaces are a good idea on paper, but you still need to secure the non namespaced name when you reach a bit of popularity or someone else will who will push malware there knowing people will often add a crate by the name they think it has and not necessarily the one it has.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#16

Post by jcelerier »

cloudhead wrote: post #9
marmaduke wrote: post #7

Is such a recent graphics API really necessary? Why isn't a 2D canvas good enough in for this sort of thing?

It's not strictly necessary, I chose wgpu for a few reasons: * Its backend (gfx-rs) is one of the most mature rust libraries for doing graphics * The popular "classic" 2d libraries like cairo and skia are very big and complicated to build / depend on * wgpu will eventually also work on the web, so it's a great option for broad platform compatibility * In terms of efficiency (memory, battery, cpu etc.), the modern gra…

> * Today, 4K screens are pretty common, and in the future, 144hz monitors will be more and more popular. If I want to render 2d graphics with no latency in those setups, access to the GPU makes things feasible

are those not feasible today ? due to vsync & al I still have less latency on apps that do software rendering than hardware, even on a 4K 120hz screen

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#17

Post by cloudhead »

jcelerier wrote: post #16
cloudhead wrote: post #9

Earlier quoted context omitted.

It's not strictly necessary, I chose wgpu for a few reasons: * Its backend (gfx-rs) is one of the most mature rust libraries for doing graphics * The popular "classic" 2d libraries like cairo and skia are very big and complicated to build / depend on * wgpu will eventually also work on the web, so it's a great option for broad platform compatibility * In terms of efficiency (memory, battery, cpu etc.), the modern gra…

> * Today, 4K screens are pretty common, and in the future, 144hz monitors will be more and more popular. If I want to render 2d graphics with no latency in those setups, access to the GPU makes things feasible are those not feasible today ? due to vsync & al I still have less latency on apps that do software rendering than hardware, even on a 4K 120hz screen

Interesting. Yeah, vsync is a latency killer and it's disabled by default in `rx`. What software renderers are not so good at is drawing lots of pixels every frame, so for example panning a view with lots of images open, or zooming in and out of an image that covers the screen.

I'd expect these kinds of operations to be slow at high resolution without the help of the GPU. You could probably speed things up with SIMD and multi-threading, at the expense of implementation complexity.

Re: Rx v0.3 Released, a modern and minimalist pixel editor in Rust

#20

Post by jacobolus »

newnewpdro wrote: post #18

Vulkan support required for a pixel editor? So I can't run this on my X220 despite having a dual-core 2.8Ghz i7 processor, since its integrated GPU is a generation just shy of having Vulkan support. A pixel editor .

It’s one person’s volunteer hobby project, and you’re sarcastically complaining about it using modern hardware features.

It’s free software. Go fork it and code up a variant for legacy hardware yourself.

Post reply on HN