Subversion Repositories public iLand

Rev

Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
1222 3150d 11h werner / public SVN  
1221 3150d 11h werner /branches/ public SVN  
1220 3150d 11h werner /branches/version1.0/ Version 1.0  
1218 3150d 13h werner / clean up repository - make 1.0 trunk again!  
1217 3150d 13h werner / clean up repository - make 1.0 trunk again!  
1212 3156d 17h werner /branches/iland_regen/src/ iLand-caption in pro files  
1157 3368d 20h werner /branches/iland_regen/ merge of changes in the trunk (up to the version used for the 2016 DICE simulation batch).  
1104 3438d 18h werner /branches/iland_regen/ Branch dedicated to playing around with establishment/regeneration.
Goals are:
(i) speed up
(ii) introduction of new features for Yellowstone
 
816 4263d 07h werner /branches/port_qt5_64bit/ merge from iLand trunk (e.g. the new in() function for expressions)

now first (+-) working version of the bridging of Javascript and C++ world.
 
811 4268d 09h werner /branches/port_qt5_64bit/src/ working on the Forest Management Engine.
* new classes that represent Agent, AgentType, FMUnit, FMStand, ...
* +- working evaluation of expressions (activities) in the context of stand/site/... variables.
 
793 4298d 11h werner /branches/port_qt5_64bit/src/ Move from QScriptEngine to QJSEngine (=V8). Most of the stuff was quite smooth, but there are some open issues.
• Global functions (“print”, “include”, “alert”) are commented out (could be solved by moving functions to the “Globals” object and by creating alias JS-functions, i.e. function alert(x) {Globals.alert(x); } )
• Object creation: “new XXX”, XXX=ClimateConverter, CSVFile, … does not work now
possible solution: factory-pattern (i.e. var csv = Globals.newCSV())
 
780 4409d 14h werner /branches/port_qt5_64bit/src/ Steps to build iLand with Qt 5 and with MSVC compiler and 64 bit.
http://iland.boku.ac.at/blogpost44

removed also a couple of warnings that were thrown by the MSVC compiler.
 
779 4422d 13h werner /branches/port_qt5_64bit/  
769 4552d 20h werner /trunk/src/ v 0.84
helper.cpp: added QMutex to handle possible crash when adding timers to the timers list
modules: added a catch() around the execution of modules (this should fix crashes due to unhandled exceptions)
 
763 4614d 14h werner /trunk/ Build for Qt 4.8.3 - new executables and DLLs  
762 4614d 15h werner /trunk/src/plugins/ upgrade Qt 4.8.3  
761 4614d 19h werner /trunk/ upgrade to Qt 4.8.3  
759 4646d 12h werner /trunk/src/ restarting the "ilandc" command line version of iLand.  
758 4648d 12h werner /trunk/src/ tests with the random generator; (see also the blog post about random numbers). Now the generations of the generator are deactivated (i.e. set to 0). The ignition calculation of the fire module is now based on the resource unit (instead of the single fire pixel).  
710 4943d 14h werner /trunk/ new exe version.
includes limitation to 1 fire/year and fixes to ESRI ASCII grid exports.
 
674 5005d 10h werner /trunk/src/ added scripting capabilities (JavaScript) to the "Modules". Now a module can add own objects/properties to the global javascript object. The fire module adds a "FireScript" ("Fire" in JS) object that can be used e.g. to manually "ignite" fires.  
665 5046d 13h werner /trunk/src/ modified the output infrastructure to deal with outputs defined by Modules. Added a fire output.  
646 5146d 15h werner /trunk/src/ reorganized the fire module code and other stuff.
* added new interfaces and linked some of them already (setup(), ...)
* separated the plugin from the implementation (fireplugin.h vs. FireModule)
* worked on finding a way to create "layeredgrids" (how to avoid the templates...)- i have a solution now but still not sure if it really works
 
641 5153d 07h werner /trunk/src/ started development of the plugin / module system.
this includes playing around with qmake and the QPluginLoader.
Now the plan is to build a static library for each module and use the Qt mechanism to load them. The fire module is a kind of a test pilot - lets see how the needed interfaces etc. develop.