> My thought process begun like this: "How can I create my report?" I did
> not wanted to use any complicated accounting application, only few simple
> linked tables. Well, instead of creating a table right on my desk-top
[1] I had
> to think first, what application I have to use. I had more options, then I
> decided to use MS Excel, as I was on Windows at the moment, and I have
just talked
> to a fried who wanted similar report, but she does not use OO.org.

I imagine on Etoile it would work something like this:

 - While in a workspace/project/desktop, hit the Create New Document button
 - This creates a blank white rectangle on your screen (user-defined size:
perhaps A4 or Letter or 800x600px)
 - User hits Insert > Table button (options of things to insert might be
from the AppKit service component list here:
http://www.dromasoftware.com/etoile/mediawiki/index.php?title=Service_Components
)
 - (Optional) Resize the document or resize the table
 - Start editing the table

With this process you eliminate the steps of having to pick an
application, and having to name or save your document. The document just
_is_, just as if you had grabbed a pice of paper from your desk and
started writing on it.

> After opening the spreadsheet application [2] I used the first sheet and
> labeled it "Accounts", then created [3] next sheet as "Periodical
transactions",
> and the last one was "Balance". I have referenced cells across the
sheets [4]
> - that is, I have used sums from accounts and transaction sheets on the
> balance sheet. It is quite simple to reference sheets in Excel.
>
> Then I realised that I do not like navigation through thin tabs at the
> bottom of the window. I wanted kind of book with pages.

At this point, if I were in Etoile, I would have created 2 new documents,
inserted tables into them and started editing them. If I wanted to share
content between the documents, I would have clicked on the source field(s)
in one table, clicked the Insert > Pipe button and drawn a link to the
target field(s).

> Fortunately, the application
> I was using (OO does that too) has ability to create inter-document links.
> In both mentioned apps you reference sheets by name, therefore when you
rename the
> sheet the link is broken.

Bad, bad interface! Go to your room!

> [5] In XLS, creating the link was 2 clicks away
> - "link" toolbar button, "sheet name" in a dialog. In OO it was more
> complicated:
> "link button", "inter-document link", "expand list of sheets", "select the
> sheet it second dialog". [6] So far I have created a cover page with 3
> links to other sheets. To move back I have put a link on each sheet to
the contents
> page.
>
> Now I have a nice book with simple navigation through links. But ... I can
> not put anything else in this book, only pages that contain tables. I
can not
> have native text page or native diagram page. Yes, I can insert text frame
> there or embed graphics, but all the pages will be spreadsheet pages.
Even the
> contents is a spreadsheet table... [7]

Not a problem with Etoile -- a document is just a container for the
components you choose to add to it. Because each component is edited by
way of Services (rather than as individual documents in an application), a
document doesn't assume a default appearance or configuration.

> [1] - I would like to say to my computer: "Create a sheet with a table
> here", then by doubleclicking on that sheet appropriate tool is opened.
Creating
> a sheet can be as simple as draggin "sheet" prototype from kind of palette
> to my project container/desktop.

Yep -- exactly what I described.

> [2] How I should know what application to use for creating a spreadsheet?
> there is no "Spreadsheet" application, only something called "Excel",
> "OpenOffice Calc" or "Gnumeric".

Point being you shouldn't have to think in terms of applications. You
should be able to think in terms of tasks and documents, and have the
computer respond appropriately.

> [3] see [1]
> [4] missing feature in desktop environment is putting contents from one
> sheet/document/page into another one. In this case I have used contents of
> one cell in another sheet. I would like to use contents of my 'Balance'
sheet
> in a text document too or someone would like to put in the statusbar.
But how
> to reference the contents? And how to get the contents?

Pipes. Pipes are our friend.

> [5] Environment should reference object by their ID, not its name. This
> does not mean that every object should have unique identifier, it should be
> sufficient for referenced object to have identifier created.

Objects (Documents and Components) should never rely on user-editable
names to keep track of a file's location or identity. File names are for
users, not computers. That's been the subject of my whole rant about
inodes and aliases.

> [6] Linking should be top-level feature, preferably by drag-and-drop or
> gorm-like connection on the environment/desktop level across documents. Or
> at least there should be a palette/inspector with list of available
targets:
> one creates a selection in a document, selects target in the panel and
clicks
> 'Connect'/'Create link'

Click source. Click Insert > Pipe. Click target. Line should be
automatically drawn between the two. A drag and drop method might also be
nice, like how InterfaceBuilder or Dreamweaver handle link building.

> [7] This is part for the project-oriented environment: no spreadsheet
> workbook with more sheets but a project with spreadsheet pages, text
pages, diagram
> pages, photos ... One can glue that into one document if he/she likes.
> How?
> Another longer topic :-)

As long as what we want is clearly specified, developing according to the
spec document should just be an issue of manpower and time. Of course, I'm
a designer, so I have no idea what I'm talking about :)


J.





Reply via email to