Chew Choon Keat

I've setup a repo to test with bad extensions, with pull requests layered on top to confirm the fixes work https://github.com/choonkeat/elm-element-navigation/pulls Feel free to complicate the dom and app logic...

The filenames of an upload is largely inconsequential. Every upload is given a unique ID, and is rightly treated as a new file. (Even if it is "an update profile...

To use the example scenario above > 4. User load profile, your app shows `` - this is a db lookup on your app, to retrieve and render the html...

> the client already knows the unique URL for the image this will always be the case. your desktop/web/mobile app will always be managing content e.g. list of users (name,...

#### Proposal 1 ``` ruby Paperclip::Thumbnail.new(File.new("dog.png"), geometry: '1000x', convert_options: "-crop 296x399+582+79") ``` Should give you what you need. resize (enlarge) the image to 1000px wide, then crop `296x399` with offset...

For Proposal 1, your app now has to remember the crop coordinates. Unless that's part of the requirement, I'd much prefer not storing them in my app. Proposal 2 is...

The geometry options section need to be escaped, so it will be `http://server.com/view/path/crop%3D100x100%2B234%2B120%3Bresize%3D100x300/dog.png` I think if we look for `=` we don't have to break backwards compatibility. i.e. moving forward,...

FYI I've had success implementing client side cropping with https://github.com/fengyuanchen/cropper and uploading the base64 data via the new `/upload_url` #35

If your app is managing/storing the crop coords info, then upload without crop for attache to store; your front end applies the crop instead

Yup. Hope that works for you?