[Libreoffice-ux-advise] [Bug 98372] SIDEBAR: Research/Reference sidebar deck

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=98372

V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Writer                      |ux-advise

--- Comment #5 from V Stuart Foote <vstuart.foote at utsa.edu> ---
Mock-up looks like a good start, you forgot to insert a Tab bar button for
switching to the Deck.

--Network connectivity--
When this Research/Reference content panel(s) be implemented as a core feature
of LibreOffice--it will be important to be able to completely disable any
external connection. That is, the mock-up should be clear to provide a "Not
Active" mode, with no Encyclopedia "selected". And any network hooks must be
silent when in that mode.

Pushing this enhancement over to the UX-advise side for design and
implementation. Otherwise if these core content panels are effective for
Writer, they would be equally effective in Impress, Calc and Draw (possibly
even Math if you connect to the right journal services).

(In reply to Yousuf (Jay) Philips from comment #3)
> > We don't actually need to do this as a LibreOffice core feature. Especially
> > as the Sidebar Deck is a perfect container to encourage extension developers
> > to build content panels against.
> 
> I guess i'd have to disagree, as extension imagine if each provider created
> their own extension, what would the sidebar turn into. It is better that we
> create the core functionality and let providers (most of which wouldnt spend
> the time to create their own extension) create just the minimum needed
> integration to enable their service to function within it.
> ...

@Jay, still believe the flexibility is needed and will attract interesting
projects to implement Sidebar based extensions. Where most extensions now
provide Toolbar or Dialog based interface, they could provide richer Sidebar
Deck held content panels of various function. Much like the work Jan-Marek is
investigating to host the WollMuxBar in a set of Sidebar content panels with
dedicated deck and tab bar launcher.

Our goal for Sidebar should be publishing an API and IDL in the SDK for control
and layout of Sidebar Deck, Tabbar and Content panels--and continuing to
develop the internal framework needed for holding state in profile (per module,
per user) and in extending ODF to carry any needed content to make the document
portable. Another discussion and subject of Design & UX preliminary survey.

Stuart

-- 
You are receiving this mail because:
You are on the CC list for the bug.