[texworks] Document Version-ing and synctex Previewing

[Paul A Norman]

Thanks Charlie,

Some good helpful advice.

I am thinking that as many of these systems accept command line
instructions it may be possible to do it outside TeXworks proper
perhaps through Tw scripting leaving people free to use whatever
versioning system they are already familiar and comfortable with.

Perhaps scripts being provided to ease interaction with some of the
more popular repository set ups could be a useful way forward?

I think the point you make about making sure that whatever set-up
someone chooses to go with does allow export to one or more of the
other main systems is worth focussing on.

For now I'll probably look at possibilities with  Bazaar when I get some time.

Paul ...
From http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html

"Plays Well With Others

"Bazaar transparently supports foreign branches for Subversion, Git
and Mercurial repositories. This means you can use normal Bazaar
clients and commands on these - special commands are generally not
required!

"See our tutorial for an introduction to using Bazaar as a Subversion
client. As of Oct 2009, Git and Mercurial integration is less mature
but rapidly progressing along the same lines.

"...you can use fast-export to switch your code base across if and
when another tool better meets your needs.

"In short, choosing Bazaar is a very safe choice. Above all, it’s dead
easy to use and suitable for everyone in your community/team,
regardless of their role or platform of choice"


On 22 June 2011 11:26, Charlie Sharpsteen <chuck at sharpsteen.net> wrote:
>
> On Tue, Jun 21, 2011 at 3:49 PM, Paul A Norman <paul.a.norman at gmail.com> wrote:
>>
>> Thanks,
>> I'm very interested in the one, Bazaa,  that Alain Delmotte has turned up for no other reason than it apparently allows varying degrees of  integration into the other version control  systems mentioned recently here (which I have used in the past) as welll.
>> Looks like it is nicely .py and truly natively cross platform.
>> And it really is major with Canonical, yet is stand a lone personnel wise.
>> I mean really major with Canonical !
>> What do others think? ANy experience with Bazaar?
>> Paul
>
> When choosing a version control system for a project, the first thing I think about is off-site hosting for a central repository since it is nice to always have access to a clone of the work no matter where I am and a backup no matter what happens at home. Documents and research papers are interesting in that some of them are likely to be private or access-restricted while others may be shared with others. Most repository hosts provide free accounts upon the condition that they be used to store material that is publicly available under open-source licenses and then make their money by charging for private repositories. Bitbucket, which works with Mercurial, is interesting in that it allows unlimited private repositories and charges based on the size of the team that has access to those private repos.
> If you like Python, Mercurial is also written in Python and used to manage the source code of Python its self.  I have not used Bazaar for any personal projects, but to me the major selling point seems to be Launchpad which not only hosts repositories, but automatically builds and Linux packages and makes them available to package managers like apt.
> Of course, if you are comfortable setting up your own server to host a central repository it doesn't really matter which VCS you choose---go for the one that tickles your fancy.  As long as the system you choose has support for dumping data to the 'git-fast-export' format, it will be easy to move projects to another system if you change your mind later.
>
> -Charlie