Professional Documents
Culture Documents
xb
The Rodeo Editor for the Macintosh (BETA)! 3
Signing Up! 3
Logging In! 4
Logging Out! 4
Rodeo Views! 6
The Web View! 6
The Defs View! 7
The HTML View! 8
Rodeo Modes! 8
The View Mode! 8
The Edit Mode! 9
Locking a Definition! 11
Linking to an Image! 16
Rodeo 2.0.x BETA is a Desktop app for the Mac that lets you create and edit definitions that
our server converts into Rodeo apps, pages, and objects for the Web. The aim of this short
document is to get our BETA users up and running with Rodeo 2.0.xb, and is not intended as full
documentation.
Join Rodeoapps.com to discuss questions and issues not covered here.
Signing Up
If you haven’t already signed up for the Rodeo BETA offer:
• Go to http://rodeoapps.com/limited-pre-release-offer.
• Scroll down to the blue CLICK HERE link and click it.
• Fill in and submit the Sign-up form.
• Check your Inbox for an email verifying receipt of your form, and containing a PayPal
link.
IMPORTANT: You must click the PayPal link to pay for your license before we can register
you on our server.
• Within 24 hours of payment, you’ll receive a “Welcome to the Rodeo” confirming that
the User Name and Password you supplied in your sign-up form has been registered with
our server — and containing two links:
One for downloading another zip file containing the new BETA version 2.0.xb.
• Since this early release of 2.0.xb does not yet incorporate all of the niceties of the 1.0x
pre-release version, we recommend that you familiarize yourself with both versions.
• You can run these two versions of Rodeo simultaneously, moving back and forth between
them at will.
• Several Pickers are available in the Rodeo 1.0.x’s Definitions editor that have not yet
been migrated to 2.0.xb — and you might find it more efficient to set certain properties of
objects in the old version, such as:
URL links
Background Images
Logging In
• Unzip the downloaded file and double-click the
Rodeo 2.0.xb app icon to go to the Login
screen.
• Enter your registered User Name and Password
and click the Log In button (or type Return or
Enter) to open the editor.
• After successful login, the Rodeo Tree with its
hierarchical list of objects will be loaded on the
left — and the Rodeo Home page will appear
on the right. (It may take a few seconds for the
Tree to populate.)
NOTE: Once you are logged into the Rodeo server, your session will persist until you log out.
So if you quit Rodeo without logging out, when you open it again, login is bypassed — and the
Tree and the Rodeo Home page are loaded right away.
Logging Out
• Click the Logout button on the right side of the top toolbar (or choose
‘Logout” from the Go menu), and you’ll be returned to the login screen.
• You can either login again from this screen, leave the application in this
state and return later to login again — or quit the application.
Drag tools and bar graphics on and off the toolbar to add or remove them.
Use the Show menu and its associated checkbox to specify whether icons appear large
or small, and with or without text.
Rodeo Views
Three Ways to View Your Apps
• The Web View
• The Definitions View
• The HTML View
Tables can be sorted, scrolling fields scrolled, line items in lists selected, etc.
• If you have navigated away from this view and wish to restore it:
Click the Web button on the top toolbar (or choose Web View from the View menu).
Alternatively, if you are in edit mode, click the View mode button.
• Once you select a target item in the hierarchical Tree list, there are three ways to view its
definition (example shown above):
Click the Defs icon on the top toolbar (or choose Defs View from the View menu).
Click the Edit Mode button that appears on the right side of the bottom toolbar, then
click the item on that page whose definition you wish to view. (More on working in
edit mode later in this document.)
• Click the HTML icon in the toolbar (or choose HTML View from the View menu).
• The HTML script for the currently selected page will be displayed in the workspace. This
script includes revised code for the app-level definitions, the page’s definitions, and the
definitions for all of the objects on that page.
• Select all or part of the HTML to copy and paste it into any text or html editor.
Rodeo Modes
The Rodeo workspace has two operational modes:
• The View Mode
• The Edit Mode
• To put your app into edit mode, simply click the Edit Mode button on the right side of the
bottom toolbar.
• When you do this, two things happen:
The name of the Edit Mode button changes to View Mode (which you can click at
any time to return to Web View).
NOTE: In Rodeo 1.0.x, the edit mode is identified by rainbow gradients in the
window’s header and footer. But it was too easy to forget that you were in this mode,
click an item to test its behavior — and end up in that item’s definition instead. So
we’ve adopted the checkerboard background to make the window’s editable state
much more obvious.
If you have Rodeo selected in the Tree, you can add an app.
If an app is selected in the Tree, you can add a page to that app.
If a page is selected in the Tree, you can add an action or a listed UI item to that page.
NOTE: The list of supported objects for pages is growing daily, so keep an eye on the
Rodeoapp.com site for news of updates.
Deleting an Object
• Click any item in the Tree.
Select the target page in your tree where you want your app’s table object to appear,
then click the + button.
For the moment, this data object is just a placeholder — but it will soon allow you to
upload data files. For now, just create it and leave it.
Set the table’s data property to the name of your data object:
Set the title of column 1 to ID, then set its visible property to false if you want to hide
it:
NOTE: Do not use the ID field for any of your data. This field belongs to the data
object, which maintains it internally.
Remove the default line in the table definition that sets it’s filename.
Since the table does not know what sort of data it will be displaying, set the text
alignment of columns manually. Your table object will appear empty on the page —
except for its column titles.
This field can be on the same page as the table object (so that your record would
display next to the table, for instance) — or on a different page in the app.
Each object that is to display a portion of the data must have its data property set to
the name that you gave your data object when you added it to the app. In our
example, you would add the following to the definition of your first name field:
The name of any object whose data is also displayed in the table MUST be the same
as the table’s column name for that item. So, if the table displays the first name of
each person in your database under a column titled “first” — then you would also
name the field “first.” You can create a label for the field that says “First Name,” if
you wish — but the field that displays the name must be called “first.”
NOTE: Do not set a data property for any static information or decorative objects
used merely for design or instructional purposes, etc. — and whose data you don’t
need or wish to save.
You can set the button’s definition to show or hide the name.
Set the data property of your button to the name of your data object:
Set the action of the button according to the built-in action you wish it to perform:
Once you do this, you are done. The action for each of these buttons is built into the
data object, so you do not need to define any of these actions in your app.
If your record appears on a separate page from your table, you may also find it useful
to create a button on the record page that returns the user to the table list. This button
should not be linked to the data object — but it must be linked to an action which you
WILL have to add. However, all you have to state in the action is:
Call it anything you want, but for an example, we’ll call it “image.”
Set the data property of the field to the name of the data object.
• Add an image to your record page to page.
Give the image the same name as your URL field. In this example, that would be
“image.”
Set the top and left properties according to where you want the image to display on
the page.
Set the size properties according to the size of the largest image you wish to display.
Set the data property of the image to the name of the data object.
You do not need to set the filename property for the image, since the data object will
reference the URL in your “image” field, instead.
• Each time you create record, enter the URL to its associated image into the “image” field
and save the record.
The next time the record is displayed, the image will display in the linked image
object.
Once you have finished creating your database, if you don’t want users to edit the
database, you can optionally hide this field, along with the New, Save, and Delete
buttons. But to add any new records, or modify the URLs for existing records, you’ll
need to show it again.
• From the ‘Publish Content’ menu, choose ‘On Rodeo Server...’ (The two additional
options that are currently disabled will be available soon.)
• Click the Publish button in the resulting dialog to complete the publishing operation:
That’s it. Your app is LIVE and you’re all done — unless, of course, you’d like to build your
own self-contained viewer for your application.
• Click the Build button in the resulting dialog to create a native Mac app to house your
content (i.e., pages, images, data, logic, etc.):
Click ‘Show in Finder’ to go to the place in your Mac where your application
has been stored.
Click ‘Run App’ to open and view your app in your proprietary viewer:
Standard Mac Applications menu, named after your app. In our illustrated example,
the app is called ‘Portfolio.’ Its built-in options include:
• Plus the standard options that let users hide your app, hide other apps, show all
currently open application, or quit your app.
The File menu offers the standard ‘Page set-up...’ and Print options for your app’s
current page.
The Edit menu offers the standard edit options, including Undo, Cut, Copy, and Paste
— and lets users do things like check spelling as they type in an editable field.
The View menu lets users Refresh, Stop [refreshing], Hide or Show the toolbar, and
Customize the toolbar. In the picture below, since the Portfolio app already has its
own Previous and Next buttons, as an example we removed these items from the
toolbar — along with Print, since it is also readily available from the File menu:
The Help menu offers the standard search field for general Mac help information.
Rodeo builds all of these menus, options, and behaviors into your proprietary viewer for you
— so that you don’t have to write a single line of code to implement any of these standard Mac
application features.