[DevLog # Gmail-TUI: Replicating Gmail-Webs Navigation
Thanks to all the kind support on the previous DevLog, I am back with the latest update on my Gmail-TUI application! If you are not aware of this OpenSource project, I am developing a Terminal-based UI application that aims to replicate the Gmail-Web experience in the terminal, without the need for a Web-Browser:
Read DevLog #01 | Contribute to the Project's GitHub Repository
Replicating Gmail-Web's Navigation
While the implementation of the Inbox feature is still a work in progress, I have implemented a better navigation system within the Gmail-TUI than its previous version, as can be seen above.
In the earlier version, the user would be directly prompted to compose a mail and send it, since that was the only feature available at that time. After the recent modifications, however, a basic blueprint has been laid for how a user will be able to navigate within this application:
- The Login Screen is now shown as the main page.
- After a successful login, the Dashboard is displayed with possible options for Composing Mails (Implemented) and Viewing Inbox, Starred, and Draft mails (WIP).
- Upon selecting the desired option, the user is led to a new page for performing option-related operations.
- Exit & Back options have been provided on appropriate pages for a better user experience.
A successful login is currently being validated by sending a 'Login-alert' mail to the person trying to log in. If the email-password does not match, then the 'Login-alert' mail will not be sent to the user and they will be prompted to retry again.
As of now, only the Compose options is functional but after the implementation of the IMAP-Protocol, the remaining options will be modified to perform related operations.
Plans For Now
Okay, so to recap, since the first DevLog, the following functionalities have now been added to Gmail-TUI:
- ✅ A login page for entering email ID and password
- ✅ Composing and sending mails
- [WIP] Listing received emails with email IDs in the Inbox
- [WIP] Opening the content of the received mail after clicking it
- [WIP] Viewing sent emails in the Sent-Box
- ✅ Area to choose from the Compose, Inbox, Drafts, Sent buttons
Since networking has never really been my strongest point, I have been working on better understanding the IMAP Protocol that is to be used to display emails in User’s inbox. Sadly for me, I have been struggling with properly grasping the related concepts. Or rather, I feel like I am unnecessarily prolonging the implementation of the Inbox feature by wanting to learn more and more about IMAP because of just how fascinating it really is!
I understand how it’s to be implemented in the code now but there's a part of me that wishes I wouldn’t move on until I understand everything about IMAP - which I realise is pretty impractical.
Therefore, I have made up my mind: I will be implementing the inbox feature using whatever knowledge I have gained so far and ensuring that this feature is present in the next version of Gmail-TUI. I mean, what is the point of trying to capture so much knowledge without even trying to implement it somewhere... Right?
If you liked reading this DevLog and would like to have a closer look at my development process, please consider following me on X, Reddit, and GitHub!
The above is the detailed content of [DevLog # Gmail-TUI: Replicating Gmail-Webs Navigation. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg
