From f11e93e3bd05d133d2b0df7dd6c4a33f4ed7fefa Mon Sep 17 00:00:00 2001 From: Ben Harris Date: Thu, 13 Oct 2022 10:07:05 +0100 Subject: [PATCH] js: Update comment on possible future enhancements Load/save has been in the JavaScript backend for a while, as have prettier controls. And JavaScript-capable touchscreens are all around us, if still poorly supported by Puzzles. --- emcc.c | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/emcc.c b/emcc.c index 06c87f4..04ab178 100644 --- a/emcc.c +++ b/emcc.c @@ -12,19 +12,8 @@ /* * Further thoughts on possible enhancements: * - * - I think it might be feasible to have these JS puzzles permit - * loading and saving games in disk files. Saving would be done by - * constructing a data: URI encapsulating the save file, and then - * telling the browser to visit that URI with the effect that it - * would naturally pop up a 'where would you like to save this' - * dialog box. Loading, more or less similarly, might be feasible - * by using the DOM File API to ask the user to select a file and - * permit us to see its contents. - * * - I should think about whether these webified puzzles can support - * touchscreen-based tablet browsers (assuming there are any that - * can cope with the reasonably modern JS and run it fast enough to - * be worthwhile). + * touchscreen-based tablet browsers. * * - think about making use of localStorage. It might be useful to * let the user save games into there as an alternative to disk @@ -35,9 +24,6 @@ * button pair. Also, that might be a useful place to store * preferences, if I ever get round to writing a preferences UI. * - * - some CSS to make the button bar and configuration dialogs a - * little less ugly would probably not go amiss. - * * - this is a downright silly idea, but it does occur to me that if * I were to write a PDF output driver for the Puzzles printing * API, then I might be able to implement a sort of 'printing'