Unfortunately in minimal maintenance mode for the last 3 years. https://blog.helftone.com/monodraw-maintenance-mode/ Still works well though.
Monodraw: ASCII art editor for the Mac
21–30 of 109 posts
Re: Monodraw: ASCII art editor for the Mac
#22Unfortunately in minimal maintenance mode for the last 3 years. https://blog.helftone.com/monodraw-maintenance-mode/ Still works well though.
Re: Monodraw: ASCII art editor for the Mac
#23Re: Monodraw: ASCII art editor for the Mac
#24What an amazingly polished app! It's refreshing to see a new app feel perfectly at home on macOS. $10 to support these folks is worth it.
Re: Monodraw: ASCII art editor for the Mac
#25Re: Monodraw: ASCII art editor for the Mac
#26Re: Monodraw: ASCII art editor for the Mac
#27A couple of workflow tips for using Monodraw:
* Open a few docs in Monodraw at a time and leave them open for your different needs: text boxes, figlets, diagrams. Each with a few elements already waiting to be filled, cut & pasted, etc.
* For larger docs (e.g. newsletters) finish the writing in your text editor and bring it into Monodraw. Think Publisher or InDesign. Yeah, you can edit in here, but it's weird. Best for layout.
* Browse the sample file that opens by default when you load Monodraw. Good fodder in there.
* Snippets!
* Yes, it is just text but there is FILL to give order (front to back) of elements. This is really handy for making slides that expose a list one item at a time.
* Cut and Paste chunks in and out of your Monodraw file with your main document or take a clipped screen capture for dropping into a graphic or fancy format document (e.g. Illustrator). No need to export and paste.
Re: Monodraw: ASCII art editor for the Mac
#28What an amazingly polished app! It's refreshing to see a new app feel perfectly at home on macOS. $10 to support these folks is worth it.
Re: Monodraw: ASCII art editor for the Mac
#29Earlier quoted context omitted.
And think about how much more work it was. And how much more work it'll take to maintain and update. It's an interesting choice to do native. That said, very impressive work.
> And think about how much more work it was. And how much more work it'll take to maintain and update. This isn't really true when supporting a single platform, assuming the author is fluent in AppKit etc.