https://studio.rarewire.com/wordpress... :)

256 is the default. You should be able to change it to 512 or 128.

height="fit" will resize the text container and not the font size of the text.

try size="fit" this will resize the font to fit in the space allotted for the text container.

Tyler,

There is an 'onscrollaway' attribute that triggers anytime you move away from an item in a pager, list, etc.

Currently the gallery only supports tile tags which can be images only. This is an interesting idea to include other assets. I will log a feature request.

As far as retina support, have you tried using the 'quality' attribute on the gallery tag? This should help with your issue.

Thanks for the question.

Currently our Android publishing offering is not yet pushed to the Studio. In the meantime, you can write WIRE code in our studio that can display on an Android device by downloading fusebox from the Google Play store and viewing the app through it.

Currently any app project that has iOS checked will also be available in the Android fusebox. Eventually we will turn on the checkbox and offer Android specific settings and publishing. Until that time you can build and test on Android and if you are ready to publish an Android APK, you will need to contact us at RareWire to help you do that.

Try the Web Example in the Android fusebox again, I corrected a small error.

No, paginate only allows you to display one node at a time.

List tags do have an attribute called "step". Defines a set of objects to pass within a list. Example: If a step is set to 2, then the list will return index numbers 1,3,5, etc.

This way you could use 2 lists, one for odd and one for even results.

Ok, I see now, the last line was missing before. Sorry.

Because classes are driving your object tags, it is certainly possible to explode code into an object within another object, however it will always create the object at the bottom of the z-order of the parent. So as a best practice this isn't something that we do. As classes get complex, it is hard to predict where the second object will live.

In this case you might be okay to leave it as is, but in other scenarios you probably could crash the app if the object builds a class that doesn't fit just right.

I would recommend that you take the pager and put in it your bpanelweb class and then call your pager class there so you only have one object tag in your main block. It is much more predictable.

It looks like your 'contents' pager that contains all of the objects from the pager class is a sibling to your bpanelweb objects. Am I missing something here?