Hi, all,

Back to the topic of custom pages...

tonight i've been adding some functions to th1 to make it useful for
creating custom pages (namely SELECT-only access to the db), and i'm about
ready to start plugging that in to the first draft of custom pages support.
The question on my mind is:

Which of these is prefered:

1) http://.../MyCustomPage
2) http://.../custom/MyCustomPage
3) something different?

:-?

Advantages of (1): we can potentially override built-in pages/commands.
Whether that's good or bad, i don't yet know. Depending on which command(s)
get overridden with custom ones, a repo might require manual surgery on the
db to recover from mistakes.

Advantages of (2): we have a well-defined namespace under which to place
custom commands, with no risk (or option) of accidentally replacing a
built-in command.

Insofar as possible this support "should" work via HTTP and CLI modes, e.g.:

fossil custom MyCommand ...

(doh, i need to feed the CLI args into th1 and add some args processing
funcs to it...)

TH1 of course isn't as full-fledged as TCL, but it's there, it's easy to
work with at the C level, and it's more powerful than i thought it was (not
as much so as i'd like, but it's a good starting point for prototyping this
stuff). If it turns out th1 will be too cumbersome/problematic/whatever,
switching over to TCL is still an option. If there are strong arguments for
immediately preferring TCL over th1, please speak up before i invest the
weekend on this ;).

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to