Viewer 2: Finally starting to show promise

Viewer 2.2 is now out and available – and it is finally starting to look like something many people can live with.

The ability to customise the interface has long been a bugbear in all iterations of the Viewer; and while we still cannot reasonably expect to be able to fiddle with things to the Nth degree, the ability to re-order things like the on-screen buttons is a step forward. We don’t all work the same way, we don’t want to do the same things – we’re not all right-handed or left-handed, much less all left-, or right-brain dominant – so this is going to help many reorganise things into a way that they feel is more logical and easier to use when it comes to their needs. Kudos, at last.

Similarly, the ability to float options away from the sidebar is a good step forward – although it seems from comments that the sidebar still remains the focal-point of the “new” Viewer, and not the in-world view; so my personal pet peeve with the Viewer remains.

It’s also nice to see the promised two-way “dialogue” between TPV developers and LL start to yield fruit, with tools we’ve seen commonplace in several TPVS – texture alignment, Google-powered translation, etc., – finally entering into Viewer 2; may snowstorm result in much more of this – and in both directions.

It’s also nice to see some major idiocy in the Viewer finally disappear, seemingly despite LL’s repeated refusal to initially listen and then simply drag their heels after admitting the problem(s). That parcel icons are now on by default is welcome news so is the ability to turn off scripted lighting and particle generators. Given the amount of resistance shown by LL to do the former, I wonder who took Esbee or someone outside and gave them a firm talking-to?

The reaction to the new Viewer has, overall, been positive in the comments following Esbee’s post, and there have even been some very good suggestions put forward for future improvements. I would hazard a guess that, unless said suggestions find their way into a TPV from a third-party – such as Kirstenlee’sS20, which still outstrips Viewer 2 and offers a (largely) genuine pleasure of a Viewer experience – and thus potentially into Snowstorm, I seriously doubt that they’ll be taken anywhere by Esbee et al.

Are these change enough to get me to jump ship from 1.23.5? Well, to be honest, no, not quite yet. I am curious to see if Marine updates her initial cut of the RLV-enabled version of Viewer 2 she put out on the 10th Oct, and which appears to be based on the Viewer 2.2 code as it stood then; whether changes were made to the base code between the 10th and yesterday’s release is beyond me. If she does, I’ll give things another look; but I’m still very attached to Phoenix – not just because of RLV, but because it still offers capabilities that are extraordinarily handy when keeping an eye on sims and tenants. These far outweigh the bells and whistles offered by Viewer 2, such as media-on-a-prim (which itself seems to have fizzled out like a wet firework rather than illuminating Second Life like a night-time space shuttle launch). As to the really useful features of Viewer 2: Alpha Masks, Tattoo Layers – they are already in the majority of TPVs, and so are hardly an encouragement to make the jump elsewhere.

So where is my incentive to move? Multi-attach / multi-wear? Very nice, but not actually essential, given how long I’ve lived without them – and certainly not worth a trade-off with that bloody sidebar barging out onto my screen without me cluttering-up world-view real estate with minimised windows torn off from it. And then we have the biggie: does search actually work in Viewer 2 now? I’ve honestly lost track of that situation.

Which really means my personal analysis of the latest release is really, “Congratulations, LL on getting a new usable Viewer out there for people. Pity you opted to push the code through the door eight months premature; you’ve still left yourselves a big mountain to climb in the eyes of the more cynical as a result of that mistake. But – well done, all the same, for keeping to your promise vis Snowstorm”.

Out with the globe, in with the storm

Note: Following this post being published, Esbee Linden made a formal blog on the subject on August 17th

In his address at SLCC 2010, Philip made mention of “standardising” the viewer platform. At the time I was curious as to what this might mean and asked a speculative question or two. Later, during SLCC 2010, Q Linden (whom I hope makes a full recovery from his stroke) and others gave more insight into what is going to be happening, and Oz Linden posted an announcement on the opensource dev list (thanks to Argent Stonecutter for the link).

Q’s opening of the SLCC presentation was somewhat enlightening, in that it confirmed many people’s views that Viewer 2.x proceeded along a development path that was simply far too rapid. In fact he candidly admits that it was developed and rolled out to meet a given schedule, rather than when it was “ready” (in November, for example, a meeting was held in which the “to do” list of outstanding work on the Viewer was cut down to a list of things that could be done in the remaining time frame prior to the release of the Viewer.

He also admits that Linden Lab erred when preparing the ground for Viewer 2, in that they didn’t create sufficient use cases to reflect how the Viewer is actually used in-world (that LL needed to “invent” user types in order to build the use cases in the first place also surprised me. After all, what are we out here, if not users?). The upshot of this is an admission that the overall capabilities of Viewer 2 are too narrowly focused.

This may sound like a “well, duh!” statement – but I think it fair to say that such an admission from the development team is somewhat refreshing. It’s not often the Lab or its employees own up to mistakes, and Q’s comments do add up to a strong admission of  having erred, and a hint that the lesson has been learned internally, “For marketing reasons we felt we wanted to keep it secret and we wanted to release it in a kind-of ‘ta-da!’…I think you won’t be seeing any more of that sort of behaviour from us any more! Yes, I hear the applause, thank you!”

Following this, Esbee went over the new methodology for Viewer development – Project Snowstorm, which has the core aim of rapid, effective deployment of new features and functionality. Essentially, and as hinted at by Philip, this will be achieved through meeting three goals:

  • Weekly, visible progress on the Viewer – which not so much is focused on weekly releases per se (although that is something Philip indicated he’d like to see), but more a case of making the development process more visible too all, including users being able to attend development meetings
  • Improving the user experience – hitting Philip’s requirements of Fast, Easy, Fun (a slogan I *still* loathe, but there you go)
  • Revitalising the open-source community

It is this last point that is the most interesting and – if carried through  – marks a radical change in Viewer development; one that would seem to have many potential benefits – and not just for Linden Lab.

The core of this new approach is that Viewer development will be somewhat streamlined, with LL themselves working on specific elements of the Viewer while leaving things open so that third-party developers can engage directly with the LL team and take on development of a given aspect or function within the Viewer, and developers with existing fixes or functions that could benefit the Viewer can deposit their work with the team for potential integration into the Viewer.

This effectively means the end of Snowglobe, the open source “version” of the Viewer code.  To quote Oz Linden, “The main Linden Viewer is now completely open source…the source code is available on a public repository…NOW!” What is more is that this repository is to be the central “integration repository” where all code from Linden Labs will go prior to integration into the Viewer.

Alongside of this is the re-licensing of the code from GPL to LGPL – which, if I am understanding things correctly, means that it will be both easier to incorporate the Viewer code into other Viewers (I assume those that can be used on OSGrids and the like) and – particularly from LL’s point of view – will make the licensing of the code for use in “closed” third-party Viewers significantly easier, potentially attracting other professional organisations towards developing their own Viewer systems without the “stigma” of being associated with open source code. Again, given LL’s stated desire to drive SL onto more mobile platforms – tools such as the iPhone, Droid, the iPad, etc. – this would seem to be a good move, as it will allow third-party organisations with the expertise LL lacks to develop the kind of functionality such tools will require if people are to use to them to access SL and use it for more than just chat and IM.

It’s not just developers who have the chance to be more directly engaged with Viewer development either. AS Esbee said, users will be able to get involved as well: iterative releases will be available bi-weekly or us to use and feed back upon, and even daily releases, or “project releases” covering specific features under development will be made available and user feedback encouraged.

From a non-technical perspective, this does seem to be a logical approach, and in some respects, it is a shame that, when they opened the Viewer code to the community, LL didn’t show foresight and put these measures in place then. Of course, the devil will be in the details – and there is much that will serve as either proof of the pudding or still needs to be addressed  / clarified. In listening to the presentation, a number of points occurred to me, some of which were echoed by others in the Q&A session.

One issue that springs to mind is who will, in the final analysis, determine what is “right” for integration into the Viewer, and will other agendas overrule the core goals – such as making SL Fast, Easy, Fun? “Linden knows best” has been very much a part of the Lab’s culture and has been seen time and again, particularly with the arbitrary closure of JIRAs or the turning of a deaf ear to valid user requests.  With the best will in the world, cultural behaviour is the hardest thing to fix in an organisation.

An extension of this concern comes down to user input actually being heard and acted upon. Q openly admitted at the start of the presentation that LL erred with Viewer 2 in not creating enough user cases on which to model the viewer. Now they seem to be swinging to the opposition end of the pendulum swing: seeking too much user input. There are – as Q and Esbee acknowledge – many diverse uses for SL, and as such diverse sets of users have diverse needs. Some are going to apposite in their aims, others opposite. How are filters going to be applied to stop all these calls simply swamping Snowstorm with the result that the individual internal dev teams beyond them simply cherry-pick or (again) turn a deaf ear?

So where does this leave the current crop of TPVs? Oz was pretty unequivocal on the matter: the Viewer 1 code base will not be developed any further by Linden Lab (Q also touched on the need to depreciate 1.23 in the future, simply due to security issues). Therefore, with the Viewer 2 code base becoming publicly accessible, the view seems to be that TPVs will be encouraged to continue – as well as give input to the new project – but will be expected to migrate to the Viewer 2 code base.  Certainly, there doesn’t seem a move on hand to proactively “shut down”  TPV development, but it is going to be interesting to see how this moves forward and who engages through Snowstorm as is intended, and who simply continue to work on their own Viewers utilising the now-available Viewer 2 code.

Overall, this move strikes me as positive. *IF* LL can carry through on this with the necessary internal cultural changes and if we all, developers and interested residents alike, engage with Snowstorm and LL constructively, positively and openly on our own part, then there is no reason why this project should give birth to something very worthwhile and which benefits us all.

Wishful thinking and Viewer 2

On Monday, NWN confirmed that Tom (T Linden) Hale  had gone from Linden Lab. There was some confusion over this, as (at least for some of us) his in-world Profile (alongside that of Cyn (Linden) Skyberg, also laid-off last week) remained accessible when the likes of Pink Linden’s Profile poofed almost as the news of the lay-offs hit the wires.

Hale’s departure has prompted speculation that Viewer 2.0 is about to go the same way.

All I can say is, guess again, kids.

The basis for the speculation is that Hamlet, in his piece, cites “sources” who suggested a link between Hale’s departure and the “poor performance” of Viewer 2.

Now, whole I’m no great fan of Viewer 2 – I think it was released far to early in its development cycle and with far too many flaws that could have easily been addressed if the developers had been allowed to engage with residents properly and constructively as the Viewer went into the initial “closed Beta”. But, that said, I don’t go along with the idea that the Viewer is going to be scrapped – or even that it is a failure.

The fact of the matter is, it is still far too early to judge the Viewer dispassionately. This is for a number of reasons – some of which I’ve touched on before, but are worth repeating:

  • The viewer was released too early and with to many basic flaws / bugs (the god-awful sidebar behaviour; the myriad of search issues, etc.); as such, it was never going to find favour or popularity among a user base that has time and again proven itself somewhat “anti” change in SL whatever the colour of said change
  • The development / release cycle of Viewer 2 is improving; more to the point the likes of Kirstenlee Cinquetti are demonstrating to LL just what needs to be done to the Viewer 2 user interface to enable it to gain a broader foothold. And Linden Lab is actually listening. The 2.1 release addresses many of the UI shortfalls contained within the initial 2.0 releases and are, in themselves, making Viewer 2 far more user-friendly. What’s more they come on top of changes quickly rolled out in response to the initial “backlash” against other elements of UI functionality, demonstrating the LL are trying to get the balance right. So long as this continues, Viewer 2 will gain wider use
  • The Viewer, together with the New User Experience was intended to be the vanguard of a drive to generate a marked increase in new sign-ups. However, neither can exist in a vacuum – for either to have a major impact on the rate of flow of new users joining SL, they need to be coupled to more aggressive promotion of SL by Linden Lab. This hasn’t really happened. Ergo, both the Viewer and the NUE exist (again, as I’ve said before) in some kind of Costner-esque la-la land of “if you build it, they will come”.

As such, it is hard to see Viewer 2, even the degree of time, effort and money invested in it to date is simply going to vanish as a result of Hale’s departure. Rather the reverse would seem to be the case – as recent blog posts have indicated – the release cycle for Viewer 2 is going to increase, again indicating it is here to stay. I’d also lay odds on it being the foundation for the new “browser-based access” to SL that was announced alongside of the restructuring.

If Hale’s departure was connected in any way with the “poor performance” in Viewer 2’s uptake, I can only assume that it was because he was the one selected to fall on his sword (or tripped in the direction of his sword). Again, we’ve seen very little aggressive marketing from Linden Lab when it comes to getting users through the doors – either utilising Viewer 2 or the New User Experience. Some suggest the total growth in sign-ups since the release of both has been around the 50K, which is not a huge amount given SL’s user retention figures – and much of that influx seems to have been off the back of James Cameron’s Avatar rather than any sustained marketing strategy on the part of Linden Lab.

That there has been no sustained strategy (or any real marketing uptake – when was the last time Catherine (Smith) Linden was in the limelight?) tends to suggest that if Viewer 2’s take-up is already being looked at so critically that a sacrifice was warranted…then one cannot help but roll the word “scapegoat” around in an idle fashion.

Indeed, I’ve often found it interesting that LL have never considered the position of Director of Marketing as being a executive management post.

But to come back to the point: no – whatever the reason for Hale’s departure (including the merging of departments that effectively made his role somewhat redundant), it is not indicative that Viewer 2 is going anywhere other than forward in the immediate future.

Viewer 2 – getting there?

Linden Lab have released an “Alpha” of Viewer 2.1.

They’re making progress it seems – calling the release “Alpha” rather than trumpeting it as an “almost ready Beta”. Who sez they don’t listen?!

On a serious note, the new release (which admittedly, I have yet to download and try) brings with it several much-needed improvements – such as the bane of my life, the Sidebar, now “overlaying” the world-view as an option, rather than shunting it rudely off to the left. Why anyone would want the latter option constantly shattering their experience, I’ll never understand; but at least we now have the long-overdue option to get rid of it for something altogether smoother.

They’ve also finally got the message about camera controls – recombining things into a single pane (why, oh why were they ever split-off in the first place?), and they’ve made the bottom button bar somewhat more customisable to meet the needs of experienced users.

All this is very much to the good – although again points to a broken train of thought somewhere along the development trail, as all of these features should have been there from the get-go, and thank heavens for Kirstenlee Cinquetti for demonstrating to LL that all this and more could have been done from the get-go via her (still) infinitely superior S20 viewer.

Viewer 2.1 brings us a step closer to OpenID authentication for SL-related services. About time to.

A novel feature being introduced to Viewer 2.1 is Voice Morphing. Clearly, despite claims that we’ve already clocked up 28+ billion years of chat on Voice, not enough of us are using it. There are many reasons for this – some of which I’ve pointed to in that post.

Voice Morphing is an attempt to resolve some of these issues by providing the means for people to “sound like their avatar should sound” – with a range of robotic, furry and other voices – including the option to sound like a member of the opposite sex.

I have to admit that I’ve avoided Voice in the past in part because I simply don’t want my mental image of the people / creatures I’m interacting with shattered by hearing the real voice behind the avatar. It’s not the only reason I’ve largely steered clear of Voice after some early playing (and using it at a couple of OH meetings in-world), but it is one. As such, I’m going to be curious as to how the morphing tool is viewed / taken up.

On the one hand, I can see it being a lot of fun; on the other, I can seen some trying to use it for drama purposes (anyone using a female avatar and one of the female voices in place of their own must be a guy, for example). On the third hand (yes, I occasionally have Beeblebrox moments) I can see it not making an iota of difference all ways around.

The main reason for presenting the third hand is simply because a) people are slow to change their ways, and in terms of rp, where this has the biggest potential use, if it is not adopted by the many within a particular rp environment, the few won’t bother either; and b) it is, at the end of the day, a subscription service; and while “only” about $3 a month (L$750), given LL’s recent track record, doubtless many will avoid it simply because of the pleasure they’ll have in not giving LL more of their hard-earned  pennies. Especially when the voices are pre-packaged. If you only want a female voice – then it is “only” $3 a month. But if you vary from, say a male gladiator to a sci-fi robot to a furry according to your mood, then you’re looking at $9 a month to give all your forms a voice.

Mind you…I can see the MOTD promotion for Premium Accounts now: “Upgrade and (homes, support, blah, blah)…offset the cost of your in-world Voices with weekly stipends!”

All-in-all, however, the moves being made with Viewer 2.1 are welcome.

Viewer 2: Getting the message

Esbee Linden posts about the forthcoming Viewer 2.1, and makes something of a ballyhoo over it. 400,000 downloads is a surprising figure. Emerald has been around a while and yet people question the Modular Systems’ claim that in excess of 70,000 have downloaded it. Given Viewer 2 has been with us less than three months, 400K is a very surprising figure. Nevertheless I expect at least one fanboi will be looking through Hubble and praising the figure for all its worth and using it as further “proof” that there is nothing wrong with Viewer 2.0….

Beyond the hype, however, there are some telling statements from Esbee. Most interesting is her list of forthcoming attractions, namely:

  • Adding individual volume controls for Shared Media objects.
  • Customization of the bottom bar, so that you can quickly access the features and functionality that you use most often.
  • Updates to the camera and movement controls, so we can allow you to pan and orbit your view of Second Life at the same time.
  • Adding the ‘Build’ option back to the right-click context menu.
  • Fixing the bug where CTL-ALT-F1 does not hide all the Viewer UI as it should. This fix should solve a lot of problems for our machinimists and photographers.
  • Adding a preference that allows users to control whether the Side Bar opening resizes the world or slides over it.

