Re: Don't save expansion bit in distribution .leo files?

On Fri, Dec 7, 2018 at 11:53 AM Matt Wilkie wrote: > In my own projects I like having the node tree expanded to whatever I was > doing last, so the default setting `@bool put-expansion-bits-in-leo-files = > True` is appropriate. In shared .leo files, as in `LeoPyRef.leo` and > friends this is les

Re: LeoWapp Getting Started

On Sat, Dec 8, 2018 at 12:54 PM Edward K. Ream wrote: Handling the widgets is the easy part. You can see the code in JS side > (flex.Widgets) of leoflexx.py. The tricky part is the python part, which > exists in the PY side of leoflexx.py. The last part of the puzzle is the > startup code, als

Re: LeoWapp Getting Started

On Saturday, December 8, 2018 at 12:39:59 PM UTC-6, Edward K. Ream wrote: Supposing that the server is 100% python, then leoflexx.py is surely at > least a guide. At present, leoflexx.py imports Leo's core and uses flexx > to communicate between the PY side and the JS side. Surely that same m

Re: LeoWapp Getting Started

On Sat, Dec 8, 2018 at 10:56 AM Joe Orr wrote: > Got PhosphorJS to work, so that's cool. > > Definitely agree that we want to get the actual Leo python code doing the > work of modifying file. I'm thinking that the UI needs to be 100% HTML5+Js > talking RESTfully to some kind of service. Since I

Re: LeoWapp Getting Started

Got PhosphorJS to work, so that's cool. Definitely agree that we want to get the actual Leo python code doing the work of modifying file. I'm thinking that the UI needs to be 100% HTML5+Js talking RESTfully to some kind of service. Since I don't know much Python and even less about Leo, on the

leoflexx.py progress report

Work is proceeding as expected. #1005 contains an up-to-date to do list. LeoWapp continues to be pre-alpha software. Today I worked on making the minibuffer more functional. The resulting code is cleaner and shorter than before. This has

Re: LeoWapp Getting Started

On Sat, Dec 8, 2018 at 8:03 AM Edward K. Ream wrote: In discussing this with Rebecca I see that I may have left a misleading impression of my thoughts. LeoWapp *must *support Leo's core. That's what "meeting in the middle" > means to me. > ... > I shall reject forking Leo's core by rewriting it

Re: LeoWapp Getting Started

> On Dec 8, 2018, at 9:03 AM, Edward K. Ream wrote: > > What's a POC? It generally means Proof Of Concept. -- 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 le

Re: LeoWapp Getting Started

On Sat, Dec 8, 2018 at 7:45 AM Joe Orr wrote: I had a look at PhosphorJS and it looks like the best menu and layout > library I've seen. Spent 2 hours this morning trying to get it to compile > with no luck though. > > If I can get PhosphorJS to work (any typescript gurus out there? I raised > an

Re: LeoWapp Getting Started

I had a look at PhosphorJS and it looks like the best menu and layout library I've seen. Spent 2 hours this morning trying to get it to compile with no luck though. If I can get PhosphorJS to work (any typescript gurus out there? I raised an issue on the phosphorjs repo), I think the next ste

Re: Leo nodes as shared urls

Matt, You probably already know this but you can link to individual nodes with LeoVue. Just need to put an index.html page in the same folder as the leo file and it is viewable in browser. Joe On Friday, December 7, 2018 at 1:18:43 PM UTC-5, Matt Wilkie wrote: > > Wish: easy linking to specifi