FYI, new developments

[jcw]

There has been quite some progress on the Vlerq project in the past  
months, which is finally evolving from being a research project to  
producing tangible software.

Vlerq aims to become Metakit's successor one day.  It will remain  
file-format compatible with Metakit as long as possible (though at  
some point new features in Vlerq will need to extend the current file  
format).

If you want to track the progress on this, see
        http://www.vlerq.org/vqr/347
Development and testing are geared towards Tcl right now, but 70% of  
the core code is in C and intended to become usable for other  
languages as well (as well as from pure C).

The main differences with Metakit are:
  - substantially higher performance for many operations
  - scalable well beyond 2 Gb on 64-bit platforms
  - no more attached vs. unattached view dichotomy
  - a completely different "differential" commit model
  - dataflow-capable, i.e. automatic change propagation
Those last two are central to Vlerq, but still some way off.

-jcw


_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit

[Ralf Schmitt-2]

Jean-Claude Wippler wrote:
> There has been quite some progress on the Vlerq project in the past
> months, which is finally evolving from being a research project to
> producing tangible software.
>
> Vlerq aims to become Metakit's successor one day.  It will remain
> file-format compatible with Metakit as long as possible (though at some
> point new features in Vlerq will need to extend the current file format).
>

I didn't know that vlerq uses the same file format.
Does it already make sense to start a python wrapper? Would it already
be usable as a replacement for metakit or are some major features missing?

- Ralf

_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit

[John Fletcher-2]

JC

What advice would you give to someone who mainly uses Metakit
as a means to use E4Graph?

Is E4Graph going to migrate to Vlerq?

Thanks

John
--
Dr John P. Fletcher   Tel: [phone] (direct line)
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University, Aston Triangle, BIRMINGHAM B4 7ET  U.K.              
CEAC Web site http://www.ceac.aston.ac.uk/
FAX: [phone]


_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit

[jcw]

John Fletcher wrote:

> What advice would you give to someone who mainly uses Metakit
> as a means to use E4Graph?
>
> Is E4Graph going to migrate to Vlerq?

Since E4Graph uses the C++ interface, that requires a C++ wrapper for  
Vlerq.  This is not going to happen soon - see http://www.vlerq.org/ 
vqr/374 for a tentative roadmap.

There should be no reason to stop using Metakit or E4Graph, IMO.  
They work, and I will continue to fix bugs whenever needed.  Metakit  
will be around for a long time to come.

-jcw


_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit

[jyl]

Anyways, when the C++ interface is ready, I will consider doing e4Graph
2.0 with Vlerq. It does not make sense to proceed with the 1.0 e4Grpah for
future development since it is limited in several important ways.

--JYL

> John Fletcher wrote:
>
>> What advice would you give to someone who mainly uses Metakit
>> as a means to use E4Graph?
>>
>> Is E4Graph going to migrate to Vlerq?
>
> Since E4Graph uses the C++ interface, that requires a C++ wrapper for
> Vlerq.  This is not going to happen soon - see http://www.vlerq.org/
> vqr/374 for a tentative roadmap.
>
> There should be no reason to stop using Metakit or E4Graph, IMO.
> They work, and I will continue to fix bugs whenever needed.  Metakit
> will be around for a long time to come.
>
> -jcw
>
>
> _____________________________________________
> Metakit mailing list  -  Metakit@...
> http://www.equi4.com/mailman/listinfo/metakit
>

_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit

[jcw]

Ralf Schmitt wrote:

> I didn't know that vlerq uses the same file format.
> Does it already make sense to start a python wrapper? Would it already
> be usable as a replacement for metakit or are some major features  
> missing?

Missing: save & commit - see http://www.vlerq.org/vqr/374

It's still early days.  For read-only use, i.e. on existing files, a  
Python wrapper could be useful to see how performance & memory usage  
stack up and to start exploring the best way to expose it all to Python.

-jcw



_____________________________________________
Metakit mailing list  -  Metakit@...
http://www.equi4.com/mailman/listinfo/metakit