Log In  

The idea behind PICO-8 is pretty amazing in that you can make the games in the same environment you play them in. The pico-8 webpage itself says, and I quote: "Create a whole game or program in one sitting without needing to leave the cosy development environment"... except if you wanna look at the docs, then you gotta do awkward switching between a text editor and the pico-8 environment. Thus, I think the documentation should be embedded into the IDE. On a second note, trying to find any particular function in the docs is not a fun experience. For example, if I want to know what arguments "print" takes, I have to search the readme file for "print" (of course), but there's a ton of references to the function before the actual documentation for it, which means I have to go over all of them before I find the actual line which explains what the function should be called as. It could be nice to have the usual thing for function documentation in the IDE -- you type the name of the function in your code, hit F1, and it shows the reference for this particular function. I know that pico-8 is still in alpha, but I feel like this is one feature that is a must-have for comfortable development.

P#33702 2016-12-19 10:15 ( Edited 2016-12-20 19:56)

:: enargy

Nice suggestion for built-in documentation.

One tip, if you want to look up parameters for a built-in function, try searching "[NAME] " instead. For example, "rect ". This should limit your results a bit.

Also, this cheat sheet/wiki is pretty helpful: https://neko250.github.io/pico8-api/

It even includes some of the non-documented features, like grabbing mouse inputs.

P#33707 2016-12-19 10:26 ( Edited 2016-12-19 15:26)

I really want it all in the paperback form with the plastic comb binding, a la this classic.

P#33711 2016-12-19 10:49 ( Edited 2016-12-19 15:49)
:: tlm

Hah! That is a fun idea, miscbill. Printing it out would probably help somewhat.

P#33712 2016-12-19 10:53 ( Edited 2016-12-19 15:53)

@miscbill: Oh wow, I remember that dog-eared book! Sadly, I was probably too young (and impatient) to make the full use of it, back in the day.
But that's the beauty of PICO-8; the simplicity of BASIC, but the power of SO much more! :D
Count me in for a plastic-bound PICO-8 Programmers Reference! ;)

P#33720 2016-12-19 12:59 ( Edited 2016-12-19 17:59)

Also don't forget the wiki, which has a thorough API reference organized both by category and alphabetically:


I've looked into doing a comb-binding manual for Pico-8. Full color is expensive, and nobody offers comb binding and full color together with print on demand services. So it'd probably be a limited bulk print run and a fulfillment service of some kind. Maybe next year. :)

P#33723 2016-12-19 15:40 ( Edited 2016-12-19 20:40)
:: Offler

@Tim I agree completely. Pico-8 would feel more complete with built-in documentation. I usually program on my PocketCHIP so I never leave pico-8 (except for looking at the printh output).

It would be fun to make a cart to show the idea and hopefully inspire Zep to add this to pico-8.

P#33726 2016-12-19 16:35 ( Edited 2016-12-19 21:35)
:: Stompy

Someone could make a documentation cart, but i don't think adding this to the console is in fitting with the minimalist ideas

P#33745 2016-12-19 23:15 ( Edited 2016-12-20 04:15)

I dunno, I feel like it fits fairly well to have onboard docs; the self-contained nature of the system is one of my favorite things about it, thematically.

If you need a lore justification, the idea that the docs are stored in a firmware utility chip on the motherboard of the console itself would justify having the information sitting around and readable without otherwise compromising the constraints of the cart system itself.

P#33782 2016-12-20 14:56 ( Edited 2016-12-20 19:56)

[Please log in to post a comment]

Follow Lexaloffle:        
Generated 2020-06-02 20:15 | 0.023s | 2097k | Q:30