Rewriting Gemview's Gemtext Parser Part 2

In my last [post](../rewriting-gemtext-parser) I described the reasons behind and implementation of the new Gemtext parser for GemView. In the summary, I pointed out a few areas of "low hanging fruit" which might make for some nice improvements over both the old parser and the new in it's then state.

Rewriting Gemview's Gemtext Parser

When I first began the GemView project, I had chosen to use an external crate to handle most gemini related tasks, such as connecting to the server, retreiving documents, and parsing gemtext. GemView would only really have to handle rendering the parsed GemText. Or so I thought.

April Update

I've been quite busy code wise lately but haven't made time to post anything. Almost all of the recent work has been on Rust projects, and while I haven't abandoned Zterm, I'm becoming more and more drawn to the Rust ecosystem. It's just that good.

Handling Unsupported Protocols in Gemview

[GemView](https://codeberg.org/jeang3nie/gemview) is meant to be a generic and reusable Gemini browser widget, while [Eva](https://codeberg.org/jeang3nie/eva) is the browser built to leverage it. GemView can already handle surfing around geminispace using the gemini protocol, but you never really know what types of links are going to be found in Geminispace.

April Update

There's been a slow but steady march of progress on these two projects over the past week, and I think it's now at the point where I could say that Eva is, while still a wip, somewhat useful.

Gemini Browser Widget

The [gemini](https://gemini.circumlunar.space) protocol is a simple, text oriented internet communication protocol. I don't want to go into too much detail about what Gemini is, I'll leave that to the reader to research if interested. This post is about a new project to create a freestanding gemini browser widget for gtk4, much like webkit2gtk is for the web, and a simple, nice browser which leverages it.