[Dev] Update CPIA documentation for 0.4

[Ted Leung]

Hi John,

I this is a good "state of the union" type document, and it did help me 
to understand a little more of what is  going on in CPIA.  Some 
thoughts:

* It would help if you used fonts/styles to set off names of classes, 
methods, etc.   Also links to relevant parts of the API docs would also 
help (not for every class, but for the important ones)

* In a few paragraphs it would make it easier to follow if you took the 
paragraph and turned it into an outline/list.   Examples of those 
paragraphs are:
    1) the paragraph that starts "Another way to get a more in-depth 
understanding of CPIA"
    2) the paragraph that starts "The dispatchEvent method of View"

* Another helpful thing (not sure if it belongs in this document or a 
CPIA Overview type of document) would be a few diagrams:
    1) various pieces of CPIA
    2) a picture of the app showing the various blocks that make up the 
application window

* In the paragraph on event dispatch ("The dispatchEvent method of 
View..."), I couldn't tell how the various dispatching options got 
selected.  Is this done automatically by CPIA or do I the developer 
need to do something?  If I need to do something, what do I do?

* "CPIA events use notifications are subject to the limitations of 
notifications" -- I think you meant to drop "use notifications"

* For the blocks "whose design we're less than happy with", are you 
planning to do all of those changes for 0.5, or will some of them end 
up happening in 0.6?

* Does there need to be a discussion of drag and drop handling or 
clipboard handling?  Again, I'm just asking

* Are blocks/views going to be the part of the system that takes care 
of I18N?

* What happens when I build something like an e-mail compose view that 
has a bunch of text fields, etc.  Is there any automatic binding of the 
text field contents to attributes s on some Item?  I think that an 
expanded section on how blocks handle data would be very helpful

* Is there anything special that needs to be done when the UI is 
communicating with a background thread, like the situation in e-mail?

* In the section on ItemCollections:  right now we can only associate a 
query with an ItemCollection.  Does it make sense to associate a query 
with a block?

* In the penultimate paragraph on addressing, do we really want to end 
up with 2 separate addressing methods?  It seems like we ought to be 
able to use a new addressing scheme to  handle the core and schema.  
The repository itself might still use the paths, but then no chandler 
client would see them.  I'm concerned about having too many mechanisms.

Ted

On Oct 19, 2004, at 5:43 PM, John Anderson wrote:

> I just updated the CPIA documentation for 0.4 and would appreciate any 
> constructive feedback
>
> http://wiki.osafoundation.org/bin/view/Chandler/CpiaZeroPointFourStatus
>
> John
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>
----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42