Moose-dev August 2013

moose-dev@list.inf.unibe.ch

26 participants
167 discussions

by Tudor Girba

Hi, Here is a little announcement for those that like Glamour. Andrei and I worked on making Glamour more dynamic by pushing the presentation definition at execution, rather than at browser construction time. To achieve dynamic presentation creation, before you needed to use the GLMDymamicPresentation. For example, the MooseFinder was built like: MooseFinder>>compose self finder show: [ :a | a dynamic display: [:each | | dynamic | dynamic := GLMCompositePresentation new. each mooseInterestingEntity mooseFinderPresentationsIn: dynamic. dynamic ] ]. Now, the same code becomes: MooseFinder>>compose self finder show: [ :a :each | each mooseInterestingEntity mooseFinderPresentationsIn: a ]. You can see more details here: http://www.humane-assessment.com/blog/building-dynamic-browsers-with-glamour Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 8 months

Re: Moving OSProcess from Squeaksource to smalltalkHub

by Stéphane Ducasse

Ok just be prepared to have problem with squeaksource and its way to handle files. As a general policy I think that Moose should not rely on external servers. So may be we should clone OSProcess and copy your changes from time to time. Stef On Aug 25, 2013, at 5:55 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Wed, Aug 21, 2013 at 02:12:23PM -0400, David T. Lewis wrote: >> On Wed, Aug 21, 2013 at 05:30:44PM +0200, St?phane Ducasse wrote: >>> Hi dave >>> >>> Moose needs OSProcess and squeaksource is unstable so I will move OSProcess (except if you want to do it) because >>> we should get our build stable and I should losing teim trying to build moose. >>> >>> So let me know. >> >> Hi Stef, >> >> I will move OSProcess to another server by this weekend at the latest. I >> will move CommandShell also, because I think that you are using PipeableOSProcess >> in the ConfigurationOfOSProcess, and that is in the CommandShell package. >> I'll check the configuration to be sure. >> >> Dave > > Hi Stef, > > I am now working with the SCG support team for SqueakSource to move the > SqueakSource service to another server to maintain continued operation. > The Squeak board is supporting this and should be able to provide the > server (although I do not have access to this yet). I hope to be able > to do this without any changes to URLs or Metacello configurations. > > For now the existing SqueakSource will stay on line at least for a little > longer, and I am putting my attention into making the transition happen. > If it does not work out for some reason, I will move the OSProcess > repository at that time. > > Dave >

10 years, 8 months

Roassal Scalability

by mathieubmddehouck＠mailoo.org

Hi An idea to improve roassal scalability was to split the collection elements belonging to ROContainers and builder, into two different collections : edges and nodes. It would permit not to unset shape after we add new edges or nodes, and it would save little time when asking for elementsNotEdges. But after a little trial, it seems that it will ask a huge refactor of roassal to see a real gain in time, with just splitting the collection it gets worse. For example, each time we need both nodes and edges in the same collection we have to concatenate the new collections and it's time consuming. Always working with Object withAllSubclasses as benchmark, we spend 28 second in copyReplaceFrom:to:with ( concatenation ). And it brings us from 69 sec to 136 sec... A beautiful loss of 67 seconds... The idea came when using rawEdgesFrom:to: was long, in fact it used to call elementsNotEdges for each iteration, then in our case a little more than 11000 times, and that was long, but now, as we don't call it so often it is quick enough. That was maybe not that a good idea to split the collection. Tell me what you think. Regards Mathieu

10 years, 8 months

using athens fonts is dead slow in roassal

by Tudor Girba

Hi, Try this: [view := ROMondrianViewBuilder new. view shape label fontSize: [:x | x ]. view nodes: (10 to: 100). view open] timeToRun On my MacBookPro i7 2.6 GHz this takes 23s. The actual reason is that LogicalFont>>widthOfString: looks up the real font when the font is not yet cached. And this ends up looking for files on the disk. I do not know an easy way out, but as it is, we cannot use font scaling essentially. And because of that, visualizations like Annotation Constellation are not practicable anymore: http://www.themoosebook.org/book/externals/visualizations/annotation-conste… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 8 months

Issue 972 in moose-technology: MNU GLMTreeMorphNodeModel>>previousLink:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 972 by benjamin...(a)gmail.com: MNU GLMTreeMorphNodeModel>>previousLink: http://code.google.com/p/moose-technology/issues/detail?id=972 In Moose48 downloaded 2013-08-24... FreeTypeCache allInstances explore > select '1 item' tab > select 'a FreeTypeCache' > select 'State' tab > 'fifo' variable > select 'nnnn items' tab ---> MNU GLMTreeMorphNodeModel>>previousLink: Attachments: GLMTreeMorphNodeModel#previousLink.png 80.6 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 8 months

Graph-ET update

by Daniel Aviv Notario

