Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thanks for the reply, and am looking forward to the bug fixes.  I'm not much on feature requests in general for small projects as usually the designer already has a roadmap, etc. and makes adjustments based on real world usage, etc.  BUT if you EVER run out of ideas, just say so, I think a couple of us may have some...like pressure sensitivity with the pencil tool and it's various 'nibs'/brushes, but it's also something I could probably make myself if there's already way to detect pen pressure....

Right now, I'm still in the experimenting and exploration stage, so I probably shouldn't be asking too many questions just yet.  :)

I did have a non bug question and more of a question about LIL.  I noticed some of it's syntax looks like SmallTalk.  Is it in any way related and did that influence the decision to use it (aside from it's small footprint)? I didn't know if you were going back to some of the influences over Hypercard in this '2023 Remix' version and was just curious.  

Okay, back to decking the halls of my cards with cool stuff.  

There isn't currently a way to detect pen pressure, (it's a bit difficult portability-wise) but it is possible to define custom brushes that respond to the speed or direction of strokes- see the "brushes.deck" example deck.

Lil was designed and written for Decker; the platform and the scripting language co-evolved. There's no deliberate influence from Smalltalk; Lil is primarily aesthetically influenced by Lua (which is popular for beginners) and semantically influenced by Q (which contains many powerful ideas, especially its vector-oriented and database-related functionality). I have a background working with APL-family languages, and Lil is an attempt to surface some of the same expressiveness and design philosophy in a more approachable package.