> > Looks good to me (not many practical changes ;)) However, who cares about > all the tweaks, imho macroid's strength is that you can create your own > tweak library perfectly suited to your needs. > You can probably think of macroid.contrib as a tweak library perfectly suited to my needs :)
Sure you need a few examples to get people started, but after that i think > most people will start to create their own tweaks. So personally, i'd not > bother to expand the contrib tweak package too much ;) > > I think macroid's strength is making 'advanced' things easy, like the > RuleRelativeLayout to ease building layouts, ui-event handling, or the > straightening of the threading mess with ui threads, and of course, > tweaks/snails combinations to reactively update layouts/views. But all > that's already there ;) > > What i've stumbled on: Binding services (i ended up with something close > to scaloid's service binder (without scaloid's lifecycle management > https://github.com/pocorall/scaloid/#lifecycle-management)), creating > custom views (not sure there's a smart way to make this easier, if there > is, i haven't found it), custom fragment transitions (also a really minor > thing). > I think creating custom views is outside of scope — Macroid is more about combining existing ones. Besides, the respective Android API is rather rigid, so I don’t see much space for improvement there. Fragment transitions and navigating between activities definitely both deserve their own DSLs, and I’m going to work on that. But these DSLs can hopefully be added on top in a non-breaking manner. I currently haven’t put much thought into service binding, maybe you could elaborate on the problems and share your solution? Nick -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
