- Moose-dev - INF Mailman

by mathieubmddehouck＠mailoo.org

Hi Wanted to have likkle fun, so I tried something with like a laggered tree, I saw that someone asked for it. Not committed yet, but in a near morrow, still have crossing problems even with Bezier curves because all the nodes of the same line do not have the same y. Regards Mathieu

12 years, 2 months

3
2
0 0

Re: Moved Hierarchical Graph

by Tudor Girba

Hi Dennis, I went briefly over your code. I think the algorithm gets in a good state! - MalHgRepository should be removed from this level. It is essentially not used. It only adds global variables and it is not essential for the algorithm. - MooseAlgos is at the lowest level in Moose, and it should have no dependencies to other parts like FAMIX. Please fix the tests. - The MalHgVisitorTask hierarchy and MalHgBottomUpNodeVisitor are not used and should be removed from the package. - MalHgUtilities are not used within the package and should be removed from the package. - FILOStack is only used in a test so it seems to not be particularly useful. In general, we want to keep global state to a bare minimum because we want to enable unforeseen combinations at object-level. Caches can be built at a certain application level, but only if truly necessary. After we do this cleaning, we can move on to add the package to the configuration. Cheers, Doru On Apr 18, 2013, at 7:12 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Dennis, > > Excellent news :). I will try to take a bit of time to look into it. > > Just please let's have these discussions over the mailing list because others might get interested as well. In case you think that you would waste other people's time, HierarchicalGraphs is now part of the 5.0 Roadmap :) > > Cheers, > Doru > > p.s. and please use tudor(a)tudorgirba.com > > On Apr 17, 2013, at 2:24 PM, Dennis Schenk <d.schenk(a)students.unibe.ch> wrote: > >> Hi Doru, >> >> I moved the Quicksilver-Core to Moose-Algos-HierarchicalGraph and the tests to Moose-Tests-Algos-HierarchicalGraph. I also renamed the classes. Could you take a look and see if everything looks good from your point of view? >> >> I did not touch ConfigurationOfMooseAlgos so far as I am not sure to which version the packages should be added. I assume 2.4? But did not see a version for this. >> >> I guess one of the next steps should be to look how we can further merge the code bases, e.g. using classes like MalGraphNode and MalGraphEdge as parents of MalHgNode and MalHgEdge. I also made some utilities which I can guess are already implemented somewhere, like a linear equation generator. If you have some ideas there, or would like to code on this as well, tell me. >> >> Cheers, >> Dennis > > > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

12 years, 2 months

3
6
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/372/> ------------------------------------------ [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/hudson935403054952537838.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest + ./pharo Pharo.image save moose-latest-dev-4.8 /tmp/hudson935403054952537838.sh: 4: /tmp/hudson935403054952537838.sh: ./pharo: not found Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years, 2 months

1
0
0 0

Re: Laggered Tree

by Stephan Eggermont

Mathieu wrote: >Wanted to have likkle fun, so I tried something with like a >laggered tree, I saw that someone asked for it. Yes, that was me. >Not committed yet, but >in a near morrow, still have crossing problems even with Bezier curves >because all the nodes of the same line do not have the same y. Nice! The result has a much better height-to-width than the simple layout. I never said it was trivial :) Getting rid of the crossing problem would probably take one of the chip- or pcb-layout algorithms. Stephan Eggermont

12 years, 2 months

1
0
0 0

Visualization of language

by Yuriy Tymchuk

Hi everyone. Let's say that I'm prototyping some model. Is there some tool to show it's structure like moose meta browser does? I mean, you can use moose meta browser, but what if you want to visualize my model alone? And what if I want to refine the visualization? -- View this message in context: http://moose-dev.97923.n3.nabble.com/Visualization-of-language-tp4027132.ht… Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 2 months

3
3
0 0

robust editors

by Tudor Girba

Hi, As you might know we have a couple of dedicated editors for: - Glamour - Roassal - EyeSee, and - Mondrian Until now, if you had certain errors in the code, the whole editor would be rendered useless. I finally fixed this, and now the editors should be robust: if you have an error in the code (for example, syntax problem), you get a default rendering that exhibits the problem (see attachments). If you happen to find any other problems with the editors, please let me know. Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

12 years, 2 months

3
2
0 0

call for help: webpage redesign

by Tudor Girba

Hi, I would like to start a project to redesign the Moose webpage: http://www.moosetechnology.org/news/call-for-help-webpage-redesign (you can tweet this :)) The initial goals of the redesign are: • redesign the first page to make the message clear: Crafting analyses made easy; • provide a get started set of pages; • provide a structure for documentation; • provide a better space for sub projects. Would anyone be interested in joining the effort? Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

12 years, 2 months

2
1
0 0

ConfigurationOfGlamourSeaside

by Diego Lont

Hi all, I am not fully done testing, but so far looking good, so here I share how far I am: > Version 0.4 is tested in Moose 4.8. I loaded it in Pharo 2.0 and got an error while loading Seaside Tests. Only the tests depend on this project, so this should be ok. Maybe the tests even run, when you proceed on the warning. > Important note: the configuration of Seaside30 comes from Seaside30 repository instead of the MetacelloRepository on squeak source. So you need to load this configuration manually before loading GlamourSeaside. After manually loading configuration of GlamourSeaside and Seaside30 the following should load this project: (ConfigurationOfGlamourSeaside project version: '0.4') load: 'Examples' After that you should of course start the server by: ZnZincServerAdaptor startOn: 8080 Cheers

12 years, 2 months

5
14
0 0

rubric performace

by Tudor Girba

