pythoncard-users Mailing List for PythonCard (Page 179)

Andy Todd wrote:

> Lindstrom Greg - glinds wrote:
> 
>> Greetings-
>>
>> I have been coding Python for about 3 years, and have been using 
>> TkInter and
>> wxWindows for about a year.  having just run across PythonCard via the
>> weekly summary, I am interested in finding out what it is about, and 
>> what it
>> can do for me.  I have downloaded and installed the files, and run the
>> samples.py demo. I then read through the tutorial, but found it to be 
>> little
>> help; for example, I am told to run the PythonCard resourceEditor to 
>> create
>> or modify an existing application, but I have no clue how to run the
>> resourceEditor!
> 
> 

> 
> A-ha, you have discovered our deliberate mistake designed to lure in 
> unsuspecting tutorial writers! We should really add this to the tutorial 
> and the FAQ;
> 
> The easiest way to run the sample applications that are shipped with the 
> PythonCard prototype framework is via the 'sample' application. To start 
> this up, navigate to the directory where you have unzipped the package 
> (or set up your CVS copy) and from there go to the 'samples' sub 
> directory. From here, either type 'python samples.py' from the command 
> line or double click on 'samples.py' in your favourite file system 
> explorer.
> 
>  From this sample application you can then launch any of the supplied 
> PythonCard modules.


Of course, what I *meant* to say here was;

To launch any of the supplied PythonCard modules (such as the 
resourceEditor) just select the module name from the list on the left of 
the window and press the "launch" button.

> 
> If you have problems running this sample sampler then feel free to send 
> an email to the mailing list (pyt...@li...) 
> asking for help. It may save you an email if we give you our first 
> response here - "of course you have installed PythonCard in such a way 
> that the directory PythonCardPrototype is on your Python path, haven't 
> you?"
> 
> 
>>
>> I need help getting started with this package.  If you are willing to 
>> help,
>> I am willing to write a step-by-step tutorial for the group.
>>
>> Greg Lindstrom
>> Acxiom Corporation,                    mail: CWY10011149
>> InfoBase Products Development                  office: (501) 342-1626
>> 301 Industrial Blvd, Conway, AR, 72032     fax:     (501) 336-3911 
>> email: Gre...@ac...           "The great thing about 
>> standards is there are so many to choose from"
>> Michael Hudson
>>
>>
> 
> Any additions, subtractions or long divisions will be gladly received. 
> Welcome to PythonCard Greg, I know you will enjoy what we have and am 
> looking forward to your contribution.
> 
> Completely off topic, I set up the first database server for InfoBase 
> Australia, hope your 'links' are still doing fine.
> 
> Regards,
> Andy


for i in range(1,100000):

    proof.read()

Oh-dear-time-for-a-beer-and-some-cricket-ly y'rs,
Andy
-- 
-----------------------------------------------------------------------
 From the desk of Andrew J Todd esq.
"Another year older, still no wiser." - Me, on my birthday

Lindstrom Greg - glinds wrote:

> Greetings-
> 
> I have been coding Python for about 3 years, and have been using TkInter and
> wxWindows for about a year.  having just run across PythonCard via the
> weekly summary, I am interested in finding out what it is about, and what it
> can do for me.  I have downloaded and installed the files, and run the
> samples.py demo. I then read through the tutorial, but found it to be little
> help; for example, I am told to run the PythonCard resourceEditor to create
> or modify an existing application, but I have no clue how to run the
> resourceEditor!


A-ha, you have discovered our deliberate mistake designed to lure in 
unsuspecting tutorial writers! We should really add this to the tutorial 
and the FAQ;

The easiest way to run the sample applications that are shipped with the 
PythonCard prototype framework is via the 'sample' application. To start 
this up, navigate to the directory where you have unzipped the package 
(or set up your CVS copy) and from there go to the 'samples' sub 
directory. From here, either type 'python samples.py' from the command 
line or double click on 'samples.py' in your favourite file system explorer.

 From this sample application you can then launch any of the supplied 
PythonCard modules.

If you have problems running this sample sampler then feel free to send 
an email to the mailing list (pyt...@li...) 
asking for help. It may save you an email if we give you our first 
response here - "of course you have installed PythonCard in such a way 
that the directory PythonCardPrototype is on your Python path, haven't you?"


> 
> I need help getting started with this package.  If you are willing to help,
> I am willing to write a step-by-step tutorial for the group.
> 
> Greg Lindstrom
> Acxiom Corporation,                    mail: CWY10011149
> InfoBase Products Development                  office: (501) 342-1626
> 301 Industrial Blvd, Conway, AR, 72032     fax:     (501) 336-3911 
> email: Gre...@ac...           
> "The great thing about standards is there are so many to choose from"
> Michael Hudson
> 
> 

