Comments (12)
I think what is happening is /root/FolderA is interpreted as removing the file
'FolderA' from the directory '/root/'. It's probably reasonable for Gource to
check
if there is a directory with that path and remove that instead.
Gource assumes all paths it is given from a log file end in files.
Is this an SVN repo? What script did you use to generate your log? Did you use
svn-gource.py with the --filter-dirs option?
I would quite like to tidy up the SVN support, partly because the contributed
script
is written in python which I'm not really that interested in learning.
Cheers
Original comment by [email protected]
on 12 Jan 2010 at 9:53
- Changed state: Started
from gource.
Yeap, it's an svn repo converted with svn-gource.py without --filter-dirs
option. With
--filter-dirs as far as I remember everything is even worse: folder actions are
completely ignored insead of expanding them as list of actions with chidren
files.
Original comment by [email protected]
on 12 Jan 2010 at 9:59
from gource.
Ah ok. I think understand now.
I might have a go making a smarter SVN conversion script in perl.
Original comment by [email protected]
on 12 Jan 2010 at 10:14
from gource.
I've written small ruby script that fixes data produced by svn-grouce.py - it
adds
children files removal commands on folder remove.
But it's not perfect. For example "svn folder copy" will not be correctly
processed
since it also have one command in log and no source path info (original svn log
has
such info, but it's cut out by svn-gource.py) ~_~`
Original comment by [email protected]
on 12 Jan 2010 at 10:19
Attachments:
from gource.
[deleted comment]
from gource.
Cool someone might find that useful.
Could you post an example of an 'svn folder copy' log xml entry?
Original comment by [email protected]
on 12 Jan 2010 at 10:41
from gource.
In subversion xml log it's something like this:
<path
copyfrom-path="/trunk/newfoldername"
copyfrom-rev="123"
action="A">/trunk/oldfoldername</path>
Original comment by [email protected]
on 20 Aug 2010 at 7:47
from gource.
Thanks for making a donation :)
I've been meaning to add support for renames so I will address directory
actions too.
Original comment by [email protected]
on 21 Aug 2010 at 2:39
- Changed title: Support renames and folder removal
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from gource.
Thanks for your great work :)
Original comment by [email protected]
on 21 Aug 2010 at 8:07
from gource.
Hi!
I really like your projects and spent some time playing with it on some svn
repositories.
As Alexander I remarked that folder deletes and copies (including moves,
renamings, branching...) were not handled correctly.
So i built a Java program that parses a svn xml log and "fixes" it by
recursively adding the same commmands to subdirectories and files of a copied
or deleted directory.
Here are the source files. The program needs jdom and takes one argument, the
name/path of the log file.
It outputs three files : the old and new version in a pretty format for easy
diff, and the new version in a format compatible with gource (for some unclear
reason the pretty formated xmls fail when input into gource).
I will be glad to get your comments/suggestions/fixes.
Anyways, thanks for this great, poetic, beautiful, useful work!
Original comment by [email protected]
on 8 Apr 2011 at 10:32
Attachments:
from gource.
Thanks Julian!
Hopefully people will find this useful until I address this in Gource. I added
directory deletion handling for SVN logs in 0.30 (assuming this works), but I
have not added support for the other SVN specific commands yet.
I have made some assumptions about the format of the SVN xml file in order to
'seek' into it at any point and find the next commit (the closing '</logentry>'
tag must be on a new line for instance), which might be why your XML doesn't
parse.
Cheers
Andrew
Original comment by [email protected]
on 9 Apr 2011 at 5:19
from gource.
I would like to see improved support for folder renames and moves in this great
visualization tool, as it is the most dissatisfying piece at the present time,
IMHO. When a folder is renamed, the folder link and its name (if visualized)
should simply flash. If a folder is moved to another location, the simulation
currently "explodes", whereas a more satisfactory result would be for the link
to be reattached to the new location, with the simulation "pulling" the rest of
the tree to the new location. Something similar might be done with individual
file moves, with the file visualizers sliding over to their new locations.
I'm using Git, in case that has any bearing on the issue.
Original comment by [email protected]
on 24 May 2014 at 4:59
from gource.
Related Issues (20)
- There is no fullscreen HOT 1
- Gravatar support HOT 3
- option to highlight directories and set user/dir/filename color HOT 2
- No stop when last date is passed HOT 1
- predictable temporary filename HOT 1
- Doesn't link GL correctly on OS X (10.6.3) HOT 10
- Segfault on OS X if run with no parameters HOT 3
- Please add a --user-image-program option to shell out to get user images HOT 1
- Add option to configure/disable aging of nodes HOT 2
- [PATCH] Build failure with binutils-gold HOT 2
- stop-position outside of range 0 – 1 HOT 1
- Assertion failure in vbo_exec_bind_arrays HOT 4
- Auto-zoom HOT 3
- Pause/delay at end HOT 2
- cursor.png not included in Makefile.am HOT 1
- New package release HOT 3
- Filter for user HOT 3
- vulnerability: rewrite arbitrary user file HOT 1
- --hide-user-images option HOT 2
- What is the deeper meaning? HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gource.