Community
Participate
Working Groups
Please refer to bug 345978
I thought bug 345978 was deferred. I'll check tomorrow how much time is needed to fix bug 345980 and bug 345981 and let you know.
Gosia has cycles to look at it.
Created attachment 197491 [details] small changes to explorer If you don't need a git log view with its actions this functionality for very close to be working, only minor changes included in the attachment are necessary to made. This is what you should do to make it work 1. Add a parent div to your page (I assume its id is "parentID") 2. Add git.css to your style sheet (this will require adding line "@import "css/git.css";" to git-status.css) 3. Import 'orion/git/git-commit-navigator' (I assume it's defined as "mGitCommitNavigator") 4. Create navigator: var navigator = new mGitCommitNavigator.GitCommitNavigator(serviceRegistry, null, null, "parentID"); All you need here is service registry 5. Populate your navigator with data. Assuming you have your a Branch json defined as "Branch" it should be enough to call: navigator.loadCommitsList(Branch.CommitLocation + "?page=1"); You can call it whenever you need to change the commit list. As you see the commit list is pageable, but the page size is fixed. I will have to file another bug to change the page size, because our default page size may be too large for your needs. Calling above won't mark you the incoming/outgoing changes. To do this you have to call navigator.renderer.setOutgoingCommits(CommitsInJsonData); or navigator.renderer.setIncomingCommits(CommitsInJsonData); _before_ you call loadCommitsList. To get the commit list you can use gitService.getLog function, for instance full code to display git log with outgoing changes marked would be: gitService.getLog(Remote.CommitLocation, "HEAD", function(scopedCommitsJsonData, secondArg) { navigator.renderer.setOutgoingCommits(scopedCommitsJsonData); navigator.loadCommitsList(Branch.CommitLocation + "?page=1"); }); where Remote is the json representation of the Remote assigned to this branch. To obtain it you may refer to Branch.RemoteLocation. Marking incoming changes will be described wider in Bug 345981.
Gosia/Szymon :thanks for the detailed guidance. Seems promising. I will give it a try . I also opened Bug 348558 to get the RemoteLocation from git status response.
I've pushed the changes. Libing if you have problems with it reopen.
*** Bug 345981 has been marked as a duplicate of this bug. ***