Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Interface description language


Related Topics

In the News (Mon 13 Oct 08)

  
  udk: Unoidl syntax description
Idl is a language to describe interfaces and types independently of any programming language and hardware platform.
An idl description is used by the idl compiler to generate code for these interfaces in a selected target language.
Because the lexical conventions of the idl and the structure of the definitions have a large degree with the ANSI standard for C++.
udk.openoffice.org /common/man/idl_syntax.html   (649 words)

  
  Interface description language : IDL
IDLs are used in situations where the software on either side may not share common "call semantics", referring to the way the computer language "talks" to the routines.
IDLs are a subset of both, a general language to which both can conform to enable language-independent code.
IDLs are most commonly found in software intended to allow routines to be called on other machines, known as remote procedure call.
www.wordlookup.net /id/idl.html   (325 words)

  
 Interface description language - Wikipedia, the free encyclopedia
An Interface Description Language (or alternately, Interface Definition Language), or IDL for short, is a computer language used to describe a software component's interface.
IDLs describe an interface in a language-neutral way, enabling communication between software components that do not share a language – for example, between components written in C and components written in Pascal.
IDL specification language, the original Interface Description Language.
en.wikipedia.org /wiki/Interface_description_language   (194 words)

  
 OMG IDL
Interfaces for OMG's standard CORBAservices, CORBAfacilities, and Domain Facilities are all specified in OMG IDL.
IDL interface definitions are elegant and (usually!) easy to write and understand.
A mapping assigns a language variable type to each IDL variable type, and a translation from IDL's operation format to the language's invocation of a member function or other operation invocation format.
www.omg.org /gettingstarted/omg_idl.htm   (1189 words)

  
 The Zephyr Abstract Syntax Description Language
Figure 2 is a description of the lexical structure of tokens used in the ASDL grammar in Figure 1.
The description language and external data encoding are fixed; the particular target language interfaces are not.
Although the ASDL description is not a verbatim translation of the C++ implementation, the majority of the ASDL description captures most of the features of the C++ implementation in a natural way.
www.cs.princeton.edu /~danwang/Papers/dsl97/dsl97.html   (6337 words)

  
 DMA Interface and Process Model
A COM interface can also be described in C or C++ by declaring a typedef for a pointer to a C struct that has fields which are pointers to functions.
Interface inheritance, i.e., C++ class inheritance, is a C++ language concept that has no counterpart in the C language.
In addition to the IUnknown interface (which must be supported by all COM objects), DMA requires all DMA objects to support the IdmaProperties and IdmaObject interfaces.
www.infonuovo.com /dma/dma1.0-7/interf.htm   (2292 words)

  
 [No title]
The generated language specific modules are used by programmers to implement server objects (usually by inheriting from automatically generated parent classes) and/or to generate typed references to remote objects.
For interface types, the language specific types (usually a class) are used by programmers to construct servers (via subclassing of automatically generated parent classes) and/or to generate typed references to remote objects after narrowing.
Interfaces that inherit from other interfaces are termed subclasses (for historical reasons) of those in- terfaces and this relationship applies transitively.
www.usenix.org /publications/library/proceedings/coots95/full_papers/muckelbauer.txt   (8690 words)

  
 Performance Testing: Interface description language
It is essentially a common language for writing the "manual" on how to use a piece of software from another piece of software, in much the same fashion that a user manual describes how to use a piece of software to the user.
IDLs are used in situations where the software on either side may not share common "call semantics", referring to the way the computer language "talks" to the routines.
IDLs are a subset of both, a general language to which both can conform to enable language-independent code.
www.stens.ca /kb/IDL   (218 words)

  
 XPIDL - MDC
XPIDL is an Interface Description Language used to specify XPCOM interface classes.
Interface Description Languages (IDL) are used to describe interfaces in a language- and machine-independent way.
IDLs make it possible to define interfaces which can then be processed by tools to autogenerate language-dependent interface specifications.
developer.mozilla.org /en/docs/XPIDL   (119 words)

  
 W3C Workshop on Multimodal Interaction. Position Paper: The MONA Project
Using our language, they were able to reproduce their imagined user interfaces with high accuracy on these devices.
We believe that our experimental language addresses many of the issues required for this language, as well as for the interface language to the application.
Language elements and structure might as well be expressed in any other XML format, for example as a namespace to extend other languages.
www.w3.org /2004/02/mmi-workshop/simon-ftw.html   (1828 words)

  
 Uno/Article/Understanding Uno - OpenOffice.org Wiki
