<div dir="ltr">Workspaces are great for scripting and exploring ideas etc. And working with already existing objects. It's not so good for developing but very good for other important computing and learning needs.<div><br></div><div>Best,</div><div>Karl</div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 5:55 PM, Chris Muller <span dir="ltr"><<a href="mailto:ma.chris.m@gmail.com" target="_blank">ma.chris.m@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All Jakob had to do was "do it" on:<br>
<br>
myXml := '<SomeElement>.... all kinds of XML ... </SomeElement>'<br>
<br>
He now has access to myXml. Then replace all the text in the<br>
workspace with that from the other workspace. Done.<br>
<br>
I guess I see Workspaces for learning and discovery for newbies.<br>
Short, simple, explorations of syntax and class library.<br>
<br>
Attempting to do work as complex as parsing a large XML is going to<br>
present further challenges above and beyond accessing an object. If<br>
someone feels the need to "link workspaces" they really should stop<br>
and consider just making a class. In fact, I think linked workspaces<br>
would lead a newbie down the wrong path..<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Mar 17, 2016 at 11:28 AM, karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>> wrote:<br>
><br>
><br>
> On Thu, Mar 17, 2016 at 4:39 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
>><br>
>> On Thu, Mar 17, 2016 at 4:58 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>><br>
>> wrote:<br>
>> ><br>
>> > On 17.03.2016, at 01:43, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Wed, Mar 16, 2016 at 11:58 AM, Bert Freudenberg<br>
>> > <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>><br>
>> > wrote:<br>
>> >><br>
>> >><br>
>> >> > On 16.03.2016, at 18:48, marcel.taeumel <<a href="mailto:Marcel.Taeumel@hpi.de">Marcel.Taeumel@hpi.de</a>><br>
>> >> > wrote:<br>
>> >> ><br>
>> >> > Mabye we need a simple way to link bindings across tools. Then, for<br>
>> >> > example,<br>
>> >> > we could simple connect a Workspace window to the text box in the<br>
>> >> > Inspector<br>
>> >> > (resp. Object Explorer) and all would share the same bindings. Then,<br>
>> >> > you<br>
>> >> > could simply select stuff in the Object Explorer, evaluate "x :=<br>
>> >> > self"<br>
>> >> > and<br>
>> >> > you would have access to x in that other Workspace (resp. Inspector's<br>
>> >> > text<br>
>> >> > box).<br>
>> >><br>
>> >> Not a bad idea … what could be a UI for connecting workspaces?<br>
>><br>
>> Why not just invoke the halos on the inspectors built-in workspace and<br>
>> clone it with the upper-green button and use that?<br>
>><br>
> This would break workflow I think because like Jacob wrote, you open a file<br>
> in a Workspace and you need a reference to that from another already open<br>
> Workspace.<br>
><br>
> How about another copy command, like 'copy as reference' and then you could<br>
> paste it in another Workspace ?<br>
><br>
><br>
> Best,<br>
> Karl<br>
</div></div></blockquote></div><br></div>