Playground details
by Stephan Eggermont
And once we start looking to details:
- The blue rectangle indicating the focus is on the stack list, and its surrounding tab
have an incorrect size, the right side is cut off.
8 years, 11 months
Re: Playground and Shortcuts
by Goubier Thierry
One example of a workaround:
MessageListBrowser>>updateTree
| prevSelected |
prevSelected := self selectedItem.
self updateList.
prevSelected ifNotNil: [self selectItems: (Array with: prevSelected)]
...
Thierry
Le 04/07/2014 09:15, Goubier Thierry a écrit :
> I'll keep looking.
>
> I have issues with the way selection works between the model and the
> MorphTreeMorph, and I had a bunch of work-around code in my apps, as I
> suspect most users of MorphTreeMorph have (Glamour, Nautilus, etc...).
>
> I try to go step by step and get test cases. That helps. Trying to debug
> with a possibly not working debugger in Moose is not convenient :)
>
> Thierry
>
> Le 04/07/2014 08:43, Tudor Girba a écrit :
>> I forgot to mention that funny enough, clicking on any element in the
>> stack list works just fine. Strange :)
>>
>> Cheers,
>> Doru
>>
>>
>> On Fri, Jul 4, 2014 at 8:00 AM, Tudor Girba <tudor(a)tudorgirba.com
>> <mailto:tudor@tudorgirba.com>> wrote:
>>
>> Thanks. It seems to work the same as the one before from the point
>> of view of Glamour.
>>
>> However, I noticed a strange difference in the debugger. Try this:
>> - Do "1/0"
>> - In the debugger, select the first entry from the top of the stack
>> - Then press down once => it works fine
>> - Then press down again => it goes up!
>> (this behavior is reproducible with the version 3 of your slice as
>> well)
>>
>> I do not know what causes it. Andrei, could you take a look? I do
>> not have time to look at it too deeply right now.
>>
>> Cheers,
>> Doru
>>
>>
>>
>>
>> On Fri, Jul 4, 2014 at 7:25 AM, GOUBIER Thierry
>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>> wrote:
>>
>> Hi Doru,
>>
>> can you test the new slice for 13422 (.4) ? I made a small
>> semantic change to the way the model update the selection after
>> a list update. I haven't seen anything wrong after loading it in
>> Moose (including with the debugger).
>>
>> Thierry
>>
>> ------------------------------------------------------------------------
>> *De :* moose-dev-bounces(a)iam.unibe.ch
>> <mailto:moose-dev-bounces@iam.unibe.ch>
>> [moose-dev-bounces(a)iam.unibe.ch
>> <mailto:moose-dev-bounces@iam.unibe.ch>] de la part de Tudor
>> Girba [tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>]
>> *Envoyé :* jeudi 3 juillet 2014 22:34
>>
>> *À :* Moose-related development
>> *Objet :* [Moose-dev] Re: Playground and Shortcuts
>>
>> Hi,
>>
>> Indeed, it looks good!
>>
>> Doru
>>
>>
>> On Thu, Jul 3, 2014 at 10:24 PM, Tudor Girba
>> <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote:
>>
>> I am testing right away.
>>
>> Doru
>>
>>
>> On Thu, Jul 3, 2014 at 10:20 PM, GOUBIER Thierry
>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>>
>> wrote:
>>
>> Normally solved with the latest slice:
>>
>> SLICE-Issue-13422-Image-crashes-because-an-open-Nautilus-browser-hangs-onto-many-objects-while-code-is-being-loaded-ThierryGoubier.3.
>>
>>
>> Bug was: Wrong selection update loop while cleaning the
>> listManager on update.
>> I also added a real delete for the removed morphs during
>> update.
>>
>> I won't integrate yet, I'd like to explore things about
>> the selection while updating mechanism, and the Moose
>> image is hard to use on my netbook.
>>
>> Can you test if this solves all the problems you could
>> see with trees and lists? I checked that it solved the
>> debugger and the test case issues.
>>
>> Thierry
>> ________________________________________
>> De : moose-dev-bounces(a)iam.unibe.ch
>> <mailto:moose-dev-bounces@iam.unibe.ch>
>> [moose-dev-bounces(a)iam.unibe.ch
>> <mailto:moose-dev-bounces@iam.unibe.ch>] de la part de
>> GOUBIER Thierry
>> Envoyé : jeudi 3 juillet 2014 17:26
>> À : Moose-related development
>> Objet : [Moose-dev] Re: Playground and Shortcuts
>>
>> Ok. I'll look into that later today, have to pick up the
>> kids.
>>
>> So far, so good. Update is correct, selected element is
>> removed but is
>> kept as expanded (because of the select, I guess), but
>> then it seems to
>> be reintroduced in the tree.
>>
>> Working out of the test case Stephan pointed out.
>>
>> Thierry
>>
>> Le 03/07/2014 16:58, Tudor Girba a écrit :
>> > 30851 already contains the problematic issue.
>> >
>> > Doru
>> >
>> >
>> >
>> > On Thu, Jul 3, 2014 at 4:50 PM, Goubier Thierry
>> <thierry.goubier(a)cea.fr <mailto:thierry.goubier@cea.fr>
>> > <mailto:thierry.goubier@cea.fr
>> <mailto:thierry.goubier@cea.fr>>> wrote:
>> >
>> > Ok.
>> >
>> > Where is the configurationOfGlamour? The current
>> Moose5.0 beta image
>> > in the pharo launcher is on 30851.
>> >
>> > Thierry
>> >
>> > Le 03/07/2014 16:45, Tudor Girba a écrit :
>> >
>> > Or that Glamour uses an internal API that it
>> should not :)
>> >
>> > Doru
>> >
>> >
>> > On Thu, Jul 3, 2014 at 4:41 PM, Stephan
>> Eggermont
>> > <stephane(a)xs4all.nl
>> <mailto:stephane@xs4all.nl> <mailto:stephane@xs4all.nl
>> <mailto:stephane@xs4all.nl>>
>> > <mailto:stephane@xs4all.nl
>> <mailto:stephane@xs4all.nl> <mailto:stephane@xs4all.nl
>> <mailto:stephane@xs4all.nl>>>> wrote:
>> >
>> > I can confirm it is the 13422 fix that
>> is broken/incomplete
>> >
>> > Stephan
>> >
>> _________________________________________________
>> > Moose-dev mailing list
>> > Moose-dev(a)iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>
>> <mailto:Moose-dev@iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>>
>> > <mailto:Moose-dev@iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>
>> <mailto:Moose-dev@iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>>__>
>> > https://www.iam.unibe.ch/__mailman/listinfo/moose-dev
>> >
>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>> >
>> >
>> >
>> >
>> > --
>> > www.tudorgirba.com <http://www.tudorgirba.com>
>> <http://www.tudorgirba.com>
>> > <http://www.tudorgirba.com>
>> >
>> >
>> > "Every thing has its own flow"
>> >
>> >
>> >
>> _________________________________________________
>> > Moose-dev mailing list
>> > Moose-dev(a)iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>
>> <mailto:Moose-dev@iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>>
>> > https://www.iam.unibe.ch/__mailman/listinfo/moose-dev
>> >
>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>> >
>> >
>> > --
>> > Thierry Goubier
>> > CEA list
>> > Laboratoire des Fondations des Systèmes Temps
>> Réel Embarqués
>> > 91191 Gif sur Yvette Cedex
>> > France
>> > Phone/Fax: +33 (0) 1 69 08 32 92
>> <tel:%2B33%20%280%29%201%2069%2008%2032%2092>
>> > <tel:%2B33%20%280%29%201%2069%2008%2032%2092> /
>> 83 95
>> > _________________________________________________
>> > Moose-dev mailing list
>> > Moose-dev(a)iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>
>> <mailto:Moose-dev@iam.unibe.ch
>> <mailto:Moose-dev@iam.unibe.ch>>
>> > https://www.iam.unibe.ch/__mailman/listinfo/moose-dev
>> >
>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
>> >
>> >
>> >
>> >
>> > --
>> > www.tudorgirba.com <http://www.tudorgirba.com>
>> <http://www.tudorgirba.com>
>> >
>> > "Every thing has its own flow"
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>>
>> --
>> Thierry Goubier
>> CEA list
>> Laboratoire des Fondations des Systèmes Temps Réel
>> Embarqués
>> 91191 Gif sur Yvette Cedex
>> France
>> Phone/Fax: +33 (0) 1 69 08 32 92
>> <tel:%2B33%20%280%29%201%2069%2008%2032%2092> / 83 95
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>>
>> --
>> www.tudorgirba.com <http://www.tudorgirba.com>
>>
>> "Every thing has its own flow"
>>
>>
>>
>>
>> --
>> www.tudorgirba.com <http://www.tudorgirba.com>
>>
>> "Every thing has its own flow"
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>>
>> --
>> www.tudorgirba.com <http://www.tudorgirba.com>
>>
>> "Every thing has its own flow"
>>
>>
>>
>>
>> --
>> www.tudorgirba.com <http://www.tudorgirba.com>
>>
>> "Every thing has its own flow"
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
8 years, 11 months
Roassal2 - shape instance and elements
by Leo Perard
Hi,
I'm not sure it is but I think I have found a bug where elements share the
same instance of a shape.
Here an example:
view := RTView new.
els := (RTBox new size: 20) elementsOn: (1 to: 10).
view addAll: els.
els do: [ :e |
e on: TRMouseClick do: [ :event |
e shape color: Color random. e update. els atRandom update. view
signalUpdate ]
].
RTHorizontalLineLayout on: els.
view open
It should only change the color of one element but it doesn't.
So I don't know if it is wanted or not.
--
Cheers,
Leo Perard
University of Lille 1
8 years, 11 months
Playground and Shortcuts
by Leo Perard
Hi all,
the usual shortcuts with Linux (Alt+d for example) are not working with the
Playground.
I have to use the Ctrl+ shortcut to use it. I replace the playground by the
workspace and it works with it so I guess the bug is in the playground.
But not all of the shortcuts are not working, for example Alt+o is working.
The list of those that do not work:
Alt+a
Alt+i
Alt+d
Alt+c
Alt+x
Alt+v
maybe others but I didn't check them all.
I'm on ubuntu 13.10 64bits.
--
Cheers,
Leo Perard
University of Lille 1
8 years, 11 months
Re: Playground and Shortcuts
by Stephan Eggermont
Could it be related to the failing test in CI?
(Mac Mavericks 10.9.2)
GLMUpdateMorphicTest>>testInvalidateSelection
(browser panes first port: #selection) value: 3.
entity removeLast.
announcer announce: GLMTestAnnouncement.
self assert: (browser panes first port: #selection) value isNil.
self assert: listMorph model selection isNil
When I run the glamour tests from the test runner, there
is one TestFailure. If I try to debug it, the debugger doesn't work
(shows only one pane)
8 years, 11 months
Roassal2 - update RTLabel Shape
by Leo Perard
Hi,
I want to update the shape of an element which has an RTShape and I want to
change the text.
When I update nothing append. If I change the color it works so I think
there is bug when updating the text.
view := RTView new.
el := (RTLabel new text: 'Hello') element.
view add: el.
el on: TRMouseLeftClick do: [ :event | el shape text: 'Change'; color:
Color red. el update. view signalUpdate ].
view open
--
Cheers,
Leo Perard
University of Lille 1
8 years, 11 months
Re: length of edges in roassal
by Fabrice Atrevi
Hi Mr Alexandre,
How can i visualize your exemple in Glamour. which method can i call?
Actually, i use the default builder in Glamour with roassal (
ROMondrianViewBuilder,
i think!).
Thanks!
2014-06-09 4:06 GMT+07:00 <moose-dev-request(a)iam.unibe.ch>:
> Send Moose-dev mailing list submissions to
> moose-dev(a)iam.unibe.ch
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> or, via email, send a message with subject or body 'help' to
> moose-dev-request(a)iam.unibe.ch
>
> You can reach the person managing the list at
> moose-dev-owner(a)iam.unibe.ch
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Moose-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Roassal2: sending @ RTLabelled to an empty edges group
> bug (Alexandre Bergel)
> 2. Re: RTView>>cleanAll: does not remove labels (Alexandre Bergel)
> 3. Re: length of edges in roassal (Alexandre Bergel)
> 4. Re: Loading large XML files in MOOSE (Serge Stinckwich)
> 5. Jenkins build became unstable: moose-5.0 #1593
> (admin(a)moosetechnology.org)
> 6. Re: Roassal2: sending @ RTLabelled to an empty edges group
> bug (Johan Fabry)
> 7. Re: Loading large XML files in MOOSE (Alexandre Bergel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 08 Jun 2014 16:02:08 -0400
> From: Alexandre Bergel <alexandre.bergel(a)me.com>
> Subject: [Moose-dev] Re: Roassal2: sending @ RTLabelled to an empty
> edges group bug
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <EE750C18-4B56-4A1F-8A91-D1EB8377B5D2(a)me.com>
> Content-Type: text/plain; charset=windows-1252
>
> I am not sure to understand this.
>
> The following does not produce an error: RTGroup new @ RTLabelled
>
> Alexandre
>
>
> On Jun 8, 2014, at 3:00 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
>
> > I hit send to fast, sorry.
> >
> > The origin of the bug is Array>>@ interactionClassOrObject line 2: obj
> := interactionClassOrObject elementToBeAdded. The interactionClassOrObject
> is a RTLabelled class, and it DNU?s that message.
> >
> >
> > On Jun 8, 2014, at 2:49 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
> >
> >> Hi all,
> >>
> >> at some point I was sending @RTlabelled to a group of edges that
> happened to be empty, and up came the debugger :-(
> >>
> >>
> >> ---> Save our in-boxes! http://emailcharter.org <---
> >>
> >> Johan Fabry - http://pleiad.cl/~jfabry
> >> PLEIAD lab - Computer Science Department (DCC) - University of Chile
> >>
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> Moose-dev(a)iam.unibe.ch
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >
> >
> >
> > ---> Save our in-boxes! http://emailcharter.org <---
> >
> > Johan Fabry - http://pleiad.cl/~jfabry
> > PLEIAD lab - Computer Science Department (DCC) - University of Chile
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 08 Jun 2014 16:19:53 -0400
> From: Alexandre Bergel <alexandre.bergel(a)me.com>
> Subject: [Moose-dev] Re: RTView>>cleanAll: does not remove labels
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <04B5400A-15E9-45A1-B88C-F8907FFCB826(a)me.com>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> Well spotted!
> Fixed in version 0.272 of Roassal
>
> Alexandre
>
>
> On Jun 8, 2014, at 2:15 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
>
> > Hi all,
> >
> > another small bug in Roassal2: sending cleanAll to a view does not
> remove the labels attached to nodes in that view.
> >
> >
> > ---> Save our in-boxes! http://emailcharter.org <---
> >
> > Johan Fabry - http://pleiad.cl/~jfabry
> > PLEIAD lab - Computer Science Department (DCC) - University of Chile
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 08 Jun 2014 16:26:20 -0400
> From: Alexandre Bergel <alexandre.bergel(a)me.com>
> Subject: [Moose-dev] Re: length of edges in roassal
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <CD07EFD1-41E3-4E83-B4E6-9B9F8B7CEC79(a)me.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi Fabrice,
>
> I am not sure what you actually need. Why do you find the edges too short?
> Currently we cannot set the length of edges. This will come soon, but
> right now we cannot.
>
> If you want to minimize crossing, then there are two solutions:
> - use a sugyama layout: RTSugiyamaLayout
> - use the force based Layout. Execute in a workspace:
> RTRoassalExample new exampleForceBasedLayoutAnimated
>
> Let us know how it goes...
>
> Cheers,
> Alexandre
>
>
>
> On Jun 7, 2014, at 5:18 PM, Fabrice Atrevi <atrevifabrice(a)gmail.com>
> wrote:
>
> > Hi!
> > I'm using roassal in glamour for painting. I want to know how i can give
> a length for edge. Like in the screenshot, the default length is too small.
> And if possible, i want boxes and arcs do not intersect.
> >
> > Thanks,
> >
> > --
> > ATREVI D. Fabrice
> > Master en Informatique A l'Institut de la Francophonie pour
> l'Informatique (IFI/Hano?)
> > <relation_seir.PNG>_______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 8 Jun 2014 22:35:46 +0200
> From: Serge Stinckwich <serge.stinckwich(a)gmail.com>
> Subject: [Moose-dev] Re: Loading large XML files in MOOSE
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID:
> <CAOysuxUk5nOt9U_=PHXobF=
> df9ExjGcVGBZjE9-XCbsuzQw8dw(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Thank you Doru for the help.
>
> First case: 74Mb XML file. I'm able to load the string in memory but
> the XML parser crash the image before the end.
> Second case: 10Mb XML file. I'm able to load the string in memory,
> parse the XML file. When I start to process the XML file in order to
> create an object structure, the panel "Space is too low" appear.
>
> I would like to give a try with the XMLPullParser. I guess this is
> working correctly, because I find it with the Configuration Browser.
>
>
> On Sat, Jun 7, 2014 at 10:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
> > Hi,
> >
> > Ok, I looked a bit, and here is a way to get it to work. It is not at all
> > ideal given that it loads the entire string before parsing it, but it
> surely
> > will work with an xml of your size:
> >
> > contents := fileReference readStreamDo: [ :stream | stream contents ].
> > svnlog := (XMLDOMParser on: contents )
> > documentReadLimit: contents size;
> > parseDocument.
> >
> > Cheers,
> > Doru
> >
> >
> >
> > On Fri, Jun 6, 2014 at 12:50 PM, Tudor Girba <tudor(a)tudorgirba.com>
> wrote:
> >>
> >> I encountered a similar situation before, but there is a way to go
> beyond
> >> that limit.
> >>
> >> I do not have the code at my disposal right now, but look at the
> >> XMLDOMParser constructor, and at some point you will see a hardcoded
> limit
> >> value. You should be able to pass another one in.
> >>
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >> On Fri, Jun 6, 2014 at 11:22 AM, Serge Stinckwich
> >> <serge.stinckwich(a)gmail.com> wrote:
> >>>
> >>> Dear all,
> >>>
> >>> I want to process large XML file (typically event logs with more than
> >>> 80Mb data) and I'm not able to do that at the moment with the XML DOM
> >>> parser (it says I reach the read limit after 3094 XML lines) and I
> >>> guess I will have problem to manage such a large file in memory after
> >>> that.
> >>>
> >>> Should I switch to an event-driven XML parser in order to avoid
> >>> loading all the XML file in memory ? Do we have such a parser for
> >>> Pharo ?
> >>>
> >>> --
> >>> Serge Stinckwich
> >>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> >>> Every DSL ends up being Smalltalk
> >>> http://www.doesnotunderstand.org/
> >>> _______________________________________________
> >>> Moose-dev mailing list
> >>> Moose-dev(a)iam.unibe.ch
> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >>
> >>
> >>
> >> --
> >> www.tudorgirba.com
> >>
> >> "Every thing has its own flow"
> >
> >
> >
> >
> > --
> > www.tudorgirba.com
> >
> > "Every thing has its own flow"
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 8 Jun 2014 22:41:04 +0200 (CEST)
> From: admin(a)moosetechnology.org
> Subject: [Moose-dev] Jenkins build became unstable: moose-5.0 #1593
> To: moose-dev(a)iam.unibe.ch
> Message-ID:
> <
> 704547223.139.1402260064428.JavaMail.jenk_moose(a)ci-jenkins3.inria.fr>
> Content-Type: text/plain; charset=UTF-8
>
> See <https://ci.inria.fr/moose/job/moose-5.0/1593/>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 8 Jun 2014 17:03:22 -0400
> From: Johan Fabry <jfabry(a)dcc.uchile.cl>
> Subject: [Moose-dev] Re: Roassal2: sending @ RTLabelled to an empty
> edges group bug
> To: moose-dev related tools <moose-dev(a)iam.unibe.ch>
> Message-ID: <EE3A1133-EF75-4DBF-924E-65844A997CEC(a)dcc.uchile.cl>
> Content-Type: text/plain; charset=windows-1252
>
>
> I think it?s best that I show you when you are back ? it?s so deep in my
> code that I cannot easily reproduce it in a simple example :-(
>
> On Jun 8, 2014, at 4:02 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
> wrote:
>
> > I am not sure to understand this.
> >
> > The following does not produce an error: RTGroup new @ RTLabelled
> >
> > Alexandre
> >
> >
> > On Jun 8, 2014, at 3:00 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
> >
> >> I hit send to fast, sorry.
> >>
> >> The origin of the bug is Array>>@ interactionClassOrObject line 2: obj
> := interactionClassOrObject elementToBeAdded. The interactionClassOrObject
> is a RTLabelled class, and it DNU?s that message.
> >>
> >>
> >> On Jun 8, 2014, at 2:49 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote:
> >>
> >>> Hi all,
> >>>
> >>> at some point I was sending @RTlabelled to a group of edges that
> happened to be empty, and up came the debugger :-(
> >>>
> >>>
> >>> ---> Save our in-boxes! http://emailcharter.org <---
> >>>
> >>> Johan Fabry - http://pleiad.cl/~jfabry
> >>> PLEIAD lab - Computer Science Department (DCC) - University of
> Chile
> >>>
> >>>
> >>> _______________________________________________
> >>> Moose-dev mailing list
> >>> Moose-dev(a)iam.unibe.ch
> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>>
> >>
> >>
> >>
> >> ---> Save our in-boxes! http://emailcharter.org <---
> >>
> >> Johan Fabry - http://pleiad.cl/~jfabry
> >> PLEIAD lab - Computer Science Department (DCC) - University of Chile
> >>
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> Moose-dev(a)iam.unibe.ch
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
>
>
>
> ---> Save our in-boxes! http://emailcharter.org <---
>
> Johan Fabry - http://pleiad.cl/~jfabry
> PLEIAD lab - Computer Science Department (DCC) - University of Chile
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 08 Jun 2014 17:05:54 -0400
> From: Alexandre Bergel <alexandre.bergel(a)me.com>
> Subject: [Moose-dev] Re: Loading large XML files in MOOSE
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <7A240162-C07C-4883-9005-834221F8973D(a)me.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Serge, you are using a mac don?t you? Have you tried to augment the memory
> of the image?
>
> Open using a text editor the Info.plist file, contained in the VM folder.
> By checking on the internet, 1880000000 is apparently the biggest value
> possible.
> http://forum.world.st/OSX-squeak-crash-maximal-size-of-image-td2952312.html
>
>
>
>
> Cheers,
> Alexandre
>
>
> On Jun 8, 2014, at 4:35 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com>
> wrote:
>
> > Thank you Doru for the help.
> >
> > First case: 74Mb XML file. I'm able to load the string in memory but
> > the XML parser crash the image before the end.
> > Second case: 10Mb XML file. I'm able to load the string in memory,
> > parse the XML file. When I start to process the XML file in order to
> > create an object structure, the panel "Space is too low" appear.
> >
> > I would like to give a try with the XMLPullParser. I guess this is
> > working correctly, because I find it with the Configuration Browser.
> >
> >
> > On Sat, Jun 7, 2014 at 10:56 PM, Tudor Girba <tudor(a)tudorgirba.com>
> wrote:
> >> Hi,
> >>
> >> Ok, I looked a bit, and here is a way to get it to work. It is not at
> all
> >> ideal given that it loads the entire string before parsing it, but it
> surely
> >> will work with an xml of your size:
> >>
> >> contents := fileReference readStreamDo: [ :stream | stream contents ].
> >> svnlog := (XMLDOMParser on: contents )
> >> documentReadLimit: contents size;
> >> parseDocument.
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >>
> >> On Fri, Jun 6, 2014 at 12:50 PM, Tudor Girba <tudor(a)tudorgirba.com>
> wrote:
> >>>
> >>> I encountered a similar situation before, but there is a way to go
> beyond
> >>> that limit.
> >>>
> >>> I do not have the code at my disposal right now, but look at the
> >>> XMLDOMParser constructor, and at some point you will see a hardcoded
> limit
> >>> value. You should be able to pass another one in.
> >>>
> >>>
> >>> Cheers,
> >>> Doru
> >>>
> >>>
> >>> On Fri, Jun 6, 2014 at 11:22 AM, Serge Stinckwich
> >>> <serge.stinckwich(a)gmail.com> wrote:
> >>>>
> >>>> Dear all,
> >>>>
> >>>> I want to process large XML file (typically event logs with more than
> >>>> 80Mb data) and I'm not able to do that at the moment with the XML DOM
> >>>> parser (it says I reach the read limit after 3094 XML lines) and I
> >>>> guess I will have problem to manage such a large file in memory after
> >>>> that.
> >>>>
> >>>> Should I switch to an event-driven XML parser in order to avoid
> >>>> loading all the XML file in memory ? Do we have such a parser for
> >>>> Pharo ?
> >>>>
> >>>> --
> >>>> Serge Stinckwich
> >>>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> >>>> Every DSL ends up being Smalltalk
> >>>> http://www.doesnotunderstand.org/
> >>>> _______________________________________________
> >>>> Moose-dev mailing list
> >>>> Moose-dev(a)iam.unibe.ch
> >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> www.tudorgirba.com
> >>>
> >>> "Every thing has its own flow"
> >>
> >>
> >>
> >>
> >> --
> >> www.tudorgirba.com
> >>
> >> "Every thing has its own flow"
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> Moose-dev(a)iam.unibe.ch
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>
> >
> >
> >
> > --
> > Serge Stinckwich
> > UCBN & UMI UMMISCO 209 (IRD/UPMC)
> > Every DSL ends up being Smalltalk
> > http://www.doesnotunderstand.org/
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev(a)iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
8 years, 11 months
