Menu

#12 Additional Page tool: browser

Deferred
open
nobody
5
2006-11-01
2006-11-01
Spicerun
No

Currently, the spec calls for the page panel to contain
an edit tool, capable of editing text in unicode, rtf
and plain text.

This request it to add an additional tool, or control,
for pages that would provide a browser. This would not
be a general-purpose browser, but rather a mechanism to
display a page of html that is associated with the
tuxworx file by a mechanism to be determined.

Adding an additional tool to the page panel toolset in
the form of a browser would provide the ability to
generate pages containing wiki information, using one
of the micro-wiki tools (DoxWiki, TiddlyWiki, or
similar). Using wiki tools in a browser would provide a
simple editor that would immediately add links and
images into tuxworx files, although the images would be
stored external to the file itself.

This request envisions creating a new page, and
selecting 'wiki', for example, instead of 'text' or
'rtf'. This would cause the browser control to be
associated with that page. Behind the scenes, a
wiki-on-a-stick html document would be generated,
ready to be modified by the user. This wiki/html
content will be the pages contents during its life.

Handling html/xml files inside a tuxworx file would be
problematic, and is an issue that must be resolved
before the browser control would be possible.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.