-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactoring Widgets names #14
Comments
Yes, text fields certainly should be renamed. If you encounter other unintuitive names, write them here, I'll change some of them. |
Oh ok. Will do that and get back to you |
Here are some names you might consider platform.enterMessageLoop() -> platform.runMessageLoop();
TabWidget -> Tab
EditLine -> TextInput
EditBox -> TextArea
CanvasWidget -> Canvas
ImageWidget -> Image // cus its already under the Widgets module. Those are some few suggestions now. Will add more when I encounter any. As is stands, the api is quite clean, reading from the examples dir. |
Ok, so I've done: platform.enterMessageLoop() -> platform.runEventLoop();
TabWidget -> Tabs
EditLine -> TextField // as in Flutter, MaterialUI, SwiftUI, UIKit, JavaFX...
EditBox -> TextArea
CanvasWidget -> Canvas
|
Great. Thanks. Also wanted to know if the UI is reactive like flutter or react. It didn't seem so just by looking at the code. If not, do you think it'll be an interesting thing to do or you'd recommend a third-party lib like rx-d |
Yes, it is. Old widgets are now called "elements", and new widgets work upon them, somewhat like react components or flutter widgets. I still have to port about half of old widgets onto new system. |
Nice. |
Why is beam ui not in the dub repository already? |
Because I made major API reconstructions in the past and I still need to do some more. Coming soon... |
What do you think remains to be done to have a beta version of some kind out? |
Hi. I was super busy last two months, now a little less busy, slowly working for release. I need to do these things:
|
Glad you're back. |
So upon browsing through the api docs and could find a text input. Its appears its called EditLine by looking through code samples. I remember dlangui had some these weird names but you'd probably agree we now commonly refer to them as TextInput, TextEntry, TextBox, etc in mainstream UI.
Have you thought about changing some of the names to better fit familiar terms?
The text was updated successfully, but these errors were encountered: