Hello,
I have some nodes on a view, and I would like that on ROMouseEnter,
some edges are shown, and on ROMouseLeave they disappear.
My code is a bit complex, but I can recreate the scenario in a script
if you need.
Best regards,
Martin
Hi all!
I am Juraj Kubelka and I am obtained sponsorship from Object Profile company for 4 months. Right now I live in Santiago de Chile and in August 2013 I am going to start PhD program here.
The goal of my 4 months work is to "get rid of Mondrian" from the all Moose tools and replace it with Roassal. Alexandre Bergel posted more specific details about it.
Well, the first I want to ask: Can I obtain access into related Moose repositories on http://smalltalkhub.com? My account is JurajKubelka.
Today I did the first pair-programming with Alexandre Bergel. We added some tests in order to do changes and committed into Moose repositories.
Cheers,
Jura
Hello,
I am trying to arrange two sets of nodes in verticalLineLayout with
Roassal, and within a set, the nodes are arranged in a gridLayout. The
script below allows works fine except that the execution time is too long
when the number of nodes is large and hence I am unable to achieve
multi-layout visualization for large number of nodes.
view := ROMondrianViewBuilder new.
view shape rectangle withoutBorder.
view node:#aaa forIt:[
view shape rectangle.
view nodes: (1 to: 10000).
view gridLayout.
].
view shape rectangle withoutBorder.
view node:#bbb forIt:[
view shape rectangle.
view nodes: (1 to: 1000).
view gridLayout.
].
view verticalLineLayout.
view open
Can you please have a look or could you suggest an alternate solution? I
have created my own custom layout but that is tied to the structure of my
nodes and hence not generic.
tx.
usman
Hi Alex,
Right now, Versionner makes the #development version point to an actual
version, and this breaks the flow in Moose, especially when we commit
something to Roassal. Could you change the behavior such that #development
point to the baseline associated with the current version?
Cheers,
Doru
On Wed, Mar 20, 2013 at 3:32 PM, Alexandre Bergel
<alexandre.bergel(a)me.com>wrote:
> Yep, it is part of 1.287.
>
> Thanks Doru!
>
> Alexandre
>
>
> On Mar 20, 2013, at 5:13 AM, Dennis Schenk <d.schenk(a)students.unibe.ch>
> wrote:
>
> > Hi Alexandre,
> >
> > Just saw that Tudor already did what I suggested. Nevermind then :)
> >
> > Cheers,
> > Dennis
> >
> >
> > On Wed, Mar 20, 2013 at 9:44 AM, Dennis Schenk <
> d.schenk(a)students.unibe.ch> wrote:
> > Hi Alexandre,
> >
> > I think we should remove the test
> testEdgeDrivenLayoutingOfCollectionClass from ROTreeMapLayoutTest, since,
> as you pointed out correctly, it is based on something that can change.
> Meaning if something changes within the Collection class hierarchy, we
> would have to adapt the test, which is not desirable.
> >
> > I would suggest to remove the test. I will think about creating another
> one which tests the special case we had with the collection subclass
> treemap.
> >
> > Cheers,
> > Dennis
> >
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I'm was exploring some methods to build method wrappers and I discovered Spy.
Unfortunately the sample code provided on http://www.moosetechnology.org/tools/Spy does not run.
When you reach this point
> You can simply invoke it with:
>
> | packageSpy |
> packageSpy := DemoTestCoveragePackageSpy runTestAndGatherForPackageNamed: 'Mondrian'.
There is no "DemoTestCoveragePackageSpy" yet.
Afterward this class is defined but still there is no message "runTestAndGatherForPackageNamed".
Any hep would be appreciated.
Thanks in advance,
Roberto
Hi!
In the meantime we have a reliable solution to manage configuration, I have updated http://squeaksource.com/Versionner.html
The two most significant changes are:
- SmalltalkHub is now supported
- Committing a project now produces a stable version (instead of a development) and the most recent baseline is marked as #development.
In the meantime to have Versionner2 around, I worked a bit on Versionner to solve some pressing issues with Moose.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> If you want to use Versionner on Pharo1.4 with SmalltalkHub, there is no problem. You just need to declare an http repository:
> MCHttpRepository
> location: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal/main'
> user: ''
> password: ''
Thanks, it works fine
>> @Christophe: what is needed to have Versionner working on Pharo 2.0.
>
>
> I still have work to be able to edit existing configurations (add packages, projects, ...) but "old" Versionner commands are still there.
> The biggest issue I have with Pharo2 is MetacelloToolBox.
> Metacello have been ported to Pharo2 but not MetacelloTests (despite this, it seems to work quite fine).
> Metacello Toolbox shipped with Pharo2 is not working because it comes from another branch than Metacello core (different behavior, methods missing).
> I planned to work on this point next week with Esteban.
> Once done, I just need to check that we do not have issues with announcements (biggest change for Versionner between pharo 1.4 and 2.0).
>
> To resume, to have the "old" Versionner working, the point is to fix MetacelloToolbox in Pharo2 and check announcements.
> I will see with Esteban if we can start this work earlier (have Metacello tests green in Pharo2, update the toolbox).
> I hope to have good news on this front very soon because I also decided to give up Pharo 1.4 for dev. We have Pharo2 and now Pharo3 on the road, I cannot use anymore on old version.
>
> Is it fine for you?
Yes, it looks like to be okay.
Thanks for this update
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I updated the book with the code that works with the latest Glamour.
Also, if you want to see examples, they already exist in the image. For the GLMMorphPresentation, you have an example here:
GLMBasicExamples>>morphIcons
For further clarifications, you better join the Moose mailing list:
moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Cheers,
Doru
On Mar 28, 2013, at 3:25 PM, Jesus Nuñez <poissonbreaker(a)gmail.com> wrote:
> Hello everyone,
>
> Does anybody have the full definition of GLMMorphPresentation such
> that is usable with Glamour, especifically with the
> GLMCompositePresentation?. Actually the only method it defines is
> #renderGlamorouslyOn:.
>
> On the other hand in my installed version of Glamour, GLMTabulator
> does not have the #using: method and in the monticello repositories
> does not seems to be a version that has it. In Moose Book=>Building
> browsers with Glamour=>custom presentations section
> (http://www.themoosebook.org/book/internals/glamour/presentations/custom),
> it is used for embeed a widget from Morphic. which is exacly what I
> need. If somebody knows the version used in the examples please let me
> know it.
>
> Thanks in advance,
> Jesus Nuñez
>
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
