Moose-dev June 2012

moose-dev@list.inf.unibe.ch

20 participants
112 discussions

Issue 798 in moose-technology: Mondrian should store edges in the most specific parent of the from/to nodes

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.7 New issue 798 by tudor.gi...(a)gmail.com: Mondrian should store edges in the most specific parent of the from/to nodes http://code.google.com/p/moose-technology/issues/detail?id=798 The edges should be stored in the most specific parent of the from and to nodes, and not in the parent of the node in which they are defined. This is because the layout takes this information into account. For example, the below layout does not show a tree inside node 1. view := MOViewRenderer new. view node: 1 forIt: [ view shape label. view nodes: (10 to: 11). view treeLayout. ]. view edgesFromAssociations: {10 -> 11}. view open.

11 years, 8 months

Jenkins build is unstable: moose-latest-dev #1004

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1004/>

11 years, 8 months

Issue 701 in moose-technology: Cut and Paste do not update a Glamour Port

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 701 by alexandr...(a)gmail.com: Cut and Paste do not update a Glamour Port http://code.google.com/p/moose-technology/issues/detail?id=701 Email snippets: Regarding copy paste, indeed it seems that pasting a text does not update the port. Please open a ticket. ------- I found another strange behavior, likely to be a bug. Try: -=-=-=-=-=-= | browser | browser := GLMFinder new. browser text act: [:prez :v | prez text inspect ] on: $i entitled: 'Inspect'. browser openOn: 'hello world' -=-=-=-=-=-= If you type something and press cmd-i then you open an inspector on what you have typed. Now, do a cut and paste in the textpane, and press cmd-i. You have an inspector on 'hello world', no matter what you have cut&pasted.

11 years, 8 months

Issue 806 in moose-technology: Roassal does not store edges in the proper place

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 806 by tudor.gi...(a)gmail.com: Roassal does not store edges in the proper place http://code.google.com/p/moose-technology/issues/detail?id=806 If you do: view nodes: #(1 2) forEach: [ :each | view shape label. view nodes: ({each * 10 . (each * 100)}). view treeLayout. ]. view edgesFromAssociations: {10 -> 100. 20 -> 200}. The inner nodes are not laid out in a tree. The reason is that the edges are stored in the parent node that defines them, rather than in the most specific common parent of the from and to nodes. We got the same problem in Mondrian.

11 years, 8 months

update for Roassal

by Usman Bhatti

Hello, I am trying to add an update event in GLMMorphicRoassalRenderer so that when the pane containing the roassal visualization is sent an update event, the corresponding roassal visualization is redrawn (please see: http://code.google.com/p/**moose-technology/issues/**detail?id=808<http://code.google.com/p/moose-technology/issues/detail?id=808> ). Now, I can trigger painting block of the GLMRoassalPresentation but there are some missing entities and the layout not being applied properly.Please find attached to this mail my code for GLMMorphicRoassalRenderer class to trigger the update event. Can you please see what is missing in my code that does not allow proper rendering of roassal visualization? You can use this code to test the updated rendering feature: | browser startNumber | browser := GLMTabulator withStatusbar. startNumber := 1. browser column: #one. browser transmit to: #one; andShow: [ :a | a roassal title: 'Numbers in Roassal'; painting: [:view :number | view shape label. view interaction on: ROMouseClick do: [ :event | ROFocusView new on: event element view: view raw ]. view nodes: (startNumber to: number). view edgesFrom: [:each | each // 5 ]. self halt. view treeLayout. view addMenu: 'Refresh' callBack: [ :stack | startNumber := 10. (browser paneNamed: #one) update ]. ]]. browser openOn: 42 tx, Usman

11 years, 8 months

Issue 808 in moose-technology: refresh a GLMRoassalPresentation

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal New issue 808 by guillaum...(a)gmail.com: refresh a GLMRoassalPresentation http://code.google.com/p/moose-technology/issues/detail?id=808 the update function on GLMRoassalPresentation don't call the painting block. Consequently the visualization is not refreshed.

11 years, 8 months

understanding edges in Roassal

by Usman Bhatti

Hello, I have this script. The problem is that when there are duplicate entities on my canvas, edges are constructed for only one of them. |myView entity otherEntities | myView := ROMondrianViewBuilder new. entity := 1. otherEntities := #(2 2 3 3 4 4). myView shape rectangle withoutBorder. myView node: #entity forIt: [ myView nodes: otherEntities forEach: [:each | myView shape label. myView node: each name]. ]. myView shape rectangle withoutBorder. myView node: #otherEntities forIt: [ myView shape rectangle. myView node: entity ]. myView shape line color: Color red; width: 1. myView edges: otherEntities from: #yourself to: entity. myView verticalLineLayout center. myView open. [image: Inline image 2] The edges to all the entities can be drawn using this script which is a bit inelegant. ((myView raw elementsSuchThat: [:each | each model name includesSubString: 'other']) first elements) do: [:each | myView raw add: (myView buildEdgeFrom: each to: (myView lookup: entity))]. [image: Inline image 3] Question: how to deal with duplicate entities in Roassal? May be this occurs seldom in reality? regards, Usman

11 years, 9 months

a question on ROGrid layout

by Usman Bhatti

A small script to display some elements. |mainNode view title childNodes| view := ROView new. mainNode := (ROElement spriteOn: 'A Test Node') + ROBorder. childNodes := (ROElement spritesOn: (1 to: 10)). childNodes do: [:each | each + ROBorder]. *mainNode addAll: (ROGridLayout on: childNodes).* view add: (ROVerticalLineLayout on: (mainNode)). view open Now, I would like to construct my ROGrid layout such that items per line are 3. However, there is no method in ROGridLayout that allows setting the line item count AND returns a collection of ROElements. So, I may propose the following code to be added on ROGridLayout (class-side): on: aCollection withLineItemsCount: aBlock | myLayout | myLayout := self new gapSize: 5; lineItemsCount: aBlock. myLayout applyOn: aCollection. ^ aCollection let me know if it makes sense. regards, Usman

11 years, 9 months

**IMPORTANT** MUST READ: Pharo Association and Consortium

by Stéphane Ducasse

Dear Pharoers and Smalltalkers This mail is really important so read it carefully. Especially the last part of the mail is important for the immediate future: we need your support and input. Read section ***Support*** at the end of this mail. Context ======= After taking into account feedback from companies and pharo users in different occasions and discussing with the INRIA lawyers and the team in charge of the administrative aspect of the consoritum here is the setup we finally want for the consortium. We will have two separated entities: - one french law 1901 association for individuals and - one consortium for institutions (companies, research groups, laboratories, universities...) managed by INRIA We hope that in the long run the consortium will be fully managed by the association but in the current bootstrap phase INRIA is a good solution. ============== The Pharo Association ============== The goal of the association is to promote Pharo. It will have its own web site. Individual Memberships (managed by the Pharo Association) ---------------------- There are two individual memberships - Individual Pharo Association Member: Yearly fee 40 Euros - Golden Individual Pharo Association Member: Yearly fee 99 Euros You will get a nice goody, reduction access to conferences, reduction for training and access to teaching material, be part of the pharo groups on social networks, be part of the pharoAssociation-individual-members mailing-list, get access and registered to the pharo association web site. Others (managed by the Pharo Association) ---------------------- The association will be able to issues bills so you will be able to buy a Pharo distribution when your organization cannot be a member, a sponsor or doing a donation to the Pharo consortium. End of Pharo Association Description =========================== The Pharo Consortium (managed by INRIA) =========================== The goal of the consortium is to structure and build an umbrella to foster business around Pharo and to promote Pharo. A company, user group, research group, team or institution can be a consortium member, not individual member. There are three levels of fees and corresponding benefits. You decide your degree of support. The annual fees are - Bronze 1000 Euros - Silver 2000 Euros - Gold 4000 Euros Consortium members main advantages are ---------------------------------------- Non individual members of the consortium get the following advantages: - privileged access to the core development team via a specific mailing-list pharo-core-team-for-members(a)lists.gforge.inria.fr - influence priorities of the next development. The member will be able to propose agenda points and items for the executive team. They will be requested one month in advance before the committee meeting. - get access to privileged core engineer time (to address pharo core problems) - Bronze member gets one day of engineering time + is automatically a diamond sponsor. - Silver + two days of engineering time + one job description for job dashboard + is automatically a diamond sponsor.. - Gold four + 4 days of engineering time + multiple job description for job dashboard + is automatically a diamond sponsor. - Training special prices and possibility to become pharo trainer - Pharo consortium member can also ask and pay for extra support days at INRIA engineer prices (around 600 Euros) per day. - Member can offer to their client access to the possibility to pay for extra support days at INRIA engineer prices (around 600 Euros) per day. - The core team can provide contact with experts for certain areas of development. Pharo Consortium Gouvernance: steering committee ---------------------------------------- The consortium will be managed as follows: There will be a steering committee and an Executive Team. * A steering committee is composed of one representative of each member (except individuals). * The chairman of this committee will be Inria * Steering Committee Role : - The Steering Committee follows the execution of the PHARO R&D Team - It validates and gives input about the task list of the Executive Team. - It can propose members of the executive team. - It prepares, organizes conferences, seminars or other animations to promote PHARO and have new members - It revises the annual fee * Decisions taking: after consultation and collect of representative member points of views, Inria takes the final decision. * The steering committee will communicate via a private mailing-list. It may meet physical once a year. * An agenda to reach conclusion will be established by Inria on proposals of the members (the members will be queried a month in advance). Technical Executive Committee (akaR&D task) ---------------------------------------- * The Executive Team is composed of members proposed by the steering board and RMOD Team * Its roles is to * Study, analyze and validate external contributions for PHARO * Report to the steering committee * Present a task list to the steering committee. * Propose, schedule and implement tasks in conformance with the tasks list. * Coordinate the release Pharo and its VMs Pharo consortium Sponsoring --------------------------- Orthogonally to memberships, an entity can be a sponsor of the consortium without being a pharo consortium member. Pharo consortium are de factor platinium sponsor. Sponsors will get their logos name exposed to the consortium web site. There are two kinds of sponsors: - normal 500 Euros - diamond 1000 Euros Job board --------- Non consortium member companies will be able to pay a fee (1000 Euros) to post job offers to the job board. End of Pharo Consortium Description ===================== *** Support and Answer needed*** ===================== To be able to pay an engineer by the consortium, INRIA needs to make projection, build budget, pay attention to visa and other important administrative tasks. To deal with the risk that the consortium may not collect enough to pay a full salary we are considering to ask INRIA to help us financially. To do so we have to give some concrete figures to INRIA and motivate our request. In addition, our team (RMOD) on its own budget will try to compensate by allocating extra resources However, this will be only a one shot. In addition, some of our team members have been approached by google to work on chrome and dart Virtual Machines. So if we really get a future we should build it now. Many of you told us that they want to support the consortium, now we need to know what would be amount of membership, sponsoring you could give. So please read carefully this mail and send us a mail at stephane.ducasse(a)inria.fr with the same subject than this one. We will collect the information and build a case to present to INRIA. Thanks in advance for Pharo and for the future that we are building together. The RMOD team and the Pharo board

11 years, 9 months

Magritte / XML bridge

by Stéphane Ducasse

Hi guys I would like to show in the magritte chapter I'm revisiting a bit more meat. I'm playing with magritte 30 and I would like to know if there is a way to save objects based on their magritte description. Stef

11 years, 9 months

← Newer
1
...
4
5
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2012