[The subject of this topic sounds painful!]
Problem
People want to write about something β such as an image, a map, or a
movie β and not require readers to have to break the flow by clicking a
link to view the object. Instead, the author would line the object to
appear in the middle of the post.
Solution
GroupServer replaces recognised URLs β such as links to YouTube β with
embedded objects, such as the Flash movie player from the aforementioned
Google department. This would be done as part of the post-rendering
code. The same code already replaces URLs with links; the idea is to
extend this code to create a pluggable architecture of URL handlers.
Comments? Suggestions?
Problem
People want to write about something β such as an image, a map, or a
movie β and not require readers to have to break the flow by clicking a
link to view the object. Instead, the author would line the object to
appear in the middle of the post.
Solution
GroupServer replaces recognised URLs β such as links to YouTube β with
embedded objects, such as the Flash movie player from the aforementioned
Google department. This would be done as part of the post-rendering
code. The same code already replaces URLs with links; the idea is to
extend this code to create a pluggable architecture of URL handlers.
Comments? Suggestions?