Category: V7 Style

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”.

Quick note: A couple of other blogs have linked to this piece as a review of the new UI. If you are looking for a review, you can find mine here. This article only references the fact the new Viewer is released, and doesn’t carry any specifics.

Well, well.

After blogging yesterday that Viewer 3.2 had reached Beta – lo and behold, and with no fanfare whatsoever, it’s released!

Apparently there was a blog post about it that Tateru spotted on Monday, but it appears to have vanished into the sub-etha.

Version 3.2.0 (244443), dated Nov 3rd, doesn’t have the latest revisions that the Beta release has – there is no Destination Guide open by default, and there are no translation options on the Chat Preferences, nor does Inventory have the Direct Delivery revision (not surprising, given yesterday’s announcement). The new attach points (Neck and Centre) have yet to appear – although they are in the Beta, so expect them & translate, etc., shortly.

However, everything else I covered in my First Looks piece on the new UI is there – including the direct-to-marketplace shopping button top right of the screen which is liable to annoy many who have in-world shops.

I’m not sure when on Monday the switch-over occurred; I’ve been checking the download page daily of late (sometimes more than twice), and when I downloaded the latest Beta, the release Viewer was still 3.1.2.

Short Random Thoughts on the UI

Given we have a button-based UI, I’m not going to suggest anything radical, but here are some thoughts:

• Make the Chat  bar optionally “sticky” so that if positioned over the bottombutton area, it displays a-la V1, without the floater surround (i.e. so the “nearby chat” floater title and X to close vanish). This would:
  • Reduce screen space used by the bar
  • Allow a further V1-like feel to the Viewer, helping those moving over from V1 feel more at home
• Add more button options for greater flexibility, for example:
  • Environment settings to access the Environment Settings floater (and add sun positions as buttons on the floater)
  • Quick Preferences button, a-la Phoenix / Firestorm, that provides access to frequently used options such as the Draw distance, Particles count, Height offset, Physics and LOD sliders, etc, and WindLight presets

Button floaters were an idea that crossed my mind as well, but I’m not convinced they’d be a benefit.I hope the code is such that TPVs adopting the UI can add their own buttons easily enough.

I’m a little surprised that the improved camera controls / floater still hasn’t appeared and can’t help wondering what LL are doing with it.

Would also be nice at some point to see some form of client-side AO option included in the Viewer. TPVs have these as standard, they don’t impact on the sales of AOs (as people still need the walks, etc.). On that subject, LL, isn’t it about time the default waddle was reworked into something of a “unisex” walk?

Anyway, random thoughts aside, if you’ve not given the new UI a test, I recommend you do, even if you’re not a regular official Viewer user – it’s worth a look-see, and even if buttons aren’t to everyone’s liking, they at least allow a greater flexibility of approach to screen layout – and even allow a sort-of pseudo Viewer 1.x layout.

Updates: 9th November

Two excellent JIRAs on the UI have been raised, and they are certainly worth Watching (which, as we all know, is the new Voting – although putting in a vote as well won’t do any harm!)

• VWR-27388 – make all menu options draggable to the button areas – thanks to Pat Perth
• VWR-27455 – make button groups repositionable within the button areas (i.e. move to left/right or top/bottom edge of placement areas – thanks to Gwyneth Llewelyn
• I’ve also raised a JIRA for the addition of a “Quick Preferences” button to access specific sliders: VWR-27457.

Also on the 9th, LL’s blog post on the Viewer reappeared, together with a number of links:

• Getting Started with the New Second Life Viewer
• Customizing the New Second Life Viewer
• Additional Features in the New Second Life Viewer

This post also included information on my.secondlife.com Direct Messaging, which I covered last month.

As most know, changes to the Google translation services are coming. The v1 service was depreciated in May of this year while free access to v2 service was discontinued for “new” application requests on the 24th August (access switching over to their paid service), with all existing access to the free service started prior to the 24th August due to be discontinued from December 1st.

The Lag – via Oz Linden mulled over alternatives for a time, via JIRA, and this has resulted in two options for continuing to use an in-built translator in the future, by using either the paid-for Google Translate API, or by using the Microsoft Bing translation API.

The new translation options are not live as yet, but can be seen in the latest Development Viewer (3.2.2 (224260) or above or the latest Beta Viewer (3.2.1 244227 or above and which also has the new Viewer UI incorporated in it).

Accessing the Translate Options

To access the translation options, go to PREFERENCES -> CHAT and click on CHAT TRANSLATION SETTINGS. This will open a further floater:

As can be seen, the Google translate option is retained – but you’ll have to sign-up and pay for the service yourself.

The Bing option provides a means to continue with a free translation service, but will require you register for a WindowsLive ID, if you don’t already have one.

Using the Bing Translator Service

To obtain a Bing AppID:

• Click on the Bing AppID link in the floater. If you have a WindowsLive account and are logged in, you’ll be taken to the application registration page
• If you don’t have a WindowsLive account or are not logged in, you’ll be taken to the sign-in registration page
• Once you are signed-in or have gone through the registration / verification process, you’ll be taken to the application registration page. This isn’t a terribly helpful page, but essentially:
  • In Application Name type “bing” or “bing translator” (although I get the impression just about anything will work)
  • Fill-out the rest of the required fields and accept the terms & conditions
• Clicking SAVE takes you to your Applications page – this may take a while to load, (and may even time-out – did on me the first time) – but it should eventually display the application name you gave, and an ID – highlight and COPY this
• In the Viewer Chat Translations Settings floater:
  • Check ENABLE MACHINE TRANSLATION WHEN CHATTING
  • Click the Bing Translator API radio button
  • Paste your copied AppID into the Bing AppID field.
  • Click OK
• Close the floaters and away you go!

Note that as this is a Development Viewer, as such details on the Chat Translation floater may change between now and it reaching a formal release (work was still on-going last week).

I actually missed this at the start of the month (blame it on my birthday and work…). The new Viewer UI has taken a step closer – it’s now at Beta (3.2.1 244227), and includes all the latest revisions, including:

• The Destination Guide bar open by default
• The new chat translation options

Interestingly, the Direct Delivery Received Items section of Inventory, that was present in the Development Viewer is not present in the Beta release (nor is it visible in the latest Development Viewer release (3.2.2 (224260)). Is this an indication that LL are heed calls from merchants not to release DD before the New Year, or that the code slipped into the earlier Development releases in error?

I’ve taken it for a quick spin, and found performance to be equitable to earlier releases, and other than the translation and Destination Guide tweaks, I’ve not come across any significant changes – but it was a quick spin.

Given the UI is now in Beta and caveating the DD situation and – more importantly – the progression of the OpenGL fixes, this could be taken to mean the UI will be in a release update sooner rather than later – although admittedly not as soon as part of me thought LL might shunt it out.