Thanks for the quick response!

I'm looking for a good way to compartmentalize the data that will be used for each of the wires.

I guess I could write a json blob to a SQLite table on the main wire side and then pick it up in the sub wire?

I could use a variable on the main wire side that would contain the unique key to be used to do the query in the sub wire.

What do you typically do?

The app I am testing from is: 6858

I used my original salesforce account, even tried creating a new account; I can't get the salesforce login to pop-up using the example from the class.

I have gone through the integration blog entry from above

I have the salesforce consumer key and call back in my salesforce rarewire sdk settings.

Not sure what the best, next step should be. I am at the Hackathon this weekend. Any help is appreciated :)

Thanks! I like your thought for the javascript/system time approach. I think I will give that a try as well as see how "onresume" works.

I was looking through the documentation and hadn't noticed the "onresume" property, before.

P.S. very excited about the tag. I will have to refactor some of my code to take advantage of that. Many new features...Yay!

At this point, only while it is open.

Not a problem. I appreciate the time you are spending to figure it out. If it would help to have me stop by some day when you have time, I would be happy to run through it with you.

I took a look. The problem with the onchange event happens even if I don't call the twitterCharsLeft function.

I have changed the "testit" app to simply call an alert every time I type a character (onchange) in the textfield. The alert shows the content of the textfield.

The first time I type a character, the alert comes up empty. The second time I type a character, the alert comes up with the first character I typed, not the second one...and so on.

Is the expectation that the textfield.text property should have the most current character(s) in it when the onchange event fires?

Cool! Good to know about the count property.

Regrettably, I can't use it to determine the available characters in a tweet.

A tweet's length is not just the sum if its characters. If there is a URL in the tweet you have to use the length of 22 even if the URL is greater or less than 22 characters. This is due to the t.co URL used for shortening a URL in a tweet. Twitter URL shortening is 22 characters for any http URL and 23 for any https URL.

I have copied the twitter-text.js into functions.html to enable the correct calculation

I still think the onchange might have an issue :)

Cool! That took care of my apostrophe problem (Yay!)

There still seems to be an issue with the onchange event and the text being one character behind when the text property is referenced in the onchange action.

You can see this in the "testit" app that I have in my account. You have access to it.

Thanks!

I think apostrophes in a wire variable still cause an issue when trying to call a javascript function with that string as a parameter.

The use of any of the encoding options doesn't put the string in a state that will allow it to be successfully used as a parameter in a javascript function call. From what I am seeing, the apostrophe is never escaped.

There are two things contained in this comment:
1) Original issue: apostrophes still seem to terminate the wire variable string incorrectly when used in a javascript function call
2) Related issue: textfield text isn't in sync with onchange event

I changed the "testit" app to reflect my problem with apostrophes specific to my apps code.

In doing so, since fusebox v1.5 came out, I implemented my specific need. The specific need is taking the content of the textfield and passing it to a javascript function that determines the number of characters left for the tweet.

Originally, I was doing this on the save event of the screen in my app (apostrophes messed up the call to the character counting javascript function, otherwise it worked).
With the release of fusebox v1.5 I started using the onchange event for the textfield. I call the same javascript function; I can now check the length as the person types (Yay!).

In doing this test, I think I may have come across a bug with the onchange event. After you press the first key for the textfield, it calls the onchange action but the "text" property of the textfield is empty. When you press the second key, you get the content from the first key press, etc...

You can see both of these issues in the "testit" app.

Thanks!

Yup. I had tried it in my app and it didn't work. I decided to remove it from the complexity and created an app called "testit" (you have access).

All it does is let you enter text in a textfield and then push a button that applies the decodeURIComponent and the JSON.stringify and pops an alert with the results. If you include an apostrophe in the textfield you get an empty string for a result. If you have quotes, but no apostrophes you get the appropriately escaped string as a result. Apostrophes seem to be the downfall :(