![]() | This article is rated List-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
I want to help with this content regarding platform-independent application platforms. Each of the products/platforms in the current grid allow web developers to produce applications that run and behave as native applications on a variety of desktop and/or mobile platforms.
There is clearly critical mass in this category as the pendulum swings back to native apps from pure browser based apps that were championed as part of the customer adoption trends Web 2.0 and SaaS. Adobe AIR, Sun Java FX and Microsoft Silverlight are huge players driving these solutions for the desktop. Appcelerator Titanium, Nitobi PhoneGap and Rho's RhoMobile lead a pack of up-and-coming products that address mobile alonge with desktop solutions.
In my opinion, this page is inappropriately titled. Internet application frameworks tend to be javascript/ajax libraries. examples include: jQuery, MooTools, scriptalicious, etc. A better title could be "Multi-Platform Application Development"
Discussion, please, so we can confidently move forward.
Freedman1 ( talk) 19:25, 30 November 2009 (UTC)
Voldik666 ( talk) 09:27, 1 March 2010 (UTC)
I disagree, the change would make no reference to the internet, a critical component. D Holliday. —Preceding unsigned comment added by 76.28.206.147 ( talk) 21:35, 11 March 2010 (UTC)
Infiniplex2 ( talk) 19:25, 30 November 2009 (UTC)
The changed title would be misleading, many other things could also be considered multi-platform. For example, anything in Pure Java, and C++ that only uses cross-platform libraries.
Rich Internet applications can be built easily by running a local Web server, such as Apache, or one of the many tiny and faster alternatives, such as Mongoose, as the operating platform. Then the application itself is written in a server-side language, such as PHP. No sandbox, Ajax or other security workarounds are needed, as such a setup has complete access to the local machine's operating system and file system (as complete as any executable file). The user interface is naturally browser windows and tabs, although the browser can be made to generate standalone windows easily.
The principal drawback of this methodology is the rather severe security precautions enforced by most browsers on local operations the first time such applications are run: the user must click at least one obscure warning button to permit operation, or else the application must run in HTTPS using a trusted certificate, which costs a significant amount of money. Just as with executable files, too, malware and viruses are significant risks for the end user.
Another drawback, if the application is to be used by other computers on the Web, is the need to make the local computer visible on the Web. This may involve registering its domain name, tracking WAN IP changes by the ISP, and making NAT or Firewall entries in the local Internet router or wireless adapter.
While I doubt that there is any market penetration of this methodology, it has always been available and, in my experience, works well in all aspects. I use it frequently for my own standalone software tools, particularly where the Internet is used or where quick implementation is needed. The additional functionality of PHP as compared with JavaScript is an advantage. For me, this methodology has replaced the use of Visual C++ and Visual Basic due to its convenience and development speed. David Spector ( user/ talk) 12:35, 15 August 2012 (UTC)
The entries on this list are dated, incomplete and follow no structure. Maintaining this page would be a lot of work and it can be misleading for inexperienced people. Wikipedia is a place for people to aqquire general knowledge, this page goes beyond this mission. Therefore I suggest deleting this topic. 2A03:7846:CDE1:101:B5EB:6AC2:C0CB:228E ( talk) 15:35, 4 February 2023 (UTC)
![]() | This article is rated List-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
I want to help with this content regarding platform-independent application platforms. Each of the products/platforms in the current grid allow web developers to produce applications that run and behave as native applications on a variety of desktop and/or mobile platforms.
There is clearly critical mass in this category as the pendulum swings back to native apps from pure browser based apps that were championed as part of the customer adoption trends Web 2.0 and SaaS. Adobe AIR, Sun Java FX and Microsoft Silverlight are huge players driving these solutions for the desktop. Appcelerator Titanium, Nitobi PhoneGap and Rho's RhoMobile lead a pack of up-and-coming products that address mobile alonge with desktop solutions.
In my opinion, this page is inappropriately titled. Internet application frameworks tend to be javascript/ajax libraries. examples include: jQuery, MooTools, scriptalicious, etc. A better title could be "Multi-Platform Application Development"
Discussion, please, so we can confidently move forward.
Freedman1 ( talk) 19:25, 30 November 2009 (UTC)
Voldik666 ( talk) 09:27, 1 March 2010 (UTC)
I disagree, the change would make no reference to the internet, a critical component. D Holliday. —Preceding unsigned comment added by 76.28.206.147 ( talk) 21:35, 11 March 2010 (UTC)
Infiniplex2 ( talk) 19:25, 30 November 2009 (UTC)
The changed title would be misleading, many other things could also be considered multi-platform. For example, anything in Pure Java, and C++ that only uses cross-platform libraries.
Rich Internet applications can be built easily by running a local Web server, such as Apache, or one of the many tiny and faster alternatives, such as Mongoose, as the operating platform. Then the application itself is written in a server-side language, such as PHP. No sandbox, Ajax or other security workarounds are needed, as such a setup has complete access to the local machine's operating system and file system (as complete as any executable file). The user interface is naturally browser windows and tabs, although the browser can be made to generate standalone windows easily.
The principal drawback of this methodology is the rather severe security precautions enforced by most browsers on local operations the first time such applications are run: the user must click at least one obscure warning button to permit operation, or else the application must run in HTTPS using a trusted certificate, which costs a significant amount of money. Just as with executable files, too, malware and viruses are significant risks for the end user.
Another drawback, if the application is to be used by other computers on the Web, is the need to make the local computer visible on the Web. This may involve registering its domain name, tracking WAN IP changes by the ISP, and making NAT or Firewall entries in the local Internet router or wireless adapter.
While I doubt that there is any market penetration of this methodology, it has always been available and, in my experience, works well in all aspects. I use it frequently for my own standalone software tools, particularly where the Internet is used or where quick implementation is needed. The additional functionality of PHP as compared with JavaScript is an advantage. For me, this methodology has replaced the use of Visual C++ and Visual Basic due to its convenience and development speed. David Spector ( user/ talk) 12:35, 15 August 2012 (UTC)
The entries on this list are dated, incomplete and follow no structure. Maintaining this page would be a lot of work and it can be misleading for inexperienced people. Wikipedia is a place for people to aqquire general knowledge, this page goes beyond this mission. Therefore I suggest deleting this topic. 2A03:7846:CDE1:101:B5EB:6AC2:C0CB:228E ( talk) 15:35, 4 February 2023 (UTC)