5 ms·
I'd love to give it a try. However, Pharo still doesn't run out of the box on my Fedora system. It used to work, up to Pharo ~5-6, then stopped working altogeth
by klibertp 4y ago
I'd love to give it a try. However, Pharo still doesn't run out of the box on my Fedora system. It used to work, up to Pharo ~5-6, then stopped working altogether. There's little documentation around installation and even less info on troubleshooting. I'd love to like Pharo, but it simply doesn't work, and nobody cares :( From my memories of it, even when it was still starting properly, it worked... Well, some of the time. Resizing the default font killed the looks of all UI elements, for example.
It's all fixable with enough time and effort, no doubt. Unfortunately, I don't have that kind of time on my hands anymore. I'd love to see and use all the new shiny tools developed in and for Pharo, but - even if it started working again - I don't have the time to read all the code and piece the puzzle together on my own. Some kind of documentation would be nice. Hopefully, included in the distribution. No such luck as far as I can see.
So, even knowing that I'm missing out on some really cool things, I recently switched my Smalltalk development to Cincom® VisualWorks© Smalltalk (I hope I got these Rs and Cs right...) It's a version from 6 years ago at this point and partially closed-source, but it's rock-solid and stable, very well documented with thousands of up to date (easier to provide when you're working with a stable system) pages in PDFs, with guides and references; comes with a lot of goodies and working, well tested support for namespaces, inner classes, visibility modifiers for classes, extended streams (though they're closer to RxJava than classic streams, and I didn't like them very much), some other language extensions (no traits though), the GUI painter, and so on. And all of that works, even if some of it looks less glamorous then the screenshots presented here, which are all I'll ever see of this toolkit until Pharo starts treating users with a bit of basic respect.
I have a blog post about making VW IDE a bit prettier - just look at the screenshots: https://klibert.pl/posts/smalltalk-ide-quickfix.html https://klibert.pl/posts/smalltalk-ide-quickfix.html - yeah, it looks so last-gen, right? I know. But it works. And it survived like 3 system upgrades, 1 reinstall and 1 fresh install on a new laptop without issues. If only Cincom was more flexible when it comes to licensing the commercial version!
- tudorgirba 4y agoGlamorous Toolkit build the VM differently from Pharo. Please give the distribution a try: https://gtoolkit.com/download/ https://gtoolkit.com/download/
- klibertp 4y agoOh, OK, I'll try. Thanks for letting me know! :)
- klibertp 4y agoIt worked! Not sure why or what's the difference, but Pharo downloaded from here: https://pharo.org/download https://pharo.org/download still doesn't work - it opens a window but never draws anything in it, it's stuck showing whatever was below it and never updates.
- tudorgirba 4y agoGlamorous Toolkit is based on Pharo, but it is a separate project with its own build system and even graphical stack. I am glad it works for you. Feel free to ask questions.
- infinite8s 4y agoWhat is the main difference in your build approach? Are there any major changes to the underlying VM?
- tudorgirba 4y agoIn GT, the Pharo VM is like a library, not the main executable. We have two threads: one that runs the UI rendering and one that runs the Pharo image. Also, our build infrastructure is coded in Rust, and all VM libraries we create are written in Rust as well.
- infinite8s 4y agoAh so is the UI written in Smalltalk? Or Rust?
- tudorgirba 4y agoThe low level rendering is handled through Skia and it's hosted in windows handled by Winit. But all the high level model is in Smalltalk.