This language is used to describe the types defined by a component.
To make a language available for UNO, a bridge between this language and UNO has to be created.
In order to be used in the programming language, the IDL specifications have to be translated.
wiki.services.openoffice.org /wiki/Uno/Article/Understanding_Uno   (1758 words)

  
 InterfaceSpecification/InterfaceTable - GNOME Live!
FreeDesktop.org provide interfaces that are followed so that interface consumers may integrate applications into both the GNOME and KDE desktops.
Interface consumers are encouraged to use interfaces as documented.
These interfaces ensure a high degree of stability because running 'make check' is used to verify that the built libraries conform to an expected listing of symbols via the abicheck script.
live.gnome.org /InterfaceSpecification/InterfaceTable   (894 words)

  
 Interface Definition Language   (Site not responding. Last check: 2007-10-15)
IDL provides the standard interface between objects, and is the base mechanism for object interaction.
IDL (Interface Definition Language) is the base mechanism for object interaction.
A complete compiler of IDL would translate IDL into client side and server side routines for remote communication in the same manner as Sun's current RPCL compiler.
burks.bton.ac.uk /burks/foldoc/65/58.htm   (190 words)

  
 XPCOM Part 2: XPCOM component basics
The language-neutral way to specify an interface is to use an IDL or interface description language.
Since the interface description (in the form of a C++ header file) is used at compile time, it is referred to as early binding.
The XPIDL syntax for specifying an interface is; the
www-106.ibm.com /developerworks/components/library/co-xpcom2.html   (3054 words)

  
 IDLE: Unified W3-Access to Interactive Information Servers
IDLE is a language designed to describe the user interface of interactive information servers in a way that allows automatic translation of W3-requests to server-commands.
The language IDLE allows the programmer to concentrate on the hard part of the task: automating the user interaction required to fetch useful data from an interactive information server.
Of course, the ability to read and understand interface descriptions written in IDLE is one of the key aspects of a translation server.
www.perrochon.com /archiv/pubs/95www3/95www3.html   (3843 words)

  
 Roadmap for Language-Agnostic Scripting Support
Furthermore, a component will be able to manipulate (or be manipulated by) another component without regard for the language in which either is implemented.
An XPConnect interface flattening scheme is required for reflecting multiple DOM interfaces on JavaScript objects for cases where the interfaces are not part of an inheritance chain.
Once the DOM interfaces have been recast using XPIDL, an alternative scripting environment could, in theory, be supported in the browser by simply writing an XPConnect binding for the language (e.g., "PerlConnect" or "PythonConnect").
www.mozilla.org /scriptable/agnostic.html   (617 words)

  
 User Interface Tailoring using Semantic Information
Assuming a general model that partitions user interfaces into windows and widgets, a window is generally visualized unaltered on each platform, from a compositional point of view, although using different platform specific widgets.
Semantic information about the relation between widgets is inserted into a user interface description language with what might be called the XML Semantic Linking Language (XSLink), which needs to be defined.
The description results in a semantic net, on which the clustering process is based.
www.w3.org /2002/07/DIAT/posn/salzburg.html   (712 words)

  
 SRPC Interface Description Language (SIDL)   (Site not responding. Last check: 2007-10-15)
SIDL is a language for describing the interface provided by an
Before implementing a server, the programmer should create an SIDL file describing the server's interface.
An SIDL procedure definition gives the name and arguments of a procedure offered by the interface which is being described.
www.cs.princeton.edu /shrimp/Srpc/sidl.html   (393 words)

  
 Component Architectures
A software component is a set of objects with published interfaces, and it obeys the rules specified by the underlying component model.
Though these IDLs differ in syntax, they can be used to specify almost the same concept of an interface.
An interface consists of a set of ``functions'' or ``methods'' with typed parameters, and return types.
charm.cs.uiuc.edu /papers/MilindThesis.www/node7.html   (441 words)

  
 CS210: Advanced Software Paradigms   (Site not responding. Last check: 2007-10-15)
