JADE (programming language): Difference between revisions
WP:NOTHOWTO; Undid revision 1188623518 by WonderXcom (talk) |
No edit summary |
||
| Line 8: | Line 8: | ||
{{Use dmy dates|date=June 2014}} | {{Use dmy dates|date=June 2014}} | ||
[[File:JADE (programming language) logo.svg|thumb|The Jade Software Corporation logo]] | [[File:JADE (programming language) logo.svg|thumb|The Jade Software Corporation logo]] | ||
'''JADE''' is a proprietary [[object-oriented]] software development and deployment platform product from the New Zealand-based [[Jade Software Corporation]], first released in 1996.<ref>{{cite web|url=https://www.jadeworld.com/who-we-are/ | title=Jade – Who We Are |publisher=[[Jade Software Corporation]]}}</ref><ref>{{cite web|url=https://www.zdnet.com/article/jade-delivers-version-7-1/|title=Jade Software delivers Jade 7.1|publisher=[[ZDnet]]|accessdate=21 December 2019}}</ref> It consists of the JADE programming language, [[Integrated development environment]] and [[debugger]], integrated [[application server]] and [[object database]] management system. | '''JADE''' is a proprietary [[object-oriented]] software development and deployment platform product from the New Zealand-based [[Jade Software Corporation]], which was first released in 1996.<ref>{{cite web|url=https://www.jadeworld.com/who-we-are/ | title=Jade – Who We Are |publisher=[[Jade Software Corporation]]}}</ref><ref>{{cite web|url=https://www.zdnet.com/article/jade-delivers-version-7-1/|title=Jade Software delivers Jade 7.1|publisher=[[ZDnet]]|accessdate=21 December 2019}}</ref> It consists of the JADE programming language, [[Integrated development environment]] and [[debugger]], integrated [[application server]] and [[object database]] management system. | ||
Designed as an end-to-end development environment to allow systems to be coded in one language from the [[database server]] down to the [[client (computing)|clients]], it | Designed as an end-to-end development environment to allow systems to be coded in one language from the [[database server]] down to the [[client (computing)|clients]], it provides [[API]]s for other languages, including [[.NET Framework]],<ref name="dotNET">{{cite web|url=http://www.scoop.co.nz/stories/BU0905/S00125.htm|title=Scoop Independent News – JADE 6.3|accessdate=21 December 2019}}</ref> [[Java (programming language)|Java]], [[C (programming language)|C]]/[[C++]] and [[Web service]]s. | ||
Although a free limited | Although, a free limited license is available for development, using the JADE platform requires per-process fees to be paid. | ||
==Language== | ==Language== | ||
| Line 20: | Line 20: | ||
===Programming model=== | ===Programming model=== | ||
Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but does not support the overloading of methods or operators, and until Jade 2018 lacked parameterised constructors.<ref name="obscure"/> | Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but it does not support the overloading of methods or operators, and until Jade 2018 lacked parameterised constructors.<ref name="obscure"/> | ||
Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model–view–controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema. | Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model–view–controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema. | ||