Any additions, subtractions or long divisions will be gladly received. 
Welcome to PythonCard Greg, I know you will enjoy what we have and am 
looking forward to your contribution.

Completely off topic, I set up the first database server for InfoBase 
Australia, hope your 'links' are still doing fine.

Regards,
Andy
-- 
-----------------------------------------------------------------------
 From the desk of Andrew J Todd esq.
"Another year older, still no wiser." - Me, on my birthday

Andy Todd <an...@ha...>:
> 
> Thanks Patrick, looks like you have just identified my weekend reading. 
> Has anyone on the list got any experience with webware and/or get any 
> comments?
 
I've barely glanced at MiddleKit, but I have very positive experiences
with Webware in general. (Perhaps not all that relevant to
PythonCard.. :)

> Regards,
> Andy

--
Magnus Lie Hetland                                  The Anygui Project
http://hetland.org                                  http://anygui.org

Patrick K. O'Brien wrote:

> Webware has something like this (persisting objects to a database) that
> might be worth looking into. It works with mySQL now, but is supposed to
> work well with just about any database, at least in theory. I haven't worked
> with this yet, but I know it works well for the Webware folks. Here is a
> good starting point:
> 
> http://webware.sourceforge.net/Webware/MiddleKit/Docs/Intro.html
> 
> ---
> Patrick K. O'Brien
> Orbtech
> 
> [snip]
> 
> 
>>I'm all in favour of adding persistence support with shelve or ZODB. I'm
>>also working on a persistence API (still at the 'conceptual' stage) and
>>would be interested in any thoughts or observations on the applicability
>>of trying to fit a common standard to several different storage
>>mechanisms (relational, object, flat file, etc.)
>>
> 
> [snip]
> 
> 
>>Regards,
>>Andy
>>--
>>-----------------------------------------------------------------------
>> From the desk of Andrew J Todd esq.
>>This space for rent
>>
> 
> 
> 

Thanks Patrick, looks like you have just identified my weekend reading. 
Has anyone on the list got any experience with webware and/or get any 
comments?

Regards,
Andy
-- 
-----------------------------------------------------------------------
 From the desk of Andrew J Todd esq.
"Another year older, still no wiser." - Me, on my birthday

I just wanted to get a link into the archive...

Open Source Databases Linkfest
http://www.skippingdot.net/2002/01/30

ka

Webware has something like this (persisting objects to a database) that
might be worth looking into. It works with mySQL now, but is supposed to
work well with just about any database, at least in theory. I haven't worked
with this yet, but I know it works well for the Webware folks. Here is a
good starting point:

http://webware.sourceforge.net/Webware/MiddleKit/Docs/Intro.html

---
Patrick K. O'Brien
Orbtech

[snip]

> I'm all in favour of adding persistence support with shelve or ZODB. I'm
> also working on a persistence API (still at the 'conceptual' stage) and
> would be interested in any thoughts or observations on the applicability
> of trying to fit a common standard to several different storage
> mechanisms (relational, object, flat file, etc.)

[snip]

> Regards,
> Andy
> --
> -----------------------------------------------------------------------
>  From the desk of Andrew J Todd esq.
> This space for rent

Since we are investigating storage formats for PythonCard, I went ahead and
asked the question about the data format stability of ZODB. The question and
response are below.

ka

-----Original Message-----
From: Barry A. Warsaw [mailto:ba...@zo...]
Sent: Wednesday, January 30, 2002 8:14 AM
To: Kevin Altis
Subject: Re: FW: zodb data format stability

>>>>> "KA" == Kevin Altis <al...@se...> writes:

    KA> Unless you know the answer, one of the questions I want to ask
    KA> about ZODB, which probably applies to any object data store is
    KA> the long-term stability of the format.

    KA> I'm mostly concerned about things like creating say an
    KA> addresses database with Python 2.1 and ZODB and then of course
    KA> being able to pass that database around to a Mac, Linux,
    KA> Windows and have it work. But then there is the issue of
    KA> switching versions of Python and/or the ZODB module say a
    KA> couple of years from now, opening the database and having it
    KA> get corrupted, even though no changes were made to your
    KA> program or framework. Also, do we need to be careful to use
    KA> built-in Python types such as int and string? Do you know what
    KA> I mean re my concerns?

ZODB is pretty closely tied to Python pickles, which are guaranteed to
be portable across platforms and Python releases.  They are
endian-safe and 32/64-bit safe, so you should have no problem moving
Data.fs files between different systems.

Pickles are a Python-specific data format so if you wanted to
interchange the data between different programming languages, you'd
need to use an intermediate format.

The data format for FileStorage is well defined so even if we changed
the Data.fs format in a later version of ZODB (unlikely), we'll no
doubt provide migration/update tools.  Backwards compatibility is very
important to us.

