Data Forms in [[include]]
nav_first.pngFirst: thread:379
Feedback from naive user
Edited: 26 Oct 2011 12:41 by: Sheepdog
Comments: 3
nav_prev.pngPrevious: thread:370
Revision comments
Edited: 14 Sep 2010 19:52 by: dhb
Comments: 1
Last: thread:141
Which aspects of this design do people want first?
Edited: 11 Nov 2009 12:44 by: leiger
Comments: 14
Next: thread:364
Hidden field - changes improvements
Edited: 09 Jun 2010 11:24 by: leiger
Comments: 1

rurwinrurwin wrote on 30 Jun 2010 12:43

There are many applications of Data Forms that can never be realised until ListPages can be nested. Since ListPages will never be able to be nested, these applications will never see the light of day. In the absence of ListPages then, why not extend [[include]] to allow constructions that are otherwise impossible?

For example:

  1. You have a Pro site, with per-site profiles. (Or a free site and pretend you do.) You could make those profiles Data Forms and use fields from them, (for example game-rank, or forum signature), throughout the site. However if the site has any complexity at all, most of those uses are already inside ListPages invocations. A forum signature is only of use on a forum, and that is certainly built with ListPages.
  2. You use Data Forms as a database of objects. You want to refer to one of these objects from within a page-based forum — At the moment you would have to use an iframe or be satisfied with a link, both of which present the entire page, and that may be more than you want.

There are several ways this could be done, some of which I have described:

Here is another one:

[[with pagename]]
... Wikidot code ...

Where Wikidot code can contain an [[include]].

But any way that we can use Data Forms with [[include]]s would be great.

Start a new sub-thread

AND includes in fields of data forms. By Steven Heynderickx 0 Comments 30 Jun 2010 13:40

Comments: 0

Add a New Comment
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License