<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>Is there any way I can start squeak from a command window, *headless*, and WITHOUT providing a script and have an interactive application^ Say, for instance, my application waits for input and answers back the square of the number I type in?</div><div><br></div><div>I've tried a gazillion examples I found and it just doesn't work at all...</div><div><br></div><div>I'm on Windows 10 if that helps.</div><div><br></div><div>I get all kinds of errors : stdout is not open or "<span>VirtualProtect(x,y,PAGE_EXECUTE_READWRITE): No error" or missing ', or variable out of scope (WHAT?!?!?)...</span></div><div><span><br></span></div><div><span>In other words, I'm fed up trying.</span></div><div><span><br></span></div><div><span>I could do that stuff in 2 minutes in any other language and this makes me sick!</span></div><div><span><br></span></div><div><span></rant><br></span><br></div><div><br></div><div class="ydp97777b77signature">----------------- <br>Benoît St-Jean <br>Yahoo! Messenger: bstjean
<br>Twitter: @BenLeChialeux
<br>Pinterest: benoitstjean
<br>Instagram: Chef_Benito<br>IRC: lamneth
<br>Blogue: endormitoire.wordpress.com
<br>"A standpoint is an intellectual horizon of radius zero". (A. Einstein)</div></div>
<div><br></div><div><br></div>
<div id="ydpb495a8bfyahoo_quoted_3418057187" class="ydpb495a8bfyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, April 6, 2018, 5:28:13 a.m. EDT, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpb495a8bfyiv7143182247"><div><div dir="ltr"><br clear="none"><div class="ydpb495a8bfyiv7143182247gmail_extra"><br clear="none"><div class="ydpb495a8bfyiv7143182247gmail_quote">2018-04-06 11:11 GMT+02:00 H. Hirzel <span dir="ltr"><<a shape="rect" href="mailto:hannes.hirzel@gmail.com" rel="nofollow" target="_blank">hannes.hirzel@gmail.com</a>></span>:<br clear="none"><blockquote class="ydpb495a8bfyiv7143182247gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><span class="ydpb495a8bfyiv7143182247">On 4/6/18, Nicolas Cellier <<a shape="rect" href="mailto:nicolas.cellier.aka.nice@gmail.com" rel="nofollow" target="_blank">nicolas.cellier.aka.nice@ gmail.com</a>> wrote:<br clear="none">
> 2018-04-06 11:04 GMT+02:00 Nicolas Cellier <<br clear="none">
> <a shape="rect" href="mailto:nicolas.cellier.aka.nice@gmail.com" rel="nofollow" target="_blank">nicolas.cellier.aka.nice@ gmail.com</a>>:<br clear="none">
><br clear="none">
>> By re-routing one or two rivers, it sounds effectively possible, but we<br clear="none">
>> need may little washing particles<br clear="none">
>><br clear="none">
><br clear="none">
> No I don't promise it for May, I meant many<br clear="none">
<br clear="none">
</span>Nicolas,<br clear="none">
<br clear="none">
Do you have a particular idea how an implemenation plan/ outline of<br clear="none">
tasks to do for 'rerouting the rivers for the water to be used for<br clear="none">
cleaning' would look like?<br clear="none">
<br clear="none">
--Hannes<br clear="none">
<br clear="none"></blockquote><div>Hi Hannes,<br clear="none"></div><div>isn't it precisely what Tim (and you) are trying to achieve thru this call to goodwill?<div class="ydpb495a8bfyiv7143182247yqt5607595158" id="ydpb495a8bfyiv7143182247yqtfd17873"><br clear="none"><br clear="none"> <br clear="none"></div></div><div class="ydpb495a8bfyiv7143182247yqt5607595158" id="ydpb495a8bfyiv7143182247yqtfd44503"><blockquote class="ydpb495a8bfyiv7143182247gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
><br clear="none">
>> <a shape="rect" href="https://en.wikipedia.org/wiki/Labours_of_Hercules#Fifth_" rel="nofollow" target="_blank">https://en.wikipedia.org/wiki/ Labours_of_Hercules#Fifth_</a><br clear="none">
<div class="ydpb495a8bfyiv7143182247HOEnZb"><div class="ydpb495a8bfyiv7143182247h5">>> labour:_Augean_stables<br clear="none">
>><br clear="none">
>> 2018-04-05 19:47 GMT+02:00 tim Rowledge <<a shape="rect" href="mailto:tim@rowledge.org" rel="nofollow" target="_blank">tim@rowledge.org</a>>:<br clear="none">
>><br clear="none">
>>><br clear="none">
>>><br clear="none">
>>> > On 05-04-2018, at 10:13 AM, K K Subbu <<a shape="rect" href="mailto:kksubbu.ml@gmail.com" rel="nofollow" target="_blank">kksubbu.ml@gmail.com</a>> wrote:<br clear="none">
>>> ><br clear="none">
>>> > <a shape="rect" href="http://wiki.squeak.org/squeak" rel="nofollow" target="_blank">wiki.squeak.org/squeak</a> is an excellent resource for Squeakers.<br clear="none">
>>> However, it's interface is a bit dated and could do with some<br clear="none">
>>> improvements.<br clear="none">
>>><br clear="none">
>>> I agree that the UI is a bit blah (and your suggestions are interesting)<br clear="none">
>>> but far more worrying is the out of date state of so many pages. Every<br clear="none">
>>> now<br clear="none">
>>> and then I go on a minor rampage to mark obviously obsolete pages,<br clear="none">
>>> delete<br clear="none">
>>> clearly ridiculous one, recycle those pages, update stuff where I know<br clear="none">
>>> what<br clear="none">
>>> can be improved and so on. We suffer from a colossal swathe of<br clear="none">
>>> effectively<br clear="none">
>>> empty pages generated by some long-gone process/project that appeared to<br clear="none">
>>> consider that dumping class name as page and (maybe) sticking class<br clear="none">
>>> comments in was a good idea. There are strings of pages forming the<br clear="none">
>>> promising beginnings of tutorials that simply fade out<br clear="none">
>>> to.........{crickets}<br clear="none">
>>><br clear="none">
>>> Almost anyone can help to clean up the swiki. Pick some page from the<br clear="none">
>>> front page, follow it down the rabbit-hole a bit, look at the pages that<br clear="none">
>>> link to a duff page, clean them up a bit, recycle bad pages, rewrite<br clear="none">
>>> poorly<br clear="none">
>>> thought out explanations, maybe replace ancient screenshots with ones<br clear="none">
>>> taken<br clear="none">
>>> from a current Squeak. (as an example, take a look at<br clear="none">
>>> <a shape="rect" href="http://wiki.squeak.org/squeak/3480" rel="nofollow" target="_blank">http://wiki.squeak.org/squeak/ 3480</a> - lots of very out of date examples<br clear="none">
>>> there). Even simple things like organising into proper lists and editing<br clear="none">
>>> text into proper paragraphs can help a lot in readability. You don't<br clear="none">
>>> need<br clear="none">
>>> to be a great expert to provide a valuable service here - but I bet that<br clear="none">
>>> spending some time in the swiki will start to make you an expert, even<br clear="none">
>>> if<br clear="none">
>>> it's only by making you look up the real state of something!<br clear="none">
>>><br clear="none">
>>> If everyone on the squeak-dev list edited a swiki page once a week we'd<br clear="none">
>>> very quickly see big improvements.<br clear="none">
>>><br clear="none">
>>> tim<br clear="none">
>>> --<br clear="none">
>>> tim Rowledge; <a shape="rect" href="mailto:tim@rowledge.org" rel="nofollow" target="_blank">tim@rowledge.org</a>; <a shape="rect" href="http://www.rowledge.org/tim" rel="nofollow" target="_blank">http://www.rowledge.org/tim</a><br clear="none">
>>> I'm so skeptical that I'm not sure I'm really a skeptic<br clear="none">
>>><br clear="none">
>>><br clear="none">
>>><br clear="none">
>>><br clear="none">
>><br clear="none">
><br clear="none">
<br clear="none">
</div></div></blockquote></div></div><div class="ydpb495a8bfyiv7143182247yqt5607595158" id="ydpb495a8bfyiv7143182247yqtfd68687"><br clear="none"></div></div></div></div></div><div class="ydpb495a8bfyqt5607595158" id="ydpb495a8bfyqtfd19731"><br clear="none"></div></div>
</div>
</div></div></body></html>