- Moose-dev - INF Mailman

alert: what happens to the domain moosetechnology.org ?

by Alexandre Bergel

Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 6 months

1
0
0 0

[ANN] [Release] Neptuno, the DBXBrowser

by Guillermo Polito

Hi! We are glad to announce the first stable release of the DBXBrowser, named Neptuno, the last piece in the DBXTalk tools project sponsored by ESUG. *What is this browser?* It is a Glamour based browser which works as a GUI to work with OpenDBX connections. * How does it look like?* I attach a screenshot with a brief look :) *Which databases does it work with?* It is currently working with OpenDBX connectors for: - mysql - postgresql - oracle - sqlite * How should I download it?* I'd like to link to the site here, but it's currently down (and we are working for your happiness :D ), so: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfDBXBrowser'; load. (((Smalltalk at: #ConfigurationOfDBXTools) perform: #project) perform: #version: with: #stable) load: 'Neptuno' *How should I contact the DBXTalk team for feedback, bug reports, questions, or whatever?* The project's mailing list: dbxtalk(a)googlegroups.com The project's issue tracker: http://code.google.com/p/dbxtalk/issues The (currently down) site, with docs and stuff: http://dbxtalk.smallworks.com.ar/ Thanks! The DBXTalk team

13 years, 6 months

2
1
0 0

Glamour trees were not showing icons

by Guillermo Polito

I attach a little changeset with the fix and a screenshot of what I am talking about :). Cheers, Guille

13 years, 6 months

3
2
0 0

dynamic sub browser gets not rendered :/

by Guillermo Polito

Hi! I have a browser where I do something like: browser transmit to: #somePane; andShow: [ :a | a dynamic presentation: [ :some :element | some custom: element buildCustomBrowser ] ] And then, I have implemented #buildCustomBrowser for example as: buildCustomBrowser | browser | browser := GLMTabulator new. browser row: #tables. browser transmit to: #tables; andShow: [ :a | a table title: ('Columns for {1}' format: { table name }); addColumn: (GLMTableColumn new title: 'Column name'; computation: #name); addColumn: (GLMTableColumn new title: 'Null'; computation: [ :column | column nullable asString ]); addColumn: (GLMTableColumn new title: 'Type'; computation: [ :column | column typeName asString ]); addColumn: (GLMTableColumn new title: 'Length'; computation: [ :column | column length asString ]); addColumn: (GLMTableColumn new title: 'Primary Key'; computation: [ :column | column isPrimaryKey asString ]); display: self columns; yourself. ]. ^browser And It does not render the table :(. If I change it to something like: buildCustomBrowser | browser | browser := GLMTablePresentation new. browser title: ('Columns for {1}' format: { table name }); addColumn: (GLMTableColumn new title: 'Column name'; computation: #name); addColumn: (GLMTableColumn new title: 'Null'; computation: [ :column | column nullable asString ]); addColumn: (GLMTableColumn new title: 'Type'; computation: [ :column | column typeName asString ]); addColumn: (GLMTableColumn new title: 'Length'; computation: [ :column | column length asString ]); addColumn: (GLMTableColumn new title: 'Primary Key'; computation: [ :column | column isPrimaryKey asString ]); display: self columns. ^browser It works, but I can't have several presentations for the same object... :( I tried debugging the code, but I get lost and lost a lot of time without figuring anything :(. Is there a way to do this? any workaround? or is it a bug or it is ignorance from my side? Thanks! Guille

13 years, 6 months

2
5
0 0

Re: Coccinelle in Moose

by Usman Bhatti

On Mon, Jan 9, 2012 at 11:24 PM, Julia Lawall <julia.lawall(a)lip6.fr> wrote: > On Mon, 9 Jan 2012, Usman Bhatti wrote: > > For me, it should work without modification....The following method that >> you >> are using should carry out the desired functionality... >> LinearFillColor: #counts within: rules; >> > > Thanks, but I'm not sure to understand. We just got one white box and one > black box. Maybe it will look better with more data? Yes. That is the reason. You can see a gradient of color for nodes with more data. > > > julia > > > LinearFillColor: part should take as a parameter the count of a single >> rule. >> The within: part should take an array that contains all the counts of all >> your rules in the system... >> >> On Mon, Jan 9, 2012 at 4:50 PM, Julia Lawall <julia.lawall(a)lip6.fr> >> wrote: >> I got some help from Damien Cassou, and he wrote the following >> code: >> >> viewRules: rules >> view interaction popupText: [:rule | rule ruleName]. >> view shape rectangle >> linearFillColor: #counts >> within: rules; >> withoutBorder. >> view nodes: rules forEach: [:rule | self viewRule: rule]. >> view verticalLineLayout. >> >> I would like the colors not to be arbitrary, but to vary >> depending on the counts value. For example, for a small value, >> I would like a light color and for a large value I would like a >> dark color. I could for example normalize the values so that >> they are between 0 and 100. Is there an easy way to do this? >> >> thanks, >> julia >> >> >> >>

13 years, 6 months

1
0
0 0

Re: Coccinelle in Moose

by Usman Bhatti

For me, it should work without modification....The following method that you are using should carry out the desired functionality... LinearFillColor: #counts within: rules; LinearFillColor: part should take as a parameter the count of a single rule. The within: part should take an array that contains all the counts of all your rules in the system... On Mon, Jan 9, 2012 at 4:50 PM, Julia Lawall <julia.lawall(a)lip6.fr> wrote: > I got some help from Damien Cassou, and he wrote the following code: > > viewRules: rules > view interaction popupText: [:rule | rule ruleName]. > view shape rectangle > linearFillColor: #counts > within: rules; > withoutBorder. > view nodes: rules forEach: [:rule | self viewRule: rule]. > view verticalLineLayout. > > I would like the colors not to be arbitrary, but to vary depending on the > counts value. For example, for a small value, I would like a light color > and for a large value I would like a dark color. I could for example > normalize the values so that they are between 0 and 100. Is there an easy > way to do this? > > thanks, > julia >

