I used, or at least tried, all of the solutions on the Codea forums for backup code. Some of them are really inspiring and comfortable to use. But I needed something more barebone, more lightweight - more K.I.S.S. Something that is as easy to use as it is fast and decent.
I was thinking for a few days on how I could implement it (from the design point of view). And the most simple thing, that came to my mind, was a slider. No fancy buttons or deep, complicated menus. No time-wasters and eye-destroyers. Fast and efficient!
* Copy code from Gist. Paste it into a new project (long-press on the big +).
To use, just add a dependency inside your project (+ sign in top-right corner).
No fancy buttons or deep, complicated menus. No time-wasters and eye-destroyers. Fast and efficient!
is great! But once you have made your backup, you need to add this functionnality. And this one. And that one too. Etc, etc… and before you know it, you’ve made deep, complicated menus!
@Ignatz unfortunately CodeaCommunity crashes my Codea very often. I don’t know where the issue lies. And I dislike the additional ccConfig tab… It’s all useful and has its purpose, but Also adds a certain level of complicity and overhead, which you additionaly have to manage.
@Jvm38 What would you need to add after you made the backup? Sorry I’m not sure I understand you correctly.
You actually slide right and the backup is done. then you can just go back to the editor and resume working. Messed up? Slide left and restore a copy.
@se24vad maybe i am too doubtful, i’ll be glad to head from you about this in a couple months from now, and see if you have sticked to this version. Let’s see where it goes. Very nice work anyway . @ignatz i am worried about the savelocaldata… how is it managed by codea? does it get removed when the project is deleted?
@se24vad Cool light weight backup utility! I’ve been addressing your concerns with CC. I’m re writing it from the ground up. It’s modular based so all you really need is the core which connects. You can then hook the different events and handle it as you please. This will allow for the expanded use of CC including a simple backup on the cloud.
This project aims at someone who is working on a private project, which doesn’t get shared (until its done, at least). While experimenting, you like to save some progress now and then. Quickly. While having some overview of what you have laid by side. At least I feel like this when prototyping and testing ideas.
The backups are project specific. And after the job is done, you wouldn’t need all those backups anyway. - That’s why I decided to go with saveLocalData instead of Dropbox, Documents, Images or all the others.
Sure, CodeaCommunity is head and shoulders better, but ‘beating’ it wasn’t the goal of this project anyway. There are a ton of solutions. This one is just one of them, which I wanted to share, as a ‘Thanks’ to the vibrating community and its helpful people.
@se24vad it’s going slowly because I’m completely rewriting the client. The core of CC simply connects and triggers the connect event. After that the standard CC modules can be used or you can load your own. It’s using preset triggers that the modules listen for and react accordingly. Each module, if you chose, can add params to the config or you could write your own project loading system and bypass the config. Each module is stored in documents and has the ability to update itself if the author of the module updates it. So CC can have each module update independently without the need to update cc.
I decided to do this to make it easier for me to manage the project and I’m hoping there are at least a handful of people that would like to write their own modules and share them with the community. This will result in still having a single place for people to share projects, but allow different backup and restore needs based on taste.
Very interesting…