[Boost-commit] svn:boost r41449 - in sandbox/SOC/2007/signals/libs/dataflow: doc doc/blueprint doc/concepts doc/introduction example/blueprint

From: stipe_at_[hidden]
Date: 2007-11-28 20:04:03

Author: srajko
Date: 2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
New Revision: 41449
URL: http://svn.boost.org/trac/boost/changeset/41449

Log:
version 0.8.1
Text files modified: 
   sandbox/SOC/2007/signals/libs/dataflow/doc/blueprint/blueprint.qbk             |     4 ++--                                    
   sandbox/SOC/2007/signals/libs/dataflow/doc/concepts/component.qbk              |     2 +-                                      
   sandbox/SOC/2007/signals/libs/dataflow/doc/future.qbk                          |     4 ++++                                    
   sandbox/SOC/2007/signals/libs/dataflow/doc/introduction/introduction.qbk       |     5 +++--                                   
   sandbox/SOC/2007/signals/libs/dataflow/example/blueprint/blueprint_example.cpp |     3 ++-                                     
   5 files changed, 12 insertions(+), 6 deletions(-)

Modified: sandbox/SOC/2007/signals/libs/dataflow/doc/blueprint/blueprint.qbk
==============================================================================
--- sandbox/SOC/2007/signals/libs/dataflow/doc/blueprint/blueprint.qbk	(original)
+++ sandbox/SOC/2007/signals/libs/dataflow/doc/blueprint/blueprint.qbk	2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
@@ -3,13 +3,13 @@
 The [DataflowBlueprint] layer
 provides generic components that can hold the "big picture"
 of a dataflow network.  This is particularly useful for those dataflow
-frameworks (such as [DataflowSignals] where the dataflow network is stored in
+frameworks such as [DataflowSignals] where the dataflow network is stored in
 the individual components - i.e., there
 is no global picture of the network available.
 
 A blueprint component corresponds to an actual
 component - but whereas the actual component takes care of the work, the
-blueprint component provides a run-time polymorphic interface which can be
+blueprint component provides a run-time polymorphic interface and can be
 embedded in a BGL graph. A dataflow network blueprint uses such a graph
 to hold the blueprint components and the connectivity information.
 In addition, blueprint components provide run-time port reflection.

Modified: sandbox/SOC/2007/signals/libs/dataflow/doc/concepts/component.qbk
==============================================================================
--- sandbox/SOC/2007/signals/libs/dataflow/doc/concepts/component.qbk	(original)
+++ sandbox/SOC/2007/signals/libs/dataflow/doc/concepts/component.qbk	2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
@@ -12,7 +12,7 @@
 [variablelist
     [[C] [A [ComponentConcept] type.]]
     [[CT] [The [ComponentTraitsConcept] type of `C`.]]
-    [[I] [An MPL Integral Constant in the range \[0, n of ports exposed by C).]]
+    [[I] [An MPL Integral Constant in the range \[0, number of ports exposed by C).]]
     [[c] [An object of type C.]]
 ]
 

Modified: sandbox/SOC/2007/signals/libs/dataflow/doc/future.qbk
==============================================================================
--- sandbox/SOC/2007/signals/libs/dataflow/doc/future.qbk	(original)
+++ sandbox/SOC/2007/signals/libs/dataflow/doc/future.qbk	2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
@@ -11,6 +11,10 @@
 * *Serialization* - It should be possible to serialize and deserialize a
   network blueprint. This could be used to store datafow programs, or to send
   them over the network.
+
+* *Separation of network blueprint and network instance* - Right now the
+  `network` class serves both as a blueprint and as an instance of the
+  network.  These two will be decoupled in the future.
   
 * *Component banks* - Banks of components which can be accessed at runtime.
 

Modified: sandbox/SOC/2007/signals/libs/dataflow/doc/introduction/introduction.qbk
==============================================================================
--- sandbox/SOC/2007/signals/libs/dataflow/doc/introduction/introduction.qbk	(original)
+++ sandbox/SOC/2007/signals/libs/dataflow/doc/introduction/introduction.qbk	2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
@@ -377,9 +377,10 @@
 The Dataflow library uses the trunk version of Boost - it might not work
 perfectly with release versions of boost.
 
-Version 0.8.1 (under construction)
+Version 0.8.1
+ \[[@http://www.boost-consulting.com/vault/index.php?direction=&order=&directory=Dataflow& available in the Boost vault]\]
 
-* Started the [DataflowBlueprint] layer (simple runtime reflection and network modeling).
+* Started the [DataflowBlueprint] layer (runtime reflection and network modeling).
 * Expanding the [ComponentConcept] concept (compile-time reflection of ports).
 * VTK example Jamfile now works work with Windows (not just Darwin+X11 VTK).
 * Provided an example using [BoostGIL].

Modified: sandbox/SOC/2007/signals/libs/dataflow/example/blueprint/blueprint_example.cpp
==============================================================================
--- sandbox/SOC/2007/signals/libs/dataflow/example/blueprint/blueprint_example.cpp	(original)
+++ sandbox/SOC/2007/signals/libs/dataflow/example/blueprint/blueprint_example.cpp	2007-11-28 20:04:03 EST (Wed, 28 Nov 2007)
@@ -31,7 +31,8 @@
 public:
     blueprint_example()
     {
-        // Add the components to the network.
+        // Add the components to the network.  So far, ONLY signals::storage
+        // models the Component concept.
         source = network.add_component<signals::storage<void(int)> >(100),
         sink = network.add_component<signals::storage<void(int)> >(0),
         source_float = network.add_component<signals::storage<void(float)> >(100.1f),