 |
Author |
Topic: request for comments - history (Read 767 times) |
|
fry
|
request for comments - history
« on: Jul 23rd, 2003, 4:38pm » |
|
i'd like some input on the 'history' mechanism in processing. i haven't been able to develop it as much as i'd like, but i wanted to get a bit of input back on a few points.
1. does anyone use the history menu in its current implementation?
2. we're planning to add a forward/back for history, ala photoshop. how's this sound?
3. what about seeing visual diffs of the code between multiple versions of history? i'm putting together an app to do this for an exhibition, might be possible to drop into p5. would this make you more inclined to use the history mechanism?
4. the original intent of storing history.. usually when i have a project, i'll archive the folder it's in, giving it a version number or a date, each time that i've done something semi-major, so that i can go back and visit an old version if necessary. this process gets annoying to keep track of, and i'd like the environment to be doing this in the background all the time. unfortunately, as of now, the history doesn't keep track of changes to the data files (or other files that will eventually be included with your project) so it's not quite optimal, though it may be expanded to include this sort of thing. your thoughts?
i'm leaning towards an implementation of 3 & 4, but would like to get some feedback from y'all about what you'd prefer or if there are other ideas.
|
|
|
|
|
toxi
|
Re: request for comments - history
« Reply #1 on: Jul 23rd, 2003, 4:55pm » |
|
yeah, i'm using the history pretty regular/often, mainly when realising i've started going down a dead end road.
i'm with you regarding points 3+4: visual diffs would be great as it's often not very obvious where the differences are when rolling back and the source doesn't fit fully in the editor window. at the moment the only clue is the timestamp in the history menu.
point 4, backing up the entire project folder would be top too, but it's not in the first few lines on my wishlist.
my 2p...
|
http://toxi.co.uk/
|
|
|
fry
|
Re: request for comments - history
« Reply #2 on: Jul 23rd, 2003, 4:57pm » |
|
good to know, i wouldn't have guessed this, so thanks for the info.
others?
|
|
|
|
|
arielm
|
Re: request for comments - history
« Reply #3 on: Jul 23rd, 2003, 5:12pm » |
|
i'm not using the history right now, i guess because i like to:
- have a whole snapshot (i.e. including data)
- have a way to "comment" each version (with a custom folder file name or a text file inside): the problem with classic history stuff is that you only have a date information to remind you what something is about...
(seems like there's an history mechanism in eclipse too.. i'm not using it but i guess it could be interesting to see on what principles it's based)
|
Ariel Malka | www.chronotext.org
|
|
|
benelek
 
|
Re: request for comments - history
« Reply #4 on: Jul 30th, 2003, 3:48pm » |
|
hiya. i haven't been checking up on the bboard for the last week or so, and already i feel a bit out of step!
i've started using the history function as another stimulus for design; as in, unzipping a history file from one project and using it as a data file in another sketch. to me this is something like an equivant to all those "experiential-mapping" applets which track people's lives through events, etc.
i must admit, though, i've never really used the history function as it might be intended. the exception to that, is when i've been working on something, haven't saved for a while and p5 crashes. it's a wonderful tool in crash recovery!
*two cents*
~benelek
|
|
|
|
|
mKoser
|
Re: request for comments - history
« Reply #5 on: Jul 30th, 2003, 4:17pm » |
|
i actually never use the history-stuff mainly because my way of using Proce55ing was developed when P5 still was crashing alot, this means I often end of having something like:
flowertail_001
flowertail_002
flowertail_003_3D_flowerhead_implemented
flowertail_004
flowertail_005_ready_for_web
i like to be able to trace me steps back, especially because I often (also) go down a deadend road, which might be usefull in another project, just not in the current one!
i get lost in the date/time-stamp ... dunno if a visual would help? i am not sure I would use if I didn't get a chance to add my comment (ie. "_ready_for_web") ... maybe?
my 2cents!
Mikkel
|
mikkel crone koser | www.beyondthree.com | http://processing.beyondthree.com
|
|
|
fry
|
Re: request for comments - history
« Reply #6 on: Jul 30th, 2003, 7:24pm » |
|
yeah, this is precisely what we'd like to address with the history thing.. but it's not doing it now. i wind up doing the same thing with my own projects but would prefer to have a mechanism to just keep track of it silently / by default / in the background. sounds like some tweaking is in order, at any rate.
|
|
|
|
|
Koenie
 
|
Re: request for comments - history
« Reply #7 on: Jul 30th, 2003, 8:40pm » |
|
I sometimes use it, when I made a terrible mistake somewhere in the code. But I think it's hard to view the history for new users especially. Maybe a history browser would be an idea?
Koenie
|
http://koeniedesign.com
|
|
|
kevinP
|
Re: request for comments - history
« Reply #8 on: Feb 16th, 2004, 7:54am » |
|
on Jul 23rd, 2003, 4:38pm, fry wrote:
3. what about seeing visual diffs of the code between multiple versions of history i'm putting together an app to do this for an exhibition, might be possible to drop into p5. would this make you more inclined to use the history mechanism
4. the original intent of storing history.. usually when i have a project, i'll archive the folder it's in, giving it a version number or a date, each time that i've done something semi-major, so that i can go back and visit an old version if necessary. this process gets annoying to keep track of, and i'd like the environment to be doing this in the background all the time. unfortunately, as of now, the history doesn't keep track of changes to the data files (or other files that will eventually be included with your project) so it's not quite optimal, though it may be expanded to include this sort of thing. your thoughts |
|
I think an option to add a history note would be useful (like in CVS). I also like to be in control. What would be nice would be a "Save version..." command in the file menu, similar to Save as, but instead of the option to change the file name, the file is simply saved in same folder with a verion number appended. (sketch_mysketch --> sketch_mysketch.01, etc.). This way I can save "key versions" at points where I feel that I need better version control than a simple undo.
-K
|
| « Last Edit: Feb 16th, 2004, 7:57am by kevinP » |
|
Kevin Pfeiffer
|
|
|
|
