A list for the developers of CellML tools

Text archives Help


RE: [[cellml-dev] ] libCellML handling of non-valid CellML - discussion request


Chronological Thread 
  • From: "Alan Garny" <alan.garny AT inria.fr>
  • To: <cellml-tools-developers AT lists.cellml.org>
  • Subject: RE: [[cellml-dev] ] libCellML handling of non-valid CellML - discussion request
  • Date: Mon, 19 Jan 2015 11:51:23 +0100
  • Organization: INRIA

> > OK, I now understand where you guys are coming from, and it makes
> > sense. I guess I was just being 'lazy' and wanted everything in
> > libCellML, so that I don't have to use various libraries to handle
> > CellML files, although I have already started doing that (for the
> > Pretty CellML view in OpenCOR). (Now, when it comes to the CellML
> > Annotation view in OpenCOR, I can see that switching from the CellML
> > API to libCellML might involve quite a bit of work...)
>
> yes, it will be a lot of work - but it will also be a more useful tool at
> the end of
> the day. This is one reason why I believe we should only be developing one
> annotation tool that can be reused/embedded into many different
> applications.

I guess this is going to be difficult, especially since most annotations only
make sense when performed through some kind of a GUI. So, I am not sure how
this could be 'easily' reused here and there.

> libCellML is, in my view, a library for interacting/working with CellML
> Models
> - not files. Its perhaps a subtle distinction, but quite an important one.

Yes, I can see the distinction and I agree with it.

Alan




Archive powered by MHonArc 2.6.18.

Top of page