Re: free_layout branch status?
On Wed, Jul 27, 2011 at 7:41 PM, lewis lewisn...@operamail.com wrote: Running Unit Tests with the latest build 4439 can result in leoRecentFiles.txt being overwritten. After running launchLeo.py leo/test/unitTest.leo (Alt-4) and unitTest.leo is still active the FileRecent Files menu is disabled. The overwrite occurs upon closure of the unitTest.leo file. As you say, it's not the running of the unit tests that overwrites leoRecentFiles.txt, but the closing of unitTest.leo. This is intended, in the sense that it Leo's normal operation. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
True, but it overwrites and removes all previous file records which surprised me. That's why I suggested a backup, or just add unitTest.leo to the leoRecentFiles.txt file. Lewis On Jul 28, 9:03 pm, Edward K. Ream edream...@gmail.com wrote: As you say, it's not the running of the unit tests that overwrites leoRecentFiles.txt, but the closing of unitTest.leo. This is intended, in the sense that it Leo's normal operation. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
On Thu, Jul 28, 2011 at 8:39 AM, lewis lewisn...@operamail.com wrote: True, but it overwrites and removes all previous file records which surprised me. I wonder whether perhaps a unit test does this... Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
free_layout branch status?
In another thread Terry asked about merging the free_layout branch into the trunk. I just pulled the latest rev, 4449. It may do what it is supposed to do, but it fails all the viewrendered tests. I won't consider doing a merge until you can demonstrate a branch that works. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
On Wed, 27 Jul 2011 04:12:58 -0700 (PDT) Edward K. Ream edream...@gmail.com wrote: In another thread Terry asked about merging the free_layout branch into the trunk. I just pulled the latest rev, 4449. It may do what it is supposed to do, but it fails all the viewrendered tests. I won't consider doing a merge until you can demonstrate a branch that works. How do I run the viewrendered tests? I do HOME=/tmp python launchLeo.py leo/test/unitTest.leo Alt-4 and get -- Ran 731 tests in 43.765s OK Cheers -Terry -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
On Jul 27, 9:00 am, Terry Brown terry_n_br...@yahoo.com wrote: How do I run the viewrendered tests? I do I guess I was expecting you to read my mind :-) 1. In test.leo, you should see the proper docstring when choosing a plugin from the plugin menu. I see lots of docutils errors. I'm not sure why this is happening: it may be missing stylesheets, or problems with a plugin. BTW, The viewrendered plugin is enabled in test.leo. 1. In test.leo, there are various nodes that are children of the node: Recent--viewrendered examples Clicking one of the test nodes, @svg bubbles.svg, should show the rendered body text. For this node, the rendering should be an animated svg graphic. For me, choosing the viewrendered command shows the graphic in a separate window rather than a new pane in the Leo window. Some kinds of rendering do work: @svg, @image, rst and html. However, the separate rendering pane does not appear to support movies. You may prefer something other operation, but I'd like to discuss the new user interface before merging into the trunk. 2. Choosing a plugin in the plugins menu opens a separate rendering pane, with lots of docutils errors. This may be a configuration problem, but I'd like to have it work by using the viewrendered plugin if it exists. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
On Wed, 27 Jul 2011 07:18:00 -0700 (PDT) Edward K. Ream edream...@gmail.com wrote: 1. In test.leo, you should see the proper docstring when choosing a plugin from the plugin menu. I see lots of docutils errors. I think part of the problem is the free_layout branch needs to have free_layout enabled by default, I'll add it to leoSettings on that branch. I'll check the things you've mentioned, but when I was re-implementing viewrendered I had a test doc. with html / rst / svg / a movie and they all worked. I've always found the presence of both untiTest.leo and test.leo confusing for running tests, can you confirm that my approach for running unit tests is correct: HOME=/tmp python launchLeo.py leo/test/unitTest.leo Alt-4 (even if that doesn't include the viewrendered tests) Cheers -Terry -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
On Wed, Jul 27, 2011 at 9:26 AM, Terry Brown terry_n_br...@yahoo.com wrote: I've always found the presence of both untiTest.leo and test.leo confusing for running tests, can you confirm that my approach for running unit tests is correct: HOME=/tmp python launchLeo.py leo/test/unitTest.leo Alt-4 Yes. That looks right. You might want to disable caching as well. test.leo was intended for by-hand tests. All the real unit test should be in unitTest.leo. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
Re: free_layout branch status?
Edward, Running Unit Tests with the latest build 4439 can result in leoRecentFiles.txt being overwritten. After running launchLeo.py leo/test/unitTest.leo (Alt-4) and unitTest.leo is still active the FileRecent Files menu is disabled. The overwrite occurs upon closure of the unitTest.leo file. Is this intended result of running unit tests? Maybe a backup file should be created. Leo Log Window Leo 4.9 final, build 4411(4439), June 21, 2011 Python 2.7.2, qt version 4.7.2 Windows 6, 1, 7600, 2, Lewis On Jul 28, 4:41 am, Edward K. Ream edream...@gmail.com wrote: On Wed, Jul 27, 2011 at 9:26 AM, Terry Brown terry_n_br...@yahoo.com wrote: I've always found the presence of both untiTest.leo and test.leo confusing for running tests, can you confirm that my approach for running unit tests is correct: HOME=/tmp python launchLeo.py leo/test/unitTest.leo Alt-4 Yes. That looks right. You might want to disable caching as well. test.leo was intended for by-hand tests. All the real unit test should be in unitTest.leo. Edward -- 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 group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
