Viewer 3.2 UI JIRA

More people are trying-out the new FUI (apparently “Flexible User Interface”, and not “phooey” as someone jokingly insisted!) in Viewer 3.2, and some interesting JIRA are starting to appear.

If you’ve made the hop, you might want to consider taking a look at some of these and adding your support to any you agree with (remember to WATCH rather than VOTE – or do both to be on the safe side!):

  • VWR-20738: add ability to organise buttons in Customise Toolbars floater
  • VWR-27209: a Navigation bar only option to top bar of UI
  • VWR-27222: add Estate & Statistics Bar buttons and include multi-use separator in Customise Toolbars
  • VWR-27318 / VWR-27330: provide the option to use either the toolbars or the Sidebar
  • VWR-27358: allow the Chat Bar and an “IM Bar” to be docked, as if a button-like element, to the bottom bar area
  • VWR-27388: make any menu option draggable to the button bar
  • VWR-27448: recover the ability to dock windows at the edge of the screen and have them behave like tabs
  • VWR-27455: make the button bars on Viewer 3.2 dockable to top/bottom or right/left (depending on the edge) and not only on the middle
  • VWR-27457: create a “Quick Preferences” button for rapid access to frequently used preferences
  • VWR-27463: add Picks, Places, and Destinations to menus
  • VWR-27599: some floater window sizes and positions are sometimes reset to default after a crash, and all are on viewer update

While the following are not strictly Viewer 3.2 related, some may feel they still apply:

  • VWR-26688: allow notifications to be positioned to a different area of the screen

Note that I don’t pretend that this is an exhaustive list, nor have I included any JIRA for 3.2.0 through 3.2.2 marked as “fix pending”. Finally, JIRA listed above should not in any way be taken as a personal endorsement on my part – they’re simply what came up in search & while perusing the results!

Update 17th November

  • Adding EXP-1449 left click drag to control avatar not working, when “single click on land” action set to “move to clicked point”.

8 thoughts on “Viewer 3.2 UI JIRA

  1. Alternatively just install Firestorm LOL
    As nearly all those complaints are standard on the Phoenix FS viewer 🙂
    In fact as i read this blog, i was thinking a Firestorm user just wanted his favourite things from Firestorm adding to the Linden viewer, so created lots of JIRA

    /me Goes off singing….. Hong Kong Phooey number one super guy!! Hong Kong Phooey quicker than the human eye!!


    1. As a confirmed Firestorm user, I’m keen to see how the new UI is implemented in FS. I understand the team now have the code in their repository. There’s a lot FS already covers, as you say, and things like a sticky chat bar could well end up implemented in FS ahead of Viewer 3.2!


      1. I also use FS and im finding a few bugs that i hope are fixed, along with the obvious of being able to upload mesh and the integration of social networking such as twitter.
        As it stands…. and for the first time in a long time, i think the Linden viewer is ahead on point right now.
        For a long time Emerald, Phoenix and Firestorm users, always had bragging rights over the Linden official viewer users regarding extra gadgets etc.
        the gap has closed!
        Coming from someone whos always used TPVs this is bold statement


        1. I have to agree that the gap is closing.

          I tend to use Viewer 3.2 a lot more than I did previous versions of the “official” Vieewer – even if performance still isn’t up to scratch compared with something like FS. There are some issues I’d really like to see sorted in the UI: having the chat bar “sticky”; being able to close the chat bar on tapping ENTER; integrated chat & IM; greater flexibility of placement if toolbar buttons (VWR-27455) and inclusion of a “separator” to allow in-use buttons to be grouped.

          That said, I can’t see myself converting; Firestorm has tools and capabilities that do still make using it a joy, and these may never find their way into the official Viewer.


  2. Depending on how LL might interpret these things, if they all get pushed into the next viewer, they might actually be able to pull in some of the majority who hates the LL viewer.

    FPS performance, crashes, and such have never been an issue for me, but how the UI looks and is implemented makes a huge impact on usability. V2 was horrendous, and v3 was implemented to pull away from the v2 fiasco – So far, not bad…but also not as good as v1.

    Still blows my mind that they thought they could get rid of the docked chat bar (whilst they’ve also removed keyboard shortcuts for chat, making chat history harder to pop up & not sticky, making notices insignificant, and making IM’s hard to see), isn’t this a social-centric game? They seem hell-bent on eliminating the in-world social aspect, while pushing for external social aspect (facebook, twitter, online profiles, etc.)


    1. Hence the TPV Policy & TPVs – give users a choice without the headache of maintaining a totally unmanageable code base that tries to please everyone :).


Comments are closed.