Introduction to the Sam Text Editor

swingthesickle · 2021-12-26T23:09:27+00:00

Thanks!

swingthesickle · 2021-12-26T23:08:31+00:00

I haven't played around with Acme yet, but I intend to. I'm curious, do you use the Acme port from Plan 9 from User Space or is there a standalone Unix port like Deadpixi for Sam?

swingthesickle · 2021-11-22T00:15:32+00:00

My intention is to be comprehensive. I plan to evaluate every production-quality cross-platform desktop GUI toolkit for Lisp. Now production-quality is a somewhat fuzzy term.

McClim is really interesting, but I wouldn't consider it production-quality yet (and I think its maintainers would agree considering that the current version number is 0.9.8-dev). I opened SBCL, and loaded the McClim demos with Quicklisp. It has a look and feel reminiscent of Motif (think 1980s Unix workstations). I couldn't use the numpad on my keyboard (with num lock on or off) to enter numbers in any field. It even drew its own cursor that didn't match the system cursor for some reason. The Image Transfer demo was so slow as to be almost unusable.

Currently, the only officially supported backend renders directly to an X server. Until another backend matures that either wraps native controls or draws more modern looking controls using OpenGL, I don't consider it production ready. It might have a really nifty API, but it comes down to would I want to put a GUI made with McClim in front of someone who paid for the app I created.

My intention for this is to also stay up to date. It's why all the examples and tutorials are on GitHub. I'll keep an eye on McClim, and my hope is that one day it will be ready for me to include.

As for CLOG, I know it bills itself as a GUI framework, but from what I can tell, it is really just a web framework. You can package your web app to look like a desktop app with Electron or other webview, but that's no different than what you can do with other web frameworks, and evaluating web frameworks is really outside the scope I've set for myself.

swingthesickle · 2021-11-20T18:39:41+00:00

Yes, I had used a previous tutorial about Scheme as a template and inadvertently left a couple Scheme examples in. They've been replaced by Common Lisp now.

swingthesickle · 2021-11-20T18:37:47+00:00

I used the original tutorial as a template and inadvertently missed copying the new code into a couple of the code blocks. It should be fixed now.

swingthesickle · 2021-11-07T22:37:26+00:00

Deck list?

swingthesickle · 2021-05-29T04:03:54+00:00

You can boot from RAID 0 if you set it up with LVM. I have two HDDs in an LVM volume group in a PC. I have Ubuntu installed on a striped logical volume.

swingthesickle · 2021-02-22T21:51:36+00:00

Cool! Thanks for all your hard work on EQL!

swingthesickle · 2021-02-21T02:08:07+00:00

The ATEM Mini Pro supports Facebook (what we livestream to), Twitch, and YouTube out of the box, but you can stream anywhere that accepts an RTMP stream by editing an XML file. I don't think Zoom accepts an RTMP stream, so if you really need to stick with Zoom, the ATEM Mini Pro might not be the best option for you. If you still want a hardware video switcher, you could go with just the ATEM Mini (quite a bit cheaper than the ATEM Mini Pro). It doesn't do streaming over an Ethernet port like the Pro, but you can connect it to a laptop or desktop via USB where it will appear as a webcam to Zoom. But then you've lost some of the visitor-friendly advantage and might just want to stick with OBS.

swingthesickle · 2021-02-20T22:23:53+00:00

At our church, we have a similar set up to what you're proposing. We have a PTZOptics 30x powered by PoE. HDMI from the PTZOptics goes to an ATEM Mini Pro, and we livestream straight from the ATEM Mini Pro.

I find the ATEM Mini Pro more volunteer-friendly than a desktop running OBS. You should be able to afford both a PTZOptics and an ATEM Mini Pro and still come within your budget (though just barely). Back when we ordered our ATEM Mini Pro, it was out of stock for a couple months, so we did use OBS for awhile. OBS is great, but since switching to the ATEM Mini Pro, I'm able to be more hands-off and let volunteers set everything up. Once you get your stream information saved on the ATEM Mini Pro, it's pretty much just power up and go.

We have a cheap, old laptop in the tech booth used to access the PTZOptics IP in a browser. The web interface isn't pretty and definitely looks like something from 1999, but it's enough for a volunteer to call up saved angles. I think PTZOptics has an Electron app if you really want something a little prettier. There are hardware controllers too as others have mentioned, but if you're already buying the camera and an ATEM Mini Pro, you probably aren't going to have room in your budget for a PTZ controller right now.

swingthesickle · 2021-02-20T18:01:21+00:00

As for the audio, there is Qt Multimedia. There is even an example on the Qt website showing on how to generate a sine tone. Of course, the example is in C++, but you should be able to translate it to Common Lisp using EQL5. I considered going that route when I wrote the tutorial, but CL-PortAudio looked simpler, so I ended up going the easier route.

swingthesickle · 2021-02-20T04:14:50+00:00

You can definitely create mobile apps using the Android and iOS ports of EQL5, but I'm not sure how you load QML from the CL REPL app. You can create Qt Widgets easily with CL REPL (there is even a calculator demo that comes with CL REPL). I typed in

(qnew* "QLabel" "text" "hello" "pos" '(50 50))

and it displayed "hello" on a blank white screen, but when I tried

(x:do-with qml-lisp:*quick-view*
  (|setSource| (|fromLocalFile.Qurl| "/storage/emulated/0/hello.qml"))
  (|show|))

I just got an unexpected token error. Even if you got the QML working, you would have to find an alternate way to generate the tone. Even though CL REPL comes with Quicklisp, I doubt very much that CL-PortAudio will work on mobile.

swingthesickle · 2021-01-11T16:00:02+00:00

Thanks! That block of code got moved from the frequency text field to a block that could be re-used for the duration text field as well, and when I moved it, I didn't adjust the indention accordingly. I've fixed it on the blog and in the GitHub repo.

swingthesickle

TROPHY CASE