![]() The bursting of the dot-com bubble in the fall of 2001 marked a turning point for the web. 2009: Tim O'Reilly and John Battelle answer the question of "What's next for Web 2.0?" in Web Squared: Web 2.0 Five Years On. A side-effect of this is that when adding tags, any floor information (id) provided to Mattertag.add and Mattertag.editPosition will be ignored.Oct. Instead, floor and room information is automatically inferred by the position specified. Tag.add and Tag.editPosition no longer accept a floor, nor do they accept a room. ![]() ![]() Preferring Rooms over FloorsĮach tag’s associated data now prefers room information over floors info. There are a number of other smaller changes between the current Mattertag namespace and the new Tag namespace. Note that we are looking into providing observable state for things like hover states, open tags, docked tags, etc. Continue to use the existing Mattertag events. There are currently no events in the Tag namespace for things like clicking or hovering tags. Note, we are looking into providing general “look at” functionality as well as the ability to open, close, and dock tags programmatically. There is currently no functionality in the Tag namespace to navigate to a tag. Tag.allowAction accepts the actions that are allowed so that false is false and true is true. We identified that preventAction had a confusing double negative where a false equated to the action being allowed ( !prevented). In order to prevent actions on tags, migrate from Mattertag.preventAction to Tag.allowAction ![]() Tags have unified file uploads, external media attachments through OEmbed, and custom HTML Sandboxes under attachments. Adding Custom HTML WidgetsĪdding custom HTML (or code sandbox) to a tag should be migrated from Mattertag.injectHTML to Tag.registerSandbox and Tag.attach. Tags now support multiple media (or attachments) per tag. Providing media in Mattertag.add or Mattertag.editBillboard should be migrated to use Tag.registerAttachment and Tag.attach. Eventually, this will also be the case for Pointer.editTexture. Instead, Asset.registerTexture should be used. The Tag namespace does not have a registerIcon function like the Mattertag namespace does. We have moved to a unified texture registry for icons and other visuals. Mattertag.registerIcon should be migrated from Mattertag.registerIcon to Asset.registerTexture. A brief summary of the major changes Existing Functionality However, any future Tag capabilities will be added to the Tag namespace. After the full release, the Mattertag namespace will be considered deprecated, but still functional. The Mattertag namespace should continue to work whether or not the application is using Tags 2.0. Rather than shoehorning a new interface on top of an existing namespace, Tags 2.0 (Tags) seek to provide the foundation for more powerful tag-based capabilities in the future. However, the Mattertag interface and architecture doesn’t directly support future extended capabilities, such as hosted content. ![]() Traditional Mattertags allow for the viewing of embedded content and information about particular locations within a Matterport space. Some are now more robust and require more than a single step to use. Most operations that are available in the Mattertag namespace have an equivalent operation in the Tag namespace. Tags (2.0), is the successor to Mattertags. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |