Curious indeed, no offense in my previous comments, Sir. Perhaps you are the same Milen who worked on Socialite? Not sure I find it in your resumee but the Джумеров name matches this article .) https://www.novinite.bg/index.php/articles/6180/Prilojenieto...
At least back in the day, it used to be common to "buy a license" or "buy a serial key". I didn't really put too much thought into the phrasing, as I haven't received any feedback.
Regardless, when you buy it, it's yours forever - no activation, no DRM, no subscription, no fine print.
Yeah I'm very familiar with Josh Ge and Rex - my current project uses rex files for loading images - I just have a lot of metadata I bake in through hacky ways and rex format is not very flexible - rexpaint is great though
I don't use the app often, but I felt comfortable purchasing because it wasn't a subscription. The few times I do want ASCII art, it does the job perfectly, so it works super well to have in my back pocket. Thanks for not going the subscription route.
Are there any enhancements that you've wanted to do, but haven't had the time?
I'm a huge fan, and am surprised how stable Monodraw has been for me. I've kept a single, growing document open as a scratch pad for the last three years. The only downtime was converting it to the new-ish file format haha.
There’s this layout library in C called clay which is basically a renderer agnostic flex box style layout engine. You might be interested in reading its source!
Yeah, there's a few such libraries that I'm aware of but I haven't had time to evaluate them. I do plan to at least look into them and make decision from there.
nucleic/kiwi uses the same algorithm that autolayout uses. It's also a tried and true implementation I've used many times, including in console environments.
In the retro computing world, the use of "ASCII" to construct levels and worlds is quite prevalent.
I immediately considered whether Monodraw might be used as a kind of level editor in that context.
Would you consider adding an '8-bit character bitmap' mode, which allows for the bitmap to also be edited?
With such a feature, Monodraw would become immediately applicable to those of us building retro games for older platforms where this technique is used rather extensively to produce compelling art-work.
For context, here is an example game which uses plain ol' ASCII chars to deliver some fun Moon Buggy action:
> Would you consider adding an '8-bit character bitmap' mode, which allows for the bitmap to also be edited?
Can you clarify with an example? Monodraw supports "surfaces" which are just like bitmaps - you can use the Pencil tool and draw on those surfaces with any characters you want (there's a palette in the inspector), just like a bitmap editor.
Adding more character sets besides ASCII and shape elements?
Having all the Unicode emoji galore as an option would be great. Not just for colorful code docs, but millions of social media content creators out there!
I guess we might be describing the same thing, and I am yet to have time to download and play with Monodraw (IT policies), but if there is indeed a way that surfaces could be replaced at a pixel level, so that for example the 'A' character becomes a Pacman, then we'd be aligned.
The only issue is, are these surfaces 8x8 or similar, and would it be possible to load in a 6x8 bitmap, for those unusual 8-bit computers of the era which used them .. I refer to my favourite system of the period, the Oric Atmos, which graphics techniques are described here: https://osdk.org/index.php?page=articles&ref=ART9
IF I can edit the bitmap and render as 6x8 characters, Monodraw would be immediately useful for level design. In any case, when I have access to a non-work computer, I hope to spend some time digging in and informing myself, so apologies if none of this is relevant ..
There are plenty of tools which can be used to do these kinds of projects, I'm more intrigued by the nice interface of Monodraw and whether it can be added to the repertoire ..
Not parent commenter, but I've been using rexpaint for a while but the editor is clunky and format too limited, I've been looking at other options - At a quick look monodraw does look interesting as a more fully featured replacement.
Like many others I also want to express my gratitude for a fantastic app. I bought it in 2016 and it’s seen a lot of use since then (recently almost daily). Being able to copy to clipboard for adding diagrams in source code is the killer feature!
I am trying it for the first time. One point of feedback, with the caveat that my only experience so far is opening the tutorial:
I immediately hate that when intending to scroll vertically using the trackpad on my macbook, it constantly unintentionally scrolls horizontally as well and I have to correct it. It is particularly irritating since there is no content on the canvas to see when scrolling.
Maybe I'm just super accustomed to browser scrolling behaviors, which snap scrolling based on initial direction.
I'm mostly posting this because its the kind of papercut that might be forgotten over time.
Once I started using it for actual diagrams, the issue completely faded away. Scrolling a super long vertical-only document is an unimportant edge case.
This is the god damn holy grail of ascii chart editing.
Great app... it's had a place on my macOS dock for years. I use it for adding diagrams to my team's internal developer documentation (mostly in a series of Markdown files).
What is the Unicode support? Namely the "Symbols for Legacy Computing"[0] (including the latest supplements [1]) with "newly available" full octants palette could be neat to get sub-character "octant pixel" precision. (And/or exploitation of Braille [2] for the same purpose.)
(Not a Mac user, so cannot try, and not clear from screenshots for me; these all seem like ASCII + )
It definitely looks like a cool app, and I was excited to test it out, but I don't have a Mac. If you ever hit the point where a rewrite makes sense, it would be awesome as a universal app.
One idea I've been toying with would be to do a Kickstarter-style campaign and if it reaches a certain threshold, then I know it would be worth porting.
Targeting Windows/Linux/web still means I cannot re-use the sources. But targeting web might be faster in terms of development time, although I don't have deep expertise on non-Apple platforms, so I cannot say for sure.
Why? There are already all kinds of web sites that do this kind of thing. Monodraw's unique selling point is that it's a native Mac app that takes advantage of the Mac UI and it's done well so the UX is top notch.
If you don't care about making the best possible app that you can, go ahead and do it in the browser. You will get something that's probably good enough and runs everywhere. But it's going to use more battery, more memory, and more bandwidth and not feel like a Mac app. Plus (IMHO) it's less fun to develop for the browser.
I believe the attention to detail that sets Monodraw apart can be transposed to the web as well — albeit diverging from MacOS conventions.
It’s possible to make great web apps, it just takes the kind of care and dedication that @milen has already proven to have. If the web interface lowers the barriers to developing a cross-platform version of Monodraw, then I think it would be silly not to consider investing in it.
Nice tagline, but surely it's not just plain text. It's some unicode shenanigans. How does one make sure their console can display all the necessary characters? How does one make sure others can see their creation?
>I find it unlikely that such copy protection would actually convert a non-paying user into a customer.
I used to think that but then kept tripping across customers who ran multiple copies of my software after purchasing a single license. I now wish I'd tightened the DRM from the start.
I think you're missing his point. If you tightened DRM, would those customers that ran multiple copies pay for multiple licenses?
Fighting piracy is generally not worth it. Those people would never pay, so you're fighting to stop a pirate from using it, not to get them to pay. There's a big difference.
The way that DRM and similar user-not-in-control technologies are making the world into a skinner box is a bigger problem than anything solved by those technologies.
Companies participating in that transformation don't get my money and I'm glad to know that this isn't one of them.
People who pirate software at scale are not typically interested in ASCII art. It doesn't quite cross the threshold of business value and usefulness (e.g. SolidWorks, Photoshop) that would attract pirates.
Just wanted to say: really love the app. Been using it for years. I love the image overlay since I mainly enjoy making ascii renditions of pictures manually by hand.
3x2 were more popular, used in, among others, Teletext and the TRS-80. The only place we found the 4x2s was the Kaypro portable (using the upper 128 positions of the character generator plus a reverse video bit to get all 265 combinations).
Yeah, it was. After I finished working on the iOS app I was previously involved with, I needed to either find a job or make another app.
I was browsing StackOverflow and saw some cool looking ASCII diagrams, thinking to myself "How can I make these easily on macOS?". So that's how the idea was born.
I then spent about 1.5yrs from the initial commit until v1 release. Unfortunately, the financials didn't work out, so I had to find a job eventually.
But I'm still maintaining the app and do have longer term plans when my job situation changes.
you were involved with clear? damn! i was one of the first users back then, even using it to this day! monodraw looks awesome, will definitely check it out!
I was one of the co-creators of Clear and the developer who built the iOS app. It was co-created by me, Realmac and Impending. I had previously interned at Realmac and had been friends with the founder, Dan (they acquired another app of ours - EventBox, which later got rebranded as Socialite).
We created the most popular (at the time) “all in one” app for macOS back in 2008 called EventBox [1].
It aggregated RSS, Twitter, Digg, Facebook, Flickr, Reddit.
So it’s a very old idea that’s just coming back - like a lot of things, it goes in cycles.
We ended up selling the software to another company. My personal advice - never build your business on top of other companies data/APIs, they can cut you off at any point.
> 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!).
I've considered the idea of letting other developers have access to the source code and help with the development. Unfortunately, I couldn't figure a way to make it fair - e.g., if someone starts contributing, do they start receiving a percentage of the proceeds? What's a fair percentage and what about multiple external contributors?
I could never come up with a workable model, so it's either fully open-source or proprietary. As I mentioned in another comment, I believe the way to go is an open data format which allows interoperability. This way there's no lock-in and competing apps (open or closed) can exist.
For what it's worth, the Monodraw data format is not secret, it's just compressed JSON. I haven't documented it because it's more of an implementation detail and I'd rather spend my very limited time on improving the product.
Thank you for the comment, apologies if I came off a bit antagonistic! It's just a little frustrating when you see really great apps potentially ending.
It's really too bad there's not a better indie-dev model for the App Store, if I am buying an app (I think maybe I maybe paid $19 for Monodraw -- totally worth it btw), am I buying the app as-is? or do I get updates ... if so how long should I expect to get them and are the updates minor fixes or bigger whizbang features.
I can see that once an app gets to a steady state, there's probably diminishing returns in putting a lot of effort into new features esp. if your market is small. On the other hand, if the app has some sort of subscription, now there is an expectation for updates (not unreasonable, but possibly the numbers might not work for the developer).
I think Pixelmoter sort of got this right, although they did release a Pro version separately (which I also bought). However, I suspect they're a much larger company and probably have quite a large market share and can afford to continue to release updates to keep it fresh (and for someone like me, the app is exactly what I need vs. say photoshop and the price point is reasonable).
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 a plain text format (currently, it’s just zipped JSON which doesn’t play nice with VCS).
Interoperability is key to competition and avoiding lock-in, so I’ll push in that direction as my time permits.
I understand your concerns about open-sourcing the codebase and won’t try to convince you otherwise. It’s your code.
That said, I would like to share my perspective on the subject, having given some thought to if/how I should open source my code. I don’t feel that I have any ground to stand on if I were to choose not to open source my code. That same code would be uploaded to the internet using a web browser or other tool that is open source. That code is probably compiled or interpreted by a tool that’s open source. For me, it all runs on an operating system that’s open source. Nearly everything that I am able to do as a software developer is built on the shoulders of giants who, out of kindness and conviction in their beliefs, chose to make an entire ecosystem of software available to the world, with source code available, free of charge. I feel that I owe it to the world to pay that legacy forward.
Aye, but you're commenting on a Mac program, which is necessarily developed on a closed, anti-competitive system (and in the context of that ecosystem, accepting it as normal). GP lives in a much darker world than you.
> I believe in a strong, centralised product vision and execution
Fair point! I'm reminded of this quote from Jaron Lanier:
> Why are so many of the more sophisticated examples of code in the online world—like the page-rank algorithms in the top search engines or like Adobe’s Flash—the results of proprietary development? Why did the adored iPhone come out of what many regard as the most closed, tyrannically managed software-development shop on Earth?
>An honest empiricist must conclude that while the open approach has been able to create lovely, polished copies, it hasn’t been so good at creating notable originals. Even though the open-source movement has a stinging countercultural rhetoric, it has in practice been a conservative force.
I love free software, yet most of the software I use is proprietary. (I consider my own apathy as contributing to the problem...)
As for this point,
- The code will be packaged up and sold by unscrupulous people who will not contribute back
an interesting example is Jason Rohrer, who has open sourced all (?) his games.
The way he got around this is that he made a multiplayer game, where the $20 in effect gave you access to the main server. People indeed repackaged his game, sold it on other platforms etc. Yet last I checked, he was doing better than ever. (Probably cause he keeps pushing out updates to keep the game interesting.)
Not sure how well this works for "single-player software", although Aseprite seems to be doing all right. (Though technically not free software anymore, despite being open-source...)
Nitpick: Aseprite is source-available, not open source by the Open Source Initiative's definition. From the Aseprite EULA [1]:
> (g) Source code.
> You may only compile and modify the source code of the SOFTWARE PRODUCT for your own personal purpose or to propose a contribution to the SOFTWARE PRODUCT.
The OSI's definition of open source [2] permits distribution of unmodified and modified copies (with the exception of lone, unmodified copies; I read somewhere that adding a hello world program is a workaround):
> 1. Free Redistribution
> The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
...
> 3. Derived Works
> The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
"free software" is ambiguous to English speakers/writers, but "open source" is ambiguous in its own way.
By the way, there is a "Fork of the last GPLv2 commit of Aseprite" called Libresprite [3].
A license wouldn't stop the unscrupulous people, they'll keep making clones of it and ignoring the license.
This means I have to start chasing any clones, engage legally and try to take them down. It's just not worth the time - I would rather spend the time on improving Monodraw instead.
If unscrupulous people are willing to ignore the license anyway, wouldn't they just hex edit to change the branding to sell clones even while it's closed source?
Thank you all for the kind words regarding the app.
Unfortunately, my time is extremely limited which is why I haven’t had the chance to push more updates out.
I’ve got a few highly requested features in the works but I cannot promise when they’ll see the light of day (I usually get to make progress during my holidays).
I’m still committed to fixing any breakages due to OS upgrades and ensuring the product continues to work.
Thanks for your work in making an excellent tool; I, and many of my coworkers, use this. The price point is entirely fair and it’s a pleasure to use every time. But - above this - thank you also for prioritising personal life above development.
It’s great as it is and we’ll be happy to see new features when you’re ready. I would be really proud if I were in your position.
Thank you, Milen! It's nice to see Bulgarians being behind a popular desktop app! I've been a paid user for years and Monodraw is among the first apps I install when I get a new MacBook machine!
to offer a guess, I assume plantext probably means plain ASCII or maybe extended US ASCII (adds IBM box drawing chars, etc.) As opposed to full unicode text charset.
Hi - I'm not a user but I am reacting to obvious love many developers have for your app.
Have you thought about open-sourcing it?
Or even keeping it closed source but crowd-sourcing help?
No need for profit sharing - your income is a nominal management fee if that. Just need a nice credits page to give thanks to the names of the people who contributed.
There’s no affiliation whatsoever, I’m actually quite surprised every time Monodraw appears on the front page as the app just had its 10th birthday.
I would have assumed most people in the community would know about it by now.