Talk:Develop: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Paulswartz (talk | contribs) No edit summary |
||
Line 15: | Line 15: | ||
:I think that for now, keep should bundle up the whole activity. It should automatically do a keep when first started on an activity. When restarted with a bundle, it should check that there is an older bundle of the same activity. If there is, it should overwrite the activity in the unbundled directory structure; if not, it should do a "copy of"-type renaming. To export individual files for editing, there should be another button, not "keep". [[User:Homunq|Homunq]] 12:43, 5 February 2008 (EST) |
:I think that for now, keep should bundle up the whole activity. It should automatically do a keep when first started on an activity. When restarted with a bundle, it should check that there is an older bundle of the same activity. If there is, it should overwrite the activity in the unbundled directory structure; if not, it should do a "copy of"-type renaming. To export individual files for editing, there should be another button, not "keep". [[User:Homunq|Homunq]] 12:43, 5 February 2008 (EST) |
||
:Right now, keep just saves all the files. I like the idea of Keep bundling the Activity into an .xo file; but then what happens when we resume? We're no longer talking about a directory on the disk, but a single file. [[User:Paulswartz|Paulswartz]] 01:25, 6 February 2008 (EST) |
Revision as of 06:25, 6 February 2008
see also Talk:Old Develop activity.
Journal resume, tabbed editing.
Response to [1], copied here:
Adding tabbed editing has made me rethink how Develop works. Before, when you hit Keep, Develop saved the activity with a copy of the file that you were editing. This way you could come back to an older version. With tabbed editing, my plan now is:
- each file (eventually, only each changed file) gets an object in the datastore.
- when we keep, we keep each of the individual files that's opened, and then store the object ids
- if we want to go back in time, we can resume either an individual file or the whole activity at that time
This means Develop needs to support being resumed with a file or a saved Develop activity. Eventually, it should also support being resumed with an Activity, to start development on that.
- I think that for now, keep should bundle up the whole activity. It should automatically do a keep when first started on an activity. When restarted with a bundle, it should check that there is an older bundle of the same activity. If there is, it should overwrite the activity in the unbundled directory structure; if not, it should do a "copy of"-type renaming. To export individual files for editing, there should be another button, not "keep". Homunq 12:43, 5 February 2008 (EST)
- Right now, keep just saves all the files. I like the idea of Keep bundling the Activity into an .xo file; but then what happens when we resume? We're no longer talking about a directory on the disk, but a single file. Paulswartz 01:25, 6 February 2008 (EST)