regexbook's profile picture. RegEx Book application for #macOS - made by @robertvojta

RegEx Book app

@regexbook

RegEx Book application for #macOS - made by @robertvojta

Do you wonder how hard is to manage a side project? How much work is it? Here's what's missing (+ small amount of TODOs in the code).

regexbook's tweet image. Do you wonder how hard is to manage a side project? How much work is it? Here's what's missing (+ small amount of TODOs in the code).
regexbook's tweet image. Do you wonder how hard is to manage a side project? How much work is it? Here's what's missing (+ small amount of TODOs in the code).

Edge cases handled as well 😉

regexbook's tweet image. Edge cases handled as well 😉
regexbook's tweet image. Edge cases handled as well 😉

Improved error messages.

regexbook's tweet image. Improved error messages.

New feature - document based regular expressions (save them for later use/inspection) with proper undo & redo. Yeah, even these check boxes are part of the undo & redo. They're part of the regular expression.


UI experiment no. 2 - AST moved down, navigation sidebar trashed, ...

regexbook's tweet image. UI experiment no. 2 - AST moved down, navigation sidebar trashed, ...

Let's throw some real regex (emailregex.com) at RegExKit. Works 😉 Simplified AST a lot (reused Lexer tokens) and it looks good!

regexbook's tweet image. Let's throw some real regex (emailregex.com) at RegExKit. Works 😉 Simplified AST a lot (reused Lexer tokens) and it looks good!

Another example - mismatched (). No need to calculate opening & closing parentheses to find where the problem is - I will show it to you.

regexbook's tweet image. Another example - mismatched (). No need to calculate opening & closing parentheses to find where the problem is - I will show it to you.

This is what I meant with excellent error reporting - where exactly & what. This specific error means that the syntax is okay, but the maximum allowed number is 0x0010ffff. Screenshot contains "printed" error, not yet an explanation (= user friendly text).

regexbook's tweet image. This is what I meant with excellent error reporting - where exactly & what. This specific error means that the syntax is okay, but the maximum allowed number is 0x0010ffff. Screenshot contains "printed" error, not yet an explanation (= user friendly text).

I consider error reporting tests like these as a good foundation for the quick reference (= what you shouldn't do aka common mistakes).

regexbook's tweet image. I consider error reporting tests like these as a good foundation for the quick reference (= what you shouldn't do aka common mistakes).

Excellent error reporting, right? This was one error before, but there's a difference between how to write it (syntax) and if it has proper meaning. More errors is good in this case.

regexbook's tweet image. Excellent error reporting, right? This was one error before, but there's a difference between how to write it (syntax) and if it has proper meaning. More errors is good in this case.

Feature no. 5 - examples. This is invaluable part of the whole project. You can read documentation, you can play with it, but examples, especially around edge cases, help a lot.


Feature no. 4 - quick reference. There's not enough info. NSRE documentation is outdated (doesn't contain everything), it's hard to find documentation for operator precedence, ... Quick reference must be complete and everything must be documented.


All these three features are almost ready to be shipped. But you know, remaining 10% of work takes 90% of time. Still need some love, but I'm happy with them.


此帳戶目前尚未追蹤任何人
Loading...

Something went wrong.


Something went wrong.