- Moose-dev - INF Mailman

by Tudor Girba

Hi, As a first step towards less floating windows, Glamour browsers open now in maximized mode by default. Let me know what you think. Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

12 years, 1 month

1
0
0 0

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

by admin＠moosetechnology.org

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

12 years, 1 month

1
1
0 0

help with updating links and code from moosetechnology.org

by Tudor Girba

Hi, Now that we have moved to SmalltalkHub, all links and loading code from moosetechnology.org needs to be updated. I would need help to get it up to date. It is easy: - pick a project, like http://www.moosetechnology.org/tools/petitparser - update the links and load script - test :) Cheers, Doru -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

12 years, 1 month

2
2
0 0

New shape, bug

by mathieubmddehouck＠mailoo.org

Hi There was a strike in Lille, and I admit it's not that easy to work home, it's far more easy to sleep in the sofa. I have made a new shape anyway : ROArc, its an arc of a sixth of circle, maybe we can script it to choose the another shape (1/4, 1/2 ...). Gofer new smalltalkhubUser: 'MathieuDehouck' project: 'RoassalAlgorithm'; package: 'Roassal-New'; load You can try: -=-=-=-=-=-=-=-=-=-=-=- "Source code: ROExample>>expandableNodesOn:" "Preambule. It includes the initialization. " | view rawView layout | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "-------------" "-------------" layout:= ROVerticalCompactTree new. view shape circle size: 15 . view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. layout userDefinedEdges: view edges. view layout: layout. layout verticalGap: 70; horizontalGap: 30. view applyLayout. view nodes do: [ :f | (layout childrenFor: f) do: [ :t | (t model inheritsFrom: f model) ifTrue: [ t model methodDict keysDo: [ :k | (f model methodDict includesKey: k) ifTrue: [ view edgeFromAssociation: f model ->t model ] ] ] ] ]. view edges do: [ :e | e - ROLine + (ROArc new color: (Color r: 0 g: 1 b: 0.5 ); width: 2) ]. layout userDefinedEdges do: [ :e | e - ROArc + ((ROLine new) color: (Color r: 1 g: 0 b: 0 ); width: 2 ) ]. view shape: (ROBezierCurve orthoVertical new color: (Color r: 0.9 g: 0.8 b: 0 ); width: 2 ) . view edgeFromAssociation: (view nodes at: 1) model ->(view nodes at: 33) model. view edgeFromAssociation: (view nodes at: 5) model ->(view nodes at: 45) model. view edgeFromAssociation: (view nodes at: 8) model ->(view nodes at: 36) model. "-------------" "-------------" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view open. -=-=-=-=-=-=-=-=-=-=-=-=- And you'll see that when we set a new shape in the easel, only the next edge is affected. In this example red edges represent inheritance, green arcs represent overriding on parent's methods, and the 3 other are just for test purpose. And we noticed that only one of the three is drawn in yellow, the two other are in straight grey. And I think, we got the same problem when defining multiple edges at the same time, only the first take the newly set shape. Regards Mathieu

12 years, 1 month

3
10
0 0

New features for forceBasedLayout

by mathieubmddehouck＠mailoo.org

Hello I've added new features for the force based layout. You can change the gravity center, tell where you want to see your fixed nodes and so on. I still have a bug with padding, and resizeStrategy, for example when you click on Example in the view. Gofer it smalltalkhubUser: 'MathieuDehouck' project: 'RoassalAlgorithm'; package: 'RoassalForceBaseLayout'; load. Try this : --------------------------- "Preambule. It includes the initialization. " | rawView view layout | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "enter your script below" "-------------" "-------------" view interaction on: ROMouseEnter do: [ :n | | nodes | nodes := view raw elementsFromModels: n element model allSubclasses. ROHighlightElements on: nodes ]. view interaction on: ROMouseLeave do: [ :n | | nodes | nodes := view raw elementsFromModels: n element model allSubclasses. ROUnhighlightElements on: nodes ]. view shape rectangle size: 10. view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. layout := ROForceBasedLayout_N new. layout fix: (view nodes last) at: 450@450; gravityAt: 437@38 . view layout: layout. view applyLayout. "-------------" "-------------" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view open --------------------------------------- Mathieu

