![]() Meanwhile, KDevelop isn't locked into C++, it manages the same parse-language-into-AST framework for dynamic languages such as Python and PHP. Its completion is also extremely smart, as are little situational helpers that pop up. Something I've always enjoyed is its semantic syntax highlighting, where, say, the same variable is assigned the same color through code. What would be cool is, like in vc-annotate, that it's easy to see the full commit message as well as see the diff without "losing" the current blame.KDevelop has a more complete C++ parser than both in my experience, and uses it to greater effect. In the blame: if I click on "show file diff" for a past revision, I don't see a way to get back to the blame. What I also pine for is good diff viewing (left+right panels with code + the typical smooth connections between both). Your blame has a history to the left, which is awesome, if it'd be possible to re-blame based on one of those entries then I'd immediately start using this blame, even with the bullet above as it is. I also cannot select any text.Īnother thing that I regularly do and that's missing from the built-in blame is to navigate backwards/forwards inside of the blame (like e.g. There also appear to be some issues with yours (" is escaped as ' for instance, same for *). I currently like the "integrated" blame better: mainly because I can call it from the file itself (alt g b) + it uses my syntax highlighting + font. what I prefer to have in my IDE is basically anything that has to do with the code files themselves: blame, log, diff, merge conflicts, stash/commit (looking at diffs) In general: for me personally I don't mind going outside of my IDE to do more "architectural" git stuff: branching/stashing/resetting/. The history view is a big (!!) step up from what's available today. It’s a complicated task that I wish to facilitate as much as possible.ĭiff: Better browsing for file diffs and full diffs.Įnded up building myself to try, works well : ) Some thoughts: Merges: I would like to provide a custom tool to handle the merges. Now I show graphic representation of merge commits (when one branch is merge into another) and what branch is what.Īs future features (v2.0.0) you will have I want to test it with really big repos but I’ll do it at work. Qt is so fast that it only takes ~250 msecs to open repos as Stellarium or Musescore. I make some tests and most of the times it won’t show at all for opening repos. Progress dialogs when cloning or opening really big repos. Possibility of applying patches or import them. ![]() Patches: One functionality I didn’t think I needed but I considered that people may like it so, I took it back with some improvements: Multi-selection of commits to export them. There are some pending changes that will be done on the v2.0.0.ĭiffs: Between files, between random commits, etc. The old backend has been reworked in a 85%. The branches are shown in a tree structure, more easy to follow. I added my own QLogger as submodule and I’ve added some logs as well. So, there is a whole new screen where you can review the history of a file and blame it. ![]() ![]() Thanks to the refactor!īlame & History: I didn’t expect I could make it to have this feature in the v1.0.0 version but I pushed a bit for it. This was one of the features I wanted for further versions but, why not?Īs a complement to this, I also added the feature of opening the submodules and interact with them as they where normal repositories. Submodules: I also added support for opening, adding and updating the submodules in a repository. Multi-repository support: One of the biggest features (in implementation) was to add support to have multiple repositories opened at the same time. ![]()
0 Comments
Leave a Reply. |