View Single Post
  #10 (permalink)  
Old 02-29-2008, 02:36 PM
colonel's Avatar
colonel
Retired Staff
Offline
Location: Shawnee, KS
 
Join Date: Jan 2007
Posts: 2,434
Reputation: 508
colonel knows their stuffcolonel knows their stuffcolonel knows their stuffcolonel knows their stuffcolonel knows their stuffcolonel knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Changing default wm 6.1 theme

Here is another example. Notice the stwater and tdywater and the corresponding numbers behind them. This will set the images for portrait and landscape.

Code:
<wap-provisioningdoc>
    <characteristic type="Registry">
        <characteristic type="HKCU\Software\Microsoft\Today">
            <parm name="Skin" value="\Windows\Graveyard.tsk" datatype="string"/>
            <parm name="UseStartImage" value="1" datatype="integer"/>
        </characteristic>
        <characteristic type="HKLM\Software\Microsoft\Color">
			<parm name="5" value="2302755" datatype="integer"/>
			<parm name="8" value="0" datatype="integer"/>
			<parm name="9" value="16777215" datatype="integer"/>
			<parm name="4" value="16777215" datatype="integer"/>
			<parm name="6" value="0" datatype="integer"/>
			<parm name="7" value="12632256" datatype="integer"/>
			<parm name="10" value="16776960" datatype="integer"/>
			<parm name="11" value="12632256" datatype="integer"/>
			<parm name="12" value="16744448" datatype="integer"/>
			<parm name="13" value="0" datatype="integer"/>
			<parm name="14" value="12632256" datatype="integer"/>
			<parm name="15" value="16777215" datatype="integer"/>
			<parm name="16" value="16771012" datatype="integer"/>
			<parm name="25" value="0" datatype="integer"/>
			<parm name="26" value="12632256" datatype="integer"/>
			<parm name="27" value="16777215" datatype="integer"/>
			<parm name="28" value="16777215" datatype="integer"/>
			<parm name="36" value="16776958" datatype="integer"/>
			<parm name="37" value="16116958" datatype="integer"/>
			<parm name="38" value="16744448" datatype="integer"/>
			<parm name="39" value="16777215" datatype="integer"/>
			<parm name="40" value="255" datatype="integer"/>
			<parm name="34" value="7566195" datatype="integer"/>
		</characteristic>
		<characteristic type="HKCU\Software\Microsoft\Today">
			<parm name="DPI" value="96" datatype="integer"/>
		</characteristic>
		<characteristic type="HKCU\Software\Microsoft\Today\Graveyard.tsk">
			<parm name="Color_Highlight" value="7566195" datatype="integer"/>
			<parm name="Color_HighlightText" value="16777215" datatype="integer"/>
			<parm name="Color_SoftkeyFlat" value="2302755" datatype="integer"/>
			<parm name="Color_TitleFlat" value="2302755" datatype="integer"/>
			<parm name="Color_CommandBar" value="2302755" datatype="integer"/>
			<parm name="Color_CommandBarText" value="16777215" datatype="integer"/>
		</characteristic>
    </characteristic>
    <characteristic type="FileOperation">
        <characteristic type="%CE2%" translation="install">
            		<characteristic type="tdywater_240_320.gif" translation="install">
				<characteristic type="Copy">
					<parm name="Source" value="%CE2%\TDYWATER1.gif" translation="install" />
				</characteristic>
			</characteristic>
			<characteristic type="tdywater_320_240.gif" translation="install">
				<characteristic type="Copy">
					<parm name="Source" value="%CE2%\TDYWATER2.gif" translation="install" />
				</characteristic>
			</characteristic>
			<characteristic type="stwater_240_320.gif" translation="install">
				<characteristic type="Copy">
					<parm name="Source" value="%CE2%\STWATER1.gif" translation="install" />
				</characteristic>
			</characteristic>
			<characteristic type="stwater_320_240.gif" translation="install">
				<characteristic type="Copy">
					<parm name="Source" value="%CE2%\STWATER2.gif" translation="install" />
				</characteristic>
			</characteristic>
        </characteristic>
    </characteristic>
</wap-provisioningdoc>
Now, you don't really need to do the copying of the files and you could just name them to begin with. However this is a little safer as it avoids any file conflicts during the build and makes sure the proper files are in place on boot.

Again, if this is still confusing, hang tight until the new buildOS and OEM.rar is released. These will be in there. I am also trying to get tiermann to include this in OEMizer.
__________________
Kitchen updates at www.ppckitchen.org and you can get BuildOS help Here

If you have been helped by me or would like to support developers like Olipro, helmi_c, and others please feel free to Donate

ALWAYS FLASH BACK TO YOUR CARRIER'S OFFICIAL ROM BEFORE TAKING YOUR PHONE IN FOR SERVICE OF ANY KIND

Reply With Quote