Firstly, congratulations to the Rev team that has been working on O4W. I have been dabbling in Web Apps in OI for a number of years, but frankly the earlier OI web facilities didn't cut the mustard. O4W on the other hand appears to be a web-based user interface that matches the calibre of the underlying MV database. My humble opinion is that you are very much on the right track with O4W.

My first question relates to how we should go about creating non-database associated forms. The current arrangement seems to require database association… Or am I missing something?

Firstly, congratulations to the Rev team that has been working on O4W. I have been dabbling in Web Apps in OI for a number of years, but frankly the earlier OI web facilities didn't cut the mustard. O4W on the other hand appears to be a web-based user interface that matches the calibre of the underlying MV database. My humble opinion is that you are very much on the right track with O4W.

My first question relates to how we should go about creating non-database associated forms. The current arrangement seems to require database association… Or am I missing something?

Hi, Robert. Glad you like O4W!

If you're coding your own O4W stored procedures (using the APIs), then there's no "data binding" - you define and populate all the controls and elements programmatically.

If you're using the O4W Form Wizard, then you can "user defined fields" on the Groups tab. These user defined fields aren't data-bound, but can be filled in and manipulated via the associated commuter module of the form. You _will_ have to specify a table to use for the form, but if you wanted everything to be unbound the selected table can just be ignored.

Hope that helps,

- Bryan Shumsky

Revelation Software, Inc.

Hi Bryan

I wish to make our App a Facebook Application. I see from the documentation that we can talk to Facebook. O4WFacebook(action, param1, param2, param3, param4, styleInfo)

Unfortunately, there are no examples provided so I am unsure where to put the code.

Could you please provide an example? In particular, do you know how to gain access to the Facebook user's record.

Thanks

Roberty

Hi Bryan

I wish to make our App a Facebook Application. I see from the documentation that we can talk to Facebook. O4WFacebook(action, param1, param2, param3, param4, styleInfo)

Unfortunately, there are no examples provided so I am unsure where to put the code.

Could you please provide an example? In particular, do you know how to gain access to the Facebook user's record.

Thanks

Roberty

Hi, Robert. The O4WFacebook API allows you to do things like put up a "like" button, or a "login" button, but does NOT provide you with functionality to extract user information, or even to perform a login into facebook by itself. It's a way for a Facebook developer to put up various Facebook controls (the "Social plugins"), but isn't full "facebook integration", so it may not be what you're looking for.

However, in case it is…

You must pass in an "action" (describing what you want the API to do), such as "INIT" (initialize the facebook api), "LOGIN" (put up a login button), "LIKE" (put up a "like" button), "RECOMMEND" (put up a "recommend" button), etc., as the first parameter. The full list of options are: INIT, LOGIN, LIKE, ACTIVITY, LIKEBOX, LIVE_STREAM, FACEPILE, and COMMENTS.

The first call you must make (during the CREATE event of your form) is for the INIT action, and you must pass in as the second parameter the "appid" that you were assigned by Facebook as a developer. So your call would look like this:

O4WFacebook("INIT", appid)

(If you're not familiar with how to get a Facebook appid, here's a link that seems to explain the process pretty clearly)

You can then call any of the other actions; in most cases, the additional parameters are optional. For the LOGIN action, you can specify a "1" in the second parameter if you want to show faces. The third parameter is the number of rows to display, if desired:

O4WFacebook("LOGIN", "1", 5)

or just

O4WFacebook("LOGIN")

For the "LIKE" and "LIKEBOX" action, the second parameter is the URL you want to specify as being liked; for the "ACTIVITY" or "RECOMMEND", the second parameter is the domain part of the URL.

The other parameters give you additional control over layouts, etc., that depend on the action you've chosen. If you have a specific question about one of the actions, I can provide more detail; I'd suggest you start with just a bare minimum, though, and see if that gives you what you're looking for.

- Bryan Shumsky

Revelation Software, Inc.

Bryan

>If you have a specific question about one of the actions, I can provide more detail;

Ok, may I draw your attention to the Social Plugin called 'Registration' (http://developers.facebook.com/docs/plugins/registration/)

I have set up Facebook to point to an O4W Procedure, which at this point seems to make most sense.

What would you do from here?

Thanks

Robert

Bryan

>If you have a specific question about one of the actions, I can provide more detail;

Ok, may I draw your attention to the Social Plugin called 'Registration' (http://developers.facebook.com/docs/plugins/registration/)

I have set up Facebook to point to an O4W Procedure, which at this point seems to make most sense.

What would you do from here?

Thanks

Robert

Hi, Robert. Unfortunately, the "registration" plugin (and the enhancement to the "Login" button that allows for registration) are relatively new changes to the Facebook social plugin APIs, and are not yet "wrapped" in O4W's O4WFacebook call.

However, now that you've got a developer's ID (appid), you should be able to (for example) put up a Login button as a way to test at least _that_ functionality. I imagine that we will add additional Facebook support for the new APIs in the future.

- Bryan Shumsky

Revelation Software, Inc.

View this thread on the Works forum...