yade-dev team mailing list archive

[Vaclav Smilauer <eudoxos@xxxxxxxx>]

> Also
> (finally) I have checked that there is wiki available on berlios, and
> I have enabled it. I didn't investigate yet how it works.

If you mean http://yade/berlios.de/pmwiki/, it's me who installed it a
few days ago (I used pmwiki before: it is PHP and needs no db) to try it
out. Or is there some central one on berlios?

> Currently I'm wonderig whether we should:
> 
> (a) totally switch to wiki - the current yade webpage will be
>     copied/pasted into wiki and replaced with a simple URL redirection.
> 
> (b) Or whether the wiki should be complimentary: a link to wiki added on
>     the right-bar menu of the yade webpage. 
> 
> The best thing that wiki can serve us, is documentation. Everyone
> will be able to write docs quickly, and then the docs will
> be copied back into main yade webpage if we chose (a). Or... maybe we
> should perform:
> 
> (c) the variant similar to (a) but only with "Documentation" section?
>     Move all current documentation into wiki, and change the link to
>     "Documentation" on the right-bar menu so that it will point to wiki?

I would be all for (a), or progressively move most stuff to the wiki
(=when modifying something on the current site, put link to the wiki and
cut&paste it there; and leave the rest alone for now).

OTOH, if we move everything to the wiki, perhaps we could consider some
more powerful engine (with latex plugins etc: moinmoin needs python,
which is not on berlios; mediawiki perhaps, but it needs db to be set
up).

Perhaps creating wiki hosted on wikia.com (or something else) would
elimiate administration costs and would also ease things if we move from
berlios.de.

> I think that we will soon make a release, just before I start
> fiddling with the containers (that will allow parallelization)
> because those changes will be deep into yade core - it will be
> useful to make a release just before that.
(And switch to vtk.)

Yes, I thought of that already. I had list of things that are necessary
before the release like this:

* replace dynamic_cast by macro CAST everywhere, which will be #defined
as either static or dynamic, depending of debugging flags (gain 2x
speedup from that in optimized builds) 
  * remove unused elements 
  * write some overall documentation - the basics of yade's functioning 
      * Frederic suggests to make wiki where more detailed stuff could
        be edited by different people 
  * perhaps remove redundant path elements (flatten the tree) - only
    possible with scons 
  * scons 
  * debian package (will have to package wm3 for that as well - take
    only a few used elements and compile that as a lib?); this will make
    it possible to install easily on a few debian variants (stable,
    current ubuntu, LTS ubuntu, for example). 
  * fix compilation with g++ >= 4.1 !!

Of those, everything except documentation (which will be work-in
progress anyway) and removing unused elements where I am not entirely
sure is done.

> 
-- 
Vaclav Smilauer <eudoxos@xxxxxxxx>

_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev