search

square / mortar

A simple library that makes it easy to pair thin views with dedicated controllers, isolated from most of the vagaries of the Activity life cycle.
Apache License 2.0
2.16k stars 156 forks source link

BluePrint should not be public API #104

Closed rjrjr closed 9 years ago

rjrjr commented 9 years ago

Especially after the introduction of @WithModule

cpetosky commented 9 years ago

I see ebc7707669c36740fc17f887f4eaa2e8001e39ca removed Blueprint generally, but the README still refers to things in terms of Blueprint.

Is there a timeline for updated best practices with Mortar? I'm interested in porting an existing app to it.

(Sorry if this is the wrong forum to ask this -- didn't see a mailing list or similar.)

rjrjr commented 9 years ago

We're trying to get the momentum back up — we need it too, especially as Dagger 2 approaches and Google starts to improve testing.

Anyway, don't want to make promises I won't keep, but I'm hoping you'll see a steady trickle of work over the next few weeks. In the meantime, our shipping apps are based on the versions currently in Maven central, which have been stable for a while. FWIW.

On Fri, Jan 16, 2015, 3:17 PM Cory Petosky notifications@github.com wrote:

I see ebc7707 https://github.com/square/mortar/commit/ebc7707669c36740fc17f887f4eaa2e8001e39ca removed Blueprint generally, but the README still refers to things in terms of Blueprint.

Is there a timeline for updated best practices with Mortar? I'm interested in porting an existing app to it.

(Sorry if this is the wrong forum to ask this -- didn't see a mailing list or similar.)

— Reply to this email directly or view it on GitHub https://github.com/square/mortar/issues/104#issuecomment-70338353.

pyricau commented 9 years ago

@rjrjr we should close this issue, right? BluePrint being dead, it's definitely not a public API.

@cpetosky yep we need to update the readme.