[Decapod] Updated design for thumbnails (before and after image dewarp)

Boyan Sheytanov boyan.sheytanov at asteasolutions.com
Sun Jan 17 20:08:16 UTC 2010


Sounds great!

Lets keep it simple for now.

- Boyan

2010/1/14 Jonathan Hung <jonathan.hung at utoronto.ca>

> Boyan,
>
> This is a great conversation and I think we're all on the same page.
>
> For the focus issue, I will start a new email thread on that.
>
> I think it'll be good to proceed with working in pairs of pages to start
> and see if we can add single page operations later if there is a demand.
>
> I'll start refining the wireframes now with this design.
>
>
> - Jonathan.
>
> ---
> Jonathan Hung / jhung.utoronto at gmail.com
> Fluid Project - ATRC at University of Toronto
> Tel: (416) 946-3002
>
>
> On Thu, Jan 14, 2010 at 4:51 AM, Boyan Sheytanov <
> boyan.sheytanov at asteasolutions.com> wrote:
>
>> Hi again!
>>
>> I thought things over a bit and here's what I reached at. If we are always
>> working with the two images (left and right) as a pair (that's certainly the
>> case in Capture, and it is making things easier in Remastering mode), then
>> it's better not to split the image of the page spread in two and work with
>> the grouped pair. If we have a single image, it won't be noticeable to the
>> user since he cannot work with only one of the pages. And it would simplify
>> code and markup. One point for working on the page spread level.
>>
>> On the other hand, what happens if a page spread captures the one half
>> clearly and the other is defective (imagine a thick book when you capture
>> the pages in the beginning or at the end - the page on the thick part would
>> look differently). In this case the user might want to recapture the spread
>> by repositioning the book but keep the good page. Is that making sense or am
>> I trying to be a nasty user? As for duplicates, we might persist the indices
>> of the pages that have been deleted and when the user recaptures the spread,
>> ask him to choose whether to keep the original or update it with the newly
>> captured (on second thought, that really looks kind of complex and
>> confusing).
>>
>> Not sure if we want to provide such a sophisticated interface to the user.
>> Might be a good idea to keep things simple (as in your design) as a start
>> and if there is user feedback on inabilities to deal with single pages, add
>> that feature at any later stage.
>>
>> Open to any thoughts on my chaotic ideas.
>>
>> Greetings,
>>
>> Boyan
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Decapod" group.
>> To post to this group, send email to decapod at googlegroups.com.
>> To unsubscribe from this group, send email to
>> decapod+unsubscribe at googlegroups.com<decapod%2Bunsubscribe at googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/decapod?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Decapod Internal" group.
> To post to this group, send email to decapod-internal at googlegroups.com.
> To unsubscribe from this group, send email to
> decapod-internal+unsubscribe at googlegroups.com<decapod-internal%2Bunsubscribe at googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/decapod-internal?hl=en.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100117/48f175cc/attachment.html>


More information about the fluid-work mailing list