View Full Version : Skins explained - I hope :o)
Rockas
3rd November 2004, 20:47
First of all, as usual... Forgive my English
I know... making skins for Rebuilder has been a hard issue... not anymore :)... after killing half of my brain I think I managed to develop a method that can help everyone and make it easy.
Imagine that you design a background with 697 pixels of width and 548 pixels of height.
To get the data for your Form size variable (on your skin .txt) you'll need a calculator :)
Just make it this way:
______________________________________________________
«Keep in mind the width and height that I gave - above - as example»
(548+50+3)*10+50%=9015 => for height (if you want, use excel and make the formula as it is)
(697+3+3)*10+50%=10545 => for width (if you want, use excel and make the formula as it is)
______________________________________________________
Then you must insert the results on your .txt file...
You'll get something like this:
[Main]
Form=9015,10545
Scale=548,697
______________________________________________________
The why:
Well I don't have an explanation for all the numbers 'cause I don't know the source code of Rebuilder - even if I knew... I'm not a programmer, just a designer, so it would be the same :) - anyway... here it goes:
(548+50+3)*10+50%=9015
=>548 is the height of this example background;
=>50 is the space (in pixels) occupied by the window's (window of Rebuilder) title bar and the menus area on Windows XP default aspect, if you use Classical aspect use 42 instead but this won't make significant changes, though;
=>3 is the width of the window's (window of Rebuilder) bottom border;
=>about the multiplication by 10 and the sum of 50% don't ask me... it just works that way, ok? :D;
=>9015 is the result of the formula;
(697+3+3)*10+50%=10545
=>698 is the width of this example background;
=>3+3 is the sum of left and right window's (window of Rebuilder) borders;
=>same as above;
=>10545 is the result of the formula;
______________________________________________________
All the other data (like box position, height and width) you can get from your image Editor, reading the pixel values.
You must get the data from the top left corner of your object for location and its size for width and height.
Variable="y_position","x_position","height","width"
Example:
AudioList=109,375,80,220
109 = Y position
375 = X position
80 = height
220 = width
______________________________________________________
I've tested this method with Photoshop and MediaChance's RealDraw and it works perfectly.
There is an issue with, at least (on main interface - my tests were with it only), the Status Box and VTS box - there must be an error on the source code of Rebuilder it self - they don't assimilate the exact size that you enter, but they get the location right, though... I think jdobbs will correct this on the next releases.
Thanks and keep it UP
uff!!! It’s hard to explain something without images lol... is there a way of posting html? lol
ps. the skin that I used for my tests is THIS (http://www.dvdrebuilder.com/ROCKAS_LEATHER.jpg) - not finished... so don't bother ask lol
Rockas
4th November 2004, 00:07
What?!?!? no feedback?!?!?
I hate to be right all the time :D
Just kidding... just don't forget to say if everything works fine, ok?
p200002
4th November 2004, 16:03
Having looked into the txt files under skin directory, I finally gave up using my artistic and creative "talent" on rebuilder. :stupid:
huesage
4th November 2004, 16:21
Exelent work Rockas !
I am just waiting for the video box bug to get taken care of, then I will pick up the interface again.
jdobbs
4th November 2004, 19:02
Video box bug?
Rockas
4th November 2004, 19:56
@jdobbs
I've explained on the first post... VTS box text and status don't get the height that we enter... there must be something wrong with them on the source code :confused:
This happens on the main interface... don't know about the others... I didn't get time, yet, to test them :(
keep it UP
edit:
@p200002
Man... it's more simple that it seems at first sight... but without a little effort everything is hard :)
ouiouioui
4th November 2004, 22:27
yeah, thanks for have explain ;) i'l test it tomorrow
jdobbs
5th November 2004, 18:50
I don't think I understand all the number crunching here...
If you a create a form with a scale of 500, 800 -- the form has 500 vertical and 800 horizontal units of measurement in its client area. Top, Left is 0,0 and bottom, right is 500,800 the center of the form is 250, 400.
I think you are somehow confusing the additional area used to hold the "Batch mode" as somehow part of the initial form. Normally that extended area would be a seperate image all together (although it doesn't have to be. You can make that area larger, smaller, wider, taller... it's all up to you.
DK
5th November 2004, 23:38
i'm having severe problems realizing a new layout for the setup window
having created this skinDotNoise_Setup (http://uncas.atlandide.net/images/DotNoise_Setup.jpg) i'm not able to make it fit in any way
- can i assign a new scale/form for this section?
i tried to assign Scale=492,657 because my file is 657x492 but this scale was of no good
( i did work with pixel scale in the main window successfully btw)
no matter what i try to insert as values it seems completely useless - any hint anyone?
- the textfile is missing a subtitle section whereas audio is present
+++++++
this is what the result looked like:
Crappy DotNoise Setup (http://uncas.atlandide.net/images/dotnoise_setup_bad.jpg)
and here is content of the setup section:
(i have tried w/out form+scale - everything is measured in pixel)
[SETUP]
Form=8175,9945
Scale=492,657
Background=dotnoise/UMS_DotNoise_Setup.jpg
CCEBasic=86,112,28,161
CCEBasicButton=540,6720,375,435
CCEBasicButtonGraphic=
CCE250=169,76,29,145
CCE250Button=1080,6720,375,435
CCE250ButtonGraphic=
CCESP=226,69,29,153
CCESPButton=1620,6720,375,435
CCESPButtonGraphic=
ReJig=281,62,29,184
ReJigButton=2200,6720,375,435
ReJigButtonGraphic=
QuEnc=109,416,29,154
QuEncButton=2700,6720,375,435
QuEncButtonGraphic=
EclPro=167,441,29,137
EclProButton=3300,6720,375,435
EclProButtonGraphic=
Decoder=226,442,29,147
DecoderButton=3840,6720,375,435
DecoderButtonGraphic=
Decomb=281,422,29,174
DecombButton=4440,6720,375,435
DecombButtonGraphic=
MinCheckbox=247,321,17,17
DTSCheckbox=178,321,17,17
AudioAllButton=349,201,31,39
AudioAllButtonGraphic=
AudioNoneButton=399,202,31,39
AudioNoneButtonGraphic=
AudioSaveButton=443,205,30,34
AudioSaveButtonGraphic=
++++++++++++++
i did not bother to change/adobt the xyzBUTTON values btw so pls ignore those numbers
Rockas
5th November 2004, 23:42
@jdobbs
I know the "numbering" sounds strange... but if you try the formulas you'll see that it works... and it is the better way of doing it for people that work with Photoshop or other image editing software... as long as it gives user the pixel position and sizes of objects.
But anyway... I'd like to hear from someone that tested the theory besides me :)
Anyone?
thanks and keep it UP
edit:
@DK
Can you send me the source image?
DK
5th November 2004, 23:46
@ rockas
i have linked to the dotnoise_setup.jpg file, so you might as well download it
and yes, i did work with the formula given and it worked fine to a certain degree
seems that after a certain top-value the numbers are not working correctly anymore - so trial & error helped me out
Rockas
5th November 2004, 23:48
you're right, I'm so stupid :o
OK I'll give it a try.... by the way... did you received my last e-mail?
Rockas
5th November 2004, 23:50
What's the size of the image of your main interface?
jdobbs
5th November 2004, 23:53
@DK
Send me the entire set (.txt and graphics) and I'll take a look at it.
jdobbs
DK
5th November 2004, 23:55
i'm sory i haven't checked my mail in the last hour or so - will do so now
here is the complete *.txt:
++++++
[Main]
Form=9045,10590
Scale=550,700
BatchWidth=15090
Background=dotnoise/UMS_DotNoise.jpg
BatchBackground=0,700,550,300
BatchBackgroundGraphic=dotnoise/UMS_DotNoise_Batch.jpg
#General rule: Object=Top,Left,Height,Width
#Graphic=Path starting at "Skins" directory
#Color
Source=11,147,22,378
SourceButton=11,554,26,35
SourceButtonGraphic=
Working=363,423,18,250
WorkingButton=388,429,33,33
WorkingButtonGraphic=
Output=443,423,18,250
OutputButton=411,634,33,33
OutputButtonGraphic=
VTSList=80,254,74,188
AudioList=81,25,109,178
SubList=81,496,109,178
Progress=496,130,17,305
Overall=525,365,17,257
Percent=525,621,17,50
StatusBox=365,30,99,256
PrepareButton=359,293,33,120
PrepareButtonGraphic=
PrepareButtonColor=&H00D8D8D8&
EncodeButton=396,294,33,120
EncodeButtonColor=&H00D8D8D8&
EncodeButtonGraphic=
RebuildButton=432,295,33,120
RebuildButtonColor=&H00D8D8D8&
TranscodeButton=396,294,33,120
TranscodeButtonColor=&H00D8D8D8&
BatchList=75,728,347,248
AddButton=420,757,42,44
AddButtonGraphic=
DelButton=420,834,42,44
DelButtonGraphic=
SaveButton=418,909,42,60
SaveButtonGraphic=
SaveButtonColor=&H00D8D8D8&
Frame=1980,60,4215,6135,0,6360,5715,4215
[CCE_SETTINGS]
Background=dotnoise/UMS_DotNoise_CCE.jpg
Label01=VBR_Bias :,180,180,&HFFFFFF
Label02=Quality Prec :,540,60,&HFFFFFF
Label03=VBR_Passes :,240,2460,&HFFFFFF
[FILTER_EDIT]
Background=dotnoise/UMS_DotNoise_AVS.jpg
TextColor=&HFFFFFF
[README]
Background=dotnoise/UMS_DotNoise_AVS.jpg
[SETUP]
Scale=492,657
Background=dotnoise/UMS_DotNoise_Setup.jpg
CCEBasic=86,112,28,161
CCEBasicButton=540,6720,375,435
CCEBasicButtonGraphic=
CCE250=169,76,29,145
CCE250Button=1080,6720,375,435
CCE250ButtonGraphic=
CCESP=226,69,29,153
CCESPButton=1620,6720,375,435
CCESPButtonGraphic=
ReJig=281,62,29,184
ReJigButton=2200,6720,375,435
ReJigButtonGraphic=
QuEnc=109,416,29,154
QuEncButton=2700,6720,375,435
QuEncButtonGraphic=
EclPro=167,441,29,137
EclProButton=3300,6720,375,435
EclProButtonGraphic=
Decoder=226,442,29,147
DecoderButton=3840,6720,375,435
DecoderButtonGraphic=
Decomb=281,422,29,174
DecombButton=4440,6720,375,435
DecombButtonGraphic=
MinCheckbox=247,321,17,17
DTSCheckbox=178,321,17,17
AudioAllButton=349,201,31,39
AudioAllButtonGraphic=
AudioNoneButton=399,202,31,39
AudioNoneButtonGraphic=
AudioSaveButton=443,205,30,34
AudioSaveButtonGraphic=
Rockas
5th November 2004, 23:55
The problem is that I forget to tell that the setup image must have the same size of the main interface image :o
Sorry
DK
6th November 2004, 00:00
ok, i will try again sometimes later
thanx for the advice
++++++
sorry, jdobbs
didnt see your posting before - this baord is so painfully slow :(
mail is sent
jdobbs
6th November 2004, 01:22
Originally posted by Rockas
The problem is that I forget to tell that the setup image must have the same size of the main interface image :o
Sorry It shouldn't. The position and size of objects gets scaled just like the backdrop...
DK
6th November 2004, 02:04
like i said i was not able to make the setup background fit
cf the screenshots postet above
i'd be glad for any input/advice
Rockas
6th November 2004, 03:23
Originally posted by jdobbs
It shouldn't. The position and size of objects gets scaled just like the backdrop...
I was refering to my method... when the scale is set to the pixels size of main interface, the setup window must have the same size if we want to use the same method...
but I promisse that I'll study the problem and come up with some easy solution for this :)
... tomorrow
l8nights
9th March 2006, 14:48
I anted to add for anyone that wishes to make a skin for themselves that after following the advice given by Rockas in this thread, creation was pretty simple thnx
I have one addition after toying w/ the "set-up" screen the initial calculations of
(548+50+3)*10+50%=9015
for height should be changed to
(xxx+30+3)*10+50%=xxxx
this is because the set-up screen runs w/ only the border and not the extra menu bar that the main interface uses
just wanted to help save some time if any one happens across this. =)
rendez2k
13th March 2006, 16:28
Maybe what we actually need is somebody clever like Rockas to come up with a new skin-making app!?
Rockas
13th March 2006, 16:36
lol I guess that is the first time that someone actually calls me "clever"... don't tell my wife about that :D
come up with a new skin-making app
hmmm... I don't know about that... I don't think that there are a lot of people interested on doing skins :)
People usually use the defaults.
jdobbs
13th March 2006, 18:08
I actually had originally planned to do just that... but, as Rockas mentioned, the interest level seemed pretty low.
rendez2k
13th March 2006, 19:44
I actually had originally planned to do just that... but, as Rockas mentioned, the interest level seemed pretty low.
Seems odd - the skinning community appears to have a massive following thses days. If you made an app, I for one would give it a shot!
if it needs a special application in order to be able to create a skin than i guess this skin wont be anything genuine or decent looking
l8nights
14th March 2006, 03:34
photofiltre and a calculater?? I'll give you a good price, lol
the creativity would have to come from a different source GggG
it' really not difficult once you get the scaling down.
I'm not that great of a "graphics guru" like some in this thread but I like mine it suit's me
http://img390.imageshack.us/img390/1797/skinshot1vt.jpg
I have to agree w/ DK, it would have to be quite extensive to allow a good deal of "personal touch".
JohnGalt
14th March 2006, 03:46
15 twips to a pixel. remember that & you should be good to go.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.