This does as you wish and runs in Sesame2 and 3.

var aa as string

aa = @RedirectProcess("/usr/bin/perl", "print 'hello world';")
writeln(aa)
 

Actually, on my system, perl doesn't need the full path. The first argument is the process to be invoked and the second is a string that is passed to that process through stdin. Because perl (and most scripting languages) will accept the program to run through stdin, it runs that program. The return value catches the stdout of that program and places it in the "aa" string.

Of course this isn't limited to just script interpreters. Here are examples of accessing a mySQL database from Sesame2:

var aa as string

aa = @RedirectProcess("mysql --user=yourlogin --password=yourpassword", "show databases")
writeln(aa)
 

var aa as string
var sql as string

sql = "USE dbtest;"
+     "SELECT * FROM AUTHORS;"
+     "GO"

aa = @RedirectProcess("mysql --user=you --password=pwd", sql)
writeln(aa)
 

Nominally open.

Sesame3 alpha/beta testing has been on hiatus while we beta test Sesame 2.5.3.

WOW! From your screenshot, it appears like we will be able to view (and interact with?) the embedded application. Very exciting!

Looking good.  Can you elaborate a bit on "other applications"?  Are you doing something like making a block where a "Sync" type of process is visible, so almost any app can be displayed on the form?  Could that include a browser, QuickBooks, etc?

This is extremely minor but one cannot save the code immediately after successful testing in the program editor. You have to exit the editor and then save it in the control panel using Command Menu.  It would be nice if the code could be saved from Program  Editor.  That will save a few key strokes and one is likely to save more often and could make a difference in a catastrophic event and ease of operation.  May be conrol-S as that is common with the other programs.

I know that the  save in the Control Panel also check for the error in the Layout Design but that could be checked at the final exit.   

Today we had our quarterly SANE meeting.  After some discussions about getting programming to run from the RetrieveSpec screen, we got into discussions about what we know about Version 3.

We agreed as a group that one of the biggest needs we had and wanted to see in version 3 was better tools to use with diagnosing programming steps.  There was total agreement that we really need a tool that allows us to Single Step through the code, with a view of the variables and their values after each step.  The ability to insert BreakPoints would be a big plus after that, but as a minimum we really want to have Single Step ability.   

We could not think of any major programming development tool that does not have this feature.  Even the lowly batch file allows you to do a Single Step (and it was also the recollection that even Q&A had Single Step tools in Version 2).

WriteLn has been the suggested tool since Sesame came out, but it is really too cumbersome to keep typing in the lines, commenting them out.  Knowing which subroutines were called is needed to know where to insert many WriteLn functions.

So we are respectfully requesting as a group that Single Step tools be provided with the release of Version 3.  We are sure that many other users will chime in and agree with this request.

Thanks for listening.  We are hoping to see that feature announced at the National Sesame Group Meeting we are also hoping to attend with the Version 3 Release (We all missed any mention of where on the East Coast that was going to be held  ).

Bob_Hansen wrote on May 6^th, 2012 at 4:13am:


Rumor has it,  it's going to be in a small city in Ohio and the users are going to take the incredible Lantica team to a wonderful dinner at a really nice place and then the next couple of mornings the users are going to show up and answer phones and take messages so the Lanticans can have a few days of peace and quiet.