WEB AUTHORING PLUGIN IMPLEMENTATION

• US 20080184135A1
• Filed: 01/26/2007
• Published: 07/31/2008
• Est. Priority Date: 01/26/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Allaire, Joseph James, Washburn, Donald "Spike" Arthur
• Application Number:
  US11/627,742
• Publication Number:
  US 20080184135A1
• Time in Patent Office: Days
• US Class Current: 715/752
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting

Abstract

Methods are described for implementing a plugin in a blog or other structured online document. One embodiment of the method includes providing an interface between a blog-editing application and a plugin, receiving an indication that the plugin is to be invoked; presenting a user interface based on the plugin to receive settings that define characteristics associated with an object to be rendered in a blog post, receiving the settings, creating an editable code fragment based on the settings that can be utilized to present a rendering associated with the plugin, and presenting the rendering in the blog-editing application.

Claims

1. One or more computer-readable media having computer-useable instructions embodied thereon for performing a method of implementing a plugin in a blog post, the method comprising:

providing a local blog-editing environment whose format is derived from a remote blog site, the blog-editing environment being presented based on editing-environment rendering code;

receiving an instantiation indication that indicates that a plugin is to be utilized;

based on the plugin, presenting a user interface that includes one or more controls to receive one or more settings from a user that define characteristics associated with an object associated with the plugin;

receiving the one or more settings;

based on the one or more settings and the plugin, creating an editable code fragment that can be inserted into the editing-environment rendering code, wherein the editable code fragment provides an association with the plugin by way of a user-selectable rendering in the blog-editing environment;

inserting the editable code fragment into the editing-environment rendering code; and

presenting the user-selectable rendering in the blog-editing environment.

2. The media of claim 1, wherein the plugin includes a portion of programming code that can be packaged and run in connection with another application.

3. The media of claim 2, wherein the plugin takes the form of a library, including a dynamically linked library that can be loaded into a running application to augment the capabilities of that application.

4. The media of claim 1, wherein the instantiation indication includes an indication received by a user as a result of traversing a menu structure or completing a key sequence.

5. The media of claim 1, wherein the instantiation indication includes an attempt to add a media component to a blog post.

6. The media of claim 5, wherein incident to the attempt, the user interface is automatically presented without user intervention.

7. The media of claim 1, wherein the settings include one or more of:

an indication of a size of the object;

an indication of a presentation format of the object; and

an indication of a location of a component associated with the object.

8. The media of claim 1, wherein the editable code fragment includes an editable HTML code fragment.

9. The media of claim 1, wherein the user-selectable rendering is an atomically selectable objected presented in the blog-editing environment.

10. The media of claim 1, further comprising receiving a change indication that a change to one or more of the characteristics is desired.

11. The media of claim 10, further comprising re-presenting the user interface incident to receiving the change indication.

12. The media of claim 11, wherein re-presenting the user interface includes presenting the user interface with an indication of current settings.

13. The media of claim 11, further comprising receiving additional or a change to current settings.

14. The media of claim 13, further comprising modifying the user-selectable rendering based on the additional or change to the current settings.

15. The media of claim 1, further comprising referencing the editable fragment to determine what logic needs to be generated to expose functional aspects of an object to be rendered based on the fragment to publish the blog post.

16. The media of claim 15, further comprising publishing the blog post, wherein an object is published in the post that appears in one of two formats:

the same as the user-selectable rendering;

or

a further-customized format that is different from the user-selectable rendering.

17. One or more computer-readable media having computer-useable instructions embodied thereon for performing a method of implementing a plugin in a blog post, the method comprising:

providing an application program interface that provides an interface between a blog-editing application (“

application”

) and a plugin to extend functionality of the application;

receiving an indication that the plugin is to be invoked;

presenting a user interface based on the plugin to receive settings that define one or more characteristics associated with an object to be rendered in a blog post;

receiving the settings;

creating an editable code fragment based on the settings that can be interpreted by the application to present a rendering associated with the plugin; and

presenting the rendering in the blog-editing application, wherein the rendering is selectable, and can re-invoke the user interface incident to a an indication of a desire to do so.

18. One or more computer-readable media having computer-useable instructions embodied thereon for performing a method of implementing a plugin in a blog post, the method comprising:

presenting a rendering of an editable code fragment, wherein the editable code fragment is generated from user settings received by way of a user interface presented by a plugin associated with a blog-editing environment;

receiving a command to publish a blog post composed by utilizing the blog-editing environment and containing the rendering;

referencing the editable code fragment to determine programming logic necessary to render and object that includes any information associated with the rendering; and

publishing the object in a blog post, wherein the object is associated with the logic to provide functional aspects associated with the object.

19. The media of claim 18, wherein the blog-editing environment is automatically derived from a format of a remote blog site.

20. The media of claim 18, wherein the rendering is atomically selectable by a user.