documentation, close some tickets...

src/lib/iter-adapter.hpp

@@ -128,6 +128,7 @@ namespace lib {
    * - the source container needs to provide hasNext() and iterNext() free functions.
    * - we may need friendship to implement those extension points on the container 
    * - the end-of-iteration can be detected by bool check
+   * @note it is possible to "hide" a smart-ptr within the CON template parameter.
    * 
    * \par Stipulations
    * - POS refers to the current position within the data source of this iterator.

src/proc/assetmanager.hpp

@@ -73,11 +73,11 @@ namespace asset {
       /** provide the unique ID for given Asset::Ident tuple */
       static ID<Asset> getID (const Asset::Ident&);
       
-      /** retrieve the registerd smart-ptr for any asset */
+      /** retrieve the registered smart-ptr for any asset */
       template<class KIND>
       static P<KIND> wrap (const KIND& asset);
       
-      /** find and return corresponging object */
+      /** find and return corresponding object */
       template<class KIND>
       P<KIND>  getAsset (const ID<KIND>& id)  throw(lumiera::error::Invalid);
       

tests/43session.tests

@@ -69,21 +69,21 @@ END
 
 TEST "issuing typed queries" QueryResolver_test <<END
 out: Query-Results: sizeof\( .+IterAdapter.+Cursor.+shared_ptr.+Resolution
-out: ^6$
-out: ^5$
-out: ^4$
-out: ^3$
-out: ^2$
-out: ^1$
-out: ^0$
+out: ^6
+out: ^5
+out: ^4
+out: ^3
+out: ^2
+out: ^1
+out: ^0
 out: Query-Results: sizeof\( .+IterAdapter.+Cursor.+shared_ptr.+Resolution
-out: ^a$
-out: ^ra$
-out: ^era$
-out: ^iera$
-out: ^miera$
-out: ^umiera$
-out: ^Lumiera$
+out: ^a
+out: ^ra
+out: ^era
+out: ^iera
+out: ^miera
+out: ^umiera
+out: ^Lumiera
 END
 
 

tests/components/proc/mobject/session/defsregistryimpltest.cpp

@@ -182,7 +182,7 @@ namespace mobject {
               
               i = reg_->candidates(q3);
               ASSERT ( *i++ == o3);  // found by direct match
-              ASSERT ( *i++ == o1);  // followed by the ordered ennumeration
+              ASSERT ( *i++ == o1);  // followed by the ordered enumeration
               ASSERT ( *i++ == o2);
               ASSERT ( *i++ == o3);
               ASSERT ( *i++ == o3);

tests/lib/iter-adapter-test.cpp

@@ -98,12 +98,9 @@ namespace test{
         const_iterator end ()       const { return const_iterator(); }
         
         
+        
       protected: /* ==== API for the IterAdapter ==== */
         
-        friend class IterAdapter<_Vec::iterator,      TestContainer>;
-        friend class IterAdapter<_Vec::const_iterator,TestContainer>;
-        
-        
         /** Implementation of Iteration-logic: pull next element. */
         template<class ITER>
         friend void

wiki/renderengine.html

@@ -1134,9 +1134,9 @@ Connecting data streams of differing type involves a StreamConversion. Mostly, t
 * retrieve a //strategy// for implementing a connection
 </pre>
 </div>
-<div title="Concepts" modifier="Ichthyostega" modified="200910311750" created="200910311729" tags="overview" changecount="4">
+<div title="Concepts" modifier="Ichthyostega" modified="200910312026" created="200910311729" tags="overview" changecount="5">
 <pre>This index refers to the conceptual, more abstract and formally specified aspects of the Proc-Layer and Lumiera in general.
-More often than not, these emerge from immediate solutions, being percieved as especially expressive, when taken on, yielding guidance by themselves. Some others, [[Placements|Placement]] and [[Advice]] to mention here, immediately substantiate the vision.</pre>
+More often than not, these emerge from immediate solutions, being percieved as especially expressive, when taken on, yielding guidance by themselves. Some others, [[Placements|Placement]] and [[Advice]] to mention here, immediately substantiate the original vision.</pre>
 </div>
 <div title="ConfigQuery" modifier="Ichthyostega" modified="200804110335" created="200801181308" tags="def" changecount="5">
 <pre>Configuration Queries are requests to the system to &quot;create or retrieve an object with //this and that // capabilities&quot;. They are resolved by a rule based system ({{red{planned feature}}}) and the user can extend the used rules for each Session. Syntactically, they are stated in ''prolog'' syntax as a conjunction (=logical and) of ''predicates'', for example {{{stream(mpeg), pipe(myPipe)}}}. Queries are typed to the kind of expected result object: {{{Query&lt;Pipe&gt; (&quot;stream(mpeg)&quot;)}}} requests a pipe excepting/delivering mpeg stream data &amp;mdash; and it depends on the current configuration what &quot;mpeg&quot; means. If there is any stream data producing component in the system, which advertises to deliver {{{stream(mpeg)}}}, and a pipe can be configured or connected with this component, then the [[defaults manager|DefaultsManagement]] will create/deliver a [[Pipe|PipeHandling]] object configured accordingly.
@@ -1262,7 +1262,7 @@ As we don't have a Prolog interpreter on board yet, we utilize a mock store with
 {{{default(Obj)}}} is a predicate expressing that the object {{{Obj}}} can be considered the default setup under the given conditions. Using the //default// can be considered as a shortcut for actually finding a exact and unique solution. The latter would require to specify all sorts of detailed properties up to the point where only one single object can satisfy all conditions. On the other hand, leaving some properties unspecified would yield a set of solutions (and the user code issuing the query had to provide means for selecting one soltution from this set). Just falling back on the //default// means that the user code actually doesn't care for any additional properties (as long as the properties he //does// care for are satisfied). Nothing is said specifically on //how//&amp;nbsp; this default gets configured; actually there can be rules //somewhere,// and, additionally, anything encountered once while asking for a default can be re-used as default under similar circumstances.
 &amp;rarr; [[implementing defaults|DefaultsImplementation]]</pre>
 </div>
-<div title="DesignDecisions" modifier="Ichthyostega" modified="200909291401" created="200801062209" tags="decision design discuss" changecount="24">
+<div title="DesignDecisions" modifier="Ichthyostega" modified="200910312026" created="200801062209" tags="decision design discuss Concepts" changecount="25">
 <pre>Along the way of working out various [[implementation details|ImplementationDetails]], decisions need to be made on how to understand the different facilities and entities and how to tackle some of the problems. This page is mainly a collection of keywords, summaries and links to further the discussion. And the various decisions should allways be read as proposals to solve some problem at hand...
 
 ''Everything is an object'' &amp;mdash; of course, that's a //no-brainer,// todays. Rather, important is what is not &quot;an object&quot;, meaning it can't be arranged arbitrarily