WebOS Internals - User contributions [en]

User:AlisonW

2011-08-29T12:26:17Z

AlisonW:

'''[http://twitter.com/#!/AlisonW @AlisonW]'''

* Owner of original Pre ''(updated to WebOS 2.1.0)'' and TouchPad 32Gb ''(WebOS 3.0.2)''

Talk:Changing keyboard layout on Touchpad

2011-08-29T12:21:57Z

AlisonW: Cursor keys

== Cursor keys ==

Thanks for this; one thing I very quickly realised was the most amazing omission from the TP keyboard was any way of moving the cursor (especially if you mis-type a long web address), specifically [home] [end] [->] and [<-] options. I had been wondering whether the layout itself could be amended to insert a generic ''cursor-move'' key (pref by reducing the width of the space bar and adding [<-] and [->] under the 'n' and 'm' keys, with shift giving the [home] and [end], but the info here suggests that may not be possible. Having other options on the [Tab] key might be? Anyway, anyone else looking at possible ways to add these oh-so-necessary functions? --[[User:AlisonW|AlisonW]] 12:21, 29 August 2011 (UTC)

Application talk:MetaDoctor

2011-03-07T17:53:15Z

AlisonW: /* Ubuntu */ new section

== How to change a provider's DB-entry so 3G data can be used on the Pre ==

This is a bit off-topic, and should be either removed completely or replaced by a link to [[How to solve 3G data problems]], IMHO.
--[[User:Mephinet|Mephinet]] 12:07, 8 January 2011 (UTC)

== Ubuntu ==

To clarify one thing, one my Kubuntu (ubuntu with KDE front-end) java wouldn't start with a <code>Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.</code> but it has worked fine (albeit with different issues!) on my ubuntu (with Gnome) netbook. --[[User:AlisonW|AlisonW]] 17:53, 7 March 2011 (UTC)

Portal:Carriers

2009-10-27T00:19:47Z

AlisonW: /* Name (GSM) */ updating

==United States==
===Sprint (CDMA)===

Sprint is the only carrier at the moment, and is available in the USA at the moment.

==Europe==
===Name (GSM)===
*Germany: Telefónica
*Ireland: Telefónica (O2 brand)
*Spain: Telefónica
*UK: Telefónica (O2 Brand)

Next steps

2009-10-26T23:06:58Z

AlisonW: /* Installing Optware in the Emulator? */ how

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

Note that using the WiFi connection for the above steps is to be highly recommended over the 3G or GSM options, which are reported as sometimes failing. (Turn on aeroplane mode then turn on and connect to WiFi)

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your Pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addess. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (which will be located in /opt/bin/bash, once you've completed the quilt install procedure above), you will have to [http://www.webos-internals.org/wiki/Setup_Bash create] an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.

Next steps

2009-10-26T23:05:36Z

AlisonW: gr.

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

Note that using the WiFi connection for the above steps is to be highly recommended over the 3G or GSM options, which are reported as sometimes failing.

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your Pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addess. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (which will be located in /opt/bin/bash, once you've completed the quilt install procedure above), you will have to [http://www.webos-internals.org/wiki/Setup_Bash create] an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.

Next steps

2009-10-26T23:01:38Z

AlisonW: add wifi not 3g preference

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

Note that using the WiFi connection is to be highly recommended over the 3G option, which is reported as sometimes failing.

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your Pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addess. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (which will be located in /opt/bin/bash, once you've completed the quilt install procedure above), you will have to [http://www.webos-internals.org/wiki/Setup_Bash create] an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.

User:AlisonW

2009-10-26T22:25:25Z

AlisonW: create

@AlisonW

Talk:Portal:Patches to webOS

2009-10-26T22:24:59Z

AlisonW: New section: Re WebOS versions

== catagories ==
we have ten catagories for webOS apps
do we need to catagorize these so that they aren't one giant long list?
[[User:Rboatright|rboatright]] 20:30, 28 July 2009 (UTC)

== separate pages ==
It may be beneficial to create separate pages for each patch. For example, the Camera Modifications & Additions page contains multiple patches, two distinct countdown timers, Shutter Sound On/Off Button. I have the Shutter Sound On/Off Button installed, and it's working on 1.1.0, but it looks like the count-downs do not (I haven't tried, so I can't say for sure).
[[User:JackieRipper|JackieRipper]]

: I agree. Each mod should be split onto it's own page. [[User:Rboatright|rboatright]] 15:39, 29 July 2009 (UTC)
: I split the pages with multiple modifications and added their links to the article. [[User:Hopspitfire|hopspitfire]] 17:41, 29 July 2009 (UTC)

== Editing and new pages ==
Users editing this page, please keep the columns organized alphabetically. [[User:Hopspitfire|hopspitfire]] 06:50, 1 August 2009 (UTC)

At the top of each new Patch page, please put:

<pre><nowiki>
{{template:patch}}
</nowiki></pre>

This will make the wiki much more cohesive. -[[User:Hopspitfire|hopspitfire]] 09:07, 3 August 2009 (UTC)

== naming ==

we need a better naming scheme for patches. "Patch blah blah" does not make sense as an article title. here are some options:
* just the name of the patch. i think this is the best option. you can still organize them using [[wikipedia:Wikipedia:Categorization|categories]] or that template you seem to be fond of.
* "Patches/Name of Patch". this will give you a link back to the Patches page on each of these pages.
** you may also extend this to "Patches/Application/Name of Patch"
* "Patch: Name of Patch"
—[[user:X1011|X1011]] 10:00, 3 August 2009 (UTC)

I've tried using colons, but that makes the patch unsearchable. Using a "/" is also avoided [[User_talk:Hopspitfire#Porting_pages|read here]], therefore I changed them all to Patch [application] [description]. Using only the name of the patch (example: "Force Offline Send Without Dialog") creates clutter and confusion without specifying what it is (a Patch). Furthermore, we need to specify what application it actually patches so that people can look at a glance and know exactly what it is: Patch Messaging Force Offline Send Without Dialog. Also, have a look at the source code of the Patches Portal, it's much cleaner now that I've renamed all the patches. -[[User:Hopspitfire|hopspitfire]] 20:46, 3 August 2009 (UTC)

i think templarian just meant not to use '/' as part of the title of a regular article so as not to unintentionally create a [[metawikipedia:Help:Link#Subpage feature|subpage]].

we can use the patch template to organize the articles and prevent confusion. we can add a parameter to the template to specify which application the patch is for. we can also add a patch category and an application-specific category based on the parameter, so that any article using the template will automatically be included in those categories.

not sure how using only the name creates clutter; i think the opposite is true: that adding extra prefixes clutters the title of an article.

—[[user:X1011|X1011]] 09:30, 4 August 2009 (UTC)

== Quilt incorporation ==

It seems like people have abandoned quilt. Making all these modifications and then risking your pre breaking on a software update, or meticulously going in and undoing all the changes you've made before a software update seems like a wasted step in the wrong direction. There is also no way to to distinguish in Quilt, which patches are working in the current version of webOS you have, which kinda goings along with the naming topic above.
--[[User:S4rs|S4rs]] 18:06, 3 August 2009 (UTC)

agreed; a wiki is not a good software repository. not sure i can help, though; i haven't started using Quilt yet. —[[user:X1011|X1011]] 09:36, 4 August 2009 (UTC)

== Are more patches 1.2.1 compatible than are shown? ==

These patches are listed as not yet being 1.2.1 compatible but are'nt they in the 1.2.1 autopatch feed for Preware and WOQI?
*Camera: Shutter Sound On-Off Button
*Clock: Enabling the Hidden Theme
*Messaging: Change "Enter Key" To Create Newline
*Messaging: New Cards For Each Conversation
*Messaging: Adding Timestamps to All Received Messages
*Tasks: Always Show Details of New Tasks
*Browser: Delete Individual History Items
*Calendar: Show All-Day Events in Month View
*Camera: Using Volume Buttons to Take a Picture
*Email: Delete All
*++Messaging: Force Offline Send Without Dialog
*Messaging: Forward Messages
*Messaging: Jump Forward, Backward One Word at a Time
*Messaging: Landscape Orientation
*Messaging: Message Sound
*++PDF Viewer: Change Orientation
*Phone: Disable Various Call Sounds

Note: The Music Player: Bookmarking does nto work with classical or opera genres etc. and has not been made obsolete.
[[User:Milominderbinder|Milominderbinder]] 03:49, 7 October 2009 (UTC)

The listings are a bit confusing to follow with regards to compatibility with versions. Should a patch be listed multiple times, once for each version that it works with, or if the patch works with the current version, do we not care about the older versions that it may have worked with? I would propose reorganizing the patch list as a table, with all the patches listed then have a column for each version, and put "OK", "N/A", or some other designation in each respective location. It'd also be easy to add to when new versions of WebOS come out. [[User:Roto|Roto]] 23:37, 10 October 2009 (UTC)

== Creating a patch ==

I know this probably isn't the right place, but I'm trying to create a patch to submit for inclusion in Preware. I'm comfortable with the Linux command line and creating standard patch files. I need to know if there's a special format or header that I need to add to the standard patch file. I also need to know if patches are still applied with / as the working directory, and how to submit the patch for inclusion in Preware once it's been tested. Thanks.

== Re WebOS versions ==

I note that in the UK (and, I believe, the rest of Europe) we are being ''held back'' (as it were) from the latest WebOS releases currently. As such, might there be sense in listing which apps ''will'' work this side of the pond even though not 'that' side. --[[User:AlisonW|AlisonW]] 22:24, 26 October 2009 (UTC)