Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 967 by chisvasi...(a)gmail.com: Cannot change the selection index
dynamically in drop down list presentations
http://code.google.com/p/moose-technology/issues/detail?id=967
I am trying to change dynamically selection index of a droplist in Glamour.
But changing the selectedIndex upon selection does not change anything in
the browser. Here is my code:
|browser |
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [:x | 1 to: 12 ];
selectedIndex: 10 ].
browser transmit from: #one; to: #two; andShow: [:a |
a list
display: [:x | 1 to: x ];
selectionAct: [:aPres :each | (browser paneNamed: #one) presentations
first selectedIndex: 1] entitled: 'select in dropList'
].
browser openOn: 1
Populating the pane port with the selected does change the list items but
it does not update the selected value in the dropdown list.
selectionAct: [:aPres :each | ((browser paneNamed: #one) port: #selection)
value: (1)] entitled: 'select in dropList'
].
--
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
ok thanks
Let me know if you need help.
Stef
On Aug 21, 2013, at 8:12 PM, David T. Lewis <lewis(a)mail.msen.com> wrote:
> On Wed, Aug 21, 2013 at 05:30:44PM +0200, St?phane Ducasse wrote:
>> Hi dave
>>
>> Moose needs OSProcess and squeaksource is unstable so I will move OSProcess (except if you want to do it) because
>> we should get our build stable and I should losing teim trying to build moose.
>>
>> So let me know.
>
> Hi Stef,
>
> I will move OSProcess to another server by this weekend at the latest. I
> will move CommandShell also, because I think that you are using PipeableOSProcess
> in the ConfigurationOfOSProcess, and that is in the CommandShell package.
> I'll check the configuration to be sure.
>
> Dave
>
Hi,
I am playing with ROForceBasedLayout, and I just realize that it does not
take into account the size of nodes. That is a pity.
For example, if you execute:
view nodes: (1 to: 100).
view edgesFrom: [ :x | x // 5 ].
view forceBasedLayout
... you get a nice picture.
But, if you execute:
view shape rectangle size: #yourself.
view nodes: (1 to: 100).
view edgesFrom: [ :x | x // 5 ].
view forceBasedLayout
... you get a messy one with overlapping nodes.
Would it be difficult to make the layout react to the size of nodes?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Status: New
Owner: ----
CC: anquetil...(a)gmail.com
Labels: Type-Defect Priority-High Component-VerveineJ
New issue 714 by tudor.gi...(a)gmail.com: VerveineJ does not produce correct
values for classes in annotation instances
http://code.google.com/p/moose-technology/issues/detail?id=714
Take a look at the example below:
@XmlElement(name = "Time", required = true, type = String.class)
protected Date time;
The value of the third attribute of the annotation instance is the actual
source code of the String class. Instead, it should be just the
string 'String.class'.
Ideally, we would get an actual reference, but the string would do for now.
Hello,
I am trying to change dynamically selection index of a droplist in Glamour.
But changing the selectedIndex upon selection does not change anything in
the browser. Here is my code:
|browser |
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [:x | 1 to: 12 ];
selectedIndex: 10 ].
browser transmit from: #one; to: #two; andShow: [:a |
a list
display: [:x | 1 to: x ];
selectionAct: [:aPres :each | (browser paneNamed: #one) presentations first
selectedIndex: 1] entitled: 'select in dropList'
].
browser openOn: 1
Populating the pane port with the selected does change the list items but
it does not update the selected value in the dropdown list.
selectionAct: [:aPres :each | ((browser paneNamed: #one) port: #selection)
value: (1)] entitled: 'select in dropList'
].
Could you suggest how can I update droplist and the list upon the change of
selectedIndex?
tx
Usman
Dear colleagues and friends,
We are happy to announce the First Visualization Contest with Roassal.
What can I win?
- 150 euros, sponsored by ObjectProfile
- a über-cool ObjectProfile T-shirt and some wonderful stickers
- maximum publicity of your work
- a nice award certificate, delivered during ESUG
How can I win?
- you have to produce a visualization with Roassal. You can use the Pharo, VisualWorks or VAST version of Roassal. Here is an example of what we expect http://bit.ly/sunburstDemo
- making a video is mandatory. The video will weight the most in our decision. The video could be of any length and has to include your name and say that is was made (partly or completely) with Roassal. No need to talk, just show off!
- making your code available and easy to install will help you get more points
How can I submit?
- send the links of your video and other material (if needed) to info(a)objectprofile.com Every email you will send to this email will be acknowledged. If you do not receive a 'Ok' from us, it means we haven't read it, in that case send your email again after a few days.
- the deadline for submitting is September 4, 2013
Mini FAQ?
- Is the object-profile team allowed to participate? No
- Should my visualization or code be open source? No need for this, whatever license is fine. However your video should be made public.
- How can I get more information? Just comment on the facebook https://www.facebook.com/ObjectProfile or using Twitter @ObjectProfile or send email to info(a)objectprofile.com
- What I submit twice? Yes, no problem with that
- How will judge the videos? both the esug community and the object profile team. The Esug community will have 30% of the final grade, object profile the remaining 70%
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://ObjectProfile.comhttp://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
The following people have accounts on Moose Jenkins:
anquetil
vincent.blondeau(a)inria.fr
tudor(a)tudorgirba.com
stephane.ducasse(a)inria.fr
yuriy.tymchuk(a)me.com
muhammad.bhatti(a)inria.fr
camille.teruel(a)inria.fr
damien.pollet(a)inria.fr
esteban.lorenzano(a)inria.fr
If others want to join the project, you have to:
- create an account on: https://ci.inria.fr
- ask to join the moose jenkins.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
hi all,
Where do Magritte errors get logged? On Moose tracker or somewhere else?
There is a defect in validation of numbers like 3.48e-5
since Magritte MAStringReader >> visitNumberDescription: only allows a
dash at the start.
I've included the details below just so I don't lose them.
regards -ben
MAStringReader >>visitNumberDescription: aDescription
| contents |
(aDescription label first = $r) ifTrue: [ self haltOnce ].
contents := self contents.
contents isEmpty
ifTrue: [ MAReadError signal ].
(contents occurrencesOf: $-) > 1
ifTrue: [ MAReadError signal ].
(contents indexOf: $-) > 1
ifTrue: [ MAReadError signal ].
"^^^^^"
(contents occurrencesOf: $.) > 1
ifTrue: [ MAReadError signal ].
(contents allSatisfy: [ :each | '+-0123456789.eE' includes: each ])
ifFalse: [ MAReadError signal ].
super visitNumberDescription: aDescription
Hi dave
Moose needs OSProcess and squeaksource is unstable so I will move OSProcess (except if you want to do it) because
we should get our build stable and I should losing teim trying to build moose.
So let me know.
Stef
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Milestone-4.8
New issue 968 by usman.bh...(a)gmail.com: Update droplist presentation
selection index
http://code.google.com/p/moose-technology/issues/detail?id=968
I am trying to change dynamically selection index of a droplist in Glamour.
But changing the selectedIndex upon selection does not change anything in
the browser. Here is my code:
|browser |
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [:x | 1 to: 12 ];
selectedIndex: 10 ].
browser transmit from: #one; to: #two; andShow: [:a |
a list
display: [:x | 1 to: x ];
selectionAct: [:aPres :each | (browser paneNamed: #one) presentations
first selectedIndex: 1] entitled: 'select in dropList'
].
browser openOn: 1
Populating the pane port with the selected does change the list items but
it does not update the selected value in the dropdown list.
selectionAct: [:aPres :each | ((browser paneNamed: #one) port: #selection)
value: (1)] entitled: 'select in dropList'
].
Could you suggest how can I update droplist and the list upon the change of
selectedIndex?
--
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 will soon need to analyze quite some java code at once and I'm already
sure that one Moose image will not be enough for all that code. Therefore I
would like to try to persist the model on a database. Do you have any
pointer to a possible persistence manager/OODBMS/RODBMS to use for that
purpose?
Thanks in advance,
Fabrizio
ROUnhighlightElement and ROHighlightElement classes have been removed from
Roassal so GLMBasicExamples>>roassalWithCustomHighlight should be changed.
Here is the fix that works:
| browser |
browser := GLMTabulator new .
browser
with: [:tabulator |
tabulator column: #index; column: #visualization.
tabulator transmit to: #index; andShow: [:a | a list ].
tabulator transmit to: #visualization; andShowIfNone:[ :a |
a roassal
painting: [:view :collection :roassal |
view shape label.
view interaction on: ROMouseLeftClick do: [:ann | (roassal pane port:
#selection) value: ann element model ].
view nodes: collection.
view gridLayout.
roassal on: GLMContextChanged do: [:ann |
ann property = #selection ifTrue: [
ann oldValue ifNotNil: [
ROBlink unhighlight: (ann presentation view raw elementFromModel: ann
oldValue).
ROBlink
highlight: (ann presentation view raw elementFromModel: ann value)
].
]]]].
tabulator transmit from: #index; to: #visualization port: #selection.
tabulator transmit from: #visualization port: #selection; to: #index port:
#selection.
].
browser openOn: (1 to: 42)
Hi,
In order to start the organization of the MooseDay in Lille, we would like to know, who would be interested in attending and who would like to make a presentation. The idea would be to organize it the first or the second week of October.
Please let us know your interest in the MooseDay in Lille (France).
Thanks in advance.
Anne
Hi Fabrizio,
Moose models are highly interconnected, and the analyzing algorithms tend to touch
a lot of other objects. There is very limited locality of reference, so a RDBMS (or NoSQL)
cannot help you here. You basically would only be swapping in and out objects.
Stephan