WebOS Internals - User contributions [en]

Google Latitude

2010-01-31T00:09:05Z

X1011:

I was rather surprised to find that Google Latitude works great on the Prē if and only if you know this magic invocation:

http://maps.google.com/maps/m?mode=latitude

Why the hell doesn't http://google.com/latitude mention this? It's a mystery.

If you plug in the magic invocation, it pops open your Google Maps
application in Latitude mode. I bookmarked it. I would guess there's a
way to start up the Google Maps application in Latitude mode directly, but
I can't figure it out.

Next steps

2009-12-30T08:09:03Z

X1011: deprecated template

{{deprecated|
If all you want to do is install an SFTP server, then just go to the Optware section in [[Preware]] and install it from there.
}}

=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.'''
''' This is confirmed to work with webOS 1.3.1 '''
''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)

As part of this process, you will be creating an unprivileged user account that you can later use to log in to your device. The username that you pick must be lowercase, longer than 3 characters, contain at least one letter, and may only be letters, numbers, dashes (-), and underscores (_). Once you enter your username, you will enter a password. Make sure to pick a strong password for your own security. If you make a typo when entering your password, don't panic. Once the script has finished running, simply type:

<div style="font-size:100%;">
<source lang=bash>
passwd username
</source></div>

"username" should, of course, be the username that you created. This will allow you to re-enter your password correctly.

==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>
**[[Tutorials_Linux_DDNS_for_EVDO|Dynamic DNS]] is helpful for consistently accessing the Pre over EVDO with a simple name.
*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.

=Install Preware=
To start getting the most out of your new webOS Device you should install Preware. Continue on to the [[Application:Preware|Preware]] page. There you will see all the ways to install Preware on your device. Including stand-alone installers, package installation and an automated script like you did here.

Talk:Main Page

2009-12-08T22:20:04Z

X1011: /* Article organization */

This page is for discussion of the Main Page. For discussion of general policies, see [[WebOS Internals talk:Policies and guidelines]]

== Beta Main Page ==

This isn't in use right now, but when It comes the time to swap out the main page again.

[[Main_Page_beta]]
[[Template:Page-main-beta]]

== Article title capitalization ==

Are we sure we want to use title case for article titles? [http://en.wikipedia.org/wiki/Wikipedia:Mos#Article_titles Wikipedia uses sentence case], and i think it looks much better.
—[[User:X1011|X1011]] 06:35, 20 July 2009 (UTC)<br>
Also, same question for section headings —[[user:X1011|X1011]] 12:45, 20 July 2009 (UTC)

I think it usually works out good since a lot of pages are displayed as: <nowiki>[[Page Name]], also with the headers of course don't uppercase "a", "and", etc.</nowiki> --[[User:Templarian|Templarian]] 13:21, 20 July 2009 (UTC)

'''from #webos-internals:'''
<source lang="text" enclose="div">
Rick_: X1011, the pages-to-be-moved page on the new wiki uses the PAGE NAME as a link to create the page on the new wiki rather than the old page link from the old wiki.
Rick_: In general _most_ of them are fine.
Rick_: We prefer "Page About Smashing the Pre" to "Page about smashing the Pre" because it _is_ the title of the page, and so _should_ be in title case.
Rick_: or that's the consensus of the team to date.
</source>

== Registration error warning ==

Instead of having the warning about getting an error on confirming your registration on the main page, could an admin put it on the [http://www.webos-internals.org/index.php?title=Special:Userlogin&type=signup create account page]? —[[user:X1011|X1011]] 01:58, 23 July 2009 (UTC)

The Special:* namespace pages are not editable. -- Rod

Maybe not inside the wiki editing system, but surely it's editable at some level. I think we should put user experience before "that's too hard to do". —[[user:X1011|X1011]] 23:55, 23 July 2009 (UTC)

Agreed - I'll look into it. -- Rod

==Front page mispelling and Description Addition==

There's a mispelling on the top of the front page (I don't have rights to edit this page)

"Thank you for heling us convert all the pages from the old wiki!"

should be:

"Thank you for hel'''p'''ing us convert all the pages from the old wiki!"

Also, can you add something referencing "Kernels" in the development tools' description?

-[[user:hopspitfire|hopspitfire]] 05:33, 23 July 2009 (UTC)

Added kernels to the list --[[User:Templarian|Templarian]] 19:23, 27 July 2009 (UTC)

== Protection ==

Why is Main Page protected? It shouldn't be protected unless it is vandalised; see [[wikipedia:WP:NO-PREEMPT]]. As seen in the above section, regular people have useful contributions. —[[user:X1011|X1011]] 21:52, 24 July 2009 (UTC)

I disagree. We're getting 20K page views a day. Let's keep the main page clean and functonal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the main page has 14,428 total views to date. we shouldn't assume our users will make it dirty and unfunctional before we even give them a chance. Wikia has [[wikia:c:help:help:main page#What if I don't want visitors to edit my main page?|a good writeup]] on why the main page should not be protected.

also, in the future, when you protect a page, please include a note explaining why you are doing so.

—[[user:X1011|X1011]] 08:07, 28 July 2009 (UTC)

The main page is currently editable, was this intentional? [[User:Hopspitfire|hopspitfire]] 07:03, 1 August 2009 (UTC)

Yea, rick only set it to be protected till aug 1st while updates were going on. The idea was so that users wouldn't mess with it as the site was being setup / structured. --[[User:Templarian|Templarian]] 22:42, 2 August 2009 (UTC)

: The idea was that there was a gazillion links on the FRONT page of the old wiki. we wanted the front page of the new wiki to lead to DEPARTMENTS instead of having a zillion links on it. -- that's worked out now, and seems institutionally embedded so why not let the protection expire? [[User:Rboatright|rboatright]] 22:51, 2 August 2009 (UTC)

As many of seen the front page is no longer protected. The edit tab has been hidden, but editing can be easily done by "?title=Main_Page&action=edit". Hopefully this solved any disagreements people may have with the editing/protection of the main page. --[[User:Templarian|Templarian]] 14:24, 5 August 2009 (UTC)

That can be simplified even more just by typing "?action=edit". -[[User:Hopspitfire|hopspitfire]] 21:20, 5 August 2009 (UTC)

== Research/Reference Portal ==

We need to add the Research/Reference portal to the front page. I recommend re-organizing the front page.

I'd start with putting "Getting Started" on the top-middle by itself, then follow the diagram below:

<pre><nowiki>
-------------Getting Started-------------
Linux Apps---Source Patches---Dev Tools
Research-------webOS Apps-----Hardware
Recovery--------SDK Docs------Wiki Help
</nowiki></pre>

We also need an icon for "Research", maybe put a lab suit over Tux with a doctor's mask. What do you think?

I also agree with the post above regarding the unprotection of the front page (at least to autoconfirmed users). -hopspitfire

yes, we need to add a box for the research portal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

As of today all of this has been done (including Tux in a lab coat). --[[User:Templarian|Templarian]] 15:11, 5 August 2009 (UTC)

== featured article ==
I think we need a "featured article" on the main page. Right now, that wuld be
terminal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the featured articles look great. --[[User:Templarian|Templarian]] 13:15, 30 July 2009 (UTC)

== Article organization ==

I noticed that there are a lot of manually maintained lists on this wiki. I'm not sure why the Category system is not being used, since it provides a better way to manage lists. A manually maintained list provides more information such as a summary, but a category is much easier to maintain and the users can browse a category page. Pages such as the [[Portal:webOS_Applications_All]] might be better as a category page. Actually, it looks like [[Special:Categories]] are rarely used. The category system could also compliment the current system as well.
: Any problem if I start adding lots of pages into appropriate categories?

Also, an [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style_%28infoboxes%29 infobox] on certain article types such as applications would help with origination. A script such as the one used on the [http://www.mediawiki.org/wiki/Extension_Matrix Extension Matrix] might eventually be plausible in the future once infoboxes are more commonly used.
: Can I create them?
How zealous about organization is it ok to be?
:[[User:Servel333|Servel333]] 18:59, 8 December 2009 (UTC)

i'm all for both ideas. i tried organizing this wiki at one point but i didn't have time to teach everyone how to properly use a wiki and was also meeting resistance. i never even bothered with the application pages because there were plans to make a proper repo site ([[Preware Design#Site]]). see also [[Talk:Portal:Patches to webOS#naming]] for my suggestions on organizing the patches. —[[user:X1011|X1011]] 22:20, 8 December 2009 (UTC)

Talk:Portal:Patches to webOS

2009-12-08T22:14:24Z

X1011: /* Creating a patch */

== 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. --[[user:Dallashigh|Dallashigh]]

== 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)

Talk:Portal:Patches to webOS

2009-12-08T22:14:03Z

X1011: /* Creating a patch */ sign your comments

== 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. --[[user:Dallashigh|]

== 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)

Meetups

2009-08-23T19:36:22Z

X1011: /* Dallas */ preDevCamp is past

People interested in meeting up should plop in their area and name so when we have critical mass it can be organized.

See also [http://predevcamp.org/ predevcamp.org].

== United States ==

=== Arizona ===
==== Phoenix, AZ ====
# EvanDotPro

=== California ===
==== Fresno ====
# A2NY

==== San Diego/Los Angeles ====
# JonVisc
# seigex (Inland Empire)
# hopspitfire

==== San Francisco/Bay Area/SJ ====
Since Palm, Inc. is located in the Bay Area, Palm employees may join us for some tech talk or tips and tricks.

http://www.meetup.com/palm-webos/

# rulethirty (organizer)
# Robi
# jblebrun
# simplyflipflops
# pEEf
# bzhou (eno in IRC, optware manager)

=== Colorado ===
==== Denver ====
# destinal
# rcanzlovar
# raeb

=== Kentucky ===
==== Cincinnati/NKY ====
# xandrake__
# foamcoretrash

=== Massachusetts ===
==== Boston ====
# nebula (MIT campus area)
# [[User:FreeTim|FreeTim]] (MIT campus area - in Kendall Sq.) Please join us in the [http://www.webosboston.org WebOSBOSTON community - We have monthly meetings.]
# djbclark Danny Clark <dclark@pobox.com> http://pobox.com/~dclark (MIT campus area)
# oc80z (MIT,Central Square for drinks)
# beingboston (Newton, Watertown area. Has T pass, can travel)
# trokair (Waltham area, can travel)
# r3compile
# asedeno (MIT)

=== Minnesota ===
==== Minneapolis/St. Paul ====
# xluryan
# helfire

=== Missouri ===
==== Kansas City ====
# xorg (attending [http://kansascity.predevcamp.org/attendees/ KC predev camp] - a couple dozen have signed up and growing)

=== Nevada ===
==== Las Vegas: [[wikipedia:DEF CON (convention)|Defcon]] 17 ====
# emkman
# pEEf
# destinal
# tharris-

=== New York ===
==== Albany ====
# JackieRipper

=== Oregon ===
==== Portland Area ====
# rck

=== Texas ===
==== Austin ====
# HattCzech
==== Dallas ====
# HebrewzHammer
# [[user:X1011|X1011]] ([[wikipedia:University of Texas at Dallas|UTD]], attended [http://dallas.predevcamp.org/ preDevCamp])

=== Washington ===
==== Seattle Area ====
# tictac
# BurntSky
# meshuga

=== Wisconsin ===
==== Madison ====
# christianwilcox

Meetups

2009-08-23T19:35:49Z

X1011: wiki. you're doing it wrong

People interested in meeting up should plop in their area and name so when we have critical mass it can be organized.

See also [http://predevcamp.org/ predevcamp.org].

== United States ==

=== Arizona ===
==== Phoenix, AZ ====
# EvanDotPro

=== California ===
==== Fresno ====
# A2NY

==== San Diego/Los Angeles ====
# JonVisc
# seigex (Inland Empire)
# hopspitfire

==== San Francisco/Bay Area/SJ ====
Since Palm, Inc. is located in the Bay Area, Palm employees may join us for some tech talk or tips and tricks.

http://www.meetup.com/palm-webos/

# rulethirty (organizer)
# Robi
# jblebrun
# simplyflipflops
# pEEf
# bzhou (eno in IRC, optware manager)

=== Colorado ===
==== Denver ====
# destinal
# rcanzlovar
# raeb

=== Kentucky ===
==== Cincinnati/NKY ====
# xandrake__
# foamcoretrash

=== Massachusetts ===
==== Boston ====
# nebula (MIT campus area)
# [[User:FreeTim|FreeTim]] (MIT campus area - in Kendall Sq.) Please join us in the [http://www.webosboston.org WebOSBOSTON community - We have monthly meetings.]
# djbclark Danny Clark <dclark@pobox.com> http://pobox.com/~dclark (MIT campus area)
# oc80z (MIT,Central Square for drinks)
# beingboston (Newton, Watertown area. Has T pass, can travel)
# trokair (Waltham area, can travel)
# r3compile
# asedeno (MIT)

=== Minnesota ===
==== Minneapolis/St. Paul ====
# xluryan
# helfire

=== Missouri ===
==== Kansas City ====
# xorg (attending [http://kansascity.predevcamp.org/attendees/ KC predev camp] - a couple dozen have signed up and growing)

=== Nevada ===
==== Las Vegas: [[wikipedia:DEF CON (convention)|Defcon]] 17 ====
# emkman
# pEEf
# destinal
# tharris-

=== New York ===
==== Albany ====
# JackieRipper

=== Oregon ===
==== Portland Area ====
# rck

=== Texas ===
==== Austin ====
# HattCzech
==== Dallas ====
# HebrewzHammer
# [[user:X1011|X1011]] ([[wikipedia:University of Texas at Dallas|UTD]], attending [http://dallas.predevcamp.org/ preDevCamp])

=== Washington ===
==== Seattle Area ====
# tictac
# BurntSky
# meshuga

=== Wisconsin ===
==== Madison ====
# christianwilcox

FreeTim Sandbox

2009-08-22T21:27:05Z

X1011: FreeTim Sandbox moved to User:FreeTim/Sandbox: personal sandboxes don't go in the main namespace

#REDIRECT [[User:FreeTim/Sandbox]]

User:FreeTim/Sandbox

2009-08-22T21:27:05Z

X1011: FreeTim Sandbox moved to User:FreeTim/Sandbox: personal sandboxes don't go in the main namespace

==Sandbox Comment==
OK. Erased the previous page. Working on Komodo Edit install docs now. - Tim-<BR><BR>

{{article-two-columns
|width1=60%
|column1=
==Brief Description==
* The Palm Development Kit (SDK) is a free download from Palm
* Komodo Edit is a free cross-platform editor from AciveState
* There is a Komodo webOS Add-on from Templarian to assist the Palm Pre development in this environment to make things easier.
* The Komodo WebOS Add-on features:
** quick project generation
** One button packaging and testing of your projects to the Emulator for testing
*** as well as to the Pre
** One button close and removal of projects from the Emulator
** Integrates JSLint, the Beautifier, and much more!
** Saves valuable time when developing your application for the Palm Pre WebOS.
<BR><BR>Below are specific installation instructions for the Komodo webOS Add-on.<BR><BR>
|column2=
==Add-On Prerequisites==
* Virtual Box
* The SDK (Palm Software Development Kit. - including the emulator.)
* You need [http://www.activestate.com/komodo_edit/ Komodo Edit v.5.1] - select "Try It" to download it and install. (not covered here.)
}}
==Komodo WebOS Add-on Download==
* Middle-click this to open in new tab [http://webos.templarian.com/komodo/ to Download the Komodo webOS Add-on from Templarian HERE.]
**This is the Add-on you'll need for Palm Pre development. Go to this page and view the link to the file.
* Then, RIGHT click the link on his page to the .xpi file itself and do Save-As, save into a folder. <BR><BR>
===Komodo WebOS Add-on Install===
* Run Komodo first.
* Then open the folder where you've saved the Add-On .xpi file
* With both Komodo and the Folder open at the same time, drag-and-drop into Komodo, near the top to the right of Help on the menu bar, below the blue title bar as shown here (the white icon in this image is the dragged-over .xpi file)
[[Image:Komodo1.gif]]
* When you release it will install itself into Komodo.
* If you get a warning about Trusted Source at this point, you must choose Install Now button.
* [[Image:Komodo2.gif]]
* You only need to do this once - future upgrades happen automatically from within Komodo Edit, itself.
* Next Komodo should show the completed install screen
* [[Image:Komodo4.gif]]
* You must choose RESTART NOW for the Add-On to begin running.
<BR><BR>

==Enable the WebOS Add-On==
* While the add-on has a lot of interesting features you will find they are all disabled when you first enter Komodo.
* [[Image:Komodo3.gif]]
* In order to enable it, go into menu item View - and choose WebOS at the bottom.
* Your finished screen shot should look like the below.
* If you can see the options for the Add-On near the bottom, the install worked.
* Future updates are automatic on startup of Komodo!<BR><BR>
[[Image:Komodo5.gif]]
<BR><BR>
===Next===
* Now do the same thing for "Code Intelligence" add-on.
** Download Code Intelligence (-------------- link needed here --------)
* From within Komodo, do menu items
**Edit
**Preferences
**Code Intelligence
***Add an API Catalog > Select the .cix file for Code Intelligence.
<BR>---------Screen Shot Needed Here---<BR><BR

* Link to the next steps - create a blank folder, create a new project, yadda yadda yadda...
* --------- Link more here -----------

<BR><BR>
===Errata===

Application talk:Terminal

2009-08-13T00:02:58Z

X1011: new discussions go at the bottom (old discussions will be archived eventually)

== 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)

== Fullscren (curses?) apps scroll wrong ==
Another quick bug: when running irssi or BX only the first line above the status bar line(s) scrolls. When going between landscape and portrait mode, the screen refreshes properly, but still only one line scrolls in either mode. This is as of 0.1.5. --[[User:T3rmin|T3rmin]] 17:00, 28 July 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]]

== 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]]

Talk:Portal:Research

2009-08-13T00:00:30Z

X1011: section and signature

== Signal strength on pre ==
signal strength on my pre goes up and down while standing in the same place. Also have the 800w and signals side by side with the pre aren't even close. 800w always has more bars. Does anybody know how to fix the pre? --[[user:Grabeard|Grabeard]]

WebOS Internals talk:Policies and guidelines

2009-08-12T05:09:13Z

X1011: /* Proposed: Redirects */

== Proposed: Protection ==

a policy similar to [[wikipedia:Wikipedia:Protection policy]], where pages are only protected if they are repeatedly vandalised or if there is an edit war —[[user:X1011|X1011]] 04:19, 27 July 2009 (UTC)

see also [[wikia:c:help:help:main page#What if I don't want visitors to edit my main page?|Wikia's advice against protecting the main page]] and [[metawikipedia:Protected pages considered harmful]]. —[[user:X1011|X1011]] 03:42, 28 July 2009 (UTC)

It will be noted --[[User:Templarian|Templarian]] 04:06, 28 July 2009 (UTC)

[[Special:Protectedpages]], We only have 3 pages protected, and 2 files. The main page will most likely always be protected, please use the discussion as you are now to point out suggestions. Thanks and hopefully this answers your question. --[[User:Templarian|Templarian]] 13:13, 28 July 2009 (UTC)

we currently have 5 protected pages (one is move-protected only) and 2 protected files.

there is no consensus yet on whether the main page will be protected indefinitely. see [[Talk:Main Page#Protection]].

i have not posed a question. i have proposed a policy. you have not yet stated whether you agree or disagree with it. if you state that you disagree, please explain why.

—[[user:X1011|X1011]] 06:16, 29 July 2009 (UTC)

: Ok, I'll jump in. I think the main page should be protected. I don't know about others, but the main page is our face to the world, and the risk of defacing that exceedsthe value. I am not unaware of the common mistakes described at http://help.wikia.com/wiki/Help:Common_mistakes and am willing to re-consider. But for today, the only argument in the wikia article that is meaningful is the idea that many users will not get beyond the front page and may not even realize that the wiki is editable. While that may have been true some time ago, in this self-selected and computer-literate group we're dealing with, I can't see it. [[User:Rboatright|rboatright]] 14:49, 31 July 2009 (UTC)

if the group we're dealing with is so enlightened, then they should also be less prone to vandalism and more likely to have useful contributions, even for the main page. to my knowledge, there has been no vandalism to this wiki so far. even if something does get messed up, whether with good or bad intentions, it can quickly and easily be fixed. the 1-week protection on the main page has just expired; i say we give it at least a trial and see whether it will get worse or better due to public edits. —[[user:X1011|X1011]] 08:25, 1 August 2009 (UTC)

Are we really expecting non-editor contributions on the front page? If we are seriously expecting that (and there is sufficient structure and instructions on the front page that first-time visitor will not stuff up the formatting, or undo all the collaboration which has occurred so far on the front page look and feel), then I'm happy for it to be unprotected. But I'm skeptical that is the case. Otherwise, we should work how to protect the front page in a way that editors can edit it. [[User:RodWhitby|RodWhitby]] 23:11, 1 August 2009 (UTC)

an editor is anyone who signs up for an account here and makes an edit. i'll assume you're talking about non-admins.

yes, i am expecting non-admins to want to contribute to the main page. [[user:Hopspitfire|Hopspitfire]] made a couple of edits soon after the protection expired, and i expect other users to follow.

—[[user:X1011|X1011]] 02:24, 3 August 2009 (UTC)

I'm referring to the "Editors" group (which is different from Sysops), of which yourself and Hopspitfire are members. I expect that major contributors would be part of that group and exempt from page protection limits. [[User:RodWhitby|RodWhitby]] 02:46, 3 August 2009 (UTC)

i just tried editing a protected page; i cannot. regardless, i still think it's an unnecessary barrier for people who may just want to make a small correction. also, Wikia's point about implying a hierarchy among editors is still valid. —[[user:X1011|X1011]] 03:08, 3 August 2009 (UTC)

I'm happy to trial an unprotected front page, as long as we have the Editors group in place so that protection can be implemented at a moment's notice if there is vandalism without affecting the access of the major contributors if we need to do that. FYI, I'm not sure we've worked out how to allow the Editors group to edit protected pages yet, but that is definitely the intention, and is just awaiting someone working out how to do it. [[User:RodWhitby|RodWhitby]] 03:13, 3 August 2009 (UTC)

BTW, I don't see an edit button on http://en.wikipedia.org/wiki/Main_Page ... that's the example that I think we're following. [[User:RodWhitby|RodWhitby]] 03:14, 3 August 2009 (UTC)

what can sysops do that 'editors' won't be able to, and why have the distinction?

Wikipedia's main page was not protected at first. it was only protected after vandalism became a persistent problem. i think that's the model we should follow.

—[[user:X1011|X1011]] 05:00, 3 August 2009 (UTC)

== Proposed: Redirects ==

i don't think we should delete redirects. see [[wikipedia:Wikipedia:Redirect#harmful]] for the reasoning. in our case, we also have redirects from the old wiki to preserve. —[[user:X1011|X1011]] 08:33, 27 July 2009 (UTC)

We killed the old wiki. Also most page movements are done to pages that are roughly very new. Some redirects have been left if they are for larger pages, but all internal links are redirected and that page becomes orphaned internally. --[[User:Templarian|Templarian]] 04:06, 28 July 2009 (UTC)

the old wiki is still up, and there are links to it from other sites. i'm ok with deleting new redirects; we can add an exception for that to the policy. —[[user:X1011|X1011]] 05:06, 28 July 2009 (UTC)

All pages moved from the old wiki to the new wiki should have had redirects added on the old wiki. No exceptions. -- Rod

yes, that is part of the reason i want to preserve redirects within this wiki. —[[user:X1011|X1011]] 05:38, 28 July 2009 (UTC)

: And as a general policy, I just don't see that redirects are evil on a plain old wiki. DOUBLE redirects (or deeper) are evil because they don't actually get REDIRECTED you end up on a redirect page.

: So, it's my policy to go in and SPLIT double redirects, so the first side of the double ends up as a direct. But I don't DELETE them. As I said to Matt, one of my patrol pages at wikipedia has 27 incoming redirects, and that's a good thing. For example, I think we need redirect pages for [[Portal:Accessing Linux]] from [[rooting]] [[root login]] [[Accessing Linux]][[Accessing-Linux]] [[AccessingLinux]] and perhaps more. Redirects are good. [[User:Rboatright|rboatright]] 14:25, 31 July 2009 (UTC)

so it seems we're all cool with redirects existing; i will put this policy on the page soon. —[[user:X1011|X1011]] 05:09, 12 August 2009 (UTC)

== proposed: off-wiki discussion ==

"Discussions establishing consensus on issues affecting the community at large (such as policies) must take place on the WebOS Internals wiki." —[[user:X1011|X1011]] 05:04, 12 August 2009 (UTC)

WebOS Internals talk:Policies and guidelines

2009-08-12T05:04:22Z

X1011: New section: proposed: off-wiki discussion

== Proposed: Protection ==

a policy similar to [[wikipedia:Wikipedia:Protection policy]], where pages are only protected if they are repeatedly vandalised or if there is an edit war —[[user:X1011|X1011]] 04:19, 27 July 2009 (UTC)

see also [[wikia:c:help:help:main page#What if I don't want visitors to edit my main page?|Wikia's advice against protecting the main page]] and [[metawikipedia:Protected pages considered harmful]]. —[[user:X1011|X1011]] 03:42, 28 July 2009 (UTC)

It will be noted --[[User:Templarian|Templarian]] 04:06, 28 July 2009 (UTC)

[[Special:Protectedpages]], We only have 3 pages protected, and 2 files. The main page will most likely always be protected, please use the discussion as you are now to point out suggestions. Thanks and hopefully this answers your question. --[[User:Templarian|Templarian]] 13:13, 28 July 2009 (UTC)

we currently have 5 protected pages (one is move-protected only) and 2 protected files.

there is no consensus yet on whether the main page will be protected indefinitely. see [[Talk:Main Page#Protection]].

i have not posed a question. i have proposed a policy. you have not yet stated whether you agree or disagree with it. if you state that you disagree, please explain why.

—[[user:X1011|X1011]] 06:16, 29 July 2009 (UTC)

: Ok, I'll jump in. I think the main page should be protected. I don't know about others, but the main page is our face to the world, and the risk of defacing that exceedsthe value. I am not unaware of the common mistakes described at http://help.wikia.com/wiki/Help:Common_mistakes and am willing to re-consider. But for today, the only argument in the wikia article that is meaningful is the idea that many users will not get beyond the front page and may not even realize that the wiki is editable. While that may have been true some time ago, in this self-selected and computer-literate group we're dealing with, I can't see it. [[User:Rboatright|rboatright]] 14:49, 31 July 2009 (UTC)

if the group we're dealing with is so enlightened, then they should also be less prone to vandalism and more likely to have useful contributions, even for the main page. to my knowledge, there has been no vandalism to this wiki so far. even if something does get messed up, whether with good or bad intentions, it can quickly and easily be fixed. the 1-week protection on the main page has just expired; i say we give it at least a trial and see whether it will get worse or better due to public edits. —[[user:X1011|X1011]] 08:25, 1 August 2009 (UTC)

Are we really expecting non-editor contributions on the front page? If we are seriously expecting that (and there is sufficient structure and instructions on the front page that first-time visitor will not stuff up the formatting, or undo all the collaboration which has occurred so far on the front page look and feel), then I'm happy for it to be unprotected. But I'm skeptical that is the case. Otherwise, we should work how to protect the front page in a way that editors can edit it. [[User:RodWhitby|RodWhitby]] 23:11, 1 August 2009 (UTC)

an editor is anyone who signs up for an account here and makes an edit. i'll assume you're talking about non-admins.

yes, i am expecting non-admins to want to contribute to the main page. [[user:Hopspitfire|Hopspitfire]] made a couple of edits soon after the protection expired, and i expect other users to follow.

—[[user:X1011|X1011]] 02:24, 3 August 2009 (UTC)

I'm referring to the "Editors" group (which is different from Sysops), of which yourself and Hopspitfire are members. I expect that major contributors would be part of that group and exempt from page protection limits. [[User:RodWhitby|RodWhitby]] 02:46, 3 August 2009 (UTC)

i just tried editing a protected page; i cannot. regardless, i still think it's an unnecessary barrier for people who may just want to make a small correction. also, Wikia's point about implying a hierarchy among editors is still valid. —[[user:X1011|X1011]] 03:08, 3 August 2009 (UTC)

I'm happy to trial an unprotected front page, as long as we have the Editors group in place so that protection can be implemented at a moment's notice if there is vandalism without affecting the access of the major contributors if we need to do that. FYI, I'm not sure we've worked out how to allow the Editors group to edit protected pages yet, but that is definitely the intention, and is just awaiting someone working out how to do it. [[User:RodWhitby|RodWhitby]] 03:13, 3 August 2009 (UTC)

BTW, I don't see an edit button on http://en.wikipedia.org/wiki/Main_Page ... that's the example that I think we're following. [[User:RodWhitby|RodWhitby]] 03:14, 3 August 2009 (UTC)

what can sysops do that 'editors' won't be able to, and why have the distinction?

Wikipedia's main page was not protected at first. it was only protected after vandalism became a persistent problem. i think that's the model we should follow.

—[[user:X1011|X1011]] 05:00, 3 August 2009 (UTC)

== Proposed: Redirects ==

i don't think we should delete redirects. see [[wikipedia:Wikipedia:Redirect#harmful]] for the reasoning. in our case, we also have redirects from the old wiki to preserve. —[[user:X1011|X1011]] 08:33, 27 July 2009 (UTC)

We killed the old wiki. Also most page movements are done to pages that are roughly very new. Some redirects have been left if they are for larger pages, but all internal links are redirected and that page becomes orphaned internally. --[[User:Templarian|Templarian]] 04:06, 28 July 2009 (UTC)

the old wiki is still up, and there are links to it from other sites. i'm ok with deleting new redirects; we can add an exception for that to the policy. —[[user:X1011|X1011]] 05:06, 28 July 2009 (UTC)

All pages moved from the old wiki to the new wiki should have had redirects added on the old wiki. No exceptions. -- Rod

yes, that is part of the reason i want to preserve redirects within this wiki. —[[user:X1011|X1011]] 05:38, 28 July 2009 (UTC)

: And as a general policy, I just don't see that redirects are evil on a plain old wiki. DOUBLE redirects (or deeper) are evil because they don't actually get REDIRECTED you end up on a redirect page.

: So, it's my policy to go in and SPLIT double redirects, so the first side of the double ends up as a direct. But I don't DELETE them. As I said to Matt, one of my patrol pages at wikipedia has 27 incoming redirects, and that's a good thing. For example, I think we need redirect pages for [[Portal:Accessing Linux]] from [[rooting]] [[root login]] [[Accessing Linux]][[Accessing-Linux]] [[AccessingLinux]] and perhaps more. Redirects are good. [[User:Rboatright|rboatright]] 14:25, 31 July 2009 (UTC)

== proposed: off-wiki discussion ==

"Discussions establishing consensus on issues affecting the community at large (such as policies) must take place on the WebOS Internals wiki." —[[user:X1011|X1011]] 05:04, 12 August 2009 (UTC)

Talk:Main Page

2009-08-12T04:55:56Z

X1011: link to WebOS Internals talk:Policies and guidelines

User talk:Templarian

2009-08-12T03:19:03Z

X1011: /* main page edit tab */

== Protection ==

You are protecting too many pages. If you think i am going to get into an edit war with you, i am not; i follow the [[wikipedia:wp:1RR|one-revert rule]]. In general, do not assume you are the final word on everything; this is a wiki open to everyone, so things must be decided by consensus. If you disagree with someone, start a discussion to establish a consensus. Please review [[wikipedia:wp:Protection policy]] for a good example of a protection policy. —[[user:X1011|X1011]] 04:33, 27 July 2009 (UTC)

Those pages were protected because of the growing amount of members. It had nothing to do with you. Sorry for the confusion. --[[User:Templarian|Templarian]] 12:48, 27 July 2009 (UTC)

since you did not explain yourself in the protection log, i could only guess your reasons.

a growing amount of members is not reason enough to protect pages. please see my proposed policy on [[WebOS Internals talk:Policies and guidelines]], look over the linked articles, and say why you agree or disagree (on [[WebOS Internals talk:Policies and guidelines]], please).

—[[user:X1011|X1011]] 03:59, 28 July 2009 (UTC)

Sure it is. --[[User:Templarian|Templarian]] 04:19, 28 July 2009 (UTC)

this seems to conflict with what you posted in [[WebOS Internals talk:Policies and guidelines]]. please explain yourself ''there''. —[[user:X1011|X1011]] 04:57, 28 July 2009 (UTC)

== discussion ==

please don't split discussions; put replies on the same discussion page as the comment you're replying to. —[[user:X1011|X1011]] 04:01, 28 July 2009 (UTC)

== main page edit tab ==

see [[MediaWiki talk:Common.css]] —[[user:X1011|X1011]] 04:39, 5 August 2009 (UTC)

and again —[[user:X1011|X1011]] 05:13, 7 August 2009 (UTC)

one more time (you should be watching discussion pages you're participating in; you may want to enable the "Add pages I edit to my watchlist" option on the Watchlist tab in preferences.) —[[user:X1011|X1011]] 01:35, 8 August 2009 (UTC)

are you going to post the log or do i have to talk to the others? —[[user:X1011|X1011]] 03:19, 12 August 2009 (UTC)

Template:Page-main

2009-08-08T09:07:01Z

X1011: removing leftover dotted border

<table width="100%" cellspacing="10" cellpadding="0">
<tr>
<td colspan="3" style="background-color:#FBE6FB;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">
<div style="text-align:center;padding:10px;font-size:18px;">Thank you for helping us move from the old wiki!<br/> Now, please help us in testing all our patches <br/>against 1.1 here: [[Portal:Patches to webOS]]. </div>

</td>
</tr>
<tr>
<td colspan="3">

'''Welcome to the WebOS Internals wiki'''

This site is for collecting information about the inner workings of webOS, which powers everybody (else)'s favorite smart phone, the Palm Pre. If you add information which you did not discover yourself, please try to give credit to the original researcher. Also, please do not add information that has not been confirmed. This is meant to be a collection of facts, and our site is growing quickly, so organization may sometimes be lacking.</td>
<tr>
<tr>
<td style="background-color:#FFFFE0;width:33%;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-1-1}}}</td>
<td style="background-color:#F1F1F1;width:33%;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-2-1}}}</td>
<td style="background-color:#ECF9FF;width:33%;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-3-1}}}</td>
</tr>
<tr>
<td style="background-color:#FFFFE0;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-1-2}}}</td>
<td style="background-color:#F1F1F1;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-2-2}}}</td>
<td style="background-color:#ECF9FF;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-3-2}}}</td>
</tr>
<tr>
<td style="background-color:#FFFFE0;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-1-3}}}</td>
<td style="background-color:#F1F1F1;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-2-3}}}</td>
<td style="background-color:#ECF9FF;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-3-3}}}</td>
</tr>
<tr>
<td style="background-color:#FFFFE0;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-1-4}}}</td>
<td style="background-color:#F1F1F1;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-2-4}}}</td>
<td style="background-color:#ECF9FF;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{cell-3-4}}}</td>
</tr>
<tr>
<td colspan="3">
<table width="100%" cellspacing="0" cellpadding="0">
<tr>
<td>{{{leftnav}}}<td>
<td style="text-align:right;">{{{rightnav}}}</td>
</tr>
</table>
</td>
</tr>
<tr>
<td style="background-color:#FFFFE0;vertical-align:top;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{irc}}}</td>
<td style="background-color:#F1F1F1;vertical-align:top;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">
{{{coderepositories}}}</td>
<td style="background-color:#ECF9FF;vertical-align:top;border-top:1px solid #999;border-left:1px solid #999;border-right:1px solid #333;border-bottom:1px solid #333;">{{{resources}}}</td>
</tr>
<tr>
<td colspan="3">

{{portal-two-columns
|column1=
==Featured Article==
{{WebOS Internals:Featured_Article/Current}}

[[WebOS Internals:Featured_Article|Past and future featured articles]]
|column2=
==Featured Project==
{{WebOS Internals:Featured_Project/Current}}

[[WebOS Internals:Featured_Project|Past and future featured projects]]
}}

== Disclaimer ==

{{WebOS Internals:General disclaimer}}

</td>
</tr>
</table>

MediaWiki talk:Common.css

2009-08-08T01:36:52Z

X1011: /* main page edit tab */

== main page edit tab ==

woah, hold on. do not hide the main page's edit tab. see [[WebOS Internals talk:Policies and guidelines#Proposed: Protection]] for the discussion on restricting editing of the main page. —[[user:X1011|X1011]] 09:46, 4 August 2009 (UTC)

: Majority agreed in the sysops in IRC. --[[User:Templarian|Templarian]] 13:56, 5 August 2009 (UTC)

you said on my talk page that this was decided a while ago; was that before the discussion on [[WebOS Internals talk:Policies and guidelines#Proposed: Protection]] (~august 2)? —[[user:X1011|X1011]] 04:25, 6 August 2009 (UTC)

Must of been during... I believe you were the only one for not removing the button. The front page was setup so that it will not have to be edited for a long time. It's for the most part static with the featured article stuff in templates. --[[User:Templarian|Templarian]] 05:24, 7 August 2009 (UTC)

post the log in [[WebOS Internals talk:Policies and guidelines#Proposed: Protection]]; we can continue the discussion there. —[[user:X1011|X1011]] 05:32, 7 August 2009 (UTC)

and make sure to include the timestamp(s) (at least one at the beginning) —[[user:X1011|X1011]] 01:36, 8 August 2009 (UTC)

User talk:Templarian

2009-08-08T01:35:33Z

X1011: /* main page edit tab */

Talk:Preware Design

2009-08-08T01:18:42Z

X1011: /* XML feeds */

{{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)

Talk:Preware Design

2009-08-08T01:18:21Z

X1011: /* XML feeds */ sign!

{{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]]

== 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)

File talk:Tux with Broken Pre.png

2009-08-08T01:12:52Z

X1011: /* ... */

== ... ==

why does this Tux have pubic hair? —[[user:X1011|X1011]] 13:20, 7 August 2009 (UTC)

: Those are the fragements ofthe broken pre he's holding. -- [[User:Rboatright|rboatright]] 19:30, 7 August 2009 (UTC)

it really doesn't look like it; not to mention the pieces on the ground are not missing from the halves he's holding. —[[user:X1011|X1011]] 01:12, 8 August 2009 (UTC)

File talk:Tux with Broken Pre.png

2009-08-07T13:20:53Z

X1011: ...

== ... ==

why does this Tux have pubic hair? —[[user:X1011|X1011]] 13:20, 7 August 2009 (UTC)

MediaWiki talk:Common.css

2009-08-07T05:32:45Z

X1011: /* main page edit tab */

User talk:Templarian

2009-08-07T05:13:01Z

X1011: /* main page edit tab */

Talk:Preware Design

2009-08-06T04:35:00Z

X1011: /* License id */

{{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)

== 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)

MediaWiki talk:Common.css

2009-08-06T04:25:24Z

X1011: /* main page edit tab */

User talk:X1011

2009-08-06T04:20:25Z

X1011: revert (you deleted a section)

== moving pages ==
{{Warn|reason=You did a good job moving those other pages around, but please make sure to fix all linking pages after you move it, and file the old page under [[Admin Changes]]. Another note don't move pages out of the help section. --[[user:Templarian|Templarian]]}}

Wikipedia puts their policies in the Wikipedia: namespace. This separates technical help pages (how do i do this?) from policy pages (what is the established standard for this?). I think we should follow a similar model. If you disagree, start a discussion section in [[WebOS Internals talk:Policies and guidelines]], move these comments there, and then state your reasons clearly. —[[user:X1011|X1011]] 03:15, 27 July 2009 (UTC)

== noob page ==
re your NOOB page. Great job. I think it needs to be prominently linked off the front page, requiring a change to the front page template. [[User:Rboatright|rboatright]]

talking about [[NOOB Friendly Getting Started]] aka [[Portal: Where to Get Started]]? that's not mine; that was the work of [[user:Imop45|Imop45]] —[[user:X1011|X1011]] 04:37, 28 July 2009 (UTC)

== magic wand ==
Magic wand should be coming up. Con census was yes. That said, before making BIG changes to the layout of the wiki, please, lets try to have a consensus of the editors. [[User:Rboatright|rboatright]]

cool, will do, but keep in mind that granting adminship should [[wikipedia:WP:NOBIGDEAL|not be a big deal]] —[[user:X1011|X1011]] 04:37, 28 July 2009 (UTC)

: when I first started editing wikipedia in 2003, when it had less than 5K articles, adminship was a big deal. Jimbo didn't like that, and it wasn't long later that he made his famous "will-nilly" comment. but the simple reality is that who you choose to be part of the editorial team early on shapes the eventual outcome of the community's identity.

: Never-the-less, happy to welcome you aboard. [[User:Rboatright|rboatright]] 13:34, 28 July 2009 (UTC)

the 'editorial team' is everyone who chooses to edit the wiki. restricting adminship only makes it harder for people who want to contribute deeply. —[[user:X1011|X1011]] 06:00, 29 July 2009 (UTC)

still waiting on that magic wand... —[[user:X1011|X1011]] 02:31, 3 August 2009 (UTC)

[http://www.webos-internals.org/index.php?title=Special%3AListusers&username=&group=Editors&limit=50 Editor List] Been busy, but whitby should be getting this sorted out shortly (still has to add "editors" to the list for the protect page) --[[User:Templarian|Templarian]] 02:59, 3 August 2009 (UTC)

== contact ==
I added you to the [[Contact]] page. -[[User:Hopspitfire|hopspitfire]] 05:58, 3 August 2009 (UTC)

Talk:Main Page

2009-08-05T06:56:45Z

X1011: butchering your comments (moving some to MediaWiki talk:Sidebar)

== Beta Main Page ==

This isn't in use right now, but when It comes the time to swap out the main page again.

[[Main_Page_beta]]
[[Template:Page-main-beta]]

== Article title capitalization ==

Are we sure we want to use title case for article titles? [http://en.wikipedia.org/wiki/Wikipedia:Mos#Article_titles Wikipedia uses sentence case], and i think it looks much better.
—[[User:X1011|X1011]] 06:35, 20 July 2009 (UTC)<br>
Also, same question for section headings —[[user:X1011|X1011]] 12:45, 20 July 2009 (UTC)

I think it usually works out good since a lot of pages are displayed as: <nowiki>[[Page Name]], also with the headers of course don't uppercase "a", "and", etc.</nowiki> --[[User:Templarian|Templarian]] 13:21, 20 July 2009 (UTC)

'''from #webos-internals:'''
<source lang="text" enclose="div">
Rick_: X1011, the pages-to-be-moved page on the new wiki uses the PAGE NAME as a link to create the page on the new wiki rather than the old page link from the old wiki.
Rick_: In general _most_ of them are fine.
Rick_: We prefer "Page About Smashing the Pre" to "Page about smashing the Pre" because it _is_ the title of the page, and so _should_ be in title case.
Rick_: or that's the consensus of the team to date.
</source>

== Registration error warning ==

Instead of having the warning about getting an error on confirming your registration on the main page, could an admin put it on the [http://www.webos-internals.org/index.php?title=Special:Userlogin&type=signup create account page]? —[[user:X1011|X1011]] 01:58, 23 July 2009 (UTC)

The Special:* namespace pages are not editable. -- Rod

Maybe not inside the wiki editing system, but surely it's editable at some level. I think we should put user experience before "that's too hard to do". —[[user:X1011|X1011]] 23:55, 23 July 2009 (UTC)

Agreed - I'll look into it. -- Rod

==Front page mispelling and Description Addition==

There's a mispelling on the top of the front page (I don't have rights to edit this page)

"Thank you for heling us convert all the pages from the old wiki!"

should be:

"Thank you for hel'''p'''ing us convert all the pages from the old wiki!"

Also, can you add something referencing "Kernels" in the development tools' description?

-[[user:hopspitfire|hopspitfire]] 05:33, 23 July 2009 (UTC)

Added kernels to the list --[[User:Templarian|Templarian]] 19:23, 27 July 2009 (UTC)

== Protection ==

Why is Main Page protected? It shouldn't be protected unless it is vandalised; see [[wikipedia:WP:NO-PREEMPT]]. As seen in the above section, regular people have useful contributions. —[[user:X1011|X1011]] 21:52, 24 July 2009 (UTC)

I disagree. We're getting 20K page views a day. Let's keep the main page clean and functonal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the main page has 14,428 total views to date. we shouldn't assume our users will make it dirty and unfunctional before we even give them a chance. Wikia has [[wikia:c:help:help:main page#What if I don't want visitors to edit my main page?|a good writeup]] on why the main page should not be protected.

also, in the future, when you protect a page, please include a note explaining why you are doing so.

—[[user:X1011|X1011]] 08:07, 28 July 2009 (UTC)

The main page is currently editable, was this intentional? [[User:Hopspitfire|hopspitfire]] 07:03, 1 August 2009 (UTC)

Yea, rick only set it to be protected till aug 1st while updates were going on. The idea was so that users wouldn't mess with it as the site was being setup / structured. --[[User:Templarian|Templarian]] 22:42, 2 August 2009 (UTC)

: The idea was that there was a gazillion links on the FRONT page of the old wiki. we wanted the front page of the new wiki to lead to DEPARTMENTS instead of having a zillion links on it. -- that's worked out now, and seems institutionally embedded so why not let the protection expire? [[User:Rboatright|rboatright]] 22:51, 2 August 2009 (UTC)

== Research/Reference Portal ==

We need to add the Research/Reference portal to the front page. I recommend re-organizing the front page.

I'd start with putting "Getting Started" on the top-middle by itself, then follow the diagram below:

<pre><nowiki>
-------------Getting Started-------------
Linux Apps---Source Patches---Dev Tools
Research-------webOS Apps-----Hardware
Recovery--------SDK Docs------Wiki Help
</nowiki></pre>

We also need an icon for "Research", maybe put a lab suit over Tux with a doctor's mask. What do you think?

I also agree with the post above regarding the unprotection of the front page (at least to autoconfirmed users).

-hopspitfire

yes, we need to add a box for the research portal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

== featured article ==
I think we need a "featured article" on the main page. Right now, that wuld be
terminal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the featured articles look great. --[[User:Templarian|Templarian]] 13:15, 30 July 2009 (UTC)

MediaWiki talk:Sidebar

2009-08-05T06:56:38Z

X1011: /* Google group */ moving comments from talk:Main Page

== Naming cleanup ==

I propose the following changes to the portal box in the sidebar:
* [[Portal:Accessing Linux| Accessing Linux]] should not be a portal. It is more of a tutorial, and most people only need it once. It would be better to have it only linked from the main page.
* webOS Applications and Linux Applications renamed to just webOS and Linux. These portals are already more than just applications, and more things will probably be added to them.
* Hardware Information renamed to Hardware
* Research & Reference split. (the line's already wrapping, so it wouldn't take up more space)
* The page [[Portal:Misc]] renamed to [[Portal:Miscellaneous]]. If it can be spelled out in the sidebar, it definitely can be spelled out in the article title.
* The Palm SDK & Docs renamed to SDK
* Put Miscellaneous after Tools

This would be the result:
<div class='portlet'>
<div class='pBody'>
* [[Portal:webOS|webOS]]
* [[Portal:Linux|Linux]]
* [[Portal:Hardware|Hardware]]
* [[Portal:Research|Research]]
* [[Portal:Reference|Reference]]
* [[Portal:SDK|SDK]]
* [[Portal:Tools|Tools]]
* [[Portal:Miscellaneous|Miscellaneous]]
* [[Portal:Community|Community]]
</div>
</div>

That looks much nicer, don't you agree? More concise and not as much line wrapping.
Of course, the pages themselves will have to be renamed, too.

Tell me what you think. If you're an admin who can edit the sidebar, i already have the code ready for you in a comment here for easy copy and paste.<br>

—[[user:X1011|X1011]] 05:05, 23 July 2009 (UTC)

On second thought, lets not rename the linux and webos portals. --[[User:Templarian|Templarian]] 17:30, 24 July 2009 (UTC)

:Why? The names are inappropriate and too long. —[[user:X1011|X1011]] 21:35, 24 July 2009 (UTC)

:They would be to generic. --[[User:Templarian|Templarian]] 13:24, 27 July 2009 (UTC)

:I don't see why; we don't have any other portals with webOS or Linux in their names. —[[user:X1011|X1011]] 02:02, 28 July 2009 (UTC)

it does look nicer, but it's less informative.
The consensus of the webos-internals ops is for the time being the answer is "no." recognizing that things are changing VERY FAST and we may revisit this again in the not-too-distant future.
[[User:Rboatright|rboatright]] 00:14, 27 July 2009 (UTC)

less informative how? would it prevent someone from finding what they're looking for?

we can implement just some of the changes if there are specific parts you guys don't like.

also, where was this consensus reached? if it was in IRC, please post the log. i think in the future, consensus should be established on the wiki so that it is documented and everyone can be a part of it.

—[[user:X1011|X1011]] 00:30, 27 July 2009 (UTC)

I think there's a clear distinction between webOS / Mojo apps and things that run in a terminal - linux apps.

That blurs a little with the advent of terminal, but only a little.

I think that your proposed sidebar mod reduces the amount of information available, and makes navigation more troublesome. We have the space, why not use it?

[[User:Rboatright|rboatright]]

i think you may be misunderstanding me; i'm not proposing to merge the webOS and Linux portals; just to rename them.

as for the space: firstly, we don't necessarily have it; the sidebar currently extends beyond the bottom of the browser window for me. second, just because we have space doesn't mean we should use it up; keeping it uncluttered makes navigation easier.

—[[user:X1011|X1011]] 05:20, 28 July 2009 (UTC)

== Combining portals ==

On the left side-bar of the page, can we remove "Research & Reference" and combine it with "Development Tools"? Otherwise, we have a page with barely any links (the former) and it makes the left side-bar more cluttered. Also, Research isn't even on the front page.

-hopspitfire

My view is that each logically separate category should have its own page. How would people know to find research in the tools page? Don't worry about lack of content for now; this wiki is still new.

We'll have to see about putting research on the main page. It will need an icon. Perhaps start a discussion on [[talk:Main Page]].

—[[user:X1011|X1011]] 23:25, 26 July 2009 (UTC)

== Google group ==

The Google group should go on the community portal instead, since that's where irc is too. Or if you want it to be more prominent, on the main page, but at least not on the sidebar. We don't need to put everything on the sidebar and clutter it up. —[[user:X1011|X1011]] 03:41, 27 July 2009 (UTC)

In general you are correct, but the sidebar is where things go that are _important_ and the announcement list is important.

The sidebar does not extend too far at this point. Perhaps a set of smaller icons above the big boxes on the main page... Announcements, Projects, etc.

I still think we need a "Current page in the news" where we feature the current "hot" page if there is one. Right now that would be Terminal. Terminal is non-trivial to find. (other than by search.)

[[User:Rboatright|rboatright]] 02:51, 28 July 2009 (UTC)

I agree that we could move the google group off the sidebar onto the main page [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

Agreed. Terminal and Google Groups are things we want to draw attention to now. In the long run, they do not need to be as prominent. -- Rod

rboatright, i disagree; the main page is where important things go; the sidebar is where navigation goes.

please put any further discussion of a featured page in [[Talk:Main Page#featured article]].

—[[user:X1011|X1011]] 07:36, 28 July 2009 (UTC)

So it got reorganized, but lets leave the subscribe here up for a bit till everyone that wants to can subscribe (it's also on the main page). --[[User:Templarian|Templarian]] 13:15, 30 July 2009 (UTC)

Preware Design

2009-08-05T06:40:47Z

X1011: /* Preware */ renaming section

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Name ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_plug_pluginname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>A+++ would download again</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>freezes every second tuesday when bluetooth is enabled</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T06:40:02Z

X1011: /* XML Feeds */ webOS and version are 2 separate words, so they should be distinguished

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webOSVersion>
<min>1.0.3</min>
<max>1.1</max>
</webOSVersion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_plug_pluginname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>A+++ would download again</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>freezes every second tuesday when bluetooth is enabled</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T06:37:36Z

X1011: /* XML Feeds */ fixing filename of plugin

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_plug_pluginname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>A+++ would download again</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>freezes every second tuesday when bluetooth is enabled</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T06:35:04Z

X1011: /* XML Feeds */ comments should be abridged by the client so they can be expanded if desired

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>A+++ would download again</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>freezes every second tuesday when bluetooth is enabled</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T06:21:26Z

X1011: /* XML Feeds */ using xml highlighter

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T06:12:52Z

X1011: /* XML Feeds */ fix inconsistencies between review and comment

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="comment">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T05:19:59Z

X1011: /* Feeds */ search url

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages to="424" type="comment">
<message id="420">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search?q=string[&filters]
#example:
preware.org/feed/xml/search?q=search+string&category=Utilities&user=12
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-05T04:56:15Z

X1011: /* Licences */ spelling

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licenses ===
Name id
Apache-2.0 apache2.0
BSD bsd
CDDL cddl
CPL-1.0 cpl1.0
GPL-2 gpl2.0
GPL-3 gpl3.0
LGPL-3 lgpl3.0
MIT mit
MPL-1.1 mpl1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<license id="mit">MIT</license>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages to="424" type="comment">
<message id="420">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search/string/[filters/]
preware.org/feed/xml/search/search%20string/category:Utilities/user:12/
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Talk:Preware Design

2009-08-05T04:51:37Z

X1011: /* License id */

{{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)

== 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)

User talk:Templarian

2009-08-05T04:39:46Z

X1011: New section: main page edit tab

Application talk:Terminal

2009-08-04T09:51:14Z

X1011: /* Font Size Feature Request */ sign your comments

== Bugs: tab completion, slowdown ==
-Tab completion working fine as of 1.5.

-Slowdown is not fixed, but better
As of 1.5, slowdown only seems to happen if something is actively scrolling the terminal. If something (like find) is running and scrolling the screen, or if I flick it to scroll and immediately minimize it and try to open other apps, it still slows down, but when it is sitting at a screen not doing anything, the phone seems fine.
--[[user:Zinge|Zinge]]

== Fullscren (curses?) apps scroll wrong ==
Another quick bug: when running irssi or BX only the first line above the status bar line(s) scrolls. When going between landscape and portrait mode, the screen refreshes properly, but still only one line scrolls in either mode. This is as of 0.1.5. --[[User:T3rmin|T3rmin]] 17:00, 28 July 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]]

== 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)

MediaWiki talk:Common.css

2009-08-04T09:46:30Z

X1011: main page edit tab

Talk:Portal:Patches to webOS

2009-08-04T09:36:19Z

X1011: /* Quilt incorporation */

Talk:Portal:Patches to webOS

2009-08-04T09:30:57Z

X1011: /* naming */

User talk:Hopspitfire

2009-08-04T08:53:55Z

X1011: sectioning unrelated comment

== Porting pages ==

Hey, welcome to the wiki. One thing: don't add your signature to pages you transfer over from the old wiki. This is a community effort, those pages will be edited by other people, and we want to try to keep a consistent look across pages. Thanks. —[[user:X1011|X1011]] 17:18, 20 July 2009 (UTC)

All instances of signature have been removed -hopspitfire

== / in page titles ==
If you can please do not use "/" in page titles. --[[User:Templarian|Templarian]] 23:27, 20 July 2009 (UTC)

== THANK YOU for your hard work on the wiki! ==

Please accept this "nobody knows the trouble I've seen" award as a token of our appreciation.

[[image:drudgery.jpg]]

[[User:Rboatright|rboatright]] 02:11, 24 July 2009 (UTC)

Congrats on becoming an Editor --[[User:Templarian|Templarian]] 13:16, 28 July 2009 (UTC)

== Deletions ==

I just had a horrible thought.

All those deletions you're doing that are pages that only had you as an editor...

if you delete the redireccts, aren't you deleting the thing that the old-page on the old-wiki links to? so you have broken the redirect FROM the old-wiki?

and that means that if anyone had blog-pages or precentral posts that linked to those, THOSE are broken.

I've never understood what's wrong with lots of redirects. One of my patrol pages on wikipedia has 27 redirects that end up there. And that's a GOOD thing. :-)

[[User:Rboatright|rboatright]] 05:16, 31 July 2009 (UTC)

agreed; see [[WebOS Internals talk:Policies and guidelines#Proposed: Redirects]] —[[user:X1011|X1011]] 05:59, 31 July 2009 (UTC)

Sit tight guys, I'm fixing all the links from predev. [[User:Hopspitfire|hopspitfire]] 06:01, 31 July 2009 (UTC)
*edit All broken links have been fixed on predev. Rick, thanks for bringing this up. [[User:Hopspitfire|hopspitfire]] 06:16, 31 July 2009 (UTC)

Talk:Portal:Patches to webOS

2009-08-03T10:00:31Z

X1011: New section: naming

Talk:Portal:Patches to webOS

2009-08-03T09:37:29Z

X1011: fix headings

Preware Design

2009-08-03T09:05:02Z

X1011: moving suggestion to discussion page

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licences ===

* Apache-2.0
* BSD
* CDDL
* CPL-1.0
* GPL-2
* GPL-3
* LGPL-3
* MIT
* MPL-1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages to="424" type="comment">
<message id="420">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search/string/[filters/]
preware.org/feed/xml/search/search%20string/category:Utilities/user:12/
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Talk:Preware Design

2009-08-03T09:04:58Z

X1011: New section: button resizing

{{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)

== 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]]

Preware Design

2009-08-03T09:00:10Z

X1011: fix up intro

This app is to be a front end to the [[Preware Repository Description|Preware open-source Mojo repository]], the webOS-internals project to supply end users with applications, plugins, and updates thereof all in one user-friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Suggestions ==

: 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.

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licences ===

* Apache-2.0
* BSD
* CDDL
* CPL-1.0
* GPL-2
* GPL-3
* LGPL-3
* MIT
* MPL-1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages to="424" type="comment">
<message id="420">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search/string/[filters/]
preware.org/feed/xml/search/search%20string/category:Utilities/user:12/
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>

Preware Design

2009-08-03T08:52:48Z

X1011: it seems the discussion is taking place on the discussion page; imagine that

== Background ==
This app is to be a front end to the [[Preware Repository Description|Preware open source Mojo repository]]. For those that do not know Preware is name of the webOS-internals project to supply end users with applications/plugins/updates all in one user friendly place.

== Why this is Important ==

This morning (25 July 2009) after my morning OA meeting, at coffee I ran a set of paper prototypes of a gui appstore front end for the webos-internals ipkg feed past a group of women aged 45 to 72 who had not previously used a Pre.

Each of them had the chance to go into launcher, bring up an app, run it, go into the app store, look around, etc before starting the prototyping session.

First, as a group they all hated the palm appstore. They disliked the horizontal scrollers at the top, they disliked the scrolling aspect of the entire page. They wanted much more clear indications that a scroll was available, but they thought that a thinner leaner first page would be much better.

After 30 minutes of the group tearing up 4x6 cards and scribbling new ones, we ended up with the following decisions which I pass along.

* the first scene should have 5 selections
** Upgrade your installed apps
** Patches for existing apps
** WebOS applications
** Delete things you have installed
** Alpha list of everything

each of those opens a new scene. along the bottom of the scene is a fixed button bar with on the left, an INSTALL button, in the center a BACK button and on the right a DELETE button

that button bar is ALWAYS there except on scene 1. They know and understand the back gesture, but they liked the idea of a back button even so, and since there was a space, why not?

the install and delete buttons dim out or come live as appropriate.

They were divided on the subject of keeing a banner for the app store at the top of the screen, some liked the idea of a HOME button. Some did not and wanted the space for the lists and said "banner only on the home page.

Each subsidiary screen brings up a list of apps. that list scrolls in the space ABOVE the button bar.
Tapping an ap brings up the long description of the app and enables the install or delete button as is appropriate.

The graphical design should be very VERY clean and not busy. It was a major complaint about the Palm app store that it was too busy.

Templarian's mockup for the PreWare home page is a really good basis to work from, and it would be good if the gui app resembled the submission and management page. It will change depending on comments here.

I thought this would give us a starting place

- Rick

== Project Repository ==

http://gitorious.org/webos-applications/installer

== Suggestions ==

: 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.

== Development help ==

PreWare is being developed as an open source project. '''We really want help on the development of this app!''' The source of the application is available at http://gitorious.org/webos-applications/installer

Anyone can check out a copy. If you would like check in privlidges, simply message [[User_talk:Rboatright|Rboatright]] or [[User_talk:Templarian|Templarian]] on their talk pages.

You will need to register an ssh key with gitorious. If you've never done that, a walk through is available at http://nathanj.github.com/gitguide/ Substitute gitorious.org for github in the instructions.

== Preware ==

The "Pre" in "Preware" does not refer to the Palm Pre, it refers to "before" as far as app testing goes, and is a pun on "Freeware"

== Submissions ==

Submissions will have their icons ripped out for application use.

=== Licences ===

* Apache-2.0
* BSD
* CDDL
* CPL-1.0
* GPL-2
* GPL-3
* LGPL-3
* MIT
* MPL-1.1

=== Legal Acceptance on Submission ===

I hereby... fill in this with the legal stuff

== Application ==

(Images will be updated below as suggestions come in, wiki forces cache so CTRL+SHIFT+R in modern browsers)

[[Image:OPS_App_Mockup1.png]]

== Site ==

[[Image:OPS_Mockup.png]]

== Removing Applications ==

Main thing to include is a way to keep track of applications that depend on certain plugins. We cannot have users uninstalling plugins that are required for an installed app to run.

== IPKG Feed ==

The standard IPKG feed will be accessible by everyone.

== XML Feeds ==

=== Application Feed (List/Filtered) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Application View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="41">
<package>appname</package>
<version>1.0.0</version>
<name>Application Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<depends>
<depend id="20" type="plugin">
<package>pluginname</package>
<version>1.0.0</version>
<name>FileIO</name>
</depend>
</depends>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Plugin View ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<applications>
<application id="20">
<package>pluginname</package>
<version>1.0.0</version>
<name>Plugin Name</name>
<webosversion>
<min>1.0.3</min>
<max>1.1</max>
</webosversion>
<maintainer id="42">
<name>John Doe</name>
<email>email@domain.com</email>
</maintainer>
<architecture>all</architecture>
<filename>com.domain_app_appname_1.0.0_all.ipk</filename>
<md5sum>325ca724c05288eb182dd7ebdd493926</md5sum>
<size>123456</size>
<category>Utilities</category>
<source>http://www.preware.org/41/</source>
<applications>
<application id="20">
<type>plugin</type>
<version>1.0.0</version>
<name>FileIO</name>
</application>
</applications>
<description>A long description</description>
</application>
</applications>
</preware>
</syntaxhighlight>

=== Review (to Applications / Plugins) ===

<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages>
<message id="420" type="review">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

=== Comment (tbd) ===
<syntaxhighlight lang="html4strict">
<?xml version="1.0" encoding="UTF-8"?>
<preware>
<messages to="424" type="comment">
<message id="420">
<user id="10">FooBar</user>
<text>If this is a long comment it will be cut off at a random point with [...] character.</text>
</message>
</messages>
</preware>
</syntaxhighlight>

== Address Structures ==

=== Site ===

I don't know how much of this we can really change, I think Drupal could be rather strict.

<source lang="text">
# Application Page
preware.org/packagename/
# .ipk uses direct id
preware.org/41/filenameto.ipk
preware.org/
</source>

=== Feeds ===

Yea this section needs major input.

<source lang="text">
# Full List IPKG
preware.org/feed/

# XML files for application use (full list)

# XML Categories List
preware.org/feed/xml/category/
# XML Categories List Specific, encode spaces with (%20)
preware.org/feed/xml/category/games/
# XML Application Specific
preware.org/feed/xml/application/23/
# XML Plugin Specific
preware.org/feed/xml/plugin/24/
# XML Search
preware.org/feed/xml/search/string/[filters/]
preware.org/feed/xml/search/search%20string/category:Utilities/user:12/
# XML Application Reviews
preware.org/feed/xml/review/23/
</source>