3 ms·
The long loading time might be unoptimized-yet parsing of various XML files of ones app. In general, it's mostly an evolutionary work on existing IntelliJ Andro
by p_l 14y ago
The long loading time might be unoptimized-yet parsing of various XML files of ones app. In general, it's mostly an evolutionary work on existing IntelliJ Android plugin.
The View editor afaik has some support for custom views, but only some - it's rather iffy (IntelliJ Android view renderer simply used Android libs to render them, but of course that doesn't work for everything, and anything fully programmatic is dead anyway). Fwiw, IntelliJ's XML editor was always much better at not freaking out at the fact that you haven't finished writing that new tag so of course your view doesn't validate (something that was a constant for me back when I used Eclipse).
The editors in general are standard for IntelliJ, with some nifty transformations added - the XML string example reminds me of how IntelliJ dynamically renders certain idioms into Java 8 forms while still keeping the code in 1.6 (well, that's how I have it configured, that is).
In general, it's nice, I hope it will be available as plugin into plain old IntelliJ as well.
- njs12345 14y agoIn Eclipse you can use View.isInEditMode to hide code that doesn't work in the preview. Bit of extra work but probably worth it, having your custom views work in the layout editor can be a timesaver. I'd imagine that works in Android Studio too.