I released the first alpha version today. Getting a lot of positive feedback on Reddit.
Still a long way to go though :3
We could make a template repository for it, as renderers are mostly meant to live in its own crate.
Yes.
iced could entirely be an implementation detail of your UI toolkit, like coffee does. But if you are building a renderer for the built-in widgets, then iced_three makes sense. We may end up splitting the built-in widgets into their own crate too. Still unsure about this. Many things to learn from use cases.
Also, I imagine renderer crates could provide an API to render your own custom widgets efficiently. That would be great too.
Exciting.
@krankur Depends on the complexity of the project.
Iced is renderer-agnostic. This means the library won't do any drawing for you at all. Therefore, in order to use it you need a renderer implementation. There is not a general purpose renderer for Iced yet (the library was just released!). Building such a renderer is the next milestone.
Because of this, Iced is not ready yet for anything too complicated. Currently, it is best suited for simple use cases where building your own simple renderer is feasible, like game menus, dev tools, simple apps, etc. I wouldn't recommend it for a somewhat complex GUI yet. That said, any efforts in this direction would be very welcome to improve the library.
And there are no stupid questions, feel free to ask anything here!
I am working on something that needs text input at specific positions. Normally I would use a textbox or something similar for this. But with your work a label would be sufficient. But I couldn't figure out, if there is something like focus for the widgets.
Hey, @Maikel1963. The character limit in the
input example is defined here: https://github.com/hecrj/coffee/blob/master/examples/input.rs#L95
Thanks for the kind words!
What do you mean by focus? There is indeed no text input widget yet, but we should be able to reuse the widgets found in
iced eventually (https://github.com/hecrj/iced).
"focus" in the context I am thinking of is to ignore all character input as long as there is no textbox selected which is meant to accept input via keyboard (has focus). But it is not very complicated to create a struct which handles just this. Only that I didn't want to invent it anew if it alredy exists.
@Maikel1963 Feel free to join the Iced Zulip and ask any questions there: https://iced.zulipchat.com/
me and my girl are trying to make a text adventure game with coffee and it's a pretty fun endeavor, haha :D
the code is here, but there's not much visually and gameplay-wise going on yet: https://git.sr.ht/~magnusi/heaven-underground
i tried some fun stuff, like declarative generics-based input processing (https://git.sr.ht/~magnusi/heaven-underground/tree/master/src/input.rs#L107) but i'm not experienced with gamedev at all :sweat_smile:
anyways, I got a few questions/concerns
\1. when I build for Windows (I'm a Linux guy mostly), fonts don't work in Vulkan. Am I doing something wrong and that shouldn't happen or is that a bug? I haven't seen it mentioned anywhere else :sweat_smile:
\2. how would one go about implementing something such as video playback? Like pre-recorded a cutscene? Is that even possible? This might not be related to coffee, I think, I don't know much about gamedev
\4. this is just me being curious: do I understand it correctly that OpenGL is locked to 60fps and Vulkan is unlocked? I'm developing on a pretty old and weak thinkpad, so the 60fps might just be a coincidence :sweat_smile:
@luciusmagn 1. This may be that your Windows graphics drivers are different or do not support Vulkan that well. Try updating them, if you haven't yet.
\2. I'm honestly not completely sure. I imagine you'd need to decompress the video and stream that data to the GPU to finally display the result as a texture. It's easier said than done! :sweat_smile:
\3. I'd try
rodio or cpal. I know some folks have used it with coffee. We should eventually offer built-in audio support.
\4. They should both enable Vsync. This may be related to the driver differences I mentioned in \1.
in coffee?