Sorry if anyone receives this twice. There was a temporary glitch in my list
membership so I'm reposting.
On Nov 19, 2009, at 12:00 PM, Quinn Taylor wrote:
Simply put, because Versions doesn't care whether or not a file is selected
if a parent directory is selected.
Exactly. Actually I
Tested Cornerstone a bit recently... interface is definitely more
clunky than Versions. Overall I think Versions still has the edge,
despite its quirks, but man, if the browser columns would stay put and
the commits/updates were non-modal, there'd be no contest. :)
The built-in diff viewer
On Nov 19, 2009, at 12:00 PM, Quinn Taylor wrote:
Simply put, because Versions doesn't care whether or not a file is selected
if a parent directory is selected.
Exactly. Actually I would say this is a bug. It feels to me like it violates
the principle of least surprise, in that it's odd to
@Tomo
I personally often work on more than one thing on a project, and
when
I want to commit, I would like to be able to commit different things
seperately.
Could you not just selected individual files to commit in the list
view or am I missing something?
Versions should also know that I have
I'm always submitting a few files from versions so that I can submit related
file changes together.
Cmd-click/shft-click on the files to select the ones you want to submit and
submit them. I think checkboxes would get in the way.
- Hardy
On Nov 19, 2009, at 10:35 AM,
It's a matter of workflow preference. Yes, you can select files and folders in
the main GUI before committing — command-clicking etc. obviously works, but
just because something is possible doesn't mean that's the only way anyone
would/should ever want to do it. (Exhibit A: Windows) However, it
I've only done the selective commits by selecting files that I want to commit,
not the other way around as you are suggesting, but isn't what you want to do
just...
Show changed files, select all, cmd-click the file/files you don't want to
commit?
I've only used Eclipse once for a small
I think you're misunderstanding my point. I'm not extolling the virtues of
Eclipse, I also find it annoying in many ways, but for large Java projects, it
does redeem itself. (FWIW, configuring a project is IMO the absolute worst part
of Eclipse. Once you get past that, working with it isn't
Quin,
I get your point. Why not expand your hierarchy select them all with
shift click and deselect the folders and the items you wish to exclude
with command click?
- Marijn
On Nov 19, 2009, at 5:18 PM, Quinn Taylor wrote:
I think you're misunderstanding my point. I'm not extolling the
Simply put, because Versions doesn't care whether or not a file is selected if
a parent directory is selected. (sigh) Because it's often a lot more work than
removing a single resource, and as I've stated, with hierarchical selection, it
can be non-trivial to select everything but. No offense
I've worked with Eclipse and TortoiseSVN, and work daily with Versions and
SmartSVN. The workflow Quinn lays out is the same I have with SmartSVN and
it's so much simpler to do than the cmd+click option, which is really
impossible if you have a both wide and deep folder hierarchy. If you do
Totally agree that checkboxes in a commit dialog makes much more sense
with large, deeply nested projects than manually selecting everything
you want to commit. I had to deal with this for several months on a
large project and believe me, it would be much faster to have
checkboxes presented. As
Checkboxes beside files in the commit window are a must have.
I personally often work on more than one thing on a project, and when
I want to commit, I would like to be able to commit different things
seperately.
Another ridicilously silly thing is, if I change something like the
database
On Mon, Nov 16, 2009 at 10:30 AM, Tomo tomo.gla...@gmail.com wrote:
Another ridicilously silly thing is, if I change something like the
database config file (wich is only different on my local version), or
application config file, I want to commit stuff without this going up
with them.
On Mon, 16 Nov 2009 16:35:54 +0100, Ray raimondi...@gmail.com wrote:
I agree with the commit UI changes, but this is a workflow issue.
For some use cases, I agree this is a workflow issue, but for others it
isn't. You might want to partially commit your entire working directory
because
Another feature relating to commit.
If I'm trying to commit a file that's not under version control, it's
probably because I'd like to add it. When the window pops up to say
'xxxs' is not under version control, there should be a button which
says Add this and then retries the commit. If I try to
I'd like to second the request for a non-modal commit/update process -
personally I think this is the current #1 major impediment to
productivity in Versions, and fixing it would make the experience of
using the app so much more smooth.
Thanks guys!
-Gabriel Gilder
Another feature request:
could we get file sizes inside the dialog showing the status of
updates/commits?
for example, tortoiseSVN offers the following: total file size,
current size (updates during download) and download speed.
i have a few libraries being used by a project, and some of them
I gave that a shot and it made a slight difference, but the column
widths are still pretty inconsistent between launches. Basically it
seems like the Name column always shrinks a little bit, and all the
other columns grow a bit, especially Last Modified Author. Since my
project doesn't have any
You could try and see if backing up and trashing your Versions
preference file fixes the issue.
Regards,
--
Jasper
the versions team
On Sep 10, 8:45 pm, Gabriel Gilder gabriel.gil...@gmail.com wrote:
Awesome, glad to hear these are in the works.
I took a look at the column widths again on
20 matches
Mail list logo
