Mozart development

[Boriss Mejias]

Hi Torsten,

Thanks a lot for this initiative. I think it is a great opportunity to 
gather momentum once again in the Mozart community. I will answer to 
some of your points bellow.

Torsten Anders wrote:
> Dear all,
> 
> As you know, the core Mozart development cooled down somewhat. On the 
> other hand, we have now the infrastructure for a community-driven 
> development (e.g. developers can register at 
> http://gforge.info.ucl.ac.be/projects/mozart/ and the MEP scheme 
> controls the language development).
> 
> Would it be OK, if I announce at places like freshmeat.net that Mozart 
> is meanwhile developed by its community and that we cordially welcome 
> people to join?

I completely agree. Another activity to promote Mozart will be a 
Lightning Talk we got accepted at FOSDEM. Over there we will present the 
main strengths of the language and mention some of the cool applications 
that has been developed by the community.

http://www.fosdem.org/2007/schedule/events/79

> 
> For this purpose, it would perhaps be helpful to somewhere list all the 
> Mozart-development related projects which are currently in the pipeline. 
> People could be invited to join these projects. Would the project wiki 
> at http://gforge.info.ucl.ac.be/plugins/wiki/index.php?id=17&type=g be a 
> suitable place for this list? A wiki would have the advantage that the 
> list could be updated easily. Here is my first version for such a list.
> 
>   - Gecode for Oz: Geoz (https://gna.org/projects/geoz/)
> 
>   - 'Lispish' Macros for Oz (is Olivier Tonglet or anyone else still 
> working on this?)
> 
>   - The Virtual Manual for Mozart/Oz 
> (http://www.vendian.org/oz/wiki/index.cgi?VirtualManual)
> 
>   - Distributed programming: e.g., p2pkit 
> (http://gforge.info.ucl.ac.be/projects/p2pkit/)
also p2ps hosted at
http://gforge.info.ucl.ac.be/projects/p2ps

and the integration with the Distribution Subsystem. It is a branch at 
the svn repository called mozdss-branch


> 
>   - Unicode support: e.g., http://www.snowlion.nl/mozart/ and 
> http://www.mozart-oz.org/mogul/info/fkonvick/unicode.html (I may get 
> back to people like Maarten van den Dungen and Vladimir Zykov who were 
> very much iinterested in Unicode support for Mozart and offered their 
> help -- without much response at a time when Mozart development was 
> still rather closed)
> 

Filip Konvicka has also done some related job.

that's it for now
cheers
Boriss

> 
> Moreover, I think we should also list stuff we would like to see, 
> although there hasn't been much or no development on them yet. Possibly 
> many entries on this wish list will remain wishes for a very long time, 
> but perhaps also someone new gets motivated because she/he did something 
> similar before already, who knows.. Here are some ideas for such a TODO 
> list:
> 
>   - Oz developers guide documentation at http://www.mozart-oz.org/ 
> (pointer to http://gforge.info.ucl.ac.be/projects/mozart/, pointer to 
> subversion doc, pointer to subversion browser, pointer to bug tracker 
> etc., pointer to hackers at mozart-oz.org, developer FAQ, pointer to Ozdoc, 
> explanation of MEPs. cf. www.python.org/dev)
> 
>   - Eclipse IDE support for Mozart development (there is already 
> webspace reserved at http://gforge.info.ucl.ac.be/projects/mozeclipse/)
> 
>   - SWIG (www.swig.org) support for Oz/Mozart (that would considerably 
> simplify interfaces for GTK, OpenGL, ..., and 'raw' Gecode)
> 
>   - OPI improvements: I would very much like to show the OPI procedure 
> arguments, provide a direct pointer from the source code into the 
> documentation, etc. Is the Crisol project from the AVISPA Research team 
> still progressing (cf. 
> http://lists.gforge.info.ucl.ac.be/pipermail/mozart-users/2005/006644.html)? 
> 
> 
>   - Oz documentation: Some shorter tutorial(s) for a quick start (e.g. 
> 'Oz for Dummies', 'Oz for the <YourLanguage> Programmer'). Finalisation 
> of the unfinished Oz documentation (e.g. the 'Tutorial of Oz', and 
> 'Distributed Programming in Mozart').
> 
> 
> An important but somewhat hard question is this: how can the development 
> of individual Oz contributions be maintained by the community? In 
> particular, how are orphaned Mogul packages maintained? For example, ozh 
> (http://www.mozart-oz.org/mogul/info/franzen/ozh.html) still supports 
> only Mozart 1.2.5. Filip Konvicka provided a patch for 1.3.* 
> (http://lists.gforge.info.ucl.ac.be/pipermail/mozart-users/2006/008016.html), 
> but that patch hasn't been merged into the ozh Mogul package.
> 
> OK, so far. What do you think?
> 
> Thank you.
> 
> Best,
> Torsten
> 
> -- 
> Torsten Anders
> Sonic Arts Research Centre • Queen's University Belfast
> Frankstr. 49 • D-50996 Köln
> Tel: +49-221-3980750
> http://strasheela.sourceforge.net
> http://www.torsten-anders.de
> 
> _________________________________________________________________________________ 
> 
> mozart-users mailing list                               
> mozart-users at mozart-oz.org
> http://www.mozart-oz.org/mailman/listinfo/mozart-users