Magritte MAStringReader >> visitNumberDescription: validation error for negative exponents
by Ben Coman
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
10 years, 1 month
Mondrian…. :(
by Stéphane Ducasse
ComplexShape strikes back….
This package depends on the following classes:
MONodeShape
MOLayout
MOGraphElement
MOShape
MOShapeSelector
You must resolve these dependencies before you will be able to load these definitions:
MOFormsLayout
but I modified the configurationOfMondrian
baseline29: spec
<version: '2.9-baseline'>
spec for: #'common' do: [
spec blessing: #'baseline'.
…
package: 'Mondrian-Core';
package: 'Mondrian-ComplexShape' with: [ spec requires: 'Mondrian-Shapes' ];
package: 'Mondrian-Layouts' with: [ spec requires: 'Mondrian-Core' ];
package: 'Mondrian-Help';
package: 'Mondrian-Tests' with: [ spec requires: 'HealthReportProducer' ];
package: 'Mondrian-Pharo-Tests' with: [spec requires: 'Mondrian-Tests' ];
package: 'Mondrian-Shapes' with: [ spec requires: 'Mondrian-Core' ];
package: 'Mondrian-Events' with: [ spec requires: 'Mondrian-Core' ];
package: 'Mondrian-Visitor' with: [ spec requires: #('Mondrian-Shapes' 'Mondrian-Pharo-Morphic') ];
package: 'Mondrian-Util';
package: 'Mondrian-Normalizers';
package: 'Mondrian-Example' with: [ spec requires: 'Mondrian-ComplexShape' ];
package: 'Mondrian-ShapeVisitor' with: [ spec requires: 'Mondrian-Shapes' ];
package: 'Mondrian-Pharo-Morphic' with: [ spec requires: 'Mondrian-Core' ];
package: 'Mondrian-FADELayout' with: [ spec requires: 'Mondrian-Core'
].
spec group: 'Tests' with: #('Mondrian-Tests' 'Mondrian-Pharo-Tests' 'CollectionExtensions' 'Mondrian-FADELayout' 'Mondrian-Visitor' 'Mondrian-Example' 'Mondrian-Util' 'Mondrian-Help'). ].
so I do not get it :(
Stef
10 years, 1 month
Moving OSProcess from Squeaksource to smalltalkHub
by Stéphane Ducasse
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
10 years, 1 month
Issue 968 in moose-technology: Update droplist presentation selection index
by moose-technology@googlecode.com
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
10 years, 1 month
persisting moose models
by Fabrizio Perin
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
10 years, 1 month
GLMBasicExamples>>roassalWithCustomHighlight needs update
by Usman Bhatti
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)
10 years, 1 month