Hi all, Hi Doru!
There is the kick-off of ComplexShape implementation in Roassal. If you
file-in the attached code into
https://ci.inria.fr/moose/job/moose-latest-dev-4.8/, you will be able to
play with it a bit. There is ROGridBuilderTest test class with two
examples.
Doru, I suppose you are almost only one who manage Mondrian's complex
shapes. Would you please examine the code and give me your opinion? Thank
you a lot. … Of course any one can give me some feedback :-) I would
appreciate it.
For now I focused to do UML Class diagram. I know about blue-prints which
can be done similar way. I have not seen other complex shapes. So there is
an open space for other requirements which can impact interface and design.
Implementation breaks several tests because of change
in ROContainer>>encompassingNestedRectangle. I removed a default extent (5@5)
which is not wanted. I will fix the tests later when the implementation
will be accepted.
Thank you for any response or question,
Jura
[image: Imágenes integradas 1]
Hi!
I wrote a new test:
---
ROHorizontalLineLayoutTest>>testStretch
| previous |
ROHorizontalLineLayout new stretch; on: elements.
previous := nil.
elements do: [ :el |
previous notNil ifTrue: [ self assert: el position x > previous position x
].
previous := el ].
---
It is the same like ROHorizontalLineLayoutTest>>testLayout. I added
#stretch on the first command.
Should it work? It breaks in the message
ROHorizontalLineLayout>>doStretchHorizontal:,
because it expect aGraph and ask for "aGraph bounds" and others. It obtains
a collection of elements. Right now I do not understand what aGraph it
should obtain.
Thanks for any advise,
Jura
Hi,
I did some modifications to Moose-SQL and Famix-SQL to support also create
index statements. I was developing on a 4.7 image than I wanted to merge
the code on smalltalkhub but I could find the project. Moose-SQL and
Famix-SQL have been moved to smalltalkhub or they are still in
squeaksource?
Thanks,
Fabrizio
FYI
Doru
Begin forwarded message:
> From: Janko Mivšek <janko.mivsek(a)gmail.com>
> Subject: [smaltalk-gsoc-students] Call for students
> Date: April 11, 2013 9:01:58 PM GMT+02:00
> To: smalltalk-gsoc-students(a)googlegroups.com
> Reply-To: smalltalk-gsoc-students(a)googlegroups.com
>
> Dear Students,
>
> Now it is your turn! You will have to register in our website first [1],
> put there some information, show interest for the projects and contact
> the project mentors. After the registration step you will get all the
> mentors information in order to contact them. By pressing the button on
> the project, you will show your interest. This is not something formal yet.
>
> Of course you can propose your own project too. In this case write a
> proposal in a format other projects have and send it to admins (see the
> email on the bottom).
>
> Our mentors will vote for the most interesting projects and in the
> middle of the voting Google will tell us, how many projects will
> actually be funded. Voting will happen in May, with final results
> expected at the end of May. At that time you will finally know if you
> are accepted or not.
>
> Of course, there can be many students interested per project. This means
> that interest for this project is high, but on the other side a chance
> that you will be chosen is lower. It is up to you to convince a mentor
> that you are the best!
>
> Note also that the Ideas page is deprecated. On ideas page just the
> project ideas were collected. Now, we are preparing the real projects.
> So, please from now on always refer to this link for the projects:
>
> http://gsoc2013.esug.org/projects
>
> So, your initial steps are:
>
> 1. Register on our special Smalltalk GSoC website (with
> your Google account!):
>
> http://gsoc2013.esug.org/admin?view=loginGoogle
>
> 2. Edit your profile to get some more contact information for
> mentors to let you know,
> 3. Fulfill your brief Biography page (see Biography tab on profile),
> 4. Go to Projects page, choose up to three projects and click there
> 'I'm interested' button,
> 5. Contact and discuss with project mentors about your interest.
>
> Subscribe also to a special mailing list [2] where we will help you with
> further steps.
>
> Deadline: as soon as possible, because the deadline to register on
> official GSoC website [3] is 3.May, which is, well, soon! But about
> that later...
>
> Finally, we will really appreciate if you can help us to distribute this
> call for students. One of our goals is to increase the Smalltalk
> community. Those who have access to universities can distribute this
> among the students. Distribute also our poster [4] in many languages,
> English one attached.
>
>
> [1] http://gsoc2013.esug.org
> [2] Students mailing list:
> http://groups.google.com/group/smalltalk-gsoc-students
> [3] Official GSoC website
> http://www.google-melange.com
> [4] Poster in PDF and image format, in many languages
> http://gsoc2013.esug.org/poster
>
>
> Good luck!
> Janko & Serge
>
> ---
> GSoC Admin Team
> smalltalk.gsoc(a)gmail.com
> http://gsoc2013.esug.org
>
>
> --
> You received this message because you are subscribed to the Google Groups "Smalltalk GSoC students" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to smalltalk-gsoc-students+unsubscribe(a)googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
Yes, I was always wandering why the platform is called Moose.
Begin forwarded message:
> From: Clément Bera <clement.bera(a)inria.fr>
> Subject: proof that moose guys use waterfall project methodology
> Date: 11 квітня 2013 р. 12:36:27 GMT+02:00
> To: Yuriy Tymchuk <yuriy.tymchuk(a)me.com>
>
> https://9gag.com/gag/4457261
>
> --
> Clément Béra
> Mate Virtual Machine Engineer
> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/239/>
------------------------------------------
Started by upstream project "roassal" build number 84
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/hudson4553338059259466114.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.VLXNo/Pharo-20596.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 127 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 97 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: 97; 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
Hello,
I have some nodes on a view, and I would like that on ROMouseEnter,
some edges are shown, and on ROMouseLeave they disappear.
My code is a bit complex, but I can recreate the scenario in a script
if you need.
Best regards,
Martin