Hope that helps,
-Barry

Greetings-

I have been coding Python for about 3 years, and have been using TkInter and
wxWindows for about a year.  having just run across PythonCard via the
weekly summary, I am interested in finding out what it is about, and what it
can do for me.  I have downloaded and installed the files, and run the
samples.py demo. I then read through the tutorial, but found it to be little
help; for example, I am told to run the PythonCard resourceEditor to create
or modify an existing application, but I have no clue how to run the
resourceEditor!

I need help getting started with this package.  If you are willing to help,
I am willing to write a step-by-step tutorial for the group.

Greg Lindstrom
Acxiom Corporation,                    mail: CWY10011149
InfoBase Products Development                  office: (501) 342-1626
301 Industrial Blvd, Conway, AR, 72032     fax:     (501) 336-3911 
email: Gre...@ac...           
"The great thing about standards is there are so many to choose from"
Michael Hudson



*********************************************************************

The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.

Kevin Altis wrote:

> I can't guarantee which of the items below will actually get done in the
> next month, but all of them have been brought up on the list in the last few
> weeks or I've been thinking about them on my own. The main issue for me is
> changing how we wrap the underlying wxPython controls used for our
> components. This is by far the largest and most far-reaching change to the
> framework, so I'll start a separate topic for it tomorrow. Even the
> timeframe of a month is arbitrary; most of the items below could be
> completed sooner, but things always seem to take longer than expected and I
> end up finding more things to complete in the meantime. Feel free to add
> your own "hot issues" into the mix and/or identify which items below are the
> most important to you.
> 
> I'm always interested in pursuing (or better yet helping others pursue) the
> items that will get more people actually trying and then using PythonCard,
> creating more apps of their own or samples and thus helping to identify any
> problems in the current design. In the absence of feedback I just follow my
> own muse. If people end up participating more on the list, writing
> documentation, or working on the framework itself that is a big bonus.
> 
> ka
> ---
> 
> tentatively called release 0.7
> 
> remove _delegate "HAS-A" for components and change to direct
>   "IS-A" subclasses
>   if the switch goes well, go ahead and add additional wxPython
>   controls
> 
> migrate MenuBar, Menu, MenuItem to subclasses of wxPython classes
> 
> improve resourceEditor
>   make a dedicated property editor
>   add dialog editing to resourceEditor
> 
> more work on components, add type information
> 
> continue localization experimentation
>   add strings to resource format
>   possibly make separate special simplified localized resource file
>     that only contains strings: labels, text, titles, etc.
>     update Resource loading to support simplified resource format
>     add support to resourceEditor as well
> 
> add idle, timer, move, size, and exit events
> 
> investigate an IDLE clone for source editing?
> 
> resolve background/window/frame, panel/form issue
>   once done, add support for additional window styles
>   including scrolling windows. how does wxNotebook fit
>   in here?
> 
> simple cross-platform printing via wxHtmlEasyPrinting
>   this will give us plain and basic formatted printing
>   page setup, print, print preview
> 
> tests of shelve and/or ZODB as persistence mechanism
> 
> incorporate Cliff Wells CSV importer for Python/wxPython
>   http://sourceforge.net/projects/python-dsv/
> 
> threading - update one of the existing samples such as
>   hopalong or findfiles to show how to use a separate thread
>   for long running tasks or create a new sample. i previously
>   suggested doing a PythonCard version of webchecker and/or
>   websucker, which are included in the Python Tools directory
> 
> more documentation
>   rewrite getting started
>   migrate text files to html
>   tidy up the web site
>   start using www.pythoncard.org domain?
> 
> start identifying wxPython-mac issues with PythonCard
> 
> ----
> beyond 0.7
> 
> move to first "real" alpha version
>   change package name to PythonCard instead of PythonCardPrototype
> 
> require Python 2.2
> 
> do more "market research" to determine what features are needed
>   to get people using PythonCard instead of tkinter, especially
>   people new to Python
> 
> designate someone other than me as the release manager
>   setup PythonCard descriptions on the Vaults of Parnassus,
>   freshmeat.net, and other outlets for promotion of PythonCard
> 
> 


I like the list, and given current progress rates by everyone apart from 
Kevin I think that a month is optimistic. Still, lets aim for that kind 
of timescale.

In terms of the items on the list;

Has any thought of scintilla for the source editing component? I'm 
speaking from a position of complete ignorance here so the usual caveat 
applies.

I'm all in favour of adding persistence support with shelve or ZODB. I'm 
also working on a persistence API (still at the 'conceptual' stage) and 
would be interested in any thoughts or observations on the applicability 
of trying to fit a common standard to several different storage 
mechanisms (relational, object, flat file, etc.)

