This is the climax of what sox has been cooking his way toward, release by release, over the last few months.
What was once the preview tab on posts and comments is now also a what-you-see-is-what-you-get editor. Before, to add links, headings, quotes, and styling, you had to be a markdown wizard. Now, you can use a toolbar and click buttons like most editors you're familiar with.
The important part of this, and where sox put a ton of energy, is that the markdown editing experience is preserved. When editing a post or comment, you can switch between markdown and wysiwyg modes and see the changes you make in one reflected in the other. The wysiwyg, what we're calling compose for lack of a better name, is an editable preview of the markdown, and write is a editable representation of the markdown "source code" for the work you do in compose.
In many ways this is the beginning of our plans for the editor experience. It's the main way everyone makes SN what they want it to be and we want to maximize that. Before too long we'll add image resizing and, yes, a table editor, but we plan to go much further.
Sox is standing by for any bugs you find or suggestions you might have. Oh, and any complements of course.
Also, big shout to @optimism who has been helping us put the engineering back in software engineering.
Thanks @sox
Any update on the android keyboard bug 🐛
I'm investigating this now, can I ask you which keyboard are you using?
Samsung default.
(Used foss heliboard and works fine)
I see, I don't have a Samsung device right now but I'll find a way to get that keyboard and find a fix.
The problem (or the advantage, perspectives) on Android is that every keyboard can have their own IME[1] implementation, leading to bugs almost always unique to each keyboard. We're doing great efforts in trying to squash them all because we care and we're not easily comfortable in asking people to "just use another keyboard".
IME is what controls autocorrect and characters that need to be
composedlike Japanese ones ↩This looks like the cursor blinking. I'm on the Brave browser on PC.
Welcome to virtual cursors! Browsers can't normally land a cursor in "non-editable" elements, but everything in
composemode is editable ... so we fake a cursor!It can be pretty janky and to make it less janky we implemented a way to insert a paragraph if you click at the top or bottom side of an element. Let us know if you encounter any issues or odd behavior!
Oh! cool
I see 👀
I guess i could go back to a keyboard from zapstore
But i find them over customizable and I end up over complicating and cluttering the keys 🔑 😒
When I'm constructing a post, I write it out in standard notes app and paste it in
The most compatible keyboard so far is Google Keyboard (Gboard), you can try that, if you'd like, while we prepare a fix for your Samsung Keyboard.
Oh I wasn't aware of that, or maybe I... forgot, sorry.
I'll investigate asap, thank you ^^
> Also, big shout to @optimism who has been helping us put the engineering back in software engineering.
In what sense?
Also, good job!
Generally, he's been pushing for more rigor in dev processes and alerting us to how accessible rigor is now.
Haha, maybe I should ask him a crash course on this too. We lack a lot of rigor in academic coding...
I've kind of gone the other way. I used to spend a lot more time making my research code elegant, extensible, and modular.
But I realized that I rarely benefitted from it, since the requirements of different projects are often so different.
So I'm much more comfortable slapping together code that just gets the job done now. For my research work, at least.
I think that it only makes sense in production code. I basically have 4 levels of rigidity:
I guess I rarely venture outside of 1 and 2 with my codes. I do have a FOSS code that I maintain and build on regularly, and collaborators are free to use it, with the huge caveat that I am not responsible for any errors in the code. They are also free to modify it, but they rarely do, as most are allergic to Fortran. And it's very much spaghetti code that I've only recently started to refactor using Cursor.
Yes. So don't waste too much time. For your refactoring, especially in fortran, I'd go the way of 3, simply because you don't want to introduce sloppy architecture.
I posted a bit about this process yesterday, in #1452429.
If your software were something like openssl or the linux kernel or in general something considered best in class and has gotten a couple 100k installs, you want to be extremely careful. This is what 4 is for.
@south_korea_ln how's the weather, in any other language?
If you detail your frustrations or questions in a post, you might be so lucky.
please forgive my usual obnoxious change of topic:
is the site's API documented anywhere, in dead documents, infinitely friendlier than "use cursor bro"?
No personal offense intended to you, nor to any of the good folks listed by
git shortlog, but I'm terribly sick of relearning websites at the speed of the vibe.We're behind in documentation, also because we're trying to ship at the speed of light.
For example, the editor has a somewhat extensive documentation focused on its inner workings and how to build for it (also really great for
use cursor bro), but it's not updated and some things have changed.I'm personally glad that
composemode is not collapsing in on itself like a dying star, so now I can prioritize stuff like documentation.tl;dr I agree that documentation is a serious matter, especially now that the codebase is bigger than ever. I'll make an official issue on github.
"shipping" culture is worse than ebola
:+1:TIL we have one already: https://github.com/stackernews/stacker.news/issues/1089
I actually agree, it is worse than ebola. We have a lot to do though.
"cathedral" spires rise higher than "bazaar" tents not because people consider clowns and the circus a joke...
gaudi survives longer than tupac.
Ahoy hoyTest test Good stuff guys
Vs. This
And
the other thing I.vibedI'd say it's perfect! Nice work!!
Yooo
been working so well for me - yay @sox way to go
Thank you!! I think you'll love what's coming next.
i wrote this comment in the
wysiwyg.i think it is pretty cool.
well done, @soxwell done, @sox
reallycool.
double click
could you please describe how the "caption" is relevant? [yes, I realize you didn't deliberately make it so the words "double click" are caption, or alt text; however the quote above is how your comment looks when disabling automedia]
Now you’ve got a good challenge here!
Probably very naive question...
This seems like it has been quite the work and endeavour. Yet, I'm surprised that's the case. Isn't an editor like the most common thing in online platforms? Aren't there out of the box solutions that achieve what you want, with extreme levels of customisation?
Or are those mostly crappy and not to SN standards?
Genuinely asking, I'm sure there is a reason @sox put so much time and love in this.
We are using what most people would consider an out of the box solution - and some people ship to customers as-is.[1]
The problem with most editors is that they tend to do one thing (markdown) or the other (wysiwyg) to an okay degree, but none of them do markdown and wysiwyg compatibility to this degree. (Try using any other website's hybrid editor, doing some ambitious styling and switch back and forth between modes.)
In the hopes of protocoling SN someday, we want to keep markdown as the base encoding of content here. Yet, in the interest of helping folks from any walk of life participate on SN, we want to make adding nice content to SN easy.
Yes. Do you have one you love the most and wish it were everywhere?
All of this work is the extreme customization part of an out of the box solution. Our customization needs just go beyond add new styling options.
We have bugs fixed in our editor that even Facebook hasn't fixed in their products yet, and they are the ones working on the underlying library. ↩
do you realize that "office" has been keeping microsoft afloat, while games and cloud services are a rounding error?
market capture of windows users is not because of paint and pinball.
changing the toolkit for bringing the UX mockups to life does not make the problem any easier, and honestly, HTML5 is no lighter a nightmare than the previous prototypes.
Whoa cool.
What would you say are your biggest roadmap priorities now?
For the editor or generally?
Generally.
User facing:
zapping meaningfully takes too much time, relative to the baseline of "would I complain if the polite european tourist stopped rounding tips"
edited to comp the editors; added
$$meaningfully$$[an extra format "inline mathematics", hiding behind the ellipsis]Ngl SN increased my markdown skills haha
But this tool bar will be very welcomed
Awww shewt I got underline now!! Formatt junkies unite!
sox cooked
Huzzah!
Amazing work @sox!
# congrats ~lol nice job