13 years, 6 months

1
0
0 0

Re: Coccinelle in Moose

by Usman Bhatti

You can have a look here for instructions for loading Moose in Linux: http://www.moosetechnology.org/download/4.6 I haven't used it on Linux myself; I am sending this mail to moos-dev list and there are people who are successfully using it on Linux. They may be able to suggest a better solution to the problem. Usman On Sat, Jan 7, 2012 at 8:09 AM, Julia Lawall <julia.lawall(a)lip6.fr> wrote: > I am having lots of problems loading moose on Linux (Ubuntu). The first > three times, it got part of the way through, eg to ConfigurationOfMondrian, > and then it would hang. Now I have tried two more times, and each time it > crashes. The part of the crash dump that was still in my shell buffer is > below. > > But I am not sure to understand how it all works, either. Even if I > succeed to load it once, do I have to keep going through the same process > every time I want to use it? > > It would be nicer if one could go to the package manager of ubuntu and > click on moose and it would download and install itself. We have such a > facility for Coccinelle, actually both a released ubuntu one and one that > we maintain ourselves: > > https://launchpad.net/~npalix/**+archive/coccinelle<https://launchpad.net/~npalix/+archive/coccinelle> > > julia > > > > 0xff779970 M [] in MetacelloGofer(Gofer)>**allResolvedIn: -1177336940: > a(n) MetacelloGofer > 0xff77a194 M [] in Dictionary>at:ifAbsentPut: -1177330664: a(n) Dictionary > 0xff77a1b0 M Dictionary>at:ifAbsent: -1177330664: a(n) Dictionary > 0xff77a1d0 M Dictionary>at:ifAbsentPut: -1177330664: a(n) Dictionary > 0xff77a1f0 M MetacelloGofer(Gofer)>**allResolvedIn: -1177336940: a(n) > MetacelloGofer > 0xff77a214 M [] in MetacelloGofer(Gofer)>**allResolved -1177336940: a(n) > MetacelloGofer > 0xff77a238 M Array(SequenceableCollection)>**do: -1177330788: a(n) Array > 0xff77a258 M MetacelloGofer(Gofer)>**allResolved -1177336940: a(n) > MetacelloGofer > 0xff77a270 M GoferPackageReference(**GoferReference)>**resolveAllWith: > -1177330996: a(n) GoferPackageReference > 0xff77a298 M MetacelloFetchingMCSpecLoader(**MetacelloCommonMCSpecLoader)> > **resolvePackageSpecReferences:**gofer: -1191416520: a(n) > MetacelloFetchingMCSpecLoader > 0xff77a2c0 M [] in MetacelloFetchingMCSpecLoader(** > MetacelloCommonMCSpecLoader)>**retryingResolvePackageSpecRefe**rences:gofer: > -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a2dc M BlockClosure>on:do: -1177337116: a(n) BlockClosure > 0xff77a308 M MetacelloFetchingMCSpecLoader(**MetacelloCommonMCSpecLoader)> > **retryingResolvePackageSpecRefe**rences:gofer: -1191416520: a(n) > MetacelloFetchingMCSpecLoader > 0xff77a348 M [] in MetacelloFetchingMCSpecLoader>**linearLoadPackageSpec:gofer: > -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a364 M [] in MetacelloPharoPlatform>do:**displaying: -1209283404: > a(n) MetacelloPharoPlatform > 0xff77a388 M [] in ProgressInitiationException>**defaultMorphicAction > -1177340728: a(n) ProgressInitiationException > 0xff77a3a4 M BlockClosure>on:do: -1177339480: a(n) BlockClosure > 0xff77a3cc M [] in ProgressInitiationException>**defaultMorphicAction > -1177340728: a(n) ProgressInitiationException > 0xff77a3ec M BlockClosure>ensure: -1177339616: a(n) BlockClosure > 0xff77a410 M ProgressInitiationException>**defaultMorphicAction > -1177340728: a(n) ProgressInitiationException > 0xff77a428 M MorphicUIManager>**progressInitiationExceptionDef**aultAction: > -1214906544: a(n) MorphicUIManager > 0xff77a444 M ProgressInitiationException>**defaultAction -1177340728: > a(n) ProgressInitiationException > 0xff77a460 M UndefinedObject>handleSignal: -1216819196: a(n) > UndefinedObject > 0xff77a480 M MethodContext(ContextPart)>**handleSignal: -1191661348: a(n) > MethodContext > 0xff77a4a0 M MethodContext(ContextPart)>**handleSignal: -1191661440: a(n) > MethodContext > 0xff77a4c0 M MethodContext(ContextPart)>**handleSignal: -1191421700: a(n) > MethodContext > 0xff77a4e0 M MethodContext(ContextPart)>**handleSignal: -1191415972: a(n) > MethodContext > 0xff77a4fc M ProgressInitiationException(**Exception)>signal -1177340728: > a(n) ProgressInitiationException > 0xff77a514 M ProgressInitiationException>**display:at:from:to:during: > -1177340728: a(n) ProgressInitiationException > 0xff77a540 M ProgressInitiationException class>display:at:from:to:**during: > -1214347848: a(n) ProgressInitiationException class > 0xff77a56c M ByteString(String)>**displayProgressAt:from:to:**during: > -1177340876: a(n) ByteString > 0xff77a594 M MetacelloPharoPlatform>do:**displaying: -1209283404: a(n) > MetacelloPharoPlatform > 0xff77a5b4 M MetacelloFetchingMCSpecLoader>**linearLoadPackageSpec:gofer: > -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a5d4 M MetacelloPackageSpec>**loadUsing:gofer: -1191434076: a(n) > MetacelloPackageSpec > 0xff77a600 I [] in MetacelloFetchingMCSpecLoader(** > MetacelloCommonMCSpecLoader)>**linearLoadPackageSpecs:**repositories: > -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a620 M OrderedCollection>do: -1181405472: a(n) OrderedCollection > 0xff77a648 I MetacelloFetchingMCSpecLoader(**MetacelloCommonMCSpecLoader)> > **linearLoadPackageSpecs:**repositories: -1191416520: a(n) > MetacelloFetchingMCSpecLoader > 0xff77a678 I [] in MetacelloFetchingMCSpecLoader>**atomicLoadPackageSpecs: > **repositories: -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a698 M BlockClosure>ensure: -1181404712: a(n) BlockClosure > 0xff77a6c0 I MetacelloLoaderPolicy>**pushLoadDirective:during: > -1191426384: a(n) MetacelloLoaderPolicy > 0xff77a6e8 I MetacelloLoaderPolicy>**pushAtomicLoadDirectivesDuring**:for: > -1191426384: a(n) MetacelloLoaderPolicy > 0xff77a710 I MetacelloFetchingMCSpecLoader>**atomicLoadPackageSpecs:**repositories: > -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a73c I MetacelloFetchingMCSpecLoader(**MetacelloCommonMCSpecLoader)> > **load -1191416520: a(n) MetacelloFetchingMCSpecLoader > 0xff77a760 I MetacelloMCVersionSpecLoader>**load -1191421484: a(n) > MetacelloMCVersionSpecLoader > 0xff77a788 I MetacelloMCVersion>**executeLoadFromArray: -1191567612: a(n) > MetacelloMCVersion > 0xff77a7a8 M [] in MetacelloMCVersion>**fetchRequiredFromArray: > -1191567612: a(n) MetacelloMCVersion > 0xff77a7cc M [] in MetacelloPharoPlatform(**MetacelloPlatform)>** > useStackCacheDuring:**defaultDictionary: -1209283404: a(n) > MetacelloPharoPlatform > 0xff77a7e8 M BlockClosure>on:do: -1191421608: a(n) BlockClosure > 0xff77a80c M MetacelloPharoPlatform(**MetacelloPlatform)>** > useStackCacheDuring:**defaultDictionary: -1209283404: a(n) > MetacelloPharoPlatform > 0xff77a834 M [] in MetacelloMCVersion>**fetchRequiredFromArray: > -1191567612: a(n) MetacelloMCVersion > 0xff77a854 M BlockClosure>ensure: -1191421988: a(n) BlockClosure > 0xff77a884 I [] in MetacelloMCVersion>**fetchRequiredFromArray: > -1191567612: a(n) MetacelloMCVersion > 0xff77a8a8 I [] in MetacelloPharoPlatform>do:**displaying: -1209283404: > a(n) MetacelloPharoPlatform > 0xff77a8cc M [] in ProgressInitiationException>**defaultMorphicAction > -1191423164: a(n) ProgressInitiationException > 0xff77a8e8 M BlockClosure>on:do: -1191422124: a(n) BlockClosure > 0xff77a910 M [] in ProgressInitiationException>**defaultMorphicAction > -1191423164: a(n) ProgressInitiationException > 0xff77a930 M BlockClosure>ensure: -1191422260: a(n) BlockClosure > 0xff77a954 M ProgressInitiationException>**defaultMorphicAction > -1191423164: a(n) ProgressInitiationException > 0xff77a96c M MorphicUIManager>**progressInitiationExceptionDef**aultAction: > -1214906544: a(n) MorphicUIManager > 0xff777208 M ProgressInitiationException>**defaultAction -1191423164: > a(n) ProgressInitiationException > 0xff777224 M UndefinedObject>handleSignal: -1216819196: a(n) > UndefinedObject > 0xff777244 M MethodContext(ContextPart)>**handleSignal: -1191661348: a(n) > MethodContext > 0xff777264 M MethodContext(ContextPart)>**handleSignal: -1191661440: a(n) > MethodContext > 0xff777280 M ProgressInitiationException(**Exception)>signal -1191423164: > a(n) ProgressInitiationException > 0xff777298 M ProgressInitiationException>**display:at:from:to:during: > -1191423164: a(n) ProgressInitiationException > 0xff7772c4 M ProgressInitiationException class>display:at:from:to:**during: > -1214347848: a(n) ProgressInitiationException class > 0xff7772f0 M ByteString(String)>**displayProgressAt:from:to:**during: > -1191423444: a(n) ByteString > 0xff777320 I MetacelloPharoPlatform>do:**displaying: -1209283404: a(n) > MetacelloPharoPlatform > 0xff777354 I MetacelloMCVersion>**fetchRequiredFromArray: -1191567612: > a(n) MetacelloMCVersion > 0xff777384 I [] in MetacelloMCVersion>**doLoadRequiredFromArray: > -1191567612: a(n) MetacelloMCVersion > 0xff7773a4 M BlockClosure>ensure: -1191426180: a(n) BlockClosure > 0xff7773d4 I MetacelloMCVersion>**doLoadRequiredFromArray: -1191567612: > a(n) MetacelloMCVersion > 0xff7773f8 I MetacelloMCVersion>load -1191567612: a(n) MetacelloMCVersion > 0xff777410 M ConfigurationOfMoose class>loadDefault -1191864456: a(n) > ConfigurationOfMoose class > 0xff777428 M UndefinedObject>? -1216819196: a(n) UndefinedObject > 0xff777460 I Compiler>evaluate:in:to:**notifying:ifFail:logged: > -1191664976: a(n) Compiler > 0xff7774a0 I [] in SmalltalkEditor>**evaluateSelectionAndDo: -1191674848: > a(n) SmalltalkEditor > 0xff7774bc M BlockClosure>on:do: -1191665020: a(n) BlockClosure > 0xff7774f0 I SmalltalkEditor>**evaluateSelectionAndDo: -1191674848: a(n) > SmalltalkEditor > 0xff777514 I SmalltalkEditor>**evaluateSelection -1191674848: a(n) > SmalltalkEditor > 0xff77752c M [] in PluggableTextMorph>doIt -1191989900: a(n) > PluggableTextMorph > 0xff777554 I [] in PluggableTextMorph>handleEdit: -1191989900: a(n) > PluggableTextMorph > 0xff777574 I TextMorphForEditView(**TextMorph)>handleEdit: -1191988544: > a(n) TextMorphForEditView > 0xff77759c I PluggableTextMorph>handleEdit: -1191989900: a(n) > PluggableTextMorph > 0xff7775b8 M PluggableTextMorph>doIt -1191989900: a(n) PluggableTextMorph > 0xff7775d0 M Workspace(StringHolder)>**perform:orSendTo: -1192006832: > a(n) Workspace > 0xff777600 I [] in ToggleMenuItemMorph(**MenuItemMorph)>**invokeWithEvent: > -1191672980: a(n) ToggleMenuItemMorph > 0xff777620 M BlockClosure>ensure: -1191665696: a(n) BlockClosure > 0xff777648 I CursorWithMask(Cursor)>**showWhile: -1214866608: a(n) > CursorWithMask > 0xff777670 I ToggleMenuItemMorph(**MenuItemMorph)>**invokeWithEvent: > -1191672980: a(n) ToggleMenuItemMorph > 0xff777694 I ToggleMenuItemMorph(**MenuItemMorph)>mouseUp: -1191672980: > a(n) ToggleMenuItemMorph > 0xff7776b0 M ToggleMenuItemMorph(**MenuItemMorph)>handleMouseUp: > -1191672980: a(n) ToggleMenuItemMorph > 0xff7776cc M MouseButtonEvent>sentTo: -1191666012: a(n) MouseButtonEvent > 0xff7776e8 M ToggleMenuItemMorph(Morph)>**handleEvent: -1191672980: a(n) > ToggleMenuItemMorph > 0xff777718 M MorphicEventDispatcher>**dispatchDefault:with: -1191666028: > a(n) MorphicEventDispatcher > 0xff777738 M MorphicEventDispatcher>**dispatchEvent:with: -1191666028: > a(n) MorphicEventDispatcher > 0xff777758 M ToggleMenuItemMorph(Morph)>**processEvent:using: > -1191672980: a(n) ToggleMenuItemMorph > 0xff77778c M MorphicEventDispatcher>**dispatchDefault:with: -1191666028: > a(n) MorphicEventDispatcher > 0xff7777ac M MorphicEventDispatcher>**dispatchEvent:with: -1191666028: > a(n) MorphicEventDispatcher > 0xff7777cc M MenuMorph(Morph)>processEvent:**using: -1191673548: a(n) > MenuMorph > 0xff7777ec M MenuMorph(Morph)>processEvent: -1191673548: a(n) MenuMorph > 0xff777808 M MenuMorph>handleFocusEvent: -1191673548: a(n) MenuMorph > 0xff777830 M [] in HandMorph>sendFocusEvent:to:**clear: -1215573028: a(n) > HandMorph > 0xff77784c M [] in PasteUpMorph>**becomeActiveDuring: -1215123516: a(n) > PasteUpMorph > 0xff777868 M BlockClosure>on:do: -1191666124: a(n) BlockClosure > 0xff777894 M PasteUpMorph>**becomeActiveDuring: -1215123516: a(n) > PasteUpMorph > 0xff7778b8 M HandMorph>sendFocusEvent:to:**clear: -1215573028: a(n) > HandMorph > 0xff7778e0 M HandMorph>sendEvent:focus:**clear: -1215573028: a(n) > HandMorph > 0xff777904 M HandMorph>sendMouseEvent: -1215573028: a(n) HandMorph > 0xff777928 M HandMorph>handleEvent: -1215573028: a(n) HandMorph > 0xff777954 M HandMorph>processEvents -1215573028: a(n) HandMorph > 0xff77796c M [] in WorldState>doOneCycleNowFor: -1214958408: a(n) > WorldState > 0xff7713ac M Array(SequenceableCollection)>**do: -1216805840: a(n) Array > 0xff7713c8 M WorldState>handsDo: -1214958408: a(n) WorldState > 0xff7713e4 M WorldState>doOneCycleNowFor: -1214958408: a(n) WorldState > 0xff771400 M WorldState>doOneCycleFor: -1214958408: a(n) WorldState > 0xff771420 M WorldState>doOneSubCycleFor: -1214958408: a(n) WorldState > 0xff77143c M PasteUpMorph>doOneSubCycle -1215123516: a(n) PasteUpMorph > 0xff771464 I MenuMorph>invokeModalAt:in:**allowKeyboard: -1191673548: > a(n) MenuMorph > 0xff771490 I MenuMorph>invokeModal: -1191673548: a(n) MenuMorph > 0xff7714b4 I MenuMorph>invokeModal -1191673548: a(n) MenuMorph > 0xff7714d8 I PluggableTextMorph>**yellowButtonActivity: -1191989900: a(n) > PluggableTextMorph > 0xff7714f8 M TextMorphForEditView>**mouseDown: -1191988544: a(n) > TextMorphForEditView > 0xff771514 M TextMorphForEditView(Morph)>**handleMouseDown: -1191988544: > a(n) TextMorphForEditView > 0xff771530 M MouseButtonEvent>sentTo: -1191673604: a(n) MouseButtonEvent > 0xff77154c M TextMorphForEditView(Morph)>**handleEvent: -1191988544: a(n) > TextMorphForEditView > 0xff771588 M MorphicEventDispatcher>**dispatchMouseDown:with: > -1191673752: a(n) MorphicEventDispatcher > 0xff7715a8 M MorphicEventDispatcher>**dispatchEvent:with: -1191673752: > a(n) MorphicEventDispatcher > 0xff7715c8 M TextMorphForEditView(Morph)>**processEvent:using: > -1191988544: a(n) TextMorphForEditView > 0xff771608 M MorphicEventDispatcher>**dispatchMouseDown:with: > -1191673752: a(n) MorphicEventDispatcher > 0xff771628 M MorphicEventDispatcher>**dispatchEvent:with: -1191673752: > a(n) MorphicEventDispatcher > 0xff771648 M TransformMorph(Morph)>**processEvent:using: -1191989012: > a(n) TransformMorph > 0xff771688 M MorphicEventDispatcher>**dispatchMouseDown:with: > -1191673752: a(n) MorphicEventDispatcher > 0xff7716a8 M MorphicEventDispatcher>**dispatchEvent:with: -1191673752: > a(n) MorphicEventDispatcher > 0xff7716c8 M PluggableTextMorph(Morph)>**processEvent:using: -1191989900: > a(n) PluggableTextMorph > 0xff771708 M MorphicEventDispatcher>**dispatchMouseDown:with: > -1191673752: a(n) MorphicEventDispatcher > 0xff771728 M MorphicEventDispatcher>**dispatchEvent:with: -1191673752: > a(n) MorphicEventDispatcher > 0xff771748 M SystemWindow(Morph)>**processEvent:using: -1192006784: a(n) > SystemWindow > 0xff771788 M MorphicEventDispatcher>**dispatchMouseDown:with: > -1191673752: a(n) MorphicEventDispatcher > 0xff7717a8 M MorphicEventDispatcher>**dispatchEvent:with: -1191673752: > a(n) MorphicEventDispatcher > 0xff7717c8 M PasteUpMorph(Morph)>**processEvent:using: -1215123516: a(n) > PasteUpMorph > 0xff7717f0 M PasteUpMorph>processEvent:**using: -1215123516: a(n) > PasteUpMorph > 0xff771810 M PasteUpMorph(Morph)>**processEvent: -1215123516: a(n) > PasteUpMorph > 0xff771830 M HandMorph>sendEvent:focus:**clear: -1215573028: a(n) > HandMorph > 0xff771854 M HandMorph>sendMouseEvent: -1215573028: a(n) HandMorph > 0xff771878 M HandMorph>handleEvent: -1215573028: a(n) HandMorph > 0xff7718a4 M HandMorph>processEvents -1215573028: a(n) HandMorph > 0xff7718bc M [] in WorldState>doOneCycleNowFor: -1214958408: a(n) > WorldState > 0xff7718e0 M Array(SequenceableCollection)>**do: -1216805840: a(n) Array > 0xff7718fc M WorldState>handsDo: -1214958408: a(n) WorldState > 0xff771918 M WorldState>doOneCycleNowFor: -1214958408: a(n) WorldState > 0xff771934 M WorldState>doOneCycleFor: -1214958408: a(n) WorldState > 0xff771950 M PasteUpMorph>doOneCycle -1215123516: a(n) PasteUpMorph > 0xff771970 I [] in Project class>? -1214722400: a(n) Project class > -1214675564 s [] in BlockClosure>? > > Most recent primitives > basicNew: > replaceFrom:to:with:**startingAt: > basicNew > basicNew: > basicNew > species > basicNew: > replaceFrom:to:with:**startingAt: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > at:put: > basicNew: > basicNew > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > basicNew > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > basicNew > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > basicNew > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > basicNew > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > basicNew > basicNew > basicNew: > atAllPut: > at:put: > at:put: > findFirstInString:inSet:**startingAt: > species > basicNew: > replaceFrom:to:with:**startingAt: > basicNew: > replaceFrom:to:with:**startingAt: > replaceFrom:to:with:**startingAt: > shallowCopy > translate:from:to:table: > shallowCopy > basicNew > new: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > shallowCopy > new: > replaceFrom:to:with:**startingAt: > at:put: > at:put: > at:put: > shallowCopy > at:put: > at:put: > at:put: > new: > replaceFrom:to:with:**startingAt: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > shallowCopy > at:put: > shallowCopy > compare:with:collated: > compare:with:collated: > shallowCopy > shallowCopy > compare:with:collated: > compare:with:collated: > compare:with:collated: > shallowCopy > Abort > pl-59034:Pharo-1.3-13315-**OneClick.app: > > > > > > > > > > > On Fri, 6 Jan 2012, Usman Bhatti wrote: > > Hi Julia, >> >> As discussed, I am sending you the link to the repo where I uploaded the >> source code that we worked on today. >> Here you can get the latest moose image. >> http://ci.moosetechnology.org/**job/moose-latest-dev/<http://ci.moosetechnology.org/job/moose-latest-dev/> >> >> open a workspace and evaluate this code: >> >> Gofer new >> url: 'http://www.squeaksource.com/**Coccinelle<http://www.squeaksource.com/Coccinelle> >> '; >> package: 'Coccinelle'; >> load. >> >> Once the above code executed, you can start the visualization by executing >> the following command. >> >> CoccinelleEntries new showMaps >> >> bon weekend, >> >> Usman >> >> >>

