BoxScript

2004

ACM Southeast Regional Conference, 2007

BoxScript is a Java-based language that supports the componentoriented programming paradigm. BoxScript introduces a composition strategy and type structure to support two main properties of component-oriented programming, compositionality and flexibility. This paper briefly introduces the fundamental concepts of BoxScript and then describes how BoxScript components (i.e., boxes) are realized as clusters of interrelated Java interfaces, classes, and packages.

Proceeding of the Conference on Applied Research in Information Technology, Acxiom Laboratory for Applied Research, 2005

Component-oriented software development has become an important approach to building complex software systems. This paper describes the component-oriented language BoxScript whose design seeks to support the concepts of components in a clean, simple, Java-based language. This paper presents the key concepts and syntax of BoxScript and how it supports compositionality and flexibility and gives an example to illustrate its usage.

A profound change is taking place in the world of applications programming. Some of the most profound new developments are web-based hosting of components and distributed components that run interactively on several different machines. Students can be exposed to component-level programming through a visual language such as Visual Basic, but this will not expose the student to the full scope of the most recent developments. This paper describes the advances in component-level programming, and gives suggestions for integrating component-level development into existing curricula. The paper first describes custom controls, the precursor to component-level programming, and shows how the concepts of custom controls have evolved into more comprehensive standards. The use of existing components in several different contexts is discussed. The most important contexts are standard application development, web-based design, and distributed application development. We show how a single component...

2020

Although component-based software development have been subject to extensive research for many years, most software systems are still based on the objectoriented paradigm. We believe that one of the main causes is a lack of support for Component-Oriented Programming (COP). Indeed, a lot of work proposed component models such as Unified Modeling Language (UML), Enterprise JavaBeans (EJB) or Corba Component Model (CCM) that are only available at design time. At the implementation stage, object-oriented languages are mainly used which prevent developers to fully switch to COP. In this paper, we identify five requirements (decoupling, adaptability, unplanned connections, encapsulation and uniformity) for COP based on an analysis of the state of the art and limitations of existing work. We then propose an extended version of the Scl component language that fulfills these requirements.

Lecture Notes in Computer Science, 1995

1997

Computer Languages, Systems & Structures, 2008

Lecture Notes in Computer Science, 2007

Computer Languages, Systems & Structures, 2012