Hello Edward,
Am Dienstag, 27. März 2012 14:53:03 UTC+2 schrieb Edward K. Ream:
Adding multiple sets of (colored) links will be one of the defining
features of Leo 5.0. But that's almost so easy as to be not worth
discussing!
Much of Leo's long-term development will focus on huge
On Sun, Apr 1, 2012 at 4:34 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
At least from my point of view I would also add documentation to this
list.
A reasonable idea, but I have reservations. The problem, imo, is that
people don't typically read documentation ;-)
The best designs,
Hello Edward,
Am Sonntag, 1. April 2012 14:14:34 UTC+2 schrieb Edward K. Ream:
On Sun, Apr 1, 2012 at 4:34 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
At least from my point of view I would also add documentation to this
list.
A reasonable idea, but I have reservations. The
On Sun, Apr 1, 2012 at 9:23 AM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
Aren't you comparing apples and oranges here? - The iPhone is a device or a
UX-Technology, while Leo is an app (outliner, editor, PIM, IDE, etc.)
That's true. But I still don't think that documentation is all
On Monday, April 2, 2012 2:51:16 AM UTC+7, Edward K. Ream wrote:
That's true. But I still don't think that documentation is all that
useful. For interesting questions one must ask.
IMO there should always be a step-by-step getting started cookbook
targeted to the relative noob on
I think that fossil http://www.fossil-scm.org is worth trying when we
speak of distributed systems. It consists of just one executable and it has
included http transport, standalone http server, cgi enabled,...
Actually I have made some simple script-buttons few months ago to
disassemble Leo
I realize I'm speaking from a technically impoverished background, and I am
repeating myself, but only because I really think this is important. If I'm
way off base, missing something fundamental about the desired functionality
please let me know, or of course feel free to ignore.
IMO if it's
On Wednesday, March 28, 2012 12:16:38 PM UTC+2, HansBKK wrote:
Selecting any one of git/fossil/mercurial etc as a dependency for
distributed Leo will IMO deliver a much lower return on effort expended
than a solution that allows a group to go Leo on top of whatever cool
tool they're
On Wed, Mar 28, 2012 at 5:16 AM, HansBKK hans...@gmail.com wrote:
IMO if it's at all possible, a solution should be implemented that is
generic and carried in the filesystem and therefore not proprietary to any
single DVCS - or other file-sync-and-merge tools like Dropbox or Unison or.
True,
Adding multiple sets of (colored) links will be one of the defining
features of Leo 5.0. But that's almost so easy as to be not worth
discussing!
Much of Leo's long-term development will focus on huge distributed
Leo outlines. This also relates to wishlist bug: sync nodes to a
common
Zope provides a coding framework which has evolved into a set of
tools and a very disciplined methodology. Folks who understand the
complexity and use the idioms correctly seem to build apps which don't
end up hitting walls due to scale or extensibility. This seems to come
at the price of a
On Tue, Mar 27, 2012 at 9:39 AM, Kent Tenney kten...@gmail.com wrote:
I don't think the Z world would provide a lot of help with
distributed/shared outlines.
If Leo is to stand on shoulders here, my guess is that the giant would more
likely be one of the distributed versioning systems. Git
On Mar 27, 9:42 am, Edward K. Ream edream...@gmail.com wrote:
I'll put git on the list of things to study.
Linus's talk at Google is so interesting:
http://www.youtube.com/watch?v=4XpnKHJAok8
It would be great to have Leo be distributed in the way he
describes...
EKR
--
You received this
On Mar 27, 10:19 am, Edward K. Ream edream...@gmail.com wrote:
On Mar 27, 9:42 am, Edward K. Ream edream...@gmail.com wrote:
I'll put git on the list of things to study.
Linus's talk at Google is so
interesting:http://www.youtube.com/watch?v=4XpnKHJAok8
It would be great to have Leo be
On Mar 27, 10:36 am, Edward K. Ream edream...@gmail.com wrote:
I'm still watching. This is a terrific talk. Way better than average.
Leo (.leo files) makes merging harder. Git makes merging easier, so
Linus says. I wonder whether we could use the git tricks in Leo, or
just simply use git
On Mar 27, 10:45 am, Edward K. Ream edream...@gmail.com wrote:
Leo (.leo files) makes merging harder. Git makes merging easier, so
Linus says. I wonder whether we could use the git tricks in Leo, or
just simply use git to merge .leo files...
Git doesn't track files, it tracks content.
On Tue, Mar 27, 2012 at 3:53 PM, Edward K. Ream edream...@gmail.com wrote:
1. Huge Leo outlines would likely be based on zodb or Zope itself.
The next thought was new: Zope has *already* solved many (all?) the
problems that Leo would encounter with distributed/shared outlines.
So rather than
... and by faster, I mean both speed at which it gets implemented, and
speed at which it executes.
On Tue, Mar 27, 2012 at 10:33 PM, Ville M. Vainio vivai...@gmail.com wrote:
On Tue, Mar 27, 2012 at 3:53 PM, Edward K. Ream edream...@gmail.com wrote:
1. Huge Leo outlines would likely be based
On Tue, Mar 27, 2012 at 2:33 PM, Ville M. Vainio vivai...@gmail.com wrote:
It would probably be a much faster and orthodox solution to expand
on the sqlite work, already done.
Thanks for the reminder. I'll keep this in mind.
EKR
--
You received this message because you are subscribed to
This may be of interest.
http://www.confreaks.com/videos/443-rubyconf2010-git-the-stupid-nosql-database
-m
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com.
To unsubscribe from this
20 matches
Mail list logo
