Launching Playdate Guides - The Everything-Written-Guide for everything Playdate Development

SDK Development Discussion
, ,
1

HI all!

I realize that there's already more than one guide out there... and having made a video guide (that's the last self-plug, I promise) , I remember the early feedback was for a installation guide in written form rather than video format.

I recently heard this suggestion again on these forums, so I went ahead and started the project: on Playdate Guides !

For now it will live in a Github repo, but likely will become an independent site if it works well down the line. Give it a star here: https://github.com/Franchovy/Playdate-Guides

I'll be creating a few guides per week at this rate, making sure that all the more complex parts of the SDK I've grown familiar with become easier to tackle! If helpful I'll be recording videos for those as well, but written guides are a good way to get more out in less time, hence my excitement around the suggestion.

I also think it will be important to showcase guides regarding common tools, such as LDtk, third-party libraries and engines, as well as different programming languages! All of which I need to familiarize myself with first before I can start posting, but they will get there eventually.

If you want to contribute, feel free to submit a PR with your own guides, or don't hesitate to contact me on Discord or visit in my virtual space!

5 Likes
2

image
image555×107 6.31 KB

Just pointing this out: no license basically implies “all rights reserved” and no one can reuse this (I’m not a lawyer though)…if you want people to do whatever they want with your code/asset you need something like the Unlicense, Public Domain, CC0 and so on :slight_smile:

3

Interesting to hear that. I won't be pursuing them, but I appreciate the pointer and will look into updating that license appropriately :wink: Thank you!

4

I don’t know if here or github (issues) would be the better place to mention this - I just started out with developing for the PlayDate and stumbled over your guides because I really prefer written guides and tutorials over video but I noticed a few issues in just the first two parts already:

One would be right at the beginning:

Then, write the following:

playdate.update()
    print("Hello World")
end

I know, basic code example. But this code runs in the update loop which should run once-per-tick, or 30 times per second by default on the console.

That code snipped doesn’t compile - it’s missing the function keyword before playdate.update() :frowning:

Second issue is in the Sprite tutorial:

Start by creating a folder called assets inside of source and adding the following image to it. (link removed because I wasn’t allowed to post with a link to github?)

The link ends up as a 404 because the entire ‘Your-first-Sprite’ folder seems to be missing from git.

I wasn’t sure if I should file a PR / Issue on GitHub so I thought I’d bring it up here first.
Thank you for making the effort to write these guides in the first place though :purple_heart:

2 Likes
5

Thank you for the feedback, and good job on the debugging! I'm gonna review both of these. Clearly need to review them more carefully before uploading. I'm very happy they came up and were useful to you!

Let me know if there's any topics you'd be interested in having covered by the guides. Happy to add to the knowledge base and to help out.

6

Fixes pushed, thanks again for pointing them out! Hope to hear some suggestions! :slight_smile: