[Chandler-dev] What is next for Chandler desktop?

[D John Anderson]

On Sep 5, 2007, at 5:03 PM, Grant Baillie wrote:

>
> On 5 Sep, 2007, at 14:47, D John Anderson wrote:
>
>>
>> On Sep 5, 2007, at 2:05 PM, Katie Capps Parlante wrote:
>>
>>>
>>> - Perhaps we shouldn't be storing UI items in the repository. Yes,
>>> transparently persisting UI state is in theory a cool property,  
>>> but in
>>> practice I don't know that we are effectively getting the  
>>> persistence
>>> right and it perhaps comes at too great a cost.
>>
>> Are you proposing that we don't use transparent persistence for  
>> storing blocks and other associated UI data structures?
>
> Yes, that is the suggestion/proposal.

It seems to me that the transparent persistence isn't a problem but a  
feature because it makes the code so much easier to write and much  
less error prone.

Having worked on lots of projects that required I do a SQL queries  
every time I need to access some data convince me that it slows  
progress. I suspect a better solution would be to keep a mostly  
transparent persistence model but change the data storage and/or data  
structure underneath it to avoid requiring the programmer to manage  
the data access manually.

>
> --Grant
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev