Tim Shadel wrote:
I use local versioning tons in Eclipse. Right click, Compare to... |
Local History... Or something like that. It's a snap to see diffs of
specific files over time. I don't pay much attention to how many
versions it keeps, but I can sometimes see days back, even on heavily
edited files.
Also check out Right Click, Replace with... | Local History... I
think you can replace sections of code from old files, but I use this
feature less.
--Tim
On 10/12/05, Qin Zhang <[EMAIL PROTECTED]> wrote:
It's called local versioning. Basically, whenever you save a file, it's
recorded. You can revert to any previous version up to a given limit.
JBuilder has this functionality and I used it sometimes years ago. I
remember I see this in eclipse 3.1 too while fiddling around with its
configuration settings, but I never used it.
Cheers,
Cedric
----- Original Message -----
From: austen <[EMAIL PROTECTED]>
Date: Wednesday, October 12, 2005 6:02 pm
Subject: [HACKYSTAT-DEV-L] Source code collection
So I was thinking about Hackystat again (It just sucks you in!) and
was wondering if Hackystat functionality could be extended to collect
source code snippets that a developer is hacking on. The reason
why I
started thinking about source code collection was the way I created
the usermaps GUI. I was having problems getting it to display
properly and basically ended up following this process:
1. Write some code, build it, view it.
2. Re-write the code, build it and view it again.
3. Rinse and repeat.
After long periods of time trying to get the GUI to look how I wanted,
I ended up re-writing the same code. For example I would move buttons
back to locations that they have already been or resized components
back to a previously used dimension. Because of the mass amounts of
code re-writing, I would waste time waiting for the build process to
finish only to see that the result is again a view that I do not wish
to see.
I was thinking that if a sensor could collect code snippets you were
working on, the developer would be able view them later and minimize
the re-writing of the same code. After talking in the lab today with
Hongbing, Julie, and James, the approach turned into a comparison of
code snippets to the actual snapshot of the GUI.
This would be helpful since the majority of my work on HackyInstaller
deals with getting the GUI to look just right. I don't know if
Hackystat would be able to collect snippets of code because code
changes so much during the hacking session. And maybe the GUI
creation process won't be as painful when the new build system is in.
Anyways, just a thought.
Cheers,
austen
Austen,
I think it's a good idea. Tim seems to have used local versioning within
eclipse, but it's not implemented in the most user efficient way. Maybe
your idea can contribute to a better front-end for that feature and
maybe even improve it.
As for the GUI side of things, I think your frustrations leads back to
the fact that the GUI editor isn't sophisticated enough to give you
WYSIWYG capabilities and come out with good code. I believe it'll be
improved in the future because the Java hacker gods aren't going to want
to stay behind forever.
Cheers,
James