13 years, 6 months

4
3
0 0

Glamour - width of a GLMTableColumn

by Andre Hora

Hello, The code below works fine, but I am not sure if it is correct way. Is there another way to change the width of a GLMTableColumn? | finder d | finder := GLMFinder new. d := finder table display: [ :x | x lines ]. d addColumn: (GLMTableColumn new title: 'v.'; computation: [ :e | '999']; width: 30). d addColumn: (GLMTableColumn new title: 'aut.'; computation: [ :e | 'anAuthor']; width: 70). d addColumn: (GLMTableColumn new title: 'code'; computation: #asString ). finder openOn: (Date>>#addMonths:) getSource thanks! -- Andre Hora

13 years, 6 months

1
0
0 0

Re: Coccinelle in Moose

by Usman Bhatti

It seems that one needs to follow the instructions given on moose website to correctly startup moose on Linux/Ubunto. On Sat, Jan 7, 2012 at 11:07 AM, Julia Lawall <julia.lawall(a)lip6.fr> wrote: > On Sat, 7 Jan 2012, Usman Bhatti wrote: > > You can have a look here for instructions for loading Moose in >> Linux:http://www.**moosetechnology.org/download/**4.6<http://www.moosetechnology.org/download/4.6> >> > > Thanks. I was just going through pharo. > > > I haven't used it on Linux myself; I am sending this mail to moos-dev list >> and there are people who are successfully using it on Linux. They may be >> able to suggest a better solution to the problem. >> > > Thanks! That seems to start up as it should :) > > julia >

13 years, 6 months

1
0
0 0

Table Rendered does not put horizontal scrollbar

by Guillermo Polito

Hi Doru! GLMMorphicListingRendered>>treeMorphFor:and: Which is the method that renders a table, hehe, only puts a vertical scrollbar: treeMorphFor: tmpTreeModel and: aPresentation | tmpTreeMorph columns | tmpTreeMorph := MorphTreeMorph new. tmpTreeMorph makeLastColumnUnbounded; doubleClickSelector: #onDoubleClick; getMenuSelector: #menu:shifted:; keystrokeActionSelector: #keyStroke:from:; cornerStyle: tmpTreeMorph preferredCornerStyle; borderStyle: (BorderStyle inset width: 1); autoDeselection: aPresentation allowsDeselection; hResizing: #spaceFill; vResizing: #spaceFill; layoutFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 1)). columns := aPresentation columns isEmpty ifTrue: [ OrderedCollection with: (MorphTreeColumn new rowMorphGetSelector: #elementColumn)] ifFalse: [ aPresentation columns collect: [:each | GLMMorphTreeColumn new startWidth: each width; glamourColumn: each; headerButtonLabel: (aPresentation titleValueOfColumn: each) font: StandardFonts menuFont target: nil actionSelector: nil arguments: #(); yourself ]. ]. tmpTreeMorph preferedPaneColor: Color white; model: tmpTreeModel; nodeListSelector: #roots; columns: columns. aPresentation isMultiple ifTrue: [tmpTreeMorph beMultiple] ifFalse: [tmpTreeMorph beSingle]. tmpTreeModel chunkSize: aPresentation amountToShow. * tmpTreeMorph vShowScrollBar.* ^ tmpTreeMorph buildContents And if you have a large table with many columns, you can't scroll to the rightest end. I've changed that line by tmpTreeMorph showScrollBars. and the list and tree examples looks still ok. Thanks, Guille

13 years, 6 months

2
3
0 0

Re: Glamour: how to do 'A transmit to B' & 'B transmit to A'

by Cesar Couto

My name is Cesar Couto and I am working with Nicolas Anquetil at INRIA. I think this code just works with list, but it does not work mondrian painting. Look this simple code using mondrian: |browser| browser := GLMTabulator new. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | a mondrian painting: [ :view :bug | view shape label. view node: 'one'. view shape rectangle. view node:1 ] ]. browser transmit to: #two; andShow: [ :a | a mondrian painting: [ :view :bug | view shape label. view node: 'two'. view shape rectangle. view node:2 ] ]. browser transmit from: #one; to: #two port: #selection; andShow: [ :a | a mondrian title: [ :entity | 'one clicked']; painting: [ :view :class | view shape label. view node: 'one clicked'. view shape rectangle. view node:3 ]]. browser transmit from: #two; to: #one port: #selection; andShow: [ :a | a mondrian title: [ :entity | 'two clicked']; painting: [ :view :bug | view shape label. view node: 'two clicked'. view shape rectangle. view node:4]]. browser openOn: MooseModel root allModels first. Both of the panes open correctly. But when I click on the entities in one pane, the other pane turn gray and nothing happens. What do you think? Cesar Couto -- http://www.decom.cefetmg.br/cesar

