Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: An approach is described for addressing API modifications to ensure client compatibility. An associated method may include receiving, via a communications network, a web services request from a client application. The request may include requested information and request metadata in a first data format in accordance with a data contract. The method further may include transmitting the web services request to a server application and receiving from the server application a server response to the web services request. The server response may include a response to the requested information in a second data format and response metadata in the second data format. The method further may include evaluating the server response by completing a comparison of the request metadata in the first data format with the response metadata in the second data format and generating a client-compatible response to the web services request based upon the comparison.

Abstract: Arrangements described herein include accessing user data associated with a user participating in a web conference. The user data includes user analytics generated by tracking and analyzing use, by the user, of web based resources unrelated to the web conference. A plurality of topics discussed during the web conference can be identified in real time. For each respective topic that has a high probability of being of interest to the user, at least one bookmark for the web conference can be generated. Data contained in the bookmark artifact can be applied to a recording of the web conference to bookmark in the recording of the web conference each respective topic that has a high probability of being of interest to the user. An association between the recording of the web conference and the user can be created.

Abstract: An approach is described for addressing API modifications to ensure client compatibility. An associated method may include receiving, via a communications network, a web services request from a client application. The request may include requested information and request metadata in a first data format in accordance with a data contract. The method further may include transmitting the web services request to a server application and receiving from the server application a server response to the web services request. The server response may include a response to the requested information in a second data format and response metadata in the second data format. The method further may include evaluating the server response by completing a comparison of the request metadata in the first data format with the response metadata in the second data format and generating a client-compatible response to the web services request based upon the comparison.

Abstract: Arrangements described herein include accessing user data associated with a user participating in a web conference. The user data includes user analytics generated by tracking and analyzing use, by the user, of web based resources unrelated to the web conference. A plurality of topics discussed during the web conference can be identified in real time. For each respective topic that has a high probability of being of interest to the user, at least one bookmark for the web conference can be generated. Data contained in the bookmark artifact can be applied to a recording of the web conference to bookmark in the recording of the web conference each respective topic that has a high probability of being of interest to the user. An association between the recording of the web conference and the user can be created.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: Visualizing user interfaces specified by source code includes executing, using a development application, source code including a segment of source code specifying a user interface and, responsive to executing the segment of source code, generating, using a processor, a first screenshot including the user interface. The first screenshot is correlated with the segment of source code. The first screenshot is stored in association with the segment of source code.

Abstract: In one embodiment, a file includes data that is divided into a plurality of sections, and each section may include metadata that includes the revision history for that section. A specific section of the file may be selected and its revision history queried. In response to such a query, the revision history for the selected section is extracted from the section metadata and may be displayed. If a portion of a section has been copied from a source section and pasted into a target section, the section metadata for the target section may be updated to include information about the source section. For each change to the section data, the section metadata may also include a version number, a revision date and time, a revision author and the actual insertion, deletion or other change to the section data.

Abstract: In one embodiment, a file includes data that is divided into a plurality of sections, and each section may include metadata that includes the revision history for that section. A specific section of the file may be selected and its revision history queried. In response to such a query, the revision history for the selected section is extracted from the section metadata and may be displayed. If a portion of a section has been copied from a source section and pasted into a target section, the section metadata for the target section may be updated to include information about the source section. For each change to the section data, the section metadata may also include a version number, a revision date and time, a revision author and the actual insertion, deletion or other change to the section data.