12 years, 1 month

5
10
0 0

bezier vs radial bezier?

by Alexandre Bergel

Hi Mathieu, I have seen we have a ROBezierCurve and RORadialBezierCurve. What are the difference between the both? They produce a slightly different rendering. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 1 month

1
0
0 0

Re: [Pharo-users] SmalltalkWorld chartFrameworks.

by Esteban Lorenzano

and not just the moose people :) take into account that all those project has been migrated to smalltalkhub, under the moose team: http://smalltalkhub.com/#!/~Moose for the moose guys: what about promote the right configurations to MetaRepoForPharo20? (I know there are a lot of cool stuff in that team that can be shared :P) (yeah, I know... I'm annoying with this "configurations" stuff, but someone has to remember it, otherwise it will be wrongly empty :) Esteban On May 17, 2013, at 8:44 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > ****ALL*** the moose people are using PetitParser and it loads in 20. > so where you took the code from? > > The official repositories are on SmalltalkHub/Moose > > Stef > > On May 16, 2013, at 8:27 PM, Alain Busser <alain.busser(a)gmail.com> wrote: > >> Hi, >> >> I have a similar problem with PetitParser (loads well under Pharo 1.4, not as well under Pharo 2.0) >> >> Alain >> >> >> On Thu, May 16, 2013 at 8:56 PM, Camille Teruel <camille.teruel(a)gmail.com> wrote: >> >> On 16 mai 2013, at 17:59, stephane ducasse wrote: >> >>> yes normally the moose people. >>> This is strange because eyesee is in Moose and we load it daily in 2.0. >> >> Maybe the smalltalk hub repo is more up to date? >> >>> >>> Stef >>> >>>> Thanks for your answer Camille! >>>> >>>> I tried it. >>>> It loads well on 1.4 but in 2.0 shows warining about a non satisfied blockclosure class. >>>> >>>> Then when I run the test there is a faliure with the anouncements, which also accured when I tried the examples. >>>> >>>> Is someone maintaining this? >>>> >>>> Thanks again, >>>> Juan >>>> >>>> >>>> On Thu, May 16, 2013 at 11:27 AM, Camille Teruel <camille.teruel(a)gmail.com> wrote: >>>> Hi Juan, >>>> >>>> You can have a look to eyeSee: >>>> >>>> Gofer it >>>> squeaksource: 'EyeSee'; >>>> package: 'ConfigurationOfEyeSee'; >>>> load. >>>> (Smalltalk at: #ConfigurationOfEyeSee) loadDefault >>>> >>>> >>>> On 16 mai 2013, at 16:03, Juan Ignacio Vaccarezza wrote: >>>> >>>>> Hi all, >>>>> >>>>> Does anybody know a chart framework? Im looking fo something like jfreechart (java chart framework). >>>>> I need bar graph, pie chart, and line chart. >>>>> >>>>> Thanks, >>>>> Juan >>>> >>>> >>> >> >> >

12 years, 1 month

1
0
0 0

script: roassal + athens

by Tudor Girba

Hi, Until we get a proper configuration working and accepted, here is a script to make Roassal work with Athens: MooseImageSetupCommandLineHandler new installFonts. "this depends on a Moose image" Gofer new smalltalkhubUser: 'Pharo' project: 'Athens'; package: 'ConfigurationOfAthens'; load. (Smalltalk at: #ConfigurationOfAthens) loadVersion: '2.1'. Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal'; package: 'RoassalAthens'; load. ROPlatform setCurrent: 'athens'. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 1 month

4
4
0 0

Question: How can I play with Hismo visualisations?

by Juraj Kubelka

Hi! How can I play with Hismo visualisations? For example: HismoClassHistoryGroup>>viewHierarchyEvolution Thank you. Jura

12 years, 1 month

2
1
0 0

moose book down?

by Usman Bhatti

http://themoosebook.org/ not working...

12 years, 1 month

2
1
0 0

Re: EyeSee _ Update Data

by Usman Bhatti

On Tue, May 7, 2013 at 3:00 PM, Tran Thi Nhu HOA (etudiante) < ttnhoa(a)ifi.edu.vn> wrote: > On 05/07/2013 08:00 PM, Tran Thi Nhu HOA (etudiante) wrote: > > > Good evening Usman Bhatti, > > Thanks to your help. I have look at GLMExamples class in glamour, most of > the scenarios with examples. But i don't find any solution of my problem. > > The workflow is some panes: (as image below) > + one to select a model ( the first panel), > > + two, three, four to visualize a model (Equations, Parameters, > Compartment), > > + the last one to be able to visualize some graphical (Sample bar chart) > > simulation of a model. > > Until now, i have displayed data on Glamour Pharo (as image below) and > graph by EyeSee > > but i can't update data (change the parameters on panel "Value of > parameters" et "Value of compartments" and change the equations --> update > and store the parameters ---> create an instance of a class (a model) with > the parameters --> display result as a graph(update graph)) > How to store the value of parameters and call an instance of a model and > update on EyeSee? > > you'll have to look how Transmissions and Ports work in Glamour. The link here is an excellent resource, but its down. http://themoosebook.org/ You can also have a look at the book chapter: http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Glamour.pdf > I look at the example but don't exist like this. > > I don't know how to update data, can you show me? Is Glamour Seaside able > to do like this? > > I haven't used glamour-seaside and I dont know about its capabilities. > Thanks in avance, > > Sincerely, > > ttnhoa > > PS: I want to discuss on the topic on Moose -dev, however i don't find how > to post an image of description (the fonction on my computer not run ). I > will post the discussion after. Thanks. > > > > > > > > > > > > > > > > > > > > > On 05/07/2013 05:35 PM, Usman Bhatti wrote: > > hello ttnhoa, > > do you mind if discuss on the topic on Moose-dev list so that others can > benefit too? > > > > On Sun, May 5, 2013 at 7:05 PM, <ttnhoa(a)ifi.edu.vn> wrote: > >> Good evening Usman Bhatti, >> I'am a vietnamese master student working in Ha Noi, Viet Nam >> on epidemiological model visualization. The idea of my work is to be >> able to build some browser in order to navigate inside these kind of >> models and also with the help of Glamour-Seaside, Eye-See, we want to >> provide the same interface on the web. >> Basically each model is define by a set of parameters (name -> float) >> and a set of equations. >> The workflow is quite simple : 3 panes, one to select a model, one to >> visualize a model, the last one to be able to visualize some graphical >> simulation of a model. >> >> I see your discussion at fervrier with le subject: >> 'stuck in Glamour-Merlin flow and update doesn't help' >> And you works with outils EyeSee, Glamour. I try the code that you >> registre in forum and its runs very well. >> You continue to work in this topic (Glamour, EyeSee)? >> > > yes. > > >> You know how to display data (from a model to EyeSee), update the data >> (from a form, parameters ---> model --> update, visualise graphique of >> model on EyeSee) ? >> > > Have a look at GLMExamples class in glamour. you have most of the > scenarios with examples. > > regards, > usman > > >> >> >> Thanks in avance, >> ttnhoa >> >> _____________________________________ >> Sent from http://forum.world.st >> >> > > > -- > Cordialement, > ttnhoa > > > > -- > Cordialement, > ttnhoa > >

12 years, 1 month

1
0
0 0

Distribution map improvements

by Stéphane Ducasse

Juraj did you look at Distribution Map because we should really improve it. For example introducing an API to control label is important in all the visualization based on top of roassal removePrefix: 'Seaside*' removePrefixes: #('SW*' 'Seaside*') removePostFix: '*Test' removePostFixes: #('*Tests' '*Test') contractUpTo: 6 I think that we are quite poor with the customisation of the visualizations we produce. We do them but after the last 10% are not done. So we end up with ugly distributionMap and other just because of that. We did Konkrator just as a step to improve the situation but nobody uses it :). Stef

12 years, 1 month

6
8
0 0

Question about Roassal

by mathieubmddehouck＠mailoo.org

Hi I was working on translating the center of the radial tree at the middle of the window and I faced a problem. I had already faced it when working on the ForceBasedLayout. How does the layout access to his view to get informations ? (Basically it could be very useful to access to the camera to have size informations...) Regards Mathieu

12 years, 1 month

6
18
0 0

Other question about Roassal

by mathieu

Hi I was wondering how to give different senses to different edges, so have a look at edgeDrivenLayout and subclasses. It seems that there are 2 sets of edges ( edges and userDifinedEdges ) and then we face a problem: - How do we do if we want to represent more than two kinds of edges ? Is Roassal able to draw dotted line ? (I haven't found it) Regards Mathieu

12 years, 1 month

5
9
0 0

about computing twice the layout for nothing

by Stéphane Ducasse

Hi mathieu You told me that in certain cases the layout was computed twice. Can you tell us in which case? Stef

12 years, 1 month

1
0
0 0

font installer & free type fonts

by Tudor Girba

Hi, To ease the transition to Athens, we need to get free type fonts in the image. I researched a bit, and found a couple of font families that are nicely free and open-source: DejaVu, Source Code Pro, Source Sans Pro, and LinLibertine. I put together a little tool that imports a TTF file and installs it in a dedicated class. You can find a library of already imported fonts on SmalltalkHub: http://www.smalltalkhub.com/#!/~girba/FreeFonts/ More details about this library can be found at: http://www.tudorgirba.com/blog/free-font-collection-for-pharo For example, you can use the SourceCodeProRegular font as a code font like: Gofer new smalltalkhubUser: 'girba' project: 'FreeFonts'; package: 'SourceCodeProRegular'; load. (Smalltalk at: #SourceCodeProRegular) new install. FreeTypeSystemSettings loadFt2Library: true. StandardFonts codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10). The Moose image already comes with a convenience method to set a complete free type font set: MooseImageSetupCommandLineHandler new installFonts. Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

12 years, 1 month

3
7
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/451/> ------------------------------------------ Started by upstream project "roassal" build number 207 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/hudson3859419998523888206.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/pharo-linux-latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs + ./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+ ./pharo moose-latest-dev-4.8.image mooseimagesetup [31m==== Startup Error: ConnectionTimedOut: Data receive timed out. [0mSocket>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc... Socket>>waitForDataFor:ifClosed:ifTimedOut: Socket>>waitForDataFor: Socket>>receiveDataSignallingTimeout:into:startingAt: SocketStream>>receiveData SocketStream>>next ZnLineReader>>processNext ZnLineReader>>nextLine ZnStatusLine>>readFrom: ZnStatusLine class>>readFrom: ZnResponse>>readHeaderFrom: ZnResponse(ZnMessage)>>readFrom: ZnResponse class(ZnMessage class)>>readFrom: ZnClient>>executeRequestResponse ZnClient>>getConnectionAndExecute in Block: [self executeRequestResponse] BlockClosure>>ensure: 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>>waitForDataFor: in Block: [ConnectionTimedOut signal: 'Data receive timed ou...etc... [0m[31mGot startup errors: [0m[31m ConnectionTimedOut: Data receive timed out. [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years, 1 month

1
1
0 0

petitdelphi moved to smalltalkhub

by Tudor Girba

Hi, I moved PetitDelphi (the work of Stephan and Diego) to SmalltalkHub. You can play with it in a Moose image via this script: Gofer new smalltalkhubUser: 'Moose' project: 'PetitDelphi'; package: 'Famix-Delphi'; package: 'Famix-DelphiImporter'; package: 'PetitDelphi'; load. Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

12 years, 1 month

2
1
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/446/> ------------------------------------------ [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/hudson7883097654829162139.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/pharo-linux-latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs + ./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: Error: Could not resolve: OSProcess [OSProcess] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.smalltalkhub.com/mc/Moose/Moose/main ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/OSProcess: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushAtomicLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: OSProcess [OSProcess] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://www.smalltalkhub.com/mc/Moose/Moose/main ERROR: 'GoferRepositoryError: Could not access http://www.squeaksource.com/OSProcess: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years, 1 month

1
1
0 0

Issue 937 in moose-technology: [Enhancement] Moose logo

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 937 by alan.mcn...(a)gmail.com: [Enhancement] Moose logo http://code.google.com/p/moose-technology/issues/detail?id=937 I've downloaded Moose 4.8 image (rather than the Gopher I used before). This shows the Moose logo on the desktop. Could I suggest the Moose logo should be configurable to be shown / not shown using: Settings Browser / Appearance / Desktop / Show logo... -- 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

12 years, 1 month

1
2
0 0

Issue 936 in moose-technology: Moose Panel - No Disk error

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 936 by alan.mcn...(a)gmail.com: Moose Panel - No Disk error http://code.google.com/p/moose-technology/issues/detail?id=936 After opening the Moose Panel, clicking on the Import Model from MSE file icon (marked MSE) up pops a windows (not Pharo) error message (attached). Although I am running Windows (Win 7), this looks like a Linux or Mac mount point. Does anyone have any idea what is happening? Problem is not fatal, as when I select cancel it goes on perfectly well to display the directories and files and allows me to select a MSE file, but it is a pain. Attachments: DiskError.png 18.0 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

12 years, 1 month

1
3
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/429/> ------------------------------------------ [...truncated 873 lines...] basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: at:put: @ @ basicNew new: at:put: class class basicNew basicNew basicNew: class stringHash:initialHash: basicNew basicNew new: at:put: new: at:put: basicNew basicNew basicNew basicScanCharactersFrom:to:in:rightX:stopConditions:kern: new: at:put: at:put: perform:with: perform: class new: replaceFrom:to:with:startingAt: at:put: stack page bytes 4096 available headroom 3300 minimum unused headroom 3476 (last object overwritten) ./pharo: line 11: 2236 Aborted (core dumped) "$DIR"/"pharo-vm/pharo" -vm-display-null "$@" Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results ERROR: Failed to archive test reports hudson.util.IOException2: remote file operation failed: <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> at hudson.remoting.Channel@4ce1e2b3:moose-slave at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:825) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.util.IOException2: Failed to read <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…> at hudson.tasks.junit.TestResult.parse(TestResult.java:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:140) at hudson.tasks.junit.TestResult.<init>(TestResult.java:116) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: org.dom4j.DocumentException: Error on line 109 of document file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…> : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:227) ... 15 more Caused by: org.xml.sax.SAXParseException; systemId: file://<https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/Glamour-Tests-Morphic…;> lineNumber: 109; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:391) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1404) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:882) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:582) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1370) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1740) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1393) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2769) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525) at org.dom4j.io.SAXReader.read(SAXReader.java:465) ... 18 more

12 years, 1 month

3
4
0 0

is the new force based layout integrated?

by Tudor Girba

Hi, Is the new force based layout already integrated in Roassal? Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

12 years, 2 months

4
6
0 0

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

by admin＠moosetechnology.org

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

12 years, 2 months

1
0
0 0

QuickSilver bug

by Serge Stinckwich

Dear all, I'm doing some experiments with QuickSilver, but I have always some Morph issue when running an expression like this one: QsSystemViewer for: 'Zinc' I expand the node and try to zoom out. After a while, I have a broken morph with red square and yellow cross. The problem apparently is always in ROView>>elementsToRenderDo: aBlock Maybe a Roassal bug. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

12 years, 2 months

6
14
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev