<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
Hi Hannes,<div><br></div><div>the "AnimMorphicProject" is a thing from the "Animations" package. It has nothing to do with Vivide itself. You would just miss some animations if you run Vivide in a regular MorphicProject. There is no need to have a custom project for Vivide because it is basically a new ToolSet.</div><div><br></div><div>For better understanding the Project concept, I suggest to take a look at SqueakShell:</div><div><code> Installer swa
project: 'SqueakShell';
install: 'SqueakShell'.</code></div><div><code><br></code></div><div><code>Best,</code></div><div><code>Marcel</code></div><div><br></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 05.10.2017 23:29:47 schrieb H. Hirzel <hannes.hirzel@gmail.com>:</p>Hello Marcel
<br>
<br>attached is a screen shot of a 'class outline' of FileList done with
<br>Vivide (the version based on Squeak 5.1, [3]). On the right hand side
<br>is the script you posted earlier today.
<br>
<br>This helps to look at the system in a synoptic using screen estate well.
<br>
<br>Would it be possible to have a preconfigured Vivide version for the
<br>most recent trunk in [3] for finding out about current issues as well?
<br>
<br>Or even better - have Vivide as a loadable project type like what we
<br>are trying to do now with EtoysProject?
<br>
<br>Kind regards
<br>Hannes
<br>
<br>
<br>
<br>On 10/5/17, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:
<br>> Hi, Hannes.
<br>>
<br>> Here is the script that produced the output. Just do-it in a workspace:
<br>>
<br>> {
<br>>
<br>> [:in :out | in do: [:class | out add: {
<br>> #object -> class.
<br>> #text -> (ViLabelService doObject: class).
<br>> #icon -> (ViIconService doObject: class) } ]]
<br>> -> { #isProperty -> true.
<br>> #view -> ViTreeViewExtended }.
<br>>
<br>> [:in :out | in do: [:class | out add: {
<br>> #object -> class.
<br>> #text -> (ViObjectOriginService doObject: class) } ]]
<br>> -> {(#isProperty -> true)}.
<br>>
<br>> [:in :out | in do: [:class | out addAll: class subclasses]].
<br>>
<br>> 1. "reference to the first step"
<br>> } asScript openScriptWith: {StringHolder}.
<br>>
<br>>
<br>> Best,
<br>> Marcel
<br>> Am 05.10.2017 15:55:40 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:
<br>> I am using Vivide [1], whose standard scripts make use of Widgets [2]. There
<br>> are pre-configured Squeak images [3].
<br>>
<br>> Best,
<br>> Marcel
<br>>
<br>> [1] https://github.com/hpi-swa/vivide/ [https://github.com/hpi-swa/vivide/]
<br>> [2] https://github.com/hpi-swa/widgets [https://github.com/hpi-swa/widgets]
<br>> [3] https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/vivide/
<br>> [https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/vivide/]
<br>> Am 05.10.2017 15:50:58 schrieb H. Hirzel <hannes.hirzel@gmail.com>:
<br>> I agree, Marcel. Please, what is this nice tool you have been using
<br>> for the screen shot?
<br>> --Hannes
<br>>
<br><br></hannes.hirzel@gmail.com></marcel.taeumel@hpi.de></marcel.taeumel@hpi.de>
</blockquote>
</div></body>