Hi,
On 10/27/11 19:48, Edward K. Ream wrote:
[...]
The iPhone parallel doesn't become valid until the gui era.
But we are in the gui era now, and my experience is that the need for
complex docs is a sign of design defects.
The contrary point of view isn't entirely invalid: consider the rst
On Wed, 09 Nov 2011 06:36:08 -0500
Offray Vladimir Luna Cárdenas wrote:
> And, contrary to the crowd opinion, I find difficult to believe that Mac
> is a model for good design if you want people creating stuff with their
> machines instead of consuming it. The videos before the launching of
>
On 11/09/11 08:05, Terry Brown wrote:
On Wed, 09 Nov 2011 06:36:08 -0500
Offray Vladimir Luna Cárdenas wrote:
And, contrary to the crowd opinion, I find difficult to believe that Mac
is a model for good design if you want people creating stuff with their
machines instead of consuming it. The
OK, did the steps
There are two @test Assert True nodes and I assumed I should ignore
the one in the @ignore branch
If I understand right, Alt-4
(1) only runs unit @test nodes that are marked
(2) sends results to console
And I originally thought Alt-4 used leoDynamicUnittest.py but by
addi
I'm going to back-burner the live updating ideas and concentrate
on running static analysis on Leo files, so no need to worry about
this on my account.
Thanks,
Kent
On Tue, Nov 8, 2011 at 3:12 PM, Kent Tenney wrote:
> On Sun, Nov 6, 2011 at 3:35 PM, Edward K. Ream wrote:
>> On Nov 6, 2:20 pm, K
On Tue, Nov 8, 2011 at 7:19 PM, Edward K. Ream wrote:
>> I've just updated all my batch files so they start with: chcp 65001,
>> and I think that is the end of this adventure.
This was a bad idea, regardless of bzr complaints. Clearly, I want a
testing environment that is as close to "typical"
On Wed, Nov 9, 2011 at 5:36 AM, Offray Vladimir Luna Cárdenas
> The moment you want to create is the moment that you
> need to deal with details of creation and is also the moment you will need
> to deal with documentation, that's why the idea of Smalltalk about the
> system being the curricula or
On Tue, Nov 8, 2011 at 3:25 PM, ne1uno wrote:
> shouldn't there be some way to incorporate the sense of levels in unit
> tests?
I don't need such levels: Instead, I select the desired tree in
unitTest.leo and hit Alt-4, which *in unitTest.leo* is bound to
run-selected-unit-tests-locally.
In the
On Wed, Nov 9, 2011 at 7:39 AM, mdb wrote:
> OK, did the steps
> There are two @test Assert True nodes and I assumed I should ignore
> the one in the @ignore branch
Correct.
> If I understand right, Alt-4
> (1) only runs unit @test nodes that are marked
> (2) sends results to console
C
On Tue, Nov 8, 2011 at 2:55 PM, Kent Tenney wrote:
> I see no mention of activate/deactivate events in ...
Scripting Leo with Python-->@file
Oops. Missing docs. I'll fix this soon.
Leo's qt gui generates two such events::
g.doHook('activate',c=c,p=c.p,v=c.p,event=event)
g.doHook('ac
On Tue, Nov 8, 2011 at 3:12 PM, Kent Tenney wrote:
> I don't know what "in selectHelper" means
In leoPy.leo, search for "def selectHelper".
> To test event handlers, I'm using the following which monitors
> the selectx and unselectx events
You probably don't need this extra code.
The eventFil
Hello,
I am using leo-editor-snapshot-20090253. If you open attached file,
save shadow file and try to reread it, it won't be read correctly, the D
node changes.
I have originally encountered this on much bigger file and in that case it
actually caused corruption - shadow file could not be rea
The contract-or-go-left (Alt-Left) command now collapses all children
when selecting the parent.
This fixes an almost subliminal "huh" that sometimes happens when I
think I am in one child, but aren't, and I expect another child to be
collapsed when hitting Alt-Left.
I am tempted not to mention t
I see in Leo documentation that is possible to add attributes to nodes
and .leo files.
I am thinking of adding date created & date modified attributes to
nodes for a particular project.
Has anyone done this already ? (before I re-invent the wheel)
And I wonder if node dates have ever been conside
On Wed, Nov 9, 2011 at 11:01 AM, Juraj Variny wrote:
> I am using leo-editor-snapshot-20090253. If you open attached file, save
> shadow file and try to reread it, it won't be read correctly, the D node
> changes.
Thanks for this report. It's on the list to fix.
I believe the best fix will
the creation date of a node can be teased from the gnx
I use the following functions:
def gnx2tuple(gnx):
"""return a tuple (year, month, day, hour, minute, second)
"""
result = gnx.split(".")
# remove the user component
who = result.pop(0)
date = result.pop(0)
#not all
On Nov 3, 10:03 am, "Edward K. Ream" wrote:
> In any event, my initial enthusiasm for the scanner-based approach was
> unfounded. I had forgotten to remove the code that completely ignores
> whitespace. When I did so, the original whitespace failure reappeared!
Rev 4767 of the trunk completes
On Oct 28, 2:49 am, zpcspm wrote:
> Sometimes I have to look at badly aligned HTML code and keep asking
> myself questions like "here's the opening tag, I wonder where it
> closes".
To be clear, rev 4767 imports data.html properly.
Edward
--
You received this message because you are subscrib
On Thu, Oct 27, 2011 at 3:29 PM, Edward K. Ream wrote:
> On Thu, Oct 27, 2011 at 1:21 PM, Ville M. Vainio wrote:
>> This method
>> w3ill destroy all your history and all your files will get new file
>> ids, so your new branch will be totally incompatible with old branch.
>
> Not ok with me.
Is i
Thanks I did not know about gnx. Your gnx2tuple( function makes it
easy to create a datetime object
def gnx2datetime(gnx):
import datetime
(year, month, day, hour, minute, second) = gnx2tuple(gnx)
dx= datetime.datetime(year, month, day, hour, minute, second)
return dx
However, a
On Nov 9, 11:02 pm, "Edward K. Ream" wrote:
> On Oct 28, 2:49 am, zpcspm wrote:
>
> > Sometimes I have to look at badly aligned HTML code and keep asking
> > myself questions like "here's the opening tag, I wonder where it
> > closes".
>
> To be clear, rev 4767 imports data.html properly.
>
> E
21 matches
Mail list logo