CSV entries for target zone settings rather than settings.json #17

Closed
opened 2015-11-01 15:31:34 -06:00 by mattbk · 4 comments
mattbk commented 2015-11-01 15:31:34 -06:00 (Migrated from github.com)

It would be easier for people to input target zones in a CSV file in Excel than in a JSON file.

It would be easier for people to input target zones in a CSV file in Excel than in a JSON file.
mattbk commented 2015-11-01 20:53:08 -06:00 (Migrated from github.com)

JSON is touchy.

JSON is touchy.
mattbk commented 2015-11-02 08:22:05 -06:00 (Migrated from github.com)

The easiest way might be to split this off into a separate JSON file. Leave other settings in settings.json, but build a new targets.json file that is created from CSV using something like http://www.mybelovedphp.com/2013/10/16/converting-csv-to-json-with-php/.

That way we don't have different types of information in the same JSON file.

The easiest way might be to split this off into a separate JSON file. Leave other settings in settings.json, but build a new targets.json file that is created from CSV using something like http://www.mybelovedphp.com/2013/10/16/converting-csv-to-json-with-php/. That way we don't have different types of information in the same JSON file.
mattbk commented 2015-11-02 12:09:22 -06:00 (Migrated from github.com)
This will help me test: http://www.convertcsv.com/csv-to-json.htm
mattbk commented 2015-11-02 13:02:55 -06:00 (Migrated from github.com)

image

Structure will be different in JSON, hopefully won't result in too many changes.

![image](https://cloud.githubusercontent.com/assets/3729038/10891163/f4ac19ee-8161-11e5-82e0-639bc8f092a9.png) Structure will be different in JSON, hopefully won't result in too many changes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: matt/changeblindness#17
No description provided.