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