-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull data from Google Sheet #38
Comments
The desktop version of Cider supports writing to a project directory. In there all the card listings are saved as .csv files. Those can be opened up in any .csv editor like Google Sheet for editing. Once the project is reopened in Cider, it will pick up those changes. Ex. project structure: https://github.com/oatear/cosmic-apple-game So far my thinking is that tracking changes to a project and tagging versions is much easier and more robust if you save your project into a repository than to track separate files in Google Sheets. I will continue to reconsider it. I originally segregated each deck to have its own assets. That was not a great experience when having to re-upload the same images for symbols used in different decks. I will think more on the multiple folder idea. There is however benefit in having a flat map of all the assets as they are available on one table and can be searched and filtered. Its also easy enough to hierarchically name the assets, ex. icon-health, feature-potion, location-forest. |
It would be great if we could store/pull data for the cards from a Google Sheet (public available url of course). There would be less need to implement a lot of sophisticated features in the data editor if this was possible.
It would also be excellent if we could point the assets at at Google Drive folder (or other cloud storage). Using the filenames as the names. Right now, it seems the assets are the same across any deck, which doesn't seem correct unless there is more of a distinction between a project (with one or more decks) and a deck. Similarly, there is no ability to have a folder to organise assets (like one folder for icons and another for feature art). The ability to link to a google folder (and maybe cache it) would make all of that much easier.
The text was updated successfully, but these errors were encountered: