Hmm, I was about to write that the goal of collective behavior is to
model the behavior of the groups (like you demoed at ESUG), and I
wanted to ask how do you store this behavior in Store.
Now I see that I misunderstood completely. From the arguments below,
I believe it is not really worth the trouble.
Doru
>> B1) the reasons for collective behavior
>>
>
> To save memory.
>
> Each moose element has a back pointer to its model. This is 4 byte
> per element, ie 4 MB per 1 Mio elements. Which are realistic maybe
> even low numbers when analysing histories or traces. With collective
> behavior the memory footprint is (4 + F) * M * T, where F is the size
> of an anonymous class, M is the number of models and T is the number
> of element types used per model. Given that F is about 80 byte
> (including object headers and metaclasses etc pp) and T maybe about
> 25, that is 2 KB = 0.002 MB per Model.
>
>
>> B2) the solutions for collective behavior
>>
>> I propose to talk about each of these two points individually,
>> because they are not the same to me.
>
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Some battles are better lost than fought."
Hi,
A new webpage based on Pier is up and running at: http://
moose.unibe.ch .
Feedback is welcome :).
Here is an overview:
-- the front page is supposed to offer all sorts of entry points into
the contents.
-- publications are read from a bib file that contains the entries
from scg.bib that are marked as moose-pub. For each publication a
page is created whose title is the title of the paper, the url is the
key of the entry and the tags of the page are the keywords of the
entry. This is useful for the publications cloud that you can see on
the front page.
I spent quite some time to add missing moose-pub keywords and to add
several other keywords. Now that the keywords are actually used,
perhaps we will have an incentive to add some more for our
publications :)
-- on the front page there is a place for a highlight that is
randomly shown. At the moment there are just 2 movies with Mondrian.
It would be cool to have more such videos with your nice tools :). To
add your highlight, you have to add a page below randomhighlight
similar to:
http://moose.unibe.ch/randomhighlight/videomondrianbasics
-- on the tools page, each tool has a page allocated. You can add
tags in each tool page, and these keywords are taken into account in
the tools cloud. For example, you can specify whether the tool is in-
visualworks or in-java.
-- there is a news feed. At the moment it is broken due to some
Apache settings or something :), but it should be available at:
http://moose.unibe.ch/news?view=PBEntriesRssView
-- the site contains the content from the Smallwiki page. I also took
the liberty to copy some content from personal sites (like codecity
or softwarenaut). I hope that is Ok.
-- you can follow the changes via RSS:
http://moose.unibe.ch/?view=PRChangesRssView
-- the webpage is persisted in the image, and the image is scheduled
to be saved under a different name 1 hour after a change.
You need a user to change the page, please ask me for one. There are
two types of users: admin and editor. The admin can do everything,
while the editor can just edit :). You will probably get an editor user.
Further details about how to edit the site can be found at:
http://moose.unibe.ch/varia/howtoedit
This is just version 1. There are several things that are still in plan:
- make publications updated periodically from external urls.
Currently it is updated manually.
- make the tool page a special component that has explicit links to
publications and developers. The tool should also have an explicit
license field.
- port the Store queries from VW to Squeak to create activity reports.
- add last update information on each page.
- work on the css to make it use a better alignment
Cheers,
Doru
p.s. I would like to thank Lukas Renggli and Adrian Lienhard for
their help and patience :).
--
www.tudorgirba.comwww.tudorgirba.com/blog
"We cannot reach the flow of things unless we let go."
> From: Tudor Girba <girba(a)iam.unibe.ch>
> Date: November 22, 2007 11:51:01 AM GMT+01:00
> To: Toon Verwaest <toon.verwaest(a)gmail.com>
> Cc: Moose-dev Moose Dev <moose-dev(a)iam.unibe.ch>
> Subject: Re: moose.unibe.ch
>
> Indeed, this is the main rule of web design.
>
> But, in this case, the problem is in Pier. I will fix it soon.
>
> Doru
>
>
>
>
> On Nov 22, 2007, at 11:21 AM, Toon Verwaest wrote:
>
>> This is how your moosepage looks on firefox. Since 44.68% of your
>> visitors come from firefox (+3% mozilla). I would strongly advice
>> you to have a look at designing the site so its compatible with
>> non-safari browsers. On internet explorer it already looks fairly
>> ok but not great either. And actually, safari represents only 15%
>> of the users, so only 15% of the users see the page correctly.
>> Isn't this one of the major web design rules?
>>
>> cheers
>> Toon
>
>
>
> --
> www.tudorgirba.com
> www.tudorgirba.com/blog
>
> "Obvious things are difficult to teach."
>
>
--
www.tudorgirba.comwww.tudorgirba.com/blog
"One cannot do more than one can do."
Toon and me created a moose-dev channel on freenode to hang around,
please feel free to join us
irc://chat.freenode.net:8000/moose-dev
Is this a correct IRC link? ... we'll see :)
cheers,
AA
When i try to load moose config 1.23 in a fresh image i get the
following error:
Warning: Package "HapaxNamespace" cannot be loaded.
The following classes cannot be loaded because their environment is not
in the image nor in the package being loaded:
LICENSE (environment path: Root.Smalltalk.Hapax)
When i hit ok anyway, i get a lot of unloadable class definitions
Warning: Package "Clustering" cannot be loaded.
The following classes cannot be loaded because their environment is not
in the image nor in the package being loaded:
CorrelationSquare (environment path: Root.Smalltalk.Hapax)
ClusterTest (environment path: Root.Smalltalk.Hapax)
CorrelationVector (environment path: Root.Smalltalk.Hapax)
DendrogramLeaf (environment path: Root.Smalltalk.Hapax)
ClusteringData (environment path: Root.Smalltalk.Hapax)
TimeWarpingEngine (environment path: Root.Smalltalk.Hapax)
ValueItem (environment path: Root.Smalltalk.Hapax)
CollectionItem (environment path: Root.Smalltalk.Hapax)
DistanceSquare (environment path: Root.Smalltalk.Hapax)
ClusterEngine (environment path: Root.Smalltalk.Hapax)
SeriationEngine (environment path: Root.Smalltalk.Hapax)
Dendrogram (environment path: Root.Smalltalk.Hapax)
DendrogramTest (environment path: Root.Smalltalk.Hapax)
ClusteringVector (environment path: Root.Smalltalk.Hapax)
DendrogramNode (environment path: Root.Smalltalk.Hapax)
VectorItem (environment path: Root.Smalltalk.Hapax)
FeatureCollection (environment path: Root.Smalltalk.Hapax)
etc...
Cheers,
Matt
Hi,
I am trying to load my prerequisites (MooseDevelopment) and first I
get this:
"Warning: Package "Meta-FM3-Model" cannot be loaded.
The following classes cannot be loaded because their environment is
not in the image nor in the package being loaded:
MultivalueLink (environment path: Root.Smalltalk.Meta)"
Followed by a bunch of unloadable definitions in Meta.
After loading everything I could, I try to initialize the meta
descriptions and I get:
"Unhandled exception: Message not understood: #on:opposite:
UndefinedObject(Object)>>doesNotUnderstand:
EMOF.Class>>initialize
..."
Could you guys fix it?
Thanks,
Ricky
