You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(pro) less friction if the png cart happens to be amenable to conversion (no warnings)
(con) less friction; p8x8 is definitely "some assembly required", and asking the user to do some work (re-export the cart as text, using pico8 or shrinko8) seems like a good first step
(con) if the png cart produces warnings when converted, how is the user supposed to edit the cart's code? by re-exporting it as text anyway, right? most carts will require some changes -- in particular, the symbols you get in PICO-8 when you hold shift and press a letter (like btn(❎)) need to be changed
(con) extra features = extra code to maintain
if we decide to support this, we should look at shrinko8's implementation for any edge cases -- for instance, there appear to be 2 separate versions of the .p8.png encoding format
The text was updated successfully, but these errors were encountered:
should we support importing PNG carts?
considerations
btn(❎)
) need to be changedif we decide to support this, we should look at shrinko8's implementation for any edge cases -- for instance, there appear to be 2 separate versions of the .p8.png encoding format
The text was updated successfully, but these errors were encountered: