4/17/2023 0 Comments Second life appBut if you have a very low end Android phone that is from a lesser-known brand, don't get your hopes up.Īnd yeah, it would be nice if this all lead to a native Apple (M chip) viewer. You might need some good storage capability. I imagine stock Apple iPhones/iPads released in the last few years will run it (likely recent Samsungs and Google Pixels, etc.). Since it's likely the early releases of mobile will have a reduced feature set, it will also be important to show mobile users how they can do what they can't do on mobile - on their personal computer - whether it's editing a shape, or adding textures to a mesh, or whatever.Īs far as hardware, I can't imagine that it's going to be so high-end that you'd have to have the best and the latest. Maybe they will be familiar with something like The Sims or Fortnight, and will need to adjust to the free-form nature of SL. Some of that will need to be tailored to the first-time user arriving on a mobile platform. New user experience/onboarding will become even more important if that's the case. I think there's going to be a lot of people just discovering our favorite virtual world.20 years after it began! It will be really interesting to see the impact that this mobile viewer will have as far as attracting new folks to SL. The open source enforcement lawsuits were years ago now. This is all pretty much settled and noncontroversial today. Preferably as a Github "pull request" to merge it into the main branch, which is how this is normally done today. But if someone were to add support for "notation" format (which puppetry is using), they'd have to release the code for that. It supports the XML and binary representations of LLSD, but not the "notation" format, which isn't used much. That's a little library for reading and writing LLSD (Linden Lab Serial Data). Here's library code of mine licensed under LGPL 2.1. If LL creates a viewer based on pieces of the existing viewers, they're stuck with licensing it under LGPL and making the code available. This is unusual for an executable program LGPL is usually for libraries that you link into a larger program. If the new code is integrated into the old code, yes, they do have to release any new proprietary code. But LGPL doesn't mean you *must* release any proprietary code. Considering it's Linden Lab, I think they'll make it open source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |