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?
> 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.
> 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.
If you are going to make proposals like that, you really need to go into
serious detail, show code, etc.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
