I was playing around with version 0.7 and 0.8 Alpha, and was wondering what the difference was? Were any of the intended feature updates to the point of implementation?
Thanks for trying out LINK!
To the first question.
Drag and drop pngs or jpgs into the program was the big one.
Otherwise, mainly quality of life updates.
Wrapping can be set by resizing the note’s sides and disables it by dragging the right side all the way to left. Dragging the bottom similarly effects note resizing, particularly if you delete text.
I added a Serif font. Other ttf fonts should work just fine but aren’t supported without hacking the code.
Speaking of code, the 0.8 alpha’s source is available on GitHub if that interests you. MIT license so go nuts.
There’s probably more I’m not thinking of. I highlighted the important bits in devlogs. If I get a moment I’ll summarize other things I missed in a new devlogs, but no promises.
To the second question, I didn’t really have a clue what I was going for which is why development has stalled. Most of my plans were too far fetched and I couldn’t figure out where I wanted to take LINK next.
For the most part, LINK does what I wanted it to but it didn’t quite hit the mark.
I have an idea I’m working on. If it floats, expect to see it in The Tool Jam 2.
the idea of forking it on GitHub is really intriguing to me, however, I am an extremely novice programmer. From glancing at the repository, LINK is coded in LUA correct?
I dabbled in LUA years ago for a minecraft mod, and haven't touched it since. I am currently in college and have studied C/C++ so far, how similar is LUA to those in your opinion?
They work well together but that’s about it.
I’d always suggest someone learn Lua. I’m a little biased, but I find the language to be very easy to read while being expressive and fast.
That said, LINK’s code base is a bit overwhelming because most of the code resides in link.agpack/main.lua and I use Vim’s code folding to keep it organized, meaning sections are contained within blocks surrounded by “{{{” and “}}}”.
I use this inline style (where most of the logic is contained in the update loop) because I find it easy to add new code and refactor old code until I work out how to separate it into self contained modules (which I’ve been working on to use some of the code in my latest project).
But by all means, check out the code. Bring a notebook and feel free to ask any questions you might have. I might be able to point you in the right direction.
I’d avoid working out edit mode at the moment. It works but it’s a dumpster fire that I’m trying to deal with right now.