@JakAttak - lol, you can’t win them all. I know what you mean, there are some things my brain wasn’t built to understand. #-o
@JakAttak you don’t need to fully understand the pipeline or anything like you just need to think it as a grid of colours for the fragment shader, and almost like a vertex manipulator for the vertex shader. It’s not hard, although it looked almost impossible when I started them. Still does in places mind you…
The user and all related content has been deleted.
Codea and LUA are truly interesting, though it is a bit hard to learn, at the end if you can do the job, you are rewarded with hours of fun. After all there is nothing like creating something. And it’s probably best to stick to Codea’s example projects, tweaking the code here & there a bit and watching the results. And the AirCode feature in Codea is a lot of help - write some code and see the effects instantly, so if there is a mistake in your code you can instantly rectify it. If you make mistakes while normally writing on your iPad, the compiler won’t let you through unless you write it correctly, AirCode only executes all the correct part, so if some wrong code is written, there is no effect, so you instantly understand that your last line was wrong and can change it or remove it.
@Ignatz eBooks are truly helpful.
I mostly learned by trying and modifying other people’s scripts (I started on a game called powder toy that has a Lua API)
I learned with Codea, just playing around
@Ignatz great books! Thanks so much for them.
I learned Lua by the in app CODEA references (Love the Lookup selection, wish Search was on same popup menu), the Lua.org references, and forum examples.
I started programming in 1963 in IBM 7090 assembler, FORTRAN and CDC 1604 assembler. Did a bit of Pascal, PL/1, VB, C# over the years. All this experience helps learn new stuff.
But I find CODEA and Lua have been the easiest to learn and the most fun to use.
For those of you who have kept up with my CODEA Enlightenment project, my aim is to make learning from forum and GITHUB examples as easy as possible.
My intent originally was just to make it easy for me to learn and reuse other’s code.
Thanks to everyone who has helped produce this great and very useful product.
Isn’t this a really old post?
@Saturn031000 Just because a discussion was started a long time ago, that does not mean the content is no longer relevant nor additional posts bad.
I’m still learning. There is so much… <:-P
This raises an interesting point. In the past the mod team have seemed to be quite strict about not reviving very old threads. I can see why that could be annoying if the thread is on a long-depreciated feature, or a bug that was squashed ages ago, a workaround that’s no longer needed etc. But aside from those cases, is the no-bumping-old-threads “rule” necessary? When you click a thread, it shows by default #latest, and the posts are all clearly time-stamped, so I don’t think it’s particularly disorientating when an old thread comes back. And it might encourage people to use the discussion search feature more, if they knew that the results were not just “read only”. But what do people think?
It’s a matter of judgement. Some old threads are clearly finished, others like this one are open ended.
I learned some basic syntax (sprites and a ton of if statements) and then just fooled around until I had a game. I kept coming up with newer ideas and just learned new stuff as I needed it with help from the reference or forums.
for what my opinion is worth (not much) i am very much on the ‘let them live’ side, so i dont like when people make hard comments about poping up old threads. If you dont like them, just let the thread sink again. And if people keep commenting into this revived thread, well, that means there is a need for that.
@Jmv38 this is the only proper way, users won’t keep an old thread up if the content is bad or irrelevant like some, but either way, it’s nice to keep some form of talk flowing.
where can I get Lua for beginners.pdf ?
@bellboymartin I’m not sure if there’s a beginners pdf. The way I learned Lua was to look thru a Lua reference or the Codea reference to see what some of the commands were. I would then write simple programs just to see what the commands would do. I would modify thing to see what would happen. If things got confusing, I would ask questions or look for examples of code. The programs started small, but got larger as I learned more. So, if you have any questions or you would like to see a specific example of something, just ask. Everyone here will help, you just need to ask.
Pretty much trial and error… but after Pascal, Basic, Java, TMS9900 assembly, C, C++, Java, JavaScript, VB, Ruby, they all start to look sort of alike. There are things I love about Lua — collections. And things I hate — also collections. I seriously appreciate that you can trust the string handling. Recent coding on microcontrollers has reminded me of the hair-rippling experience of dealing with C string libraries (don’t, just don’t).
Don’t discount the example code. It’s fantastically valuable for “how’d they do that?” moments.
Don’t know lua just what parts are in codea.
Hey, a full learning resource for lua is being written over at https://luascript.dev/learn it’ll reach you step by step not just how to write lua, but how to code from the ground up. No experience needed and, it’s completely free