leojs milestone

50 views
Skip to first unread message

Félix

unread,
Jan 3, 2022, 1:03:46 AM1/3/22
to leo-editor
leojs, even if just in an early alpha stage, just got up to it's biggest milestone so far: complete outline editing commands.  (including using the 'real' system's clipboard for copy/paste operations!)

I was so excited to get it to work that i posted this without even testing it under other OSes, oh well... I'll fix it tomorrow if it doesn't work under windows, going to bed now :)
--
Félix

Edward K. Ream

unread,
Jan 4, 2022, 5:08:16 AM1/4/22
to leo-editor
On Mon, Jan 3, 2022 at 12:03 AM Félix <felix...@gmail.com> wrote:
leojs, even if just in an early alpha stage, just got up to it's biggest milestone so far: complete outline editing commands.  (including using the 'real' system's clipboard for copy/paste operations!)

Congratulations. leojs is the most important project in the Leonine world right now. I am following your progress with great interest.

What, if anything, do you plan to do about Leo's importers?  Do you plan to transliterate them? Will leojs continue to use a bridge to Leo for some commands?

Edward

Félix

unread,
Jan 6, 2022, 9:47:03 PM1/6/22
to leo-editor
>Congratulations. leojs is the most important project in the Leonine world right now. 
Thanks!! 
> do you plan to do about Leo's importers? 
Yeah, ill transliterate the importers too (probably last though)
>Will leojs continue to use a bridge to Leo for some commands?
Not sure yet, in fact I dont know yet if leointeg will somewhat be absorbed in leojs, or the opposite... 

More thoughts about leojs

- Since leojs is somewhat (in a sense) the 3rd rewrite of leointeg, and that I was learning all those APIs and code bases at the same time, and also because I write leojs solely with leointeg, I have now spotted many small bugs or annoyances in leointeg (not even all noted in leointeg's issues yet)  that I will abstain of reproducing in leojs. (and fix in leointeg later this year)

New thing I want to try out -> right after stabilizing the outline-editing that I just managed to finish last week, is the possibility of running vscode+leojs standalone in the browser :


trivial things to do 
- body pane
- find panel

non-trivial things to do
- file save/load .leo & .leojs (I'm working on this right now)
- external files / various '@'-files nodes save/load
- leoShadows for mulder algo, @clean etc...
- chapters (what even is that I never tried nor read about it lol)
- importers 
- ...?

(Djeez I should really do a project subsection like I did for leointeg at https://github.com/boltex/leointeg/projects/1 )

Please don't hesitate to comment on all that stuff! :)
--
Félix

Edward K. Ream

unread,
Jan 10, 2022, 8:31:11 AM1/10/22
to leo-editor
On Thu, Jan 6, 2022 at 9:47 PM Félix <felix...@gmail.com> wrote:

> do you plan to do about Leo's importers? 
Yeah, ill transliterate the importers too (probably last though)

I am still considering how to fully integrate Vitalije's new python importer into the main importer framework.  I'll let you know what I decide.
>Will leojs continue to use a bridge to Leo for some commands?
Not sure yet, in fact I dont know yet if leointeg will somewhat be absorbed in leojs, or the opposite... 

That's fine.  No rush.

More thoughts about leojs

- Since leojs is somewhat (in a sense) the 3rd rewrite of leointeg, and that I was learning all those APIs and code bases at the same time, and also because I write leojs solely with leointeg, I have now spotted many small bugs or annoyances in leointeg (not even all noted in leointeg's issues yet)  that I will abstain of reproducing in leojs. (and fix in leointeg later this year)

I am enjoying your corrections. Please keep them coming.
New thing I want to try out -> right after stabilizing the outline-editing that I just managed to finish last week, is the possibility of running vscode+leojs standalone in the browser :



That's way cool. It would put leoflexx.py to rest for good :-)

Edward
Reply all
Reply to author
Forward
0 new messages