Frankly, while it is good news that the above are all being added to Viewer 2.0 – the fact remains that they should have been there from Day One. Period. While Viewer 2.0 is primarily aimed at new users who, granted, come into SL with a raft of different expectations than the rest of us, the fact remains that Viewer 2.0 also has to service those of us who have been here a while – and things like the irritating camera controls, restricted build functionality, lack of cohesive access to functions via the taskbar, etc., simply fail to consider, much less address the needs of the experienced user.

Similarly fundamental bugs such as the Sidebar jarring the in-world view to the left, the failure of CTRL-ALT-F1 should have been picked up and addressed long before the Viewer went to public Beta (and I have it on good authority that both of these issues were repeatedly raised during the closed beta testing, so absolutely no excuses here).

Performance issues are something I’m not going to comment on – they’re an accepted pitfall in an environment as dynamic as SL, and something somewhere is likely going to cause issues and problems along the way; as long as LL stay on top of them, that’s all that matters.

The Avatar customisation is also interesting, although potentially it will push Viewer 2.0 further from those wishing to stay with a 1.2x code base for their Viewer and put more of a load on TPV developers as they try to maintain and fix establish 1.2x code and integrate / back-engineer the newer code into their products. Even so, a greater flexibility for clothing layer use is to be welcomed.

Now, if they really could get the new search tool sorted out, then we might be approaching a waypoint to celebrate; but I’ll let Ciaran Laval give you the low-down on the situation there.