I'd also like to beef up our packaging, maybe provide a proper installer 
and certainly be more cross platform friendly. The first step here is to 
update the setup.py to ensure that the components are installed in 
'site-packages' and the samples are kept seperate. I know Kevin is also 
keen on not compiling resource files to .pyc and this is also on the list.

I think we should probably spend some more effort on the web site as 
well. Someone with a little more design flair than I may like to suggest 
  improvements or come up with a catchy style. We should probably also 
upgrade our documentation techniques and support formats other than 
html. I know Magnus uses some tools to generate different outputs from 
the same source for the AnyGUI docs, and Mark Pilgrim uses something 
similar for Dive into Python. I'll have a bit of a look around but don't 
let me stop anyone else coming up with something that works.

I see someone has reserved www.pythoncard.org at network solutions by 
the way, was that you Kevin?

Regards,
Andy
-- 
-----------------------------------------------------------------------
 From the desk of Andrew J Todd esq.
This space for rent

At 12:35 -0800 on 28/01/02, in message Pythoncard-users digest, Vol 1 
#147 - 12 msgs, you wrote:
>From: "Kevin Altis" <al...@se...>
>To: "pythoncard-Users" <pyt...@li...>
>Subject: RE: [Pythoncard-users] localizing dialogs
>Date: Thu, 24 Jan 2002 22:59:09 -0800
>
>I've updated the dbBrowser, textEditor, and resourceEditor samples in cvs so
>[...]I agree with Francois that the resourceEditor should be one of 
>the examples
>of a localized PythonCard app. However, it won't be possible to localize the
>Property Editor window until I rewrite it. Also, many of the dialogs and
>menu items in resourceEditor will be changing quite a bit over the next
>month since the resourceEditor is one of the things I want to spend a lot of
>time improving. I expect I'll end up changing, adding, and removing dialogs
>and menus, but I won't know which ones until I start the modifications.
>
>So, nobody (that's probably you Francois) should put much time into doing a
>localized version of the resourceEditor for their language just yet, unless
>they want to deal with changes the next few weeks. I don't want anyone
>wasting their time without at least knowing it might be wasted. :)

So, what about textEditor ?
1) you _must_ have one major app localized to give you nightmares... ;-)
2) I bought RealPC and installed it on my mac at home to be able to 
run PythonCard. So, I have to justify the expense ;-)

proto-0.6.3.2.zip has been uploaded to SF. It should show up soon in the
file list.

I think I will refer to 0.6.3 and its "children" as the jinxed releases.
Actually, it goes back to the end of December when I was first trying to get
out 0.6. I suppose it is past time to consider a unit test strategy for the
GUI components to catch a lot of this stuff...

Release 0.6.3.2 2002-01-28
restored loseFocus event

Release 0.6.3.1 2002-01-26
made sillywalk.gif and lrggumby.gif opaque to fix GTK drawing
fixed exception when locale.getdefaultlocale() is None

Release 0.6.3 2002-01-25
commented out stack info dialog in resourceEditor
added FAQ.txt, updated toc.html and other documentation
changed addEventListener so the MessageWatcher is always
  the first listener to be notified
added localization support for resource files
  added minimal.fr.rsrc.py for French users as an example
Linux fixes
  resourceEditor and samples file launching
  CaptureMouse() in resourceEditor
  fixed asserts in BitmapCanvas where OnSize event was
    called prior to __init__ finishing
added registry.py, updated framework to use registry
added quotes to path/filename in resourceEditor for launching

ka

The grief continues. I tried editing some menus in the resourceEditor and
realized that 'loseFocus' events aren't firing, thus the menu editor doesn't
work. The missing line is
name = 'loseFocus'
in event.py as shown below.

class LoseFocusEvent( Event ) :

    name = 'loseFocus'

    def __init__( self, aSource ) :
        Event.__init__( self, aSource )

So now I get to do a 0.6.3.2 after all.

ka

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Kevin
> Altis
> Sent: Saturday, January 26, 2002 5:02 PM
> To: pythoncard-Users
> Subject: [Pythoncard-users] PythonCard 0.6.3.1
>
>
> It seems I am doomed to bug fix after bug fix. So now there is a
> proto-0.6.3.1.zip which fixes the problem of none of the samples working
> when your locale.getdefaultlocale() returns None and then I attempt to log
> the language and country code. Argh.
>
> Release 0.6.3.1 2002-01-26
> made sillywalk.gif and lrggumby.gif opaque to fix GTK drawing
> fixed exception when locale.getdefaultlocale() is None
>
> ka
>
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>

I can't guarantee which of the items below will actually get done in the
next month, but all of them have been brought up on the list in the last few
weeks or I've been thinking about them on my own. The main issue for me is
changing how we wrap the underlying wxPython controls used for our
components. This is by far the largest and most far-reaching change to the
framework, so I'll start a separate topic for it tomorrow. Even the
timeframe of a month is arbitrary; most of the items below could be
completed sooner, but things always seem to take longer than expected and I
end up finding more things to complete in the meantime. Feel free to add
your own "hot issues" into the mix and/or identify which items below are the
most important to you.

I'm always interested in pursuing (or better yet helping others pursue) the
items that will get more people actually trying and then using PythonCard,
creating more apps of their own or samples and thus helping to identify any
problems in the current design. In the absence of feedback I just follow my
own muse. If people end up participating more on the list, writing
documentation, or working on the framework itself that is a big bonus.

ka
---

tentatively called release 0.7

remove _delegate "HAS-A" for components and change to direct
  "IS-A" subclasses
  if the switch goes well, go ahead and add additional wxPython
  controls

migrate MenuBar, Menu, MenuItem to subclasses of wxPython classes

improve resourceEditor
  make a dedicated property editor
  add dialog editing to resourceEditor

more work on components, add type information

continue localization experimentation
  add strings to resource format
  possibly make separate special simplified localized resource file
    that only contains strings: labels, text, titles, etc.
    update Resource loading to support simplified resource format
    add support to resourceEditor as well

add idle, timer, move, size, and exit events

investigate an IDLE clone for source editing?

resolve background/window/frame, panel/form issue
  once done, add support for additional window styles
  including scrolling windows. how does wxNotebook fit
  in here?

simple cross-platform printing via wxHtmlEasyPrinting
  this will give us plain and basic formatted printing
  page setup, print, print preview

tests of shelve and/or ZODB as persistence mechanism

incorporate Cliff Wells CSV importer for Python/wxPython
  http://sourceforge.net/projects/python-dsv/

threading - update one of the existing samples such as
  hopalong or findfiles to show how to use a separate thread
  for long running tasks or create a new sample. i previously
  suggested doing a PythonCard version of webchecker and/or
  websucker, which are included in the Python Tools directory

more documentation
  rewrite getting started
  migrate text files to html
  tidy up the web site
  start using www.pythoncard.org domain?

start identifying wxPython-mac issues with PythonCard

----
beyond 0.7

move to first "real" alpha version
  change package name to PythonCard instead of PythonCardPrototype

require Python 2.2

do more "market research" to determine what features are needed
  to get people using PythonCard instead of tkinter, especially
  people new to Python

designate someone other than me as the release manager
  setup PythonCard descriptions on the Vaults of Parnassus,
  freshmeat.net, and other outlets for promotion of PythonCard

This is probably relevant to the shelve investigation.

The Google URL was a bit long, so here's an ASPN link
http://aspn.activestate.com/ASPN/Mail/Message/python-list/1001109

ka

It seems I am doomed to bug fix after bug fix. So now there is a
proto-0.6.3.1.zip which fixes the problem of none of the samples working
when your locale.getdefaultlocale() returns None and then I attempt to log
the language and country code. Argh.

Release 0.6.3.1 2002-01-26
made sillywalk.gif and lrggumby.gif opaque to fix GTK drawing
fixed exception when locale.getdefaultlocale() is None

ka

It has been almost six months since version 0.1 was released on July 26,
2001 and over seven months since the original mailing list was founded on
June 19, 2001. We've made a lot of progress during that time. According to
SF records, it also looks like Dan Winkler registered the PythonCard project
with SourceForge on January 24, 2001. Dan has been very quiet the last six
months, but I would like to thank him for his work on the original
HyperCard, starting the PythonCard project on SourceForge and letting other
people get involved.

Enjoy,

ka
ps. I hid all of the old releases. If anyone needs access to them let me
know. Also, SF appears to be having some server problems today and the 0.6.3
zip has not shown up as of 3:00 pm USA west coast time, but just keep
checking back and I'm sure it will show up.
---

Release 0.6.3 is mostly a bug fix release for Linux/GTK issues.

There is still a known wxWindows/wxPython bug that prevents setting the font
in single line wxTextCtrls, so you can't set the font on Linux with the
TextField and PasswordField components. Cliff Wells reports that sound
doesn't work with wxPython on his machine, your mileage may vary. I did not
do any work on converting layouts to sizers since 0.6.2, so fixed layouts
will still have display issues depending on the default font and font size
used under Linux/GTK.

You can get the latest version of PythonCard at:
http://sourceforge.net/project/showfiles.php?group_id=19015

Remember to backup or just delete your old PythonCardPrototype directory
before installing a new version, so that the old files aren't still in the
package directory. As always, report any problems to the list.

