Re: An xslt prototype for a read-only version of Leo as a web app
On Wed, Feb 18, 2015 at 3:23 PM, Jacob Peck wrote: > > On 2/18/2015 10:54 AM, Edward K. Ream wrote: > > 1. Visiting http://leoeditor.com/xslt-test.leo does not work. > > The browser renders xslt-test.leo xml, not html. That is, the browser > does not perform the xslt transformations. > > Your web server is configured to send .leo files as MIME type 'text/plain' > rather than 'application/xml'. That is a server-side configuration -- > contact your webhost, they should be able to put in a rule for you, if it's > not against their policy. After that, all should work just peachy! > ​Thanks for this. I discussed this with my brother Speed, and he is willing to do this. I am working on another idea just now: - Use a page containing just an html to get the desired url from the user. This form will open another page, say results.html, which run a js script on page load. The script will just run an xslt processor on the .leo file on page load using leo_to_html.xsl. This may be a complete client-side solution. We shall see... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @nosent and file parsing
might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03 AM, Edward K. Ream wrote: > > > On Wed, Feb 18, 2015 at 6:45 AM, Kent Tenney wrote: >> >> OK, I think I see. >> I'm expecting the capability of @auto, which is >> more automatic ... >> >> I'm used to rclick refresh parsing on import, @nosent >> requires parsing manually, creating the required nodes. > > > Exactly. > > Note that once you add add (or delete, or reorder) nodes in the .leo file > and save the @nosent file, Leo will remember your new organization the next > time Leo opens the file. > > >> I would >> hope the simple automation of @auto could remain, > > > @auto will remain for the foreseeable future, that is, "forever" unless > something better comes along. > > Edward > > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to leo-editor+unsubscr...@googlegroups.com. > To post to this group, send email to leo-editor@googlegroups.com. > Visit this group at http://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @nosent and file parsing
Feels like beating a dead horse here, but +1 for this. -->Jake On 2/19/2015 10:59 AM, Kent Tenney wrote: might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03 AM, Edward K. Ream wrote: On Wed, Feb 18, 2015 at 6:45 AM, Kent Tenney wrote: OK, I think I see. I'm expecting the capability of @auto, which is more automatic ... I'm used to rclick refresh parsing on import, @nosent requires parsing manually, creating the required nodes. Exactly. Note that once you add add (or delete, or reorder) nodes in the .leo file and save the @nosent file, Leo will remember your new organization the next time Leo opens the file. I would hope the simple automation of @auto could remain, @auto will remain for the foreseeable future, that is, "forever" unless something better comes along. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @nosent and file parsing
Perhaps user-configurable, with a @bool auto-on-refresh-nosent = True? On 2/19/2015 10:59 AM, Kent Tenney wrote: might it be feasible / make sense to offer @auto style parsing when doing @nosent 'refresh from disk' into a blank body? IE: initial import Thanks, Kent On Wed, Feb 18, 2015 at 7:03 AM, Edward K. Ream wrote: On Wed, Feb 18, 2015 at 6:45 AM, Kent Tenney wrote: OK, I think I see. I'm expecting the capability of @auto, which is more automatic ... I'm used to rclick refresh parsing on import, @nosent requires parsing manually, creating the required nodes. Exactly. Note that once you add add (or delete, or reorder) nodes in the .leo file and save the @nosent file, Leo will remember your new organization the next time Leo opens the file. I would hope the simple automation of @auto could remain, @auto will remain for the foreseeable future, that is, "forever" unless something better comes along. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Leo in virtualenv
Hi, Sorry for the late reaction, some time ago there were a discussion about Leo in virtualenv. Now I could test it in Python3, PyQt5 on Kubuntu: Here are the steps (I worked in a folder with write permission '/leo'): 1. Install PyQt5 in the system: sudo aptitude install python3-pyqt5 2. Create the virtual environment with the '--system-site-packages' switch and without pip (I've found this the only way, which worked): pyvenv-3.4 --system-site-packages --without-pip py3-pyqt5 3. Install setuptools and pip into the created environment: wget --no-check-certificate https://bitbucket.org/pypa/setuptools/raw/bootstrap/ez_setup.py -O ez_setup.py py3-pyqt5/bin/python ez_setup.py --insecure wget --no-check-certificate https://pypi.python.org/packages/source/p/pip/pip-6.0.8.tar.gz#md5=2332e6f97e75ded3bddde0ced01dbda3 tar xzvf pip-6.0.8.tar.gz cd pip-6.0.8 ../py3-pyqt5/bin/python setup.py install cd .. Now you can install what you want in the created environment, without affecting the system. py3-pyqt5/bin/pip install Sphinx 4. From the leo-editor source folder launch Leo with the new interpreter: In my case: /leo/py3-pyqt5/bin/python launchLeo.py Regards Zoltan -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
