Ogre资源加载详解

Ogre资源管理1.Ogre资源的载入、卸载和销毁的过程/wiki/index.php?title=%E6%96%87%E6%A1%A3:%E6%95%99%E7%A8%8B:%E4%B8%AD%E7%BA%A7%E6%95%99%E7%A8%8B:%E4%B8%AD%E7%BA%A7%E6%95%99%E7%A8%8B%E4%B8%83/pizi0475/article/details/62644672.跟踪/pizi0475/article/details/62644672.跟踪material的资源载入过程。ResourceGroupManager::initialiseAllResourceGroups()是可以初始化ogre中资源列表中所有的资源。主要通过两个函数来解析和声明一个组的资源。parseResourceGroupScripts(grp);createDeclaredResources(grp);在parseResourceGroupScripts函数中，//IterateoverscriptusersinloadingorderandgetstreamsScriptLoaderOrderMap::iteratoroi;for(oi=mScriptLoaderOrderMap.begin();oi!=mScriptLoaderOrderMap.end();++oi){。。。}根据加载器的顺序将他们一个个取出来做操作。这样保证了加载的优先级因为有些资源的加载是有依赖关系的。这个map里的东西从哪来呢？全解决方案搜索，就会发现在下面这个函数里。voidResourceGroupManager::_registerScriptLoader(ScriptLoader*su){0GRE_L0CK_AUT0_MUTEXmScriptLoaderOrderMap.insert(ScriptLoaderOrderMap::value_type(su->getLoadingOrder(),su));}而当每一种类型的ResourceManager被创建时，都会调用这个函数把自己注册进来，这样就能解析属于他们管理的资源类型的脚本了。可以到MaterialManager的构造函数中看到。//LoadingordermLoadOrder=lOO.Of;//Scriptingissupportedbythismanager#ifOGRE_USE_NEW_COMPILERS==0mScriptPatterns.push_back(“*/r/gram");mScriptPatterns.push_back(“*.material〃)；ResourceGroupManager::getSingleton()._registerScriptLoader(this);#endif//GetallthepatternsandsearchthemconstStringVector&patterns=su->getScriptPatterns();for(StringVector::const_iteratorp=patterns.begin();p!=patterns.end();++p){FilelnfoListPtrfileList二findResourceFileInfo(grp->name,*p);scriptCount+=fileList->size();fileListList->push_back(fileList);}scriptLoaderFileList.push_back(LoaderFileListPair(su,fileListList));得到一个加载器所能加载的资源类型，找出这个资源组中所有的这种资源类型的文件，把他们的文件信息存入列表中，并把这两者配对存储，放入了scriptLoaderFileList。//FirescriptingeventfireResourceGroupScriptingStarted(grp->name,scriptCount);发送—条信息'通知所有的ResourceGroupListener,开始解析组里的脚本了。//Iterateoverscriptsandparse//Notewerespectoriginalorderingfor(ScriptLoaderFileList::iteratorslfli=scriptLoaderFileList.begin();slfli!=scriptLoaderFileList.end();++slfli){ScriptLoader*su=slfli->first;//Iterateovereachlistfor(FileListList::iteratorflli=slfli->second->begin();flli!=slfli->second->end();++flli){//Iterateovereachiteminthelistfor(FilelnfoList::iteratorfii=(*flli)->begin();fii!=(*flli)->end();++fii){boolskipScript二false;fireScriptStarted(fii->filename,skipScript);if(skipScript){LogManager::getSingleton().logMessage("Skippingscript"+fii->filename);}else{LogManager::getSingleton().logMessage("Parsingscript"+fii->filename);DataStreamPtrstream=fii->archive->open(fii-filename);if(!stream.isNullO){if(mLoadingListener)mLoadingListener->resourceStreamOpened(fii->filename,grp->name,0,stream);su->parseScript(stream,grp->name);}}fireScriptEnded(fii->filename,skipScript);}}}这段代码的作用，从加载器列表中取出每一个加载器，对加载器所要解析的脚本进行一一解析。fireScriptStarted(fii->filename,skipScript);通知所有的ResourceGroupListener，开始加载脚本了。这边传入了一个bool型的skipScript的引用，这样应该就能在Listener里边对特定名称的文件进行过滤，让其不被加载。DataStreamPtrstream=fii->archive->open(fii->filename);打开当前文件名的文件，存为数据流。if(mLoadingListener)mLoadingListener->resourceStreamOpened(fii->filename,grp->name,0,stream);如果有ResourceLoadingListener,就可以对资源的打开进行监听了，在这边可又得到打开的资源文件的名字。第三个参数传入的是0，所以在这还得不到资源的名字，因为还没有解析脚本。su->parseScript(stream,grp->name);这里开始解析脚本了跟踪跳转到ScriptCompilerManager::parseScript(DataStreamPtr&stream,constString&groupName)不知道是不是ogre默认是用这个scriptLoader来解析脚本的。具体的解析过程，由mScriptCompiler->compile(stream->getAsString(),stream->getName(),groupName);即：boolScriptCompiler::compile(constString&str,constString&source,constString&group){ScriptLexerlexer;ScriptParserparser;ConcreteNodeListPtrnodes=parser.parse(lexer.tokenize(str,source));returncompile(nodes,group);}上面的代码就将文件解析为一堆的ConcreteNode了，没具体细看，按照我的理解，在不知道文件具体是干嘛用的情况下，应该只是存最顶层的每一个名字，再存上大括号里的内容吧。在OgreScriptCompiler.cpp中可以看到：boolScriptCompiler::compile(constConcreteNodeListPtr&nodes,constString&group){//Translatethenodesfor(AbstractNodeList::iteratori=ast->begin();i!=ast->end();++i){//logAST(0,*i);if((*i)->type==ANT_OBJECT&&reinterpret_cast<ObjectAbstractNode*>((*i).get())->abstract)continue;ScriptTranslator*translator=ScriptCompilerManager::getSingleton().getTranslator(*i);if(translator)translator->translate(this,*i);}}这边将Node—个个取出来然后找出对应的ScriptTranslator来进行解析。ScriptTranslator*ScriptCompilerManager::getTranslator(constAbstractNodePtr&node){ScriptTranslator*translator=0;{0GRE_L0CK_AUT0_MUTEX//Startlookingfromthebackfor(std::vector<ScriptTranslatorManager*>::reverse.iteratori=mManagers.rbegin();i!=mManagers.rend();++i){translator=(*i)->getTranslator(node);if(translator!=0)break;}}returntranslator;}具体的translator就要根据Node的ID来判断了：ScriptTranslator*BuiltinScriptTranslatorManager::getTranslator(constAbstractNodePtr&node){ScriptTranslator*translator=0;if(node->type==ANT_OBJECT){ObjectAbstractNode*obj=reinterpret_cast<ObjectAbstractNode*>(node.get());ObjectAbstractNode*parent二obj—>parent?reinterpret_cast<ObjectAbstractNode*>(obj->parent):0;if(obj—>id==ID_MATERIAL)translator=&mMaterialTranslator;elseif(obj—>id==ID_TECHNIQUE&&parent&&parent->id==ID_MATERIAL)translator=&mTechniqueTranslator;elseif(obj—>id==ID_PASS&&parent&&parent->id==ID_TECHNIQUE)translator=&mPassTranslator;elseif(obj—>id==IDTEXTUREUNIT&&parent&&parent->id==ID_PASS)translator=&mTextureUnitTranslator;elseif(obj->id==ID_TEXTURE_SOURCE&&parent&&parent->id==ID_TEXTURE_UNIT)translator=&mTextureSourceTranslator;elseif(obj->id==ID_FRAGMENT_PROGRAM||obj->id==ID_VERTEX_PROGRAM||obj->id==ID_GEOMETRY_PROGRAM)translator=&mGpuProgramTranslator;elseif(obj->id==ID_PARTICLE_SYSTEM)translator=&mParticleSystemTranslator;elseif(obj->id==ID_EMITTER)translator=&mParticleEmitterTranslator;elseif(obj->id==ID_AFFECTOR)translator=&mParticleAffectorTranslator;elseif(obj->id==ID_C0MP0SIT0R)translator=&mCompositorTranslator;elseif(obj->id==ID_TECHNIQUE&&parent&&parent->id==ID_C0MP0SIT0R)translator=&mCompositionTechniqueTranslator;elseif((obj->id==ID_TARGET||obj->id==ID_TARGET_OUTPUT)&&parent&&parent->id==ID_TECHNIQUE)translator=&mCompositionTargetPassTranslator;elseif(obj->id==ID_PASS&&parent&&(parent->id==ID_TARGET||parent->id==ID_TARGET_OUTPUT))translator=&mCompositionPassTranslator;elseif(obj->id==ID_CLEAR&&parent&&parent->id==ID_PASS)translator=&mCompositionPassClearTranslator;elseif(obj->id==ID_STENCIL&&parent&&parent->id==ID_PASS)translator=&mCompositionPassStencilTranslator;}returntranslator;}卜面以mMaterialTranslator为例，依然是在0greScriptTranslator.cpp：voidMaterialTranslator::translate(ScriptCompiler*compiler,constAbstractNodePtr&node){ObjectAbstractNode*obj=reinterpret_cast<ObjectAbstractNode*>(node.get());if(obj->name.empty())compiler->addError(ScriptCompiler::CE_OBJECTNAMEEXPECTED,obj->file,obj->line);//Createamaterialwiththegivennamestd::vector<Ogre::Any>args;args.push_back(Any(obj->file));args.push_back(Any(obj->name));args.push_back(Any(compiler->getResourceGroup()));Ogre::Anyretval=compiler->_fireCreateObject("Material",args);if(retval.isEmpty()){mMaterial=reinterpret_cast<Ogre::Material*>(MaterialManager::getSingleton().create(obj->name,compiler->getResourceGroup()).get());}else{try{mMaterial=Ogre::any_cast<Ogre::Material*>(retval);}catch(...){compiler->addError(ScriptCompiler::CE_OBJECTALLOCATIONERROR,obj->file,obj->line,"failedtofindorcreatematerial\""+obj->name+〃\〃〃)；return;}}mMaterial->removeAllTechniques();obj->context二Any(mMaterial);mMaterial->_notifyOrigin(obj->file);//以下略Ogre::Anyretval=compiler->_fireCreateObject(〃Material",ar