Help with workflow for skinning - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: Skin Development (/forumdisplay.php?fid=12)
+--- Thread: Help with workflow for skinning (/showthread.php?tid=125075)
Pages: 1 2
Help with workflow for skinning - Balinus - 2012-03-08 22:15
I have a question about the workflow that is used to maintain and develop a skin.
I have 2 objectives :
Right now, I understand how to develop the skin locally, by just using a text editor and then "svn commit", etc... The skin repo is then composed of the usual 720p directory, media, etc....
My problem comes when I try to figure out how to set up the repository that could be used inside XBMC, where the skin would be updated automatically. By looking at Hitcher and Pecinkos repository, the skins are zipped inside their own directory.
So, I guess my question is how do you develop locally (i.e. text editor), then create a zip file (through the use of svn command?) and then commit ("svn commit") this zip file to your repository?
edit - Also, how do one create an addons.xml.md5 ? Is there a command?
edit 2- Alternatively, could the skin in the repos for XBMC be with the usual skin directory layout, not in a zip file?
- pecinko - 2012-03-08 23:25
Yes basically as you said, I develop locally, make a ZIP when finished and upload it to repo. I don't use SVN.
- Jezz_X - 2012-03-09 00:03
As much as I hate to say it TheUni was right, I prefer GIT these days when developing skins because it basically lets you have a local repository on your PC with all the changes committed locally and separated and being able to be reverted (undo) one at a time or all together. If you decide later you don't like something.
You can even "branch" your skin of locally do some real crazy stuff to it while keeping the original "master" version untouched, then either merge the changes back into master or dump the whole lot. All locally on your PC.
Then when your ready you can push it somewhere on the web like github.
This is how I maintain the PVR versions of my skin I have the Master branch which is the main skin in the eden repos and then a pvr branch that has the changes I need for pvr and every time I push a new version to eden I merge all the changes I did from master into the pvr branch. And its pretty much all auto and I don't have to worry about any of it none of this pesky copy and paste stuff then guessing where to put it git knows
- Jezz_X - 2012-03-09 00:07
P.S you don't use zips in your svn/git repo you use the original images the zip files are just for people too download like this https://github.com/JezzX/skin.pm3-hd
- Hitcher - 2012-03-09 00:35
I use a batch file for creating the skin folder (with Texture.xbt) and changelog.txt.
Here's XeeBo's -
I then ZIP up the skin folder (note: must be ZIP) and add the revision number to them (ie skin.xeebo-3.0.0.zip and changelog-3.0.0.txt). [This can probably be done through the batch file but I don't know that much.]
Just run something like Little MD5-Creator on the addons.xml
- Jezz_X - 2012-03-09 01:45
heh I went a little more generic and advanced I guess than that hitcher my folder layout looks like this
where each one of the ticks is the git a separate git repo https://github.com/JezzX
and the texturepacker dir holds the exe files to make the xbt.
The shortcuts like "Build PM3.HD" is a shortcut to build.bat with the folder name passed as a paramater eg:
but you could easily type "BuildSkin.bat PM3.HD" at the command line and it would do the same, I'm just lazy and do the double click in windows
And anyway in the end out pops a folder inside "BUILD" with the compiled skin
here is the bat file
- Balinus - 2012-03-09 16:22
Wow, nice posts guys! I think this kind of information should be more visible on the forums or the wiki. The workflow of a project can be hard on newcomers. I've spent 3-4 days just to learn all the small technical steps needed to publish code (through svn in my case) and now I see that some of you don't even use these tools!
Having this information could be an incentive to some people that are not confident on this kind of matter.
So much to learn before even beginning to do some small skinning! When I complete my workflow, I'll post what I do! I'm pretty sure I'll be less advanced than what you guys do.
By looking at your scripts, it seems that you all develop on Windows right?
Thanks again! That's useful information imho.
- pecinko - 2012-03-09 16:28
Balinus Wrote:By looking at your scripts, it seems that you all develop on Windows right?
Black and myself are on OS X. Feel free to ask if you have any platform specific questions, but it does not matter really.
Well almost since texture packer can not be used as on Win platform
- Martijn - 2012-03-09 16:43
pecinko Wrote:Well almost since texture packer can not be used as on Win platform
Hmm i thought Jeroen used it on windows.
Also when building the win32 version it does use the texture packer for the confluence skin
- pecinko - 2012-03-09 16:48
pecinko Wrote:Black and myself are on OS X. Feel free to ask if you have any platform specific questions, but it does not matter really.
Martijn Wrote:Hmm i thought Jeroen used it on windows
I should have said "Well almost since texture packer can not be used on OS X in same way as on Win platform"
i.e. you have to DL 5GB of developers tools and compile whole XBMC in order to be able to use it.
- Balinus - 2012-03-09 17:40
I guess Texture Packer doesn't work well under Linux. (?). edit - There is : http://www.texturepacker.com/texturepacker/linux-version-is-here-at-least-a-bit/
Anyway, for now I'm more a coder than an artist. My short-term aim is to slowly learn skinning through maintaining igotdvds's Shade skin and update it correctly for Eden.
- pecinko - 2012-03-09 17:51
Balinus Wrote:I guess Texture Packer doesn't work well under Linux. (?). edit - There is : http://www.texturepacker.com/texturepacker/linux-version-is-here-at-least-a-bit/
It does, but (AFAIK) same rule apply as to OS X - you'll need to compile XBMC to get to it. Not artist friendly in any way, but that's how it stands ATM.
- BigNoid - 2012-03-09 18:01
Compiling is a piece of cake if you follow the included readme files.
- pecinko - 2012-03-09 18:34
Big_Noid Wrote:Compiling is a piece of cake if you follow the included readme files.
It might be easy (though I wasn't able to set up environment on OSX last time I tried) but it sure isn't convenient at all.
- BigNoid - 2012-03-09 22:38
Jezz_X Wrote:This is how I maintain the PVR versions of my skin I have the Master branch which is the main skin in the eden repos and then a pvr branch that has the changes I need for pvr and every time I push a new version to eden I merge all the changes I did from master into the pvr branch. And its pretty much all auto and I don't have to worry about any of it none of this pesky copy and paste stuff then guessing where to put it git knows
So you're saying that we shouldn't add pvr xml's to the skins in the official repo?