I put the items on the wiki on a single page. Each item to be refined
by specific issues in the bugtracker as development goes on.
On 17 juil. 09, at 16:01, Alexandre Bergel wrote:
Yeah!
That's sound like a good plan
Alexandre
On 16 Jul 2009, at 12:51, Stéphane Ducasse wrote:
Here are the notes of the Moose meeting
Cyrille, Stef, Jannik, Simon
- First goal: Moose should be usable.
- load save filtering what is saved and what should be loaded mse
- get
Distribution Map
PackageBlueprint working on PhaMoose
- We should use systematically the bugtracker available at:
http://code.google.com/p/moose-technology/
- We need a moose documentation. Now we cannot afford writing it.
We will select some tests and tagged them with a pragma and use this
pragma to indicate that the tests is a documentation tests.
Documentation will have comment and show user scenario.
- Tests should be cleaned/reorganized
- Profiling Moose
- use of hashtable instead of Dictionary to see if we can go faster
- faster sets?
- SmallDictionary?
- Run SmallLint on Moose and update methods with pragmas
- Comment in classes
- in Fame classes also
- We should get a release process
- Stable Moose version
May be we should have a Moose and Moose Public repository
- Need a Browser based on Glamour
Check VW
Check new VW browser made by doru
IO
Selection/Filter -> Group
Property displayed
Actions on selection
- Mondrian Exporter as PNG
- Mondrian caches
- Moose is too slow to load
- package info
- MC 1.5 speed up
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev