Feature requests - Revision history

Jocelyn Linden: Merged content in to :Category:Feature Requests

2007-06-19T16:56:41Z

Merged content in to Category:Feature Requests

← Older revision		Revision as of 09:56, 19 June 2007
Line 1:		Line 1:
	#redirect [[~~Implementing_new_features~~]]		#redirect [[:Category:Feature Requests]]

Jocelyn Linden: Content on this page merged in to Category:Feature Requests

2007-06-19T16:53:50Z

Content on this page merged in to Category:Feature Requests

Show changes

Jocelyn Linden: Reverted edits by Jocelyn Linden (Talk); changed back to last version by Cago Hax

2007-06-19T16:47:20Z

Reverted edits by Jocelyn Linden (Talk); changed back to last version by Cago Hax

Show changes

Jocelyn Linden: Content on this page merged in to Category:Feature Requests

2007-06-19T16:46:07Z

Content on this page merged in to Category:Feature Requests

← Older revision		Revision as of 09:46, 19 June 2007
Line 1:		Line 1:
	~~{{OSWikiContribBox}}~~		#REDIRECT [[Category:Feature Request]]

	~~== Filing Feature Requests==~~
	~~We're always looking for new ideas. Please let us know what you would like to see done.~~

	~~== Refining Feature Requests ==~~

	~~Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.~~

	~~See~~ [[:Category:Feature ~~Requests~~]] ~~for pages in this category.~~

Jocelyn Linden: Reverted edits by Cago Hax (Talk); changed back to last version by Rob Linden

2007-06-19T16:15:57Z

Reverted edits by Cago Hax (Talk); changed back to last version by Rob Linden

Show changes

Cago Hax: /* Filing Feature Requests */llTrace(integer rule,list[parameters])

2007-06-02T20:32:14Z

Filing Feature Requests: llTrace(integer rule,list[parameters])

Show changes

Rob Linden at 02:10, 26 January 2007

2007-01-26T02:10:37Z

← Older revision		Revision as of 19:10, 25 January 2007
Line 7:		Line 7:

	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.		Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.

			See [[:Category:Feature Requests]] for pages in this category.

Buckaroo Mu: Moved specific feature requests to a different page.

2007-01-09T19:21:41Z

Moved specific feature requests to a different page.

← Older revision		Revision as of 12:21, 9 January 2007
Line 7:		Line 7:

	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.		Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.

	~~== Minor Feature Requests ==~~
	*Add a "link" ("alias", "shortcut") facility to the inventory, that would not break Permissions. For instance, I have one nice set of prim dress shoes that are no-copy, and four tuxedos. I cannot make complete separate outfits, because I have only one copy of the shoes. However, using a "link", I could create an outfit folder with the tux and a link to the no-copy shoes. Still means I would only have the one set, but it would make changing clothes much much easier. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:23, 9 January 2007 (PST)

	~~== Major Feature Requests ==~~
	*A DirectX3D-driven version of the viewer, allowing those with ATi or Intel hardware accelerated cards to take advantage of the processing power. The system could allow selection as a preference of OpenGL or DirectX3D, as many Windows-only games currently do. Conditional build statements would keep the option from appearing in the non-DirectX3D capable builds. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:28, 9 January 2007 (PST)

	*A method of offloading some of the [http://www.gpgpu.org/ graphics processing to the GPU] might help increase framerate. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:37, 9 January 2007 (PST)

	*Support for detachable sub-windows, allowing the inventory, chat history, IM, etc. windows to be moved to a second monitor (if available). This is a very highly-desired feature (by those that have dual-monitor systems). [[User:Buckaroo Mu\|Buckaroo Mu]] 09:37, 9 January 2007 (PST)

Buckaroo Mu: Feature Request: Multiple Monitor Support

2007-01-09T17:37:29Z

Feature Request: Multiple Monitor Support

← Older revision		Revision as of 10:37, 9 January 2007
Line 12:		Line 12:

	== Major Feature Requests ==		== Major Feature Requests ==
	*A DirectX3D-driven version of the viewer, allowing those with ATi or Intel hardware accelerated cards to take advantage of the processing power. ~~Alternatively~~, a method of offloading some of the [http://www.gpgpu.org/ graphics processing to the GPU] might help increase framerate. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:28, 9 January 2007 (PST)		*A DirectX3D-driven version of the viewer, allowing those with ATi or Intel hardware accelerated cards to take advantage of the processing power. The system could allow selection as a preference of OpenGL or DirectX3D, as many Windows-only games currently do. Conditional build statements would keep the option from appearing in the non-DirectX3D capable builds. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:28, 9 January 2007 (PST)

			*A method of offloading some of the [http://www.gpgpu.org/ graphics processing to the GPU] might help increase framerate. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:37, 9 January 2007 (PST)

			*Support for detachable sub-windows, allowing the inventory, chat history, IM, etc. windows to be moved to a second monitor (if available). This is a very highly-desired feature (by those that have dual-monitor systems). [[User:Buckaroo Mu\|Buckaroo Mu]] 09:37, 9 January 2007 (PST)

Buckaroo Mu: Feature Request: DirectX3D or GPGPU Support

2007-01-09T17:28:52Z

Feature Request: DirectX3D or GPGPU Support

← Older revision		Revision as of 10:28, 9 January 2007
Line 8:		Line 8:
	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.		Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea.

	== ~~List of~~ Feature Requests ==		== Minor Feature Requests ==
	*Add a "link" ("alias", "shortcut") facility to the inventory, that would not break Permissions. For instance, I have one nice set of prim dress shoes that are no-copy, and four tuxedos. I cannot make complete ~~seperate~~ outfits, because I have only one copy of the shoes. However, using a "link", I could create an outfit folder with the tux and a link to the no-copy shoes. Still means I would only have the one set, but it would make changing clothes much much easier. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:23, 9 January 2007 (PST)		*Add a "link" ("alias", "shortcut") facility to the inventory, that would not break Permissions. For instance, I have one nice set of prim dress shoes that are no-copy, and four tuxedos. I cannot make complete separate outfits, because I have only one copy of the shoes. However, using a "link", I could create an outfit folder with the tux and a link to the no-copy shoes. Still means I would only have the one set, but it would make changing clothes much much easier. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:23, 9 January 2007 (PST)

			== Major Feature Requests ==
			*A DirectX3D-driven version of the viewer, allowing those with ATi or Intel hardware accelerated cards to take advantage of the processing power. Alternatively, a method of offloading some of the [http://www.gpgpu.org/ graphics processing to the GPU] might help increase framerate. [[User:Buckaroo Mu\|Buckaroo Mu]] 09:28, 9 January 2007 (PST)