Release 0.6.3 2002-01-25
commented out stack info dialog in resourceEditor
added FAQ.txt, updated toc.html and other documentation
changed addEventListener so the MessageWatcher is always
  the first listener to be notified
added localization support for resource files
  added minimal.fr.rsrc.py for French users as an example
Linux fixes
  resourceEditor and samples file launching
  CaptureMouse() in resourceEditor
  fixed asserts in BitmapCanvas where OnSize event was
    called prior to __init__ finishing
added registry.py, updated framework to use registry
added quotes to path/filename in resourceEditor for launching

More details, but I scooped this news story by a couple of hours. <wink>

---
Patrick K. O'Brien
Orbtech

-----Original Message-----
From: zop...@zo...
[mailto:zop...@zo...]On Behalf Of Barry A. Warsaw
Sent: Friday, January 25, 2002 2:25 PM
To: pyt...@py...
Cc: pyt...@py...; zod...@zo...; zop...@zo...;
zop...@zo...
Subject: [Zope-Annce] RELEASED - StandaloneZODB 1.0 release candidate 1



I'm please to announce the first official release of StandaloneZODB,
the Python object persistency system also known as the Z Object
Database.  ZODB is the object-oriented database underlying Zope; the
StandaloneZODB project's goal is to provide those same facilities to
non-Zope related Python applications.

Today we are releasing StandaloneZODB 1.0 release candidate 1.  We
expect to release the final version on 1-Feb-2002.

StandaloneZODB is based on the same code as the ZODB in Zope, albeit
on a separate release branch.  Its inspiration comes from Andrew
Kuchling's StandaloneZODB project on SourceForge.  While there are
still some differences, the Standalone 1.0 release is the first on the
path toward convergence.  Subsequent releases should complete the
merge of Andrew's and Zope Corporation's packages.

The StandaloneZODB release includes the following components:

    - Core ZODB, including the persistence machinery
    - Standard storages such as FileStorage
    - Supporting modules such as ExtensionClass
    - The persistent BTrees modules
    - ZEO
    - Experimental Berkeley storages
    - Some documentation <wink>

See the README file for details on building and installing
StandaloneZODB.  For details on using ZODB, see Andrew's included user
guide.

StandaloneZODB 1.0c1 is released under the ZPL 2.0.  It should be
compatible with all Python versions from Python 2.1 to Python 2.2.  It
may or may not work with versions earlier than Python 2.1.

Download StandaloneZODB-1.0c1.tgz from:

    http://www.zope.org/Products/StandaloneZODB

and visit the StandaloneZODB Wiki page at:

    http://www.zope.org/Wikis/ZODB/StandaloneZODB

See also:

    http://www.zope.org/Wikis/ZODB/FrontPage

for more information about our long-range ZODB plans.

Enjoy,
-Barry

Barry A. Warsaw
Zope Corporation, Pythonlabs
ba...@zo...

_______________________________________________
Zope-Announce maillist  -  Zop...@zo...
http://lists.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists - 
 Users: http://lists.zope.org/mailman/listinfo/zope
 Developers: http://lists.zope.org/mailman/listinfo/zope-dev )

Actually, I just commented out the menu item in the resource file:

  #{ 'type':'MenuItem',
  #  'name':'menuEditStackInfo',
  #  'label':'Stack Info...',
  #  'command':'editStackInfo'},

The stack name doesn't actually do anything in the framework since most of
the stack attributes were moved to the background. The stack still has a
name, since it is defined in the template.rsrc.py file and any other
resource file you edit with the resourceEditor, but the value has no impact
on an app. If it turns out we still need the stack info dialog and stack
name attribute later it will be easy to put support back in.

ka

FYI, it looks like a new release of ZODB is available:

http://www.zope.org/Products/StandaloneZODB

---
Patrick K. O'Brien
Orbtech

I've updated the dbBrowser, textEditor, and resourceEditor samples in cvs so
that they can load localized dialogs and windows. My earlier message was
misleading, the Background and GenericDialog classes both expect to receive
resources as part of their initialization. When I wrote the message I was
thinking about the PythonCardApp class and the app initialization which is
different. I didn't update textRouter, since it creates its dialogs
dynamically and so the same localization strategy won't work.

Anyway, simply changing the code to use the internationalResourceName
function I already wrote for the backgrounds works fine. You just pass in a
full path instead of just a filename in case the current working directory
has changed since the app was started.

class FindDialog(dialognew.GenericDialog):
    def __init__(self, aBg, searchText='', wholeWordsOnly=0,
caseSensitive=0) :
        # load the resource
        path = os.path.join(aBg.stack.app.applicationDirectory, \
                            model.internationalResourceName('find'))
        aDialogRsrc = res.ResourceFile(path).getResource()
        dialognew.GenericDialog.__init__(self, aBg, aDialogRsrc)


