Opened 15 years ago
Closed 14 years ago
#200 closed enhancement (wontfix)
Factor out the spiffy-related functionality of qwiki
Reported by: | Ivan Raikov | Owned by: | sjamaan |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | extensions | Version: | 4.4.x |
Keywords: | qwiki | Cc: | sjamaan |
Estimated difficulty: |
Description
Currently, qwiki seems to be rather closely tied up with spiffy and intarweb, which impedes testing on a local directory of wiki files. Perhaps it will be better to refactor qwiki so that frontends to different web servers (or CGI) can be created.
Change History (2)
comment:1 Changed 15 years ago by
Owner: | set to sjamaan |
---|---|
Status: | new → accepted |
comment:2 Changed 14 years ago by
Resolution: | → wontfix |
---|---|
Status: | accepted → closed |
Refactoring would mean duplicating a lot of stuff, I guess. I don't think it's worth the effort.
Note: See
TracTickets for help on using
tickets.
The best approach to achieve this would probably be to revive web-unity.
In the meanwhile, for testing, you could just generate static html files using
qwiki-update-file!
. For an example on how to use it, seeqwiki-install.scm
.