Hi, I did a little experiment to check the performance of Rubric when dealing with large content. And by large, I mean 45 MB or about 15 million lines of text. I opened the file in several other editors: - TextMate: 10s + the text is wrapped and can be browsed smoothly - Sublime Text 2: 10s + the text is wrapped and can be browsed smoothly - Eclipse: 5s + browsing is very slow (so it is basically useless) How did Rubric perform: - When opened with unwrapped lines: 33s + the text can be browsed smoothly - When opened with wrapped lines -> Pharo crashed :( In any case, I think being 3 times slower (even if without wrapping) than TextMate is highly exciting. Great job Alain. If you want to reproduce the experiment, here is the Smalltalk snippet I used: --- Gofer new smalltalkhubUser: 'AlainPlantec' project: 'Rubric'; package: 'Rubric-AlainPlantec.26'; load. [ contents := ((FileSystem disk workingDirectory / 'src' / 'ArgoUML-0-34' / 'output.mse') readStreamDo: #contents). (RubLipsumBasicExample windowWithScrolledText: ( RubLipsumBasicExample new string: contents; newScrolledTextNotWrapped)) openInWorld ] timeToRun --- Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

12 years, 2 months

5
6
0 0

Roassal bug / refactor

by mathieubmddehouck＠mailoo.org

Hi I've refactored bezier curves, now there's just one class ROBezierCurve, and when you call for it you can tell if you want either a radial drawing or an orthoHorizontal or vertical. Just write: + ROBezierCurve radial or + ROBezierCurve orthoVertical... And I've dowloaded the up to date version of Roassal, it seems there are bugs in populatemenu: on: and in ROFixedSizeParent. Regards Mathieu

12 years, 2 months

1
0
0 0

importers page

by Tudor Girba

Hi, I created a page dedicated to importing instructions: http://www.moosetechnology.org/docs/importers A good example of how these instructions should look like can be found here: http://www.moosetechnology.org/docs/importers/importJavaWithinFusion We would need more detailed information about: - Import C# with PMCS http://www.moosetechnology.org/docs/importers/importCSharpWithPMCS - Import C with CAnalyzer http://www.moosetechnology.org/docs/importers/importCWithCAnalyzer Cheers, Doru -- www.tudorgirba.com "Obvious things are difficult to teach."

12 years, 2 months

7
14
0 0

Issue 932 in moose-technology: Moose Meta Browser - Comments Accepted but orange "edited" border not removed

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 932 by alan.mcn...(a)gmail.com: Moose Meta Browser - Comments Accepted but orange "edited" border not removed http://code.google.com/p/moose-technology/issues/detail?id=932 Pharo2.0 Latest update: #20594 Moose 4.8 - downloaded about 3 weeks ago There is a comment panel in the Moose Meta Browser. Comments can be altered in this panel. When the comment text is altered, the panel aquires an orange border. This is standard Pharo behaviour. These changes to the comments can be committed, or accepted in Pharo terminology, by clicking the tick box in the top right corner. That this accept function is working correctly has been checked and all is OK. However, as a feedback to the user, it is expected that after the "accept" the orange border indicating that the text has been changed would go away. This is the standard behaviour of accept in, for example, the System Browser. However, in this case, the orange border remains until the Comment panel is replaced by other information. -- 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, 2 months

1
1
0 0

Issue 933 in moose-technology: Moose Meta Browser - Scope Map by scope of Entities

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 933 by alan.mcn...(a)gmail.com: Moose Meta Browser - Scope Map by scope of Entities http://code.google.com/p/moose-technology/issues/detail?id=933 Type-Enhancement Background ---------- The moose Meta Browser has a nice feature that by clicking on the tag shown against an entity, the list of entities is restricted to those in that tag or as parent entities. For example, if within the expanded Moose.Entity tree, the "Dynamix" tag is selected, and the FAMIX.Entity, Moose.AbstractGroup etc. are hidden, and only Moose.Entity (as a parent) and Dynamix.Entity (tagged Dynamix) is shown. It is also useful that clicking on this tage again reverses this restriction and all Entities are shown. Enhancement ----------- Currently the Map panel shows the Entities and relationships for eveything. It has no way of focussing in on a sub-set of interest. It would be useful if the Map reflected these changes in scope. In the above example, the Map would be re-drawan, but only showing the Moose.Entity and the set of Entities tagged as Dynamix, and perhaps with entities with relationships to those tagged to these Dynamix Entities. Obviously, when the Dynamix tag in the Entity panel is clicked the second time and restores the full list of Entities, the Map would be re-drawn again, this time with all Entities and relationships. -- 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, 2 months

1
1
0 0

Issue 928 in moose-technology: OB browser related code in glamour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 928 by usman.bh...(a)gmail.com: OB browser related code in glamour http://code.google.com/p/moose-technology/issues/detail?id=928 Glamour provides a browser based on the OBBrowser but I think the latter one has been removed from Pharo 2.0. The code can be found in GLMBasicExamples>>startBrowser. -- 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, 2 months

1
1
0 0

Fwd: New ForceBasedLayout

by mathieu

Hi So I've been working on the forcebasedlayout for more than a week now, here are some news. I've translated the D3 code, and have implemented a new quadtree, the mondrian one wasn't that compatible. But, I have a problem, it seems there is no more bug in th code, but it still doesn't do what is expected, so I read and read th D3 code and don't find where are my mistakes. I've started to write test, so maybe I will find something that way. I've made some simplifications but as I do translate javascript to smalltalk, I can't do exactly the same things, and .... Ok... made a new test, before to send this email, and in fact the problem that I have and that does not appear in javascript is due to the length of the links. It seems that in D3, the node position is kinda relative (maybe something with the window border, or something like that), but in Pharo, its more 'static', so it needs to be chosen well for each graph. Still need to be checked, but with a length of 20, in initialize, you got a good result with Collection. ----------------- | view rawView | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "-------------" "-------------" ROEaselMorphic new populateMenuOn: view. view open. 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. view layout: ROForceBasedLayout_N. view applyLayout. ------------- Enjoy Mathieu

12 years, 2 months

4
5
0 0

ForceBasedLayout

by mathieu

Yeah I do apologize, but first I commit a code that I did think wasn't working, and then do a quick commit, without looking at the self and so. Do another commit tomorrow, cleaner. Regards Mathieu

12 years, 2 months

3
2
0 0

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

by admin＠moosetechnology.org

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

12 years, 2 months

1
1
0 0

Fwd: [Pharo-project] Call for ESUG 2013 presentations

by Tudor Girba

---------- Forwarded message ---------- From: Stéphane Ducasse <stephane.ducasse(a)inria.fr> Date: Wed, Apr 24, 2013 at 3:25 PM Subject: [Pharo-project] Call for ESUG 2013 presentations To: A friendly place where any question about pharo is welcome < pharo-users(a)lists.gforge.inria.fr>, "Pharo-project(a)lists.gforge.inria.frDevelopment" < Pharo-project(a)lists.gforge.inria.fr> Please distribute as widely as possible :) 21st International Smalltalk Joint Conference - Call for Contributions Annecy, France from 9 to 13 September 2013 http://www.esug.org/conferences/2013/ This call includes: Developer Forum Smalltalk Technology Award International Workshop http://www.esug.org/Conferences/2013/InternationalWorkshop Student Volunteer http://www.esug.org/Conferences/2013/StudentVolunteers Camp Smalltalk 8 September 2013 ---------------------------------------------------------------------- For the past 21 years, the European Smalltalk User Group (ESUG) has organised the International Smalltalk Conference, a lively forum on cutting edge software technologies that attract people from both academia and industry for a whole week. The attendees are both engineers using Smalltalk in business and students and teachers using Smalltalk both for research and didactic purposes. As every year, this year's edition of the largest European Smalltalk event will include the regular Smalltalk developers conference with renowned invited speakers, a Smalltalk camp that proves fruitful for interactions and discussions. This year will be held the 9th edition of the Innovation Technology Awards where prizes will be awarded to authors of best pieces of Smalltalk-related projects and an international workshop on Smalltalk and dynamic languages (http://www.esug.org/Conferences/2013/InternationalWorkshop) You can support the ESUG conference in many different ways: * Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ * Submit a talk, a software or a paper to one of the events. See below. * Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! * Students can get free registration and hosting if they enrol into the the Student Volunteers program. See below. Developers Forum: International Smalltalk Developers Conference ------------------------------------------------------------------------ We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hand-ons tutorial. The list of topics for the normal talks and tutorials includes, but is not limited to the following: * XP practices, Development tools, Experience reports * Model driven development, Web development, Team management * Meta-Modeling, Security, New libraries & frameworks * Educational material, Embedded systems and robotics * SOA and Web services, Interaction with other programming languages Teaching Pearls --------------- New this year!!! We want two news types of sessions in addition to default talk and show us your projects sessions. - Show your business 10 min session (Get prepared!!) - Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15 min sessions aggregated. Open Forum: starting with Smalltalk ------------------------------------------------------------------------ New this year!! The event will be held at IAE Savoie Mont-Blanc - University of Savoie. This is an opportunity for students and local professionals to discover Smalltalk. A room will be freely accessible and we would like to propose some talks and workshop for Smalltalk beginners. The list of topics includes, but is not limited to the following: - Why Smalltalk ? - Panorama of Smalltalk solutions - Getting started with Smalltalk - Success stories How to submit? -------------- Submissions due on 15st June 2013 Notification of acceptance will be on done on the fly. More information at http://www.esug.org/conferences/2013 Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to Stephane.Ducasse(a)inria.fr AND USE THE following header [ESUG 2013 Developers]. Please follow the template below the email will be automatically processed! Subject: [ESUG 2013 Developers] + your name First Name: Last Name: Email where you can always be reached: Title: Type: Tutorial/Talk/Teaching Pearl/OpenForum Abstract: Bio: Any presentation not respecting this form will be discarded automatically International Workshop on Smalltalk Technologies ------------------------------------------------------------------------ http://www.esug.org/Conferences/2013/InternationalWorkshop Smalltalk is considered as a design pearl and as a beacon in the realm of programming languages and programming environments. We are proud to invite submissions to the International Workshop on Smalltalk Technologies which is held as part of the ESUG 2013 joint event. The goals of the workshop is to create a forum around advances or experience in Smalltalk. We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as - aspect-oriented programming, meta-programming, - frameworks, interaction with other languages, - implementation, - new dialects or languages implemented in Smalltalk, tools, - meta-modeling, design patterns, experience reports Technology Award Competition ------------------------------------------------------------------------ The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/conferences/2013/ Student Volunteer Program ------------------------------------------------------------------------ If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/conferences/2013 http://www.esug.org/Conferences/2013/StudentVolunteers We hope to see you there and have fun together. -- www.tudorgirba.com "Every thing has its own flow"

12 years, 2 months

1
0
0 0

Merging annotations from two models

by Guillaume Larcheveque

Hello, I have to merge user's annotations (added with Metanool) from two different models (created from sources of the same project at two different time) in order to keep these annotations in the newly generated one. Does something exist to do that? Thanks in advance. -- *Guillaume Larcheveque*

12 years, 2 months

4
5
0 0

Issue 929 in moose-technology: Editors break when there is a compile error

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: chisvasi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 929 by tu...(a)tudorgirba.com: Editors break when there is a compile error http://code.google.com/p/moose-technology/issues/detail?id=929 Try this: 1. GLMRoassalEditor open 2. Type "," 3. Run => exception (normal) 4. Type "view nodes: #(1 2 3)" 5. Run => nothing happens -- 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, 2 months

1
1
0 0

Issue 930 in moose-technology: Exporting PNGs from GLM Roassal Easel does not work

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.8 New issue 930 by tu...(a)tudorgirba.com: Exporting PNGs from GLM Roassal Easel does not work http://code.google.com/p/moose-technology/issues/detail?id=930 We should use the ROCommands for these types of actions because they are maintained. -- 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, 2 months

1
1
0 0

MooseModel in unit tests

by Juraj Kubelka

Hi! What is the right usage of MooseModel in unit tests? I would like to write something like this: -- testOpen | mooseModel | mooseModel := MooseModel root allModels anyOne. (OverviewPyramid on: mooseModel) open. -- But it is necessary to ensure there is an imported model. Thanks, Jura

12 years, 2 months

1
0
0 0

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

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/350/> ------------------------------------------ Started by upstream project "gtoolkit" build number 73 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/hudson2829681932894829787.sh + bash + wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip image.j21NP/Pharo-20599.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 + ./pharo moose-latest-dev-4.8.image moosetest --junit-xml-output [31m[33m =============================================================================== Notice: Running tests in 130 Packages =============================================================================== [0m[0m[31mError: index out of range [0mTabSelectorMorph(Object)>>error: TabSelectorMorph(Morph)>>privateAddAllMorphs:atIndex: TabSelectorMorph(Morph)>>addAllMorphs: TabSelectorMorph>>updateTabs TabSelectorMorph>>extent: TabSelectorMorph(Morph)>>bounds: TabSelectorMorph(Morph)>>layoutInBounds: TableLayout>>layoutLeftToRight:in: TableLayout>>layout:in: PanelMorph(Morph)>>doLayoutIn: PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: PanelMorph(Morph)>>fullBounds LazyTabGroupMorph(Morph)>>submorphBounds in Block: [:m | | subBox | m visible... Array(SequenceableCollection)>>do: LazyTabGroupMorph(Morph)>>submorphBounds LazyTabGroupMorph(Morph)>>privateFullBounds LazyTabGroupMorph(Morph)>>doLayoutIn: LazyTabGroupMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: LazyTabGroupMorph(Morph)>>fullBounds LazyTabGroupMorph(Morph)>>layoutProportionallyIn: ProportionalLayout>>layout:in: in Block: [:m | m layoutProportionallyIn: newBounds] Array(SequenceableCollection)>>do: PanelMorph(Morph)>>submorphsDo: ProportionalLayout>>layout:in: PanelMorph(Morph)>>doLayoutIn: PanelMorph(Morph)>>fullBounds in Block: [self doLayoutIn: self layoutBounds] BlockClosure>>on:do: PanelMorph(Morph)>>fullBounds [0mBuild 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, 2 months

1
1
0 0

Blueprint migrated into Roassal

by Juraj Kubelka

Hi! I have migrated Moose Blueprint into Roassal framework. It should behave and looks like before. If you find any issue, please inform me. Cheers, Jura

12 years, 2 months

3
7
0 0

a DNU on SmallInteger>>#add: workaround

by Esteban Lorenzano

Hi, Thanks to Usman, I found a problem in the VM with some kind of assignment structures. Of course it should work, but in the mean time, I commited a patch for 2.0 and 3.0 (in metacello, that was preventing some configurations to be loaded), but the same problem is present too in GLMMorphicTabulatorRenderer>>renderCustomColumn:ofPane:inUI:inBrowser: you might want to workaround it also. You just need to change: self renderCustomRow: each ofPane: aPane inUI: (pane := GLMMorphic containerMorph) inBrowser: aBrowser. for: pane := GLMMorphic containerMorph. self renderCustomRow: each ofPane: aPane inUI: pane inBrowser: aBrowser. yes, I know...this whould work, and *will* work, but in the mean time... cheers, Esteban

12 years, 2 months

3
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev