by date
Plan for Jules Moloney and Sam Cuttriss
Plan for Jules Moloney and Sam Cuttriss
| Name: | Architecture@Uni Melbourne | |
|---|---|---|
| Date Posted: | Jan 20, 2002 | |
| Rating: | Not Rated | |
| Public: | YES | |
| Comments: | YES | |
| RSS Feed: | or Subscribe with . | |
| Profile Page: | View profile page for Architecture@Uni Melbourne |
Blog post
STRING CVE : Virtual Design Studio for Architectural Education: Collaborative virtual environments (CVE) Our project will add functionality to the Torque engine to allow both synchronous and asynchronous collaboration on University design and research projects in architecture, landscape and urban design.
Current State of Development:
Asynchronous communication functionality has been trialed for a University design class. This curent version allows 3D browsing of comments within the environment that link to a php comments forum. A user eters a comment within the environment and can also add a 2D overlay diagram (white board).
Comments, position and diagram are uploaded.
New Work: (Target completion October 2003)
Real time Database for collaborative design based on the Torque game engine.
The previous research developed an asynchronous design critique and communication tool that enables multiple users to add comments to a fixed data set.This functionality enables real-time viewing of the same data and server based manipulation based on the string world editor (terrain editing, interior / shape displacement, rotation and scale).
However new data cannot be added without re-publishing the entire project an awkward and time consuming operation that hinders design collaboration. In addition the manipulation of this data is one way as only the server user can access the editing tools. What is required is database functionality that allows multiple users to edit and visualise design iterations in real time.
Proposed new functionality:
1.0 Allow multiple users to access a database server and add new design components to existing projects.
2.0 On client log in new design components and design edits added to existing project.
3.0 Any client can manipulate the design (environment and components) and this updates multiple clients in real time.
4.0 Management of the data set is a crucial issue:
4.1 Levels of access would need to be assigned to each user / data set.
4.2 Implementation of a 'save edit' function would be required with each edit able to be restored ( ie. users can step back and forward through design iterations).These iterations identified by title, date and user id.
4.3 Iterations can be 'searched' to speed up locations of edits.
5.0 Existing asynchronous comment( functionality extended to allow comments to be recorded with each design iteration.
Asynchronous communication functionality has been trialed for a University design class. This curent version allows 3D browsing of comments within the environment that link to a php comments forum. A user eters a comment within the environment and can also add a 2D overlay diagram (white board).
Comments, position and diagram are uploaded.
New Work: (Target completion October 2003)
Real time Database for collaborative design based on the Torque game engine.
The previous research developed an asynchronous design critique and communication tool that enables multiple users to add comments to a fixed data set.This functionality enables real-time viewing of the same data and server based manipulation based on the string world editor (terrain editing, interior / shape displacement, rotation and scale).
However new data cannot be added without re-publishing the entire project an awkward and time consuming operation that hinders design collaboration. In addition the manipulation of this data is one way as only the server user can access the editing tools. What is required is database functionality that allows multiple users to edit and visualise design iterations in real time.
Proposed new functionality:
1.0 Allow multiple users to access a database server and add new design components to existing projects.
2.0 On client log in new design components and design edits added to existing project.
3.0 Any client can manipulate the design (environment and components) and this updates multiple clients in real time.
4.0 Management of the data set is a crucial issue:
4.1 Levels of access would need to be assigned to each user / data set.
4.2 Implementation of a 'save edit' function would be required with each edit able to be restored ( ie. users can step back and forward through design iterations).These iterations identified by title, date and user id.
4.3 Iterations can be 'searched' to speed up locations of edits.
5.0 Existing asynchronous comment( functionality extended to allow comments to be recorded with each design iteration.
Recent Blog Posts
| List: | 01/20/02 - Plan for Jules Moloney and Sam Cuttriss 08/05/01 - Plan for Sam Cuttriss |
|---|
Submit your own resources!You must be a member and be logged in to either append comments or rate this resource.


Not Rated


