Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

projects
by Tudor Girba 29 Sep '11

29 Sep '11

Hi, There is not enough communication and coordination around Moose these days. Perhaps it is just the holidays, but I feel a bit lonely working on Moose. I would be interested in knowing who is working on what these days. Or at least, who would like to work on what. Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

7 10

Glamour freezed version in metacello configuration
by Guillermo Polito 28 Sep '11

28 Sep '11

Hi! I was pretty tired of not being able to load Glamour in different images, so I've created a new stable #version for pharo 1.3 and, by now, saved that configuration in the dbxtalk repo squeaksource.com/dbxtalk. Maybe someone want to integrate it in the glamour repo :). Cheers, Guille

2 3

Merlin 1.3
by Alexandre Bergel 28 Sep '11

28 Sep '11

I created the configuration with last Ben improvement. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Comments of MooseElement
by jannik.laval 28 Sep '11

28 Sep '11

Hi, I just remember that when I merged MooseElement and MooseEntity, I did not take into account the comments of the class. If someone want to copy and paste them :) Else I will do it tomorrow. Cheers, --- Jannik Laval

1 1

[Better Comment Initiative]: FAMIXSourceLanguage
by Stéphane Ducasse 28 Sep '11

28 Sep '11

We get ------ FAMIXSourceLanguage This represents the programming language in which an entity is written. It is used for dispatching entity actions for specific languages. For example, formatting a source text will be performed according to the language. We can get --------- I represent the programming language in which an entity is written. I'm used for dispatching entity actions for specific languages. For example, formatting a source text will be performed according to the language. API: format: aSourceString from: anEntity isAttached @@no idea what it is.@@ sourcedEntities References to the entities saying explicitly that are written in this language @@But it does not help me at all@@ Now I do not get why we have sourceEntities added to the source language.

3 6

Are Fame Packages defined?
by Stéphane Ducasse 28 Sep '11

28 Sep '11

Hi I was looking for the package (FM3 one) for FAMIX or Core and Java and I could not find them. Do you know if they got created? I have the impression that this is another sign that pharo need manifestoClass per packages so that we can annotate them and Moose would use them to declare them. Now imagine that we get that (we can just start adding a FAMIXJavaManifest class in the package FAMIX-Java) how do we annotate that this is a FM3Package because <package: > is used to annotate properties And I have the impression that having the distinction between definition and specialisation of annotation is better. We have FMPackage: FMClass: superclass: but we could have FMClassDefinition: superclass FMPackageDefinition: FMPackaged: Stef

2 4

Re: Sytax or what?
by Júlio Martins 27 Sep '11

27 Sep '11

Em 27 de setembro de 2011 13:42, Jùlio <jleandro.martins(a)gmail.com>escreveu: > Ah! I understood what was happening. I really needed select all code to > execute, but I didn't know is needed to open the Trascript browser to > exhibit the result. Other thing was I had not selected completely code. > Sometimes some part of the code don't was selected properly. > > :-) > > Em 26 de setembro de 2011 16:30, Alexandre Bergel-7 [via Smalltalk] < > ml-node+s1294792n3845025h64(a)n4.nabble.com> escreveu: > > Of course, you should have the transcript open (cmd-t) >> >> Alexandre >> >> >> On 26 Sep 2011, at 15:34, Stéphane Ducasse wrote: >> >> > just copy and paste it in workspace >> > select everything and do it. >> > And it should work >> > Moose has nothing special to do with a possible bug. >> > >> > It works also when putting spaces >> > >> > |i| >> > i := 5. >> > [ i >0 ] whileTrue:[ >> > Transcript show: ((i*2) asString) ; cr. >> > i := i - 1. >> > ]. >> > > -- View this message in context: http://forum.world.st/Re-Sytax-or-what-tp3848136p3848136.html Sent from the Moose mailing list archive at Nabble.com.

1 0

Re: Sytax or what?
by Júlio Martins 27 Sep '11

27 Sep '11

Well, so I will go change the form of my code |i| i:=5. [i >0] whileTrue:[ Transcript show: ((i*2) asString) ; cr. i:=i-1. ]. Why this doesn't work too? I only receive a "Nothing more expected" when I try to execute it. Em 24 de setembro de 2011 02:58, Stéphane Ducasse [via Smalltalk] < ml-node+s1294792n3838776h45(a)n4.nabble.com> escreveu: > There is a bug in Beeper and the default sound primitive > > stef > > On Sep 24, 2011, at 2:49 AM, Júlio Martins wrote: > > > I don't know why this simple code don't work in Moose/Smaltalk version > 4.5 > > > > | counter | > > counter := 0. > > [ counter < 100 ] whileTrue: > > [ counter := counter + 1. > > Beeper beep ] > > > > I believe the sytax is correct, but when I try to excute this an error > message is sent. > > Doesn't exist while loop? > > > > I don't undesrtand what's happening. > > > > View this message in context: Sytax or what? > > Sent from the Moose mailing list archive at Nabble.com. > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] <http://user/SendEmail.jtp?type=node&node=3838776&i=0> > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=3838776&i=1> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Sytax-or-what-tp3838424p3838776.html > To start a new topic under Moose, email > ml-node+s1294792n1310756h25(a)n4.nabble.com > To unsubscribe from Moose, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…>. > > -- View this message in context: http://forum.world.st/Re-Sytax-or-what-tp3843592p3843592.html Sent from the Moose mailing list archive at Nabble.com.

5 6

[Better Comment Initiative]: CustomSourceLanguage
by Stéphane Ducasse 27 Sep '11

27 Sep '11

We have ------- FAMIXCustomSourceLanguage has not been documented yet. The class comment should describe the purpose of the class, its collaborations and its variables. Instance Variables: name <ProtoObject | PseudoContext> We can get --------- @@I represent specific source language that is not a language supported by default by moose?@@ Then the comment of name is unclear to me? what is a language that is not explicitly modeled? name <MSEProperty: #name type: #String> <MSEComment: 'The name of a custom language that is not modeled explicitly.'>

2 2

[Better Comment Initiative]: FAMIXNamedEntity
by Stéphane Ducasse 27 Sep '11

27 Sep '11

We have ------- I'm an abstract class, root of the hierarchy modeling source code entities. Any of my subclasses must define the meaning of the belongsTo, an abstract property that provides polymorphic traversal. For example, FAMIXClass defines belongsTo as being the container, while the FAMIXMethod defines belongsTo to point to the parentType. I propose -------- I'm an abstract class, root of the hierarchy modeling source code entities. Any of my subclasses must define the meaning of the belongsTo property, an abstract property that provides polymorphic traversal. For example, FAMIXClass defines belongsTo as being the container, while the FAMIXMethod defines belongsTo to point to the parentType. I support the tagging of entity as stub. Marking an entity as a stub means that the Stubs should only be marked by importers and extractors. Stubbed entities represent the border of the modeled world as extracted. Stub tagging should not be recursive. Use other tags for such a purpose: a class may have an instance variable tagged as a stub because an importer got a memory leak or a bug. Still the class is not a stub, but extra analysis can mark it as incomplete. When applicable, I also point to my containing package accessible via parentPackage and modifiers. I also can return the list of invocations performed on this entity (considered as the receiver) (receivingInvocations). Finally, I provide simple name for the entity I represent. The pattern is that name returns the local name of the entity.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev