#perform:withArugments:inSuperclass:
| menu |
menu := MenuMorph new.
menu isMorph. "true"
menu perform: #isMorph withArguments: #() inSuperclass: Morph. "true"
menu perform: #isMorph withArguments: #() inSuperclass: Object."false"
menu perform: #isMorph withArguments: #() inSuperclass: ProtoObjec
You should be able to call super super, as high up as you need to go. At least
you can in VA Smalltalk.
Brad Selfridge
913-269-2385
> On Jan 15, 2017, at 3:42 PM, Hilaire wrote:
>
> Hi,
>
> Is there a way from an instance to access a method situated 2 layers up
> in the class hierarchy?
>
>
I gave a talk at Smalltalks 2016 entitled: "Dangerous Liaisons:
Smalltalk, files, and git"[1] and this thread is a perfect example the
dangers I was thinking about:).
For "history buffs", here's a link for my talk at STIC 2012 entitled
"Practical Git for Smalltalk"[2].
Dale
[1] http://fast.
Hi,
Is there a way from an instance to access a method situated 2 layers up
in the class hierarchy?
A kind of super super.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
For those that lost track of the purpose of this thread let me provide a
summary
The discussion started from the Google Visibility where Sven asked me why I
find the Pharo VCS and Monticello a very problematic implementation
I decided to reply creating a separate thread in order to not hijack the
I created Discord chat channel for this precise reason but it has its own
disadvantages like lack of search facility
I have to agree with Hillary , mailing lists is by far the most efficient
way of solving problems and is not even any slower than the online chat and
far easier for someone to spot
I like interacting with the news group too, including with this mailing
list. I found it very efficient.
Hilaire
Le 15/01/2017 à 09:46, jtuc...@objektfabrik.de a
écrit :
> And that's exactly why I still like the usenet: I can read/answer
> whenever I want, using my mail client (opera, thunderbird
I find these endless git vs monticello discussions confusing and pointless.
Maybe we can hang Q&A list somewhere on pharo website to point to? Because git
is getting increased traction in Pharo, so the same questions and endless
discussions will popup over and over again.
1. Some people here ar
On Sun, Jan 15, 2017 at 6:22 AM, Sean P. DeNigris
wrote:
> Sven Van Caekenberghe-2 wrote
> > so it is not a good idea for an open source project, as I feared.
>
> +1. I was concerned from the beginning that our conversations would get
> more
> fragmented. I rarely have time to check slack and the
On 15/01/17 04:29, itli...@schrievkrom.de wrote:
I also have thought several times that it would be nice to have a SQLite
database holding all sources/packages. How much easier life would be
with that.
That's the core idea of fossil. "GitHub alike in a box" DVCS with
tickets, wiki, web ser
My point exactly.
Currently working with a team of testers, they are very happy with mcz
indeed.
And have no clue of git.
Phil
On Sat, Jan 14, 2017 at 3:57 PM, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:
> Hi,
>
>
> On 14/01/17 06:58, Dimitris Chloupis wrote:
>
> [...]
>
>>
I am also amazed at the number of people not using basic git UI tools, like
"git gui" and "gitk" + mergetool/difftool settings in the git config
(kdiff3, meld, WinMerge, difuse) which make the work of merging so much
easier (e.g. "git difftool" or "git mergetool" on the CLI when one
encounters issu
My reasons to like the legacy/mcz style [D]VCS in Pharo:
1) No fuss in saving things when I am starting something
2) Easy to explain to someone new to Pharo
3) Can use any FTP server as a repo (Useful when in a walled garden)
4) Compatible with the package cache, so I can collect mcz's from variou
> Am 15.01.2017 um 10:29 schrieb "itli...@schrievkrom.de"
> :
>
> I would give you many more "+" - if you wish - for your opinion:
>
>
>
>
> Another point I would like to mention: keep the source code locally or
> at least have an easy
I would give you many more "+" - if you wish - for your opinion:
Another point I would like to mention: keep the source code locally or
at least have an easy option to hold all source code locally.
I've seen so many times, that git or one
On Sat, 14 Jan 2017 10:09:02 +0100, Sven Van Caekenberghe
wrote:
On 14 Jan 2017, at 00:48, Offray Vladimir Luna Cárdenas
wrote:
On STHub, fortunately is live enough to let some of us being productive
without the noise of git in front.
So true.
Let's stop bashing StHub: it works fin
Steph, Sven, Sean and everybody else,
Am 15.01.17 um 09:41 schrieb stepharong:
On Sun, 15 Jan 2017 06:22:59 +0100, Sean P. DeNigris
wrote:
Sven Van Caekenberghe-2 wrote
so it is not a good idea for an open source project, as I feared.
+1. I was concerned from the beginning that our conver
On Sun, 15 Jan 2017 06:22:59 +0100, Sean P. DeNigris
wrote:
Sven Van Caekenberghe-2 wrote
so it is not a good idea for an open source project, as I feared.
+1. I was concerned from the beginning that our conversations would get
more
fragmented. I rarely have time to check slack and the m
18 matches
Mail list logo
