(Edit: I split this topic from the Lackey-patch one since it involves the FTP stuff instead. The files I used for the patch )
Q_x wrote:I just downloaded whole FTP pack, which is nearly gigabyte now, just to see that nearly 10% of this are damn svg files.
All code is/should be hosted in a VCS or wherever its maintainer wants it. That leaves us mainly with all binaries as original images that eat a lot of space and bulky handling. Hence we moved away from bzr on your request, which is reasonable given bzr never worked that great for us in the first place. For now we're trying out the FTP, until I or somebody else sets up a VCS for binaries.
A huge majority of all those mb is raster. A very few files (2-5?) are GIMP-files, and the rest are Inkscape SVG, coupled with a very few Scribus files.
On the FTP there are only two SVG files that hold the Gaian templates: gaian creature template.svg
& gaian event template.svg
. They are 6-7mb in total. They are also not officially needed since they were mainly used to create the base which is imported into Scribus.
Whatever else is SVG on the FTP is so either because a) it's vector and something was created as such and in such a case odds are it should stay vector - it's good having the original around in case we should want to alter it some day no matter what we export it to, or b) it is SVG because it hasn't been phased out (meaning deleted and properly replaced by something else) yet.
I'm not certain I understand the problem and which SVG files got you fuelled up here
In the case of b) somebody has to do it and the only stuff I can think of that needs to be migrated from SVG and imported into something has already been done by you - the template.
Which other files do you refer to? (E.g. there is a SVG dedicated to the mark symbol you designed, but I think it's excellent keeping it SVG since that's the original. Then again, only you would know how to properly import/export it into Scribus for usage in it since I don't know know what actually works and doesn't in Scribus or sizes used in it, nor what the needs are in those files due to print-related issues which you are far more qualified for.)
To lessen the burden on bandwidth I also created a /temp dir on the FTP some time ago that is supposed to hold all "unofficial" work files etc. There is a README in it and I have already begun putting some of scattered shit in it, but I'm sure there is plenty more that needs to be moved into it by all of us.
Now, I've done the templates for a very good reason. They are PITA to prepare, but are quite easy to work with later, certainly less laborious than creating and maintaining Inkscape files.
This is in place since very long - in fact long enough to get a bit outdated, but it's still quite usable:http://chaosrealm.net/wtactics/wiki/ind ... d_Template
I guess to save my nerves I should ask politely why do you work that way. If it's your way of doing things, I'll just have to let you walk it, and not disturb too much and see how it went out in the end.
I know you have worked long and hard on the Scribus templates and in the end they are still the ones - and only ones - to be used for all work with the cards. As for the files I used to create the latest LackeyCCG patch, they're still local on my harddrive and haven't been released to the public for that very same reason.
Personally I did not use Scribus to create the LackeyCCG patch because:
a) My files don't matter since they're not official, are not nor will be released as a "replacement" for the Scribus files. The way I did it is not supposed to be the official work flow or how we'll ask people to do it. There is however a good reason for why I myself deviated from it:
b) It was my understanding, from chat and probably mail, that you were in a stage where you were currently typesetting
all the Gaian cards and maybe even the rest. It was also my understanding that this would take a while as you found it not all too exciting, as you explained somewhere - it is your every day job and you find it easy but not shemxy.
c) As you know we have an ongoing topic about the resource system, if it is broken or not. Just recently I released a video of an attempt to show some game play flow. Obviously it has many short comings, some of which you pointed out in the forum. In an attempt for us to actually start concept testing again instead of just doing forum abstractions
and to also get some nicer cards for future videos into Lackey I was in a hurry to release a "working" patch for Lackey. I also was looking forward to finally be shown
, by playing in Lackey, many of the various issues you have alerted us about since it would help me understand them and your take on them way better.
d) I don't know
Scribus (yet). I don't know how stuff is supposed to be in it properly typeset. Sure, you wrote an excellent piece on working with it, but it doesn't answer all questions that will arise about details. I don't know how the stuff, when it is properly done as you imagine it, will look like for sure in Scribus, since I haven't seen the 100% finalised typeset cards yet as they were not completed and you were working with them as far as I know.
e) I have had font-problems on my machine(s) that have messed things up in the Scribus and perhaps other files. Since you were typesetting I figured it's the last thing we need to add to the equation right now.. although I think I have finally managed to solve them.
Combine all that and it seemed unwise for me to use Scribus. I saw no reason to start doing what you already were doing and probably doing more properly than I would have - then we'd just end up with two different sets of Scribus files suddenly. I also currently work faster in Inkscape and the files were just going to be used for the LackeyCCG patch anyways, so I did it in Ink to finish it as fast as I could.
Summed up: Once you have done a final typesetting of the cards we can set "standards" on how it's supposed to look and operate and also extend the docu on it somewhat. When that's done there should, as you write, be no need to use anything else.
I just wanted to move things along so we can get back to concept testing as fast as possible.