![]() Looking forward to speaking with you soon! Want to see more? Grab some time on our calendar and give us 1:1 feedback. Windows users – we promise that a bright future is ahead. We’re trying to make SourceTree for Windows as beautiful as the OS X App, and we finally approached a point of convergence. They loved it!ĭon’t worry, we did not remove any functionality, all of those options are still accessible via right click and the “Repository” and “Actions” menus. So we created some new mockups without these buttons in the UI and tested these mockups with our existing users for over six weeks. We surveyed roughly 180,000 unique users and found that the “Reset”, “Add”, “Remove”, “Add Remove”, and “Git Flow” buttons, each individually, were used by less than 5% of those surveyed. By thoroughly looking at the click data, we found a set of buttons that were rarely used in the toolbar. One way we tackled this problem was with data. Many SourceTree users asked us to tackle SourceTree’s “interface bloat”. We don’t “dumb down” Git, but we believe we could do a better job of making SourceTree more approachable for new users. SourceTree has always helped by offering an excellent visual counterpart to the command line interface. There’s no doubt that Git has a steep learning curve. We’ve made huge strides in improving usability and UI consistency throughout SourceTree, but we’re just scratching the surface.Īddressing approachability and “interface bloat” We’re excited to share with you our future plans, but first let’s take a step back and look at how far we’ve come: The last release was a step in that direction. Our goal with SourceTree is to move towards a cleaner, simpler interface for developers new to Git while keeping all the powerful features advanced users love. Github.SourceTree Design – what’s next? By Joel Unger on March 1, 2016 Using git from terminal is fine for me but this platform makes a few things better such as commit log tracking and intuitive source code diff. It's available as an npm package, so I just run it from the command line and open it in the browser to use it on the go. The web based UI client was originally developed for Linux and Mac alone, later it was made compatible with windows. So I made a web based UI client crafted with React and Node JS. Git diff is good but visualizing things on the shell is not the same as viewing it from a UI layer. So I needed a git UI client to track what has actually changed in the scripts. Along with the js based projects I maintain, I also have a bunch of bash scripts on my digitalocean droplet which I constantly modify. Then I got comfortable with bash and started using that actively. I was using GitKraken back in 2019 and it is honestly great. (BTW, if you haven't, you should definitely look up "bisect", it's awesome).įunny thing is that I actually made my own (□). ![]() Because you have labeled buttons and menu items that are right in front of you as you go about your normal git business, it will make you wonder something like "what is bisect?" and then you know what to learn about/search for to become more familiar with git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |