Closed satanas closed 10 years ago
Yep, totally agree but I don't have in mind to release another libturpial version until the release of Turpial 3, so what I'm doing is to "hack" this things on Turpial code, label them with a comment like below and registering the issue in libturpial's repo:
#FIXME: This should be implemented on libturpial
or
#HACK: Implement this on libturpial
What do you think?
I guess it's because you want to work on Turpial only. However there we should keep this in mind as this will ease everything.
Yep, of course. After Turpial 3 release (while the people is still enjoy the new version) I will be working on a new release of libturpial with all this fixes and this will drive us directly into a new turpial release too (somekind of maintenance release). That's the plan
Done
I believe this could be handled by libturpial, probably in the accountmanager level. We could have a way to track the status of an account (disconnected, authed, etc) and show information in the UI properly according to this.