Difference between revisions of "OpenAsset"
From Ghoulwiki
Ghoulsblade (talk | contribs) (→ideas) |
Ghoulsblade (talk | contribs) (→ideas) |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 28: | Line 28: | ||
== ideas == | == ideas == | ||
| − | * interesting video about "alienbrain" (commercial asset mgmt software) : http://www. | + | * usecase : branching : [http://frittierte-butter.de/~dino/use_case1.png diagram] |
| + | * interesting video about "alienbrain" (commercial asset mgmt software by softimage) : http://www.alienbrain.com/videos.php | ||
* "perforce" seems to be the only big competitor to "alienbrain" : http://www.perforce.com/perforce/products.html | * "perforce" seems to be the only big competitor to "alienbrain" : http://www.perforce.com/perforce/products.html | ||
* HL2/Source level editing videos http://interlopers.net/index.php?page=video | * HL2/Source level editing videos http://interlopers.net/index.php?page=video | ||
* blender script to make model-preview image from grumbel : svn co svn://svn.berlios.de/windstille/trunk/scripts/ | * blender script to make model-preview image from grumbel : svn co svn://svn.berlios.de/windstille/trunk/scripts/ | ||
| − | ** | + | ** [http://pingus.seul.org/~grumbel/tmp/md5/07294e356e1f09425f79dd940dfaadf4-head.png example output] |
| + | |||
| + | == sketches == | ||
| + | |||
| + | * [http://frittierte-butter.de/~dino/use_case1.png diagram_usecase1] (suggestion-branch + direct integration, email notification) | ||
| + | * [http://frittierte-butter.de/~dino/use_case2.png diagram_usecase2] (grant access, revert changes) | ||
| + | * [http://frittierte-butter.de/~dino/use_case2b.png diagram_usecase2b] (branching with seperate lifespan, merge after a longer time) | ||
| + | * [http://xs121.xs.to/xs121/07466/blenderalien.png gui sketch] (17.11.2007, sindwiller) | ||
| + | |||
| + | == Vocabulary == | ||
| + | |||
| + | === ArtObject === | ||
| + | |||
| + | An ArtObject (AO) is one object which might contain several files, like a model and external textures | ||
| + | |||
| + | === Project === | ||
| + | |||
| + | A project is a collection of several AO. Permissions are managed at a project-level. | ||
| + | |||
| + | Only member of a project got write permission. | ||
| + | |||
| + | === Revision === | ||
| + | |||
| + | A revision of an AO is a single version of an AO, | ||
| + | |||
| + | every upload is saved as a new revision, | ||
| + | |||
| + | and it is possible to go back to any of them | ||
| + | |||
| + | |||
| + | |||
| + | == Server == | ||
| + | |||
| + | * php | ||
| + | |||
| + | * storage,versioning,database | ||
| + | |||
| + | == client == | ||
| + | |||
| + | * blender plugin (and browser/website for viewing) | ||
| + | |||
| + | * browse files, download, upload (+generate and append metadata) | ||
| + | |||
| + | * later : view changelog, download specific version | ||
| + | |||
| + | * later : authentification (username/password) | ||
| + | |||
| + | * later : delete, move, branch, merge, revert | ||
| + | |||
| + | * the plugin mainly servers as a gui (graphical user interface) and for generating/calculating metadata | ||
| + | |||
| + | * it sends requests to the server for the commands | ||
| + | |||
| + | |||
| + | |||
| + | == metadata == | ||
| + | |||
| + | - Preview images | ||
| + | |||
| + | - Poly Count | ||
| + | |||
| + | - animation infos (has skeleton, which anims are available : walk,run,jump) | ||
| + | |||
| + | - info about how many textures used and their dimension | ||
| + | |||
| + | - associated files (textures) | ||
| + | |||
| + | - (idea) : automatically generated export-format ? (md3,.mesh... depending on project settings) | ||
Latest revision as of 13:15, 26 November 2008
Contents
about
a blender plugin for uploading files to a server where they are version-managed (using svn internally) instead of saving them to local files
the big idea behind it is improving the production pipeline
plugin details
the blenderplugin should automatically append metadata such as preview image, polycount, animlist in textform, etc... to the upload, so they can be browsed without loading the complete file...
also downloading and browsing existing files should be possible in the blenderplugin
it just uploads data/files via http to the server, the server puts them into an svn there internally
organization
- forum thread : http://forum.freegamedev.net/index.php?t=msg&th=417
- browse code (trac) : http://zwischenwelt.org/trac/fgasset/browser/trunk
- commit-logs : http://zwischenwelt.org/trac/fgasset/timeline
- public readonly svn plugin : svn co svn://zwischenwelt.org/fgasset_plugin/trunk fgasset_plugin
- public readonly svn server : svn co svn://zwischenwelt.org/fgasset/trunk fgasset_server
- test-server (Ghoulsblade 23:33, 12 November 2007 (CET)) http://ghoulsblade.schattenkind.net/asset/asset.php
hosting
- we also thought about offering "hosting" , e.g. a server for the plugin that can be publically used for models under GPL or similar licenses
ideas
- usecase : branching : diagram
- interesting video about "alienbrain" (commercial asset mgmt software by softimage) : http://www.alienbrain.com/videos.php
- "perforce" seems to be the only big competitor to "alienbrain" : http://www.perforce.com/perforce/products.html
- HL2/Source level editing videos http://interlopers.net/index.php?page=video
- blender script to make model-preview image from grumbel : svn co svn://svn.berlios.de/windstille/trunk/scripts/
sketches
- diagram_usecase1 (suggestion-branch + direct integration, email notification)
- diagram_usecase2 (grant access, revert changes)
- diagram_usecase2b (branching with seperate lifespan, merge after a longer time)
- gui sketch (17.11.2007, sindwiller)
Vocabulary
ArtObject
An ArtObject (AO) is one object which might contain several files, like a model and external textures
Project
A project is a collection of several AO. Permissions are managed at a project-level.
Only member of a project got write permission.
Revision
A revision of an AO is a single version of an AO,
every upload is saved as a new revision,
and it is possible to go back to any of them
Server
- php
- storage,versioning,database
client
- blender plugin (and browser/website for viewing)
- browse files, download, upload (+generate and append metadata)
- later : view changelog, download specific version
- later : authentification (username/password)
- later : delete, move, branch, merge, revert
- the plugin mainly servers as a gui (graphical user interface) and for generating/calculating metadata
- it sends requests to the server for the commands
metadata
- Preview images
- Poly Count
- animation infos (has skeleton, which anims are available : walk,run,jump)
- info about how many textures used and their dimension
- associated files (textures)
- (idea) : automatically generated export-format ? (md3,.mesh... depending on project settings)
