It looks like this feed changed a little. Instead of "author" it now should be "dc:creator".

Looking at the feed itself (view-source:http://feeds.arstechnica.com/arstechn...) it looks like they define itemposttime as "pubdate".

I will tweak the tutorial. Thanks.

Thanks for adding me to your portfolio, but I do not have permission to access the wire editor, you will need to grant me "build" permissions.

:)

Nothing here really looks that crazy. Would it be possible for you to add Adam and I as collaborators to your App Project in the Studio so we can see first hand?

ajones@rarewire.com
icahill@rarewire.com

Thanks.

As far as the shadow issue, you might try adding an attribute of bounces="yes" This will prevent content that is smaller than the viewport from "rubber banding". Will also "snap" scrollable areas that are larger than the viewports. This will only work on Wire Engine 1.2 and it not yet available in the current version of Fusebox you have, so if you want to see it working, you will need to build an Ad-Hoc and install it on your device.

We should be submitting the new version of fusebox to the App Store this week.

Remember that this example above might not be precisely copy and paste, you will have to add your own names and assets. If you are still having problems getting it to work, you can email me at community@rarewire.com.

Thanks

Let me run some tests and I will get back to you. Imagestrip isn't widely used, so I want to make sure it doesn't have a bug.

Steve,

Unfortunately the pager tag doesn't support landscape orientations settings at this time, meaning that a pager can only be set to one direction at a time.

There are some things you can do to get around this though. I know in the past we have simply created 2 pagers and kept one off screen using xpos and ypos. Then using lxpos and lypos, move one into place and one off screen for each orientation.

Also I noticed in your example that you have the panel wrapping text. I hope you just did this for the example since text can't live outside of a tag like that.

Until you actually have content, it is probably a good test tool to add the background attribute to your panels. This will let you make each page a different color to test that they alpha on ok.

ha, taste of my own medicine. darn <code> block!

Remember to use HTML to get your code to display: http://community.rarewire.com/some.html

What you can do to fix this is to define what the alpha is for your pages upfront. You will want to do a couple of things:

(panels require a height and width to be defined)

<panel name="page1" height="100%" width="100%" alpha="1">Page 1 Content</panel>
<panel name="page2" height="100%" width="100%" alpha="0">Page 2 Content</panel>
<panel name="page3" height="100%" width="100%" alpha="0">Page 3 Content</panel>
<panel name="page4" height="100%" width="100%" alpha="0">Page 4 Content</panel>


the second thing you want to do is tell the wire which page you want to display on load. use your existing action and add the attribute oninit="yes"

<action name="showPage1" oninit="yes">
<alpha value="1" time="1" target="page1" />
<alpha value="0" time="1" target="page2" />
<alpha value="0" time="1" target="page3" />
<alpha value="0" time="1" target="page4" />
</action>

This will tell the wire to run this action on launch.