Exactly. Like this. The cool thing would be to have at the end of the day: a short description and a little tool. We can have a dedicated repository for this. We can use the same exercises for teaching and consulting purposes as well.Cheers,Doru_______________________________________________On Fri, Dec 13, 2013 at 9:53 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Yes I like the idea of katas.How to display hierarhcy inside packages?view shape rectangle.view nodes: (namespaceGroup reject: [:each | each asString beginsWith: 'java' ]) forEach:[:aNamespace |view shape rectangle fillColor: [:aClass | aClass isAbstract ifTrue: [Color red] ifFalse: [Color blue]].view nodes: aNamespace classes.view edgesFrom: #superclass.view treeLayout].view edgesFrom: #belongsTo.view treeLayoutStefHi,I would like to propose as a topic for the following Moose Dojos to focus on building tools. The challenge is to take an analysis problem and build a tool to support that problem.Let me give you some examples:- Problem: browse the Fame meta-descriptions- Solution: the Meta Browser- Problem: browse&search pragmas in Pharo- Solution: ?- Problem: ?- Solution: ?You got the idea.We could create demos for these tools and use them as showcases for how Moose enables such scenarios.Who is up for the challenge? Would you tackle this at the next Moose Dojo?Cheers,_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--"Every thing has its own flow"
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev