Hi,
is there a way to have the spotter window fixed-width, or at least cap the maximum width?
If I use dual monitors (as in I extend the Pharo window over two screens), then the spotter will be about 2000 pixels wide.
Ideally it would be nice if I could specify where the spotter appears...e.g. if pharo window width < 2000, then on the center, if > 2000 then the right quarter.
Thanks,
Peter
Hi!
Time to time I get the following message:
This is a big disturbing. I have not investigated how to reproduce the problem. But I can share an image.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I had the same issue when loading a mse some months ago...
I talked with clement and it is a problem with the new gc.
He told me that tweaking it may be enough to resolve the performances issues. But, it is possible that the gc algorithm should be rewritten: for now, only a basic one is implemented.
Cheers,Vincent
------ Message d'origine------De: Tudor GirbaDate: mer., 7 sept. 2016 08:27À: Moose-related development;Cc: Objet :[Moose-dev] major MSE loading slowdown
Hi,I raised this issue before, but somehow it slipped through the cracks. Cyril reminded me yesterday and I checked it again, and indeed, we have a significant problem with loading MSE files.After a quick evaluation, it is likely that the problem comes from Spur or another related change because nothing really changed on the loading side.This is a significant problem, and I would need help with it. If someone has time to investigate, it would be great to join forces.Cheers,Doru--www.tudorgirba.comwww.feenk.com"Problem solving should be focused on describingthe problem in a way that makes the solution obvious."_______________________________________________Moose-dev mailing listMoose-dev@list.inf.unibe.chhttps://www.list.inf.unibe.ch/listinfo/moose-dev
Hi,
I raised this issue before, but somehow it slipped through the cracks. Cyril reminded me yesterday and I checked it again, and indeed, we have a significant problem with loading MSE files.
After a quick evaluation, it is likely that the problem comes from Spur or another related change because nothing really changed on the loading side.
This is a significant problem, and I would need help with it. If someone has time to investigate, it would be great to join forces.
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."
Is there a mechanism for this? Say I want to add some actions to
SequenceableCollection's Items presentation without overriding the existing
method...
Also, is there a canonical documentation for GT? I found the blog posts, and
the presentation documentation in the Moose book, but nothing about GT's
hooks (e.g. my question above).
Thanks!
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Extending-an-Existing-GT-Presentation-tp4913845.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
I think that the #atScope: changed in Moose 6 but it seems that
MooseOutgoingCompositeQueryResult still uses the old #atScope.
To see the problem you can just copy this test in MooseQueryTest:
testProblemAtScope
self shouldnt: [ class2 querySureOutgoingAssociations atTypeScope ]
raise: MessageNotUnderstood
--
Cyril Ferlicot
http://www.synectique.eu
165 Avenue Bretagne
Lille 59000 France
Hi,
We have an engineer position at Lille (France) in the RMOD team to modernize FAME, FAMIX and software analysis tools.
The position is for two years starting in November or December. Conditions to apply are to have a master with 2 to 10 years of experience.
Industrial applications of Moose have shown some limits: (1) problem to scale, (2) modularity and extensibility and (3) user syntax. To overtake these limits, it becomes essential to modernize Moose heart. This project has three major objectives: (i) reduce the memory print to enable a better scaling, (ii) modernize Moose heart to introduce more modularity and extensibility and (iii) simplify the use and extension of Moose.
This project aims to develop a new version of Moose (Moose 2.0) more modular, less memory consumer and easier to use. Advantages of Platypus (PL)(http://dossen.univ-brest.fr/apl/index.php/Platypus <http://dossen.univ-brest.fr/apl/index.php/Platypus>) a research prototype developed in Pharo to analyse software systems as models will be combined to those of the current Moose (M) version and the new features of Pharo (P).
Moose 2.0 = flexible metamodel (M) supporting multiple inheritance and union of types (PL) + user syntaxto simplify model specifications (PL)
+ lot of analysis and visualization tools (M)
+ tool infrastructure (M)
+ model generator (PL)
+ compatibility with industrial and academic standard (PL) + low memory print (P)
+ access to method details (M) on demand (P)
Mission description (in French) and application form are available here (https://www.inria.fr/institut/recrutement-metiers/offres/ingenieurs-r-d-con… <https://www.inria.fr/institut/recrutement-metiers/offres/ingenieurs-r-d-con…>).
French is not mandatory whereas English is ;o)
If you have questions, don’t hesitate to ask.
Sincerely,
Anne Etien
hi,
could someone copy this
Name: ConfigurationOfRoassal2-AlexandreBergel.89
Author: AlexandreBergel
Time: 30 August 2016, 6:44:04.870089 pm
UUID: 224cad5b-6467-406d-9ae3-36e949b45229
Ancestors: ConfigurationOfRoassal2-AlexandreBergel.88
fix in Version 1.37
configuration to the
Repository: http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/
, please?
right now, i cannot load roassal2 in pharo5.
thanks.
--
Bernardo E.C.
Sent from a cheap desktop computer in South America.
Hi,
(how) can one add a new button to GTPlayground, next to the "do it all and go" and "remote publish"?
I want to add integration with Gists (because I find the remote publish only remotely useful),
however it seems that the buttons are hard coded.
Thanks,
Peter