First login?
Lost password?
 
 
cellml-tools-developers AT lists.cellml.org 
A list for the developers of CellML tools

Text archives Help


Re: [[cellml-dev] ] Feedback on libCellML design document


Chronological Thread 
  • From: Randall Britten <r.britten AT auckland.ac.nz>
  • To: "cellml-tools-developers AT cellml.org" <cellml-tools-developers AT cellml.org>
  • Subject: Re: [[cellml-dev] ] Feedback on libCellML design document
  • Date: Mon, 9 Feb 2015 01:59:09 +0000
  • Accept-language: en-NZ, en-US
As was decided at last week¹s LibCellML meeting, I¹ve removed the Manager.
We¹ll consider the manager again if it seems necessary when working
directly on a use case with imports. I¹ve also renamed ³Unit² to ³Units².

Regards,
Randall

On 4/02/15 11:11 pm, "David Nickerson"
<david.nickerson AT gmail.com>
wrote:

>> I still think that Manager will be needed as a support class for
>>handling
>> some of the nuances that will crop up when serialising a group of models
>> that are linked via imports. I think that some code for this would shed
>> light on the issues.
>
>I think that is showing the reason for why you consider it necessary,
>but I don't see why libCellML would ever need to concern itself with
>serialising a group of models linked by imports? I'm not sure I even
>understand what that means or how it could be something that libCellML
>needs to worry about...perhaps as you say some code would shed light
>on this but I'm not seeing how. My preference would be to see the code
>base developed without a Manager until it can be shown that things
>simply don't work without such an object.
>
>Cheers,
>Andre.


Archive powered by MHonArc 2.6.18.

Top of page