View Single Post
  #5 (permalink)  
Old 12-04-2007, 03:17 PM
tiermann's Avatar
tiermann
VIP Member
Offline
Location: PA, USA
 
Join Date: Apr 2007
Posts: 815
Reputation: 3165
tiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIPtiermann is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to tiermann Send a message via Yahoo to tiermann
Here's a quick overview of the new info you can add to option.xml added by GGuruUSA.

Code:
<OEMVersion>1.0</OEMVersion>
This is used to show the version or revision of the OEM. If you're going to keep the same AppVersion, you'll want to change this each time you make a change.

Code:
<OEMDate>10/23/2007</OEMDate>
This is the last date you modified the OEM.

Code:
<ButtonType>GroupRadioNone</ButtonType>
This is how you would like your list item to "act" in buildOS. It has 5 possible types:
  1. Hidden doesn't show on the list. Used for hidden requirements only.
  2. NoButton shows up with no button.
  3. Check shows up as a normal old checkbox.
  4. GroupRadioNone shows up as a radio button, but none of the "GroupRadioNone" items in that OEM group must be selected. They can be "unchecked".
  5. GroupRadioOne shows up as a radio button and one of the "GroupRadioOne" items in that OEM group must be selected.

Code:
<OEMAuthor>YourName</OEMAuthor>
This is used to give yourself credit for the OEM you're creating.

Code:
<AppVersion>2.0</AppVersion>
This shows the versions of the application itself. For example if your OEM contains Slide2Unlock 0.85, then it would be 0.85.

Code:
<AppAuthorURL>http://www.somesite.com</AppAuthorURL>
This is used to give the original application's author credit. It should link to either the application author's homepage, the application's homepage, or a decent thread or page with info about the application.

Code:
<AdditionalInfo>A bunch of info can go in here that you would like people to know about the OEM or application.
It can be single or multi-line.</AdditionalInfo>
Code:
    <Exclude>331439cf-a636-4243-8424-e501be3a39d2</Exclude>
    <Exclude>3dca3381-3564-4380-8f56-05ccbe08d080</Exclude>
    <Exclude>6226602c-2ba3-40bf-83e4-ea9173088ac9</Exclude>
    <Exclude>1d9a869a-f37e-479b-adc7-dc128ebcf707</Exclude>
    <Require>612345cd-2ba3-40bf-83e4-ea9173088ac9</Require>
Now this is really cool... You can add requirements and exclude other OEMs:
This example comes from the split version of Microsoft Office Mobile.
The Exclude lines tell buildOS that this OEM is not compatible with the old Office version and to exclude it if it's checked already on the list.
The Require line tells it to include some shared Office components that it will need which are included in a hidden OEM.

Last edited by tiermann; 12-04-2007 at 03:25 PM.
Reply With Quote