[Glamour] default selection in ListPresentation
by Cyrille Delaunay
Hello,
Is there a way to set a default selection to a list presentation? so that
when I open the browser, the morphic list has already a value selected.
I tried that:
|tmpBrowser|
tmpBrowser := GLMTabulator new.
tmpBrowser row: #list.
tmpBrowser transmit to: #list; andShow: [:a |
a list
display: [:input | input];
selection: #a;
yourself
].
tmpBrowser openOn: #( b c d v a d f r).
but the list still open with nothing selected
5 years, 2 months
A quick analyzis of the usage of instance variables in Moose
by Guillaume Larcheveque
Hi Moose users,
as you may know, at Synectique we experiment lots of issues about memory
usage.
That's why i had a look at the number of unused instance variables in one
of our system loaded with a big model from one of our main customer.
Total instance variables: 26.852.653
Used instance variables: 17.393.938
Empty collections: 5.023.508
Recoverable instance variables: 14.482.223
The recoverable instance variables are those with nil or an empty
collection (or MultiValueLink)
As you can see, we can save a lot of memory :-)
Here is my (dirty) code to get that:
countUsedInstanceVariableInForSubInstances: aClass
| usedInstNbr instNbr emptyCollNbr |
usedInstNbr := 0.
instNbr := 0.
emptyCollNbr := 0.
aClass
allSubInstancesDo: [ :anEntity |
instNbr := instNbr + anEntity class allInstVarNames size.
anEntity class allInstVarNames
doWithIndex: [ :e :i |
(anEntity instVarAt: i)
ifNotNil: [ :content |
([
content isEmpty.
emptyCollNbr := emptyCollNbr + 1.
false ]
on: MessageNotUnderstood
do: [ false ])
ifFalse: [ usedInstNbr := usedInstNbr + 1 ] ] ] ].
^ {('Used instance variables' -> usedInstNbr).
('empty collections' -> emptyCollNbr).
('Recoverable instance variables' -> (instNbr - (usedInstNbr -
emptyCollNbr))).
('Total instance variables' -> instNbr)}
--
*Guillaume Larcheveque*
6 years, 2 months
Fame/Famix statically typed
by Nicolas Anquetil
Why is Fame (and Famix) statically typed?
It always seemed strange to me in the Smalltalk context.
Do we really use/need this property?
(Because sometimes, it really sucks)
nicolas
--
Nicolas Anquetil -- MCF (HDR)
Project-Team RMod
6 years, 6 months
[ANN] Animation package
by Thibault Raffaillac
Hello,
I am happy to release the Animation package at last! http://catalog.pharo.org/catalog/project/Animation
This is a general animation system, which can turn any setter message into a smooth transition (provided it has a corresponding getter, and the target value supports + and *Float).
Examples:
morph position: (100@100 during: 2 seconds easing: #backOut).
morph color: (Color red during: 2 seconds).
morph title: ('tutututu' during: 2 seconds).
I am curious to see if/how it could be used with Roassal/Moose. Please send any (good or bad) feedback you may have while testing it!
Cheers,
Thibault
ps: Thanks to anonymous contributor for the second syntax, it was a lot of fun - and evil laughs :)
6 years, 6 months
smacc updates
by Tudor Girba
Hi,
John and I worked a bit together and updated the following parser:
- Delphi
- C# (supports version 6.0)
- JavaScript
As you know, SmaCC is now in the Moose distribution, and it comes with detailed abstract syntax trees. This offers new opportunities for the kinds of analyses we can provide.
Cheers,
Doru
--
www.tudorgirba.com
www.feenk.com
"There are no old things, there are only old ways of looking at them."
6 years, 6 months
Segfault on Moose 6.1 jobs
by Blondeau Vincent
Hello,
I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.
Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/console
https://ci.inria.fr/moose/job/moose-6.1/347/console
It seems that they are not failing for the same reason.
Maybe because the job is not using the latest VM? :
pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com> Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/]
Thanks in advance
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
6 years, 6 months
[ann] petitparser2
by Tudor Girba
Hi,
I am happy to announce the availability of PetitParser2, a wonderful redesign of the original PetitParser developed by Jan Kurš.
https://github.com/kursjan/petitparser2
Highlights:
- it introduces the compiler facility that speeds up parsers by a factor of ~2-5x
- it introduces the possibility of parsing streams without having them in memory
- it comes with a new structure internally that makes it more flexible
- it introduces asPParser (not a typo) to be able to have the new version working in parallel with the classic asParser
The version is already present in the latest Moose 6.1 in parallel with PetitParser. Also, several of the parsers that are shipping with PetitParser were already copied to PetitParser2 as well.
You can find more details here:
http://www.humane-assessment.com/blog/introducing-petitparser2/
Some more documentation will follow.
I think Jan did a wonderful job and the result is quite exciting. Please take a look and let us know what you think.
Cheers,
Doru
--
www.tudorgirba.com
www.feenk.com
"What we can governs what we wish."
6 years, 6 months
another question for incremental loading
by stepharo
Hi doru
If I have a model "model1" mse or database it will have internal names/id
then I have a delta or even another model
and loading it I will need to do a mapping between in memory objects of
the model 1
So you propose to remove all the entities related to entities in Model2
from model1 and to load load model2
but to do so you need to know that id:xxx in Model2 corresponds to Class
A in Model
My impression is that we should really have a uniqueName for any entity.
Stef
6 years, 6 months
Moose 6.1 build failing
by Blondeau Vincent
Hi,
I just wanted to know why the today Moose 6.1 jenkins jobs are failing : https://ci.inria.fr/moose/job/moose-6.1
It seems that someone changed the configuration to load iceberg :
./pharo $JOB_NAME.image eval "Metacello new \
baseline: 'Iceberg'; \
repository: 'github://npasserini/iceberg'; \
load. \
IceRepository defaultBackendType: IceLibgitLocalRepository. \
Smalltalk snapshot: true andQuit: true."
What is the status ?
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
6 years, 6 months
