Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Stéphane Ducasse

hi guys Apparently nicolas cellier is implementing faster stream so this would probably help moose loading huge models. Nicolas could you let us know when you have a version that we can try. We could come up with real bench on really large files. Cyrille it could be really worth that you have a look. There is a thread on squeak-dev Stef

15 years, 4 months

Re: About Metacello and the Moose process

by Dale Henrichs

----- "Simon Denier" <Simon.Denier(a)inria.fr> wrote: | Unfortunately, there have been too many threads this morning | | *About Metacello* | | Suggestions: | 1) have better names | loadLast -> loadDevVersion or loadVeryLast | loadLatest -> loadStableVersion or loadLastStable | (those 2 are really annoying) | | Also the names in the OB commands could be better and reflect the | current conventions: | Save project -> save configuration | update project -> update configuration | Update Package Methods -> update current version??? Yeah, I have sucked in creating names for things ... and the terminology has evolved. Frankly, at the moment I am caught in between two points, where I'm not sure that the new names are really really better and the desire to avoid changing the tool labels too frequently ... You are raising good points, so I will be interested in what other people think in terms of naming suggestions ... I have holiday time coming as well (today and tomorrow are "vacation" days), so I will spend some time thinking about names... | | Now, when I do a "Current Project Version" on any ConfigurationOf, it | does not work except for the one with Metacello. I dont know, maybe | the configurations do not respect some rules? It's annoying because it | breaks the above tools. I am very interested in these problems ... a pointer to the ConfigurationOf package that is causing the problem would allow me to fix the problem. In the recent releases of Metacello I have fixed the problems that I've seen and am interested in getting the issues shaken out. | | | 2) refactor the documentation | When I started with Metacello 3 months ago it was easy because there | was one recent post describing the things. Now three months later this | is a problem because things have changed a lot but this post is still | the first hit in google "metacello" | http://gemstonesoup.wordpress.com/2009/08/25/metacello-package-management-f… | | Now if you try to follow links there is this post and then this post | http://gemstonesoup.wordpress.com/2009/10/14/a-shiny-new-api-for-metacello/ | http://gemstonesoup.wordpress.com/2009/11/16/metacello-1-0-beta-14-released/ | | Finally it appears that | http://code.google.com/p/metacello/w/list | is now the source for documentation. | | There is the API reference for declaration, description of OBCommands,... | Unfortunately it lacks something about how to play with last/latest | versions with the API. | - if I go to the tutorial, it just refers to the embedded tutorial in | the code and I dont want to load the tutorial each time I need some | documentation | | So please Dale, can you put a few items about things such as | ConfigurationOfXXX project lastVersion, how to manipulate groups, | things discussed with Lukas? Excellent points ... I will take a crack at cleaning up the documentation. | | 3) Good tool for managing configuration, saving projects... | There is a small browser in GLMSmalltalkExamples>>metacelloBrowser, | maybe somebody can start to enhance it to display version and perform | commands. | | | *About the Moose process* | I dont think the Pharo process and the Moose process compare. | | The Pharo process is about integrating fixes from packages which are | | supposed to do one and only one thing, and do it well and is tested. | | The Moose process is about developers making incremental changes to | the code base so that they can work and share it immediately. Which | means it can break other things. | Now I'm pretty sure I dont want a release every time someone commits a | | package in Moose, because I'm pretty sure this someone didn't run all | | the tests before committing. So making a release for each new commit | makes no sense for me. We dont integrate changes, we just merge when | there are some divergent branches. That's why we are always working | with the dev version and the 'default' is one way to do it. | | If we want historical data about Moose, I guess it's still possible to | retrieve all latest packages at a given date. It will not be very | different from what we used at this date. | | Now about the *release* process for Moose: sure I would like that | there will be more releases. Now as Doru said, when we do a release, | we should do it for every sub projects and it's bit difficult with the | current tools. | - One way to do automatically it is to use the test server to at least | create a new version from the latest dev version and blessed it as | 'tested' if 100% tests passed or 'broken' | But I dont want such versions to pollute the manual versions, which | are supposed to be stronger. So something like create automatically | 'testedVersionXXX' with tests or broken as possible blessing. | - Then we can do manual release from time to time (every two weeks, | every months?), which requires more work as we have to do it for the | different subprojects first, and blessed it as beta or stable. Metacello does have the notion of a #development version. #development means that the specification of the version is in flux and may change over time ... It sounds like you'd want to use the #development version for the 100% tested versions, then when you are ready to snap off a real version, you'd mark all of the development versions as beta or stable or whatever (for all the contricuting projects) and then open a new #development version. BTW when I say development version I mean something like: version '1.1' with a #development blessing. Dale

