Difference between revisions of "Third Party Viewer Directory/Emergence"
m |
m |
||
| Line 2: | Line 2: | ||
{{TPVD-Detail | {{TPVD-Detail | ||
|home=http://emergence. | |home=http://emergence-viewer.googlecode.com/ | ||
|privacy=http://emergence-viewer.googlecode.com/files/Privacy%20Policy.txt | |privacy=http://emergence-viewer.googlecode.com/files/Privacy%20Policy.txt | ||
|download=http://code.google.com/p/emergence-viewer/downloads/list | |download=http://code.google.com/p/emergence-viewer/downloads/list | ||
| Line 12: | Line 12: | ||
}} | }} | ||
===History=== | |||
Emergence first emerged at the time that the Emerald Viewer was intentionally placing their users systems at risk. It was created with the goal to completely remove all code that could have been potentially tampered with in order to provide a secure alternative for people who needed a similar feature set, without using the emerald executable. More information on this can be found [http://lordgreggreg.wordpress.com/2010/08/14/emerald-reassessment/ Here] and [http://lordgreggreg.wordpress.com/2010/08/22/past-present-future/ Here]. Eventually other developers also realized that emerald could not be salvaged, and a group of developers started the [http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory/Phoenix Phoenix Viewer] project with a similar goal and emerald code base. Due to their larger support and development team, and sharing the same goal, the Emergence viewer is [http://lordgreggreg.wordpress.com/2010/09/12/emergence-notice/ Mostly Suspended]. | |||
===Code Differences=== | |||
A human readable list of changes can found at the bottom of the [https://code.google.com/p/emergence-viewer/ Google Code Hosting Page]. | |||
Additionally, after the merge of the Phoenix code base, commit logs can be easily viewed [https://code.google.com/p/emergence-viewer/source/list on this log]. | |||
===Developers and Support=== | |||
Due to the nature of this project, all Development and Support is ran by [http://world.secondlife.com/resident/f0334909-28bc-4717-ae0e-1893c2881e3d LordGregGreg Back]. | |||
Most quick support issues can be answered by other users in either the [secondlife:///app/group/0a66543a-e23a-6151-5b20-b5da6e851c8d/about Emergence Group] or [secondlife:///app/group/ac871d02-6175-64d5-6c7e-983a8a4bc112/about LordGregGreg's Group]. | |||
For issues with the code, you can send a IM or a [mailto:LordGregGreg+Emergence@Gmail.com Email] or (after you have checked other issues please) file a issue on the [https://code.google.com/p/emergence-viewer/issues/list Issues Page]. | |||
Support issues with the viewer can be logged for review | |||
{{TPVD-Footer}} | {{TPVD-Footer}} | ||
Revision as of 15:03, 8 November 2010
Emergence
| Links | Contacts |
|---|---|
| |
Platforms:  Windows
| |
Description
History
Emergence first emerged at the time that the Emerald Viewer was intentionally placing their users systems at risk. It was created with the goal to completely remove all code that could have been potentially tampered with in order to provide a secure alternative for people who needed a similar feature set, without using the emerald executable. More information on this can be found Here and Here. Eventually other developers also realized that emerald could not be salvaged, and a group of developers started the Phoenix Viewer project with a similar goal and emerald code base. Due to their larger support and development team, and sharing the same goal, the Emergence viewer is Mostly Suspended.
Code Differences
A human readable list of changes can found at the bottom of the Google Code Hosting Page.
Additionally, after the merge of the Phoenix code base, commit logs can be easily viewed on this log.
Developers and Support
Due to the nature of this project, all Development and Support is ran by LordGregGreg Back.
Most quick support issues can be answered by other users in either the Emergence Group or LordGregGreg's Group.
For issues with the code, you can send a IM or a Email or (after you have checked other issues please) file a issue on the Issues Page.
Support issues with the viewer can be logged for review
Disclaimer: Linden Lab makes no representations or warranties regarding any of the listed viewers or developers. These third-party viewers are not affiliated with or overseen by Linden Lab. Please take reasonable precautions, including virus scanning, before installing and using any of the listed viewers.