livecode | A toolkit for livecoding using Ruby and TextMate on OSX

I contacted the package author and he suggested to follow this blogpost:

https://bitsandbricks.github.io/post/code-live-from-rstudio-and-share-it-with-the-world-in-real-time/

It suggests to use ngrok, a service that provides tunnels to localhost. This acutally worked for me for some seconds, killing my livecode package in the next moment. At the moment, I can no longer use livecode not even as a localhost. I assume this error may just be my fault. The blogpost provides an easy answer to my question.

It is possible that the ask and answer dialog assets are not being included in the build. Try this:

1. Open the Standalone Application Settings from the File menu.
2. Go to the General tab.
3. Click the radio button "Select inclusions for the standalone application".
4. Go to the Inclusions tab.
5. Scroll down until you find the Answer Dialog and Ask Dialog options, and check those.

Re-build your project and see if that solves the problem. Please note that if you choose to select inclusions manually you will have to check all of the libraries, widgets, and other assets that you are using in the stack.

When the "Search for required inclusions" option is chosen in the General tab, the Standalone Application Builder is supposed to scan the stack contents and include everything that's needed automatically. But it doesn't always catch everything, so many experienced LiveCode developers always do this step manually.

If you're going to use LineReceiver, you should not override dataReceived. Instead, override lineReceived. If your protocol isn't line-oriented, you probably don't want to use LineReceiver. Also you may want to consider using the Tubes interface in either case.

Do I just define all 20 of these functions in this same “MessageListener” class, or do I write a separate class to keep all of these functions?

You should probably put them on a different class. If you put them on MessageListener then you will have more difficulty testing, refactoring, and maintaining the code because your protocol logic is tightly coupled to your application logic.

Define an explicit interface that MessageListener uses to dispatch high-level events representing network actions. Then implement that interface appropriately for your particular application. Later, you can implement it differently for another application. Or you can write test doubles. Or you can change your protocol without changing your application logic. Decoupling the two pieces gives you lots of extra flexibility compared to smashing them both into one class.

I might get 10 messages at about the same time, and they may need to call the same function, so I wasn’t sure the best architecture approach here.

I think this is orthogonal but if it's an important enough part of your protocol or application logic, you might want to consider building some kind of vectorization into the explicit interface I mentioned above. Instead of appObj.doOneThing(oneThing) perhaps you have appObj.doSeveralThings([oneThing, anotherThing]).

I also want to build a GUI to interact with the server for some troubleshooting and monitoring on occasion. I’m familiar with Tkinter and it would be fine for this, and I can write the GUI in a separate file and have it connect to the server over a socket as well. But would I use the same socket listener implemented above and just pass it similar messages? Or should I build a separate class and factory to listen for the GUI connections?

That depends on the interactions you want to perform, I suppose. If this is a GUI with extra privileges compared to the normal client, you need a protocol and server with authentication and authorization functionality or you must not use the same server and protocol because you risk giving clients those extra privileges.

If you just want to simulate a real client with a kind of debug-friendly interface that lets you easily interact with the server in ways that a client would normally interact with it, but with an interface that makes this easier for you, you can (and presumably should) connect to the same server.

Set the script of the back button to

Your statement is written correctly. If you were to execute the statement and then look at the borderColor property in the field's property inspector, you would see that it had been set to purple. However, there is something you need to know about fields in LiveCode. When you first create a field, it is set to have a subtle 3-D look to the border, which is a standard look for fields on Mac and Windows. When a LiveCode field is set to 3-D, the color of the border is determined by two separate color properties, the topColor and the bottomColor, which determine the colors of the 3-D bevels on the field. To create a single, solid line border on your field do this:

You can use dangerouslySetInnerHTML but that is not recommended

Read more here

https://zhenyong.github.io/react/tips/dangerously-set-inner-html.html