-
Radiance Release - Confession 73
2017.04.07 09:11:04
Right now I'm at Brussels Airport, waiting for my departing flight back to Zürich. The 10th European Lisp Symposium is over, and I got to have my first “real” talk at it. It was, as you might guess, about Radiance and some of the core concepts behind the project. With that, I think it is finally time to announce Radiance's proper release into the wild!
-
It's Been So Long - Confession 71
2017.02.09 23:56:12
It's been a good while since I last wrote an entry. I didn't write anything all January for a multitude of reasons, at the forefront being that it was exam season again. That's over with now, fortunately, so I do have some more time on my hands to goof off. Unfortunately though, I only have one more week left of this precious “free” time before university strikes me in the back again. I best use it wisely.
-
Radiance - An Overview - Confession 70
2016.10.30 15:11:09
It's been a good while since I last worked on Radiance. Unfortunately I can't claim that this was because Radiance was completely finished, quite far from it to be truthful. However, it has been stable and running well enough that I didn't have to tend to it either. In fact, you're reading this entry on a site served by Radiance right now. Either way, thanks to some nudging by my good friend Janne, I've now returned to it.
-
The Road Onwards - Confession 46
2014.12.28 23:56:57Just yesterday I finally finished the last big problem that plagued Radiance since its conception. Actually, the issue dates even further back all the way to when I started TyNET, since I never really did solve it until now. Though the main reason for this long delay is that I wasn't completely conscious of the issue until about half a year ago. For better or worse, things worked just well enough without absolutely having to solve it. But, ever since I grew aware of it it has been a thorn in my side as I couldn't figure out how to elegantly solve it.
-
Digging for Resources - Confession 44
2014.12.11 22:07:44In order to ensure that writing modules is easy and doesn't result in spaghetti sauce spilling everywhere, Radiance has rather strict encapsulation rules in place. However, since modules also need to be able to interact in some form, be it due to extending or sharing functionality, we need to offer some kind of interface to exchange data between them. If possible in a well-specified manner.
-
Building the Framework - Confession 43
2014.12.01 10:18:18Last time we took a quick look at how authentication and authorisation work in Radiance. However, in order to avoid a kludge in Radiance I had to resort on a bit of a hacky way to let you authenticate yourself. This time we'll work out our own solution to the problem.
-
Brushing Things up to Shine - Confession 35
2014.09.27 08:45:10Continuing on from last time, we'll now take a look at users, sessions and authentication. Starting out the most obvious deficiency in our twatter application is that anyone could post as anyone.
-
More Radiation - Confession 34
2014.09.21 14:01:01I was bored enough to implement the SQLite bridge for Radiance last week, so I'm now ready to share another quick looksies into some more of Radiance's ecosystem with you. This time we'll have a first gander at the interfaces system and database interaction, an important component of many an application.
-
Starting With Radiance - Confession 33
2014.09.15 14:38:16This is a bit of a difficult entry to write for me, mostly because I don't want to give the impression that Radiance is finished. So first of all, here's a big disclaimer: What I am about to show might change radically in the future as I iron out flaws in the design of Radiance. Nevertheless, I hope it serves as an example and insight to the basic principles employed in Radiance's structure and workflow.
-
Routing - Confession 30
2014.08.26 19:46:13No, this blog is not about another ISP issue, but rather about the issue of routing in the context of web frameworks. I've mentioned this problem briefly before. The first question that needs answering in order to solve this problem is this: What does routing even need to be able to do?
-
Radiance2 - Confession 28
2014.08.20 20:54:18I suppose it's time I talked about this since Radiance2 is now actually live! Well, at least it's partially live. The blog, as you probably noticed, got a significant overhaul both design and software wise. Plaster also got upgraded, since that was the only component that Radiance1 really had running.
-
Radiance? - Confession 14
2014.07.21 12:23:30When I initially picked up Common Lisp my intention was to rewrite TyNET in it, with the focus on making a properly usable and extensible web framework that other people could profit from as well. And while that did indeed happen to an extent it was not satisfying to me and I felt like the old approach of just going at it would not yield respectable results.
-
Building TyNETv5 Pt. 14 - Human Interface
2013.09.01 00:34:32As promised last time, I took a look at the framework and thought a bit about what I actually wanted to write in the end, versus what I had to write in actuality to achieve the same goal. I didn't think of writing a blog at the time and so I already moved on a bit from there. I'll try to recount the issues I've located even if it has been a while now.
-
Building TyNETv5 Pt. 8 - Initialize!
2013.07.01 22:17:40About high time I write a blog post about this stuff again. Apologies in advance if I sound angry or in any way derogatory about things, I'm currently not in a very preferable state of mind. Still, Imma do this because then I'll at least have done something today. So, what's this all about then?
-
Building TyNETv5 Pt. 6 - Intermission
2013.06.23 20:28:45As I was preparing lQuery for release today I noticed that I still needed a couple of other things before I was ready. One of those things was that my base syntax macro was actually not working properly (variables weren't being handled right), so I had to spend quite some time rebuilding and debugging that. Then I realized that I wanted to have a proper documentation of all the functions ready for release. Since I'm lazy and a programmer I thought I'd use lQuery to write a library that automatically generates HTML documentation files for a given package. This turned out to be a tad more complicated than I initially expected, so I couldn't finish it today. And that's basically why lQuery is delayed, oh no!