Two ideas I thought I would bounce around for input. Just theoretical
at this point but could be implemented quickly perhaps:
1) Info Forums
I'm thinking about setting up a forum using the info function as a way
to generate a very fast display. On each forum page put something
like:
[(info field={p} value="[r][c]{:title}[c]{:who}[c]{:comment}, etc..."
target=info.forum)]
Then on the list page, just go:
[t]
[(info report target=info.forum)]
[t]
Everything is all retrieved. I might even be able to get the
"read/unread" thing going by changing the forum footer to something
like this:
[(info field={p} value="#eee" target=info.forum.read.{id})]
[(info field={p} value="[r
color="{infor.forum.read.{id}::{p}}"][c]{:title}[c]{:who}[c]{:comment},
etc..." target=info.forum)]
The idea is, each time a post is viewed, a tiny bit of info is
prepared and saved, so that the display is always current and ready to
go. When viewing the pagelist, only one, or perhaps two pages are
used, and the content is put out lightning fast. Never even uses the
search function. Cool, huh?
2) Config editing
I was thinking about how to solve a specific problem this morning and
realized the best way to do it, is to use a config file--which I
really don't like doing particularly, because it involves ftp and all
that stuff. Config files are VERY powerful, but just a bit of a
hassle. Then it occurred to me the solution was to create a simple
plugin for config editing. All it should take is a config command
(which saves content to a config page) and a config function (which
reads the content of a config page). Then create a custom config
action using these two and you are good to go.
So you go to a page, click config, and either get a list of all
current config page, clickable for editing (my preference) or an edit
screen for the current pages config file. Add your changes, and boom
you are done.
There are some problems perhaps... One of course is you would have
the same security implications as the setup plugin. Still for many
users (including myself) this will be no issue at all. Second, if you
entered a mistake, you might crash your site (or at least that
hierarchy). This could be solved by not having the edit action called
for the current page, but rather, passed the page information as a GET
variable or something, so the config page doesn't get called. Meaning
you could edit a mistake if you made one. This wouldn't work if you
were editing config.php, but there may be a way around that as well,
if we think about it. Or we might just disallow that completely.
Feedback?
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