A textual description of an interface may be written in an interface description language (IDL).
Ideally, the IDL is just a subset of the programming language that the developer uses.
A language-independent IDL allows components to be written in different programming languages based on how well the language solves a particular problem.
www.seas.gwu.edu /~cs210/ComponentIDM.htm   (209 words)

  
 Index (Queen's Interface Description Language)
This is the Queen's Java Implementation of IDL -- the Interface Description Language (from "IDL: Sharing Intermediate Representations", ACM Transactions on Programming Languages and Systems 9,3 (July 1987), pp.
This is the Queen's Java Implementation of the IDL translator -- the Interface Description Language (from "IDL: Sharing Intermediate Representations", ACM Transactions on Programming Languages and Systems 9,3 (July 1987), pp.
An implementation of interface CharStream, where the stream is assumed to contain only ASCII characters (without unicode processing).
www.cs.queensu.ca /~dalamb/java/doc/idl/index-all.html   (900 words)

  
 Cover Pages: XML Markup Languages for User Interface Definition
At runtime a user interface description is generated by means of XML as a description language.
The interface component describes the interaction between the user and the application using a set of abstract parts, events, and method calls that are device and application independent.
The structure describes the organization of the parts in the interface, the style describes the presentation specific properties of each part, the content describes the information that is presented to the user, and the behavior describes user interaction with the interface in a platform-independent manner.
xml.coverpages.org /userInterfaceXML.html   (8837 words)

  
 Inter-Language Unification -- ILU
The object interfaces provided by ILU hide implementation distinctions between different languages, between different address spaces, and between operating system types.
ILU interfaces are specified in ILU's Interface Specification Language.
As a result, ILU provides support for use of the OMG CORBA IDL interface description language, and can be thought of as a CORBA ORB system (though with omissions from and extensions to the CORBA spec).
www.cs.umbc.edu /kqml/ilu   (1017 words)

  
 Aldec Inc. - The Design Verification Company - Products - Riviera - Extensive Language Support
VHDL or the VHSIC Hardware Description Language is a well-known industrial standard first introduced in 1987.
Verilog is another Hardware Description Language intended for use in all phases of the creation of electronic systems.
The new languages integrate seamlessly with the regular HDL flow.
www.aldec.com /products/riviera/pages/extensivelanguagesupport   (419 words)

  
 Interface Description Language   (Site not responding. Last check: 2007-10-15)
(IDL) A language designed by Nestor, Lamb and Wulf of CMU in 1981 for describing the data structures passed between parts of an application, to provide a language-independent intermediate representation.
Not to be confused with any of the other IDLs.
["The Interface Description Language: Definition and Use," by Richard Snodgrass, Computer Science Press, 1989, ISBN 0-7167-8198-0].
burks.bton.ac.uk /burks/foldoc/66/58.htm   (88 words)

  
 A Plattform-Independent User Interface Description Language   (Site not responding. Last check: 2007-10-15)
Often the user interface of a stand-alone application and a Web-based interface are simultaneously used.
In traditional clients the layout and the behavior is redundantly hard coded in a specific language such as C++ or Java.
Although they deal with user interface descriptions their realization concept and their aim are different.
www.ssw.uni-linz.ac.at /Research/Reports/Report16/Report16.html   (396 words)

  
 UIML.org   (Site not responding. Last check: 2007-10-15)
Our goal is to create an open standard user interface description language in XML that can be freely implemented by anyone.
The motivation is to facilitate better tools for creation of user interfaces that work on any platform available today, but which also will allow today's legacy user interfaces to evolve to new forms for use on platforms that are created years from now.
Work started in 1997 to define a canonical meta-language that can describe any user interface in a manner that is device-independent and user interface metaphor independent.
www.uiml.org   (237 words)

  
 Software Component Interface Description in SGML
In addition to such multiple language bindings, code generated from such an interface description can include proxy objects for distributed object access, script language interfaces to objects, and generic attribute interfaces enabling object database access and SGML externalizations of objects.
In this case the interface and the implementation are the same, and typedefs were used to combine the two concepts syntactically.
This approach ultimately results in the programmer doing the code generator's job, since the programmer must modify a description of the interface in both the native language's syntax and the structured comment syntax, and make sure they are consistent.
www.oasis-open.org /cover/mccoolSoftwareComponent.html   (4299 words)

  
 Software Advances and their Impact on the Design of Nuclear Data Acquisition Systems -- What are Distributed Objects   (Site not responding. Last check: 2007-10-15)
In an RPC environment, one describes a procedural interface using an interface description language.
The interface description is compiled producing header files and server and client stub files.
The compilation of the interface description language produces header files and stub files in a manner analogous to RPC.
www.msu.edu /user/foxr/cgrptr1/final_19.html   (484 words)

  
 VRIXML : A User Interface Description Language for Virtual Environments
Part of this interaction is supported by a user interface, which can be used to manipulate the objects that are contained in the environment.
This paper investigates the possibility of using a XMLbased user interface description language in order to design a user interface and specify its behavior within the virtual environment.
Some existing languages are examined and compared, and afterwards the syntax and features of our own description language, called VRIXML, are presented.
www2.edm.uhasselt.be /uixml2004/accepted/cuppens2004.html   (119 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.