WebOS Internals - User contributions [en]

Chrooting

2011-08-06T05:02:11Z

Flare576: missed an option

==Install ext3fs with Meta-Doctor==

You can use Meta-Doctor to create a ext3 fs carved out of the space that is used for the vfat LVM partition.

The Option is:
EXT3FS_PARTITION_SIZE

With that option you can specify the size of the partition

EXT3FS_PARTITION_SIZE = 2GB

for a 2GB partition.

When you Doctor the phone you will have a partition that is located at

/media/ext3fs

on device /dev/store/ext3fs (lvm partition)

==Loop mount a partition on existing partitions==

It is NOT recommended that you loop mount on top of a vfat partition (unless you use a fuseFS) because of attribute issues.

With Meta-Doctor you can increase the size of the /Var partition as well

The Option is:

VAR_PARTITION_SIZE = 2GB

It increases the size of /var to 2GB

Realize that you will be vying for space with any Preware apps, emails, and attachments.

Chrooting

2011-08-06T05:00:29Z

Flare576: updating with current Makefile options

==Install ext3fs with Meta-Doctor==

You can use Meta-Doctor to create a ext3 fs carved out of the space that is used for the vfat LVM partition.

The Option is:
EXT3FS_PARTITION_SIZE

With that option you can specify the size of the partition

EXT3FS_PARTITION_SIZE = 2GB

for a 2GB partition.

When you Doctor the phone you will have a partition that is located at

/media/ext3fs

on device /dev/store/ext3fs (lvm partition)

==Loop mount a partition on existing partitions==

It is NOT recommended that you loop mount on top of a vfat partition (unless you use a fuseFS) because of attribute issues.

With Meta-Doctor you can increase the size of the /Var partition as well

The Option is:

INCREASE_VAR_SPACE = 1

It increases the size of /var to 2GB

Realize that you will be vying for space with any Preware apps, emails, and attachments.

Application talk:Preware

2010-01-20T18:16:04Z

Flare576: /* Display Bug - Heading in "Updates" section scrolls too high */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, it may be implemented in a future version of the application.
}}

== Features and Suggestions ==

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Suggestion: --[[User:Cdjh|Cdjh]] 15:54, 30 August 2009 (UTC)
*Add a feature to remove all patches and modifications to webos before and webos update. Sort of a "Get me ready for and update" button. This would allow the user to remove all these patches such as the virtual keyboard with one button to update webos without fear. One button to add them back after the update would be cool too

Suggestion: [[User:StoneRyno|StoneRyno]] 21:05, 30 August 2009 (UTC)
*Download counts and ratings. The end of the current detail page is ok but feels more like looking at one of the technical detail scenes like the ##DEBUG# scene. I think that info can be cleaned up to look more presentable, small font size and put version last update and size in a bar near the top of the page like seen in the official app catalog.

Suggestion: [[User:Hmagoo|Hmagoo]] 11:30, 4 September 2009 (UTC)
*We're in need of a workaround for the limit on installable apps via the app catalog. Preware gets around this but also, in the process, adds to the number of installed apps as seen by the App Catalog, et al. What would be a useful feature is to be able to uninstall hunks of apps previously installed by Preware in an effort to make apps installable via the App Catalog. This would be a temporary removal as we would desire reinstalling the homebrews after using the App Catalog.
**Caveats: Homebrew apps that use databases, and installed/downloaded files would not be removed without reducing their usability, So we would want to exclude on a case by case basis or with the use of flags?
**Preware is great in keeping track of what is installed and which version, would be great to see something like this added so that we can use the App Catalog and install piles of Homebrews. (smile)

Bug?: Searching for numbers --[[User:smwald|smwald]] 02:05, 29 December 2009 (EST)
* When searching for items in preware, one is not able to search using numbers.

Feature Request: --[[User:GrillSgt|GrillSgt]] 07:29, 5 January 2010 (UTC)
* Would like to be able to rate, comment and donate on themes, patches and apps through Preware, like can be done in the App Catalog.

Feature Request: Collapse Sub-lists --[[User:Flare576|Flare576]] 18:32, 14 January 2010 (UTC)
* When viewing a list of apps and then sorting, you get small headings ("Less than $1," or "This Week"). It would be great to be able to collapse those sub-lists in order to facilitate faster list viewing.

Feature Request: Feed Keyword Filtering --[[User:Flare576|Flare576]] 02:14, 19 January 2010 (UTC)
* There are certain applications and developers that I would like to be able to simply ignore. It would be great if there was an area I could setup universal (and feed specific if you think it'd be useful) filters so that I never have to see them. This would also be a step ahead of the appstore :)

== Possible Bug/Suggestion ==

The new messages during version check/feed downloading are much better at explaining what is going on. However, I still have a problem if I get a notification or switch away from Preware after I open it before it finishes downloading. All of the steps between clicking the Preware icon and loading the feeds seem to require that Preware be in the foreground and not interrupted. Once it starts loading the feeds, I can switch away with no problem, and even get the nice banner popup that tells me when the feeds are finished. Is there a way to fix this problem so that I can open preware and immediately switch to another app, without it getting stuck on version checking or updating feeds?

I can explain the problem in more detail if this is confusing, and I can recreate it every time.

Thanks,
[[User:Zinge|Zinge]] 06:38, 30 October 2009 (UTC)

== Bug- Apps Fail to install from catalog ==

I am the developer from Engine Equals Car. Our app Media Remote will not install from the app catalog if you have preware installed. People who can work on this can contact me at support@engineequalscar.com
--[[User:Tonyparisi|Tonyparisi]] 05:18, 18 December 2009 (UTC)
*I noticed this as well, it seems to apply to all apps that are in both the official app catalog and a homebrew app catalog. You should notice that you don't need to remove preware to install the app from the official catalog, but simply disable the feed in preware then "update feeds" to refresh the list then it should install fine from the official app catalog. Hope this helps out anyone who is working on this. --[[User:Nosoupforyou|Nosoupforyou]] 03:38, 14 January 2010 (UTC)

== Display Bug - Heading in "Updates" section scrolls too high ==

When viewing "Available Updates," and sorted by date, if there is an official app with an update and you use the "Update All" button, the "Today" text will actually scroll up and get stuck under the "Package Updates" title. My scenario was one homebrew and 3 official apps with updates, but after using the button it still appeared when there were only the 3 official left. Swiping back and then stepping in again resolves the situation, but it still looks glitchy :) --[[User:Flare576|Flare576]] 18:16, 20 January 2010 (UTC)

Application talk:Preware

2010-01-20T18:15:47Z

Flare576: New section: Display Bug - Heading in "Updates" section scrolls too high

Application talk:Preware

2010-01-19T02:21:10Z

Flare576: /* Features and Suggestions */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, it may be implemented in a future version of the application.
}}

== Features and Suggestions ==

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Suggestion: --[[User:Cdjh|Cdjh]] 15:54, 30 August 2009 (UTC)
*Add a feature to remove all patches and modifications to webos before and webos update. Sort of a "Get me ready for and update" button. This would allow the user to remove all these patches such as the virtual keyboard with one button to update webos without fear. One button to add them back after the update would be cool too

Suggestion: [[User:StoneRyno|StoneRyno]] 21:05, 30 August 2009 (UTC)
*Download counts and ratings. The end of the current detail page is ok but feels more like looking at one of the technical detail scenes like the ##DEBUG# scene. I think that info can be cleaned up to look more presentable, small font size and put version last update and size in a bar near the top of the page like seen in the official app catalog.

Suggestion: [[User:Hmagoo|Hmagoo]] 11:30, 4 September 2009 (UTC)
*We're in need of a workaround for the limit on installable apps via the app catalog. Preware gets around this but also, in the process, adds to the number of installed apps as seen by the App Catalog, et al. What would be a useful feature is to be able to uninstall hunks of apps previously installed by Preware in an effort to make apps installable via the App Catalog. This would be a temporary removal as we would desire reinstalling the homebrews after using the App Catalog.
**Caveats: Homebrew apps that use databases, and installed/downloaded files would not be removed without reducing their usability, So we would want to exclude on a case by case basis or with the use of flags?
**Preware is great in keeping track of what is installed and which version, would be great to see something like this added so that we can use the App Catalog and install piles of Homebrews. (smile)

Bug?: Searching for numbers --[[User:smwald|smwald]] 02:05, 29 December 2009 (EST)
* When searching for items in preware, one is not able to search using numbers.

Feature Request: --[[User:GrillSgt|GrillSgt]] 07:29, 5 January 2010 (UTC)
* Would like to be able to rate, comment and donate on themes, patches and apps through Preware, like can be done in the App Catalog.

Feature Request: Collapse Sub-lists --[[User:Flare576|Flare576]] 18:32, 14 January 2010 (UTC)
* When viewing a list of apps and then sorting, you get small headings ("Less than $1," or "This Week"). It would be great to be able to collapse those sub-lists in order to facilitate faster list viewing.

Feature Request: Feed Keyword Filtering --[[User:Flare576|Flare576]] 02:14, 19 January 2010 (UTC)
* There are certain applications and developers that I would like to be able to simply ignore. It would be great if there was an area I could setup universal (and feed specific if you think it'd be useful) filters so that I never have to see them. This would also be a step ahead of the appstore :)

== Possible Bug/Suggestion ==

The new messages during version check/feed downloading are much better at explaining what is going on. However, I still have a problem if I get a notification or switch away from Preware after I open it before it finishes downloading. All of the steps between clicking the Preware icon and loading the feeds seem to require that Preware be in the foreground and not interrupted. Once it starts loading the feeds, I can switch away with no problem, and even get the nice banner popup that tells me when the feeds are finished. Is there a way to fix this problem so that I can open preware and immediately switch to another app, without it getting stuck on version checking or updating feeds?

I can explain the problem in more detail if this is confusing, and I can recreate it every time.

Thanks,
[[User:Zinge|Zinge]] 06:38, 30 October 2009 (UTC)

== Bug- Apps Fail to install from catalog ==

I am the developer from Engine Equals Car. Our app Media Remote will not install from the app catalog if you have preware installed. People who can work on this can contact me at support@engineequalscar.com
--[[User:Tonyparisi|Tonyparisi]] 05:18, 18 December 2009 (UTC)
*I noticed this as well, it seems to apply to all apps that are in both the official app catalog and a homebrew app catalog. You should notice that you don't need to remove preware to install the app from the official catalog, but simply disable the feed in preware then "update feeds" to refresh the list then it should install fine from the official app catalog. Hope this helps out anyone who is working on this. --[[User:Nosoupforyou|Nosoupforyou]] 03:38, 14 January 2010 (UTC)

Application talk:Preware

2010-01-19T02:14:21Z

Flare576: /* Features and Suggestions */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, it may be implemented in a future version of the application.
}}

== Features and Suggestions ==

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Suggestion: --[[User:Cdjh|Cdjh]] 15:54, 30 August 2009 (UTC)
*Add a feature to remove all patches and modifications to webos before and webos update. Sort of a "Get me ready for and update" button. This would allow the user to remove all these patches such as the virtual keyboard with one button to update webos without fear. One button to add them back after the update would be cool too

Suggestion: [[User:StoneRyno|StoneRyno]] 21:05, 30 August 2009 (UTC)
*Download counts and ratings. The end of the current detail page is ok but feels more like looking at one of the technical detail scenes like the ##DEBUG# scene. I think that info can be cleaned up to look more presentable, small font size and put version last update and size in a bar near the top of the page like seen in the official app catalog.

Suggestion: [[User:Hmagoo|Hmagoo]] 11:30, 4 September 2009 (UTC)
*We're in need of a workaround for the limit on installable apps via the app catalog. Preware gets around this but also, in the process, adds to the number of installed apps as seen by the App Catalog, et al. What would be a useful feature is to be able to uninstall hunks of apps previously installed by Preware in an effort to make apps installable via the App Catalog. This would be a temporary removal as we would desire reinstalling the homebrews after using the App Catalog.
**Caveats: Homebrew apps that use databases, and installed/downloaded files would not be removed without reducing their usability, So we would want to exclude on a case by case basis or with the use of flags?
**Preware is great in keeping track of what is installed and which version, would be great to see something like this added so that we can use the App Catalog and install piles of Homebrews. (smile)

Bug?: Searching for numbers --[[User:smwald|smwald]] 02:05, 29 December 2009 (EST)
* When searching for items in preware, one is not able to search using numbers.

Feature Request: --[[User:GrillSgt|GrillSgt]] 07:29, 5 January 2010 (UTC)
* Would like to be able to rate, comment and donate on themes, patches and apps through Preware, like can be done in the App Catalog.

Feature Request: Collapse Sub-lists --[[User:Flare576|Flare576]] 18:32, 14 January 2010 (UTC)
* When viewing a list of apps and then sorting, you get small headings ("Less than $1," or "This Week"). It would be great to be able to collapse those sub-lists in order to facilitate faster list viewing.

Feature Request: Feed Keyword Filtering --[[User:Flare576|Flare576]] 02:14, 19 January 2010 (UTC)
* There are certain applications and developers that I would like to be able to simply ignore. It would be great if there was a area I could setup universal (and feed specific if you think it'd be useful) filters so that I never have to see them. This would also be a step ahead of the appstore :)

== Possible Bug/Suggestion ==

The new messages during version check/feed downloading are much better at explaining what is going on. However, I still have a problem if I get a notification or switch away from Preware after I open it before it finishes downloading. All of the steps between clicking the Preware icon and loading the feeds seem to require that Preware be in the foreground and not interrupted. Once it starts loading the feeds, I can switch away with no problem, and even get the nice banner popup that tells me when the feeds are finished. Is there a way to fix this problem so that I can open preware and immediately switch to another app, without it getting stuck on version checking or updating feeds?

I can explain the problem in more detail if this is confusing, and I can recreate it every time.

Thanks,
[[User:Zinge|Zinge]] 06:38, 30 October 2009 (UTC)

== Bug- Apps Fail to install from catalog ==

I am the developer from Engine Equals Car. Our app Media Remote will not install from the app catalog if you have preware installed. People who can work on this can contact me at support@engineequalscar.com
--[[User:Tonyparisi|Tonyparisi]] 05:18, 18 December 2009 (UTC)
*I noticed this as well, it seems to apply to all apps that are in both the official app catalog and a homebrew app catalog. You should notice that you don't need to remove preware to install the app from the official catalog, but simply disable the feed in preware then "update feeds" to refresh the list then it should install fine from the official app catalog. Hope this helps out anyone who is working on this. --[[User:Nosoupforyou|Nosoupforyou]] 03:38, 14 January 2010 (UTC)

Application talk:Preware

2010-01-14T18:32:35Z

Flare576: /* Features and Suggestions */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, it may be implemented in a future version of the application.
}}

== Features and Suggestions ==

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Suggestion: --[[User:Cdjh|Cdjh]] 15:54, 30 August 2009 (UTC)
*Add a feature to remove all patches and modifications to webos before and webos update. Sort of a "Get me ready for and update" button. This would allow the user to remove all these patches such as the virtual keyboard with one button to update webos without fear. One button to add them back after the update would be cool too

Suggestion: [[User:StoneRyno|StoneRyno]] 21:05, 30 August 2009 (UTC)
*Download counts and ratings. The end of the current detail page is ok but feels more like looking at one of the technical detail scenes like the ##DEBUG# scene. I think that info can be cleaned up to look more presentable, small font size and put version last update and size in a bar near the top of the page like seen in the official app catalog.

Suggestion: [[User:Hmagoo|Hmagoo]] 11:30, 4 September 2009 (UTC)
*We're in need of a workaround for the limit on installable apps via the app catalog. Preware gets around this but also, in the process, adds to the number of installed apps as seen by the App Catalog, et al. What would be a useful feature is to be able to uninstall hunks of apps previously installed by Preware in an effort to make apps installable via the App Catalog. This would be a temporary removal as we would desire reinstalling the homebrews after using the App Catalog.
**Caveats: Homebrew apps that use databases, and installed/downloaded files would not be removed without reducing their usability, So we would want to exclude on a case by case basis or with the use of flags?
**Preware is great in keeping track of what is installed and which version, would be great to see something like this added so that we can use the App Catalog and install piles of Homebrews. (smile)

Bug?: Searching for numbers --[[User:smwald|smwald]] 02:05, 29 December 2009 (EST)
* When searching for items in preware, one is not able to search using numbers.

Feature Request: --[[User:GrillSgt|GrillSgt]] 07:29, 5 January 2010 (UTC)
* Would like to be able to rate, comment and donate on themes, patches and apps through Preware, like can be done in the App Catalog.

Feature Request: Collapse Sub-lists --[[User:Flare576|Flare576]] 18:32, 14 January 2010 (UTC)
* When viewing a list of apps and then sorting, you get small headings ("Less than $1," or "This Week"). It would be great to be able to collapse those sub-lists in order to facilitate faster list viewing.

== Possible Bug/Suggestion ==

The new messages during version check/feed downloading are much better at explaining what is going on. However, I still have a problem if I get a notification or switch away from Preware after I open it before it finishes downloading. All of the steps between clicking the Preware icon and loading the feeds seem to require that Preware be in the foreground and not interrupted. Once it starts loading the feeds, I can switch away with no problem, and even get the nice banner popup that tells me when the feeds are finished. Is there a way to fix this problem so that I can open preware and immediately switch to another app, without it getting stuck on version checking or updating feeds?

I can explain the problem in more detail if this is confusing, and I can recreate it every time.

Thanks,
[[User:Zinge|Zinge]] 06:38, 30 October 2009 (UTC)

== Bug- Apps Fail to install from catalog ==

I am the developer from Engine Equals Car. Our app Media Remote will not install from the app catalog if you have preware installed. People who can work on this can contact me at support@engineequalscar.com
--[[User:Tonyparisi|Tonyparisi]] 05:18, 18 December 2009 (UTC)
*I noticed this as well, it seems to apply to all apps that are in both the official app catalog and a homebrew app catalog. You should notice that you don't need to remove preware to install the app from the official catalog, but simply disable the feed in preware then "update feeds" to refresh the list then it should install fine from the official app catalog. Hope this helps out anyone who is working on this. --[[User:Nosoupforyou|Nosoupforyou]] 03:38, 14 January 2010 (UTC)
*Also I haven't checked but I wonder if enabling the palm feed in preware would prevent you from installing anything using the official app catalog since all the apps would be listed in preware now. --[[User:Nosoupforyou|Nosoupforyou]] 03:39, 14 January 2010 (UTC)

Applying Patches

2009-10-07T03:35:58Z

Flare576: /* Pushing the change back to gitorious.org */

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefore we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

Before asking questions about this procedure, please read the following documents fully:

An introduction to Quilt can be found at http://www.suse.de/~agruen/quilt.pdf

The manual for quilt is at http://linux.die.net/man/1/quilt

==Upgrading from quilt to quilt-lite==

If you have performed these instructions before the 8th Aug 2009, you will have installed a very heavyweight version of the quilt package which has a dependency on a very large perl package.

This dependency has been removed in a new quilt-lite package, which saves 26MB of space in /var as a result.

You can switch over to it as follows:

* ipkg-opt update
* ipkg-opt remove quilt perl libdb gdbm util-linux-ng e2fslibs ncursesw
* ipkg-opt install quilt-lite

Alternatively, the setup script below will prompt to uninstall quilt, perl, etc ..., and install quilt-lite, if quilt is installed.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs (or upgrades) quilt (actually quilt-lite, a version of quilt that does not depend on perl) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt-lite' package, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt-lite git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Delete any existing webos-internals modifications directories
<pre><nowiki>
rm -rf /opt/src/modifications
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Listing Applied Patches==
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt applied
</nowiki></pre>

==Removing All Patches==

Before you accept an over-the-air (OTA) update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Quilt Commands==

Other commands when using Quilt-Lite:

Please feel free to add/edit this section. I am not an expert, these are commands that I found by accident when i misspelled delete.

<pre><nowiki>
quilt
add
applied (shows applied/installed patches)
delete (removes a patch from quilt series ex: quilt delete *name of patch*)
diff
edit
files
fold
fork
graph
grep
header
import (downloads patch from git ex: quilt import *name of patch*)
mail
new
next
patches
pop
previous
push (installs patches from quilt series one at a time. quilt push -a installs all patches)
refresh
rename
revert
series (shows all downloaded patches.)
setup
snapshot
top
unapplied
upgrade

</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next, you'll need to create a public/private key pair, and the easiest way to do this is with openssh. If you want to create a pair with windows, there are PuTTYgen/Pageant instructions below under "Alternate Windows Method", but the following may be easier. After you generate a public key you'll share it with gitorious.org; your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # *see Note Below
sudo ssh-keygen -t rsa # follow the prompts, ensure you're saving to /var/home/root/.ssh
cat /var/home/root/.ssh/id_rsa.pub # copy the output and paste it into gitorious key manager
</nowiki></pre>
<nowiki>*</nowiki>There's been some work to get dropbear working, but this tutorial assumes you have openssh installed. For information about dropbear and ssh keys, see [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git this page]
* Don't forget to upload your public key from the last statement above to gitorious.org

Next, you'll need to ensure you have your environment properly configured.

<pre><nowiki>
echo $GIT_SSH # Should be /opt/bin/openssh-ssh
</nowiki></pre>

If the output of this command are anything other than /opt/bin/openssh-ssh, you'll need to update /etc/profile.d/optware. Add

<pre><nowiki>
export GIT_SSH=/opt/bin/openssh-ssh
</nowiki></pre>

To the top of the /etc/profile.d/optware.

Now you should be able to follow the steps below and contribute your code to gitorious.org.

'''Alternate Windows Method'''

The only reasons you might want to pursue this method is if you want to generate a ssh key pair on a Windows box.

