StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13657811
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-01T08:34:05.847
FavoriteCount
0
LastActivityDate
2012-12-01T08:34:05.847
LastEditDate
LastEditorUserId
0
OwnerUserId
1833003
ParentId
13210744
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I just spent a day with a partner working through this with CamanJS. Without knowing how you're constructing your view (and not knowing Pixastic at all) I'll do my best to answer. Assuming you're linking to the original image in your html, add <code>crossorigin='anonymous'</code> into the image tag: <code><img class='image' crossorigin='anonymous' data-camanheight='450' src=<%= @photo.url%>></code> This will set up the browser's expectation that the image will not come from your site's url. We found this to work for the initial image, but when CamanJS' revert() function reconstructs the image (before converting it back to a canvas element), it leaves out the header information that lets the browser know that it's ok that it is cross-origin data. So every time we reverted an image, we hit a CORS issue again. I looked through Pixastic's docs briefly, but can not advise you on whether or not you'll have a similar issue. NOTE: A super fluid experience was our priority, and we didn't want to set up a proxy, so our work-around was to keep a clone of the image tag on hand in a Javascript variable and write our own method to revert the canvas, re-cloning the the image tag, pushing one of the cloned tags into the DOM and then converting it to a new canvas element and getting rid of the old one. It ran into some CamanJS specific behaviors that made it a little 'hacky.' My partner on the project has submitted a pull request to CamanJS that retains the header info, so this may be resolved soon, making CamanJS a better solution for cross origin resource sharing. Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails set up a proxy for Paperclip images on S3?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USjeffreymatthias
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails set up a proxy for Paperclip images on S3?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.