I agree with Francois that the resourceEditor should be one of the examples
of a localized PythonCard app. However, it won't be possible to localize the
Property Editor window until I rewrite it. Also, many of the dialogs and
menu items in resourceEditor will be changing quite a bit over the next
month since the resourceEditor is one of the things I want to spend a lot of
time improving. I expect I'll end up changing, adding, and removing dialogs
and menus, but I won't know which ones until I start the modifications.

So, nobody (that's probably you Francois) should put much time into doing a
localized version of the resourceEditor for their language just yet, unless
they want to deal with changes the next few weeks. I don't want anyone
wasting their time without at least knowing it might be wasted. :)

ka

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Kevin
> Altis
> Sent: Tuesday, January 22, 2002 11:02 PM
> To: pythoncard-Users
> Subject: [Pythoncard-users] localizing dialogs
>
>
> The dialognew.py module which contains the GenericDialog class
> won't handle
> the same localization solution I used for the Background without
> a change to
> its __init__. This is best illustrated by looking at a fragment of the
> FindDialog class from textEditor.pyw
>
> class FindDialog(dialognew.GenericDialog):
>     def __init__(self, aBg, searchText='', wholeWordsOnly=0,
> caseSensitive=0) :
>         # load the resource
>         path = os.path.join(aBg.stack.app.applicationDirectory,
> 'find.rsrc.py')
>         aDialogRsrc = res.ResourceFile(path).getResource()
>         dialognew.GenericDialog.__init__(self, aBg, aDialogRsrc)
>  ...
>
> As you can see, GenericDialog expects to receive a Resource, not
> a filename.
> I think that I'm going to change the code so that only a string
> is passed to
> the GenericDialog __init__ and then GenericDialog will use
> roughly the same
> algorithm for loading the resource file as the Background class does. The
> __init__ above would become
>
>         dialognew.GenericDialog.__init__(self, aBg, 'find')
>
> I'll think about this some more before checking anything in tomorrow.
>
> ka
>
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>

(Sorry for this answer to various posts in the same message, I am in 
digest mode at this time)

At 12:09 -0800 24/01/02, in message Pythoncard-users digest, Vol 1 
#146 - 12 msgs, pyt...@li... wrote:
>From: "Kevin Altis" <al...@se...>
>
>Lately, I have been thinking that we should drop the .py file extension
>since the resource files are not executable, but then we wouldn't be able to
>use import instead of eval(), or would we?

The .py extension, allowing syntax coloring in some editors, make 
editing easier....

>  Would a .rsrc extension conflict
>with an existing extension on Linux, Windows, Mac?

The Mac does not care about extensions.
Sorry, this has change with the Internettization of hte Mac ;-) but 
still the rsrc extension is not an issue on Mac OS 9.x

>From: "Kevin Altis" <al...@se...>
>I think that I'm going to change the code so that only a string is passed to
>the GenericDialog __init__ and then GenericDialog will use roughly the same
>algorithm for loading the resource file as the Background class does. The
>__init__ above would become
>
>         dialognew.GenericDialog.__init__(self, aBg, 'find')
>
>I'll think about this some more before checking anything in tomorrow.

As soon as it is ready for localisation, i'll provide you with a 
fr_FR file for it.

>From: "Kevin Altis" <al...@se...>
>Subject: [Pythoncard-users] wxPython-Mac mailing list
>For those of you wanting to help or just follow the progress of the wxPython
>port.

Currently downloading to test what's available and provide bug reports on it.

>From: "Kevin Altis" <al...@se...>
>Subject: [Pythoncard-users] updating the documentation
>
>I want to add a FAQ, mission statement (or what is PythonCard?), and update
>the home page and screen shot pages. It looks like we also need a page
>covering the resourceEditor with screen shots.

I thought that this app was the masterpiece to be localized, since it 
is really usefull for working with PythonCard... And probably an 
extensive test of the new localisation feature...
?

>From: "Kevin Altis" <al...@se...>
>Subject: [Pythoncard-users] PythonCard FAQ 1.0
>
>What is PythonCard?
>   PythonCard is designed to be an application development framework for
>use by everybody. Its purpose and goal is ease of use and increasing
>productivity. From the first time to developer to the veteran coder who

first time developer

>Do I need to know Python to use PythonCard?
>   Yes

But learning Python is really easy. And lots of documentations and 
tutorials are available.

I added a page to hold documentation for the resourceEditor and runtime
tools.

http://pythoncard.sourceforge.net/layouteditor.html

ka

I've updated all of the State of the Framework messages for release 0.6.2.
Rather than repost all of the messages to the mailing list, you should just
visit
  http://pythoncard.sourceforge.net/toc.html
