IFrame App - Revision history

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

2023-05-16T16:37:25Z

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

← Older revision		Revision as of 18:37, 16 May 2023
Line 1:		Line 1:
	~~__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		[[File:Iframe app example.png\|thumb\|The Windows 96 Wiki application represents a typical iframe app.]]
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		An "iFrame App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said iFrame will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API.
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		Iframe apps are extremely simple to create, and require little to no effort compared to more complex applications. This is sometimes useful for hosting external content which does not necessarily want to rely on Windows 96 specific APIs.
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		=== Subtypes ===
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		==== Hosted ====
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		A hosted IFrame app is an application which has its resources hosted on the Windows 96 server itself. Hosted iFrame apps have the advantage of being able to access the top level window object without restrictions, since they are hosted on the same origin. This access usually allows hosted iFrame apps to integrate more directly with the Windows 96 environment, since all APIs are available to the frame.
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		=== Criticism ===
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~		A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~
	~~NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD~~

94.233.241.205: SEXX

2023-05-16T06:57:52Z

SEXX

← Older revision		Revision as of 08:57, 16 May 2023
Line 1:		Line 1:
	~~[[File:Iframe app example.png\|thumb\|The Windows 96 Wiki application represents a typical iframe app.]]~~		__NOTOC__NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	An "iFrame App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said iFrame will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API.		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	Iframe apps are extremely simple to create, and require little to no effort compared to more complex applications. This is sometimes useful for hosting external content which does not necessarily want to rely on Windows 96 specific APIs.		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	~~=== Subtypes ===~~		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	~~==== Hosted ====~~		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	A hosted IFrame app is an application which has its resources hosted on the Windows 96 server itself. Hosted iFrame apps have the advantage of being able to access the top level window object without restrictions, since they are hosted on the same origin. This access usually allows hosted iFrame apps to integrate more directly with the Windows 96 environment, since all APIs are available to the frame.		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	~~=== Criticism ===~~		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
	~~A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.~~		NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD
			NIGGA NIGGER FAGGOT EGG IS RETARD YOU ARE RETARD

Ctrl: the current history section is unnecessary - this is simply a page describing iframe apps and what they are

2023-02-11T18:27:05Z

the current history section is unnecessary - this is simply a page describing iframe apps and what they are

← Older revision		Revision as of 20:27, 11 February 2023
Line 11:		Line 11:
	=== Criticism ===		=== Criticism ===
	A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.		A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.

	~~===History===~~
	The first iFrame App was made by [[billygoat891]] and was called [[MyTube]], a (pretty basic) youtube revival. Billy decided he did not want to update this app all the time so instead hosted his site on GitHub pages and made the app simply have an <code><iframe></code> inside pointing to this website. Other people allegedly then copied his code for their own low-effort iFrame Apps, which simply pointed to another website they didn't even own. This led to billy trying to erase all evidence of its existence because of the plague caused by it. Unfortunately for him there were too many clones by that point, and [[MyTube]] was lost to time and forgotten.

NanderTGA: Added some history about how iFrame Apps were born, information provided by billygoat891

2023-01-27T22:21:13Z

Added some history about how iFrame Apps were born, information provided by billygoat891

← Older revision		Revision as of 00:21, 28 January 2023
Line 11:		Line 11:
	=== Criticism ===		=== Criticism ===
	A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.		A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.

			===History===
			The first iFrame App was made by [[billygoat891]] and was called [[MyTube]], a (pretty basic) youtube revival. Billy decided he did not want to update this app all the time so instead hosted his site on GitHub pages and made the app simply have an <code><iframe></code> inside pointing to this website. Other people allegedly then copied his code for their own low-effort iFrame Apps, which simply pointed to another website they didn't even own. This led to billy trying to erase all evidence of its existence because of the plague caused by it. Unfortunately for him there were too many clones by that point, and [[MyTube]] was lost to time and forgotten.

Ctrl at 22:09, 17 November 2022

2022-11-17T22:09:25Z

← Older revision		Revision as of 00:09, 18 November 2022
Line 1:		Line 1:
	[[File:Iframe app example.png\|thumb\|The Windows 96 Wiki application represents a typical iframe app.]]		[[File:Iframe app example.png\|thumb\|The Windows 96 Wiki application represents a typical iframe app.]]
	An "~~Iframe~~ App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said ~~Iframe~~ will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API.		An "iFrame App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said iFrame will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API.

	Iframe apps are extremely simple to create, and require little to no effort compared to more complex applications. This is sometimes useful for hosting external content which does not necessarily want to rely on Windows 96 specific APIs.		Iframe apps are extremely simple to create, and require little to no effort compared to more complex applications. This is sometimes useful for hosting external content which does not necessarily want to rely on Windows 96 specific APIs.

	=== ~~Criticism~~ ===		=== Subtypes ===
	~~A lot of users and developers are against Iframe apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.~~

	=== ~~History~~ ===		==== Hosted ====
	~~The first Iframe App seems~~ to ~~be [https://rel2sp2.windows96.net/data/api-examples/Guided%20Samples/3_Iframeable%20App.js an API example from v2] probably made by [[Ctrlz]]~~. This ~~app had an iframe pointing~~ to ~~[https://sys36.net sys36.net]and originated from [[~~Windows 96 ~~v2 Service Pack 1]]~~.		A hosted IFrame app is an application which has its resources hosted on the Windows 96 server itself. Hosted iFrame apps have the advantage of being able to access the top level window object without restrictions, since they are hosted on the same origin. This access usually allows hosted iFrame apps to integrate more directly with the Windows 96 environment, since all APIs are available to the frame.

	~~the first ''community-made'' Iframe App I([[User:NanderTGA\|NanderTGA]]) could find was RecordRTC by Jame AKA ctrli~~, ~~uploaded in a thread on discord (in the creations channel)~~ to ~~publish packages for Nander to upload to his repository. This package was never uploaded as he either forgot or didn't want to convert~~ the ~~icon to a different resolution~~.		=== Criticism ===
			A lot of users and developers object to most simple iFrame apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.

2A02:1812:1E05:B500:198D:6626:EA49:E9E6: added a bit of history

2022-07-31T13:08:31Z

added a bit of history

← Older revision		Revision as of 15:08, 31 July 2022
Line 6:		Line 6:
	=== Criticism ===		=== Criticism ===
	A lot of users and developers are against Iframe apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.		A lot of users and developers are against Iframe apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.

			=== History ===
			The first Iframe App seems to be [https://rel2sp2.windows96.net/data/api-examples/Guided%20Samples/3_Iframeable%20App.js an API example from v2] probably made by [[Ctrlz]]. This app had an iframe pointing to [https://sys36.net sys36.net]and originated from [[Windows 96 v2 Service Pack 1]].

			the first ''community-made'' Iframe App I([[User:NanderTGA\|NanderTGA]]) could find was RecordRTC by Jame AKA ctrli, uploaded in a thread on discord (in the creations channel) to publish packages for Nander to upload to his repository. This package was never uploaded as he either forgot or didn't want to convert the icon to a different resolution.

Ctrl: Created page with "The Windows 96 Wiki application represents a typical iframe app. An "Iframe App" refers to a single-window application which simply incorporates a full size </code> element filled to the window content container. Said Iframe will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API. Iframe apps are extremely si..."</h1> <p>2022-04-09T05:01:57Z</p> <p>Created page with "<a href="/wiki/File:Iframe_app_example.png" title="File:Iframe app example.png">thumb|The Windows 96 Wiki application represents a typical iframe app.</a> An "Iframe App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said Iframe will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API. Iframe apps are extremely si..."</p> <p><b>New page</b></p><div>[[File:Iframe app example.png|thumb|The Windows 96 Wiki application represents a typical iframe app.]]<br /> An "Iframe App" refers to a single-window application which simply incorporates a full size <code><iframe></code> element filled to the window content container. Said Iframe will usually point to an external resource (resource not hosted within the Windows 96 environment) and will have very little logic to integrate with the Windows 96 API.<br /> <br /> Iframe apps are extremely simple to create, and require little to no effort compared to more complex applications. This is sometimes useful for hosting external content which does not necessarily want to rely on Windows 96 specific APIs.<br /> <br /> === Criticism ===<br /> A lot of users and developers are against Iframe apps, since they are extremely easy to code and require almost no knowledge of the Windows 96 API and program structure.</div> </article> </main></body></html>