<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<title>C++ API frePPLe: Todo List</title>
<link href="doxygen.css" rel="stylesheet" type="text/css">
<link href="tabs.css" rel="stylesheet" type="text/css">
<link href="../styles.css" rel="stylesheet" type="text/css">
</head>
<body>
<div id="container">
<div id="menubar">
<div id="logo" align="center">
<br/><img src='../frepple.bmp' alt="frepple" /><br/>
<a href='http://www.frepple.com/'>
<strong>a Free<br/>Production Planning<br/>Library</strong>
</a>
</div>
<div id="menu">
<br/>
<h3><a href='../Main/HomePage.html'>Main</a></h3>
<h3><a href='../UI/Main.html'>User Manual</a></h3>
<h3><a href='../Tutorial/Main.html'>Tutorial</a></h3>
<h3><a href='../Frepple/Main.html'>Reference Manual</a></h3>
<h3><a href='../Main/FAQ.html'>FAQ</a></h3>
<h3><a href='index.html'>C++ API</a></h3>
<br/>
</div>
</div>
<div id="content">
<br/>
<!-- Generated by Doxygen 1.6.1 -->
<div class="navigation" id="top">
<div class="tabs">
<ul>
<li><a href="index.html"><span>Main Page</span></a></li>
<li class="current"><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="namespaces.html"><span>Namespaces</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
<li><a href="dirs.html"><span>Directories</span></a></li>
</ul>
</div>
</div>
<div class="contents">
<h1><a class="anchor" id="todo">Todo List </a></h1><p><a class="anchor" id="_todo000006"></a> </p>
<dl>
<dt>Class <a class="el" href="a00031.html">frepple::CommandMoveOperationPlan</a> </dt>
<dd>Moving in a routing operation can't be undone with the current implementation! The command will need to store all original dates of the suboperationplans... </dd>
</dl>
<p><a class="anchor" id="_todo000009"></a> </p>
<dl>
<dt>Member <a class="el" href="a00121.html#a9e22f3865dd34fd7f2e4efcec6f8221d">frepple::Operation::calculateOperationTime</a> (Date start, Date end, TimePeriod *actualduration=NULL) const </dt>
<dd><p class="startdd">not implemented yet</p>
<ul>
<li>the availability calendar of the locations of all resources loaded </li>
</ul>
<p>not implemented yet by the operation</p>
<p></p>
<p>not implemented yet</p>
<ul>
<li>the availability calendar of the locations of all resources loaded </li>
</ul>
<p>not implemented yet by the operation</p>
<p class="enddd"></p>
</dd>
</dl>
<p><a class="anchor" id="_todo000007"></a> </p>
<dl>
<dt>Class <a class="el" href="a00131.html">frepple::PeggingIterator</a> </dt>
<dd>operationplans without flowplans are skipped by the iterator - not correct! </dd>
</dl>
<p><a class="anchor" id="_todo000005"></a> </p>
<dl>
<dt>Member <a class="el" href="a00173.html#ac1008471ead60a51f3aca2b94464a3db">frepple::SolverMRP::solve</a> (const Resource *, void *=NULL) </dt>
<dd><p class="startdd">resource solver should be using a move command rather than direct move </p>
<p>Optimize the solver method as follows for the common case of infinite buying capability (ie no max quantity + min time):</p>
<ul>
<li>beyond lead time: always reply OK, without rearranging the operation plans</li>
<li>at the end of the solver loop, we revisit the procurement buffers to establish the final purchasing profile </li>
</ul>
<p>The flow quantity is handled at the wrong place. It needs to be handled by the operation, since flows can exist on multiple suboperations with different quantities. The buffer solve can't handle this, because it only calls the solve() for the producing operation... Are there some situations where the operation solver doesn't know enough on the buffer behavior??? </p>
<p class="enddd">moving routing opplan doesn't recheck for feasibility of steps... </p>
</dd>
</dl>
<p><a class="anchor" id="_todo000012"></a> </p>
<dl>
<dt>Class <a class="el" href="a00047.html">frepple::utils::DataElement</a> </dt>
<dd>only takes care of transformation from external format to C++. Not the C++ to external format yet. </dd>
</dl>
<p><a class="anchor" id="_todo000015"></a> </p>
<dl>
<dt>Class <a class="el" href="a00094.html">frepple::utils::HasName< T >::iterator</a> </dt>
<dd>not thread-safe: needs to lock the tree during iteration </dd>
</dl>
<p><a class="anchor" id="_todo000013"></a> </p>
<dl>
<dt>Class <a class="el" href="a00154.html">frepple::utils::PythonObject</a> </dt>
<dd><p class="startdd">endelement function should be shared with setattro function. Unifies the python and xml worlds: shared code base to update objects! (Code for extracting info is still python specific, and writeElement is also xml-specific) xml->prevObject = python->cast value to a different type</p>
<p></p>
<p class="enddd">object creator should be common with the XML reader, which uses the registered factory method. Also supports add/add_change/remove. Tricky: flow/load which use an additional validate() method </p>
</dd>
</dl>
<p><a class="anchor" id="_todo000011"></a> </p>
<dl>
<dt>Class <a class="el" href="a00042.html">frepple::utils::TimeLine< type >::const_iterator</a> </dt>
<dd>Make the timeline iterators fully STL compliant. </dd>
</dl>
</div>
<hr size="1"/><address style="align: right;"><small>Documentation generated for frePPLe by
<a href="http://www.doxygen.org/index.html">
<img src="doxygen.png" alt="doxygen" align="middle" border="0"/></a></small></address>
</div>
</div>
</body>
</html>
