New Kitchen (Helmi_APAC_WM3.5_NEW_Kitchen_R0) Bugs

[colonel]

Originally Posted by Kolano

I definitely agree. Having something like optional sub-install items might be nice, with some handling of missing items rather than errors/crashes (i.e. if UUID exists add this sub-item by it's UUID, if not ignore).

It is assumed tha you would setup apps like this to your own preferences. The setup in the kitchen is a guide. If you want plain, I can do that.

[Kolano]

Originally Posted by colonel

It is assumed tha you would setup apps like this to your own preferences. The setup in the kitchen is a guide. If you want plain, I can do that.

If it's as it or plain, I'd choose plain. But I'd prefer sub-installs for these sorts of things.

It's not clear how BuildOS is ordering things, but if we understood, we could probably jury rig something like sub-installs by using multiple OEM packages. Is it by the alphabetic order of the folders, first SYS then OEM?

[colonel]

Traylaunch, like many apps of its nature, sets up the apps in the reg or ini or dat. It really doesn't matter if you have multiple apps installed. It is just looking for them. If you do not intend on installing them (and you should because they are very basic and useful apps) then change the traylaunch reg.

[angel12]

so ive been trying to keep up with the other forum (who put helmi's blah blah blah in the ftp), and i was just wondering if its possible to use the oems i have built for the uni kitchen on this release, if not thats cool too, i know this still isnt "officially" released yet.

[xholmezx78]

Is there a why to replace the default Device Lock with the new Slide Lock?

Also when cooking up my mater brew in the new kitchen, are OEM cab installers different then application cab installers? I dont want to assume too much, but are the OEM installers smaller then the regular application install? Is there any differences between the installer from SPB Pocket Plus, vs. the OEM that is packaged in the kitchen?

Can we make a Stickey with the new kitchen to centralize questions, and bug reports?

[xxfwmxx]

Originally Posted by xholmezx78

Is there a why to replace the default Device Lock with the new Slide Lock?

Also when cooking up my mater brew in the new kitchen, are OEM cab installers different then application cab installers? I dont want to assume too much, but are the OEM installers smaller then the regular application install? Is there any differences between the installer from SPB Pocket Plus, vs. the OEM that is packaged in the kitchen?

Can we make a Stickey with the new kitchen to centralize questions, and bug reports?

Yeah I would love to have the new Slidelock added in as well as the iContacts app. I had installed Helmi's initial test rom using the new kitchen and icontacts wouldnt run properly on it so not sure if its possible or not. Anyways awesome job to everyone who has helped with this!!!

[schettj]

Originally Posted by angel12

so ive been trying to keep up with the other forum (who put helmi's blah blah blah in the ftp), and i was just wondering if its possible to use the oems i have built for the uni kitchen on this release, if not thats cool too, i know this still isnt "officially" released yet.

Yes... I've done this with several of my OEMs that are not in the kitchen.

Simple 4 step process
(0) copy your OEM folder to the OEM folder of the kitchen
(1) Copy an option.xml file from any existing kitchen OEM to your new OEM's folder
(2) Edit option.xml and change the description text, tip text, and guuid
- for the first two, it should describe your OEM
- for the last one, use the uuid (ie, file name of .rgu/.dms file without the extention)
(3) Drag & drop the OEM file on the BuildDsm.exe app in TOOLs

Now your OEM will show up as a choice, either checked or not by default

Example option.xml:

<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
  <Item name="AM Tasks+" group="JCS-OEM" checked="true">
    <Tip>Tasks+ Today Plugin</Tip>
    <Guid type="p">6d99973c-bc86-11db-8314-0800200c9a66</Guid>
  </Item>
</Items>

You change:
name (name shown in BuildOS OEM picker)
group (group in BuildOS - I put all mine under JCS-OEM)
checked (true means its selected by default)
Tip (tooltip)
Guid - matches the uuid of the OEM

Simple as pie.

As far as I can tell, you *can* treat this just like the old kitchen in that if you don't want something for sure, just yank it out of the OEM folder, and if you always want something, dropping it into the OEM folder w/o adding an option.xml will make it always build in. Not sure about that last bit, but several OEMs are in there w/o option.xml and they seem to always build in. Might only work if the OEM folder name does not start with "Optional_"

[Trident]

This may sound dumb, but is there a way to download an entire OEM folder from the FTP without downloading each file in the folder individually?
Some of them are zipped/rar'ed as one file, but many of them are multiple files.

[brightedge]

Originally Posted by Trident

This may sound dumb, but is there a way to download an entire OEM folder from the FTP without downloading each file in the folder individually?
Some of them are zipped/rar'ed as one file, but many of them are multiple files.

If you really want to do that, you'll have to use an FTP program like WS_FTP or CuteFTP.

[Trident]

Cool. I just got something called CoreFTP LE.
Works beautifully.
Thank you.