[1] https://chromewebstore.google.com/detail/drawio-for-notion/p...
3,672 karma · joined February 24, 2011
[1] https://chromewebstore.google.com/detail/drawio-for-notion/p...
Like last week when Safari 16 broke any use of the command key on Macs and we received 5+ reports per hour until it was fixed.
Adobe can buy the company that is supplying the devs for penpot the same way it bought Figma.
Sure the source can be reused, but you think another collection of individuals will come along and host the project in the same way?
You think the codebase would be developed/maintained at all if all the original devs left? History says otherwise, from the examples I've seen.
We put all the translations in a spreadsheet, https://docs.google.com/spreadsheets/d/1FoYdyEraEQuWofzbYCDP.... We didn't like the idea of storing in any more complex than a csv file.
All changes are shown to us in a diff before we merge, the csv is then downloaded and the i18n files created automatically after we merge the branch.
We've never had a single instance of abuse in over 10 years.
We're a funded, open source project, looking for someone to make a coherent set of diagram templates (https://app.diagrams.net/?mode=device , click new ).
This isn't a technical role. Might suit someone looking for a low pressure, low complexity role. You'll need a reasonable eye for design.
You'll need to be a independent worker. We'll say "take the current ~200 templates to 1k+ , make them useful to people, look good and be coherent as an overall set". You'll say ok and start on a plan to implement that.
Could be done part-time or full-time. If you get to 1k templates, then go to 2k, 10k if it floats your boat. Apply david@draw.io
The former is fine, as long as the license is the one that the software is publicly licensed under.
We don’t measure it at all, but there’s plenty of companies we know are over 1k users.
We found the best solution was to claim that pricing kicked in at certain usage tiers, whereas everything is actually free all the time.
The reason for its usage is historic. Originally, this project was the underlying diagramming library only, that uses the SVG DOM for rendering. There was no application and no SVG export, that wasn't a function of the library.
FOs in SVG gave us the whole range of HTML in shape labels. So, as well as complex text formatting, we used it for tables, complex composites, etc. There a large legacy of shapes that use complex HTML for labels, we can't drop support for those.
The app itself came later and the SVG export function even later. It was fairly easy to generate because we can take it from the SVG DOM. But, converting HTML to SVG requires parsing the full HTML specification and generating the SVG to maintain compatibilty. This is an horrifically large task, it would require probably 5+ people full time, we don't have that resource.
I'm not sure calling it SVG is "tacky". It is part of the SVG 1.1 spec, albeit an optional one, it's not like it's isn't SVG at all. But yes, it causes confusion, thus the entry in the README [1], "It is not an SVG editing app, the SVG export is designed only for embedding in web pages, not for further editing in other tools."
Even using SVG for word wrapping alone, we've repeatedly asked critics how to do that without HTML for measuring the font metrics, we're yet to receive an answer how to do that in JavaScript. We've had plenty of comments pointing out this is wrong, we need a practical alternative thought out in detail.
But yes, I see the problem with docker, we don't actually use any of the docker images anywhere. Why is node a problem?
We are thinking about adding an option to make the SVG export go via PDF through inkscape to make the labels all SVG. The end SVG is actually smaller than the one we produce in initial testing.
There's also various docker images [2] including one for the image generations.
[1] https://github.com/jgraph/draw-image-export2 [2] https://github.com/jgraph/docker-drawio
[0] https://www.cancerresearchuk.org/health-professional/cancer-...
As you as you do anything programmatic in/out of these drives it all hits the fan. So I'd add to the original statement - "Avoid 'technical' companies with special characters in their name", it's just not right...
You're targeting devs, we hate this stuff :). What I like is markdown based, VSCode based, open source, alternative to Confluence for tech teams. Make that clear.
Anyone in the middle can change the web site into anything they like. They could add a "donate link", saying that the author needs money to sustain the site.