Dear List,
In the SqueakSource Mondrian repository you will find a new version of
Mondrian. It addresses a number of critical issues. Please, let me
know if you find anything that does not work for you.
Mondrian-Alexandre_Bergel.249
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This version addresses the following issues:
- ISSUE #124 : Double click does not work in Mondrian. Double clicks
may be used as "view interaction on: MOMouseDouble do: [:ann | ... ]"
- ISSUE #121 : Mondrian is now significantly faster. A greater number
of nodes may be displayed now. MOBenchmarks contains a number of
different benchmarks and their progress over the time
- ISSUE #125 : The dependencies on Annoucement and Morphic are now
removed. A new class has been introduced: MOMorphicExtensionInstaller.
In its initialize method, it installs the change set that adds
windowing event notifications. MooseLoader has been updated accordingly.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
If you have OB installed, just doit:
ScriptLoader new installer ss project: 'Mondrian'; install:
'MondrianLoader'. (Smalltalk at: #MondrianLoader) load
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear,
I am extending the FAMIX 2.0 to support the C # language (now in 80%) and
would like to know if there is any API to insert data in the database or
something being developed.
Best regards,
Francisco Rodrigues
Hi
I lost some hours this morning because of this.
When I loaded mouse I got bug in the blinking cursor code.
After investigation I think that I found the problem:
mondrian loads an old version of morphic.
It is really interesting to see that we need different loading
semantics.
first Alex could you republish a new version of morphic for mondrian?
then Gofer should offer a merge possibility
stef
Hola todos,
There is a bit of confusion regarding visibility of structural
entities (at least for me). In some places, we say that a public
entity has a 'public' modifier, and in some other places, we say it is
accessed outside the package/module in which it is defined. I propose
to clear these things up.
In FAMIXNamedEntity, these methods checks for the presence of a
modifier in the method signature, as in:
isPublic
<MSEProperty: #isPublic type: #Boolean>
^ self modifiers includes: #isPublic
In FAMIXFunction, there is:
isPublic
"checker whether I am called outside the module in which I am defined"
^ self receivingInvocations anySatisfy: [:inv |
inv sender parentScope ~~ self parentScope]
I was wondering whether FAMIXNamedEntity>>isPublic and friends cannot
be renamed as #hasPublicModifier ?
In that case, #isPublic and friends will be based upon client accesses.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear List,
Anyone already though about a support in MoosePanel for history?
We could have button that adds a new ModelHistory to the list of
models, and doing a right-click on a MooseModel will enables to do a
addLastVersionForMooseModel: on one of the histories.
Any other item on the wish-list for history support?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I have the impression that Moose introduce a bug in textMorphEditor
Once I load moose I do not have anymore onBlinkCursor in the image.
The semantics of loading should be clear
for moose we should load (erase what was there)
and for component we extend we should have merge (to avoid rollback
to older versions).
Stef
