Talk:Portal:Patches to webOS

From WebOS Internals

Jump to: navigation, search

Contents

catagories

we have ten catagories for webOS apps do we need to catagorize these so that they aren't one giant long list? 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). JackieRipper

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

Editing and new pages

Users editing this page, please keep the columns organized alphabetically. hopspitfire 06:50, 1 August 2009 (UTC)

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

{{template:patch}}

This will make the wiki much more cohesive. -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 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"

X1011 10:00, 3 August 2009 (UTC)

I've tried using colons, but that makes the patch unsearchable. Using a "/" is also avoided 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. -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 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.

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. --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. —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. 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. 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. --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. --AlisonW 22:24, 26 October 2009 (UTC)

Personal tools
Google AdSense