Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 18 14:36

    sbrl on master

    Remove debug logging (compare)

  • May 01 01:31

    sbrl on master

    docs: tweak language about pepp… (compare)

  • Apr 24 13:38

    sbrl on master

    Make PeppermintParsedown::extra… Merge branch 'master' of github… (compare)

  • Apr 04 15:32

    sbrl on npm_and_yarn

    (compare)

  • Apr 04 15:32

    sbrl on master

    build(deps): bump minimist from… Merge pull request #230 from sb… (compare)

  • Apr 04 15:32
    sbrl closed #230
  • Apr 02 04:01
    dependabot[bot] labeled #230
  • Apr 02 04:01
    dependabot[bot] opened #230
  • Apr 02 04:01

    dependabot[bot] on npm_and_yarn

    build(deps): bump minimist from… (compare)

  • Mar 17 03:20

    sbrl on master

    oneboxing: change to use [[[tri… (compare)

  • Mar 12 13:27

    sbrl on master

    theme blue: style onebox (compare)

  • Mar 12 13:27

    sbrl on master

    theme photo: style onebox (compare)

  • Mar 12 13:23

    sbrl on master

    theme default: tweak appearance… (compare)

  • Mar 12 02:52

    sbrl on master

    Add initial simple oneboxing su… (compare)

  • Feb 27 16:19

    sbrl on master

    docs: Update apiDoc As it turn… (compare)

  • Feb 27 16:07

    sbrl on master

    Update development dependencies (compare)

  • Feb 27 15:57

    sbrl on master

    Update dependencies (compare)

  • Feb 27 15:56

    sbrl on master

    StorageBox: Fix crash when inde… (compare)

  • Feb 27 15:35

    sbrl on master

    lib-storage-box: make more robu… (compare)

  • Feb 19 15:22

    sbrl on master

    credits: add author of latest PR (compare)

The Doctor
@virtadpt
I was thinking a different, more featureful editor than plain <textarea>. Just thinking that because I was looking into something else, and it seemed there might be a connection.
I think Mediawiki uses the Ace editor.
My use case was "I need a text editor that doesn't suck, maybe my wiki can have a nicer text editor at the same time, that way I can kill multiple birds with one stone."
Also, I was playing with Circuitpython-online-IDE earlier that day, which got the wheels turning.
vim.wasm seems way too heavy, though. It's... vim, compiled into WASM.
Codemirror (https://codemirror.net) and Ace (https://ace.c9.io) came up as perhaps having minimal suck.
Starbeamrainbowlabs
@sbrl
Ahhhh, I see
Hmmmmm
something that's dedicated to markdown would be nice
I've seen a few around
codemirror IIRC is quite heavy
The Doctor
@virtadpt
408 kilobytes, split between the CSS and the .js file. That's as big as my index.html file.
That's a no.
Starbeamrainbowlabs
@sbrl
Yep, that's a lot
it would almost double the download size of Pepperminty Wiki as a whole
prosemirror may be an option though
https://prosemirror.net/
We'd need to implement support for all the custom syntax that Pepperminty Wiki provides though
mainly the extensions to the image syntax
Starbeamrainbowlabs
@sbrl
The package comes out as ~50.9KiB, but I bet you could easily half that using Rollup + tree shaking
Pepperminty Wiki isn't kitted out including complex JS like that though
would require some effort there
oh and wow, some of prosemirror's dependents on npm look awesome
The Doctor
@virtadpt
Prosemirror looks pretty cool. The custom syntax could be implemented as a plugin for it.
Tree shaking?
Milkdown does look cool.
Starbeamrainbowlabs
@sbrl
Yeah, it does, doesn't it?
Ah, tree shaking is a technique that can be used in Javascript build systems. It analyses the code automatically and removes dead code that isn't actually used
very handy when you're using a relatively large library!
sadly implementing Rollup support into Pepperminty Wiki would be a challenge haha
so I tend to use libraries that provide a single file already built that I can include in the extra data system Pepperminty Wiki uses
The Doctor
@virtadpt
Okay. I've never heard of that before. Good to know.
That makes sense.
Starbeamrainbowlabs
@sbrl
:-)
Adding support for it in Pepperminty Wiki would mean adding a dependency on Node.js in the build system
The Doctor
@virtadpt
...huh. I thought you could just wget the .js blob it from the CDN and reference it in HTML.
That's what I did with my site's skin.
Starbeamrainbowlabs
@sbrl
Yeah, if that's possible we can do that in Pepperminty Wiki.
Not exactly like that of course, as I use the extra data function to make it such that Pepperminty Wiki does not need an Internet connection on the server to work
The Doctor
@virtadpt
That makes sense.
Hmm.
What about this: For my website themes, I check the .js that I'm using into Git alongside the rest of it, so that it's always there.
https://github.com/virtadpt/pelican-html5up-striped/tree/master/static/assets/js
I don't know if it'd be a good option, but it is an option.
Starbeamrainbowlabs
@sbrl
Hmmmm
I don't recommend checking the JS in alongside there
Rather, the gold standard is to use npm and package.json
....but Pepperminty Wiki's architecture doesn't lend itself well to that
yet
Starbeamrainbowlabs
@sbrl
Update to the Android app: full-text search support!
I've also clicked the button to roll this rewrite out to open testing
so everyone should get it after it's been reviewed and stuff
The Doctor
@virtadpt
Early access users can get it right now. I was playing with it last night, and it's really nice.
Starbeamrainbowlabs
@sbrl
Thanks!
Now I just have page history and page editing to go
both of these are unlikely to be simple though