Getting your key on window
* Download [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>
*This will destroy your ability to actually pull down updates, so you'll need to modify the /opt/src/modificaiton/.git/config to contain:

<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>
* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
#!/opt/bin/bash

cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

Applying Patches

2009-10-07T03:34:21Z

Flare576: /* Getting Authenticated with gitorious.org */

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefore we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

Before asking questions about this procedure, please read the following documents fully:

An introduction to Quilt can be found at http://www.suse.de/~agruen/quilt.pdf

The manual for quilt is at http://linux.die.net/man/1/quilt

==Upgrading from quilt to quilt-lite==

If you have performed these instructions before the 8th Aug 2009, you will have installed a very heavyweight version of the quilt package which has a dependency on a very large perl package.

This dependency has been removed in a new quilt-lite package, which saves 26MB of space in /var as a result.

You can switch over to it as follows:

* ipkg-opt update
* ipkg-opt remove quilt perl libdb gdbm util-linux-ng e2fslibs ncursesw
* ipkg-opt install quilt-lite

Alternatively, the setup script below will prompt to uninstall quilt, perl, etc ..., and install quilt-lite, if quilt is installed.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs (or upgrades) quilt (actually quilt-lite, a version of quilt that does not depend on perl) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt-lite' package, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt-lite git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Delete any existing webos-internals modifications directories
<pre><nowiki>
rm -rf /opt/src/modifications
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Listing Applied Patches==
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt applied
</nowiki></pre>

==Removing All Patches==

Before you accept an over-the-air (OTA) update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Quilt Commands==

Other commands when using Quilt-Lite:

Please feel free to add/edit this section. I am not an expert, these are commands that I found by accident when i misspelled delete.

<pre><nowiki>
quilt
add
applied (shows applied/installed patches)
delete (removes a patch from quilt series ex: quilt delete *name of patch*)
diff
edit
files
fold
fork
graph
grep
header
import (downloads patch from git ex: quilt import *name of patch*)
mail
new
next
patches
pop
previous
push (installs patches from quilt series one at a time. quilt push -a installs all patches)
refresh
rename
revert
series (shows all downloaded patches.)
setup
snapshot
top
unapplied
upgrade

</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next, you'll need to create a public/private key pair, and the easiest way to do this is with openssh. If you want to create a pair with windows, there are PuTTYgen/Pageant instructions below under "Alternate Windows Method", but the following may be easier. After you generate a public key you'll share it with gitorious.org; your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # *see Note Below
sudo ssh-keygen -t rsa # follow the prompts, ensure you're saving to /var/home/root/.ssh
cat /var/home/root/.ssh/id_rsa.pub # copy the output and paste it into gitorious key manager
</nowiki></pre>
<nowiki>*</nowiki>There's been some work to get dropbear working, but this tutorial assumes you have openssh installed. For information about dropbear and ssh keys, see [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git this page]
* Don't forget to upload your public key from the last statement above to gitorious.org

Next, you'll need to ensure you have your environment properly configured.

<pre><nowiki>
echo $GIT_SSH # Should be /opt/bin/openssh-ssh
</nowiki></pre>

If the output of this command are anything other than /opt/bin/openssh-ssh, you'll need to update /etc/profile.d/optware. Add

<pre><nowiki>
export GIT_SSH=/opt/bin/openssh-ssh
</nowiki></pre>

To the top of the /etc/profile.d/optware.

Now you should be able to follow the steps below and contribute your code to gitorious.org.

'''Alternate Windows Method'''

The only reasons you might want to pursue this method is if you want to generate a ssh key pair on a Windows box.

Getting your key on window
* Download [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
#!/opt/bin/bash

cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

Applying Patches

2009-10-07T03:33:35Z

Flare576: /* Alternate Windows Method */

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefore we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

Before asking questions about this procedure, please read the following documents fully:

An introduction to Quilt can be found at http://www.suse.de/~agruen/quilt.pdf

The manual for quilt is at http://linux.die.net/man/1/quilt

==Upgrading from quilt to quilt-lite==

If you have performed these instructions before the 8th Aug 2009, you will have installed a very heavyweight version of the quilt package which has a dependency on a very large perl package.

This dependency has been removed in a new quilt-lite package, which saves 26MB of space in /var as a result.

You can switch over to it as follows:

* ipkg-opt update
* ipkg-opt remove quilt perl libdb gdbm util-linux-ng e2fslibs ncursesw
* ipkg-opt install quilt-lite

Alternatively, the setup script below will prompt to uninstall quilt, perl, etc ..., and install quilt-lite, if quilt is installed.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs (or upgrades) quilt (actually quilt-lite, a version of quilt that does not depend on perl) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt-lite' package, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt-lite git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Delete any existing webos-internals modifications directories
<pre><nowiki>
rm -rf /opt/src/modifications
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Listing Applied Patches==
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt applied
</nowiki></pre>

==Removing All Patches==

Before you accept an over-the-air (OTA) update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Quilt Commands==

Other commands when using Quilt-Lite:

Please feel free to add/edit this section. I am not an expert, these are commands that I found by accident when i misspelled delete.

<pre><nowiki>
quilt
add
applied (shows applied/installed patches)
delete (removes a patch from quilt series ex: quilt delete *name of patch*)
diff
edit
files
fold
fork
graph
grep
header
import (downloads patch from git ex: quilt import *name of patch*)
mail
new
next
patches
pop
previous
push (installs patches from quilt series one at a time. quilt push -a installs all patches)
refresh
rename
revert
series (shows all downloaded patches.)
setup
snapshot
top
unapplied
upgrade

</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next, you'll need to create a public/private key pair, and the easiest way to do this is with openssh. If you want to create a pair with windows, there are PuTTYgen/Pageant instructions below under "Alternate Windows Method", but the following may be easier. After you generate a public key you'll share it with gitorious.org; your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # *see Note Below
sudo ssh-keygen -t rsa # follow the prompts, ensure you're saving to /var/home/root/.ssh
cat /var/home/root/.ssh/id_rsa.pub # copy the output and paste it into gitorious key manager
</nowiki></pre>
<nowiki>*</nowiki>There's been some work to get dropbear working, but this tutorial assumes you have openssh installed. For information about dropbear and ssh keys, see [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git this page]
* Don't forget to upload your public key from the last statement above to gitorious.org

Next, you'll need to ensure you have your environment properly configured.

<pre><nowiki>
echo $GIT_SSH # Should be /opt/bin/openssh-ssh
</nowiki></pre>

If the output of this command are anything other than /opt/bin/openssh-ssh, you'll need to update /etc/profile.d/optware. Add

<pre><nowiki>
export GIT_SSH=/opt/bin/openssh-ssh
</nowiki></pre>

To the top of the /etc/profile.d/optware.

Now you should be able to follow the steps below and contribute your code to gitorious.org.

'''Alternate Windows Method'''
The only reasons you might want to pursue this method is if you want to generate a ssh key pair on a Windows box.

Getting your key on window
* Download [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
#!/opt/bin/bash

cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

Applying Patches

2009-10-07T03:32:58Z

Flare576: /* Getting Authenticated with gitorious.org */

==Introduction==

We cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license) therefore we need to manage our modifications as patches. Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied after-wards, we need a procedure and tools for doing this. This page documents this procedure.

Before asking questions about this procedure, please read the following documents fully:

An introduction to Quilt can be found at http://www.suse.de/~agruen/quilt.pdf

The manual for quilt is at http://linux.die.net/man/1/quilt

==Upgrading from quilt to quilt-lite==

If you have performed these instructions before the 8th Aug 2009, you will have installed a very heavyweight version of the quilt package which has a dependency on a very large perl package.

This dependency has been removed in a new quilt-lite package, which saves 26MB of space in /var as a result.

You can switch over to it as follows:

* ipkg-opt update
* ipkg-opt remove quilt perl libdb gdbm util-linux-ng e2fslibs ncursesw
* ipkg-opt install quilt-lite

Alternatively, the setup script below will prompt to uninstall quilt, perl, etc ..., and install quilt-lite, if quilt is installed.

==Setup Procedure (Scripted)==
The process of setting up quilt has been scripted. The script performs the following actions:
* Installs (or upgrades) git and any dependencies
* Installs (or upgrades) quilt (actually quilt-lite, a version of quilt that does not depend on perl) and any dependencies
* Configures quilt to store patches in /opt/src/patches
* Creates (or updates) a local clone of the webos-internals modifications repository

Each step is only performed if necessary. Please note that ipkg-opt needs to be installed. The instructions are found [[Next_steps|here]].

To get run the script, log into your Pre, gain root privileges and run the following commands:
<pre><nowiki>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</nowiki></pre>

==Setup Procedure (Manual Process)==
(Note: Even though you may have previously installed the optware quilt patch manager, it won't damage anything to follow the Setup procedure. Alternatively, if you KNOW FOR SURE these are installed and your packages are up-to-date, you can skip to Importing and Applying Patches).

* Log into your Pre, and gain root privileges. (Note: This command is not required when using the emulator)
<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode
<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt-lite' package, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt-lite git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:
<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:
<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Delete any existing webos-internals modifications directories
<pre><nowiki>
rm -rf /opt/src/modifications
</nowiki></pre>

* Clone the webos-internals modifications repository:
<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

==Importing and Applying Patches==

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>
** If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

** Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.
<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch
<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
# Use this to push all patches at once.
quilt push -a
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

==Listing Applied Patches==
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt applied
</nowiki></pre>

==Removing All Patches==

Before you accept an over-the-air (OTA) update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

==Reapplying all patches==

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:
<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

==Quilt Commands==

Other commands when using Quilt-Lite:

Please feel free to add/edit this section. I am not an expert, these are commands that I found by accident when i misspelled delete.

<pre><nowiki>
quilt
add
applied (shows applied/installed patches)
delete (removes a patch from quilt series ex: quilt delete *name of patch*)
diff
edit
files
fold
fork
graph
grep
header
import (downloads patch from git ex: quilt import *name of patch*)
mail
new
next
patches
pop
previous
push (installs patches from quilt series one at a time. quilt push -a installs all patches)
refresh
rename
revert
series (shows all downloaded patches.)
setup
snapshot
top
unapplied
upgrade

</nowiki></pre>

==Information for developing patches==

===Getting Authenticated with gitorious.org===
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next, you'll need to create a public/private key pair, and the easiest way to do this is with openssh. If you want to create a pair with windows, there are PuTTYgen/Pageant instructions below under "Alternate Windows Method", but the following may be easier. After you generate a public key you'll share it with gitorious.org; your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # *see Note Below
sudo ssh-keygen -t rsa # follow the prompts, ensure you're saving to /var/home/root/.ssh
cat /var/home/root/.ssh/id_rsa.pub # copy the output and paste it into gitorious key manager
</nowiki></pre>
<nowiki>*</nowiki>There's been some work to get dropbear working, but this tutorial assumes you have openssh installed. For information about dropbear and ssh keys, see [http://tumblelog.jauderho.com/post/151678345/using-dropbear-with-git this page]
* Don't forget to upload your public key from the last statement above to gitorious.org

Next, you'll need to ensure you have your environment properly configured.

<pre><nowiki>
echo $GIT_SSH # Should be /opt/bin/openssh-ssh
</nowiki></pre>

If the output of this command are anything other than /opt/bin/openssh-ssh, you'll need to update /etc/profile.d/optware. Add

<pre><nowiki>
export GIT_SSH=/opt/bin/openssh-ssh
</nowiki></pre>

To the top of the /etc/profile.d/optware.

Now you should be able to follow the steps below and contribute your code to gitorious.org.

== Alternate Windows Method ==
The only reasons you might want to pursue this method is if you want to generate a ssh key pair on a Windows box.

Getting your key on window
* Download [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

===Creating a patch===

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

===Pushing the change back to gitorious.org===

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

==Extended, annotated sample session with quilt==
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create '''before''' you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

==Background info==

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

==Script for Updating/Installing Patches==

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
#!/opt/bin/bash

cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

File:5x4-icons.png

2009-10-06T04:59:23Z

Flare576: Screen capture of the new 5x4 icons

Screen capture of the new 5x4 icons

Talk:Removing app install limit in App Catalog

2009-09-30T17:44:57Z

Flare576: New page: I've noticed that with 1.2 I can't even update official apps since I've sideloaded apps beyond the "limit." Any progress on this - It's horrible to have to remove/re-add 10-15 apps just t...

I've noticed that with 1.2 I can't even update official apps since I've sideloaded apps beyond the "limit." Any progress on this - It's horrible to have to remove/re-add 10-15 apps just to update Word Ace or Pandora... Thanks for looking into this Xorg :) -- [[User:Flare576|Flare576]] 17:44, 30 September 2009 (UTC)

Application talk:Preware

2009-09-22T19:18:43Z

Flare576:

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, it may be implemented in a future version of the application.
}}

== Features and Suggestions ==

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Xorg|Xorg]] 16:09, 20 August 2009 (UTC)
* Great that you can no see new/updated apps in 'List of Everything'. Suggest to rename 'List of Everything' to List of Newest/Updated Apps or something else that indicates this is best way to see newest apps (that may not be installed yet).
* Or consider another choice to list only new apps, excluding things already installed.
** The list of everything is called that because in the future it will not list only applications. The list of everything will include patches/themes/whatever else we decide to add to the preware installer. At which point we will add an "All" option to the available applications category list. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)
*** With all the themes rolling in now, it'd be great to have this in the next patch if possible. Totally awesome work so far! --[[User:Flare576|Flare576]] 19:18, 22 September 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Suggestion: --[[User:Cdjh|Cdjh]] 15:54, 30 August 2009 (UTC)
*Add a feature to remove all patches and modifications to webos before and webos update. Sort of a "Get me ready for and update" button. This would allow the user to remove all these patches such as the virtual keyboard with one button to update webos without fear. One button to add them back after the update would be cool too

Suggestion: [[User:StoneRyno|StoneRyno]] 21:05, 30 August 2009 (UTC)
*Download counts and ratings. The end of the current detail page is ok but feels more like looking at one of the technical detail scenes like the ##DEBUG# scene. I think that info can be cleaned up to look more presentable, small font size and put version last update and size in a bar near the top of the page like seen in the official app catalog.

Suggestion: [[User:Hmagoo|Hmagoo]] 11:30, 4 September 2009 (UTC)
*We're in need of a workaround for the limit on installable apps via the app catalog. Preware gets around this but also, in the process, adds to the number of installed apps as seen by the App Catalog, et al. What would be a useful feature is to be able to uninstall hunks of apps previously installed by Preware in an effort to make apps installable via the App Catalog. This would be a temporary removal as we would desire reinstalling the homebrews after using the App Catalog.
**Caveats: Homebrew apps that use databases, and installed/downloaded files would not be removed without reducing their usability, So we would want to exclude on a case by case basis or with the use of flags?
**Preware is great in keeping track of what is installed and which version, would be great to see something like this added so that we can use the App Catalog and install piles of Homebrews. (smile)

Talk:Preware Design

2009-08-24T13:53:14Z

Flare576: /* Features and Suggestions */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, you may implement it on the application page.
}}

== Replacing wiki pages? ==

Is this going to replace the application pages in this wiki? I think it should.
—[[user:X1011|X1011]] 22:31, 25 July 2009 (UTC)

This has not been decided yet, but in all odds it eventually will. --[[User:Templarian|Templarian]] 03:18, 3 August 2009 (UTC)

== protection ==
'''Page is now unprotected and moved to the application name space.'''[[User:Rboatright|rboatright]] 04:24, 30 July 2009 (UTC)

why is this page protected? I think we should follow [[wikipedia:WP:NO-PREEMPT]].
—[[user:X1011|X1011]] 22:31, 25 July 2009 (UTC)

Quality control by sysops. --[[User:Templarian|Templarian]] 22:44, 27 July 2009 (UTC)

are you saying that only sysops are capable of quality?

also, it says it's a discussion page. how can it be if it's protected?

—[[user:X1011|X1011]] 07:30, 29 July 2009 (UTC)

I forgot to unprotect the preware page when I moved it -- sorry [[User:Rboatright|rboatright]]

== XML feeds ==

* instead of <firmware>:
<source lang='xml'>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
</source>
* maintainer:
<source lang='xml'>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
</source>
* should a category have an id? everything else does.
* in the review, you have the type in the message tag, but in the comment, you have it in the messages tag.
* <comment> should be <text> or <body>
* in <comment>, what do you mean by 'split it somewhere'?
* does <code>preware.org/feed/xml/type/</code> have a meaning? if not, we should use:
<source lang='text'>
preware.org/feed/xml/application/23/
preware.org/feed/xml/plugin/23/
</source>

—[[user:X1011|X1011]] 09:27, 29 July 2009 (UTC)

- Agreed with all suggestions in this section, and they are now reflected in the article. --[[User:Templarian|Templarian]] 02:33, 3 August 2009 (UTC)

For "preware.org/feed/xml/application/23/" since it shares id's, couldn't it just be "/xml/23/". --[[user:Templarian|Templarian]]

== GUI Addition: Version# and Changelog ==

Idea: Add a small "Details" or "+" button on the app and plugins pages. It can go at the end of the description, or possibly to the right of the very large "Install/Delete" button. It may not be wanted though. I know we don't want to show version numbers on the app page, but I'd love to have some way to access the version number and changelog from within the Preware app, even if its semi-hidden. I read the results of Rick's papercraft gui study, and agree with a lot of the comments, but I still feel like this is something that would be helpful to have available somewhere in the app, even if it isn't immediately obvious how to get to it (since its not something that is necessarily required by the average user). --[[User:Zinge|Zinge]] 02:29, 3 August 2009 (UTC)

Changes reflected in the Preware Application mockup image. --[[User:Templarian|Templarian]] 02:46, 3 August 2009 (UTC)

Looks good, but we may want to change the "list" icon to something that look less like "go back to the app list". My suggestions are- are lowercase "i" or the "+" symbol. Any better ideas? --[[User:Zinge|Zinge]] 02:56, 3 August 2009 (UTC)

lowercase i is the correct icon, I changed it to reflect that in the mockup. --[[User:Templarian|Templarian]] 03:11, 3 August 2009 (UTC)

== button resizing ==

For the first screenshot I think it would be best if we made it so that the buttons resize. No scrolling in any form even if there notifications below it. --[[user:Templarian|Templarian]]

== License id ==

Do you think we should put the versions next to all of them to be consistent? --[[User:Templarian|Templarian]] 02:33, 5 August 2009 (UTC)

what is the purpose of having a license id? —[[user:X1011|X1011]] 04:51, 5 August 2009 (UTC)

Since the Preware app is listed for Open Source projects it was mentioned it would be nice to have it listed on the information button (which may be moved to a drop down at the right of the top title). Really treating the info screen as the information normal users do not care about seeing immediately. The license id is just a standard id that will never change. --[[User:Templarian|Templarian]] 14:12, 5 August 2009 (UTC)

are you saying the name of a license is likely to change? i doubt that. if you must have a license id, though, just make it a number like all the other ids. —[[user:X1011|X1011]] 04:35, 6 August 2009 (UTC)

Yea, probably change that to a number sometime. --[[User:Templarian|Templarian]] 05:29, 6 August 2009 (UTC)

--[[User:Flare576|Flare576]] 13:53, 24 August 2009 (UTC)== Features and Suggestions ==

Adding some suggestions... --[[User:Czar|Czar]] 14:16, 17 August 2009 (UTC)
* Remove (or mark) already installed applications in the Available Applications category.

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.
** The popup dialog is temporary until the service can supply progress of the action. When there is a progress bar, the popup will no longer be needed. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... -- (xorg)
* Option to sort complete app list by newest first (as filecoaster does) (update now has this)
* Descriptions of each app
** Descriptions will come when the feed supports them. (hopefully soonish) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe installed applications in list to uninstall
** Is there a time where you want to remove multiple apps? (multiple as in more then a couple.) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... [[User:Flare576|Flare576]] 17:49, 19 August 2009 (UTC)
* In addition to xorg's suggestion: screen shots are also supported by filecoaster; perhaps standardizing description/screen shots in the repositories?
** Screenshots will come when the feed supports them. (hopefully soonish) --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Xorg|Xorg]] 16:09, 20 August 2009 (UTC)
* Great that you can no see new/updated apps in 'List of Everything'. Suggest to rename 'List of Everything' to List of Newest/Updated Apps or something else that indicates this is best way to see newest apps (that may not be installed yet).
* Or consider another choice to list only new apps, excluding things already installed.
** The list of everything is called that because in the future it will not list only applications. The list of everything will include patches/themes/whatever else we decide to add to the preware installer. At which point we will add an "All" option to the available applications category list. --[[User:Oil|oil]] 20:44, 20 August 2009 (UTC)

Adding some suggestions... --[[User:Decimation|Decimation]] 12:30, 20 August 2009 (EST)
* Adding an "Update All" button to the update menu would be cool.. convenience is key ;)

Adding some suggestions... -- [[User:Flare576|Flare576]] 13:53, 24 August 2009 (UTC)
* Since "List of Everything" holds more than just "normal apps," it would be important for there to be a way to see "All Available Apps." I suggest removing the first page of "genres" under "Available Applications," and having the first page people see be the secondary page (ie: the one after you choose a genre) with the default Genre of "All." Then, if desired, people can use the drop down to drill into an area they care about.
<nowiki>
    If there is a concern about loading up hundreds of apps when first opening that scene (and there should be concern), or if the "Normal User" likes genre filtering, perhaps leave the initial Genre page as it is, but simply add an "All" Genre so that folks that check daily can just see what's been added/updated. Maybe there needs to be a paging system so that the device only has to worry about 100 apps at a time? Or maybe not if you guys use a clever div/hide system, I don't know :)
</nowiki>

== Issues 0.5 first public release ==
* Was working fine first several updates over several hours. Now for last day, just get spinning 'Updating' at startup. (xorg)

* seems 0.5.1 corrected that.

* I've updated to 0.5.1 and it ran first time ok. Second time get continuous spinning update. (xorg)

* Reinstalled, now working again - for now. (xorg)

Application talk:Terminal

2009-08-20T17:51:09Z

Flare576: /* Bugs: Paste? */

== Bugs: Paste? ==
- Can't seem to figure out how to paste something that was copied from another app/msg/web site. The old paste shortcut of "Gesture + V" doesn't work (because its being used for other things). I tried to "Insert" shortcut, but it didn't do anything.
--[[User:Zinge|Zinge]] 08:58, 7 August 2009 (UTC)

- Tossing in another request to get a solution in for pasting: as it stands there is no way to get some symbols (specifically curly braces) into the terminal - tough to do a rescan :) -- [[User:Flare576|Flare576]] 17:51, 20 August 2009 (UTC)

== Ansi bugs ==
Scrolling in BX is fixed. Thanks! terminal is a killer app.

Still have a bug when typing a message in IRC that's long enough to require horizontal scrolling. Instead of scrolling it does weird single-char newlines and status bar is lost.

Also when using arrow keys to move around in vim (with TERM=linux and syntax/color on), what seems to be ansi color code artifacts are printed. Arrows do work, but it's unusable due to artifacts. --[[User:T3rmin|T3rmin]] 18:05, 14 August 2009 (UTC)

== New Version Changelog? ==

The newest version from the feed seems to be 0.1.6. Anybody know what changes have been made? --[[User:Zinge|Zinge]] 19:30, 1 August 2009 (UTC)

== Font Size Feature Request ==
Well done! I notice that there are two fonts, normal and small. Would it be possible to add an intermediate font size? The 40 col is to large for seeing much and the 80 col is far to small. Would it be possible to have a ~60col font? --[[user:Dreadchicken|Dreadchicken]]

: Also, could you add a "large" font size? I don't like the small sizes for little one-line commands (wget, etc). I guess ultimately it'd be nice to have in that combo box a handful of sizes. Thank you so much for the mind-blowing awesomeness of this app, by the way. [[User:Michaelb|Michaelb]] 18:46, 17 August 2009 (UTC)

== Broadcast messages when phone sleeps/wakes ==

Has anyone figured out how to stop the broadcast messages generated on the Terminal when the phone sleeps and wakes? They clobber whatever's on the screen if you happen to turn off the phone while Terminal is open.

Other than this, great app. I'm eternally grateful. :) --[[User:zorinlynx|zorinlynx]]

I'm not sure if this will help, but there is a quilt patch in the gitorious modification for disabling some messages to the log. http://gitorious.org/webos-internals/modifications/blobs/master/luna/quiet-powerd-messages.patch --[[User:Plee3|plee3]] 21:05, 3 August 2009 (UTC)

Thank you! This has resolved the issue. --[[User:Zorinlynx|Zorinlynx]] 21:24, 3 August 2009 (UTC)

== Brackets ==
Any way to enter < or > chars? Kinda tough to dump output to a file without.
--[[User:Daemon|Daemon]]

These characters have not been implemented yet, but as a work-around, you can use tee or tee -a.
--[[User:JackieRipper|JackieRipper]]

==Colors Sticking, and Permissions==
Would it be possible to set the foreground color permanently, so that I don't havve to set it each time I log in?

I've also noticed that when I open the application, sometimes it automatically logs me in as root. How can I disable this?

Thanks for your awesome work!! -[[User:Hopspitfire|hopspitfire]] 05:47, 16 August 2009 (UTC)

I think one solution for disabling root access is to go into
/var/usr/palm/applications/org.webosinternals.terminal/app/controllers
and edit '''session-assistant.js'''
Search for the line that reads
this.termplugin.start("root");
and change 'root' to your username.
[[User:Clebio|Clebio]] 20:57, 16 August 2009 (UTC)

:That worked perfectly! Thank you.
:I'm still having trouble with the colors sticking, now when I change a color in the preferences menu and go back to the terminal, the entire screen freezes (It responds to <orange><sym><r>, but won't show the boot logo as it's shutting down, and ssh responds normally). Is this a bug? -[[User:Hopspitfire|hopspitfire]] 04:13, 17 August 2009 (UTC)
:: I get this too when I try to change preferences. [[User:Michaelb|Michaelb]] 18:51, 17 August 2009 (UTC)
: The problem has been fixed after the new update (0.1.9), THANKS! -[[User:Hopspitfire|hopspitfire]] 21:00, 19 August 2009 (UTC)

Terminal displays blank screen after install
----

It will display nothing that I type, I have tried rebooting the phone with no luck. I did see an message that looked like an error during the install:

Configuring org.webosinternals.termplugin
(offline root mode: not running org.webosinternals.termplugin.postinst)

Could the offline root mode error above be causing this? I was not in Dev mode when I installed this, should I have been?

==Curved mask blocks text on screen corners==

There used to be padding on the top and bottom of the screen to keep the curved corners of the mojo view from blocking text. Why were they removed? --[[User:Zorinlynx|Zorinlynx]] 02:12, 20 August 2009 (UTC)

Talk:Preware Design

2009-08-19T17:49:02Z

Flare576: /* Features and Suggestions */

{{box | color = #cdf |
This is a discussion page. Create a new topic with the '+' tab. Sign your comments using the signature button or by typing <code><nowiki>~~~~</nowiki></code>. If your suggestion reaches consensus, you may implement it on the application page.
}}

== Replacing wiki pages? ==

Is this going to replace the application pages in this wiki? I think it should.
—[[user:X1011|X1011]] 22:31, 25 July 2009 (UTC)

This has not been decided yet, but in all odds it eventually will. --[[User:Templarian|Templarian]] 03:18, 3 August 2009 (UTC)

== protection ==
'''Page is now unprotected and moved to the application name space.'''[[User:Rboatright|rboatright]] 04:24, 30 July 2009 (UTC)

why is this page protected? I think we should follow [[wikipedia:WP:NO-PREEMPT]].
—[[user:X1011|X1011]] 22:31, 25 July 2009 (UTC)

Quality control by sysops. --[[User:Templarian|Templarian]] 22:44, 27 July 2009 (UTC)

are you saying that only sysops are capable of quality?

also, it says it's a discussion page. how can it be if it's protected?

—[[user:X1011|X1011]] 07:30, 29 July 2009 (UTC)

I forgot to unprotect the preware page when I moved it -- sorry [[User:Rboatright|rboatright]]

== XML feeds ==

* instead of <firmware>:
<source lang='xml'>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
</source>
* maintainer:
<source lang='xml'>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
</source>
* should a category have an id? everything else does.
* in the review, you have the type in the message tag, but in the comment, you have it in the messages tag.
* <comment> should be <text> or <body>
* in <comment>, what do you mean by 'split it somewhere'?
* does <code>preware.org/feed/xml/type/</code> have a meaning? if not, we should use:
<source lang='text'>
preware.org/feed/xml/application/23/
preware.org/feed/xml/plugin/23/
</source>

—[[user:X1011|X1011]] 09:27, 29 July 2009 (UTC)

- Agreed with all suggestions in this section, and they are now reflected in the article. --[[User:Templarian|Templarian]] 02:33, 3 August 2009 (UTC)

For "preware.org/feed/xml/application/23/" since it shares id's, couldn't it just be "/xml/23/". --[[user:Templarian|Templarian]]

== GUI Addition: Version# and Changelog ==

Idea: Add a small "Details" or "+" button on the app and plugins pages. It can go at the end of the description, or possibly to the right of the very large "Install/Delete" button. It may not be wanted though. I know we don't want to show version numbers on the app page, but I'd love to have some way to access the version number and changelog from within the Preware app, even if its semi-hidden. I read the results of Rick's papercraft gui study, and agree with a lot of the comments, but I still feel like this is something that would be helpful to have available somewhere in the app, even if it isn't immediately obvious how to get to it (since its not something that is necessarily required by the average user). --[[User:Zinge|Zinge]] 02:29, 3 August 2009 (UTC)

Changes reflected in the Preware Application mockup image. --[[User:Templarian|Templarian]] 02:46, 3 August 2009 (UTC)

Looks good, but we may want to change the "list" icon to something that look less like "go back to the app list". My suggestions are- are lowercase "i" or the "+" symbol. Any better ideas? --[[User:Zinge|Zinge]] 02:56, 3 August 2009 (UTC)

lowercase i is the correct icon, I changed it to reflect that in the mockup. --[[User:Templarian|Templarian]] 03:11, 3 August 2009 (UTC)

== button resizing ==

For the first screenshot I think it would be best if we made it so that the buttons resize. No scrolling in any form even if there notifications below it. --[[user:Templarian|Templarian]]

== License id ==

Do you think we should put the versions next to all of them to be consistent? --[[User:Templarian|Templarian]] 02:33, 5 August 2009 (UTC)

what is the purpose of having a license id? —[[user:X1011|X1011]] 04:51, 5 August 2009 (UTC)

Since the Preware app is listed for Open Source projects it was mentioned it would be nice to have it listed on the information button (which may be moved to a drop down at the right of the top title). Really treating the info screen as the information normal users do not care about seeing immediately. The license id is just a standard id that will never change. --[[User:Templarian|Templarian]] 14:12, 5 August 2009 (UTC)

are you saying the name of a license is likely to change? i doubt that. if you must have a license id, though, just make it a number like all the other ids. —[[user:X1011|X1011]] 04:35, 6 August 2009 (UTC)

Yea, probably change that to a number sometime. --[[User:Templarian|Templarian]] 05:29, 6 August 2009 (UTC)

== Features and Suggestions ==

Adding some suggestions... --[[User:Czar|Czar]] 14:16, 17 August 2009 (UTC)
* Remove (or mark) already installed applications in the Available Applications category.

Adding some suggestions... --[[User:Decimation|Decimation]] 15:14, 17 August 2009 (EST)
* Show a progress bar or some sort of notification of the download/installation progress of an app..it would really be nice to have some feedback after clicking install.
* Change the pop up dialog when an app is installed/removed... it's kinda ugly. Maybe show a notification at the bottom? That would be pretty cool.

Adding some suggestions... -- (xorg)
* Option to sort complete app list by newest first (as filecoaster does)
* Descriptions of each app

Adding some suggestions...for way into the future -- (s4mb4)
* a process that would hook into the notification system to notify of available updates.

Adding some suggestions... -- [[User:Tlp|Tlp]] 23:30, 18 August 2009 (UTC)
* Swipe listed applications to delete

Adding some suggestions... [[User:Flare576|Flare576]] 17:49, 19 August 2009 (UTC)
* In addition to xorg's suggestion: screen shots are also supported by filecoaster; perhaps standardizing description/screen shots in the repositories?

Categories for available applications! And thanks for this awesome app! [[User:Clebio|Clebio]] 13:10, 19 August 2009 (UTC)

== Issues 0.5 first public release ==
* Was working fine first several updates over several hours. Now for last day, just get spinning 'Updating' at startup. (xorg)

* seems 0.5.1 corrected that.

* I've updated to 0.5.1 and it ran first time ok. Second time get continuous spinning update. (xorg)

* Reinstalled, now working again - for now. (xorg)