Viewer 2.0 gets Starlight & I tweak KLee’s sidebar

Not too long ago, Tom (T Linden) Hale passed a comment in one of the multitudinous Viewer 2.0 threads to the effect that the skin of the Viewer itself can’t really be that radically changed because it is too much a part of the of overall viewer (and had I the patience to wade through the blasted flog, but patience and the official flogs don’t seem to go hand-in-hand).

At the time he mentioned this – back when the “beta” had just started – the comment struck me as odd. The majority of the Viewer files are XML…the folder structure of Viewer 2.0 isn’t that different from 1.2x – so wher’s the problem? However, I’m also not a programmer, so what on Earth do I know?

Now, Hitomi Tiponi has issued “Starlight”, a new skin specifically for Viewer 2.0, and what is likely to be the first of many such efforts.

Starlight brings together several of the tweaks developed by Alexandrea Fride and others, and presents them in a skin design that – while keeping to the overall 80’s approach LL opted for with the Viewer – lightens the basic colour scheme up somewhat. Avi Arrow has further tweaked Hitomi’s design to make the Sidebar somewhat less intrusive  so it doesn’t block the top and bottom right HUD attachment points (or the mini-map, if you prefer having that open on the top right of the screen). I’m borrowing the following screen shot from Avi to demonstrate both Hitomi’s skin and the sidebar revision.

V2.0 “Starlight” Skin with Avi Arrow’s modified Sidebar (Credit: Avi Arrow)

Notice the additional buttons and other tweaks to the interface in the image above.

The Starlight skin can be downloaded here, and Hitomi provides full installation instructions for Windows, while Mac instructions and Avi’s sidebar mod can be found in the flog thread on the skin.

Elsehwere, KirstenLee Cinquetti continues to revise and improve her take on Viewer 2.0, and the latest – S20.12 removes the sidebar completely from the screen until such time as it is need. Instead, there is an additional button in the toolbar area, which opens a mini-selection bar when clicked, which can be used in turn to display elements of the sidebar in their usual place. It is not elegant – but it does reduce the intrusiveness of the sidebar considerably.

In a tip of the hat to Avi’s idea, I’ve further tweaked KirstenLee’s sidebar so that it no longer blocks access to the top / bottom right HUD attach points, both of which I use.

My revision to KLee’s Viewer 2.0 variant

To make the changes to the Sidebar’s appearance (Klee S20, v16 or lower):

  • Close the Viewer, if running.
  • Use a text editor (such as Notepad) to open main_view.xml contained in the skins\default\xui\en folder of your KLee Viewer installation)
  • Find the section commencing <!– side tray –>
  • Within the < panel block, change the following:
    • Height=”450″
    • Top=”195″
  • Save the changes.
  • Start the Viewer – your sidebar should now be suitably resized when opened.

Klee S20 v17 and later:

  • Close the Viewer, if running.
  • Use a text editor (such as Notepad) to open main_view.xml contained in the skins\default\xui\en folder of your KLee Viewer installation)
  • Find the section commencing: <!– side panel now scales to top n bottom KL –>
  • Within the < panel block, change the following:
    • Top=”195″
  • Save the changes.
  • Start the Viewer – your sidebar should now be suitably resized when opened.