Theming - Revision history

Utf: Reverted edits by 94.233.241.205 (talk) to last revision by Kelbaz

2023-05-16T16:41:14Z

Reverted edits by 94.233.241.205 (talk) to last revision by Kelbaz

Show changes

94.233.241.205: SEXX

2023-05-16T06:57:54Z

SEXX

Show changes

Kelbaz at 11:28, 20 March 2023

2023-03-20T11:28:12Z

← Older revision		Revision as of 13:28, 20 March 2023
Line 27:		Line 27:
	A typical (minimal) theme setup looks as follows<syntaxhighlight lang="text">		A typical (minimal) theme setup looks as follows<syntaxhighlight lang="text">
	c:/system/resource/themes/sample		c:/system/resource/themes/sample
	├ manifest.json		├─ manifest.json
	└ theme.css		└─ theme.css
	</syntaxhighlight>where		</syntaxhighlight>where

	* <code>manifest.json</code> is a theme manifest telling the theme engine how the theme should behave and what content to load to render the theme properly.		* <code>manifest.json</code> is a theme manifest telling the theme engine how the theme should behave and what content to load to render the theme properly.
	* <code>theme.css</code> is the stylesheet specifying which styles to modify.		* <code>theme.css</code> is the stylesheet specifying which styles to modify.

Kelbaz: Tweaking the codeblock to actual "tree" command

2023-03-20T11:27:18Z

Tweaking the codeblock to actual "tree" command

← Older revision		Revision as of 13:27, 20 March 2023
Line 26:		Line 26:
	==== Example setup ====		==== Example setup ====
	A typical (minimal) theme setup looks as follows<syntaxhighlight lang="text">		A typical (minimal) theme setup looks as follows<syntaxhighlight lang="text">
	+ c:/system/resource/themes/sample		c:/system/resource/themes/sample
	~~\| -->~~ manifest.json		├ manifest.json
	~~\| -->~~ theme.css		└ theme.css
	</syntaxhighlight>where		</syntaxhighlight>where

	* <code>manifest.json</code> is a theme manifest telling the theme engine how the theme should behave and what content to load to render the theme properly.		* <code>manifest.json</code> is a theme manifest telling the theme engine how the theme should behave and what content to load to render the theme properly.
	* <code>theme.css</code> is the stylesheet specifying which styles to modify.		* <code>theme.css</code> is the stylesheet specifying which styles to modify.

Kelbaz: updated default themes

2023-03-12T15:12:17Z

updated default themes

← Older revision		Revision as of 17:12, 12 March 2023
Line 19:		Line 19:
	*OS X Snow Leopard (icon theme using OS X icons)		*OS X Snow Leopard (icon theme using OS X icons)
	*Utopia (sound scheme)		*Utopia (sound scheme)
			*XP (a Windows XP theme including 4 variants)

	=== Theme Structure ===		=== Theme Structure ===

216.164.130.12: /* Acquiring Themes */

2023-02-05T04:32:05Z

Acquiring Themes

← Older revision		Revision as of 06:32, 5 February 2023
Line 5:		Line 5:

	=== Acquiring Themes ===		=== Acquiring Themes ===
	~~NININNINININININUsers~~ can acquire new themes and customizations for their system by searching through the package store, checking the preinstalled collection, or importing them from an external source (such as a forum or community).		Users can acquire new themes and customizations for their system by searching through the package store, checking the preinstalled collection, or importing them from an external source (such as a forum or community).

	New themes can also be created within the Windows 96 environment. Read more [[Creating a theme\|here]].		New themes can also be created within the Windows 96 environment. Read more [[Creating a theme\|here]].

216.164.130.12: /* Acquiring Themes */ njnnjn

2023-02-05T04:31:48Z

Acquiring Themes: njnnjn

← Older revision		Revision as of 06:31, 5 February 2023
Line 5:		Line 5:

	=== Acquiring Themes ===		=== Acquiring Themes ===
	~~Users~~ can acquire new themes and customizations for their system by searching through the package store, checking the preinstalled collection, or importing them from an external source (such as a forum or community).		NININNINININININUsers can acquire new themes and customizations for their system by searching through the package store, checking the preinstalled collection, or importing them from an external source (such as a forum or community).

	New themes can also be created within the Windows 96 environment. Read more [[Creating a theme\|here]].		New themes can also be created within the Windows 96 environment. Read more [[Creating a theme\|here]].

User3412 at 21:53, 1 December 2022

2022-12-01T21:53:15Z

← Older revision		Revision as of 23:53, 1 December 2022
Line 14:		Line 14:
	* Windows 96 (the default theme)		* Windows 96 (the default theme)
	* Base (a remix of the default theme using free icons)		* Base (a remix of the default theme using free icons)
	* Dev (a development theme to use to check icon sizes, etc.		* Dev (a development theme to use to check icon sizes, etc.)
	* Windows 98 (a theme mimicking Windows 98)		* Windows 98 (a theme mimicking Windows 98)
	* Windows 2000 (a theme mimicking Windows 2000)		* Windows 2000 (a theme mimicking Windows 2000)

HolyNetworkAdapter: removing outdated content

2022-11-06T21:31:13Z

removing outdated content

← Older revision		Revision as of 23:31, 6 November 2022
Line 13:		Line 13:

	* Windows 96 (the default theme)		* Windows 96 (the default theme)
	* Aero (a theme mimicking Windows 7)
	* Base (a remix of the default theme using free icons)		* Base (a remix of the default theme using free icons)
	* Dev (a development theme to use to check icon sizes, etc.		* Dev (a development theme to use to check icon sizes, etc.
	* Windows 98 (a theme mimicking Windows 98)		* Windows 98 (a theme mimicking Windows 98)
	* Windows 2000 (a theme mimicking Windows 2000)		* Windows 2000 (a theme mimicking Windows 2000)
	* ~~Wxp~~ (a theme ~~mimicking Windows XP~~)		*OS X Snow Leopard (icon theme using OS X icons)
			*Utopia (sound scheme)

	=== Theme Structure ===		=== Theme Structure ===

Ctrl: Created page with "An example of a custom theme. Based on Windows Longhorn, created by trabis. Windows 96 includes a powerful theming engine to allow you to create incredibly complex and beautiful themes. Themes are made up of stylesheets, scripts, images, and other resources. They can optionally provide a custom sound pack or icon theme, to further cus..."

2022-04-09T03:33:41Z

Created page with "alt=An example of a transformative theme. Based on Windows Longhorn, created by Legoman|thumb|An example of a custom theme. Based on Windows Longhorn, created by trabis. Windows 96 includes a powerful theming engine to allow you to create incredibly complex and beautiful themes. Themes are made up of stylesheets, scripts, images, and other resources. They can optionally provide a custom sound pack or icon theme, to further cus..."

New page

[[File:Legoman longhorn theme preview.png|alt=An example of a transformative theme. Based on Windows Longhorn, created by Legoman|thumb|An example of a custom theme. Based on Windows Longhorn, created by trabis.]]
Windows 96 includes a powerful theming engine to allow you to create incredibly complex and beautiful themes.

Themes are made up of stylesheets, scripts, images, and other resources. They can optionally provide a custom sound pack or icon theme, to further customize the user experience.

=== Acquiring Themes ===
Users can acquire new themes and customizations for their system by searching through the package store, checking the preinstalled collection, or importing them from an external source (such as a forum or community).

New themes can also be created within the Windows 96 environment. Read more [[Creating a theme|here]].

==== Preinstalled Examples ====
Windows 96 includes a few themes by default, namely

* Windows 96 (the default theme)
* Aero (a theme mimicking Windows 7)
* Base (a remix of the default theme using free icons)
* Dev (a development theme to use to check icon sizes, etc.
* Windows 98 (a theme mimicking Windows 98)
* Windows 2000 (a theme mimicking Windows 2000)
* Wxp (a theme mimicking Windows XP)

=== Theme Structure ===
Each theme has its own directory, and is usually saved at <code>C:/system/resource/themes/<theme_id></code> (where <code><theme_id></code> is a user defined identifier for the theme). The theme identifier may not include spaces, must not start with a number, and must be alphanumeric.

==== Example setup ====
A typical (minimal) theme setup looks as follows<syntaxhighlight lang="text">
+ c:/system/resource/themes/sample
| --> manifest.json
| --> theme.css
</syntaxhighlight>where

* <code>manifest.json</code> is a theme manifest telling the theme engine how the theme should behave and what content to load to render the theme properly.
* <code>theme.css</code> is the stylesheet specifying which styles to modify.