[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tabspace, compression tools, development guidelines

From: Friedrich Brunzema <brunzefb_at_yahoo.com>
Date: Wed, 12 Jun 2013 12:28:11 -0700 (PDT)

I will try to come up with a draft of such a file - but because I am new it will likely require a lot of edits.  I will post a proposal on the mailing list.


 From: Stefan Küng <tortoisesvn_at_gmail.com>
To: dev_at_tortoisesvn.tigris.org
Sent: Tuesday, June 11, 2013 3:02:23 PM
Subject: Re: Tabspace, compression tools, development guidelines

On 11.06.2013 15:06, Friedrich Brunzema wrote:
> Hi,
> Couple of questions which may be of general interest:
> 1. XhmikosR - saw that you compressed my new images (thanks!) - is there any specific tool you use for this, or just set the settings to max compression (I use paint.net).

The problem here is: XhmikosR does not use mailing lists.
I think he uses PNGGauntlet and some other tool.

> 2. When changing the .css, which tool do you use to pack the .css (Visual Studio reformats it nicely with Ctrl-K Ctrl-D to allow editing).

1) install node.js
2) cd to www
3) run `npm install`
4) run `node make` every time you want to create the minified files
ready for deployment. The previous steps are a one time thing.

> 3. Any guidelines as to when to run tabspace and what args to use (e.g. before checkin)?  What folders should it be run on? Is there any reason why tabspace is not checked in with the tools (I know you can download it from Stefan's tools). [I volunteer to modify the build script and add the target if someone tells me what the args and folders should be]

We just run that from time to time.
Run it on the src folder - I don't want to change the externals or code
that's not really from us since that only makes updating those difficult.
For the src folder, no arguments are needed: the default arguments are
good enough.
For the docs folder you have to specify the file extensions (xml) so
those get processed.
It's not in the tools because it's not necessary to build TSVN. But
maybe we could add it somewhere in the contrib folder.

> 4. Does it make sense to have a development guideline doc to capture some of the conventions used on the project? Again, I could start such a document, if it makes sense to everyone and does not exist already.

Maybe we really should come up with such a doc file. It's not the first
time this was asked for.
Can you come up with a draft and send it here so we can discuss it?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\    http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-12 21:28:17 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.