Re: Source code control Update button.
Re: Source code control Update button.
- Subject: Re: Source code control Update button.
- From: Alex Zavatone <email@hidden>
- Date: Thu, 29 May 2014 15:50:47 -0400
On May 29, 2014, at 2:26 PM, Marco S Hyman wrote:
>> 5 - 10 minutes to wait for the interface to update WITH NO USER FEEDBACK for a repo update is insane.
>
> Did the update take 5-10 minutes? If so you got your feedback...
No. The update didn't. The window was open with files to compare and nothing for me to do except click Cancel.
6 minutes transpired and the Update button magically enabled.
Now, as my memory refreshes itself, I remember this happening sometime last week and while I was typing an email asking "What is going on?", the Update button magically enabled AND clicked itself while I was typing an email on another computer.
> the button stayed grey until the update was done. Kind of like
> how when using the command line the cursor will stay at the
> beginning of a new line doing nothing until the command is
> finished and a prompt is displayed.
But there's no progress indicator.
There's no status indicator.
There's no pending stuff indicator.
There's no network activity indicator.
There's no indicator at all indicating that anything is being done at all.
And then, magically, the Update button enables after an indeterminate amount of time.
I've seen it, my Director's seen it, my coworkers see it.
We're waiting to do an update and the only option is to click Cancel or do nothing since Update is grayed out.
I've seen faster updates in 1991 while working on Lotus 123 for the Mac.
> Or am I misunderstanding you. I certainly wouldn't want anything
> modal going while waiting for an update as there are other things I
> might want to be doing. I suppose the button could change to
> busy while it's grey.
>
> FWIW I find it easier to use the command line for most source
> control functions. That is probably more from decades of habit
> than anything else.
>
Yeah, under my last engagement at a different client, I used the Versions SVN client in Xcode 4 without a problem. It was a joy to use. At this gig, we don't have a budget for an extra app to do version control, and our IT department switched the entire company over to SVN. We don't have a choice in the matter, we use what they support and we have to either use Xcode (I can't use my personal licenses) or the command line.
After a years of using the Versions source code control client, I'm completely shocked at how messy the SVN support is in Xcode 5.
In fact, I first tested this out be hosting my own SVN repo on my local 10.8.5 Mac and simply adding a file to a SVN 1.7.10 repo instantly crashes Xcode all the time at line 1519. 100% of the time, every time here:
Application Specific Information: Assertion failed: (svn_uri_is_canonical(child_uri, NULL)), function uri_skip_ancestor, file /SourceCache/subversion/subversion-62/subversion/subversion/libsvn_subr/dirent_uri.c, line 1519.
Even testing the same thing on another user's computer shows the same issue(s).
It's like no one ever even tested this.
See, our engineers, our Director, our contractors (me) are supposed to be coding. They are not supposed to be reporting bugs to a company to address the most basic functionality of source control that their tool claims to support.
Or writing emails asking "am I the only one who sees this and how do I fix it?"
That's what's disheartening.
> Marc
Thanks Marc. Cheers.
FYI, Apple has reached out to me on this. That's very nice to see.
- Alex Zavatone.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden