4 ms·
Looks like the android studio setup is better than the old eclipse one. I'd love to be able to double click a control there and have a default event handler app
by g_p 6y ago
Looks like the android studio setup is better than the old eclipse one. I'd love to be able to double click a control there and have a default event handler appear in my code, ready for me to add event logic.
This does look pretty nice however, though I imagine it's a one way sync, so only visualising the UI from the XML file, rather than letting you visualise and tweak your UI after seeing it populated with content that gets loaded in by Java code? I guess as everything has evolved, the amount of the actual layout contained in the XML is reducing over time.
Maybe this is where the more declarative approaches will make it easier to reconcile the layout and the content-filled layout.
- Izkata 6y ago> though I imagine it's a one way sync, so only visualising the UI from the XML file, rather than letting you visualise and tweak your UI after seeing it populated with content that gets loaded in by Java code? Yeah, though you can (for example) put default text in that then gets replaced by the Java code before anyone sees it. I don't think it's very thorough for the other widget types, though. > I guess as everything has evolved, the amount of the actual layout contained in the XML is reducing over time. This is still all XML, it's just auto-generated for you through the GUI editor.
- g_p 6y agoThanks - I think I perhaps didn't explain what I was "asking for" that well - what I meant was akin to what Jetpack Compose looks to do for Android (thanks to another commenter for pointing it out!) with the "@Preview" notation to create some "real example" UIs that can contain real exemplar content.