to get to each updated file. I'll try and keep those updated for each
release until the content is molded into some regular documentation. There
is quite a lot of info in the files, so if you are using PythonCard, they
are worth reading.

Please post any questions or corrections to the list.

ka

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Kevin
> Altis
> Sent: Wednesday, January 23, 2002 5:15 PM
> To: pythoncard-Users
> Subject: [Pythoncard-users] updating the documentation
>
>
> I decided it was time to work on documentation again, so to get
> started I'm
> just collecting information already on the mail list or other sources and
> sticking it into text files. I plan to update the files where they are
> out-of-date and then convert everything into HTML later on. Right now, I'm
> concentrating on just hunting and gathering. I'm sticking the files into:
>   http://pythoncard.sourceforge.net/text/
>
> The main documentation page is:
>   http://pythoncard.sourceforge.net/toc.html
>
> The Getting Started page
> http://pythoncard.sourceforge.net/getting_started.html is awful, so that
> needs to be redone. Erik Marcus suggested that what we really need is a
> guide that walks a new user through there first fifteen minutes and then
> their first two hours with PythonCard.
>
> I would appreciate suggestions on past emails or portions of email to
> include in the documentation. Please provide the URL to past
> emails via the
> ASPN archive (you can browse and search there). For example, addmethod.txt
> file corresponds to this post in the archive:
>   http://aspn.activestate.com/ASPN/Mail/Message/770015
>
> I want to add a FAQ, mission statement (or what is PythonCard?),
> and update
> the home page and screen shot pages. It looks like we also need a page
> covering the resourceEditor with screen shots.
>
> Please provide questions, suggestions and corrections. Anyone that writes
> some documentation gets bonus points! :)
>
> Thanks,
>
> ka
>
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>

Okay, here's the first pass at a FAQ for PythonCard.

Please provide additional questions, corrections and suggestions. I'll
probably put this version up later tonight.

I used Andy's description of PythonCard.

ka
---

PythonCard FAQ (Frequently Asked Questions)

What is PythonCard?
  PythonCard is designed to be an application development framework for
use by everybody. Its purpose and goal is ease of use and increasing
productivity. From the first time to developer to the veteran coder who
knows a dozen languages, PythonCard is designed to allow you to quickly
and easily design and build fully functioning applications with a
graphical user interface.

What is the similarity between PythonCard and HyperCard?
  The PythonCard project is using HyperCard for inspiration. The first
goal is to produce a framework. We already have runtime tools
(Message Watcher, Property Editor, Shell) and a layout editor
(resourceEditor sample), but we don't have an environment yet. You can
use the resourceEditor sample to build layouts for your applications.

Have any programs been written with PythonCard?
  Yes. For a list of the samples that have been built with PythonCard
and some screenshots of them in action go to:
http://pythoncard.sourceforge.net/samples.html
A description of each sample is included in the readme.txt file in each
sample directory.

Do I need to know Python to use PythonCard?
  Yes

What do I need to use PythonCard?
  Python 2.1 or higher and wxPython 2.3.2 or higher.

What Operating Systems are supported?
  PythonCard runs on every platform that both Python and wxPython are
available for. This includes Windows 95/98/ME/NT/2000/XP, Linux GTK,
and Solaris

Where is the home page?
  http://pythoncard.sourceforge.net/

Where can I download PythonCard?
  http://sourceforge.net/project/showfiles.php?group_id=19015

Where is the mailing list?
  http://lists.sourceforge.net/lists/listinfo/pythoncard-users

Where is the CVS?
  http://sourceforge.net/cvs/?group_id=19015

I decided it was time to work on documentation again, so to get started I'm
just collecting information already on the mail list or other sources and
sticking it into text files. I plan to update the files where they are
out-of-date and then convert everything into HTML later on. Right now, I'm
concentrating on just hunting and gathering. I'm sticking the files into:
  http://pythoncard.sourceforge.net/text/

The main documentation page is:
  http://pythoncard.sourceforge.net/toc.html

The Getting Started page
http://pythoncard.sourceforge.net/getting_started.html is awful, so that
needs to be redone. Erik Marcus suggested that what we really need is a
guide that walks a new user through there first fifteen minutes and then
their first two hours with PythonCard.

I would appreciate suggestions on past emails or portions of email to
include in the documentation. Please provide the URL to past emails via the
ASPN archive (you can browse and search there). For example, addmethod.txt
file corresponds to this post in the archive:
  http://aspn.activestate.com/ASPN/Mail/Message/770015

I want to add a FAQ, mission statement (or what is PythonCard?), and update
the home page and screen shot pages. It looks like we also need a page
covering the resourceEditor with screen shots.

Please provide questions, suggestions and corrections. Anyone that writes
some documentation gets bonus points! :)

Thanks,

ka