13 years, 6 months

4
7
0 0

Glamour Accordion arrangement

by Guillermo Polito

Hi! Mainly to Doru I think, How difficult is to have horizontal Accordion arrangement in glamour? I've hacked a bit in adding the commented lines: GLMMorphicAccordionRenderer>>render: aPresentation | presentations container expander | presentations := aPresentation matchingPresentations. presentations isEmpty ifTrue: [ ^ GLMMorphic emptyMorph ]. presentations size = 1 ifTrue: [ ^ self renderWithToolbar: presentations first ]. container := GLMMorphic containerMorph. container changeTableLayout. * "container listDirection: #leftToRight."* presentations do: [ :each | expander := self theme newExpanderIn: container label: (self titleOrIconOf: each in: container) forAll: {(self renderWithToolbar: each)}. * "expander listDirection: #leftToRight."* container addMorphBack: expander. (aPresentation pane lastActivePresentation notNil and: [ each title = aPresentation pane lastActivePresentation title ]) ifTrue: [ expander expanded: true]]. (aPresentation pane lastActivePresentation isNil and: [container submorphs notEmpty]) ifTrue: [ container submorphs first expanded: true]. ^ container But the expanders just look ugly ugly :) Other IDEs, when you collapse a widget just keep an icon without the label. Should I open an issue? Guille

