Leo is the last outliner you'll ever need. http://leoeditor.com/
Concord, our GPL outliner
61–63 of 63 posts
Re: Concord, our GPL outliner
#62Earlier quoted context omitted.
I'm almost certain he writes the code using an outliner tool as well like was the case for the scripting language that shipped with frontier and the OPML editor so that probably makes it easier for him to manage. At least it will be easy to include into a project ;-)
It's only a problem if you edit in a flat text editor. If you look in the opml folder of the repo you'll find the source files for all the js and css files.
Ah, thanks for pointing those files out. I'll have to try loading them up in Fargo for fun.
Re: Concord, our GPL outliner
#63Earlier quoted context omitted.
The GPL is not about being practical, it's about freedom. That's why it's the only licence I would consider releasing software under.
How does a license being confusing to the people that use it (and somewhat to the people that WROTE it) aid in promoting freedom?
I find it a bit dishonest when people describe GPL as confusing.
Sure, anything can be confusing. A door nob is surely confusing to some people, especially if they never seen one before. But a door nob is not inherently confusing, and intellectually honest people would not describe it as such.
Let me ask, what is confusing about a license that say:
You can and may do anything with this code, so long you allow others to do the same,
and to any modified version you might create.
To quote the license:
To protect your rights, we need to prevent others from denying you these rights or
asking you to surrender the rights. Therefore, you have certain responsibilities if
you distribute copies of the software, or if you modify it: responsibilities to
respect the freedom of others.