Re:Why don’t designers take Android seriously?
by baddox on Monday March 24, 2014 @03:32AM
(#7457138)
I've been there. I even started one small isolated project with the experimental idea to completely forego the XML layouts and just build the entire thing in Java.
Embarrassingly, it actually worked out okay. The thing is, with XML layouts, eventually the functionality requirements force you to pull in nearly all the views in Java and set styles and behavior programmatically. It's not exactly pleasant to do everything in Java (especially things like RelativeLayout.LayoutParams), but you're going to have to do it anyway, so the only thing the XML layouts really save you is setting up the view hierarchy. Perhaps if I worked with a designer who created the XML layouts and styles, this wouldn't be the case, but the Android tools for designers seem laughably bad.
Re:Why don’t designers take Android seriously?
by chroem on Monday March 24, 2014 @01:04AM
(#7456811)
Really? I picked up CSS in a few hours but I still can't begin to wrap my head around how to properly work with Android layouts.
I really wish Google would let people use HTML and CSS instead of that bizarre relational XML stuff.
Re:Why don’t designers take Android seriously?
by bluefinity on Monday March 24, 2014 @04:49AM
(#7457270)
PhoneGap is exactly that, with the bonus that's it's also cross platform.
Sadly the whole way the layout system works seeps into the programmatic APIs in all sorts of bad ways too -- like, I just want to set the width of this view... there's no setWidth, wtf? Oh... LayoutParams? What in the hell is all this. Not to mention things like every layout type having its own LayoutParams class and all the fun that comes along with changing say a RelativeLayout to a LinearLayout and then having to both change all your different dpi xml files to match (especially on tablet/phone hybrid apps), and also make a ton of code changes to correct your Java casting, etc. bleh.