Hi all! It's been a long time, but with my exams and classes I haven't been able to program a lot. This is an update to the last feature I implemented (+ A LOT of bug fixes) which is the basic composition of diagrams. :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- In Eye-See the diagrams are simply "pasted" one in top of another, which hides the bars if the value is smaller the the value on top, also the labels in the axis are overlaying, so they are difficult to read. This is fine in many ways, but I decided that the composition should scale and sort elements depending on their value.Here's a screenshot of Graph-ET along to its corresponding script:https://www.facebook.com/photo.php?fbid=501852659901336&set=a.341189… :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- I'm still working on this, I hope it'll be working (more or less) by this Monday. :-) The best of lucks!Please email me if you like ;-) - Daniel

10 years, 8 months

Adding Tabs in Glamour

by Mohammad Al Houssami (Alumni)

Hello everyone, First of all thanks to Tudor Girba for letting me know about the mailing list :) I am new to Glamour. I was checking the examples and checking the code for the tree with expansion code. I am trying to add tabs. The only problem is that the tabs don't have a similar function and I don't want the transmit part to work for both. To make things clearer I have want to show a DOM Tree in one column and when the tree is navigated attributes are shown on the second column. I want to have another tab that will just show the list of tokens that have been created during the parsing process. Because they are different, when you click on a token an error will be displayed because it does not understand the message being called. Here is the code I have: browseTree: htmlString |browser domTree | domTree := TreeConstruction new parse: htmlString. browser := GLMTabulator new. browser column: #one; column: #two. browser transmit to: #one; andShow: [:a | a tree title: 'DOM Tree Browser'; display: [ domTree htmlDocument nodes first ]; children: [:element :i | element nodes]; format: [:node| node name]. a tree title: 'Tokens List'; display:[domTree tokens]."Tokens get displayed here " ]. browser transmit to: #two; from: #one; andShow: [ :a | a text display: [:x | 'Attribute List ', x printAttributes ] ]. browser openOn: domTree . How can I achieve that? Or that is not possible?

10 years, 8 months

Issue 970 in moose-technology: Roassal Ellipse does not support no border

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal New issue 970 by tu...(a)tudorgirba.com: Roassal Ellipse does not support no border http://code.google.com/p/moose-technology/issues/detail?id=970 Try this: view shape ellipse borderWidth: 0. view nodes: #(1 2 3) You will see that the border is drawn. The current workaround is to set the borderColor to Color transparent. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 8 months

Issue 967 in moose-technology: Cannot change the selection index dynamically in drop down list presentations

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 967 by chisvasi...(a)gmail.com: Cannot change the selection index dynamically in drop down list presentations http://code.google.com/p/moose-technology/issues/detail?id=967 I am trying to change dynamically selection index of a droplist in Glamour. But changing the selectedIndex upon selection does not change anything in the browser. Here is my code: |browser | browser := GLMTabulator new. browser row: #one size: 30; row: #two. browser transmit to: #one; andShow: [:a | a dropDownList display: [:x | 1 to: 12 ]; selectedIndex: 10 ]. browser transmit from: #one; to: #two; andShow: [:a | a list display: [:x | 1 to: x ]; selectionAct: [:aPres :each | (browser paneNamed: #one) presentations first selectedIndex: 1] entitled: 'select in dropList' ]. browser openOn: 1 Populating the pane port with the selected does change the list items but it does not update the selected value in the dropdown list. selectionAct: [:aPres :each | ((browser paneNamed: #one) port: #selection) value: (1)] entitled: 'select in dropList' ]. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 8 months

Build failed in Jenkins: moose-latest-dev-4.8 #928

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/928/> ------------------------------------------ Started by upstream project "roassal" build number 405 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson5681974984614389313.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: ConnectionTimedOut: Cannot connect to 204.246.122.142:80 [0mSocket>>connectTo:port:waitForConnectionFor: in Block: [ConnectionTimedOut signal: 'Cannot connect to '... Socket>>waitForConnectionFor:ifTimedOut: Socket>>connectTo:port:waitForConnectionFor: SocketStream class>>openConnectionToHost:port:timeout: ZnNetworkingUtils>>socketStreamToUrlDirectly: ZnNetworkingUtils>>socketStreamToUrl: ZnNetworkingUtils class>>socketStreamToUrl: ZnClient>>getConnectionAndExecute ZnClient>>executeWithRedirectsRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc... BlockClosure>>on:do: ZnClient>>executeWithRetriesRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [:exception | retryCount > 0... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: ConnectionTimedOut(Exception)>>signal ConnectionTimedOut(Exception)>>signal: ConnectionTimedOut class(Exception class)>>signal: Socket>>connectTo:port:waitForConnectionFor: in Block: [ConnectionTimedOut signal: 'Cannot connect to '... Socket>>waitForConnectionFor:ifTimedOut: Socket>>connectTo:port:waitForConnectionFor: SocketStream class>>openConnectionToHost:port:timeout: ZnNetworkingUtils>>socketStreamToUrlDirectly: ZnNetworkingUtils>>socketStreamToUrl: ZnNetworkingUtils class>>socketStreamToUrl: ZnClient>>getConnectionAndExecute ZnClient>>executeWithRedirectsRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [self executeWithRedirectsRemaining: self maxNumbe...etc... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Cannot connect to 204.246.122.142:80 [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

10 years, 8 months

← Newer
1
...
7
8
9
10
11
12
13
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev August 2013