-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development status #405
Comments
I have this project aimed to be restarted next year by me. My ideas are:
Any other idea is welcome. |
Right now the project is stalled, however, I wouldn't discard the option to restart the development if enough users are interested in using it, and more importantly, contributing again. @X3MBoy are you sure gtk3 gives you enough flexibility to show all the UI controls Turpial needs? In fact, I moved to Qt because of the great support for HTML and the flexibility of the toolkit. On the other hand, the CLI interface would be a huge win. I had it in my to-do list years ago but never finished it. My recommendation before start coding is to check libturpial and fix any issue it could have. |
@satanas I'm not sure if GTK3 offers all the things I need, but it's in the wish list, because some people don't like/want to mix libraries ( I don't get how people still think this way, but they do :D ). Also, I know that to move all the code, I need to start with libturpial and I already forked it. I hope to start working with this code in 01-2018, and I hope I can come with something clean at that time and I'm counting with you if I get stucked :D |
@X3MBoy Of course! Just let me know if you need anything |
Hi @satanas, |
Thanks so much @satanas for restarting development. It's just with Twitter shutting down 3rd party clients later this year it might be worth looking at supporting other services. |
@X3MBoy Any news? |
Is Turpial still maintained? I know it is probably not but given enough user response maybe there is a chance to revive this project. Please let me know what your current ideas are and whether you would still consider development.
The text was updated successfully, but these errors were encountered: