Comment #1 on issue 432 by tu...(a)tudorgirba.com: Popup should appear only
when a certain modifier key is pressed
http://code.google.com/p/moose-technology/issues/detail?id=432
Another option would be to have the rendering happening in another thread.
Updates:
Status: WontFix
Comment #4 on issue 43 by tu...(a)tudorgirba.com: [FAME] add helper methods
for multivalued attributes
http://code.google.com/p/moose-technology/issues/detail?id=43
This issue is too old and it is unlikely it will get addressed.
--
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 912 by chisvasi...(a)gmail.com: Glamour presentations should update
their own actions when receiving GLMPresentationUpdated
http://code.google.com/p/moose-technology/issues/detail?id=912
Right now when a presentation receives GLMPresentationUpdated it does not
update its own actions.
For example bellow is some code to see this behaviour.
When the action from the composite presentation is triggered it updates the
action from the contained presentations but not its action.
Also if there is just one presentation in the composite then, due to how a
composite with one presentation is implemented, it won't update any action.
|browser|
browser := GLMTabulator new.
browser row: #aRow.
browser transmit to: #aRow; andShow: [ :composite |
composite
title: 'Composite';
updateOn: Announcement from: [ browser announcer ];
dynamicActions: [ :list || actions |
actions := OrderedCollection new.
actions add:
((GLMGenericAction new)
action: [ :presentation :model | browser announce: Announcement];
icon: GLMUIThemeExtraIcons glamorousAdd;
title: DateAndTime now asString;
yourself).
actions
].
composite list
title: 'List 1';
updateOn: Announcement from: [ browser announcer ];
dynamicActions: [ :list || actions |
actions := OrderedCollection new.
actions add:
((GLMGenericAction new)
action: [ :presentation :model | browser announce: Announcement];
icon: GLMUIThemeExtraIcons glamorousAdd;
title: DateAndTime now asString;
yourself).
actions
].
composite list
title: 'List 2'].
browser openOn: (1 to: 10)
Status: New
Owner: ----
CC: chisvasi...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Milestone-4.8 Maintainability
New issue 926 by tu...(a)tudorgirba.com: Moose should offer ZeroConf support
for quick installations
http://code.google.com/p/moose-technology/issues/detail?id=926
Moose should offer the same support for quick installations as Pharo does.
--
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 948 by step...(a)stack.nl: mooseNameOn: uses
signatureFromSmalltalkSelector
http://code.google.com/p/moose-technology/issues/detail?id=948
FAMIXMethod mooseNameOn: aStream
has an interesting implementation.
Is there a special reason not to use
the signature when it is defined,
instead of the signatureFromSmalltalkSelector?
Doru wrote:
This is horrible! Indeed, we should use the signature there, and the
signatureFromSmalltalkSelector should disappear (because it should be set
at import time).
4.8 Development
--
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 949 by step...(a)stack.nl: FAMIXMethod isConstructor: aBoolean
ignores the parameter
http://code.google.com/p/moose-technology/issues/detail?id=949
isConstructor: aBoolean
self kind: #constructor
Please fill in the labels with the following information:
* Type-Defect,
* Component-Famix
--
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
What negation is doing in MethodInvocation node? And what negation is doing in the VariableAccessorNode? What type cast is doing in VariableAccessorNode? Why does variable accessor has array? Is't not accessor_s_. Accessor. Only one. Accessor only knows only name of the variable it's accessing and the target of access. During parsing PJVariableAccessorNode is created as part of identifierWithAccessors, primary and selector grammars.
As for me this is madness. Yes, I made some mess to when I created InfixOperation instead of all the additive expressions, multiplicative expressions, etc... But to do it right now you just have to define a new node and create it for a related grammar instead of infix expression node.
I think that right now PetitJava is a bigger mess than it was
Надіслано з iPhone
Hi
I just begin looking after point of optimisation into Roassal and I
there are different points :
- firstly, it is not easy to profile
- it seems that when we move the mouse on the visualisation then it
draws everything each time we move the mouse.
And of course the biggest the visualisation is, the hottest the computer
is to be.
So maybe we should either, only draw the visible things (we must know
what is visible easily),
or we should draw the whole visualisation as a picture (bitmap or svg )
in a buffer and then just navigate in it, and keeping a list of visible
things (not to be drawn but to be checked for interactions).
I think the picture is a good solution (maybe not a perfect one) since
refreshing a picture is fine easier than redrawing the whole
visualisation.
And we should only draw changing elements with another color when
dragging them.
What do you think about that ??
Regards
Mathieu