[Tickets] [Orxonox] #294: Resource providing

[Orxonox]

#294: Resource providing
---------------------------+------------------------------------------------
 Reporter:  rgrieder       |        Owner:  rgrieder                    
     Type:  task           |       Status:  new                         
 Priority:  normal         |    Milestone:  Version 0.3 Codename: Castor
Component:  Ogre           |      Version:  0.2.0                       
 Severity:  minor          |   Resolution:                              
 Keywords:  resource, oxw  |  
---------------------------+------------------------------------------------
Changes (by rgrieder):

  * owner:  nobody => rgrieder


Old description:

> == Outline ==
> Loading files from a filesystem can be quite painful if you have to
> specify its exact location with all the folders. [[br]]
> Ogre has dealt with this problem by the means of a Resource Manager. You
> give it all the locations in a configuration file and then it sweeps all
> the contents and wraps the with a Resource. They can be of any kind
> (font, image, mesh, etc.) and that can be extended to serve our purposes.
>
> == The Task ==
> Study the Ogre Resource providing concept on the documentation pages
> (also consider the Doxygen code). Then try to extend the Ogre framework
> to be able to also also the kind of files we want to load. A little
> abstract:
>  * Level files: oxw (XML)
>  * Overlay files: oxo (XML), though this could be replaced by oxw since
> its both XML
>  * TCL scripts: tcl
>  * More to come I'm sure

New description:

 == Outline ==
 Loading files from a filesystem can be quite painful if you have to
 specify its exact location with all the folders. [[br]]
 Ogre has dealt with this problem by the means of a Resource Manager. You
 give it all the locations in a configuration file and then it sweeps all
 the contents and wraps the with a Resource. They can be of any kind (font,
 image, mesh, etc.) and that can be extended to serve our purposes.

 == The Task ==
 Study the Ogre Resource providing concept on the documentation pages (also
 consider the Doxygen code). Then try to extend the Ogre framework to be
 able to also find the kind of files we want to load. A little abstract:
  * Level files: *.oxw (XML)
  * Overlay files: *.oxo (XML), though this could be replaced by oxw since
 its both XML
  * TCL scripts: *.tcl
  * Lua scripts: *.lua
  * More to come I'm sure

--

Comment:

 Actually the Ogre Resource Management concept is quite very stable, so
 there's probably not gonna change much for us with the exception of better
 multithreading support.

-- 
Ticket URL: <http://www.orxonox.net/ticket/294#comment:2>
Orxonox <http://www.orxonox.net>
Orxonox Open Source game