Quote: Originally Posted by
kpjuk 
Hello Profit,
a while ago I tried to create a consistent objects.txt, based on skin commands.txt
If we can get to a consistent file, I can include this in the Help File, which may be a way forward. What needs to be done, can I help in any way ? The skin editor is key to clean development of skins for RR, so your contributions need to be fully supported by the community.
Let me know what I can do, but don't include programming! I did have a look at your source, and it was well beyond my simple capabilities.
cheers
KPJUK
I was up late the other night writing the begining to a Skin Commands.txt file converter aka objectgrabber. I just need to parse through the file and pull out the relevant information. From what I saw so far most objects had a common layout in the text file.
/, (B) Buttons
/, x y w h Command Tooltip
/, --- --- --- --- ------- -------
BXX,XXX,XXX,XXX,XXX,COMMAND,TOOLTIP
But some objects had less info and others had another comment line that contained more info on each property. Like above code would have "This is sent to RR" and such. So what I was going to do was read file until "/," then read first line without "/" and split based on "," which would give me the BXX line, The only problem then is what is XXX,XXX,XXX,XXX Where if I save the previous lines I can try to extract "Buttons" from line 1 "x, y, w, h, command, tooltip" from line 2 and match up with the BXX,XXX line.
Of course this doesn't take into consideration commands/CODE that get added to RR. That would be a whole other process to parse through and retrieve information.
So
/, (<object here aka B, IMG, L, A>) <Name for me to display, or function>
/, < Actual description of each parameter separated by , >
/, --- --- --- --- ------- ------- (Don’t really care bout this line)
BXX,XXX,XXX,XXX,XXX,COMMAND,TOOLTIP <-- this could be <object aka B>,<parameter names would be better here but showing pace holders is okay I guess> I.E. B,XXX,XXX,XXX,XXX, <-- maybe XXX for any numeric value
Not sure about that last line. It may be okay the way it is. As long as COMMAND,TOOLTIP,XXX and other default naming conventions stay the same.
R,B,G are numeric values so XXX is fine for me In fact all plain text/numeric values could be XXX on that last line. FONT, STYLE, CODE have actual values that are buried in the Skin Commands file that I pull out and manually put into skineditor objects file. Also Color is an added feature that requires a certain layout in the objects.txt file.
Maybe if I have more time to think about it I could layout a word document or PDF to describe a standard command list to go by. You know just incase we get an ISO Audit
PM if you want to talk more about this.
edit: p.s. this is what i end up with for the button command in my file
Button,B,x,y,w,h,Command;COMMANDCODES,Tooltip
COMMANDCODES triggers the skineditor to put the [...] to open a list of commands. Same for color "what ever,Forecolor R;RGB,g,b,whatever" RGB triggers a [...], on the "Forecolor R" Field, for a color picker the drops values into field r g b. So i would need to know that r,g,b would need r;RGB,g,b in my file. so as long as r,g,b is standard and not b,r,g or g,b,r or Pr,Yb....you know what i mean.
Inconsistent with his skin commands.txt file. Looks like more work then just doing it by hand for each release!!!! Maybe i could parse through the source files for RoadRunner 
Linear Mode
