close open_in_new

Virtual cards organize patterned content using patterned compound names.  They're not actually stored in the database but act just like "real" cards whenever you link to or include them.

 

Example

help edit space_dashboard

The following is a virtual card:

help edit space_dashboard
stop HTML encoding URLs in named links+example
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
stop HTML encoding URLs in named links+issues
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
stop HTML encoding URLs in named links+tag
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
stop HTML encoding URLs in named links+status
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
stop HTML encoding URLs in named links
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
restricting permissions on card names+discussion
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
H+discussion
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
auto save+discussion
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
improve editor help text and ubiquify it+solution
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Autocomplete in Pointers broken?+issues
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Autocomplete in Pointers broken?+tag
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Autocomplete in Pointers broken?+status
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Autocomplete in Pointers broken?
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Does navbox only work in the default location now?+issues
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Does navbox only work in the default location now?+tag
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Does navbox only work in the default location now?+status
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Does navbox only work in the default location now?
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Can you add anchor points as a standard thing?+tag
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Ticket shows up blank+discussion
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
Ticket shows up blank+issues
open_in_new
open_in_new page
fullscreen modal
edit edit
space_dashboard advanced
  • «
  • 1
  • 2
  • 3
  • ...
  • »
1 - 20 of 8021

There is not a card named John Abbe+*created in the database.  There is, however, a structure rule that determines the content of cards ending in "+*created". 

 

How To

help edit space_dashboard

A real card is a card that is formally stored in the database.  A virtual card is a non-real card with a *structure rule.

 

Virtual cards are most useful when used in combination with contextual names

 

 

Discussion

help edit space_dashboard

Okay. So I make a real card called "+*something"? And then alter the structure for that. And that structure might be a search that uses virtual cards as part of the search parameters?

--Lora Friedenthal.....2013-09-29 00:31:23 +0000

Eh, I don't know how block quote actual commands so they print instead of function. [_left]

--Lora Friedenthal.....2013-09-29 00:32:01 +0000

You mean how to show link and inclusion syntax literally? Add a backslash like this: [[I look like a link]].

 

There are many useful built-in 'right rules' so often you just need to include the virtual card. So, if there is a structure rule like this: my_search+*right+*structure, then I can use {{Some_card+my_search}} which is a virtual card the references that search rule, and the 'Some_card' part can be referenced in the search so you can also do {{Some_other_card+my_search}} which is a similar search based on a different card. Hope that helps a little.

--Gerry Gleason.....2013-10-01 13:02:33 +0000

This sounds like making my_search a real card instead of making +*my_search real card. (I'm not sure if there's any actual different between those two things.) However, you seem to be suggesting that I wouldn't need to use [[left]] in the actual search because the method of inclusion would be doing that? But... then I'm not sure what the search itself would look like. Because the name of the card on which it is included is ultimately the string I want the search to be looking for. Would the search just be specifying a location to search in and display parameters?

--Lora Friedenthal.....2013-10-01 13:16:06 +0000

Well, in order to make +my_search a virtual card,the my_search card will be created when you make the rule card (my_search+*right+*structure), but it probably is an empty card.

 

Note the *my_search is just another card, distinct from my_search, the difference being there are some conventions about star-cards (card beginning with * and 'rstar' cards whose right part begins with *. Because they have special Set associated with them, they can have rules for those sets, and conventionally some permissions are restricted.

 

I think you would probably be using left in the search WQL, but I'm a bit rusty on some of the details. Is it actually _left ? Not sure. Look at some built in examples of *right rules.

--Gerry Gleason.....2013-10-02 16:10:02 +0000

Looking at a few examples, it seems that you would use _self in the typical virtual card search for a *right rule. Presumably _self is the left part of the Set which is the left part of the Rule.

--Gerry Gleason.....2013-10-02 16:18:44 +0000
 
Tickets relevant to virtual cards