15 years, 4 months

how to we produce new version of moose

by Stéphane Ducasse

Hi I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose? Stef

15 years, 4 months

duplication between default: and version40beta2:?

by Stéphane Ducasse

15 years, 4 months

please make sur that configuration are up to date.

by Stéphane Ducasse

for example ConfigurationOfCAnalyzer was not.

15 years, 4 months

Re: how to load Canalyzer using metacello

by Dale Henrichs

15 years, 4 months

how to load Canalyzer using metacello

by Stéphane Ducasse

Hi I do not understand when I do ConfigurationOfCAnalyzer loadVersion: '1.3' nothing happens ;( still we have version0013: spec <version: '1.3' imports: #('1.2-baseline' )> spec for: #common do: [ spec author: 'simondenier'. spec timestamp: '11/27/2009 16:55'. spec package: 'CAnalyzer' with: 'CAnalyzer-simondenier.159'; package: 'XML-Parser' with: 'XML-Parser-Alexandre_Bergel.17'; package: 'Pastell' with: 'Pastell-Alexandre_Bergel.17'; package: 'Filesystem' with: 'Filesystem-cwp.51'.]. any idea. It seems that metacello is confused Bored stef

15 years, 4 months

if I want to load the latest version of moose

by Stéphane Ducasse

how should I do it? without default of course. because you know I want to be able to load any version from now. Does ((Smalltalk at: #ConfigurationOfMoose) project version: '4.0-beta.2') load. load the latest version of mondrian? In a word how can I avoid to lose hours with loading Moose? Stef

15 years, 4 months

I could not find the OSProcess requirement in MooseConfiguration

by Stéphane Ducasse

Name: ConfigurationOfMoose-cyrille_delaunay.34 Author: cyrille.delaunay Time: 2 December 2009, 2:21:04 pm UUID: de4e4698-ae05-406d-8b9e-544b5037c542 Ancestors: ConfigurationOfMoose-tg.33 adding OSProcess to the external requirements. This package is used by Moose-Wizard to import java source files with inFusion

15 years, 4 months

Fwd: [Pharo-project] Very tiny fonts

by Stéphane Ducasse

any taker because we could have hypercool fonts in pharo. Stef Begin forwarded message: > From: Juan Vuletich <juan(a)jvuletich.org> > Date: December 3, 2009 1:12:33 PM GMT+01:00 > To: Stéphane Ducasse <stephane.ducasse(a)inria.fr> > Cc: Marcus Denker <denker(a)acm.org> > Subject: Re: [Pharo-project] Very tiny fonts > > Hi Stef, > > Stéphane Ducasse wrote: >> juan >> do you have some code that we could study to turn this micro police into font in our smalltalk :) >> > > The code is already in Pharo! Look at #createDejaVu:, the senders and the methods called. > > Besides, (and I already answered this to Marcus), in Cuis evaluate Preferences tinyFonts. Then open a class browser. This font is 5 pixels high, and letters are about 3.5 pixels wide. (Not 7 pixels high and 4.3 wide as I told Marcus, my mistake.) It is the smallest size I found easy to read, especially lowercase characters. I find it useful on PDAs (together with the 6 and 7 sizes also in Cuis). It uses about the same screen space as the "Flea's Knees" and I really find it much easier to read. > > So, don't you prefer DejaVu 5 instead? > > BTW, do play with FreeType. It can produce results equivalent to my DejaVu 5, 6 and 7. > > Cheers, > Juan Vuletich > > Ps: Feel free to forward to the Pharo list > >> Stef >> On Dec 2, 2009, at 6:06 PM, Marcus Denker wrote: >> >> >>> Hi, >>> >>> While discussing Visualisations, we realized we want *really* tiny fonts... >>> Here is a hand-drawn sub-pixel font that is just 5 pixels high... >>> >>> http://typophile.com/node/61920 >>> >>> >>> Now we need to make a font for Pharo... >>> Marcus >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> ------------------------------------------------------------------------ >>> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com Version: 9.0.709 / Virus Database: 270.14.91/2542 - Release Date: 12/03/09 04:32:00 >>> >>> >

15 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev