import

[jeffXvX]

Import puzzles from csv or JSON format. It may be easier for folks to use Excel or their own editor rather than the interface on our app

[tme321]

I understand the desire behind this but it brings up 2 points.

1. I need a better target than "csv or JSON" to import. We would need to define what formats are importable. For instance, if it's csv does that mean csv with a comma between each puzzle line and a newline between each entire puzzle? If importing is a feature we need to decide what the imported data needs to look like.

2. From a bigger perspective the issue could simply be our current interface. I am open to ideas about changing it. The way I've created this entire app means the interface is completely decoupled from the logic. So it's actually trivial to change the interface and still have all the underlying logic "just work". I'm open to other ideas about how the interface should work. I'm not opposed to allowing importing but maybe the first thing we should do is look at the current interface and iterate on it instead of immediately just accepting that the interface is bad and supporting importing? That doesn't mean we couldn't still also support some form of importing. But if the interface is unusable then I think we should at least attempt to fix it first before resorting to just designing the program around importing the data.

[jeffXvX]

1. I currently have the format of a semicolon between lines and a newline between each puzzle. But a comma would probably make more sense and it's easy enough for me to change what I have now

2. The interface isn't unusable, it's just that for very large amounts of data, I find it easier to use something like Excel because (1) I can paste an existing list into it; (2) spellchecker; (3) can search to see if i've already entered a puzzle in; (4) interface is more polished; (5) i can enter data much faster.