Difference between pages "Main Page" and "Term"
(→Terminology) |
m (Terminology moved to Term) |
||
| Line 1: | Line 1: | ||
| − | == | + | ''Note for editors - please try to keep this in roughly alphabetical order'' |
| + | == Field == | ||
| + | == Item == | ||
| + | == Parameter == | ||
| + | == Reader Management == | ||
| − | + | == Slice == | |
| − | If you | + | What is ''slice''?. If you know databases (relational databases), the answer is simple. Slice is a database table. If you don't, don't worry. It's simple. |
| − | |||
| − | |||
| − | + | We use the term "slice", because we like to look at one ActionApps installation as one big pie, and each user can have a bite ( or slice ). The pie is made of items, which are particulary tasty, and each item belongs to one slice. | |
| + | So, another way to look at this is that slice is a container (basket) full of items. | ||
| − | + | There is more to slice: | |
| − | + | ~ToDo: insert picture explaining slice | |
| − | + | ||
| − | + | Slice can or can't be accessed by ActionApps User depending on the [[User Permissions]] | |
| − | + | Slice can generate parts of web pages [[Views]] depending on the actual content in it, and it can even look nice if you have spend some time playing around with the [[Design Templates]]. | |
| − | + | ||
| − | + | The way you set your slice up will be reflected in many other areas, becuase it not only holds content, but [[Slice Settings]] also determine the look of [[Item Manager]], data structure and [[Input Controls ]]. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Moreover, slices can be created, modified, deleted, exported to another ActionApps installation, imported from somewhere, synchronized across several ActionApps installations, and last but not least, blamed for things not working the way they should. | |
| − | + | Some useful links realated to slice topics: | |
| − | + | ~ToDo: link to the relevant slice documentation | |
| − | + | == View == | |
Revision as of 17:26, 7 July 2005
Note for editors - please try to keep this in roughly alphabetical order
Contents
Field
Item
Parameter
Reader Management
Slice
What is slice?. If you know databases (relational databases), the answer is simple. Slice is a database table. If you don't, don't worry. It's simple.
We use the term "slice", because we like to look at one ActionApps installation as one big pie, and each user can have a bite ( or slice ). The pie is made of items, which are particulary tasty, and each item belongs to one slice. So, another way to look at this is that slice is a container (basket) full of items.
There is more to slice:
~ToDo: insert picture explaining slice
Slice can or can't be accessed by ActionApps User depending on the User Permissions Slice can generate parts of web pages Views depending on the actual content in it, and it can even look nice if you have spend some time playing around with the Design Templates.
The way you set your slice up will be reflected in many other areas, becuase it not only holds content, but Slice Settings also determine the look of Item Manager, data structure and Input Controls .
Moreover, slices can be created, modified, deleted, exported to another ActionApps installation, imported from somewhere, synchronized across several ActionApps installations, and last but not least, blamed for things not working the way they should.
Some useful links realated to slice topics:
~ToDo: link to the relevant slice documentation
