Thomas,

I'm glad you liked :).

You should take a look of the Hypermedia podcast, particularly the long recent chapter about Data-Star[1]. I think it gives you a pretty broad overview of the possibilities of Hypermedia beyond its flagship tech: HTMX

[1] https://data-star.dev/

I really like the moment we are arriving now, where web development, particularly in the front-end, doesn't mean to subsume yourself totally to the "Javascript mindset" with all its technical design flaws, patchy features, gratuitous overcomplexity and so on. I imagine instead that now I'll doing web stuff, that I was thinking years ago, from my favorite computing environment: Pharo/GToolkit, with sparks of Javascript here and there, without making it or the web a "development platform" and thinking about the web more like a "exportation target".

My idea for this holidays, is to use hypermedia for creating an interactive publishing format for the data stories we have made with Grafoscopio and see if, eventually, it can evolve to a (reactive) web notebook, working on several Smalltalk variants (but baby steps, I'll jus start with the interactive publishing format). As usual, I'll share preliminary results, when I see there is an overlap with the topics discussed here.

Cheers,

Offray

On 15/12/24 12:15, Thomas Passin wrote:
Thank you for the links!  I'm just getting into reading the hypermedia book and already I can see that it's right up my alley.  I stopped working with web frameworks when they got so complex and  programming-oriented.  I'm repelled by many modern javascript practices. As I started reading the book it felt like I had finally met a kindred spirit.

On Sunday, December 15, 2024 at 10:37:02 AM UTC-5 [email protected] wrote:

    marimo looks pretty cool! and a breath of fresh air in the
    overcomplicated notebook space that Jupyter popularized. Once a
    tool(kit) like Jupyter becomes the defacto standard in a community
    (let's say data scientists) it is difficult to reimagine what can
    be done in that space. That's why seeing things like Pluto.jl[1]
    (named in the inspirations for marimo) that choose simplicity and
    reproducible flat files over nested unreproducible JSON, as a
    default for interactive computing is really inspiring.

    [1] https://cinemaphile.com/watch?v=Rg3r3gG4nQo

    In my case, after being pretty reluctant to web development
    (mainly because of Javascript and all the messiness behind web
    "standards" by committee ), seems that things like Pluto, marimo
    and Hypermedia systems[2][2a] are showing that the time to develop
    pretty interesting web experiences and publications without all
    that incidental complexity and without the JavaScript monoculture
    is finally arriving. I'll share my experiment on that front.

    [2] https://hypermedia.systems/
    [2a] https://hx-pod.transistor.fm

    Cheers,

    Offray

    On 13/12/24 18:45, John Clark wrote:
    All interested in interactive notebooks,

    Please also consider marimo if it's unknown to you.
    https://marimo.io/

    It's claim of being "the future of python notebooks" is not far
    off the mark, IMO. It is an evolutionary step beyond Jupyter in
    my estimation.

    Interestingly, the necessity for marimo to process cells
    internally in a tree-like manner similar to Leo is an integral
    part of what makes it work.

    Cheers

    On Saturday, December 14, 2024 at 2:57:12 AM UTC+11
    [email protected] wrote:

        In the same vein as Thomas, I was pushing Leo as an
        interactive notebook metasystem since years.

        I think that those aha moment would be greatly improved by
        screenshots particularly depicting the interactive story
        behind Leo usage in the scientific notebook context as still
        is not represented in a way that showcases Leo's advantages.
        I would say that LeoVue is something to imitate regarding how
        to showcase Leo (maybe because of its multiple and versatile
        web views for Leo structured information).

        Cheers,

        Offray

        On 13/12/24 8:58, Thomas Passin wrote:
        I've been trying to sell Leo-as-a-notebook for some time
        now.  I glad to see you are starting to get the idea at
        last! Remember, with VR3 you can render an entire tree
        starting with the current node; by locking the view you can
        navigate to and edit a node without having the rendered view
        jump out from under you.

        Jupyter has many strengths and capabilities that I don't see
        Leo ever getting.  Perhaps they aren't needed for your use.

        On Friday, December 13, 2024 at 7:36:48 AM UTC-5 Edward K.
        Ream wrote:

            The conversion script shows the power of Leo's scripting
            API. Here are the lines that clean newly imported files:

            def is_pure_python(p) -> bool:
                return not any(
                    line.startswith('# %% [markdown]')
                    for p2 in p.self_and_subtree()
                    for line in g.splitLines(p2.b)
                )
            ...
            # Delete the useless Jupyter boilerplate.
            for child in p.children():
                if child.h == g.angleBrackets(' prefix '):
                    child.doDelete()
                    break
            p.b = p.b.replace(g.angleBrackets(' prefix ') + '\n', '')
            if is_pure_python(p):
                # Change the language and remove all jupytext comments.
                p.b = p.b.replace('@language jupytext', '@language
            python')
                for child in p.children():
                    child.b = child.b.replace('# %%\n\n',
            '').replace('# %%\n', '')

            Disable these lines to retain two-way compatibility with
            Jupyter Notebooks.

            Onward to studying math!

            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 [email protected].
        To view this discussion visit
        
https://groups.google.com/d/msgid/leo-editor/9040e29e-f6db-451f-bf0a-251585c43610n%40googlegroups.com
        
<https://groups.google.com/d/msgid/leo-editor/9040e29e-f6db-451f-bf0a-251585c43610n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 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 [email protected].
    To view this discussion visit
    
https://groups.google.com/d/msgid/leo-editor/2cd34e05-7bea-49b7-a562-63e72a0ee5ecn%40googlegroups.com
    
<https://groups.google.com/d/msgid/leo-editor/2cd34e05-7bea-49b7-a562-63e72a0ee5ecn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/8b139386-72de-476e-aeae-417292332ef7n%40googlegroups.com <https://groups.google.com/d/msgid/leo-editor/8b139386-72de-476e-aeae-417292332ef7n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/leo-editor/5983f4ce-e93f-4f75-a0dd-eba351b969c2%40riseup.net.

Reply via email to