RE: [Pythoncard-users] Priority One - Object Persistence

I agree with you, Andy. Let's not pick one, let's each pick whatever we want
and see what happens. I'm willing to help with them all. I may go with
MetaKit because I have a short-term need. I've done lots of stuff in the
past with SQL (though not with Python) so I can help a bit there. And I've
played with ZODB (see my Bulldozer project at
http://sourceforge.net/projects/bdoz/) and have a real interest in making it
work.

As for sample apps, let's do a few. We'll keep them simple to begin with.
I'll probably start with Kevin's address sample, because it is already there
and working. I'd also like to create apps that I'll actually want to use. So
a to-do list would be nice, as well as a more feature-rich contact manager.

---
Patrick K. O'Brien
Orbtech

> -----Original Message-----
> Andy Todd wrote
>
> Always ready for some fun.
>
> In the ZODB persistence thread I get the impression that Dan is firmly
> in favour of using it and that Kevin has some justifiable reservations.
> You are going to use MetaKit (damn, another set of documentation to
> peruse) and have looked at Webware but aren't pursuing it. I, meanwhile,
> have said previously that I will look into pickle/shelve and have built
> our only sample that talks to external storage (dbBrowser) which so far
> is a relational database.
>
> So, between us I think we have all the bases covered. The great thing
> about having such a range of skills and experience contributing to the
> project is that there is no reason we cannot try out all of them. I
> think that there is value in each of us trying out different tools and
> sharing our discoveries. This will cover all of the options and allow us
> to implement a component based persistence solution that allows the
> developer to switch in the back end they wish to use.
>
>
> Of course you have hit the nail on the head with your response to
> Rowland's post in the 'what do we call these things' thread. We need to
> decide on the data model that we are going to (try to) implement in all
> of these storage mechanisms otherwise we will end up with a number of
> incompatible solutions with different answers to the questions that this
> kind of application asks. I'm working on an Oracle backed PythonCard
> application that will raise some of these questions - particularly how
> do I tell the backend when the attributes of a displayed object have
> changed - and will share my bumbling about with you all.
>
> So what are you thinking about for a sample application, going back to
> your post from last year I see;
>
> """
> So if the goal is simple visual construction of screens that access
> transparently persistent data, I'd like to suggest that we embark on a
> joint effort to create such an application from scratch, using the tools
> that we have so far in PythonCard, as a way to flesh out further
> requirements. The development of this sample application could even be
> documented as a tutorial for others.
>
> If there is interest in this idea, here is what I think needs to happen:
>
> 1. Decide on a sample application that reflects the kind of app people
> would have done in HyperCard.
>
> 2. Decide how we are going to store the data - CSV, ZODB, XML, MySQL, etc.
>
> 3. Develop the app in a collaborative fashion to get feedback from more
> than one person.
>
> 4. Document as much as possible so that this serves as a tutorial
> of sorts.
>
> 5. Repeat for the next app until PythonCard is perfect.
> """
>
> The major change since you posted this is the presence of the
> resourceEditor sample. As to the sample application, I'm easy so suggest
> away. Does anyone have a particular itch that they want to scratch?
>
> Regards,
> Andy
> --
> -----------------------------------------------------------------------
>  From the desk of Andrew J Todd esq.
> "Its good to have an open mind, but not so open that your brains fall out"
>
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users