Hi Alex,
Thanks for your answer.
I misunderstood RTStackedDataSet.
To me, it does not do what the doc says ;-)
I want to do exactly that:
c := RTGrapher new.
ds := RTDataSet new.
ds dotShape color: Color red.
ds points: {5@1 . 1@2 . 20@3 . 5@4 }.
ds x: [ :e | e y ].
ds y: [ :e | e x ].
c add: ds
Uppp, I just see this email. Since Abdelghani visits RMoD, I've
discussed with him in person about this topic.
Ring-Ficus is an alternative implementation to Ring (as it is in the Pharo
image). Like Ring, Ficus-Ring provides models that represent system's code
entities, and they are also polym
Hello,
Suppose that you want to show the diff between the source code of two
methods. In the case that both methods are in the same class, and that such
class is present in the system, then no problem: In a DiffModel, one can
set a context to the smalltalk syntax styler and get a nice output.
Dif
Hi!
Well… Building the list of coordinate is not a big deal :-)
{ 5 . 1 . 2 . 5 } withIndexCollect: [ :v :index | v @ index ]
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Jun 17, 20
Hi
For the mooc I have a lecture called Pharo Syntax in a nutshell and I
would love to get a couple of simple examples
that show the syntax but are not totally boring.
I thought about something like
ZnClient new
url: 'http://localhost:8080/books/1';
formAt: 'author' put:
Here are some more
https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0
Maybe for teaching, the example should somehow be familiar, recognisable.
On the other hand, that might be confusing and lead to too many comparisons.
> On 17 Jun 2015, at 21:53, stepharo wrote:
>
> Hi
>
I know ;-)
I just wanted to avoid creating new big collections
#Luc
2015-06-17 21:12 GMT+02:00 Alexandre Bergel :
> Hi!
>
> Well… Building the list of coordinate is not a big deal :-)
> { 5 . 1 . 2 . 5 } withIndexCollect: [ :v :index | v @ index ]
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:
Are there any news?
> On 06 May 2015, at 13:00, Alexandre Bergel wrote:
>
> Apparently moose will soon move to Pharo 5. Maybe next week or so.
>
> Alexandre
>
>
>
>> Le 6 mai 2015 à 04:34, Lusa Nicolas a écrit :
>>
>> Hi,
>>
>> thanks for the quick answer, I'll switch back to pharo4 for
You pointed out indeed a default in Grapher. We will fix this in the future…
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> On Jun 17, 2015, at 6:06 PM, Luc Fabresse wrote:
>
>
Hi,
I would like to describe some additional behavior for objects when they are
interacting with another objects.
The prime example is GTInspector; by default to add presentation you
implement a method with "gtInspectorPresentationOrder:". This is fine if
there is just one method like this, but w
Also the problem with visitor here is that I would need X number of
visitors for each method (GtInspectorVisitor, DisplayBlockVisitor, ...) not
to mention that I would need to have the implementation split among
multiple packages, so it is effectively NxM visitors.
Peter
On Thu, Jun 18, 2015 at 7
Hi Peter,
I am not sure I understand.
Is the worry caused by the fact that when there are multiple gtInspector*
methods then the API would get polluted?
Cheers,
Doru
On Thu, Jun 18, 2015 at 7:35 AM, Peter Uhnák wrote:
> Also the problem with visitor here is that I would need X number of
> v
The worry is caused by the fact that I do not want to pollute the protocol;
this is not just about GTInspector, but also about other classes such as
the TreeModel.
So, imagine following hierarchy; there are some "base" classes and then
unlimited number of packages, each with their own hierarchy.
13 matches
Mail list logo
