We've mentioned moving from the factory/producer/headache pattern that we currently use (Pipeline, etc) to something more fluent and more maintainable. See this JIRA : https://issues.jboss.org/browse/AGDROID-259 To that end I've stubbed out some classes and made a strawman set of unit tests for Pipeline : https://gist.github.com/secondsun/8478a5f0527fc97b2456 In the comments of some of the tests I've added questions for the implementation portion of Registrations. The ultimate goal is to make the factories and feature classes(Pipe, AuthModule, etc) flexible enough that circular dependencies can be broken and 1) modularization can happen and 2) feature additions can be quicker and change fewer stable APIs. Comments, questions, and tomatoes are welcome. -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On 07/17/2014 09:00 AM, Bruno Oliveira wrote: > Good morning Summers, make sure to assign that Jira for you, please. The > gist for an Android outsider like me seems ok, but I would like to see > these changes in at your fork for more context. > > Do you have any pointers? No it is written in Java. Right now I am more interested in discussion around the direction of the changes (in the TODO comments) before I spend a few weeks of time and get a HUGE PR build up. As such all the implementation is "throw new NotImplementedException()". But, since it seems like it will help, I will grab the JIRA ball and link to the gist as well as my current working repo. > > On 2014-07-16, Summers Pittman wrote: >> We've mentioned moving from the factory/producer/headache pattern that >> we currently use (Pipeline, etc) to something more fluent and more >> maintainable. See this JIRA : https://issues.jboss.org/browse/AGDROID-259 >> >> To that end I've stubbed out some classes and made a strawman set of >> unit tests for Pipeline : >> https://gist.github.com/secondsun/8478a5f0527fc97b2456 >> >> In the comments of some of the tests I've added questions for the >> implementation portion of Registrations. >> >> The ultimate goal is to make the factories and feature classes(Pipe, >> AuthModule, etc) flexible enough that circular dependencies can be >> broken and 1) modularization can happen and 2) feature additions can be >> quicker and change fewer stable APIs. >> >> Comments, questions, and tomatoes are welcome. >> >> -- >> Summers Pittman >>>> Phone:404 941 4698 >>>> Java is my crack. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- > > abstractj > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Summers Pittman >>Phone:404 941 4698 >>Java is my crack. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev