Repository navigation
my opinions and considerations about teamtalk android project and my development to it #3273
amirmahdifard
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
@bear101 hi. As you know, i'm a contributor of teamtalk android. But before I continue my strong development to teamtalk android? I have a question from you.
as you know, recently, @beqabeqa473 has redesighned the server entry activity. In this redesighn, he did 2 things, I agree so much with one of them and disagree with the other one.
1: he used RecyclerView instead of list view for server list, which i strongly agree, and i'll rewrite all other list views to RecyclerViews because RecyclerView is faster, stronger, etc.
2: for server entry controles, he used view binding instead of find view by id, whitch i disagree. I know view binding is new etc, but view binding generates all xml code on compile time to classes, it uses more memory, it needs to be enabled in build.gradle by setting viewbinding to true.
as I know your opinion, you like the teamtalk application to be as simple as possible, and you like teamtalk's simplysity, I like teamtalk for the same reason.
the reason I started to contribute to teamtalk android, is because I wanted to add features and fix bugs to teamtalk android, while keeping it simple, minimal and compatible. Applications like instagram etc... are using view binding but for teamtalk that I like to work on it if its simple as before, view binding is not needed for teamtalk on my opinion. find view by id keeps it simple, keeps the code the way that I enjoy working with it, doesn't generate classes of xmls up on compile time, more importantly, for an application like teamtalk that is small, find view by id is faster, and uses less memory. and it's compatible with even older androids and devices.
onistly, the reason why I love working on teamtalk android, is because it's simple, and the dialogs are small and nice, and I've partly redesighned some parts, and i'll work on it more when my internet unblocks in iran.
so, hear, the question is, do you agree with me? can I rewrite server entry activity to use find view by id instead of view binding again? I know you like teamtalk's simplysity like me, so that's why I asked you this.
before at some point, some people like @beqabeqa473 suggested some advance features for teamtalk server but you disagreed because it would make teamtalk not simple any more. Such as public/private channels, invitations for channel joins, etc. But those features will only make the teamtalk complicated. Teamtalk is now simple. So what do you think on my question? i'll respect whatever you say. I want to know this before I resume my development to teamtalk android again. Thanks!
Application
All reactions