Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix links

...

Prerequisites

  • complete the Pico-Engine NEXT Quickstart

  • have the hello_world ruleset from the Quickstart installed in a pico

  • have installed Postman, or some other HTTP app.

...

Table of Contents
maxLevel2

Video Tutorial

Note

video

doesn't use the pico-engine NEXT

shows an older developer UI

It is still correct in its discussion of picos and KRL, but doesn't match the next current developer UI


Widget Connector
overlayyoutube
_templatecom/atlassian/confluence/extra/widgetconnector/templates/youtube.vm
width400px
urlhttps://www.youtube.com/watch?v=a4VUn_XGZD8&feature=youtu.be
height300px

...

Here is a sample URL that sends an event to a pico like the one you created in the Pico-Engine NEXT Quickstart:

Code Block
http://localhost:3000/sky/event/ckcvuri6r0017conl4siq0q3r/1556/echo/hello

...

When you develop a ruleset, you may choose to use the "Testing" tab of the developer UI which can provide a simple UI for your event. The "Testing" tab works by querying your ruleset to see if it shares the name __testing and if it does, it parses the structure that __testing points to and builds simple forms to test each of the queries and events which the structure defines. The __testing structure is created automatically by the compiler.

...

Be sure to validate your source code, using one of the techniques in Developer Tips for Pico Engine to ensure that you have introduced no syntax errors into your ruleset. Once you get the "ok", go ahead and push your changes and flush the ruleset in your pico. (Review the Pico-Engine NEXT Quickstart page if necessary)

Click on the "Testing" tab of the developer UI. Choose the "hello_world" channel from the ECI dropdown. Notice under your ruleset identifier that there are three forms, one for each of the shared functions and the event that you defined in your ruleset.

...

Congratulations! You know how to send queries to a pico, either directly using a URL, or through the "Testing" tab of the UI.

More about logs

...