GitHub for Windows • Hacker News Board

Re: GitHub for Windows

#41

Post by tylermenezes » Mon, May 21, 2012, 5:10 PM UTC

cool-RR wrote: post #16

I've been expecting this for months, and as I guessed, it's pretty disappointing. I think that SmartGit is a much better GUI for Git on Windows. Just the fact that it doesn't have keyboard shortcuts is a dealbreaker.

Really? I don't like SmartGit at all? It's so flexible that it's unreasonably difficult to do even simple tasks.

I'm glad Github decided on a core feature set, and made those very easy to access.

Re: GitHub for Windows

#42

Post by MichaelGG » Mon, May 21, 2012, 5:11 PM UTC

zokier wrote: post #23

harrylove wrote: post #11

I hope this is the beginning of the end of TFS.

Not without VS integration.

VS integration is only the start. Easily/automatically integrated build, test, and work item integration is also pretty attractive.

Re: GitHub for Windows

#43

Post by base698 » Mon, May 21, 2012, 5:13 PM UTC

Was this developed on raw hardware or in a VM running on Linux/Mac?

Re: GitHub for Windows

#44

Post by coolowencool » Mon, May 21, 2012, 5:15 PM UTC

debacle wrote: post #15

This is very interesting. Will this tool be able to work with non-github git repositories?

It picked up on my non-GitHub repos and initially, it seems like I can do all the things I would expect a git repo to do.

Re: GitHub for Windows

#45

Post by protolif » Mon, May 21, 2012, 5:15 PM UTC

statictype wrote: post #20

xpaulbettsx wrote: post #8

Earlier quoted context omitted.

The UI was implemented using WPF4 and Blend. We also use a framework called Caliburn Micro as well as a framework I wrote called ReactiveUI which orchestrates connecting the UI to data via binding.

Thanks for the info. It looks like you chose to embed Chromium for rendering markdown? What was the reason for not using an embedded IE instance (which is already part of every Windows installation).

Probably because IE is a giant failboat.

Re: GitHub for Windows

#46

Post by harrylove » Mon, May 21, 2012, 5:16 PM UTC

tallowen wrote: post #5

I find it interesting that both native apps (for Windows and Mac) try hard to emulate the look and feel of their respective operating system. One thing that is great about github.com and other websites is that it feels the same across multiple environments. Furthermore web browsers try to emulate their own style not that of the host operating system. If I use chrome or firefox in mac or windows they feel basically th…

I've been developing web apps for Windows 8 lately using the native -ms- proprietary CSS styles and UI hooks available in IE 10 on touch devices. (CSS grids and scroll snap points!) Let me just say, web apps that follow the Windows 8 UX guidelines are easier to develop and, overall, just feel better to use. That is, they feel like they belong inside Windows 8.

From that perspective, I think they're doing the right thing.

Re: GitHub for Windows

#47

Post by shanemhansen » Mon, May 21, 2012, 5:16 PM UTC

This is awesome. Personally I'm a linux user so git is one of those rare tools that caters to me, but I've been in a few backwards development shops where git was looked down upon because of inferior tool support on windows when compared to subversion. I'm in favor of anything that helps bring windows users into the git-using fold ;-)

Re: GitHub for Windows

#48

Post by TazeTSchnitzel » Mon, May 21, 2012, 5:16 PM UTC

base698 wrote: post #43

Was this developed on raw hardware or in a VM running on Linux/Mac?

Would it make much difference? Hardware virtualisation is pretty fast, no?

Re: GitHub for Windows

#49

Post by ttrashh » Mon, May 21, 2012, 5:19 PM UTC

Nice work xpaulbettsx! Great to see a Caliburn.Micro getting some props. We're using it on a large WPF app now.

How many people were on the team? Did you let Phil write any Xaml?

Re: GitHub for Windows

#50

Post by xpaulbettsx » Mon, May 21, 2012, 5:20 PM UTC

statictype wrote: post #20

xpaulbettsx wrote: post #8

Earlier quoted context omitted.

The UI was implemented using WPF4 and Blend. We also use a framework called Caliburn Micro as well as a framework I wrote called ReactiveUI which orchestrates connecting the UI to data via binding.

Thanks for the info. It looks like you chose to embed Chromium for rendering markdown? What was the reason for not using an embedded IE instance (which is already part of every Windows installation).

IE doesn't participate in the WPF rendering system, so it would have all kinds of glitches like it sitting above all other controls (referred to in the docs as "Airspace Issues"), as well as unthemed controls (specifically the scroll bar - stuck out like a sore thumb). The markup that READMEs use is really simple, IE would've been fine for it.