We wanted to open a DistributionMap with a given windows size. Any idea how
to do it?
We looked with stef in the MOViewRenderer class but nothing jumps to our
eyes.
Thanks.
--
*Guillaume Larcheveque*
Hi,
I used inFamix to create an .mse File of Jython <http://www.jython.org/>.
All works well except the namespacing seems to be a bit off in the model,
e.g. there is a namespace called jython and another one called jython::util
but the first is not defined as parentPackage of the latter. I think they
should be thought - at least for Java systems.
Mircea Lungu told me there was a class floating around somewhere which
fixes this for moose models. Could anyone point me to it? I'd like to use
it for testing.
Also, is inFamix maybe capable of doing that but I haven't found it? Or are
there other tools which do the importing with namespaces linked in this way?
Cheers,
Dennis
Hi all,
I am trying to import an MSE file [1] generated by Verveine-J into the
latest moose-latest-dev image [2].
My image is basically the same you find in the Jenkins build and I am
running it on MacOS 10.7.3.
When the parsing of the file is almost completed I get this dialog:
"Space is low
Warning! Pharo is almost out of memory!
Low space detection is now disabled. [...]"
By simply closing all the windows and restarting the image, I have no luck:
The message still appears.
The message also suggests to "restart the Pharo VM with a larger memory
allocation." Unfortunately I have no idea on how to do this in general, and
on a Mac in particular. I looked at previous threads in the mailing list,
but I was not able to find any solution.
Can anyone help me with this problem, please?
Thank you in advance.
Cheers,
Alberto
[1] http://www.inf.usi.ch/phd/bacchelli/svn_2011_06_30.mse.zip
[2]
http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti…
--
View this message in context: http://moose-dev.97923.n3.nabble.com/Space-is-low-tp3823370p3823370.html
Sent from the moose-dev mailing list archive at Nabble.com.
I've had some trouble with email. I'm not sure if this one made it out
or if I just didn't get it back from the list.
I would have missed any responses.
Ben Coman wrote:
8<----cut-------
> So in the end I added 'self update' to the start of
> GLMMagrittePresentation>>reactOnAnswerFor: as follows...
> reactOnAnswerFor: aValue
> self update.
> ^ answerBlock glamourValue:
> (aValue asGlamorousMultiValue,
> self asGlamorousMultiValue,
> self entity asGlamorousMultiValue)
>
> and now the <cancel> button works as expected. However I still don't
> know what reactOnAnswerFor is meant to do, or if there
> is a more appropriate way of achieving this. Please let me know.
>
> I also haven't had any success getting the #list pane to refresh when
> a change is saved on the #detail pane. Any assistance will be greatly
> appreciated.
>
> cheers, -ben
>
Phew! That was a lot to take in. Upon further investigation I retract
modifying GLMMagrittePresentation.
The solution to both the <save> and <cancel> buttons can be encompassed
entirely within the user code with one additional line 'onAnswer:'
magritteParentPrototype := a magritte.
magritteParentPrototype "these are the essential parts"
title: 'Details';
description: [:person | person magritteDescription] ;
onAnswer: [ :ignore | browser update ] .
I have uploaded this as Glamour-Examples-BenComan.230
Note that I think this only worked for me last time when I had
MagritteMagic loaded onto Moose 4.6.
cheers, Ben
Hello,
I have a one-click moose image downloaded around first week of Feb 2012.
The problem with the image is that it's windows vm that does not launch the
image file. In fact, when I execute the vm, it creates a process (visible
in windows task manager) but nothing happens. We tried to debug it with
Igor but we couldn't (as there is no entry point). The image in the bundle
can be launched with latest windows vm (from pharo server) [meaning that
the problem comes from the vm which we cannot debug].
I downloaded another moose image today and executed its windows vm, and its
working fine.
It would be good to have a jenkins process to run moose on windows vm. Do
we have such a setup? If not, I can create one in the coming weeks.
thanx,
usman
Hi again,
I am still exploring moose and my immediate usage is to identify dead code
(classes, methods, variables). There are two issues I am facing with
false-positive.
1.) In java a lot is configured/instantiated via the usage of XML. E.g. the
Log4J configuration happens via xml, another example would be the menu
structure of an Eclipse plugin.
What would be the easiest way to represent these usages in a .mse file? Is
there a tool to merge two .mse files or combine them?
2.) The attribute/field detection of verveineJ does not see all variable
usages, e.g. it appears that it can not resolve a "this.foo" properly (e.g. in
a constructor, or in an anonymous class). I will try to have a minimal
testcase to show this issue (as my time permits).
holger
firstly, i would to thank all that supporting mosse for ussecondly, i want any one help me with details, now i have a java project built with eclipse, i want to parser all project through Famix using VerveinJ to get all information about the code number of attribute and methods classes etc. with my best regards With My Best Regards Ra'fat Ahmad Ali AL-Msie'Deen
Phone # : 0033761712744E-mail : rafatals3ode(a)yahoo.com
Take Care
>
> Correcting what I told...
>
> Hi,
>>>
>>> You can probably save time and memory by directly passing the file
>>> stream to the XMLParser:
>>> stream := (FileStream readOnlyFileNamed: aFilenameString) readStream.
>>> root := (XMLDOMParser parse: stream) root.
>>>
>>
>> I follow your suggestion Tudor, but it didn't reduce the total time
>> expended on reading of data or the reduction was minimal.
>>
>>
>>> A question: if you do you have a problem with the reading part (I mean
>>> to compute the root), or is it spent in the follow up loops?
>>>
>>
>> I not understood well your question.
>>
> I was able to compute almost everything that I needed, *but for some
>> reason, some data are lost when I iterate on root*
>>
>
> In truth it can be correct, I messed up to interpret the data.
>
>>
>>
>
>>
>>
>>> Cheers,
>>> Doru
>>>
>>>
>>>
>>> 2012/3/9 Júlio Martins <[hidden email]<http://user/SendEmail.jtp?type=node&node=4459560&i=0>
>>> >:
>>>
>>> > HI!
>>> >
>>> > I have a optimization problem to solve and I would want some hint of
>>> you.
>>> >
>>> > I am using the xml framework to work with data from xml file, and the
>>> > reading of the data is consuming much time.
>>> > In my code I do something as:
>>> >
>>> > | stream root |
>>> >
>>> > stream := (FileStream readOnlyFileNamed: aPath) contentsOfEntireFile
>>> > asString..
>>> > root := (XMLDOMParser parse: stream) root.
>>> >
>>> > root allElementsNamed: 'something' do:[ :eachB|
>>> > eachB attributeNodes attributeValueAt: 'list'
>>> > ...
>>> > eachB allElementsNamed: 'another something' do:{ :eachD|
>>> > . eachD attributeNodes attributeValueAt: 'element'
>>> > ..
>>> > ]
>>> > ]
>>> >
>>> > I know such iteration like that take much time to be executed when the
>>> file
>>> > read is big. There is a another manner to read the data from xml file
>>> that
>>> > consume less time as possible? Or have someone an idea to improve this
>>> code?
>>> >
>>> > Julio
>>> >
>>> > ________________________________
>>> > View this message in context: XML Data Parsing
>>> > Sent from the Moose mailing list archive at Nabble.com.
>>> >
>>> > _______________________________________________
>>> > Moose-dev mailing list
>>> > [hidden email] <http://user/SendEmail.jtp?type=node&node=4459560&i=1>
>>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>> >
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=4459560&i=2>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>
>>
>> ------------------------------
>> View this message in context: XML Data Parsing<http://forum.world.st/XML-Data-Parsing-tp4459560p4459560.html>
>> Sent from the Moose mailing list archive<http://forum.world.st/Moose-f1310756.html>at Nabble.com.
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>
--
View this message in context: http://forum.world.st/XML-Data-Parsing-tp4459626p4459626.html
Sent from the Moose mailing list archive at Nabble.com.
Correcting what I told...
Hi,
>>
>> You can probably save time and memory by directly passing the file
>> stream to the XMLParser:
>> stream := (FileStream readOnlyFileNamed: aFilenameString) readStream.
>> root := (XMLDOMParser parse: stream) root.
>>
>
> I follow your suggestion Tudor, but it didn't reduce the total time
> expended on reading of data or the reduction was minimal.
>
>
>> A question: if you do you have a problem with the reading part (I mean
>> to compute the root), or is it spent in the follow up loops?
>>
>
> I not understood well your question. I got to compute almost everything
> that I needed, *but for some reason, some data are lost when I iterate on
> root*
>
In truth it can be correct, I messed up to interpret the data.
>
>
>
>
>> Cheers,
>> Doru
>>
>>
>>
>> 2012/3/9 Júlio Martins <[hidden email]<http://user/SendEmail.jtp?type=node&node=4459560&i=0>
>> >:
>>
>> > HI!
>> >
>> > I have a optimization problem to solve and I would want some hint of
>> you.
>> >
>> > I am using the xml framework to work with data from xml file, and the
>> > reading of the data is consuming much time.
>> > In my code I do something as:
>> >
>> > | stream root |
>> >
>> > stream := (FileStream readOnlyFileNamed: aPath) contentsOfEntireFile
>> > asString..
>> > root := (XMLDOMParser parse: stream) root.
>> >
>> > root allElementsNamed: 'something' do:[ :eachB|
>> > eachB attributeNodes attributeValueAt: 'list'
>> > ...
>> > eachB allElementsNamed: 'another something' do:{ :eachD|
>> > . eachD attributeNodes attributeValueAt: 'element'
>> > ..
>> > ]
>> > ]
>> >
>> > I know such iteration like that take much time to be executed when the
>> file
>> > read is big. There is a another manner to read the data from xml file
>> that
>> > consume less time as possible? Or have someone an idea to improve this
>> code?
>> >
>> > Julio
>> >
>> > ________________________________
>> > View this message in context: XML Data Parsing
>> > Sent from the Moose mailing list archive at Nabble.com.
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > [hidden email] <http://user/SendEmail.jtp?type=node&node=4459560&i=1>
>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>> >
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email] <http://user/SendEmail.jtp?type=node&node=4459560&i=2>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>
>
> ------------------------------
> View this message in context: XML Data Parsing<http://forum.world.st/XML-Data-Parsing-tp4459560p4459560.html>
> Sent from the Moose mailing list archive<http://forum.world.st/Moose-f1310756.html>at Nabble.com.
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
--
View this message in context: http://forum.world.st/Re-Moose-dev-XML-Data-Parsing-tp4459619p4459619.html
Sent from the Moose mailing list archive at Nabble.com.
>
> Hi,
>
> You can probably save time and memory by directly passing the file
> stream to the XMLParser:
> stream := (FileStream readOnlyFileNamed: aFilenameString) readStream.
> root := (XMLDOMParser parse: stream) root.
>
I follow your suggestion Tudor, but it didn't reduce the total time
expended on reading of data or the reduction was minimal.
> A question: if you do you have a problem with the reading part (I mean
> to compute the root), or is it spent in the follow up loops?
>
I not understood well your question. I got to compute almost everything
that I needed, but for some reason, some data are lost when I iterate on
root. Is about it your question?
> Cheers,
> Doru
>
>
>
> 2012/3/9 Júlio Martins <jleandro.martins(a)gmail.com>:
> > HI!
> >
> > I have a optimization problem to solve and I would want some hint of you.
> >
> > I am using the xml framework to work with data from xml file, and the
> > reading of the data is consuming much time.
> > In my code I do something as:
> >
> > | stream root |
> >
> > stream := (FileStream readOnlyFileNamed: aPath) contentsOfEntireFile
> > asString..
> > root := (XMLDOMParser parse: stream) root.
> >
> > root allElementsNamed: 'something' do:[ :eachB|
> > eachB attributeNodes attributeValueAt: 'list'
> > ...
> > eachB allElementsNamed: 'another something' do:{ :eachD|
> > . eachD attributeNodes attributeValueAt: 'element'
> > ..
> > ]
> > ]
> >
> > I know such iteration like that take much time to be executed when the
> file
> > read is big. There is a another manner to read the data from xml file
> that
> > consume less time as possible? Or have someone an idea to improve this
> code?
> >
> > Julio
> >
> > ________________________________
> > View this message in context: XML Data Parsing
> > Sent from the Moose mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > 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"
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
--
View this message in context: http://forum.world.st/XML-Data-Parsing-tp4459560p4459560.html
Sent from the Moose mailing list archive at Nabble.com.
