Re: [Pythoncard-users] What Do We Call These Things?

Howdy,

As a persistance mechanism is xml_objectify and xml_pickle being=
 considered?
comparison to XML-RPC
http://www-106.ibm.com/developerworks/library/x-matters15.html#re=
sources

introduction;
http://www-106.ibm.com/developerworks/xml/library/xml-matters1/in=
dex.html

follow up;
http://www-106.ibm.com/developerworks/xml/library/x-matters11.htm=
l

Seems lightweight, transparent, and very easy to use.
The objects live in XML, keeping options open.

The latest IBM article mentions that the code is currently 
being enhanced.




On Fri, 08 Feb 2002 19:35:44 +1100, Andy Todd wrote:
>Patrick K. O'Brien wrote:
>
>>=A0My take on this is that a Hypercard application could be seen=
 as a
>>=A0collection of persistent object instances. In this case, each=
 object
>>=A0instance also knew about its display properties and could=
 override them. So
>>=A0the *class* would be "defined" to have a particular background=
 (with a set
>>=A0of buttons, etc.), but each *instance* (card) could have=
 specific additions
>>=A0(different background).
>>
>>=A0It seems to me that one could replicate much of this behavior=
 using the
>>=A0ZODB. But that would imply that we wanted the display=
 mechanism and the
>>=A0object data to be tightly intertwined and both stored in the=
 database. That
>>=A0is not how the Pythoncard framework is designed now. And I'm=
 not sure
>>=A0everyone would agree that this is a good idea. At the same=
 time, I don't
>>=A0think it would be too much of a stretch to imagine all the=
 Pythoncard
>>=A0resource files existing in the ZODB for the app. But then we=
 have the same
>>=A0problem as Zope - programmers want these kinds of things to be=
 text files,
>>=A0not buried in the database.
>>
>>=A0Just a bit of rambling.
>
>
>Rambling, possibly, but I think you have hit the nail on the=
 head. Our
>guiding principle should always by K.I.S.S. - no, not the make=
 up
>addicted band, but "Keep It Simple Stupid".
>
>We should make our central framework as elegant, simple and thin=
 as
>possible but make it easily extensible. Our default choices for=
 such
>things as persistent storage should be available to everyone,=
 but
>expandible to include more complex solutions for those who=
 require them
>(e.g. oodbms, rdbms, etc.).
>
>
>>
>>=A0---
>>=A0Patrick K. O'Brien
>>=A0Orbtech
>>
>>
>>>-----Original Message-----
>>>From: pyt...@li...
>>>[mailto:pyt...@li...]On Behalf=
 Of
>>>Francois Granger
>>>Sent: Sunday, January 06, 2002 3:22 PM
>>>To: pyt...@li...
>>>Subject: Re: [Pythoncard-users] What Do We Call These Things?
>>>
>>>
>[snip original message]
>
>>>
>
>Regards,
>Andy