2012/11/1 Jürgen Schmidt <jogischm...@gmail.com>

> On 11/1/12 11:09 AM, Lei Wang wrote:
> > I like beveled tab option.
>
> me too and it was already planned in the past to extend the existing
> solution.
>

+1 to Beveled tab option.


>
> >
> > One question, what kinds of content should be put into the sidebar? A
> > navigator window or a style list window should be put into sidebar as a
> tab
> > panel.
>
> I think that are good examples and Symphony has used it in a good way
> too. But I am also looking forward to make more more use of it to via
> extensions and integrate in other systems. It can be a file browser on a
> CMS  where you can checkin/checkout files, can share files, etc.. It can
> be a property SideBar as we know it from Symphony.
>

property sidebar is a good candidate to implement in phase I. No need to
migrated every thing from Symphony sidebar, but start from some frequent
used buttons.
Another candidate we can consider maybe clipart/gallery.
And agree that we should provide interface for extension development.

I can see it is a big feature that requires a lot of UX/development/testing
effort. So I suggest to create a wiki under 4.0 planning
wiki<https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning>to
consolidate and trace all related tasks and action items. We may also
need a branch to start ASAP.

- Shenfeng Liu (Simon)



>
> A SideBar in general is smooth and nice way to integrate in the office
> UI and provide fast access to new interesting features. And last but not
> least to make use of wide screen displays ;-)
>
> Juergen
>
>
> >
> > On Thu, Nov 1, 2012 at 4:59 PM, Kevin Grignon <kevingrignon...@gmail.com
> >wrote:
> >
> >> Hello All,
> >>
> >> I've been exploring design alternatives for adding navigation tabs to
> the
> >> docked task pane.
> >>
> >> See:
> >>
> >>
> http://wiki.openoffice.org/wiki/AOO_UX_Design_Exploration_-_Docked_Task_Pane_Container_-_Tab_User_Interface_Design
> >>
> >> Capture any thoughts or feedback in the discussion section of the wiki
> >> page.
> >>
> >> Thanks,
> >> Kevin
> >>
> >
>
>

Reply via email to