Stretching the idea of "plain text" quite far imho.
Monodraw
31–40 of 218 posts
Re: Monodraw
#32These used to be called Macro Shops back in the 90s AOL prog/punter scene.
There used to be thousands of truly incredible ASCII macro artworks. This is barely scratching the surface.
https://i0.wp.com/justinakapaste.com/wp-content/uploads/2014...
Re: Monodraw
#33what's the native linux alternative? aka not a webapp edit: hm, maybe https://github.com/nkh/P5-App-Asciio
emacs artist mode also suitable for something like that
Re: Monodraw
#34Funny. The front page (still) states: "We're a small studio that loves to make delightful apps. We just launched Monodraw." The blog says: Maintenance Mode With immediate effect, Monodraw is entering maintenance mode. This means that there will be no more updates in the future. While I'll be aiming to provide OS compatibility updates, if required, those are not guaranteed. Accordingly, the price has been reduced from…
Please not more app-store abandonware. I have a decent amount on both my phone and my MBP. Sad to see, I really liked Monodraw for creating ASCII illustrations for source code (e.g. buffer layouts etc).
Of course, probably it'll be ok for a while, but then some App Store API or updated processor requirements will render it unusable like so many others (particularly on iOS).
So now I've got several abandonware apps that I paid for: Things (v1), Quiver, Artboard and now Monodraw. I can't say any of them really had any non-minor updates since I got them certainly not features (yes, I realize Things did a separate V2 app ... but I wasn't happy about that happening so soon after buying V1). I do realize some of this is Apple's fault in the way the store is structured.
Too bad Apple doesn't enact some sort of source-code escrow such that if an app is abandoned, the source gets published, but with owner-copyright retained so no-one can resell -- as part of the T&C of submitting an app. Maybe after 1 year of abandonment for a "big" company and 2 years for indie-dev apps.
*EDIT*: Happy to see Milen's sibling comment about fixing breakage!! I realize you have to make a living -- is there a way to contribute for these new features (or is it a totally new app -- which is fine!).
Re: Monodraw
#35Earlier quoted context omitted.
And thanks to being proprietary, no one else can devote time to it, either.
I’ve toyed with the idea of open sourcing the product. I reached the conclusion that it’s not the approach for two main reasons: - I believe in a strong, centralised product vision and execution - The code will be packaged up and sold by unscrupulous people who will not contribute back I’m a strong advocate of interoperability and open data formats. The Monodraw data format is not proprietary and I do have plans for…
> The code will be packaged up and sold by unscrupulous people who will not contribute back
Choose a good license then
Re: Monodraw
#36I love this tool! I've used it to do diagrams for Mapless: https://sebastianconcept.github.io/Mapless/guides/2024/01/28... And to document this Pharo VM Plugin builder setup: https://github.com/sebastianconcept/PharoPluginBuilder
Love this too -- I use this to document source code, being able to visualize a buffer or structure layout in the code is so nice!
Re: Monodraw
#37Earlier quoted context omitted.
From the FAQ at the bottom > Why not open source the app? > > Maintaining an open-source project can be a significant amount of work and I'm not going to have the time to take on such responsibilities. Furthermore, open-sourcing full products tends to result in many clones being sold directly to unsuspecting customers which is not something I want to enable. It's strange how both of those statements are incorrect...…
a license doesn't magically stop bad things from happening.
it doesn't, but it's a deterrent. the very fact that this app had limited commercial success is reason to believe there likely won't be "many clones", especially if they're forced to go against the license
Re: Monodraw
#38I love this tool! I've used it to do diagrams for Mapless: https://sebastianconcept.github.io/Mapless/guides/2024/01/28... And to document this Pharo VM Plugin builder setup: https://github.com/sebastianconcept/PharoPluginBuilder
So you used an ASCII drawing tool to draw these diagrams in text then took a screenshot of them and uploaded to your website? That seems like such a convoluted way to draw a few rectangles. Isn't there an easier way?
Doesn't seem more convoluted than any other drawing tool to me. The UI of Monodraw appears to be pretty similar to "regular" drawing software.
Re: Monodraw
#39I love this tool! I've used it to do diagrams for Mapless: https://sebastianconcept.github.io/Mapless/guides/2024/01/28... And to document this Pharo VM Plugin builder setup: https://github.com/sebastianconcept/PharoPluginBuilder
So you used an ASCII drawing tool to draw these diagrams in text then took a screenshot of them and uploaded to your website? That seems like such a convoluted way to draw a few rectangles. Isn't there an easier way?
1. You can just “Save as” to PNG, it takes no time or effort.
2. I use to use Monodraw exclusively for making diagrams in source code, but over time I’ve become so comfortable with the tool, keyboard shortcuts, etc. that now I just use it for all diagrams. It’s a very nice tool.
Re: Monodraw
#40what's the native linux alternative? aka not a webapp edit: hm, maybe https://github.com/nkh/P5-App-Asciio
For anyone who is willing to use a webapp, I like drawio[0]. You can download locally[1] and self host (I just use the python webserver).
While finding the Github, I see they now actually package an Electron application, so that is probably worth exploring[2].