On Wed, 26 Jul 2000, you wrote:
> on 7/25/2000 8:26 PM, "Jian He" <[EMAIL PROTECTED]> wrote:
>
> > ?? ??, 26 7?? 2000 , ??????:
> >> on 7/25/2000 6:07 AM, "Jian He" <[EMAIL PROTECTED]> wrote:
> >>
> >>> How about divide turbine into 4 layers: UIPL, UIOL, BOL, OPL
> >>
> >> Exactly what purpose would that serve?
> >>
> >
> > I thinking turbine is a very good framework for web application developing,
> > and
> > I wan't to make turbine built according to a layered architecture that
> > insulates applications from the database, and provides a rich set of
> > high-level
> > data structures, and hightly configurable and extensible throgh object
> > definition technology.
>
> Uh. It already does that. What would changing the package names do?
>
Of cause the package names is not the importent. :-)
> > I am thinking turbine enterprise applications can
> > consists of Viewlet, which are largely self-contained visual application
> > units,
> > and Views and Screens, which are navigational constructs.
>
> I do not understand you. You need to give some more detail there.
>
> > Turbine also can
> > provides the ability to reconfigure and extend the Turbine Application by
> > Turbine Tools. Turbine Tools is a web bases software configration toolset,
> > rather than a programming language. It is a declarative software development
> > tool. What this means is that software is developed and enhanced by creating
> > object definitions and setting properties within them. So, the Turbine
> > Enterprise Applications software is built on object definitions that are
> > executed at run time, and are available to the developer to modify. By
> > creating
> > new object definitions(and adapting existing ones to new uses) the developer
> > and create complete new modules. It is usually not necessary for a developer
> > to
> > write program code.
>
> I do not understand you. You need to give some more detail there.
>
I want to make a proposal to implement the UIOL(User Interface Object Layer).
This layer consists of user interface object definitions.
The main object is Application. Application is a collection of screens. The
screens are accessed from the Screens Menu, as defined in the application. Each
combination of screens that is appropriate to a specific class of users can be
provided as an application.
Screen is a logical collection of views. It is not
a visual construct in itself, rather, it is a collection of views that the Menu
Bar and View bar an display. The active screen is selected from the Screens
menu.
View is a collection of viewlets which appear on the screen at the same
time. A view can be thought of as a single windows's worth of related data
forms. The user can select the current view from the View bar. A view is
associated with a single Business Object.
Viewlet is a form, composed of
controls, that occupies a portion of the Application. A viewlet can be
configured to allow data entry, provide a Web browser. It provides viewing,
entry, modification, an navigation copabilities for data in one Business
Component. ...
The definition file are XML format, I named it UIOML(User
Interface Object Markup Language) User can edit XML files to define objects, or
use Configuration Tools to develop objects, these Configuration Tools contains
Viewlet Designer, Menu Designer, Screen Designer, Application Designer... In
other layer, we also need to implement the UIPL Tools, Business Object
Configuration Tools, Data Configuration Tools...
> > Perhaps all these must have a lot of work to do, and waste
> > a lot of times. but i think we can doing the following steps:
> > 1. Defining the
> > layers.
> > 2. Implementing the User Interface Object Layer, implementing the
> > Application, Menu, Toolbar, Screen, View, Viewlet, Controls, ListView,
> > FormView, TreeView, ChartView...
> > 3. Implementing the User Interface
> > Configurating tools.
> > 4. Implementing the Business Object Layer, implementing
> > BusinessObject, BusinessCompoment, Link, Join, Field...
> > 5. Implementing the
> > Business Object Configurating tools.
> > 6. ...
> >
> > If this message is not suitable for turbine, i apologized. Perhaps it's
> > suitable for creating another project such as Web Based Enterprise Application
> > Framework.
>
> Uh Turbine is a "Web Based Enterprise Application Framework" and already
> gives you the ability to do what you want to do without changing a single
> line of code.
>
I agree it. :-)
> If you are going to make proposals like that, you really need to go into
> serious detail, show code, etc.
>
All these is almost just in my mind.
If you agree it, I will start to work, and send you the code as fast as i can, but the
works is serious big.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