13 years, 6 months

2
1
0 0

Accordion arrangement as panes

by Guillermo Polito

Hi Doru! In the Glamour examples, the accordion arrangement has declared inside of it two presentations: a list and a text. I want to treat them as single panes but I don't think glamour as it is allows me :(. In other words, can I arrange panes as an accordion? Thank you very much :) Guille

13 years, 6 months

2
1
0 0

Issue 770 in moose-technology: Updateable GLMBasicExamples throwing an error

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium New issue 770 by sean.p.d...(a)gmail.com: Updateable GLMBasicExamples throwing an error http://code.google.com/p/moose-technology/issues/detail?id=770 From the example browser (GLMBasicExamples open), when I click on '+' in either "Updateable browser" or "Updateable individual presentations", I get "Error: Instances of Pragma are not indexable"

13 years, 6 months

1
2
0 0

Glamour: how to do 'A transmit to B' & 'B transmit to A'

by Nicolas Anquetil

Hi folks, Happy new year to you all. I have a question in Glamour: We want a browser with two panes: browser row: [ :row | row column: #classmap; column: #bugmap]. the two panes show two point of view on the same thing. When we select something in #classmap we want too highlight something related in #bugmap browser transmit from: #classmap; to: #bugmap; The reverse is true to: browser transmit from: #bugmap; to: #classmap; It works somehow: we can open the browser and click on one side (either one) to update the other side. The problem is that if we start selecting in one side, then we can only select on this side, selecting on the other side blanks everything and we need to restart the whole browser. - Is this a know issue? - with a known solution? - do you need more code? nicolas -- Nicolas Anquetil -- RMod team INRIA Lille Nord Europe

13 years, 6 months

2
1
0 0

Issue 766 in moose-technology: Book: Use Action list presentation example from GLMBasicExamples

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 766 by sean.p.d...(a)gmail.com: Book: Use Action list presentation example from GLMBasicExamples http://code.google.com/p/moose-technology/issues/detail?id=766 On http://www.themoosebook.org/book/internals/glamour/presentations/action-list You could use the example from GLMBasicExamples: | browser | browser := GLMTabulator new. browser column: #one. browser transmit to: #one; andShow: [ :a | a actionList act: [:entity | entity inspect ] entitled: 'Inspect'; act: [:entity | entity explore ] entitled: 'Explore']. ^ browser openOn: #(1 2 3)

13 years, 6 months

1
1
0 0

Re: Mondrian: popup view on edges

by Alexandre Bergel

Thanks Veronica! This is now in Mondrian 2.142 2.143 is now open for contribution Cheers, Alexandre On 3 Jan 2012, at 10:45, Veronica Isabel Uquillas Gomez wrote: > Hi Alex, > > It seems that i forgot to publish this addition (included an example). > > > Name: Mondrian-Pharo-Morphic-VeronicaUquillas.31 > Author: VeronicaUquillas > Time: 3 January 2012, 2:43:11 pm > UUID: 2ce71ab8-8611-4160-a8b7-a01e57ae7e9b > Ancestors: Mondrian-Pharo-Morphic-AlexandreBergel.30 > > edges can also show a popup view > > > Cheers, > Veronica > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 6 months

1
0
0 0

Re: Issue 322 in moose-technology: Add status bar to MOBrowser and MOEasel

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #9 on issue 322 by tudor.gi...(a)gmail.com: Add status bar to MOBrowser and MOEasel http://code.google.com/p/moose-technology/issues/detail?id=322 (No comment was entered for this change.)

13 years, 6 months

1
4
0 0

Issue 499 in moose-technology: Port & transmission in Mondrian

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Mondrian New issue 499 by alexandr...(a)gmail.com: Port & transmission in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=499 Hi Alex, -=-=-=-=-= Previous discussion: What we did in Glamour was to attach to each Presentation a kind of default interaction. In your example, I would make #mouseEnter, #mouseClick ... default ports that are populated when the corresponding interactions happen on a graph element. Then of course, these ports will belong to graph elements. Like this transmissions are created between the ports of a graph element. Perhaps there will also be a need to identify graph elements by name so that you can refer to them from outside the context of a script. -=-=-=-=-= Previous discussion: Why not having ports that belong to an interaction instead? Consider the following script: view nodes: (1 to: 1000). Figure selection will imply a transmission between the root and each of these nodes. It could be a single transmission between 'root interaction' and the unique interaction of the nodes? -=-=-=-=-= Doru answer: At least two reasons. First, the ports are not just for transmitting information, but ports also allow you to store arbitrary values that model the graph element, and thus you can model the state of a visualization (including side-effects). Second, using ports you will be able to let the shape populate ports by default without writing any explicit interaction (only write transmission when you want to deal with them). Now, about we can be smart about transmissions and do what we do for shapes: we share the object between multiple graph elements. For this, we will just need a lookup of the origins instead of hardcoding them. Actually in Glamour, we have: GLMTransmission>>originatesAt: aPort and thus, you can have a smart transmission that performs a more complex check by checking if the port is part of any elements from a collection. Like this you will have only one the transmission object. You could write: view nodes: #(1 2 3) labeled: #interestingNodes. view nodes: #(5 6 7) labeled: #otherNodes. view transmitTo: #otherNodes fromAny: #interestingNodes port: #selection. Cheers, Doru

13 years, 6 months

1
2
0 0

adding checkbox in glamour status bar

by Usman Bhatti

I am trying to add a checkbox in the glamour status bar for allowing user to change the type of interaction with a visualization. I've seen different glamour examples but most are about adding lists, buttons and dropdown lists. My question: Is there an easy way to add a checkbox in the status bar of the GLMTabulator? I have a (not so elegant) solution that allows toggling for the moment. browser := GLMTabulator withStatusbar. browser column: #painting. browser act: [:b | ((b actions at: 1) title includesSubString: 'Provider') ifTrue: [(b actions at: 1) title: 'Client Dependencies'.] ifFalse: [(b actions at: 1) title: 'Provider Dependencies'] ] entitled: 'Client Dependencies'. browser transmit to: #painting; andShow: [ :a | a mondrian view: self view ]. ^ browser thanx Usman

13 years, 6 months

2
2
0 0

Adding a new partner

by Alexandre Bergel

Hi! Can the following be added to http://www.moosetechnology.org/about/partners Facultad de Ciencias Exactas, Universidad Nacional del Centro de la Provincia de Buenos Aires, Tandil, Argentina http://www.exa.unicen.edu.ar/ Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 6 months

2
2
0 0

Customizing Magritte Morphic Forms

by Sean P. DeNigris

Lukas suggested I repost this here from the Magritte list (http://forum.world.st/Customizing-Magritte-Morphic-Forms-td4251518.html): I'm playing with and already enjoying Magritte after the awesome talk Nick and Esteban gave at ESUG this year. How do I customize Magritte editors in Morphic? Specifically, for the Address example from the Seaside book, I tried: anAddress asMorph addButtons; addWindow; openInWorld. but the fields were really tiny and hid most of the text as you can see below: http://forum.world.st/file/n4251570/PharoScreenshot.2.png Then I tried a standard Morphic approach: | form window | form := anAddress asMorph addButtons. window := SystemWindow new addMorph: form fullFrame: (LayoutFrame fractions: (0@0 corner: 1.0(a)1.0) offsets: (10@10 corner: 10@10)). window openInWorld. but I got "MessageNotUnderstood: MAContainerMorph>>layoutFrame:" -- View this message in context: http://forum.world.st/Customizing-Magritte-Morphic-Forms-tp4251570p4251570.… Sent from the Moose mailing list archive at Nabble.com.

13 years, 6 months

2
5
0 0

Testing Kumpel

by Felipe González

Hi! I am Felipe González a student from Alexandre Bergel. I would like to understand Kumpel and improve it's overall quality. I will be fully working on it for the next two weeks. Here is what I can see in Kumpel: - There's no documentation in the classes nor the tests classes - Almost all test methods hasn't a proper method category - There's almost no class hierarchy - The next classes doesn't have any tests: KMPProjectBuilderConfig KMPProjectLoader KMPImportSVNCommand PPDateParser KMPFileVersion PPProjectInfoParser KMPProjectLoader KMPProjectBuilderConfig KMPProjectBuilder is the largest class, but it is almost not tested. I would like to improve the coverage of Kumpel. Does it makes sense for you to write tests for this class? Like this, I'll learn about Kumpel and hopefully be able to make a useful contribution :) I will put the result of my work in the repository ss3.gemstone.com/ss/CC6403-2011 I will let you know how it goes. Any suggestion? Regards, Felipe -- Felipe González Martínez Estudiante de Ingeniería Civil en Computación Departamento de Ciencias de la Computación Universidad de Chile

13 years, 6 months

3
2
0 0

happy new year

by Tudor Girba

Just that: Happy New Year :) Doru

13 years, 6 months

1
0
0 0

Issue 768 in moose-technology: Dynamic Presentation Example in Pharo 1.3

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 768 by sean.p.d...(a)gmail.com: Dynamic Presentation Example in Pharo 1.3 http://code.google.com/p/moose-technology/issues/detail?id=768 http://www.themoosebook.org/book/internals/glamour/presentations/dynamic I don't know if it was supposed to, but the example didn't work in Pharo 1.3, so I adjusted it | browser | browser := GLMTabulator new. browser title: 'Multi Methods Viewer'. browser column: [:c | c row: #classes; row: #methods]; column: #source. browser transmit to: #classes; andShow: [ :a | a list title: 'Classes'; display: [:model | model allClasses ] ]. browser transmit to: #methods; from: #classes; andShow: [ :a | a list title: [ :class | 'Methods from ', class name ]; beMultiple; display: [ :class | class methods ]; format: [ :class | class selector ] ]. browser transmit to: #source; from: #methods; andShow: [ :a | a dynamic with: [ :some :methods | methods do: [ :each | some text title: each name asString; display: [ each getSource] ]. some stackedArrangement ] ]. browser openOn: Smalltalk.

13 years, 6 months

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev