Talk:Portal:Patches to webOS - Revision history

X1011: /* Creating a patch */

2009-12-08T22:14:24Z

Creating a patch

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

2009-12-08T22:14:03Z

Creating a patch: sign your comments

AlisonW: New section: Re WebOS versions

2009-10-26T22:24:59Z

New section: Re WebOS versions

Dallashigh: New section: Creating a patch

2009-10-16T15:42:27Z

New section: Creating a patch

Roto at 23:37, 10 October 2009

2009-10-10T23:37:50Z

Milominderbinder: /* Aren't a lot more of the patches 1.2.1 compatible that are shown? */ typo

2009-10-07T03:50:18Z

Aren't a lot more of the patches 1.2.1 compatible that are shown?: typo

Milominderbinder: New section: Aren't a lot more of the patches 1.2.1 compatible that are shown?

2009-10-07T03:49:38Z

New section: Aren't a lot more of the patches 1.2.1 compatible that are shown?

X1011: /* Quilt incorporation */

2009-08-04T09:36:19Z

Quilt incorporation

X1011: /* naming */

2009-08-04T09:30:57Z

naming

Hopspitfire: /* naming */

2009-08-03T20:47:38Z

naming

@@ Line 77: / Line 77: @@
 == 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|]
+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)

@@ Line 77: / Line 77: @@
 == 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.
+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)

← Older revision		Revision as of 22:24, 26 October 2009
Line 78:		Line 78:

	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.		I know this probably isn't the right place, but I'm trying to create a patch to submit for inclusion in Preware. I'm comfortable with the Linux command line and creating standard patch files. I need to know if there's a special format or header that I need to add to the standard patch file. I also need to know if patches are still applied with / as the working directory, and how to submit the patch for inclusion in Preware once it's been tested. Thanks.
		+
		+	== Re WebOS versions ==
		+
		+	I note that in the UK (and, I believe, the rest of Europe) we are being ''held back'' (as it were) from the latest WebOS releases currently. As such, might there be sense in listing which apps ''will'' work this side of the pond even though not 'that' side. --[[User:AlisonW\|AlisonW]] 22:24, 26 October 2009 (UTC)

← Older revision		Revision as of 15:42, 16 October 2009
Line 74:		Line 74:

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

← Older revision		Revision as of 23:37, 10 October 2009
Line 72:		Line 72:
	Note: The Music Player: Bookmarking does nto work with classical or opera genres etc. and has not been made obsolete.		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)		[[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)

@@ Line 49: / Line 49: @@
 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)
-== Aren't a lot more of the patches 1.2.1 compatible that are shown? ==
+== 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?

← Older revision		Revision as of 03:49, 7 October 2009
Line 48:		Line 48:

	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)		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)
		+
		+	== Aren't a lot more of the patches 1.2.1 compatible that 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)

← Older revision		Revision as of 09:36, 4 August 2009
Line 46:		Line 46:
	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.		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)		--[[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)

← Older revision		Revision as of 09:30, 4 August 2009
Line 32:		Line 32:

	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'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 ==		== Quilt incorporation ==

@@ Line 31: / Line 31: @@
 —[[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. -[[User:Hopspitfire|hopspitfire]] 20:46, 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)
 == Quilt incorporation ==