Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Tudor Girba

Hi, I updated the book with the code that works with the latest Glamour. Also, if you want to see examples, they already exist in the image. For the GLMMorphPresentation, you have an example here: GLMBasicExamples>>morphIcons For further clarifications, you better join the Moose mailing list: moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev Cheers, Doru On Mar 28, 2013, at 3:25 PM, Jesus Nuñez <poissonbreaker(a)gmail.com> wrote: > Hello everyone, > > Does anybody have the full definition of GLMMorphPresentation such > that is usable with Glamour, especifically with the > GLMCompositePresentation?. Actually the only method it defines is > #renderGlamorouslyOn:. > > On the other hand in my installed version of Glamour, GLMTabulator > does not have the #using: method and in the monticello repositories > does not seems to be a version that has it. In Moose Book=>Building > browsers with Glamour=>custom presentations section > (http://www.themoosebook.org/book/internals/glamour/presentations/custom), > it is used for embeed a widget from Morphic. which is exacly what I > need. If somebody knows the version used in the examples please let me > know it. > > Thanks in advance, > Jesus Nuñez > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

12 years, 3 months

committing roassal to sthub

by Tudor Girba

Hi Alex, Moose is now loading Roassal from STHub, but in the meantime I see you are committing to squeaksource. I truly see no reason for it. You can use the following regular Monticello repository to commit to STHub: MCHttpRepository location: 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal/main' user: '' password: '' Please, let's do a little effort to accommodate this transition. Cheers, Doru -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

12 years, 3 months

Fwd: [Pharo-project] Postdoc position in Santiago

by Tudor Girba

FYI Begin forwarded message: > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: [Pharo-project] Postdoc position in Santiago > Date: March 30, 2013 2:15:57 PM GMT+01:00 > To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr>, ESUG Mailing list <esug-list(a)lists.esug.org> > Cc: smalltalk-research(a)googlegroups.com > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Dear Friends and Colleagues, > > The Chilean research agency will soon open its postdoc program. Doctors in Computer Science who want to get a rich experience are encouraged to apply. > > Working at the DCC: > ************************ > The position will have to be carried out at the DCC, University of Chile. No teaching duty is expected from you. > Research topics are broad: Testing, Code execution profiling, Visualization, programming languages, Domain Specific Languages, Programming environments, Modeling, Smalltalk, .... Yes, we are open minded people :-) > The postdoc will be inserted in the Pleiad laboratory, meaning she/he will have to interact with our PhD students, help us to guide smart students and engineers, eat chocolate with us. > > > Mini FAQ: > ************************ > - Do I need to know Spanish to apply? No, knowing Spanish is not mandatory at all. Thanks to the Chilean friendliness, even with a deeply broken Spanish coupled with a heavy accent you will have no problem to integrate. > - How long this position is for? You can stay with us up to 3 years with this position. The DCC is growing, meaning there is perspective to get a permanent position (Assistant Professor). > - How often can I expect to return home? This essentially depends on your productivity. Santiago is only 1 night away from Paris: board-in, eat, sleep, board-out, welcome home. > - What does it mean to live in Santiago? If you like sun, fresh fruits, (very) friendly people, high mountains, glaciers, nature, good wine, sushis, exotic places, ... then you will feel happy. > > > Contact: > ************************ > If you have questions, then you can directly contact the author of this email (http://bergel.eu) or meet us at esug, stic, ecoop, esec/fse > > > Links: > ************************ > http://www.conicyt.cl/fondecyt/2013/03/15/concurso-postdoctorado-2014/ > http://pleiad.cl > http://objectprofile.com > http://bergel.eu > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years, 3 months

Fwd: GSoC 2013 - Graph-ET

by Tudor Girba

And another proposal. Doru > Graph-ET > > Level: Beginner > Possible Mentor: Alecandre Bergel > Possible second mentor: Tudor Girba > > Description: > The necessity of having a chart-drawing tool integrated with Roassal is increasing day by day. > Graph-ET is a tool that allows the user to create and draw charts with small and expressive Smalltalk instructions. The user may enter a large variety of entries, and the program with parse it to fit the users need. For example, the user may use a domain of words and visualize the length of those words with just two lines of code. > The nice thing about Graph-ET is that it’s very simple to see results also the interface allows the user the play with their charts in a variety of ways. > The idea is having a kind of EyeSee but with Roassal as rendering and adding more power of desition to the user. > > Technical Details: > Graph-ET is a software that needs to draw to work, for that it mainly uses Object Profile’s Roassal to make the drawing and the interaction work. > > Benefit to the Student: > The student will learn a lot more of Smalltalk and Pharo environment. Also he will learn some chart visualization and learn to solve all the problems that come with it. Not to mention learning entry parsing. Mainly he will face with serious and critical decisions that will change the fate of his program, but that will mean significant learning process for him. > > Benefit to the Community: > The community will have the pleasure of making fast charts with small and expressive instructions; this will lead to a more simple way of making and drawing charts. > The users of Roassal will enjoy a tool that fit their needs and that work well with the software they already own. > > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

12 years, 3 months

Jenkins build became unstable: moose-latest-dev-4.8 #147

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/147/>

12 years, 3 months

Project Show & Tell - LEKtrek

by Ben Coman

LEKtrek is "a software development platform for electrical power applications". This is my masters project to provide the GUI for modeling electrical power networks, into which researchers can plug calculations. These video presentations are still a work in progress, but just in case you needed some filler for the Show Us Your Project sessions at PharoConf/MooseDay, please feel free to use any portion of the three videos listed below. These can be viewed using VLC. Note that the 020 video was the first I ever produced and suffers a little for quality until I can fix it after writing up my dissertation. Quality gets better in the later videos 010 and 030. http://files.openinworld.com/LEKtrek/ * LEKtrek 010 Introduction 2013-02-25.mp4 - 6min - background context for the project * LEKtrek 020 Explorer User 2013-02-28.mp4 - 8min30 - a tool to explore the IEC 61970 Common Information Model (of electrical power networks) * LEKtrek 030 Modeller User 2013-03-19.mp4 - 9min - a tool for modeling an electrical power network, and executing calculations on that model. The project is based on top of Roassal, Glamour & Magritte 3. It will released open-source, but I am still musing over the finer points of several licenses, which waits on completion of my dissertation. Any and all feedback on contents and aesthetics are welcome. cheers -ben

12 years, 3 months

SmalltalkHub and Versionner

by Alexandre Bergel

Hi! Roassal is now in SmalltalkHub. Although this is a happy news, being in SmalltalkHub completely disrupts the way we work here. Versionner does not run on Pharo 2.0, which means we cannot version Roassal (and the tools we planned to migrate to SHub) the way we have done up to now. An easy fix to this is to use Pharo 1.4 to do the saving (I do not mind to do it until Versionner works on Pharo 2.0). How can Gofer be updated? In Pharo 2.0 Gofer supports some methods that do not exist in Pharo 1.4. Another fix, is that we continue to work on squeaksource, and do some update time to time of SHub. @Christophe: what is needed to have Versionner working on Pharo 2.0. All our tools are properly versioned with a complete history. We cannot jeopardize this. This is not a good surprise. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 3 months

MSE and root folder in 2.0

by Yuriy Tymchuk

Have anyone tried to import model form MSE and set a root dir successfully? I'm having a bad luck with that -- View this message in context: http://moose-dev.97923.n3.nabble.com/MSE-and-root-folder-in-2-0-tp4026631.h… Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 3 months

Glamour in GSoc?

by Usman Bhatti

Doru, Do you think it can be worthwhile idea to propose a project in GSoc to port glamour on the web with Amber? I know that there is already an effort with Seaside but I am just thinking aloud. A+ Usman

12 years, 3 months

strange problem in CompiledMethod>>=

by Tudor Girba

Hi, One of the Moose test runs a visualization that manipulates CompiledMethods, and it runs into an error when trying to find an entry inside a dictionary that has compiled methods as keys. In the end, I managed to isolate the problem that can be reproduced by: 1. Download the moose image: https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… 2. Execute: (MooseIncomingQueryResult>>#selectDependencies:) = (MooseOutgoingInvocationQueryResult>>#selectDependencies:). It seems it is a Pharo problem, or something related to these particular methods. Would anyone be interested in looking into this? Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

12 years, 3 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