Thanks for the quick response!

Based on how play tags work, I decided to break the calling action into two actions. The first action ends after the play is called to the global error routine. I have a block variable specified on the calling play (_nextAction) that specifies the next action to play.

After the error routine has processed the error code, the last step is to play the passed in _nextAction.

This creates the same effect as a play being synchronous.

To get even better encapsulation and reuse abilities for the error mgt routine, would it be possible to get the synchronous effect by putting the error checking code in a separate wire and load it to start the error check and call-back to continue? (being lazy and asking before I spend some time on calling wires :) )

Thanks!
Steve

A quick update on doing PUT to Parse.com! Eventhough I can't use the PUT verb in the httpmethod, Parse.com has a "batch" option that allows you to send multiple creates/updates/deletes in one Parse request.

The beauty is that the request is a POST and it allows you to specify in the payload if you are doing a PUT/DELETE/POST.

With that being said, I can update an existing record (or many) with the "batch" call (still a real-time REST call) using httpmethod of POST :)

Yay!
Steve

P.S. I am still interested in when the PUT becomes available :)

That would be great. Thanks!

I have a record in parse that is associated with a specific user. The record contains content that the user's company will choose to use or not use.

That specific user, when they open the app, will be presented the content and will be asked to approve or reject it.

My original approach was to mark that record as approved or rejected based on the users selection.

I think what I'm going to do at this point is jump ahead in my roadmap a little bit and separate the approval from the content. I will use the object ID of the original content record to link to a separate record that shows approval or rejection of that content.

Thanks for working with me on this! I appreciate the input and the different perspectives on how to look at solving the problem.

I may have to stop by at some point, since I'm only a couple blocks from you, and let you see the app you're helping me with :-)

Thanks for the response. POST does not seem to be an option with a Parse.com REST update call.

I will see if I can get a javascript option to work with PUT. The Parse.com REST API fails on an update to an existing object when a POST is used.

They appear to look for the PUT verb for any updates to existing objects.

I tried using POST with Parse.com for an update REST call using curl (they explicitly call for PUT) and it failed. I tried PUT with the same test and same data and it worked with Parse.com

If you have any additional thoughts, they are welcome.

Thanks!

Thanks! I got a simple implementation of it to work. I appreciate the quick response!

Now, for the additional confusion on my part. Based on the "layering" of panels and text tags in my real implementation, I am not seeing consistent results :(

I have abstracted my implementation to something a little more manageable and sent you an invite to a project called "TestIt".

No big hurry, if you can take a look at the 3 examples of clickdelay (one works, two don't) and let me know what you think, I would greatly appreciate it

Thanks!
Steve

Thanks John!!

That could not have been easier. I copied your exact content to a wire file, pasted in my Parse application Id and REST API key and it worked; I was creating users in Parse.

I now know what I will be doing for the rest of the weekend :)

I have included an example that I created for an app I built. It dynamically creates the pagination circles and centers them. It also allows you to delete the circles and rebuild them. This is useful when you are changing the query on your datasource (filtering data in an app) and the result count is different.

I attempted to pull this out of a larger app. Hopefully, it is trimmed down to only what you need.

There is a wire file and an XML file used as the datasource.


<wire>
<datasources>
<datasource name="items" alias="ITEMS" source="" query="//item" providertype="xml" />
</datasources>

<styles>
<style name="contain-style" width="100%" height="100%" align="center" valign="top" padding-top="25" padding-right="25" padding-left="25"></style>
<style name="btn-style-bottom" width="100%" height="45%" align="center" margin-top="15px" margin-bottom="5" ></style>
<style name="item-style" width="100%" height="100%" borderwidth="5" bordercolor="c0c0c0" cornerradius="8"></style>
</styles>

<classes>

<class name="item-selection">
<panel name="item-[param:index]" alias="ITEM-[param:index]" style="item-style" _index="[param:index]" onscrollto="set-item" onscrollaway="from-item">
<text name="item-text-[param:index]" width="100%" height="100%" color="#ff0000" font="helvetica" size="40" alignment="center" text="[param:title]"></text>
</panel>
</class>

<class name="ellipse-inner">
<panel name="[param:container-name]"
alias="[eval:'[param:container-name]'.toUpperCase()]"
height="100%" width="[param:panel-width]" align="center">
</panel>
</class>

<class name="ellipse-item">
<panel name="[param:prename][param:index]"
alias="[eval:'[param:prename]'.toUpperCase()][param:index]"
width="5px" height="5px" valign="center" background="[param:ellipse-color]"
rightof="[eval:'[param:prename]'.toUpperCase()][eval:[param:index]-1]"
cornerradius="3" margin="13" />
</class>

</classes>

<main>

<panel name="canvas" alias="CANVAS" background="303030" width="100%" height="100%" padding="50">

<list name="item-tableview"
alias="ITEMTABLEVIEW" rowheight="150" width="100%" height="45%"
datasource="items" orientation="horizontal" pagination="no"
align="center" valign="center" margin="10" >
<object class="item-selection"
index="[param:dataSourceIndex]"
title="[param:name]" />
</list>

<panel name="ellipse-container" alias="ELLIPSECONTAINER"
bottomof="ITEMTABLEVIEW" margin="10" align="center"
height="10%" width="100%">
</panel>

<panel name="delete-ellipses" alias="DELETEELLIPSES"
bottomof="ELLIPSECONTAINER" align="center"
height="75px" width="150px"
borderwidth="2" bordercolor="808080"
cornerradius="10"
background="202020"
onclickup="delete-ellipses">
<text name="btn-action" alias="BTNACTION" width="100%" height="100%" color="808080" font="helvetica" size="24" alignment="center" valign="center" align="center" text="Delete">
</text>
</panel>

</panel>

</main>

<actions>

<action name="initialize" oninit="yes">
<assign property="datasource:items.source" value="res://items.xml" />
</action>

<action name="load-items">
<assign property="datasource:items.query" value="//item" />
<set target="DELETEELLIPSES" onclickup="delete-ellipses"/>
<assign property="object:BTNACTION.text" value="Delete" />
</action>

<action name="items-error" datasource="items" datasourceevent="datasourceerror">
<alert title="Items" message="Failed to load items" />
</action>

<action name="items-loaded" datasource="items" datasourceevent="querycomplete">
<sync>
<assign property="var:curItemNum" value="1" />

<!-- set the variables for removing ellipses -->
<assign property="var:numDeleteCount" value="1" />
<assign property="var:numToDelete" value="[datasource:items.dataSourceResultCount]" />

<!-- determine width of ellipses based on # in datasource -->
<assign property="var:valEllipseWidth"
value="[eval:15*[datasource:items.dataSourceResultCount]]" />

<!-- create the panel that will be centered on the screen and hold the ellipses -->
<create class="ellipse-inner"
target="ELLIPSECONTAINER"
panel-width="[var:valEllipseWidth]"
container-name="ellipseinner" />

<!-- these values will be used to manage the looping to build the ellipses -->
<assign property="var:numItems" value="[datasource:items.dataSourceResultCount]" />
<assign property="var:numCounter" value="1" />
<!--
call the action to build the ellipses. this action calls itself
until the counters match the number of retrieved items from the datasource
-->
<play action="build-ellipses" />
</sync>
</action>

<!-- called when you have scrolled to an item and sets the new item as the current item -->
<action name="set-item">
<assign property="var:curItemNum" value="_index" />
<set target="CHOSEN-ELLIPSE_index" tofront="yes" />
</action>

<!-- changes the old item from selected to unseleced with the pagination ellipses -->
<action name="from-item">
<set target="ELLIPSE_index" tofront="yes" />
</action>

<!--
manage the ellipses that show the number of items and
which item you have selected
-->
<action name="build-ellipses">
<sync>
<!--
this section builds two ellipses if it is the selected item. it
builds two ellipses, in the reverse z-order, if it is an unselected item. The purpose
is to allow the "selected" ellipse to be moved to the next selected
item on the scrollto event
-->
<if lhs="[var:numItems]" operator="gte" rhs="1">
<if lhs="[var:numCounter]" operator="eq" rhs="[var:curItemNum]">
<create class="ellipse-item" target="ELLIPSEINNER" ellipse-color="808080" index="[var:numCounter]" prename="ellipse" move-right="1" />
<create class="ellipse-item" target="ELLIPSEINNER" ellipse-color="ffffff" index="[var:numCounter]" prename="chosen-ellipse" move-right="1" />
</if>
<if lhs="[var:numCounter]" operator="ne" rhs="[var:curItemNum]">
<create class="ellipse-item" target="ELLIPSEINNER" ellipse-color="ffffff" index="[var:numCounter]" prename="chosen-ellipse" move-right="1" />
<create class="ellipse-item" target="ELLIPSEINNER" ellipse-color="808080" index="[var:numCounter]" prename="ellipse" move-right="1" />
</if>
</if>
<!--
increment the loop counter by 1 and determine if ellipse building is done
or if we call the build-ellipses action again, in which case we come back
through this whole action again
-->
<assign property="var:numCounter" value="[eval:[var:numCounter]+1]" />
<if lhs="[var:numCounter]" operator="lte" rhs="[var:numItems]">
<play action="build-ellipses" />
</if>
</sync>
</action>

<!--
increment the loop counter by 1 and determine if ellipse deleting is done
or if we call the delete-ellipses action again
-->
<action name="delete-ellipses">
<sync>
<if lhs="[var:numDeleteCount]" operator="lte" rhs="[var:numToDelete]">
<delete target="ELLIPSE[var:numDeleteCount]" />
<delete target="CHOSEN-ELLIPSE[var:numDeleteCount]" />
<assign property="var:numDeleteCount" value="[eval:[var:numDeleteCount]+1]" />
<play action="delete-ellipses" />
</if>
<set target="DELETEELLIPSES" onclickup="load-items"/>
<assign property="object:BTNACTION.text" value="Rebuild" />
</sync>
</action>

</actions>
</wire>



And this is the XML file



<?xml version="1.0" encoding="UTF-8"?>
<items>
<item>
<name>1</name>
</item>
<item>
<name>2</name>
</item>
<item>
<name>3</name>
</item>
<!-- <item>
<name>4</name>
</item>
<item>
<name>5</name>
</item>
<item>
<name>6</name>
</item> -->
</items>



You can uncommonly the other three nodes in the XML to prove that the circles are built dynamically

The adprovider entry field in the Medialets section of the API settings doesn't prefill. From what I can tell the value you need to put in their is "medialet". My application error stops displaying when that value is used.

I have my appid and adprovider entered, but the ad tag expects a slot name. I see in muse.medialets.com where the slot name would be listed for the app I created in Medialets, but the webpage section is empty and there isn't a way to add slot name information.

If there is a snippet or something that you could share to help me get the ad tage working, it would be greatly appreciated.

Thanks!

Where do you get the value for the "adprovider" field?