Skip to content
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

Open
aberba opened this issue Jun 23, 2020 · 12 comments
Open

Refactoring Widgets names #14

aberba opened this issue Jun 23, 2020 · 12 comments

Comments

@aberba
Copy link

aberba commented Jun 23, 2020

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?

@dayllenger
Copy link
Owner

Yes, text fields certainly should be renamed. If you encounter other unintuitive names, write them here, I'll change some of them.

@aberba
Copy link
Author

aberba commented Jun 23, 2020

Oh ok. Will do that and get back to you

@aberba
Copy link
Author

aberba commented Jun 23, 2020

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.

@dayllenger
Copy link
Owner

Ok, so I've done:

platform.enterMessageLoop() -> platform.runEventLoop();

TabWidget -> Tabs
EditLine -> TextField   // as in Flutter, MaterialUI, SwiftUI, UIKit, JavaFX...
EditBox -> TextArea
CanvasWidget -> Canvas

Image is a reserved name for lower-level API for now. I haven't decided yet where I will use it.

@aberba
Copy link
Author

aberba commented Jun 27, 2020

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

@dayllenger
Copy link
Owner

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.

@aberba
Copy link
Author

aberba commented Jun 28, 2020

Nice.

@aberba
Copy link
Author

aberba commented Jul 10, 2020

Why is beam ui not in the dub repository already?

@dayllenger
Copy link
Owner

Because I made major API reconstructions in the past and I still need to do some more. Coming soon...

@aberba
Copy link
Author

aberba commented Sep 30, 2020

What do you think remains to be done to have a beta version of some kind out?

@dayllenger
Copy link
Owner

Hi. I was super busy last two months, now a little less busy, slowly working for release.

I need to do these things:

  • popups and dialogs - they don't really work right now
  • virtualized lists/grids - like in react-window, but maybe even simpler
  • CSS font selection algorithm and @font-face - critical for CJK, emoji, icon fonts, any fancy characters
  • some very simple UI inspector
  • media queries
  • and some means to render UI to a texture

@aberba
Copy link
Author

aberba commented Oct 19, 2020

Glad you're back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants