Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1029 by rob...(a)pergl.org: Roassal Easel crashed
http://code.google.com/p/moose-technology/issues/detail?id=1029
Ubuntu 13.10
MooseSuite 4.9
Go to Browse - In Roassal Easel - eg - Adding Name - hover with mouse
around the tree
* Type-Defect
--
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
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1031 by rainbowt...(a)gmail.com: smalltalk import doesn't work
(moose5)
http://code.google.com/p/moose-technology/issues/detail?id=1031
moose 5 from pharo launcher
- open moose panel
- press import famix model from image
- select any package(s) >>>
- press next, finish
I get the debugger, closing it cancels import
Please fill in the labels with the following information:
* Type-Defect
* Component-Moose
--
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
Hi,
I looked a bit at the existing hardcoded traversal methods in a Pharo/Moose
image. To detect it, I used a traversal. Perhaps this can also be useful
for people that want to teach what a traversal is, or what an analysis is,
so I wrote a blog post about it:
http://www.humane-assessment.com/blog/looking-for-hardcoded-traversal-metho…
Cheers,
Doru
On Sat, Dec 14, 2013 at 3:44 PM, Mariano Martinez Peck <
marianopeck(a)gmail.com> wrote:
>
>
>
> On Wed, Dec 11, 2013 at 12:21 PM, Tudor Girba <tudor(a)tudorgirba.com>wrote:
>
>> Hi,
>>
>> I put together a little implementation for traversals. It is inspired by
>> an original implementation from Mariano.
>>
>
> Wow... my memory is sooo bad I don't remember ;)
>
>
>
>> Using DeepTraverser, you can traverse arbitrary graphs by describing the
>> traversal and by specifying the actions you want to perform on the nodes
>> and relations.
>>
>>
> Once (or even more times) we thought with Martin 2 things:
>
> 1) Reify the traversal in Fuel so that we could plug a different one.
> 2) Use Fuel only for traversing and allowing user a hook to plug the what
> to do with each node.
> 3) Use the same traversal of 2) for deepCopying
> 4) Use the same traversal of 2) to get an approximate memory consumption
> of the transitive closure of an object
>
> But as always happened we run out of time.
>
> Anyway...I think this is a nice area to explore. There are many uses for a
> nice traverser.
>
> Also, did you see we wrote a Rossal extension to print the fuel traversal?
>
> http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.9/Documentation/…
>
>
> The code is available in the Moose image as part of the MooseAlgos
>> subproject, but can also be loaded separately in a Pharo image via:
>>
>> Gofer new
>> url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main';
>> package: ‘ConfigurationOfDeepTraverser’;
>> load.
>> (Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment.
>>
>>
>> Just to give you an idea, here are some representative examples:
>>
>> Number
>> deep: #subclasses
>> do: [:each | Transcript show: each; cr].
>>
>> Number deepCollect: #subclasses.
>>
>> Number
>> deep: #subclasses
>> collect: #name.
>>
>> Number
>> deep: #subclasses
>> do: [:each | Transcript show: each; cr]
>> relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show:
>> to; cr ].
>>
>>
>>
>> More details about the usages and a little description of the
>> implementation can be found here:
>> http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/
>>
>>
>> Cheers,
>> Doru
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hi!
I had a look at the failing test in Moose. I have found the reason:
-=-=-=-=-=-=-=-=
FAMIXPackageGroup>>browsePackageBlueprints
<menuItem: 'Browse Package Blueprints' category: 'Visualize'>
PackageBlueprint openBlueprintBrowserOn: self
-=-=-=-=-=-=-=-=
The class PackageBlueprint is undefined.
I remember that Doru moved it somewhere?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-VerveineJ
New issue 1030 by anquetil...(a)gmail.com: VerveineJ does not export local
variables
http://code.google.com/p/moose-technology/issues/detail?id=1030
Some local variables are not exported in the mse file even when we don't
specify the -summary option
--
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
wrong mailing list…
Alexandre
Begin forwarded message:
> From: Alexandre Bergel <alexandre.bergel(a)me.com>
> Subject: [Pharo-dev] GTDebugger...
> Date: December 15, 2013 at 5:21:35 PM GMT+1
> To: Pharo Development List <pharo-dev(a)lists.pharo.org>
> Reply-To: Pharo Development List <pharo-dev(a)lists.pharo.org>
>
> Apparently it does not recognizes variables in a workspace.
> This is really annoying...
>
> Try this:
> var := 5.
> self halt
>
> in the debugger, select var and print it
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I’ve seen that in Pharo 3.0 the #methodDict has been deprecated and Spy (and myself) are actually using it.
I will find a solution for myself, but please fix this in Spy as well.
Cheers,
R
Hi,
I would like to propose as a topic for the following Moose Dojos to focus
on building tools. The challenge is to take an analysis problem and build a
tool to support that problem.
Let me give you some examples:
- Problem: browse the Fame meta-descriptions
- Solution: the Meta Browser
- Problem: browse&search pragmas in Pharo
- Solution: ?
- Problem: ?
- Solution: ?
You got the idea.
We could create demos for these tools and use them as showcases for how
Moose enables such scenarios.
Who is up for the challenge? Would you tackle this at the next Moose Dojo?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I put together a little implementation for traversals. It is inspired by an
original implementation from Mariano. Using DeepTraverser, you can traverse
arbitrary graphs by describing the traversal and by specifying the actions
you want to perform on the nodes and relations.
The code is available in the Moose image as part of the MooseAlgos
subproject, but can also be loaded separately in a Pharo image via:
Gofer new
url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main';
package: ‘ConfigurationOfDeepTraverser’;
load.
(Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment.
Just to give you an idea, here are some representative examples:
Number
deep: #subclasses
do: [:each | Transcript show: each; cr].
Number deepCollect: #subclasses.
Number
deep: #subclasses
collect: #name.
Number
deep: #subclasses
do: [:each | Transcript show: each; cr]
relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show:
to; cr ].
More details about the usages and a little description of the
implementation can be found here:
http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi everyone!
I want to display graphET diagrams in moose finder. All other diagram usages are based on Mondrian builder. Can someone help me to build diagrams with other builder?
Cheers.
Uko
Hi guys,
you will probably hate me after today, but I have one more question.
I’m trying to plot some data that is related to time. By default GraphET (and Roassal) do not support Date as value. Of course I can convert timestamp to seconds from epoch but maybe it would be cool to be able to use just Timestamp. For me it seems that evolution of some metric in time should be quite common.
Does anybody have intention to implement something like this?
Uko
Hi guys!
I want to ask everyone who is developing something important for Roassal-related projects to include your example in easel. For now on there is only some Mondrian and Roassal’s examples. Also Roberto’s tree map builder examples appear when roassal-extras are loaded.
For example GraphET has a lot of examples, but they are not integrated into easel and so it’s not easy to view them. So please, spend a bit more time to make your examples available in roassal easel and so making it easier for others to use your project.
Also my rectangle packing layout example were not transferred to Roassal, can someone please handle that?
Cheers.
Uko
hello,
i just want to report a crash of moose on the OS Windows XP
there the error message :
Sorry but the VM crashed
Exception Code : C0000005
Exception address : 66E4B46D
Current Byte Code : -1
Primitive Index : 117
Crashed in the VM thread
--
View this message in context: http://forum.world.st/crash-of-moose-WinXP-tp4729306.html
Sent from the Moose mailing list archive at Nabble.com.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1028 by chisvasi...(a)gmail.com: the transformation block is not
called correctly
http://code.google.com/p/moose-technology/issues/detail?id=1028
When using a transmission with a transformation block, the transformation
block is not called when creating the presentations. The code bellow will
show a list from 1 to 10 instead of one from 1 to 20:
browser := GLMTabulator new.
browser row: #row.
browser transmit
to: #row;
transformed: [ :anInt | anInt+10 ];
andShow: [ :aComposite :anInt |
aComposite list
display: [ 1 to: anInt ] ].
browser openOn: 10.
The transformation block is only called when populating the port, which
happens after the presentation was created.
This can be fixed by modifying GLMPresentStrategy>>presentations to use the
transformation, but the the block will be called two times.
--
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
I notice that several builds are green, though I added a breaking test to Pharo 3.
That probably means that those builds don't run all of the Pharo tests.
Most builds probably don't need to run all tests (all the time), but it might be
useful to be able to mark tests as integration tests, that are expected to be
run by all downstream builds.
Concrete, every Pharo 3 build that loads Grease should currently be red.
Stephan
Hi guys
I would like to present moose to the students at Prague and I wonder if there are
Moose presentations around. I have some but they are too marketing oriented :)
Usman the ones you did for RIC are the best I have so far.
Stef
Hi,
It seems that lately, the energy equilibrium on this mailing list got
slightly off balance. When most messages get negative, you easily get to
feel down and this gets to show in your work. To bring back the positive
energy, I kindly ask you for a simple thing:
Find one thing you like about Moose, and post as a reply to this message.
The reply can be as succinct or as elaborate as you want. You can even
write a blog post about it. And be specific. Pick something you really like
and let the world know.
And remember this: in an open-source environment, people that appreciate
the work or others have more chances of being served.
Let's see where we are :).
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
baseline17: spec
<version: '0.7-baseline'>
spec for: #'common' do: [
spec blessing: #'baseline'.
spec description: ''.
spec author: 'AlexandreBergel'.
spec timestamp: '9/11/2013 23:34'.
spec repository: 'http://www.smalltalkhub.com/mc/ObjectProfile/Roassal/main'.
spec
package: #Roassal;
package: #RoassalMorphic;
package: #RoassalExtras;
package: #RoassalAthens.
the dependencies between packages are missing.
I really do not like that after I spent 3 days fixing Moose dependencies.
Each project should be clean.
Stef
Hi guys
here at prague we tried to load
- fame
- roassal in Pharo 30
and either the configurations were not published in the right
metarepository or it was not working.
For example roassal configuration loaded from repo 20 did not
work in 3.0 (colorNames problems).
So could you publish configurations that works on 30?
Stef
Hey,
please, pretty please, write class comments. Right now I’m trying to understand how GraphET works and there no class is commented. So I have GETAbstractLineDiagram and 2 subclasses: GETLineDiagram and GETOrdinaryLineDiagram. A I’ve mentioned there are no comments. So I’m wandering what do this classes do. Where is GETUnordinaryLineDiagram or GETExtraordinaryLineDiagram. Is it GETLineDiagram? Is line ordinary or is it a diagram? Of course this are all jokes. But my message is: buy spending only a couple of minutes pet class, you can help a lot of there developers. I’d really appreciate this effort.
Cheers!
Uko