QuSheet: XML Input File
File: presentation.qus.xml
Headings
Addenda / Errata
# 1:
=
Addenda / Errata Line
(selector=
Select Text
)
(style=
)
Addenda / Errata Heading
# 1:
:=
addenda text
(style=
)
# 2:
:+
(style=
)
" / "
# 3:
:+
errata text
(style=
)
Addenda / Errata Line
# 1:
[=]
text
(field=
ae
)
(style=
)
# 2:
test =
a char
(style=
)
# 3:
true
text - addendum
(style=
)
# 4:
false
Addenda / Errata Line - not a
(style=
)
Addenda / Errata Line - not a
# 1:
[=]
text
(field=
ae
)
(style=
)
# 2:
test =
e char
(style=
)
# 3:
fif
(style=
)
# 4:
=
text - erratum
(style=
)
back navigation
# 1:
=
navigation directive 1
(style=
)
# 2:
+
predecessor
(style=
)
# 3:
+
navigation directive 2 back
(style=
)
buy line
# 1:
:=
(style=
)
<td style="border-top-style:none; border-bottom-style:none;"><a href="buy.index.html">LINK(buy.index.html,<span style="color:red; font-weight: bold">>>Buy Now<<</span>)</td>
# 2:
:+
(style=
)
<td style="border-top-style:none; border-bottom-style:none;"><a href="buy.index.html">LINK(buy.index.html,<span style="color:red; font-weight: bold">Buy Now</span>)</td>
dynamic documents.1
# 1:
:=
(style=
)
"Dynamic documents "
# 2:
:+
(style=
)
"allow the document viewer to control the "
# 3:
:+
(style=
)
amount of detail
# 4:
:+
(style=
)
" that is "
# 5:
:+
(style=
)
visibile
# 6:
:+
(style=
)
" to them at any one time."
dynamic documents.2
# 1:
:=
(style=
)
QuSheet
# 2:
:+
(style=
)
" automatically organises this detail for you from "
# 3:
:+
(style=
)
your data
# 4:
:+
(style=
)
" according to "
# 5:
:+
(style=
)
your rules and requirements.
dynamic documents.3
# 1:
:=
(style=
)
Dynamic Documents
# 2:
:+
(style=
)
" increase the "
# 3:
:+
(style=
)
content
# 4:
:+
(style=
)
" of your document "
# 5:
:+
(style=
)
without increasing
# 6:
:+
(style=
)
" its "
# 7:
:+
(style=
)
complexity.
forward navigation
# 1:
=
navigation directive 1
(style=
)
# 2:
+
successor
(style=
)
# 3:
+
navigation directive 2 forwards
(style=
)
in action.1
# 1:
:=
(style=
)
"The numerous examples on this web site provide good starting points for exploring "
# 2:
:+
(style=
)
QuSheet's
# 3:
:+
(style=
)
" functionality."
in action.2
# 1:
:=
(style=
)
QuSheet
# 2:
:+
(style=
)
" uses "
# 3:
:+
(style=
)
tables, tabs
# 4:
:+
(style=
)
" and "
# 5:
:+
(style=
)
forms
# 6:
:+
(style=
)
" to deliver a "
# 7:
:+
(style=
)
simple
# 8:
:+
(style=
)
" and "
# 9:
:+
(style=
)
intuitive
# 10:
:+
(style=
)
" user interface."
in action.3
# 1:
:=
(style=
)
QuSheet
# 2:
:+
(style=
)
" can produce "
# 3:
:+
(style=
)
multiple
# 4:
:+
(style=
)
" output files from the same input data, with "
# 5:
:+
(style=
)
individual variations
# 6:
:+
(style=
)
" as appropriate."
index navigation
# 1:
=
navigation directive 1
(style=
)
# 2:
+
index page
(style=
)
# 3:
+
navigation directive 2 index
(style=
)
index page example presentation
# 1:
:=
(style=
)
"Click "
# 2:
:+
(style=
)
LINK(presentation.trucks example.html,here)
# 3:
:+
(style=
)
" to see "
# 4:
:+
(style=
)
QuSheet
# 5:
:+
(style=
)
" transforming your data into HTML (browser friendly) output."
index page in action presentation
# 1:
:=
(style=
)
"Click "
# 2:
:+
(style=
)
LINK(presentation.in action.html,here)
# 3:
:+
(style=
)
" to see "
# 4:
:+
(style=
)
QuSheet
# 5:
:+
(style=
)
" in use."
index page overview presentation
# 1:
:=
(style=
)
"Click "
# 2:
:+
(style=
)
LINK(presentation.123.revised.html,here)
# 3:
:+
(style=
)
" to see the business benefits of "
# 4:
:+
(style=
)
Dynamic Documents.
kitchen.catalog.1
# 1:
:=
(style=
)
"Describes how your Parts and Prices catalogue can be imported into "
# 2:
:+
(style=
)
QuSheet
# 3:
:+
(style=
)
.
kitchen.customising.1
# 1:
:=
(style=
)
"Describes the customisation options which "
# 2:
:+
(style=
)
QuSheet
# 3:
:+
(style=
)
" allows you to make on your output file."
kitchen.intro.1
# 1:
:=
(style=
)
"The first presentation accompanying "
# 2:
:+
(style=
)
QuSheet
# 3:
:+
(style=
)
's Kitchen Example demonstrates how the output file was generated for a particular customer.
kitchen.modifying.1
# 1:
:=
(style=
)
Describes how to modify the example to allow different pricing structures and new or different item groups.
kitchen.modifying.2
# 1:
:=
(style=
)
Modified source code can be found here: LINK(examples/kitchen m 1.quote.html,<u>kitchen m 1</u>) (LINK(examples/kitchen m 1.qus.xml,<u>source</u>)), LINK(examples/kitchen m 2.quote.html,<u>kitchen m 2</u>) (LINK(examples/kitchen m 2.qus.xml,<u>source</u>)) and LINK(examples/kitchen m 3.quote.html,<u>kitchen m 3</u>) (LINK(examples/kitchen m 3.qus.xml,<u>source</u>)).
navigation bar
# 1:
:=
(style=
)
<table style="width:100%"><tr>
# 2:
:+
(style=
)
<td style="border-top-style:none; border-bottom-style:none">LINK(index.html,Home)</td>
# 3:
:+
(style=
)
</tr><tr>
# 4:
:+
buy line
(style=
)
# 5:
:+
(style=
)
</tr><tr>
# 6:
:+
(style=
)
<td style="border-top-style:none; border-bottom-style:none">LINK(main.features.html,Overview)</td>
# 7:
:+
(style=
)
</tr><tr>
# 8:
:+
(style=
)
<td style="border-top-style:none; border-bottom-style:none">LINK(main.examples.html,Examples)</td>
# 9:
:+
(style=
)
</tr></table>
navigation options
# 1:
=
index navigation
(selector=
dummy field
)
(style=
)
# 2:
+
space
(style=
)
# 3:
+
back navigation
(selector=
dummy field
)
(style=
)
# 4:
+
space
(style=
)
# 5:
+
forward navigation
(selector=
dummy field
)
(style=
)
pda_schedules.1
# 1:
:=
(style=
)
QuSheet
# 2:
:+
(style=
)
" can be used to produce conference schedules visible on hand-held screens as in the example "
# 3:
:+
(style=
)
LINK(http://www.qusheet.com/examples/schedule.pda.html,<u>here</u>)
# 4:
:+
(style=
)
" (best viewed on a small screen)."
pda_schedules.2
# 1:
:=
(style=
)
"The presentation below explains, in order, the "
# 2:
:+
(style=
)
output
# 3:
:+
(style=
)
" produced, the "
# 4:
:+
(style=
)
input
# 5:
:+
(style=
)
" required, and all the "
# 6:
:+
(style=
)
customisation
# 7:
:+
(style=
)
" that can be made."
pda_schedules.3
# 1:
:=
(style=
)
"After viewing this presentation you will know everything that you need to know in order to start producing your own "
# 2:
:+
(style=
)
PDA/Mobile Conference Schedules.
pda_schedules.4
# 1:
:=
(style=
)
"When you are ready to download and start customising the example file, "
# 2:
:+
(style=
)
right
# 3:
:+
(style=
)
" click and "
# 4:
:+
(style=
)
save
# 5:
:+
(style=
)
" the following link:"
pda_schedules.5
# 1:
:=
(style=
)
LINK(http://www.qusheet.com/examples/schedule.qus.xml,<u>http://www.qusheet.com/examples/schedule.qus.xml</u>)
Quick Intro Headline
# 1:
:=
quick intro
(style=
)
# 2:
:+
quick intro part 2
(style=
)
sample scenario.1
# 1:
:=
(style=
)
"As well as providing a sophisticated user interface, "
# 2:
:+
(style=
)
QuSheet
# 3:
:+
(style=
)
" accepts data from other applications via a straight "
# 4:
:+
(style=
)
cut & paste
# 5:
:+
(style=
)
" operation or using a more sophisticated "
# 6:
:+
(style=
)
XML
# 7:
:+
(style=
)
" data interface."
sample scenario.2
# 1:
:=
(style=
)
QuSheet's
# 2:
:+
(style=
)
" table-driven interface allows you to define "
# 3:
:+
(style=
)
selection
# 4:
:+
(style=
)
" and "
# 5:
:+
(style=
)
filtering
# 6:
:+
(style=
)
" criteria which organise your data into "
# 7:
:+
(style=
)
summary
# 8:
:+
(style=
)
" and "
# 9:
:+
(style=
)
detail
# 10:
:+
(style=
)
" paragraphs."
sample scenario.3
# 1:
:=
(style=
)
QuSheet
# 2:
:+
(style=
)
" automatically organises "
# 3:
:+
(style=
)
calculations
# 4:
:+
(style=
)
" to show "
# 5:
:+
(style=
)
results
# 6:
:+
(style=
)
" and "
# 7:
:+
(style=
)
""workings out""
# 8:
:+
(style=
)
" as paragraphs and sub-paragraphs."
show text
# 1:
.
text
(selector=
select text line
)
(style=
)
Summary
# 1:
=
Summary Line
(selector=
Select Text
)
(style=
)
Summary Line
# 1:
[=]
text
(field=
ae
)
(style=
)
# 2:
test =
a char
(style=
)
# 3:
true
text - addendum
(style=
)
# 4:
false
Summary Line - not a
(style=
)
Summary Line - not a
# 1:
[=]
text
(field=
ae
)
(style=
)
# 2:
test =
e char
(style=
)
# 3:
true
text - erratum
(style=
)
# 4:
false
text - normal
(style=
)
swf
# 1:
=
swf directive 1
(style=
)
# 2:
+
swf name
(style=
)
# 3:
+
swf directive 2
(style=
)
# 4:
+
swf name
(style=
)
# 5:
+
swf directive 3
(style=
)
# 6:
+
swf build
(style=
)
# 7:
+
swf directive 4
(style=
)
# 8:
+
swf name
(style=
)
# 9:
+
swf directive 3
(style=
)
# 10:
+
swf build
(style=
)
# 11:
+
swf directive 5
(style=
)
# 12:
+
swf name
(style=
)
# 13:
+
swf directive 6
(style=
)
text - addendum
# 1:
:=
line prefix
(style=
)
"A: "
# 2:
:+
text
(style=
)
text - erratum
# 1:
:=
line prefix
(style=
)
"E: "
# 2:
:+
text
(style=
)
text - normal
# 1:
:=
line prefix
(style=
)
# 2:
:+
text
(style=
)
Transcript
# 1:
.
(style=
)
# 2:
.
show text
(selector=
select text id
)
(style=
)
(expl=
id
)
View
# 1:
=
swf name
(style=
)
(expl=
swf
)
View Heading
# 1:
:=
view text
(style=
)
# 2:
:+
duration
(style=
)
)
# 3:
:+
(style=
)
You will need to view this page on a non-handheld screen to see the presentation.
Tables
a char
# 1:
a
addenda text
# 1:
Addenda
duration
e char
# 1:
e
errata text
# 1:
Errata
index page
line prefix
# 1:
(NL)
navigation directive 1
# 1:
<a href="./
navigation directive 2 back
# 1:
.html">previous</a>
navigation directive 2 forwards
# 1:
.html">next</a>
navigation directive 2 index
# 1:
.html">index</a>
predecessor
quick intro
quick intro part 2
# 1:
" for LINK(http://www.qusheet.com/main.index.html,QuSheet)"
space
# 1:
" "
successor
swf build
swf directive 1
# 1:
<OBJECT classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0" WIDTH="879" HEIGHT="550" id="
swf directive 2
# 1:
""> <PARAM NAME=movie VALUE=""
swf directive 3
# 1:
.swf?build=
swf directive 4
# 1:
""><PARAM NAME=quality VALUE=best><PARAM NAME=bgcolor VALUE=#000000><PARAM NAME=scale VALUE="exactfit"><EMBED src=""
swf directive 5
# 1:
"" quality=best bgcolor=#000000 scale="exactfit" WIDTH="879" HEIGHT="550" NAME=""
swf directive 6
# 1:
"" ALIGN="" TYPE="application/x-shockwave-flash" PLUGINSPAGE="http://www.macromedia.com/go/getflashplayer"></EMBED> </OBJECT>"
swf name
text
view text
# 1:
"View (duration "
Fields
ae
# 1:
a
# 2:
e
# 3:
n
dummy field
# 1:
0
id
Selectors
Select Text
# 1:
(field=
id
)
(table=
text
)
ascending
select text id
# 1:
(field=
id
)
(table=
text
)
unique
select text line
# 1:
(table=
text
)
line
Styles
Generation
allow_html_everything
Allow HTML in texts
allow everything (use with care)
true
Extend comma delimiter on integers
extend up and down column
4
Force indentation (amount)
4
min
Force indentation (type)
set minimum indentation
false
Generate print output?
no
handheld
Options for "small screen" output
as extra "handheld" media
true
Ignore "not found" errors?
within selection processing
200
Default Width (pixels) of Images
200
false
Optimise output spaces?
do not optimise
2
Pad size after operand
2
2
Pad size after post op total
2
2
Pad size after pre op total
2
none
Show usage message
omit
100
Output Width Size (as % of screen)
100
true
Process IMAGE, LINK and NL
yes
Sheets
123.revised
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
dynamic documents.1
)
# 5:
(base=
z base
)
(style=
)
(expl=
dynamic documents.2
)
# 6:
(base=
z base
)
(style=
)
(expl=
dynamic documents.3
)
# 7:
---
# 8:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 9:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 10:
---
# 11:
(base=
z base
)
(style=
)
Note that the Quick Win scenarios and the tutorials can now be found under <u>LINK(main.about.html,Support)</u>.
# 12:
(base=
z base
)
(style=
)
For other presentations:
# 13:
(base=
z base
)
(style=
)
(expl=
index page example presentation
)
# 14:
(base=
z base
)
(style=
)
(expl=
index page in action presentation
)
# 15:
---
# 16:
Transcript
(base=
z base
)
(style=
)
+ Field Values
+ Table Values
# 1:
swf name
123.revised
# 2:
swf build
11
# 3:
quick intro
QuSheet Overview
# 4:
duration
3m
# 5:
text
QuSheet is a windows program which enables you to communicate data and information to a client either as a web page on the WWW or as an individual email attachment, in such a way that your client can, with just a mouse click, expand or contract the amount of detail that they can see.
id
Slide 1
# 6:
text
By providing your client with a dynamic document, which they can view using any web browser, you enable your client to find the answers to their own questions immediately, as long as the information has been provided within the document. Questions such as:
id
Slide 2
# 7:
text
Where does this figure come from, and what does it include?
id
Slide 2
# 8:
text
What is the venue for the talk on hydroponics?
id
Slide 2
# 9:
text
Why am I not entitled to claim for the loss of my camera on holiday even though I took it on my surfboard?
id
Slide 2
# 10:
text
All this is done without burying your client in data or having them constantly on the phone to you.
id
Slide 2
# 11:
text
QuSheet takes the information you provide, either as headings or in tables of data, makes the necessary calculations, and presents the results in a neatly formatted document viewable by a browser.
id
Slide 3
# 12:
text
Everything is gathered efficiently into explanation groups and nested sub-groups.
id
Slide 3
# 13:
text
All your data is clearly formatted into columns, and everything is styled to your requirements.
id
Slide 3
# 14:
text
Take a look at some of the examples on the web site.
id
Where Next
# 15:
text
Or you might like to view the "Using QuSheet" tutorial. This will take you through installation and basic operation for the program.
id
Where Next
# 16:
text
The provided Quick Win scenarios will satisfy most needs, and you should be able to start producing your own QuSheet documents within around 30 minutes of downloading one. Creating your own scenarios from scratch may take just a little longer.
id
Where Next
# 17:
text
The "Working With QuSheet" tutorial is the more advanced tutorial of the two, and will take you through everything you need to know to use QuSheet.
id
Where Next
Generation Override
QuSheet and Dynamic Documents
Title
QuSheet and Dynamic Documents
in action
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
in action.1
)
# 5:
(base=
z base
)
(style=
)
(expl=
in action.2
)
# 6:
(base=
z base
)
(style=
)
(expl=
in action.3
)
# 7:
---
# 8:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 9:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 10:
---
# 11:
(base=
z base
)
(style=
)
For other presentations:
# 12:
(base=
z base
)
(style=
)
(expl=
index page overview presentation
)
# 13:
(base=
z base
)
(style=
)
(expl=
index page example presentation
)
# 14:
---
# 15:
show text
(base=
z base
)
(selector=
select text id
)
(style=
)
(expl=
id
)
+ Field Values
+ Table Values
# 1:
swf name
in action.revised
# 2:
swf build
7
# 3:
quick intro
QuSheet Overview
# 4:
duration
3m
# 5:
text
The simplest way to see QuSheet in action is to download and modify one of the examples on the web site.
id
Transcript
# 6:
text
This particular one here is the Builder example, a project with two output files, known by QuSheet as Sheets, one for the customer's quote and another for the builder's accounts.
id
Transcript
# 7:
text
Each sheet has entries which are basically line by line pointers to the Headings and Data which should appear, in order, in the output. Every line can actually specify two of these - one to be shown as a result and the other as its explanation.
id
Transcript
# 8:
text
Headings themselves are found within the Workbook part of QuSheet, and look pretty similar to the sheet's entries, with the addition that you can use the Apply column to make calculations from your headings and data.
id
Transcript
# 9:
text
Data is stored in Tables, which use Fields to define their columns.
id
Transcript
# 10:
text
It is possible, with QuSheet, to set things up in such a way that the output is entirely driven by this data. In other words, once you have done the work of defining how a sheet is to be produced, all you need to do to produce new sheets is change the data in your table.
id
Transcript
# 11:
text
For example, here I could add some plumbing work to my roof conversion, simply by adding a new line with the required values.
id
Transcript
# 12:
text
Selectors are used in conjunction with fields to set this data-driven behaviour up.
id
Transcript
# 13:
text
Generation Parameters and Styles control how the output is displayed.
id
Transcript
# 14:
text
Once all of your changes have been made, you can return to your sheet and use the Generate button to produce the output. This output file will appear in the same directory as your input / project file and will have the HTML extension so that it can be viewed by any browser.
id
Transcript
# 15:
text
Once generation has completed, the View button can be used as a shortcut method to invoke your favourite browser on the output.
id
Transcript
Generation Override
QuSheet In Action
Title
QuSheet In Action
kitchen.catalog
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
kitchen.catalog.1
)
# 5:
---
# 6:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 8:
---
# 9:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 10:
---
# 11:
show text
(base=
z base
)
(selector=
select text id
)
(style=
)
(expl=
id
)
+ Field Values
+ Table Values
# 1:
swf name
kitchen catalog
# 2:
swf build
2
# 3:
quick intro
Kitchen Example - Catalogue
# 4:
duration
15m
# 5:
predecessor
presentation.kitchen.intro
# 6:
successor
presentation.kitchen.customising
# 7:
index page
tutorial.index.kitchens
# 8:
text
There are a number of different methods you can use for importing data from outside sources into QuSheet. In the case of the kitchen example I lifted my price and parts data straight across from the Excel tables you can see here:
id
Transcript
# 9:
text
- the worktops are in this matrix of prices here
id
Transcript
# 10:
text
- as are my sinks
id
Transcript
# 11:
text
- my cookers are in these two lists
id
Transcript
# 12:
text
- and so are my fridges
id
Transcript
# 13:
text
Not a lot of data, I know, but it took literally seconds to import across.
id
Transcript
# 14:
text
You data doesn’t have to come from Excel, of course – anything where you cut and paste a matrix of values like this, where the first line and first column are headings, will do perfectly well.
id
Transcript
# 15:
text
If you want to do something more sophisticated and more automated you can go for an XML based solution, like this one here which again I’m demonstrating with Excel but which could be with any sort of XML based system you happen to have. This table is a price table so the value is basically the price and the next column is the name of the appliance with the different components of the name separated by a SPACE COMMA SPACE (you can make this separator whatever you like, by the way). Next to it is the field definition which basically cross-references with the price table so it needs to be the same as this column here.
id
Transcript
# 16:
text
With Excel you can add more entries at the end like this (remembering your separator, and remembering to put an entry in both the price table and the field).
id
Transcript
# 17:
text
Then you can do an export, go over to QuSheet, from the File Menu do an Import Replace XML data, and that’s it – if I go over to my Sheet / Table Addition now I’ve got myself a new sink.
id
Transcript
# 18:
text
I’ll talk a bit more about this XML process later.
id
Transcript
# 19:
text
First of all let me introduce a couple of QuSheet concepts – Sheets, the Workbook, Fields and Tables.
id
Transcript
# 20:
text
A QuSheet project – which is basically the file you open from here, and which has the DOT QUS DOT XML format – has one workbook and any number of sheets. The Kitchen example has two sheets, to make it consistent with other examples on the web site, but where the only difference between them is in the setting of this small-screen based generation parameter over here. If you’re interested in small-screen output take a look at the schedule presentation from the Examples web page here as that is much more geared towards this particular feature.
id
Transcript
# 21:
text
Anyway, QuSheet basically stores data using Tables and Fields. These are defined and populated within the Workbook area, though individual Sheets can add to these using the +Table Values and +Field Values sub-tabs. In order to separate out the user who produces a customer quotation from the administrator who manages your price catalogue I have put all the user’s table additions in the +Table Values page here for the Sheet. This also allows you, if you like, to keep track of more than one quotation within the project by Cloning a Sheet like this and then filling in new values in here. You have to Clone, incidentally, rather than do a New, because you need to keep your Sheet’s Entries if your sheet’s going to show anything at all (you can see the five output areas here). Keeping multiple quotes on one project will make your project file grow and grow, but it is a handy thing to do it you want to re-generate quotations later on when you make a price change. In fact, the Sheet List tab over here provides you with an easy way of doing this.
id
Transcript
# 22:
text
But anyway, for now I’m going to get rid of my new Sheet, just by using the Undo button a few times, and just work with one Sheet (this Quote one here).
id
Transcript
# 23:
text
Ok, so like I said, a Workbook defines Tables and Fields, which a Sheet can then add to. Tables and Fields appear in the separate Tables and Fields sub-tabs and you can use this drop down list over here to navigate to the right one. The Tables you are going to want to modify here are the various “Price Table” ones, and the fields will be their corresponding fields.
id
Transcript
# 24:
text
Fields, as you can see, appear as columns in Tables, and you may be wondering what tells QuSheet what Fields to display for what Tables. Any Table can actually hold a value for any Field, and what QuSheet actually does is display those Fields which have some value defined (either here or as a Sheet addition). Since, for example, the Price Table for Accessories doesn’t have anything defined in the Worktop field (and it shouldn’t), the worktop field doesn’t appear. The View menu, however, lets you change this if you like.
id
Transcript
# 25:
text
Note that columns are resizeable, and moveable. In fact, as you’ll see in a minute, we’ll need to move the column with the name over to the left hand side. If your table’s get a little scrappy you can right click on a column header and select Fit Width to tidy it up a bit.
id
Transcript
# 26:
text
Ok, so tables are just matrices of data with at least one column in (the Value of the table) and a number of extra columns depending on the Fields being used, and you will see that the 5 Price tables each use a different field to define the item that you are providing a price for. This item is specified using a line of text which is separated out with this SPACE COMMA SPACE here and you may be wondering whether you need to format up all of your data using SPACE COMMA SPACE or some other separator. In fact, you don’t – at least, you don’t have to. If you remember back here in the Excel spreadsheet I just had tables of data in without any separators – QuSheet does have a facility where it will put in this separator for you.
id
Transcript
# 27:
text
I will demonstrate this by adding in some dishwashers.
id
Transcript
# 28:
text
Over here on this Excel sheet I have a table of dishwasher prices. First of all, I will select this table, including the header line and column, and COPY. Note that Hotpoint (in this example, not necessarily in real life), hasn’t got a slimline option.
id
Transcript
# 29:
text
Next I will go over to QuSheet, go to Tables under Workbook, select the Price Table for Appliances, and move the Appliance field over to the left. You’ll see why I need to do this in a second. I’ll also make it a little bigger and tidy the other one up.
id
Transcript
# 30:
text
I will then do an Edit / Paste Add lines (and note the ADD) from Matrix. This will pop up quite a chatty little dialog box which tells me exactly what I’m going to do here – but in a nutshell this specialised Paste function will take my matrix of data (with the column and row header) and translate it into a two column matrix (which is suitable for what I want here) with the first column having a name and the second having the value. You’ll see what I mean if I just do it – I’ll put in a prefix of Dishwasher, make it rows then columns and ignore any empty cells, and here we go – our price table now has the 5 Dishwashers in it, with the names separated out with a SPACE COMMA SPACE. The reason they’re in grey is because I haven’t added these new values to my field yet so, without further ado, I’ll go over to the FIELD area and do the same thing (note that with the field, the column of prices is ignored). So now if I go back to my table you can see that the dishwashers are no longer grey, and if I go back to me Sheet / +Table Values I can now add dishwashers using the drop down list.
id
Transcript
# 31:
text
This SPACE COMMA SPACE separator, by the way, is defined under Preferences / General at the bottom here. Do be warned, though - changing this wont change your data, it’ll just change the way your data is interpreted by the LIST option I’ve just shown you and the way the Matrix Pasting function works. You’ll probably want to decide what you’re going to use here right at the beginning and then stick to it.
id
Transcript
# 32:
text
Of course, if you want to manage these separators yourself, you don’t have to use this Matrix Pasting function at all. These tables are all editable, like this, and there are some more straight forward copy and paste operations here as well. Copy and Paste works on the basis of what is visible and the order that it’s visible in, by the way – like this, you see.
id
Transcript
# 33:
text
And finally there’s the XML option – well, two XML options, actually.
id
Transcript
# 34:
text
QuSheet’s project file is, itself, entirely XML. Not the easiest XML in the world to work with since it has to handle the generic nature of the tool itself (i.e. you wont find tables called Accessory, for example). If you want to look at the Schema Definition file for a QuSheet project there’s an entry under Help over here on the right hand side which will let you do that.
id
Transcript
# 35:
text
The second XML option is the one I briefly touched upon earlier, and it basically works by QuSheet generating a Schema Definition file which reflects the project file you’ve currently defined. This schema definition file DOES have entries called Accessory or whatever – basically reflecting the tables and fields defined within the project. The Schema Definition AND the Data file are both exported from the File / Menu entry here (and note the little message box telling you the name of the files and where they’ve been put).
id
Transcript
# 36:
text
Excel can work with this quite well – in fact, I already have the schema definition defined as an XML source over here. Once I have done that and dragged and dropped the tables I’m interested in onto an XML sheet like this – I can just do an import to get the data I want
id
Transcript
# 37:
text
" - and then make changes and re-export like I did before (and I shant do it again cos you’ve seen that)."
id
Transcript
# 38:
text
Ok. Hopefully that’s told you everything you need to know to get your parts and price catalogue into QuSheet. In the next presentation I shall be telling you about how all the remaining simple changes you can make like styling, tax rates and what have you.
id
Transcript
Generation Override
Kitchen Example - Your Catalogue
Title
Kitchen Example - Your Catalogue
kitchen.customising
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
kitchen.customising.1
)
# 5:
---
# 6:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 8:
---
# 9:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 10:
---
# 11:
show text
(base=
z base
)
(selector=
select text id
)
(style=
)
(expl=
id
)
+ Field Values
+ Table Values
# 1:
swf name
kitchen customising
# 2:
swf build
2
# 3:
quick intro
Kitchen Example - Customising
# 4:
duration
9m 10s
# 5:
predecessor
presentation.kitchen.catalog
# 6:
successor
presentation.kitchen.modifying
# 7:
index page
tutorial.index.kitchens
# 8:
text
Simple customisation, by which I mean changes which don’t generally require you to understand the way that QuSheet actually processes your data in order to produce its output, basically comes down to some of the tables, styles and generation parameters. Not all of them, by the way – the ones we don’t cover now we’ll leave for the next presentation, when we’ll also be looking at Headings, Selectors and Entries.
id
Transcript
# 9:
text
So let’s have a look at a few of these Tables first.
id
Transcript
# 10:
text
If you recall from the previous presentation, you can change a table, or a field for that matter, either within the Workbook area, which basically applies to all Sheets, or individually for a given Sheet, and the way this project has been structured is to have some of the parameters set in the Table Additions area under Sheet and the rest in the Workbook.
id
Transcript
# 11:
text
However, just to illustrate how these two areas are essentially the same, you’ll recall how I said that a Delivery miscellaneous entry was automatically set to work as a Fixed unit, well that’s because if you look at the _unit table under Workbook you’ll see that it’s set to “fixed” for Delivery.
id
Transcript
# 12:
text
Three other underscore style table entries that have been set in the Workbook are the _tax rate, the _general intro paragraph and the _general farewell paragraph. These have been defined here to stop the + Table Additions area from being cluttered up with entries that would never change from one customer to another.
id
Transcript
# 13:
text
Jumping across to the Generation parameters, this is where you’ll find the title that appears at the top of the output, plus a number of other parameters which you can experiment with. Note how the yellow help pane changes to reflect what you select to tell you what a parameter is all about (this is generally how the help system works here).
id
Transcript
# 14:
text
You may wish to put in some graphics here like a company logo or what have you. Do beware though – this logo isn’t packaged in with the file that QuSheet produces, which means it will only be displayed if your client is logged on to the internet and can access whatever the picture is wherever it’s found.
id
Transcript
# 15:
text
Finally we get on to the styles, which is where pretty much all of the options for display format are set. As with tables, there are quite a lot of these defined, and some (the ones beginning with a Z) are always present, but again as with tables I’ve given the ones that I think you’re likely to want to change a name beginning with an underscore.
id
Transcript
# 16:
text
Ok – so taking them from the top down:
id
Transcript
# 17:
text
_color (center), under default, defines the background colour for the central area.
id
Transcript
# 18:
text
_general lines, again under default, defines the background colour for the general hello and farewell paragraphs.
id
Transcript
# 19:
text
_heading style defines the display options for the headings line, either at the top level or by item. The four sub-tabs, Pre Op Total, Op, Post Op Total and Explanation, refer to the four possible columns in the output (as you can see here). Not all of these columns are always displayed, and the default tab can be used to specify something applying to all the columns (so, for example, you can see here that headings are left aligned by default, but the second heading is over-ridden to be centrally aligned). Note that the default tab settings also apply to the indentation area, which is why the background colour for the headings is set individually rather than setting a default.
id
Transcript
# 20:
text
_headings for item, which as you can see here is based on the _heading style, primarily sets the type of display for the line to FIXED, which means the output is actually defined by the style, and then sets the various names for the heading columns. The final column doesn’t have a heading so this is cleared out and the background set to the same as _color (center) (like we saw earlier).
id
Transcript
# 21:
text
_item line is the basic style used to show a line item. Other styles build from this, but this one in any case sets the background colours and the currency specifier for the third column, which is always a total price.
id
Transcript
# 22:
text
The next three _item line styles build on the _item line style by defining the units to use with the different types of item (by unit, by meter and by meter squared). Note that there is no style for fixed price line items because fixed price line items don’t appear at this level – they appear at the level above.
id
Transcript
# 23:
text
_specific lines, again under default, defines the background colour for the specific hello and farewell paragraphs.
id
Transcript
# 24:
text
And finally you have _total line, which is the style used to display one of these total lines at the top level, and which you can see sets the currency for the second column.
id
Transcript
# 25:
text
Actually, that’s not quite the end. There is one other style which you need to keep an eye on: z default, the style that defines everything which hasn’t been defined anywhere else. The background colour defined here, for example, gives you the colour used right at the top and bottom of the sheet.
id
Transcript
# 26:
text
You may have a few questions with respect to how styles work after looking at all this – like, for example, what happens if you set something else rather than colour in the _color (center) style. Well, this is what all those presentations in the tutorial area, under support, are there to explain. As I’m sure you can guess there is a sophisticated style search system here, and I’ve simply used this to set certain parameters in certain places to make things reasonably easy to find. Feel free to experiment, but bear in mind it’s easy to get muddled up if you start specifying parameters all over the place and forget where you’ve set things.
id
Transcript
# 27:
text
Ok, next presentation I shall be explaining how this project works with QuSheet and showing you how to change the output groups, set up new ones and how to set up different pricing models (i.e. like a price per gallon).
id
Transcript
Generation Override
Kitchen Example - Customising your Output
Title
Kitchen Example - Customising your Output
kitchen.intro
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
kitchen.intro.1
)
# 5:
---
# 6:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 8:
---
# 9:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 10:
---
# 11:
show text
(base=
z base
)
(selector=
select text id
)
(style=
)
(expl=
id
)
+ Field Values
+ Table Values
# 1:
swf name
kitchen intro
# 2:
swf build
4
# 3:
quick intro
Kitchen Example - Introduction
# 4:
duration
15m 30s
# 5:
successor
presentation.kitchen.catalog
# 6:
index page
tutorial.index.kitchens
# 7:
text
Thank you for taking the time to consider QuSheet as the tool you will use improve the way that you communicate with your clients.
id
Transcript
# 8:
text
In this series of presentations I shall be showing you how you can use QuSheet with the Kitchens project file, which you can find over here on the Examples page on the web site, in order to produce output looking like this. This output, as you can see, is in HTML, or browser format, which makes it perfect to send as an attachment to your customers, since any customer with a PC is guaranteed to have a browser that they can use to view this file.
id
Transcript
# 9:
text
In this particular presentation, I shall quickly run through the features of the output file itself and then show you how it was generated from the project file which has already been created for you. Later presentations will show you how to modify this project file by putting in your parts and price catalogue and how you configure QuSheet’s output and operation in various ways.
id
Transcript
# 10:
text
Just before we begin, though, let me briefly assure you of QuSheet’s flexibility by pointing out how the same tool which created this pricing quotation can also be used to make:
id
Transcript
# 11:
text
a conference schedule, particularly for small screens like mobile phones and PDAS,
id
Transcript
# 12:
text
a revenue report, such as this one here for a fictional haulage company,
id
Transcript
# 13:
text
or even a tenancy agreement like this one over here.
id
Transcript
# 14:
text
You are more than welcome, of course, to look at the other examples, but otherwise simple bear in mind as you watch these presentations that there is a lot more tailoring available should you wish to explore how the tool works in more detail.
id
Transcript
# 15:
text
Ok, returning to the Kitchen output here, I have tried to create something which I hope will satisfy most people’s needs. This document, as you can see, is separated into 5 regions – two greetings ones, two farewell ones and a middle area where all the calculated information is presented. The idea behind having two greeting and farewell areas is that the outside ones contain generic messages relating to your company and the inner ones contain specific messages ones relating to your customer.
id
Transcript
# 16:
text
In the middle, after the heading line, we have the four groups of sale items, and these can be expanded by clicking on the chevron over here.
id
Transcript
# 17:
text
Note how everything lines up, up and down the columns. This is a unique feature to the way that QuSheet constructs its output, which is basically by formatting the output as a whole rather than line by line. If you’re wondering why there is such a gap between the quantity and the unit price here, for example, it’s because further on down, under Flooring, there’s a quantity provided using a lengthy unit specifier (meters squared) forcing all the other columns to shift across.
id
Transcript
# 18:
text
Flooring and Delivery are part of a 5th group known as the Miscellaneous group. This group behaves slightly differently than the others in the sense that any items placed in this group are reported at the top level here rather than appearing under another group (i.e. a “Miscellaneous” one). These items also support different pricing units, like meters squared or, with delivery here, a fixed price for the whole item.
id
Transcript
# 19:
text
Following the miscellaneous entries you can see a Subtotal area, some tax and a final total. The tax rate is, of course, configurable.
id
Transcript
# 20:
text
You may wonder how this document looks on paper. Well, QuSheet generates a separate section within the output to accommodate this, as you can see if you do a Print Preview.
id
Transcript
# 21:
text
Let me now navigate over to QuSheet itself and show you how this file was generated.
id
Transcript
# 22:
text
QuSheet is a Windows program with a number of matrices and forms all packaged up in tabs and sub-tabs. Although this looks complicated, most of the complexity is down to how QuSheet’s project file is produced – and I’ve basically done that for you with this example. Later presentations will get into some of the details that let you tailor QuSheet, but for now all I want to show you is the final stage – the bit where you basically make your final selections for the document you want to send to your customer. That bit can be found under the Sheet tab at the top, and the “plus table values” underneath, here in the 14 entries in this matrix of values.
id
Transcript
# 23:
text
You notice I used the work MATRIX rather than TABLE to describe this very table looking thing here. The reason I do that is because QuSheet uses tables to mean something else and I don’t want to overuse the word. This matrix, in fact, specifies additional values for QuSheet’s tables, where the name table appears in this first column on the left. I have defined a number of tables for this project some of which you will want to make additions to and some not. In order to make life easier for you, Ihave deliberately named the ones you will want to change with an underscore in front, which makes them appear at the top of this drop-down list.
id
Transcript
# 24:
text
Make sure, incidentally, that you have Quote rather than Quote (forced small screen) selected up here. I’ve created a forced small screen sheet here just to be consistent with all the other examples on my web site but you can ignore it, or even delete it, if you’re not interested in PDA or mobile phone devices.
id
Transcript
# 25:
text
Ok, so here you can see the first two lines containing values for the inner farewell and greeting lines, followed by lots of settings of quantity, a couple for price and one here for unit. This matrix you will see has a large column for the value of the table itself and then a number of columns providing further information about that value – generally speaking, the actual item that the customer is getting some quantity of. These columns are actually called FIELDS, and I will be talking more about them in later presentations.
id
Transcript
# 26:
text
Anyway, in this example I have put in some dummy cataloguing data for worktops, accessories and appliances, which is why these areas are not coloured grey. It also means that I can select an item by right-clicking on the cell I want to change, selecting LIST and then navigating through the various sub-menus presented. Like this here ..... and this ..... It also means that I do not have to specify a price – that’s already within my project file somewhere (and I’ll show you where in the next presentation).
id
Transcript
# 27:
text
I’ve deliberately left the Cabinet area empty (as you can see if I right-click here – no LIST option appears) just for demonstration. Any of these groups will actually accept free-form text – QuSheet colour-codes just to show you it can’t find a match within your catalogue. For example I’ll put in a dishwasher in here now, which I haven’t defined in the catalogue, just to show you. First I control CLICK (i.e. left click with my mouse with the control key held down) on a down arrow to put in a copy of a line and I’ll change that to dishwasher. Then I’ll copy that line, in the same way, with control click, and change my table to _price and the value to some suitable price.
id
Transcript
# 28:
text
Incidentally, specifying a price for something here will over-ride whatever price is in the catalogue.
id
Transcript
# 29:
text
Ok – so that’s the main categories. Further down here we have the Miscellaneous area, where you can put anything you want to appear at the top-level of your output.
id
Transcript
# 30:
text
Items in the Miscellaneous area need two, possibly three things. They need a quantity, just like the other categories, and they need a unit, which should be either "m", "m2", "fixed" or "unit" (which is the default if you don’t provide one), all in lower case. If your unit is fixed, which is automatically the case for Delivery here, then you need nothing else, the quantity is effectively the fixed price, otherwise you also have to specify a price.
id
Transcript
# 31:
text
Well, when you have done all that, you can navigate up here and hit the Generate button, and QuSheet will chug away through your data and your catalogue and this template file and so on and produce, in the same directory that you stored your project file in, which is generally one called QuSheet under your MyDocuments area, an output file called kitchen (because that’s the name of the project file) DOT quote (because that’s the name of this sheet) DOT HTML. The VIEW button here then gives you a little shortcut way of invoking your browser to go and have a look at it.
id
Transcript
# 32:
text
If you’ve seen enough now to want to have a play with this yourself, navigate over to QuSheet’s main page (www.qusheet.com), go to Buy Now and follow the instructions there with an Evaluation Licence Key if you would like to evaluate this first. This will install a working version of QuSheet on your PC and create a directory called QuSheet in your Documents or MyDocuments area. Once you’ve done that, navigate over to the Examples area and save the source link underneath the Kitchen example. If you save that to the QuSheet directory you should then be able to open it from QuSheet and do a bit of generating.
id
Transcript
# 33:
text
The next presentation will explain how you import your parts and price catalogue.
id
Transcript
Generation Override
Kitchen Example - Introduction
Title
Kitchen Example - Introduction
kitchen.modifying
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
kitchen.modifying.1
)
# 5:
(base=
z base
)
(style=
)
(expl=
kitchen.modifying.2
)
# 6:
---
# 7:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 8:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
# 12:
Transcript
(base=
z base
)
(style=
)
+ Field Values
+ Table Values
# 1:
swf name
kitchen modifying
# 2:
swf build
2
# 3:
quick intro
Kitchen Example - Modifying
# 4:
duration
18m
# 5:
predecessor
presentation.kitchen.customising
# 6:
index page
tutorial.index.kitchens
# 7:
text
This presentation has 3 parts to it all related to making modifications which change or add to the number of pricing groups in the output. All of these will be illustrated using the, maybe slightly curious, idea of adding paint to the list of items which the kitchen company sells (to paint your kitchen, presumably). This paint will be sold by the litre, and you can see that I’ve already got a price list set up in an Excel spreadsheet over here, ready to go into QuSheet.
id
Introduction
# 8:
text
In the first part of this presentation, I will describe how you add a litre based pricing structure, and illustrate this using a Paint miscellaneous entry.
id
Introduction
# 9:
text
In the second part, I will show you how you could rename one of your existing groups to Paint – which is the easiest option if you happen to have a group which you no longer need.
id
Introduction
# 10:
text
In the third part, I will show you how to add a completely new group called Paint, leaving your existing groups as they are.
id
Introduction
# 11:
text
In each case, I will save the project file as kitchen m 1, 2 and 3, which you’ll then be able to download from QuSheet’s web site if you like.
id
Introduction
# 12:
text
Ok – part 1: adding a liter based price structure. Here I am with the kitchen example that you’ve seen so far, and let me first save this as kitchen m 1, so I don’t lose my old one. Then the first thing I’m going to do is go over to the styles area under workbook and select underscore item line price per m (the one that’s used for meter).
id
Part 1
# 13:
text
Price per m (meter) is pretty similar to price per l (litre), so I’ll just clone this one and modify it. Note how the new name appears in italics in the drop-down list – this is to tell you that currently this particular style is not referenced from anywhere else in QuSheet (i.e. it’s orphaned). This will change in due course.
id
Part 1
# 14:
text
You’ll recall from the previous presentation that these styles are built from the _item line style, which sets the display unit for the last column. What we need to do here is change the display units for the first and second columns, which we can do just by changing the prefix texts from m to l (an abbreviation for litre).
id
Part 1
# 15:
text
Ok, that’s it – nothing else to do there. Next we need to go to the Tables area and define how we will identify litres in our units, which as you can see I’ve done here using this set of little tables beginning with “units”. I’ll create a new one here called “units – l” and stick an l in. The reason the last units table in the list is orphaned, by the way, is because “unit” is the default option so I don’t bother checking for it. I could actually just get rid of this table but I’ve left it in for completeness.
id
Part 1
# 16:
text
Next we need to create a heading to handle litres in the miscellaneous group – which is all we’re supporting in this part of the presentation. We already have a heading called “itemise misc (m)” as a template, so we’ll clone that to “itemise misc (l)” and then we’ll change the style on the second line to point to our new litres style. Note how we’re still orphaned here, by the way.
id
Part 1
# 17:
text
Finally we need to go to the “itemise misc” heading and slot our new one in. This heading follows a pattern you can see here – first we set the unit then we start checking it. If the unit hasn’t been set, we treat is as a fixed price. After that we compare against our various units tables and branch off to the various itemise headings respectively, finishing off with the UNIT version if we haven’t made any other match.
id
Part 1
# 18:
text
Each comparison uses three lines: a set, a comparison and a restart – so I’ll use SHIFT and click on the up arrow of the last line to add three blank lines just before the last line, like this.
id
Part 1
# 19:
text
The operator of these lines will come up with whatever operator was last set – it doesn’t matter, we’re going to over-ride it.
id
Part 1
# 20:
text
First line we do a SET on _unit with style z do not display.
id
Part 1
# 21:
text
Second line we do a COMPARISON, TEST =, with our new units – l, and again with a style z do not display.
id
Part 1
# 22:
text
Third line we do a RESTART if TRUE, with our new itemise l heading, explanation misc and style _total line.
id
Part 1
# 23:
text
And that’s it. If we look at our styles line you’ll see that our itemise per litre style is no longer orphaned, and if I go over to table additions I’ll demonstrate this by changing the flooring to paint, leave the quantity and price the same for now (note I’ve not yet put in any paint price tables – this is just to demonstrate litres), change the unit to l and generate.
id
Part 1
# 24:
text
Well – rather than get you to wait for that to happen, I’ll just show you the output – we now have $180 of paint, 20 litres at $9 per litre.
id
Part 1
# 25:
text
And that’s part 1 – which I’ll save. Part 2 is now all about changing the name of an existing group.
id
Part 1
# 26:
text
Ok, so let’s start part 2 by saving our file again, to “kitchen m 2”, and then by getting rid of these three paint lines in the table additions area, because we now want to have a paint group with a proper list and prices just like the other ones. In this case we’re simply going to re-name our cabinet group to do this quickly and easily (and assuming we’re no longer interested in selling cabinets).
id
Part 2
# 27:
text
First stage is to do some renaming. Under Tables: The Price Table for Cabinet becomes the Price Table for Paint. Under Fields: rename cabinet to paint. Under Selectors, select cabinet becomes select paint. Then finally there are four to rename under headings: Item Cabinet (to Paint), Price Cabinet (again, to Paint), Itemise Cabinets (to Itemise Paints) and Total Cabinets (to Total Paints). We’re almost there now – as you can see, our renaming percolates throughout QuSheet, so everything in this itemise Paints area points to paints now. What we need to do now is change this style line from price per unit to price per litre and then go over to the TOP LEVEL heading and change this little bit of text from Cabinets to Paint (I’ll also click on the down arrow here to move the Paint line down a bit).
id
Part 2
# 28:
text
I’ll now quickly put in the price list for the paints, as I’ve shown you in the second presentation. First I’ll go over to the Price Table for Paint and get QuSheet to display the paint field (it isn’t because this table is empty right now). Move it to the left and re-size a bit, then go over to Excel and just do a straight copy and paste of the values (I’m not using the matrix pasting functionality because I don’t have multi-menus here, just a list of colours). Then I’ll go over to the Fields area and do the same thing.
id
Part 2
# 29:
text
Now I can go to my table additions and change these cabinet lines to a paint line. We don’t need a price line anymore because we’ve put a price list in. Select the paint colour, quantity and generate and we’ll get (here’s one I did earlier), this output over here.
id
Part 2
# 30:
text
And that’s part 2 done – so again, let me save this.
id
Part 2
# 31:
text
Ok, part 3 then, which is all about creating a brand new group. I’m going to go back to where I was at the end of part 1, and this time I’m going to add a new group called Paint rather than rename Cabinets. This is going to look very similar to what I did in part 1 – i.e. I’m going to be cloning things – but on the headings and so on that you saw in part 2.
id
Part 3
# 32:
text
Let me start like I did with the other parts by saving this example as kitchen m 3, so I don’t mistakenly over-ride kitchen m 1. Then I’ll do as before and get rid of these three Paint lines here in Table Additions, because we’re no longer going to be showing Paint as a miscellaneous, and then go over to my workbook and start some adding and cloning.
id
Part 3
# 33:
text
I’ll need a Price Table – so I’ll just create a suitably named one. And a Field – so I’ll create that too.
id
Part 3
# 34:
text
Back to the table, I’ll make my paint field visibile. Move it to the left. Resize a bit. Go over to my Excel spreadsheet like I did before and bring across the prices into the Price Table (pause) and into the field. This is just as you saw with the last part but note I’m now putting my prices into a new table rather than a renamed old one.
id
Part 3
# 35:
text
Next I need to modify the DO NOT USE table. This basically gets used by the selectors to make sure that when you are looking at one group you don’t mistakenly pick up entries in another. I’ll make my paint field visible here again, and add in DO NOT USE for paints as well.
id
Part 3
# 36:
text
Now, my selectors. This is a slight pain in the neck, I’m afraid, but you need to make sure, first of all, that each selector has a line at the end for paint specifying DO NOT USE. You can do this (relatively) quickly by doing a control click on the down arrow of the last line with an arrow on to make a copy of that last line, then change the field name to paint. Five times, I’m afraid.
id
Part 3
# 37:
text
Now we need a selector for the paint itself. I’ll just clone this one to create Select Paint, and switch worktop and paint over so that we’re picking paints and not worktops.
id
Part 3
# 38:
text
Ok. Time for the headings now. I suggest we start by cloning Price Accessory to Price Paint first, like this, and then point it to the right Price Table.
id
Part 3
# 39:
text
Next we’ll clone item (accessory) to item (paint), like this. Change our two explanations here to paint, and change this forced set line here to point to our new Price Paint heading.
id
Part 3
# 40:
text
Next I suggest we clone Total Accessories to Total Paint, which is a nice straight forward one again, changing the add line to our new item (paint) with a selector equal to our new select paints.
id
Part 3
# 41:
text
Our last clone is Itemise Accessories to Itemise Paints. The second line, the set line, needs to be changed completely to point to paints now rather than accessories, and note how we change the style too so that it automatically uses a per litre basis.
id
Part 3
# 42:
text
All of our new stuff is still orphaned, as you can see, because we haven’t yet put it into the top level heading, which is the one that everything is driven from. So let’s sort that out now. If I do a control click on the down arrow on Itemise Accessories I will put it a copy of that line which I can then change to itemise my paints. Like that. Then I’ll do the same with the total line further down. Like this.
id
Part 3
# 43:
text
And we’re done. As you see if I go back to table additions I now have an extra column here for paint, and I’ll stick a bit of blue and a bit of red at the end here and show you what the new output looks like.
id
Part 3
# 44:
text
And there you go – all done.
id
Part 3
# 45:
text
Hope you found all that clear. Don’t forget there are other tutorials available from the support area on the web site, and I hope you enjoy using the product.
id
Part 3
Generation Override
Kitchen Example - Modifying
Title
Kitchen Example - Modifying
pda_schedule
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
pda_schedules.1
)
# 5:
(base=
z base
)
(style=
)
(expl=
pda_schedules.2
)
# 6:
(base=
z base
)
(style=
)
(expl=
pda_schedules.3
)
# 7:
(base=
z base
)
(style=
)
(expl=
pda_schedules.4
)
# 8:
(base=
z base
)
(style=
)
(expl=
pda_schedules.5
)
# 9:
---
# 10:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 11:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 12:
---
# 13:
(base=
z base
)
(style=
)
For other presentations:
# 14:
(base=
z base
)
(style=
)
(expl=
index page example presentation
)
# 15:
(base=
z base
)
(style=
)
(expl=
index page in action presentation
)
# 16:
---
# 17:
Transcript
(base=
z base
)
(style=
)
+ Field Values
+ Table Values
# 1:
swf name
pda_schedule
# 2:
swf build
3
# 3:
quick intro
PDA Schedule Example
# 4:
duration
23m
# 5:
text
Thank you for taking the time to consider QuSheet as the windows tool you will use to produce your conference schedules so that they can be viewed on small, hand-held, screens.
id
Introduction
# 6:
text
I have structured this presentation in the following way: First, I describe QuSheet’s output, with particular reference to the schedule example, that you’ve hopefully already seen. Second, I show you how you can tailor this example by getting your own conference data into QuSheet and by making styling changes such as modifying the colours and date formats. Finally, I describe how you can download and run QuSheet so that you can get your first conference schedule produced straight away.
id
Introduction
# 7:
text
Here, in front of you, is the schedule example web page, sized and zoomed inside a browser in a way which simulates how it would look on a mobile phone. As you can see, the various little pages of information have been linked together, forwards and backwards, using these little chevrons.
id
Output
# 8:
text
This system is ideal for display on small screens but, as you can imagine, not so terribly good on large ones. If I open the same file on a normal browser window you’ll see what I mean.
id
Output
# 9:
text
Ordinarily QuSheet will produce output suitable for large screens, as well as small ones and hard-copy, all within the same file. I have such a file open here on another tab. As you can see, in this situation, the schedule is presented a little differently, with the chevrons opening up extra levels of detail underneath the relevant lines, and then closing them up like this.
id
Output
# 10:
text
The Opera browser, which I’m using here, and which is also available for hand-held devices, allows me to switch between normal screen and small-screen output like this.
id
Output
# 11:
text
Unfortunately, at present, most PDAs and mobile phone browsers do not support this type of operation, and basically always show the default view. For that reason QuSheet has a switch to get it to generate the small-screen output as the default for the page, which is what I showed you originally.
id
Output
# 12:
text
I know from looking at your web sites that you already have attractive and sophisticated web pages set up to display your conference schedules on normal sized PC screens, so I imagine you will only want to use QuSheet to produce the small-screen version of your schedule. The other option is, of course, there if you want it.
id
Output
# 13:
text
Hard copy display, incidentally, is unaffected by any of this. If someone chooses to print out QuSheet’s schedule they will see something like this.
id
Output
# 14:
text
Moving on to QuSheet itself, once you have downloaded and licenced it (which you can do with an evaluation licence if you like), you will be presented with QuSheet’s normal windows first page like this.
id
Input
# 15:
text
Assuming you’ve also downloaded the example from the web site (and I will be showing you how to do all of this later) you will also be able to open that file from your QuSheet directory like this - at which point you will be greeted by a rather frightening looking table, with lots of tabs and options and so on.
id
Input
# 16:
text
Happily, since you’re just going to be modifying this example by adding your own data and style changes, you don’t have to worry about all this complexity at all. All you need to do to get started is to go to the Tables tab under Workbook, and then begin by looking at the _schedule table over here.
id
Input
# 17:
text
Note the underscore in front of the name, by the way. I have deliberately named any table or style which you might want to change, with an underscore, just to make it easier for you to home in on what you might want to modify.
id
Input
# 18:
text
As you will see later, all the information in here can come across from other applications, but let me just start by telling you what you’ve got in front of you in case you simply want to edit it the entries for yourself by hand.
id
Input
# 19:
text
This _schedule table contains, as you might expect, everything in your schedule. The first column has the name of the event, which doesn’t have to be unique (as you can see I have lunch in twice), unless you want to provide different details using the _details table (which I’ll now briefly go back to over here).
id
Input
# 20:
text
In this table the X column (which I’ll just expand so that you can see it) corresponds to either the Value or Speaker column of the _schedule table that I was just showing you. The value entry here defines the extra details that you might want to show for an event or speaker. Clearly if you’ve named two of your events exactly the same way then QuSheet will just put out exactly the same details – which is fine if that is what you want.
id
Input
# 21:
text
The details table has these details, and they cross-reference using this X column to the _schedule table, which I’ll go back to now.
id
Input
# 22:
text
As well as the event name, we have here a date, room, speaker and start and end times. The only reason I’ve called these last two columns T_BEGIN and T_END, by the way, is just to get them to appear together in the right order at the end of the table.
id
Input
# 23:
text
Anyway, you can edit any of these entries, like so, for example, (Use <control> click on an arrow to duplicate a line or <shift> click on an arrow to insert a blank line) or you can use a right-click to pull up specific editing windows, like date and time. As you can see, where there is no speaker associated with an activity there is a little dash here. You do need to remember to put that in.
id
Input
# 24:
text
Apart from the _schedule table and the _details table which you’ve already seen, what else is there. Well, you have a _highlight table, which basically contains the name of any _schedule event which you want highlighted in a different colour (typically for lunches and coffee breaks and things). After that you just have two, straight forward, single entry tables. One describes the venue which appears at the top of the web page. And the other provides some instructions. This one can be particularly useful to you if you want to put out a little bulletin message at the top of your schedule which your delegates will be able to see on their mobiles and PDAs as the conference goes on.
id
Input
# 25:
text
Finally, the title of the conference is set in the Generation tab over here and that’s basically everything you need to change by way of your data rather than styles (which I’ll get into in a minute).
id
Input
# 26:
text
As I said earlier, QuSheet supports two ways of importing and exporting your data to other applications. I will demonstrate the first of these and then briefly touch upon the second.
id
Input
# 27:
text
Up here under the Edit Menu there are three slightly specialised Copy and Paste operations. In order to demonstrate how this works I’ll do a Copy entire table now and then navigate over to Excel.
id
Input
# 28:
text
Here I will paste. Then change Excel’s columns a bit so that you can see the table properly. Then I’ll change something. Select it all again. Copy it. Go back to QuSheet. And do a Paste replace. And that’s it – nice and easy.
id
Input
# 29:
text
Just as a little note let me tell you that QuSheet bases its copy and paste operations on the table that you see in front of you and that since you can change what is displayed here in various ways (like changing or rearranging the columns) this mechanism is something that you can affect, though it’s not something I’m going to go into now. The QuSheet web site, incidentally, has lots of tutorials showing you how these sort of things can be done.
id
Input
# 30:
text
And as a second note, let me point out to you that the paste operation is undoable, like this, but that we’ll leave it *done* for now so that I can demonstrate how these changes work. All these little modifications that I am doing in this presentation, incidentally, are undoable in the same way.
id
Input
# 31:
text
That’s one way you can get things in and out. The other way is to use XML. Like I said before, this isn’t something I’m going to go into in great detail here. There is another presentation, linked to just below this one here which shows an example of XML data being imported and exported. All I will tell you now is that there are three menu entries here under File which allow you to export and import XML data, and that the export function, in particular, writes out a Schema Definition file as well as well as the data. Those of you who know about these sorts of things will know that this is the file which is necessary in order to have other applications work with and provide this XML data.
id
Input
# 32:
text
The final part about customising your example comes down to Styles, which are over here on the right hand side of the Workbook area.
id
Customisation
# 33:
text
Now QuSheet is a very versatile product with a lot of functionality controlling how your output comes out. For this example, however, I have put all the styling information that you might want to change in styles beginning with an underscore, and I’ll go over them all now.
id
Customisation
# 34:
text
To start with the _date style has, in its default area, a specifier indicating how a date should be displayed. You can change this if you like using this drop-down list.
id
Customisation
# 35:
text
The _time style, as you can see, does something similar for times, but note that you will need to select the times options based on seconds.
id
Customisation
# 36:
text
Over here, the style called _general schedule colours defines the three colours that are used in the three items displayed in the schedule, i.e. the times, the room and the speaker. Clicking on a colour or a colour area brings up this big grid to let you choose whatever colour you want to use. Like so.
id
Customisation
# 37:
text
The _highlighted schedule line style, under the default tab, defines how the lines you have chosen to highlight should be displayed. Whilst the _schedule line even and _schedule line odd styles provide the background colours for the alternating normal schedule lines that are displayed.
id
Customisation
# 38:
text
The _speaker details style, under the Explanation tab in this case, sets the background colour to use when displaying details about the speaker. And the _schedule details style does the same for the details of the event, though note this is currently set to leave the colour unchanged (i.e. at its default).
id
Customisation
# 39:
text
Indeed, as I’m sure you will have noticed with these styles, they don’t tend to specify very much. This is because the whole style system is based on over-riding whatever has been specified under a special style called “z default”. The way all of this overriding takes place is well beyond the scope of this presentation however I will just indicate to you that the Background and Foreground colours under the Default tab under “z default” determine the background and foreground colours which are used on the whole page, so this is where you need to go to change those. And that’s it – that’s really everything you need to know to customise this example for your own use.
id
Customisation
# 40:
text
Once you’ve made whatever changes you want to, navigate over to the Sheet tab here at the top, select either a normal sheet or a pda one (the only difference, as you will see, being here in the Generation Override tab), hit the Generate button and watch the wheels go round.
id
Generation
# 41:
text
How long the generation process will take depends on your system and the size of your schedule. On my machine with this example it takes about 30 seconds or so.
id
Generation
# 42:
text
Since this file is called “schedule” and the sheet is called “pda” QuSheet will generate an html file called schedule.pda and put it in the same directory as the input file (probably your QuSheet folder). Once generation has finished, the view button here can be used to open up your preferred browser (which you can set under the preferences / resources tab) to view it.
id
Generation
# 43:
text
And here you can see the new file, with all the changes we have put in. Different date, different styling, and so on.
id
Generation
# 44:
text
So what do you need to do now to get yourself a copy of QuSheet and start working on your own schedule.
id
Purchase
# 45:
text
First of all, from this presentation page here you can navigate to the Buy Now page and follow the instructions for downloading, licencing and running the product. You don’t actually have to buy a licence now if you don’t want to. You could get yourself an evaluation licence instead if you like, which will last you until the end of the next calendar month.
id
Purchase
# 46:
text
Assuming you do all this, the first thing QuSheet will do when it runs up is to create a QuSheet folder for you under your MyDocuments or Documents directory.
id
Purchase
# 47:
text
If you then navigate back to this presentation page you can right-click here and save yourself a copy of the example file - and that’s it - you’re ready to start. If you do have any problems, please don’t hesitate to get in touch. Thank you very much for listening.
id
Purchase
Generation Override
QuSheet, Schedules, PDAs and Mobile Phones
Title
QuSheet, Schedules, PDAs and Mobile Phones
quickwins.accounts1
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
accounts1
# 2:
swf build
7
# 3:
quick intro
Part of the Accounts Quick Win scenario
# 4:
successor
presentation.quickwins.accounts2
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
14m20s
# 7:
text
Workbook / Tables (“items”) contains the basic accounting information which feeds this scenario. Every row in the table is a separate income or expense. The first column in the table gives a description of the entry. This is followed by an amount (negatives for expenses), a category, a date and a unique id.
ae
n
id
1
# 8:
text
Category values can be specified under Fields (“category”) as a convenient way to input categories into the table from a list, though this is not necessary.
ae
n
id
2
# 9:
text
If your date range crosses more than one year, you must put the extra years in as values in Workbook / Fields (“year”).
ae
n
id
3
Generation Override
Accounts part 1
Title
Accounts part 1
quickwins.accounts2
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
accounts2
# 2:
swf build
4
# 3:
quick intro
Part of the Accounts Quick Win scenario
# 4:
predecessor
presentation.quickwins.accounts1
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
14m40s
# 7:
text
Style “_ currency”, under Default, controls your currency specifier and the way that negatives are displayed.
ae
n
id
1
# 8:
text
Style “_ top line”, under Default, controls the top line of your accounts.
ae
n
id
2
# 9:
text
Style “_ summary headings”, controls the headings for the summary area, under “Pre Op Total” for the first column, “Op” for the second and “Post Op Total” for the third.
ae
n
id
3
# 10:
text
Style “_ summary line”, under Default, controls all summary line columns (all are styled the same). Use individual tabs if you want to change individual columns.
ae
n
id
4
# 11:
text
Styles “_ detail headings” and “_ detail line” work as above to change the way that headings and data in the detail area are displayed.
ae
n
id
5
# 12:
text
Date format is specified under the “_ detail line” style under “Op”.
ae
n
id
6
# 13:
text
Styles “_ total line” and “_ negative total line”, under Pre Op Total, control how totals in the detail area are displayed.
ae
n
id
7
Generation Override
Accounts part 2
Title
Accounts part 2
quickwins.bills1
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
bills1
# 2:
swf build
1
# 3:
quick intro
Part of the Price List and Bill by Category Quick Win scenario
# 4:
successor
presentation.quickwins.bills2
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
16m
# 7:
text
Since this scenario contains two sheets, the Sheet List tab can be used to generate both at the same time.
ae
n
id
1
# 8:
text
This sheet takes all of its information from the Workbook.
ae
n
id
2
# 9:
text
Fields “category” and “item” hold definitions for your categories and items. Note that all items are defined regardless of what category they appear in – the marrying up of item and category, even the same item appearing in different categories, happens in the Table “unit price” (items appearing in different categories are treated as different items – it’s up to you to price them the same and describe them the same if they are indeed the same).
ae
n
id
3
# 10:
text
Details for a particular item in a particular category to appear in the price list are given in the value area for the Table “details”. Not every item need have details provided – this is guarded by the last line in the table which provides text to be displayed by default.
ae
n
id
4
# 11:
text
The “purchase” Table value carries additional information about the purchase. The other fields which must be filled in are “category”, “item” and “quantity”. The “price” field can be hidden away (as indeed it is in the tutorial).
ae
n
id
5
Generation Override
Price List and Bill by Category part 1
Title
Price List and Bill by Category part 1
quickwins.bills2
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
bills2
# 2:
swf build
1
# 3:
quick intro
Part of the Price List and Bill by Category Quick Win scenario
# 4:
predecessor
presentation.quickwins.bills1
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
30m30s
# 7:
text
Generation Overrides under each particular sheet is used to specify a heading. Generation Overrides for a “price list” also sets an actual indentation (6 spaces) and a 6 space pad between the columns in the output.
ae
n
id
1
# 8:
text
The “price list” sheet also defines its greeting and farewell message as Table additions.
ae
n
id
2
# 9:
text
Style “_ currency” under Default sets the currency specifier for both sheets.
ae
n
id
3
# 10:
text
Style “_ price list headings” under Pre Op Total and Op specifies the headings used in the price list.
ae
n
id
4
# 11:
text
Style “_ price list item” under the same two tabs specifies the display of the price list items.
ae
n
id
5
# 12:
text
Style “_ top line price list” controls the top line in the price list, style “_ top line purchase” does the same for the purchase.
ae
n
id
6
# 13:
text
The “tax rate” Table defines the percentage amount of tax that should be charged. The style “_ tax rate rounding” defines, in the Standard tab, how rounding of the tax calculation should take place.
ae
n
id
7
# 14:
text
The whole of the bill area has a base style called “_ base for total purchases” – a new set of defaults which moves everything to a large text size, bold with a background of Light Green. Change this within the default area to modify.
ae
n
id
8
# 15:
text
Style “_ column colours” controls the colours of the individual columns in the purchase detailed area.
ae
n
id
9
# 16:
text
Styles “_ purchase category headings”, “_ purchase category total”, “_ purchase category item”, “_ purchase item headings” and “_ purchase item” control various different lines in the output of a purchase. Purchases are displayed by category first, with the heading followed by a number of items followed by a total line, and then by item, with heading followed by number of items.
ae
n
id
10
Generation Override
Price List and Bill by Category part 2
Title
Price List and Bill by Category part 2
quickwins.leaflet1
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
leaflet1
# 2:
swf build
1
# 3:
quick intro
Part of the Leaflet Quick Win scenario
# 4:
successor
presentation.quickwins.leaflet2
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
16m50s
# 7:
text
Change Workbook / Tables (“clauses”) to set paragraphs to display on your output. The value of the table gives the text. Columns A, B and C give pre-requisite values for A, B and C as defined in your individual Sheet. The “id” column gives a unique id for your paragraph. The “pre id” column gives the id of the paragraph that this should appear under, with “top” for top level paragraphs.
ae
n
id
1
# 8:
text
The A, B and C fields are defined under Sheet / + Field Values. The sheet called “client abc” sets these as “a”, “b” and “c” respectively in this example. Use the menu entry Sheet / Clone (when in the Sheet tab) to create new sheets and change the values in those fields as you wish.
ae
n
id
2
# 9:
text
It is also possible to create paragraphs which appear using more complex conditions than a simple match of A, B and C. This requires getting into a little bit more complexity with regards to using QuSheet – in particular, moving away from the straight data driven side and programming some of QuSheet’s headings. One special paragraph has been set up as a template.
ae
n
id
3
# 10:
text
To start changing the special paragraph and its conditions, start with a project which has only one sheet. You may well need to change the Sheet Entries, and you want to do this before you clone.
ae
n
id
4
# 11:
text
The heading “special clause condition” governs whether “special clause” is displayed. Within this, “special sub-clause condition” governs whether “special sub-clause” is displayed. You can use these as templates for your own special clauses and conditions, but remember to set the Selector at your top-level to “ABC selector”.
ae
n
id
5
Generation Override
Leaflet part 1
Title
Leaflet part 1
quickwins.leaflet2
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
leaflet2
# 2:
swf build
1
# 3:
quick intro
Part of the Leaflet Quick Win scenario
# 4:
predecessor
presentation.quickwins.leaflet1
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
11m50s
# 7:
text
In this particular scenario, it makes sense to change the Title of the sheet within Sheet / Generation Overrides, but it’s up to you. Note that Workbook / Generation is using the force indentation parameters to set a minimum indentation of 4 spaces by default, since with this scenario there are numerous places where QuSheet’s calculated indentation would result in no indentation at all, and it’s more visually attractive to have some level of indentation take place.
ae
n
id
1
# 8:
text
In this scenario, also, the greeting message is varied by sheet, though the farewell message is left uniform. For a more sophisticated way of setting a greeting message take a look at the Key Item Example chapter in the Working With QuSheet tutorial.
ae
n
id
2
# 9:
text
Styling here takes place entirely within the “Default” sub-tab, and only within “_ clause” apart from the farewell and greeting text.
ae
n
id
3
# 10:
text
With special clauses, you can specify individual new styles based on the “_ clause” style to make these look different.
ae
n
id
4
Generation Override
Leaflet part 2
Title
Leaflet part 2
quickwins.plan1
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
plan1
# 2:
swf build
1
# 3:
quick intro
Part of the Plan Quick Win scenario
# 4:
successor
presentation.quickwins.plan2
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
14m
# 7:
text
Structured as a multiple-sheet project in order to allow you to re-use your holiday information - non-working days are placed under Workbook / Field (“holiday”).
ae
n
id
1
# 8:
text
A Sheet represents a plan, with + Table Values containing the necessary activity data.
ae
n
id
2
# 9:
text
Set the start date using “start” table and field “date”.
ae
n
id
3
# 10:
text
Set activities using the “activity” table with fields “category”, “duration” and “work item”. The value of the table adds details.
ae
n
id
4
# 11:
text
QuSheet scans your + Table Value rows from top to bottom, first looking for categories (phases), then looking for activities within those categories. This order is important as it is the order which QuSheet uses to determine what happens after what.
ae
n
id
5
# 12:
text
Setting the phase name under Workbook / Fields (“category”), though not necessary, is a convenient way of naming your categories to ensure that the Category column in the Activity table is correctly filled in.
ae
n
id
6
Generation Override
Plan part 1
Title
Plan part 1
quickwins.plan2
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
plan2
# 2:
swf build
2
# 3:
quick intro
Part of the Plan Quick Win scenario
# 4:
predecessor
presentation.quickwins.plan1
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
15m40s
# 7:
text
Since we are multiple-sheet, we put the heading for the sheet in the Sheet / Generation Overrides area, and the greeting in Sheet / + Table Values, so that these can vary by sheet.
ae
n
id
1
# 8:
text
Style “_ top line” (Default) controls the first line the viewer sees when he opens the sheet.
ae
n
id
2
# 9:
text
Style “_ activity by category” is based on style “_ activity”. Change the latter to affect the way that activities are displayed in all areas (this includes the date format), the former to override this just for the category summaries.
ae
n
id
3
# 10:
text
Style “_ headings” under “Pre Op Total” and “Post Op Total” controls the text used in the headings.
ae
a
id
4
Generation Override
Plan part 2
Title
Plan part 2
quickwins.schedule1
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
schedule1
# 2:
swf build
1
# 3:
quick intro
Part of the Schedule Quick Win scenario
# 4:
successor
presentation.quickwins.schedule2
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
19m20s
# 7:
text
Arranged as a single-sheet project, everything that needs to be changed is within the Workbook.
ae
n
id
1
# 8:
text
Three Fields, “event”, “venue” and “speaker”, define the various different events, venues and speakers as a convenience measure rather than an essential, in order to help ensure the correct tying up between entries in the various tables.
ae
n
id
2
# 9:
text
The “scheduled event” Table details all of the events that will take place in the conference, giving event name in the Table value followed by a date, an event id, the speaker, the starting time and the venue.
ae
n
id
3
# 10:
text
The “event details” table provides details for an event for a given event id.
ae
n
id
4
# 11:
text
The “speaker details” table provides details for the speaker.
ae
n
id
5
# 12:
text
Lunch time is set in the “lunch” Table under the “time” Field.
ae
n
id
6
Generation Override
Schedule part 1
Title
Schedule part 1
quickwins.schedule2
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
schedule2
# 2:
swf build
2
# 3:
quick intro
Part of the Schedule Quick Win scenario
# 4:
predecessor
presentation.quickwins.schedule1
# 5:
index page
../../tutorial.index.quickwins
# 6:
duration
23m40s
# 7:
text
As well as the standard changes that can be made in the Workbook / Generation parameters, there is also a minimum indentation of 4 spaces set which ensures that some indentation takes place when moving between headings which don’t present any data (like the venue names and date headings).
ae
n
id
1
# 8:
text
Table “venue text” controls the text used in the venue headings.
ae
n
id
2
# 9:
text
Style “_ date in summary” is used to display the date headings. Change the default display of the main field to change the format in which the date is displayed.
ae
n
id
3
# 10:
text
Styles “_ event details” and “_ speaker details” control the display of the detail areas within the individual events. There is also a base style in operation here called “_ inline details base” – a style which acts as a default for this area.
ae
n
id
4
# 11:
text
Style “_ headings in schedule by date”, sets the heading text in the schedule by date. Style “_ headings in schedule by venue” builds on the previous style by basically switching off the heading on the first column. The three columns correspond to the “Pre Op Total”, “Op” and “Post Op Total” style tabs.
ae
n
id
5
# 12:
text
Style “_ schedule by date line” and “_ schedule by venue line” work the same way. The display of the time column is again delegated to another style, in this case “_ time” under “Op”.
ae
n
id
6
# 13:
text
Style “_ lunch” controls the display of the lunch line, though note the display of the time is delegated to “_ time” as well.
ae
n
id
7
# 14:
text
Styles “_ speaker name in summary” and “_ speaker detail in summary” are used to display information under the Speaker Summary area.
ae
n
id
8
# 15:
text
Style “_ venue name in summary” controls how the venue name is displayed under Schedule by Venue.
ae
n
id
9
# 16:
text
The three top line styles control the styling of the three top lines.
ae
n
id
10
Generation Override
Schedule part 2
Title
Schedule part 2
trucks example
Entries
# 1:
---
# 2:
(base=
z base
)
(style=
)
(expl=
navigation bar
)
# 3:
---
# 4:
(base=
z base
)
(style=
)
(expl=
sample scenario.1
)
# 5:
(base=
z base
)
(style=
)
(expl=
sample scenario.2
)
# 6:
(base=
z base
)
(style=
)
(expl=
sample scenario.3
)
# 7:
---
# 8:
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 9:
swf name
(base=
z base
)
(style=
)
(expl=
swf
)
# 10:
---
# 11:
(base=
z base
)
(style=
)
For other presentations:
# 12:
(base=
z base
)
(style=
)
(expl=
index page overview presentation
)
# 13:
(base=
z base
)
(style=
)
(expl=
index page in action presentation
)
# 14:
---
# 15:
Transcript
(base=
z base
)
(style=
)
+ Field Values
+ Table Values
# 1:
swf name
trucks
# 2:
swf build
4
# 3:
quick intro
QuSheet Overview
# 4:
duration
4m 30s
# 5:
text
Let me assume that I run a haulage company consisting of three trucks: Huey, Dewey and Louis and a customer base for which I provide the following services:
id
Background
# 6:
text
I will make a delivery to a fixed location for a fixed price
id
Background
# 7:
text
Or I will make a delivery to an alternate location for a price based on mileage.
id
Background
# 8:
text
Or I will allow my trucks to be hired out at a daily rate.
id
Background
# 9:
text
All of my pricing information is held on Excel spreadsheets - here three tables showing prices by day, by destination and by mileage.
id
Input
# 10:
text
And I also maintain a table showing my activities for the week (here you see that for a given customer, and truck, and date, I either fill in the number of days for a daily hire, or the mileage out and mileage in when a truck was delivering on that basis, or the destination name when I was delivering to one of my well known and well priced destinations).
id
Input
# 11:
text
Additionally, I use the first column of the table to hold any extra notes that I wish to report for a given activity.
id
Input
# 12:
text
Now I have set up QuSheet to use these particular tables directly, as you can see here. And I can transfer information between Excel and QuSheet with a simple Copy and Paste function, or I can use an XML link to transfer all of my tables, cleanly, through an export and import function.
id
QuSheet
# 13:
text
Every week, after I have imported my weekly schedule, plus any changes I have made to my prices, I can use the Generate button on QuSheet to create an HTML report.
id
QuSheet
# 14:
text
On the top line there's a statement showing the dates for which the report applies and a calculated revenue figure.
id
Output
# 15:
text
Below that, under three headings, are breakdowns of that revenue, showing individual activities colour-coded according to whether they were for a fixed rate, a mileage or a daily hire.
id
Output
# 16:
text
By clicking on these lines I can expand to show how the individual calculations were made, and also display any extra notes that I have recorded for a given activity.
id
Output
# 17:
text
Where the information is displayed by customer or by truck, QuSheet automatically presents the tables of data showing the highest revenue earner first.
id
Output
# 18:
text
This example can be found on the QuSheet web site and, as with all examples, you are also able to download the source project file so that you can use it in QuSheet yourself and see what you can do.
id
Finally
Generation Override
QuSheet In Use
Title
QuSheet In Use
using.display table cells
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
display table cells
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.display table rows
# 5:
successor
presentation.using.forms
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
3m50s
# 8:
text
Cells occur at any given row and column. The column determines what goes into a cell – with explanation presented in the Help pane.
ae
n
id
1
# 9:
text
When a cell contains a key item, selecting the cell presents a drop-down list allowing you to select the relevant key-item to use. Right-clicking or pressing F12 allows you to create a new key-item in-situ.
ae
n
id
2
# 10:
text
When a cell contains text, your first option is to simply type in what you want. A right-click or F12 brings up a pop-up list with extra options (clear the field, input a date, input a time, input with a dedicated text-box and, in some cases, input from a pre-defined list).
ae
n
id
3
# 11:
text
Colour coding for display table cells / rows varies according to the display table being shown. This is explained in the help pane, though colours may be changed from the Preferences / Colours tab.
ae
n
id
4
Generation Override
Display Table Cells
Title
Display Table Cells
using.display table columns
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
display table columns
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.key items
# 5:
successor
presentation.using.display table rows
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
5m50s
# 8:
text
QuSheet uses Forms and Display Tables (not to be confused with QuSheet’s Key Item “Table”) to present data to you for viewing and editing.
ae
n
id
1
# 9:
text
The View menu item appears whenever a Display Table is being shown – a menu whose entries allow you to control the columns being displayed.
ae
n
id
2
# 10:
text
You can also hide columns by right-clicking on the heading of the column and choosing “hide”.
ae
n
id
3
# 11:
text
Columns can be moved and resized, producing a ragged-table as you work, which is fixed when you navigate away or resize.
ae
n
id
4
# 12:
text
One column, the special column, which cannot be hidden, and whose name is displayed surrounded by two dots, is expanded or contracted as necessary to allow your table to fit snug with the window borders. This behaviour can be changed from the Preferences / General tab if you wish.
ae
n
id
5
# 13:
text
You can also cause a column to expand or contract to accommodate a ragged table by right-clicking on the column header and selecting “fit width”.
ae
n
id
6
# 14:
text
The View menu contains “all” and “default” entries to allow you to restore visibility to all of your columns and to additionally restore their default widths.
ae
n
id
7
# 15:
text
The "default" for a workbook table now displays columns for fields which have a value defined, either within the workbook table or as a sheet addition. View default for a table is also invoked when you first load a project into QuSheet.
ae
a
id
8
# 16:
text
Column sizes, presence and location are stored for you by QuSheet and restored when you restart the program. The number of columns available for a display table for key item Tables depends on the project, which means that if you change these columns you may get unexpected results if you then change to another project (since these setting do not depend on the project, they depend on the user). If you think this may have happened, remember the View / All and View / Default menus.
ae
n
id
9
Generation Override
Display Table Columns
Title
Display Table Columns
using.display table rows
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
display table rows
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.display table columns
# 5:
successor
presentation.using.display table cells
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
4m30s
# 8:
text
Display Tables have numbered (and ordered) rows. This order is significant.
ae
n
id
1
# 9:
text
Rows can be moved by clicking or pressing enter on the arrow buttons.
ae
n
id
2
# 10:
text
Rows are deleted by clicking on the X.
ae
n
id
3
# 11:
text
Using Shift-click or Shift-enter on the arrow keys inserts a new blank row either above or below the row clicked on.
ae
n
id
4
# 12:
text
Using Control-click or Control-enter on the arrow keys inserts a clone of the row clicked on either above or below it.
ae
n
id
5
# 13:
text
Strangely, shift-enter on an arrow key on the last row (the insertion row) in a table behaves as if you had done so on the last actual line rather than the insertion one. This is a Windows “funny”.
ae
n
id
6
# 14:
text
Working directly on the insertion row starts a new row, at the bottom of the table, using the data you are putting in as you do it.
ae
n
id
7
# 15:
text
The arrow buttons and # button can no longer be hidden away.
ae
a
id
8
Generation Override
Display Table Rows
Title
Display Table Rows
using.forms
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
forms
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.display table cells
# 5:
successor
presentation.using.undoredo
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
2m30s
# 8:
text
Forms are collections of input fields arranged in panes, around which you can navigate with the mouse, tab keys, enter key or arrow keys.
ae
n
id
1
# 9:
text
Input fields are either text fields (sometimes purely numeric) or drop-down lists.
ae
n
id
2
# 10:
text
Non-numeric text fields are displayed with double-quotes at the beginning and end to show you where you may have spaces.
ae
n
id
3
# 11:
text
Input fields are colour coded. The grey background in particular is important with styles, as it shows you whether a particular field has been specified or not.
ae
n
id
4
Generation Override
Forms
Title
Forms
using.generation
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
generation
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.undoredo
# 5:
successor
presentation.using.preferences
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
5m40s
# 8:
text
Use the Generate button or menu item under the Sheet menu and Sheet tab to generate an output file.
ae
n
id
1
# 9:
text
Generation progress is shown using a dialog box that displays 1 or 2 progress bars.
ae
n
id
2
# 10:
text
The tool-strip button bar contains a label telling you when you last generated a sheet. It also tells you whether the last generation was successful.
ae
n
id
3
# 11:
text
QuSheet generates a backup file of your source before generating and removes it if generation was successful, just in case something untoward happens with the generation process.
ae
a
id
4
# 12:
text
The View button invokes your preferred browser (see Preferences / Resources) on the generated output file.
ae
n
id
5
# 13:
text
Use the Sheet List tab to manage multiple sheets. This presents a table with rows for every sheet, showing you the name of the sheet, when it was last generated, and whether it was generated ok (with colour coding). Clicking on the column names re-sorts this table in different ways (this is not an ordered table like the display tables in QuSheet).
ae
n
id
6
# 14:
text
Buttons on the rows allow you to generate or view individual sheets. A check box on the left allows you to mark particular sheets in order to multiply-generate a number at the same time (from the Sheet List menu). Row selection can also be used to mark or unmark multiple sheets using the Sheet List menu as well.
ae
n
id
7
Generation Override
Generation
Title
Generation
using.help
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
help
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.overview
# 5:
successor
presentation.using.navigation
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
5m40s
# 8:
text
"Note that the QuSheet logo now appears when a tab page is empty, and that some of the entries and layout of various tab-pages have changed since this presentation was made (but not in ways that affect this presentation's contents). "
ae
a
id
1
# 9:
text
The text in the help pane changes as you look at the different tab-pages and the different fields within them.
ae
n
id
2
# 10:
text
The help pane is separated from the tab-pages by a separator which you can drag up and down.
ae
n
id
3
# 11:
text
Help pane text is scrollable in the normal ways. The F10 and F11 keys also scroll the text in this pane up and down for non-mouse users, though this is a little clunky.
ae
n
id
4
# 12:
text
The help menu contains three entries to move the splitter around, plus entries to navigate to QuSheet’s home page, enter a new licence key and check for software updates.
ae
n
id
5
# 13:
text
The help menu also now contains an entry to allow you to view a read-only copy of the XML Schema Definition file for a QuSheet project (for System Integrators).
ae
a
id
6
# 14:
text
Help appears in 4 layers, one following the other.
ae
n
id
7
# 15:
text
The top help layer is the Error layer. When the input field and help pane goes red, this consists of an error message explaining what has gone wrong.
ae
n
id
8
# 16:
text
The second help layer provides explanation for a field in a form, or a table column in a table, depending on what is currently selected.
ae
n
id
9
# 17:
text
The third layer of help provides information on the current Tab page.
ae
n
id
10
# 18:
text
The fourth layer of help provides general information relevant to what you are doing now but common to many areas within QuSheet (such as information on entering data).
ae
n
id
11
Generation Override
Help
Title
Help
using.key items
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
key items
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.projects
# 5:
successor
presentation.using.display table columns
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
4m30s
# 8:
text
Key Items are Headings, Tables, Fields, Selectors, Styles and Sheets.
ae
n
id
1
# 9:
text
Key Items are the named entities in QuSheet which you use to specify what you want QuSheet to calculate and generate.
ae
n
id
2
# 10:
text
When you are looking at a key item a menu item (the key item menu) appears on the menu bar named the same as the item type (e.g. Heading), plus a drop down list appears on the tool-strip bar to allow you to select which key item you wish to look at. Items appear in this drop-down list in italics if they are not currently in use (i.e. orphaned).
ae
n
id
3
# 11:
text
The Key Item Menu (e.g. Heading) allows you to create a new key item, clone one, rename one or delete one. This menu also contains a Go To option duplicating the effects of the drop-down list on the tool-strip bar.
ae
n
id
4
# 12:
text
Where key items refer to one another in display tables, a pop-up box comes up when you press F12 or right-click which allows you to create a new key item of the relevant type “in situ” – i.e. without navigating away.
ae
n
id
5
# 13:
text
Deleting orphaned key items is safe. Deleting non-orphaned key items causes QuSheet to substitute the references to the dead key item with a suitable default.
ae
n
id
6
# 14:
text
Note that the “z” styles, even though they may be orphaned, cannot be deleted, though they can be modified.
ae
a
id
7
Generation Override
Key Items
Title
Key Items
using.navigation
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
navigation
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.help
# 5:
successor
presentation.using.projects
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
6m40s
# 8:
text
QuSheet’s pages of information, presented in the Tab page area, depend on the tabs you have navigated to and the selection you have made on the drop-down list in the Tool-Strip-bar (of what is known as your key item).
ae
n
id
1
# 9:
text
QuSheet keeps a history of pages visited to allow you to navigate backwards and forwards using the navigation buttons on the top-left. The status bar at the bottom tells you where these buttons will take you when you hover the mouse over them.
ae
n
id
2
# 10:
text
Navigating to a new location clears out your forward navigation history.
ae
n
id
3
# 11:
text
QuSheet maintains a history of what tab you are looking at within each tab, so that if you change tab at a top level and then come back you go to the right sub-tab.
ae
n
id
4
# 12:
text
Navigation can also take place as a result of an undo or redo, since QuSheet always navigates you to the right page for the command being undone or redone.
ae
n
id
5
# 13:
text
Navigation also takes place via a shortcut menu which pops up when you right-click or press F12 on a field in a table which refers to a key item.
ae
n
id
6
# 14:
text
Navigation history is cleared if you delete a key item at any point, including undoing the creation of a key item.
ae
n
id
7
Generation Override
Navigation
Title
Navigation
using.overview
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
overview
# 2:
swf build
2
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
successor
presentation.using.help
# 5:
index page
../tutorial.index.using qusheet
# 6:
duration
4m
# 7:
text
QuSheet is a single-window program with the normal window controls (minimise, maximise, close, re-size) plus occasional dialog boxes for quick questions / information.
ae
n
id
1
# 8:
text
The Menu bar has a File Menu, Edit Menu (undo and redo), Help Menu, plus some other context sensitive menus which appear and disappear as you navigate around the program.
ae
n
id
2
# 9:
text
The Tool-Strip bar has buttons which provide short-hands to common functions such as undo and redo.
ae
n
id
3
# 10:
text
The Status bar at the bottom explains what the tool-strip buttons will do when you hover your mouse over them.
ae
n
id
4
# 11:
text
The Tab-Page area is where the main business of the program takes place, with tabs, tabs within tabs, and even tabs within tabs within tabs.
ae
n
id
5
# 12:
text
The Help pane is a resizable pane of information with context-sensitive help (i.e. help text which changes according to what you are looking at or doing).
ae
n
id
6
Generation Override
Overview
Title
Overview
using.preferences
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
preferences
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.generation
# 5:
index page
../tutorial.index.using qusheet
# 6:
duration
4m30s
# 7:
text
User Preferences are viewed and set from the Preferences tab, a tab with three sub-tabs.
ae
n
id
1
# 8:
text
User Preferences are stored under your user name within windows and restored when you re-start QuSheet (the same as your display column settings).
ae
n
id
2
# 9:
text
User Preference changes cannot be undone via QuSheet's Undo/Redo mechanism.
ae
n
id
3
# 10:
text
The General sub-tab has delete confirmation options and a couple of options relating to the way display tables are, well, displayed.
ae
n
id
4
# 11:
text
The Colours sub-tab has colour setting options for the QuSheet front-end. These settings do not affect the output that QuSheet produces. Clicking on a colour pops up a colour-picker dialog box from which you can click on the colour that you want.
ae
n
id
5
# 12:
text
The Resources sub-tab is used to set your preferred browser for File / View Print Source and the View button / menu items. This sub-tab also contains settings for the background processor which you will only need to change if you are advised to do so during Generation.
ae
n
id
6
# 13:
text
The View Indeces preferences has been removed, since this has lost relevance now that table column visibility is set according to the values of the fields within the table.
ae
e
id
7
# 14:
text
The Resources sub-tab now has a setting for the number of commands held within the Undo stack.
ae
a
id
8
Generation Override
Preferences
Title
Preferences
using.projects
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
(base=
z base
)
(style=
)
# 6:
---
# 7:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 8:
(base=
z base
)
(style=
)
# 9:
---
# 10:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 11:
(base=
z base
)
(style=
)
# 12:
---
# 13:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 14:
(base=
z base
)
(style=
)
# 15:
---
+ Field Values
+ Table Values
# 1:
swf name
projects
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.navigation
# 5:
successor
presentation.using.key items
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
2m20s
# 8:
text
Since QuSheet can generate many output files from one input file, QuSheet’s input file is called a Project, to stop over-use of the word “File”.
ae
n
id
1
# 9:
text
The “File” menu, however, is maintained, since this is a convention with windows programs, though note that the file in this case refers to a QuSheet project file.
ae
n
id
2
# 10:
text
File also contains a View/Print Source item which invokes your favourite browser (specified under the Preferences / Resources tab – Internet Explorer by default) on QuSheet’s project file. From here you can use the browser’s Print function to print the source project file out.
ae
n
id
3
# 11:
text
Three tool-strip bar buttons also refer to projects – new, open and save/save as, the latter changing function from save as to save when the project has been saved at least once.
ae
n
id
4
Generation Override
Projects
Title
Projects
using.undoredo
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
undoredo
# 2:
swf build
1
# 3:
quick intro
Part of the "Using QuSheet" tutorial
# 4:
predecessor
presentation.using.forms
# 5:
successor
presentation.using.generation
# 6:
index page
../tutorial.index.using qusheet
# 7:
duration
9m10s
# 8:
text
QuSheet’s undo/redo system is accessed with the Edit menu or the undo/redo tool strip buttons. Control Z and Control Y are not supported.
ae
n
id
1
# 9:
text
QuSheet tells you what it will undo or redo using the menu or, for the tool strip buttons, the status bar.
ae
n
id
2
# 10:
text
“Doing” rather than “Redoing” clears out the “redo” forward history in much the same way as that new forward navigation cleared out the old forward navigation history.
ae
n
id
3
# 11:
text
Not everything is undoable – only those actions which affect QuSheet’s final output are. Changes to display preferences such as column sizes are not.
ae
n
id
4
# 12:
text
QuSheet file generation is also not undoable. It is up to you to backup your files.
ae
n
id
5
# 13:
text
Hitting undo or redo not only un-does the last command (or re-does the last undone command), it also cancels whatever you were doing at the time. Beware.
ae
n
id
6
# 14:
text
Input fields and cells are colour coded using the “entry” colour to indicate to you that you are mid-edit so that you do not lose your edits inadvertently when you undo or redo.
ae
n
id
7
# 15:
text
An edit is accepted by QuSheet when you press enter or navigate away, assuming that the edit was not in error (in which case it is cancelled).
ae
n
id
8
# 16:
text
The Escape key cancels an edit.
ae
n
id
9
# 17:
text
When inputting a new row in a display table using the insertion row, the whole row is colour coded using the “entry” colour to show you that the *whole row* is mid-edit. Be careful about using Undo or Redo in these situations – you wont just cancel the last change you made to the insertion row, you’ll cancel the whole of the row insertion process.
ae
n
id
10
# 18:
text
Right-clicking on the insertion row inserts (and accepts into QuSheet) a new row before popping up a dialog box to allow you to create a new key item in-situ.
ae
n
id
11
# 19:
text
All of this is explained in the 4th level of Help (see Help) under Editting.
ae
n
id
12
# 20:
text
The number of commands kept in the undo stack is configurable to between 0 and 50 under Preferences > Resources.
ae
a
id
13
Generation Override
Undo / Redo
Title
Undo / Redo
working.file overview
Entries
# 1:
(base=
z base
)
(style=
)
(expl=
Quick Intro Headline
)
# 2:
(base=
z base
)
(style=
)
# 3:
---
# 4:
Summary
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 5:
---
# 6:
View
(base=
z base
)
(style=
)
(expl=
View Heading
)
# 7:
---
# 8:
Addenda / Errata
(base=
z base
)
(selector=
dummy field
)
(style=
)
(expl=
Addenda / Errata Heading
)
# 9:
---
# 10:
navigation options
(base=
z base
)
(selector=
dummy field
)
(style=
)
# 11:
---
+ Field Values
+ Table Values
# 1:
swf name
file overview
# 2:
swf build
1
# 3:
quick intro
Part of the "Working With QuSheet" tutorial
# 4:
successor
presentation.working.key item overview
# 5:
index page
../tutorial.index.working with qusheet
# 6:
duration
3m40s
# 7:
text
QuSheet creates a folder within MyDocuments called QuSheet for your use.
ae
n
id
1
# 8:
text
Project files are of the format project.qus.xml - a QuSheet specific XML whose details are only of interest to system integrators and the like, and whose format is described by a file called QuSheetFileFormat.xsd (schema definition).
ae
n
id
2
# 9:
text
The XSD format file can be viewed from the help menu in QuSheet, not from the start menu.
ae
e
id
3
# 10:
text
QuSheet’s output is stored in the same place as the project file and called project.sheet.html (where sheet is the name of the sheet within the project being generated). A second file, project.sheet.err.html, is also produced if there is an error in the generation process, but this is just for QuSheet’s own internal use.
ae
n
id
4
# 11:
text
QuSheet’s output is viewable with a browser.
ae
n
id
5
# 12:
text
QuSheet’s project file is also viewed with a browser. If you double-click on a project file you will invoke a browser, rather than QuSheet, to view it.
ae
n
id
6
# 13:
text
QuSheet’s project file is viewed in a nice formatted fashion because of the QuSheetFileStyler.css file which the browser loads either from www.qusheet.com or from the same d