Damien
Damien
As `Settings.Secure` values could be of multiple types, we should handle this the same way [we handle SharedPreferences](https://github.com/excilys/androidannotations/wiki/SharedPreferencesHelpers) : `@SecureString`, `@SecureInt`, `@SecureFloat`, and `@SecureLong` ``` java @EBean public class MyBean...
I'm just afraid that `@SecureXXX` annotations are misinterpreted.
I think you're thinking about `@Rest` annotation :) But I agree, we're strongly linked to Spring mobile library. I don't know how we could allow the use of other libraries,...
It should be a good idea. The document says this about retaining instance : > onDestroy() will not be called (but onDetach() still will be, because the fragment is being...
> BTW I have to say, I don't think this is a good practice at all, it just useful on some small apps that don't use alternative resources (i18n, orientation,...
The main problem here is how to stop this. So, I think we should do another annotation for this feature, like `@Timer(delay = 1000)` on a method which MUST return...
I'm not sure... I think a different annotation is a better idea for two reasons : - It will be easier to use the provided Timer class to handle this...
It doesn't cost much and I think it should be helpful to many. I'm ok with this feature
I made this library a long time ago.. I definitely have to work again on this one :) But I think you're right we should add OnScroll support