Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 689 by patrick....(a)gmail.com: DNU in Dependency Brower on an
verveineJ MSE
http://code.google.com/p/moose-technology/issues/detail?id=689
In the Dependency Browser I choose a package and see a correct map of
providers but when I click on the Map of clients tab I get a debug window
with FAMIXParameterizedType(Object)>>doesNotUnderstand:
#potentialReferencingNamespaces.
Expected : Map should update with clients info.
Steps :
Download latest verveineJ and latest Moose.
verveinej.sh on a java source.
Launch moose, import generated MSE.
Select «All model classes», top right menu «Browse > Code with Dependencies»
Dependency Browser open, click Map of clients tab and navigate package tree.
Some entries trigger reported DNU.
May be dependent on generated MSE or Java source parsed ?
Debug log attached.
Attachments:
Debug.log 33.7 KB
Status: Accepted
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com
Labels: Type-Enhancement Priority-Low Component-Glamour
New issue 687 by damien.c...(a)gmail.com: Presentation choice flag
http://code.google.com/p/moose-technology/issues/detail?id=687
A presentation flag could offer presentation parametrization in the
rendering. The parametrization icons would appear vertically on the right
side. For example, a code browser could have two flags on the methods pane:
- show inherited methods (yes/no)
- show traits methods (yes/no)
Hi,
It would be so cool if someone would implement LDA in Pharo. Or at least provide a binding to a library.
And if we are at it, it would also be cool if we would have LSI again.
Anyone? :)
Cheers,
Doru
--
www.tudorgirba.com
"Presenting is storytelling."
Hi,
in the following example, I would like that the transmission from pane
#one to pane #two be triggered when the browser opens. Is it possible?
Thanks
|browser |
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [:x | (1 to: x) + 10 ];
selectedIndex: 2 ].
browser transmit from: #one; to: #two; andShow: [:a |
a list
display: [:x | 1 to: x ]].
browser openOn: 5
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
Hello,
Is there any news about rendering mondrian visualizations using some
javaScript libraries ? (I just remember some examples I saw in the mailing
list, which were cool by the way :))
Status: New
Owner: ----
CC: cy.delau...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Merlin Milestone-4.6
New issue 677 by tu...(a)tudorgirba.com: Merlin should not force round corners
http://code.google.com/p/moose-technology/issues/detail?id=677
Currently, Merlin specifies rounded corners for most morphs. This does not
work well with Pharo UI Themes that specify straight corners, such as the
GLMUITheme used in Moose.
Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium RPackage
New issue 619 by stephane...(a)gmail.com: RPackage should deal with unknown
extensions
http://code.google.com/p/moose-technology/issues/detail?id=619
In MC we have
- AST-Core
- AST-Semantic
but no
- AST-Compiler- whatever
so when we get *AST-Compiler-Overrides..... clearly this is a problem.
We should create a new package with the extension names.
Hello Doru,
How can I create a "history model" using the Hismo meta-model. Lets say that
I have different models (versions) loaded in Moose and I want to create a
Hismo model representing these models (versions).
Is there some automatic way to do that?
thanks!
--
Andre Hora
Hi all,
I'm working with glamour and was wondering if a dynamic stacker would
be a good idea. It's use would be something like this:
|stacker|
stacker := GLMStacker new.
stacker aPane: #methods.
stacker aPane: #classes when: [:obj | obj isKindOf: Class].
The default condition being [:obj | true], a stacker would only
represent the panes for which the condition is true.
What do you think?
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
Status: Accepted
Owner: ----
CC: cy.delau...(a)gmail.com
Labels: Type-Defect Priority-Medium RPackage
New issue 620 by stephane...(a)gmail.com: RPackageOrganizer should have a
better public API for unregistering package
http://code.google.com/p/moose-technology/issues/detail?id=620
in particular one that assembles all the elementary steps
- unregister back pointer (class mapping)
- unregister class extension mapping
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 646 by cy.delau...(a)gmail.com: More readable code for classes
http://code.google.com/p/moose-technology/issues/detail?id=646
In the moose panel, when I browse a class and click on the source code
tab , it shows me a big text with className, attributes and all the method.
Maybe this one could be more readable by separating more 'clearly'
thedifferent parts
Hi,
Currently we have:
FAMIXType>>namespaceScope
^ self container
However, the problem is that we now can have classes and methods as containers. So, I now reimplemented it like:
FAMIXType>>namespaceScope
^ self container
ifNotNil: [ self container namespaceScope ]
In the process I also fixed to use namespaceScope instead of container:
FAMIXMethod>>namespaceScope
^ self parentType namespaceScope
Please let me know if this introduces unwanted effects in your context.
Cheers,
Doru
--
www.tudorgirba.com
"What we can governs what we wish."
Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-EyeSee
New issue 639 by andreho...(a)gmail.com: Remove the border around each bar
http://code.google.com/p/moose-technology/issues/detail?id=639
Add the possibility to remove the border around each bar in a bar diagram.
Hi,
I finally got Metanool reasonably complete. This is a simple mechanism to help you manage annotations while you are performing the analysis. To get an idea about Metanool, you can read about it here:
http://scg.unibe.ch/archive/papers/Brue08b-Metanool.pdf
In the current implementation, Metanool is much simpler and it is embedded in the MooseFinder: you will find it in the pane with a pencil icon for each entity. Essentially, what you can do with this is to add a new meta annotation (using the + button on the top right), and then annotate various entities with this annotation.
There are two modes to work with it:
- when you look at an entity, you directly work with that entity
- when you look at a group, you work with the entities in the group (so not with the group entity)
A short demo video is available here:
http://youtu.be/XxjpgJo14pQ
Cheers,
Doru
--
www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.5
New issue 633 by tu...(a)tudorgirba.com: Closing a morphic tab of an
Accumulator browser, does not populate activeEntity properly
http://code.google.com/p/moose-technology/issues/detail?id=633
How to reproduce:
1. Execute:
browser := GLMBasicExamples new accumulator.
browser openOn: 42.
((browser paneNamed: #one) port: #strongSelection) value: 50.
((browser paneNamed: #one) port: #strongSelection) value: 60.
2. Close the first tab (50)
3. You will get 50 selected on the list to the left (while it should be 60)
Hi Doru,
I'm trying to load bleedingEdge of glamour (to overcome the announcement problem) and something is not going well, it does not loads in Pharo 1.3 nor Pharo 1.4.
How can I load it?
thanks,
Esteban
If you have a few minutes
Funny: http://www.wtfnoway.com/
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: tudor.gi...(a)gmail.com
CC: damien.c...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.6
New issue 685 by tudor.gi...(a)gmail.com: Glamour does not copy the
transmission context properly
http://code.google.com/p/moose-technology/issues/detail?id=685
The following piece of code should display 42 in the lower pane.
finder := GLMFinder new.
finder show: [:a | a list display: [:x | 1 to: x ]].
finder transmit fromOutsidePort: #entity; toOutsidePort: #something.
browser := GLMTabulator new.
browser row: #explorer; row: #details.
browser transmit to: #explorer; andShow: [:a | a custom: finder].
browser transmit from: #explorer port: #something; to: #details; andShow:
[:a | a text ].
browser openOn: 42.
Hi list,
I'm implementing a log viewer, and the usual is to show then newer entries at the bottom of the list.
I got the update mechanism working, but every time the list is updated, it shows the top of the list, even though I was looking at the bottom of the list.
How can I tell a list to show the bottom by default?
Thanks in advance!
PS: Glamour rocks!
Hi Andre,
I reviewed the Hismo changes you committed in your repo. Nice.
Please publish them in the main repository.
Cheers,
Doru
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
Hi,
I would like to create a code browser, where the top pane is a finder which
adds a new pane when some clicks on a class name. The following code works
fine except with interactions like:
1- select a class
2- select a selector of this class
3- select a class in the newly added pane
This tries to display the source code of the class selected in step 3 for
the selector of step 2 (which is wrong because selector of step 2 is only
defined in the class of step 1).
Can somebody help me please? The code is:
|extTabulator finder intTabulator|
intTabulator := GLMTabulator new column: #classes; column: #selectors;
yourself.
intTabulator transmit to: #classes; andShow: [:a | a list title: 'classes';
display: [:class | class allSuperclasses]].
intTabulator transmit from: #classes; to: #selectors; andShow: [:a | a list
title: 'selectors'; display: [:class | class selectors]].
finder := GLMFinder new.
finder custom: intTabulator.
"Makes the finder add an new pane when selecting a class"
intTabulator transmit from: #classes; toOutsidePort: #selection.
extTabulator := GLMTabulator new row: #finder; row: #source; yourself.
extTabulator transmit to: #finder; andShow: [:a | a custom: finder].
"Makes the internet tabulator exports the currently selected selector"
intTabulator transmit from: #selectors; toOutsidePort: #selector.
extTabulator transmit
from: #finder;
from: #finder port: #selector;
to: #source;
andShow: [:a | a text
display: [:class :selector | class name, '>>', selector, String cr,
((class includesSelector: selector)
ifTrue: ['ok']
ifFalse: ['ERROR: class does not have this selector!'])]].
extTabulator openOn: IdentitySet.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular
by not having them." James Iry
Hi Steffen,
I reply to the Moose list (most PP action is going on there), because
other people might be interested as well.
On Wednesday, 20 July 2011, Steffen Märcker <merkste(a)web.de> wrote:
> Hi Lukas,
>
> I've just had a look at PetitParser which seem pretty cool. However, using Visualworks, I wonder whether the visualization tools (e.g. grammar workbench) have been (going to be) portered, too.
The tools are built on Glamour and Mondrian, and likely do not work
with the older versions of these frameworks in VW. I have a similar
problem with older Pharo images that do not support loading Glamour
anymore.
What you could do is to develop the grammars using a Moose image (they
include the grammar workbench) and then export the package.
Lukas
--
Lukas Renggli
www.lukas-renggli.ch