OK, thanks Justin. We'll give it a try ourselves when the bug is fixed and get 
back to you if it doesn't work :-)

Thanks
John

On 7 Oct 2010, at 13:44, Justin Obara wrote:

> Hi John,
> 
> So in your diagram you have two examples containing several rectangles. Are 
> these rectangles the columns or the reorderable elements? If they are the 
> columns, it should work after we fix the bug I had mentioned. However, if 
> they are the reorderable elements, I'm not sure, since some of them span 
> across columns. If you have any sample markup that you could provide us with, 
> we could try it out and see what happens.
> 
> Thanks
> Justin
> 
> On 2010-10-06, at 1:35 PM, John Norman wrote:
> 
>> Thanks Justin. I have activated a watch for that JIRA. But I think I was 
>> asking a more ambitious question (hence the comment about perhaps being out 
>> of scope). The sketch below shows some of the widget layouts I was imagining:
>> 
>> J
>> 
>> <Document.pdf>
>> 
>> On 6 Oct 2010, at 14:14, Justin Obara wrote:
>> 
>>> Hi John, 
>>> 
>>> Sorry, the layout reorderer does not currently support stacked columns. 
>>> There is a jira filed for this ( 
>>> http://issues.fluidproject.org/browse/FLUID-3089 ). 
>>> 
>>> Thanks
>>> Justin
>>> On 2010-10-06, at 5:42 AM, John Norman wrote:
>>> 
>>>> I have a general question that may be out of scope. The illustrations and 
>>>> the work to date have all used a column layout. Is the reorder capable of 
>>>> working with multiple sections, e.g. a 3 column section below a one column 
>>>> section?
>>>> 
>>>> John
>>>> 
>>>> On 5 Oct 2010, at 17:36, Jonathan Hung wrote:
>>>> 
>>>>> Hi everyone.
>>>>> 
>>>>> Attached is an illustration of a proposed update to the Layout Reorderer 
>>>>> demo.
>>>>> 
>>>>> The notable changes are:
>>>>> - the use of a locked icon to indicate locked content.
>>>>> - addition of instructions and description of usage.
>>>>> - a top "drag bar" to movable content.
>>>>> - an asymmetrical layout bearing resemblance to a website with 2 sidebars 
>>>>> and a main content area.
>>>>> 
>>>>> Accessibility question:
>>>>> - How is this demo accessible to screen readers? I feel that the feedback 
>>>>> will need to be descriptive in order to convey the proper ordering and 
>>>>> relationships of objects as they are moved between columns.
>>>>> 
>>>>> Questions:
>>>>> 1.  Do you think locked content should have a more distinctive appearance?
>>>>> 2. What is your opinion of using a lock icon versus having the words 
>>>>> "Locked"?
>>>>> 
>>>>> Implementation question:
>>>>> 3. The lock icons in the content area will be implemented as background 
>>>>> images as to not interfere with ATs (in effect be invisible to screen 
>>>>> readers). However, the lock icon in the instructions will be "seen" by 
>>>>> ATs. It is potentially confusing that the instructions reference a lock 
>>>>> image, but the rest of the demo does not as far as the AT is concerned. 
>>>>> How should this be handled?
>>>>> 
>>>>> 
>>>>> Thoughts on the overall design and comments to the above questions are 
>>>>> welcome!
>>>>> 
>>>>> - Jonathan.
>>>>> 
>>>>> ---
>>>>> Jonathan Hung / [email protected]
>>>>> IDRC - Interaction Designer / Researcher
>>>>> Fax: (416) 977-9844
>>>>> 
>>>>> <Reorderer.png>_______________________________________________________
>>>>> fluid-work mailing list - [email protected]
>>>>> To unsubscribe, change settings or access archives,
>>>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>>> 
>>>> _______________________________________________________
>>>> fluid-work mailing list - [email protected]
>>>> To unsubscribe, change settings or access archives,
>>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>> 
>> 
>> _______________________________________________________
>> fluid-work mailing list - [email protected]
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
> 

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to