Jump to content

Aphrodite Tagore

Resident
  • Content Count

    62
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aphrodite Tagore

  • Rank
    Advanced Member
  1. Thank you for the very kewel little tutorial, Suella I'll have a go at it soon.
  2. I am just thinking that PJIRA and Support ticket Queues should be visibly unified with this. I mean, for one, many of the Answers to Questions will be "Post/Vote in PJIRA Bug Tracker) and "File a Support Ticket". And, well, as a community, both of those more formal functions need to have their Quality on display, IMHO. "Make Quality Visible" is an important part of meeting the challenges in this system of a Virtual World.
  3. I thought this nerdy kid from Harvard, Mark Zuckerberg, already invented The Facebook. Well, I guess Billionaire would be an adjective that could be used for Mr. Zuckerberg as well. I am just really happy that all 10 Million of us manage to achieve 60,000 concurrent sessions, more or less. Only a little less than five years ago, concurrency of 8,000 was a major event. Of course, the grid would usually go down, but, I like to celebrate the positives. I wonder when the Browser based version of WoW will be released? I suppose maybe the tech is good enough to at least try this Viewer 2... Now that I have an uber-fast CPU (3 GHz) and other yummy parts, well, I guess l need to see the world through viewer 2 eyes. I've got a broom. OMG!! The bloody smileys work!!
  4. Welcome Rod! Nice to see more Devs and MMORPG Business people comming in house. Here is exactly what you will be meeting: Technical and artistic genius fettered by mediocrity and hobbled by lacluster Western organizational culture. Job one would be intercept the failures to compute that are in evidence by such things as this example: https://jira.secondlife.com/browse/WEB-2734
  5. I am very hopeful that they will never deprecate Viewer 1.23.5, well, at least until say, Viewer 1.27.6 is stable, bug free, and mesh enabled. Off-topic, I was in a nighclub last night, and there were people named stuff like Buffy.StJohn Resident!! /Me smirks, scoffs, says: Well, if it is that much fun, have at it. *giggles* *smiles broadly* *winks*
  6. Right then. Strides? Strewth? Had there been any strides, I would have noticed, thank you. I just closed three tickets or cases that had not gotten response. I'd appreciate your not hanging curry on me, mates. Why not get the jargon or nomenclature consistent too whilst you are making improvements? It's a cultural thing you know? And, at the heart, a bit like Watts as opposed to Volt-Amps. If I notice any strides, well, I'll celebrate with you all. Still, despite all, the technology is semi-nice and a good toy for adults with leisure time to play. I've gotten bunnies now, and they are great fun. No market for the wee beasties, but, they are fun none the less. So then, to close, one word would do best: Kaizen
  7. The only value is a product that delights and engages the customer, and which causes the customer to want to spend money for the product, and to invite friends to use the product. That must be real, deliverable delight.
  8. I have noticed that, in addition to what I have expressed, a few other Commentators are going to the thought of a top level use case choice input by the resident. There was the skinning option, and then mine and another's use case selection schemas. You know, the first few orbital missions of the united States' Space Transportation System were conducted under a configuaration in which the Flight Computer had only 4kb of RAM. The microwave radio modem was pretty warm most of the time, loading and unloding small modules and data sets sent from the surface of the earth. I just note this, as, with the advent of cheap memory, and huge PC real estate, the trend toward monolithic coding has created bloat. Developers are not so constrained nowadays with a tiny footprint on RAM. There are acres of memory that can be used to store these huge applications. I have not really considered this to be advancement of the state of the art. In the days of real microcomputing, it was absolutely essential to have only active program routines in RAM, the rest sitting on peripheral volumes and loaded, as needed, and craftily hidden and nexted in branches and loops where a user input, or a screen wipe or screen change would involve the user for the tiny delay whiile a needed module loaded in. So, with a Second Life Viewer design, we see a similar premium in real estate and resources on the client side, and it seems proper small system application modularity would help both efficiency and correctness, enabling simpler QA proceedures through easily proveable modular structure. The danger in this approach though is in team forming. It must be around features or options of the whole UI and not the modules. Organizing on modular teams compartments the flow of development information far too much.
  9. This is a stimulating collection of thought. I am happy you spoke ambiguously, Q, otherwise I may not have been drawn in. When I think of a tool, the archetype of "tool", I go to the image of the knife. In many ways, more powerful than a lever or a wheel in terms of human culture. On a camping trip, I want a Swiss Army Knife. In the Surgical theater, I would want my physician to have a scalpel. At the dinner table, I want a still different edged tool. Understanding in a simplistic way the multi-varate test modern applications must meet in the wild, and how stacking tolerances in sytems rapidly can cause good designs to fail, I am almost thinking that somewhwere along the timeline, a multiple experience menu needs to be provided that will allow a user to select among a group of speciaized viewers. Said differently, on initialization of each run, a pre-run loader asks the Resident to "Choose an Experience Style" and offers choices such as 1) Socialization and Shopping 2) MMORPG 3) Machinima Production 4) Content Creation, etc. The Pre-run loader then continues intialization with a Viewer load that has a viewer optimized for the Experience Style the Resident has selected for the inworld session. A Viewer Widget to "Change Experience" could allow the Resident to have the local machine change the Viewer load mid-session, holding the inworld session in placerholder fashion, and without the usual session intialization to authorize, download and etc. I suppose I need to understand where you are in this dev now. You have managed to pique my interest.
  10. Congratulations Kim! Welcome to our world !
×
×
  • Create New...