Archive for the 'Discussions' Category

Alex Ivy Releases Updated macOS installers and Path forward 4

The problem with Advanced Lighting Model not being active is an accepted jira at BUG-41395.

The problem of leaving an extra app icon on the dock is fixed temporarily. The problem was the SL_Launcher running at viewer start and exiting to the viewer without removing the icon.

We have taken the front end code for SL_Launcher and removed it. It is just 2 lines of code that can be put back after LL makes the launcher behave better and TPV’s have the ability to complete automated viewer version updates.

Here are some updated installers:

Kokua with RLV; https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Macintosh64bit/Kokua_Test_RLV_5_1_0_42219_x86_64.dmg/download

Kokua without RLV; https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Macintosh64bit/Kokua_Test_NORLV_5_1_0_42218_x86_64.dmg/download

Hope it goes well.

Nicky

Alex Ivy Releases and Path forward 3

Status Update

There are updated test viewers available on the SourceForge Kokua project site.

For those unfamiliar, LindenLab has Project Alex Ivy in progress. Alex Ivy updated Windows and MacIntosh SecondLife viewers to 64 bit and for Windows kept a 32 bit viewer.

SecondLife Alex Ivy has progressed from white-board to Project Viewer and now is a Release Candiate viewer.

Additional details about this viewer can be found in the Alex Ivy Release Notes at:
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.0.507412

Kokua developed and provided a Linux 64 bit viewer, but never developed Windows and Mac 64 bit as we preferred
to wait until LindenLab developed upstream. We now have Windows and Mac 64 bit Alex Ivy viewers available for testing and feedback.
For RLV capable–
Mac64:
https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Macintosh64bit/Kokua_Test_5_1_0_42217_x86_64.dmg/download

Windows64:
https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Windows64Bit/Kokua_Test_Alex_Ivy_RLV_5_1_0_42217_x86_64_Setup.exe/download

For no RLV–
Mac64:https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Macintosh64bit/Kokua_Test_5_1_0_42216_x86_64.dmg/download

Windows64:
https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/Windows64Bit/Kokua_Test_Alex_Ivy_NORLV_5_1_0_42216_x86_64_Setup.exe/download

These viewers should contain functionally at par with current SL default viewers. We recommend testers focus on, but not be limited to, notifications and taking and processing snapshots as those areas caused the most problems during the recent merge.

We have also merged all other Kokua viewers to SL Default. Downloads for these can be found on SourceForge at:
https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/

Kokua Linux viewers do not yet have the Alex Ivy code base.

Enjoy.

Nicky

Pull back of preliminary release KokuaSL-4.1.2.39990

Over the past few days a preliminary KokuaSL-4.1.2.39990 release was placed in SourceForge and Bitbucket download areas. Chorazin Allen found some issues with KokuaSL-4.1.2.39990 and I have since removed the downloads. Approximately 50 users downloaded the viewers and should revert back to KokuaSL-4.1.1.39717.

macOS 10.12 (Sierra)

Our most recent macOS test viewers will run on macOS 10.12 (Sierra). For the SL Viewers that would be version 4.1.1.39869 and newer. For the OS viewers that would be 4.0.2.40582 and newer.
Our macOS developer, Gavin Hird, reports that the older versions all experience various performance issues and crashes when run on Sierra.

OS test viewers download link is https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-OS/.

SL test viewers download link is https://sourceforge.net/projects/kokua.team-purple.p/files/Kokua-SL/.

Please report any issues using our ticket system at https://sourceforge.net/p/team-purple/kokua/tickets/.

Windows 10 OpenGL issue after Anniversary Update (AU)

Ticket #426 has been opened for Kokua users
to report instances of severe performance issues after installing KB3176938 (Windows Version 1607 Build 14393.105).

Inara Pey has a blog about this at https://modemworld.me/2016/09/06/windows-10-opengl-issue-affecting-some-second-life-users/

I have 2 windows machines one laptop and one desktop with AU and the update and neither have experienced this issue.

OpenSim Grids default listing in Kokua

For: OpenSim grid managers.

We are reviewing our default grid drop down list for drops and adds.

Past practices were quid pro quo in that we included a grid on the list if grid provided our downloads link to new users at grid avatar registration or as a Downloads tab on the grid’s homepage.

That practice is still present with the following addition. If there is coverage (good or bad) of Kokua in grid branded forums we will continue the listing.

If continuation on, or an addition to the list is desired please open a ticket. If desired check Mark as Private.

The downloads link is http://team-purple.sourceforge.net/wiki/Kokua/Downloads

Kokua-3.8.3.38326 Test

Kokua-3.8.3.38326 Test is ready for download and testing. Normally, we don’t announce test viewer availability but, this viewer fixes Experience Profiles for SL users and handles the My Suitcase folder for OpenSim users. The My Suitcase patch was submitted to Kokua and other OpenSim viewer projects by Cinder Roxley. Since this Kokua Test viewer effects potentially more than just a few users I felt the blog announcement appropriate.

Download links:

Mac
MD5 011ee3d92f4da87496de20f580019d5f *Kokua_Test_3_8_3_38326_i386.dmg

Linux 32 bit
MD5 63a5ba91078c6c8480bba8d623a62a19 Kokua_Test_3_8_3_38326_i686.tar.bz2

Linux 64 bit
MD5 83eef049db3474cd080b3eed1447a3a5 *Kokua_NT_64_Test_3_8_3_38326_x86_64.tar.bz2

Windows
MD5 6611b2f890942e6ddbe4db66bd675098 *Kokua_Test_3_8_3_38326_i686_Setup.exe

Subscribe or Monitor the Test viewer download folder for additional test viewer updates.

What’s Next..?

Here at Imprudence we’ve been juggling several issues, trying to develop two different clients at the same time (Imprudence and Kokua) for three different platforms in 32bit and 64bit flavors. not to mention supporting not only the Second Life grid but all the various OpenSim grids as best we can. We think we’ve made some pretty awesome viewers but lately we’re also become stagnant as we’ve been weighted down by trying to juggle all these various things. It seems we may have over extended ourselves a bit and to fix that we need to refocus and simplify. Thus in the coming weeks we will be holding an all-hands team meeting for all Imprudence/Kokua team members, be they Dev or Support, where we will discuss what’s working and what isn’t and what we plan to do about it (Details have already been sent to all team members).

But we’d like to hear your input as well, as we make these viewers for you our users after all. Tell us what makes Imprudence special for you, what draws you to this particular Third Party Viewer over others and what you would like to see going forward.  How do you use Imprudence, and how do you use other viewers even the official one? What do you like about them, what don’t you like, and how is that similar or different from Imprudence. Do you use OpenSim, Aurora or any other alternative grids, even your own local grid? Is there anything you think that Third Party Viewers are missing that would make them easier or more productive for people? What about the site itself, this blog, the forum, the wiki and etc, how can we improve it?

While we can’t make any promises about addressing every issue, we will try to discuss any points made here in the comments.

Why doesn’t Imprudence have multilayers, inventory links, or mesh rendering?

Other viewers have them, so why don’t we? Why would a developer purposefully avoid such useful features–ones that users clearly want?

The answer is something of a mixed bag, and to get into it I’ll first have to explain a little bit about licensing and how licensing works. If you already know this stuff, please bear with me as I’ll get to my point soon.

As many of you know, Imprudence is licensed under the GPLv2+FLOSS Exceptions. The GPL is basically a software license that allows for free and open code. It’s because of this that we can easily share our code and incorporate others’ code in turn. Even so, the GPL doesn’t allow us to do whatever we want. There are certain restrictions, such as:

  • You cannot change the license of any line of code unless you are the original author, you hold copyright on that code, or the license permits it. When we get a patch submission, the author must license their code in a compatible fashion.
  • You may not distribute works based on GPL code that violate any part of the GPL itself. Doing so leaves you open to legal action.

So, how does that impact us, exactly? Imprudence is opensource. Second Life is opensource. Why can’t they work together? Here’s where the restrictions of the GPL come in: a bit over a year ago, Linden Lab decided to change the license for the Second Life viewer from GPL+Exceptions to LGPL–a similar-sounding but ultimately different license. While the LGPL is compatible with the old license, there’s no way to go from LGPL to GPL+Exceptions. This put a massive hurdle in our way as far as porting features from the Second Life.

For example, say someone submits a viewer 2/3-based patch to Imprudence.

While the GPL and LGPL are considered compatible licenses, we don’t own the copyright on the LGPL code submitted to us. Thus, we cannot change the license of that source to include exceptions. Whatever code was licensed as LGPL must stay LGPL (or equivalent) and that distinction must always be made clear wherever that code is used.

This might not sound like much of a hurdle (and at times it isn’t–we switched over to the LGPL version of our Quicktime plugin ages ago) but consider the Inventory Links patch that’s currently in most other viewers. It contains ~43K lines of code, and is made up of an unknown mix of GPL+Exceptions viewer 1 code and LGPL viewer 2 code. The two licenses are not made distinct, so the patch is clearly a violation. There’s no way we could legally use it as is.

However, if we could figure out which lines are compatible with Viewer 1 and which ones are compatible with Viewer 2, we could add the appropriate licensing and include the patch. Needless to say, this has felt like a daunting task to us, especially when we’ve been more focused on bug fixes and finalizing 1.4.0 (if you’re using 1.4 and aren’t on beta 2, I strongly recommend upgrading) as far as Imprudence goes. But, these are features you guys need. We want to include them.

My plan is to start looking at these patches one by one and sorting out which lines we can use and which lines need refactoring. As I mentioned in a comment on the beta 2 post, any volunteers who can help us with this process are welcome. Codie and I will be starting on this later tonight, and we’ll see how far we get. If you’d like to join us, please email me at mccabe@kokuaviewer.org and I’ll tell you what you can do.

You might find yourself asking, why go through so much effort for something like a little licensing issue? Why be so concerned when the author of the patch didn’t seem to be?

Our answer has always been–almost from the project’s inception–that while sometimes doing things the right way isn’t easy, these concerns are important to us. It’s thanks to licenses like the GPL, as well as the rules that accompany them, that opensource software has matured to the level it has today. Free and open software gave us the ability to start Imprudence (and later Kokua). We feel an obligation to respect that.

Anyway, I hope this clarifies for people where we’re coming from, and why we’ve done some of the things we have.

EDIT: I’ve updated this post a bit to try to make things clearer.

Mac User Survey

Greetings, Mac users! We’ve created a short survey to help us find out what sort of Macs you are using to run Imprudence, or would use to run Imprudence if it was compatible.

This information will give us an idea of how many people still use PowerPC Macs, how many people would benefit from a 64-bit version, and how many people would be affected if we updated to frameworks only available in 10.5+.

If you use a Mac, please take a moment to fill out the survey. Thanks! :)

All responses are anonymous and confidential. Please respond only once per person.

Which version(s) of Mac OS X do you use on a regular basis?
(You can find this information in the Apple menu > About This Mac.)



What processor type(s) do you have in your Mac(s)?
(You can find this information in the Apple menu > About This Mac.)