Thanks Tom! Fixed these issues in the tutorial. Sorry about that.

Tom,

I think you tried to attach some code to this topic, please use the (some HTML allowed) link above to learn how to add code snippets to the comments here.

Thanks!

anything you are using an "on" attribute for an object (onclick, onmove, onswipe, etc) your value will be the name of an action tag.

Your action can contain a variety of action tags to produced a desired effect. In your example, you might simply have 4 panels that represent your pages and create a set of actions.


<wire>
<main>
<panel name="navbar" height="100" width="100%" background="ff0000" valign="bottom">
<image name="nav-button1" source="button1.jpg" "onclickup="page1action"></image>
<image name="nav-button2" source="button2.jpg" onclickup="page2action" rightof="nav-button1"></image>
<image name="nav-button3" source="button3.jpg" onclickup="page3action" rightof="nav-button2"></image>
<image name="nav-button4" source="button4.jpg" onclickup="page4action" rightof="nav-button3"></image>
</panel>
</main>
<actions>
<action name="page4action">
<alpha value="1" time="1" target="nameofreferencepage4" />
</action>
</actions>
</wire>


Probably the best way to accomplish this is to wrap your separate text tags in panels and assign a height of "fit" this will control the height of the text to the dimensions of the panel. Then you can define your distance between the two by controlling the panels which are now wrapping your text tags.

I think most acceptable magazines are around 150 MB per issue. This would be a lot higher if your weren't using the PDF solution we have in place. For example, mags like Wired are upwards of 300mb per issue.

Using the annotations in preview will not take you out of the App, you just have to make sure you create a web tag that will act as the container for the web sites to load. This is all in this tutorial: http://content.rarewire.com/wordpress...

To launch a youtube video, just use the tutorial here: http://content.rarewire.com/wordpress...

Instead of using the "file" attribute for your videocontrol, use "url" (http://content.rarewire.com/wordpress...)

If the video in question is stored locally within the WIRE project then it will increase the size of the downloaded App but the size of the video. This of course makes the video reliable. Not sure what you can do to slim down to video without suffering in the quality department. It sounds like you have gotten it down to an acceptable size at 25 mb.

You could opt to load the video from a URL and save the download size. This would make your video dependent on an internet connection however, so that is something to consider.

Thanks Gavin,

Sorry for the late response to this ticket. We are aware of the issues with the margin features and service tickets have been created to keep track of them.

I apologize for the inconvenience and hope these get resolved soon.

Thanks for the question.

This can be accomplished in a variety of ways using WIRE.

Think of your nav bar as simply objects nested within objects, your background could be a panel or an image with attributes such as valign="bottom" and background="ff0000"


<panel name="navbar" height="100" width="100%" background="ff0000" valign="bottom">
<image name="nav-button1" source="button1.jpg" "onclickup="page1action"></image>
<image name="nav-button2" source="button2.jpg" onclickup="page2action" rightof="nav-button1"></image>
<image name="nav-button3" source="button3.jpg" onclickup="page3action" rightof="nav-button2"></image>
<image name="nav-button4" source="button4.jpg" onclickup="page4action" rightof="nav-button3"></image>
</panel>


Then use images or panel objects nested a children to your nav bar to serve as your buttons.

Check out our documentation on the panel object to give you an idea of the actions you can trigger when a user selects your "buttons"

Because WIRE is so flexible you don't have to rely on "standard". You can design images to serve as buttons and backgrounds to make your nav bar look any way you want, while still remaining native.

Good luck!

When you say "post" I am assuming you mean a block of root elements from a feed?

The most common way to establish this scenario is to create a class that builds an output that is similar to a complete set of information (image, title, body text, etc.) then within each class you call the pieces of information from the feed that you would like to see. IN some cases this does require that you broaden your query to pull in an entire node or root element that contains all the info you are looking for.

If you want to access a particular item then you can add a param for datasourceindex to your class. this will return the number of items in a feed. From there you can identify if statements and such that can whittle down the feed to the particular items you desire.

This can also be accomplished by using advanced xpathing in your query to only return a subset of the feed. Have you checked out the link from the tutorial on xpathing? http://www.w3schools.com/xpath/xpath_...

Here is an example of datasourceindex in a class: http://content.rarewire.com/wordpress...