[Pythonmac-SIG] not mac related but OLPC

2007-03-30 Thread Nehemiah Dacres
I just wanted to tell you all about the One Laptop per Child Program
in case any of you are interested in programming on a non mac and
haven't heard of this yet. It is mostly programmed in python and most
of the information is at laptop.org

-- 

"lalalalala! it's not broken because I can use it"

http://linux.slashdot.org/comments.pl?sid=194281&threshold=1&commentsort=0&mode=thread&cid=15927703
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Macintosh modules/Carbon/documentation

2007-03-30 Thread Dethe Elza
On 30-Mar-07, at 4:49 PM, Jack Jansen wrote:

> Carbon itself should be fine. It is indeed undocumented within the  
> Python documentation, but the transformation from the official  
> Apple C documentation is pretty clear (I think).

Is there anywhere that this mapping is specified?  I've always  
avoided the Mac and Carbon libraries because I had no idea where to  
begin with them, what was covered, and what I could expect to work.   
Having any kind of a starting point would be an improvement.

--Dethe


We must be careful not to build a world we don't want to live in. -- 
Stu Card


___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Macintosh modules/Carbon/documentation

2007-03-30 Thread Jack Jansen


On  30-Mar-2007, at 22:55 , Kevin Walzer wrote:

Looking at the "Macintosh Library" documentation that ships with  
2.5, I

see a lot of outdated stuff: references to the old PythonIDE,
PackageManager, and so on. What is the process for updating these  
docs,

submitting a bug report, etc.?

Also, there appears to be a lot of modules in the "Macintosh
Library"--Carbon modules, generally--that are undocumented, or are
broken, or (almost as bad) no one know if they work or not. Has anyone
gone through these to sort out what works, what should be deprecated,
etc.? Does it make sense to deprecate the entire Carbon module? What's
the process for this?



I had a chat about this with Ronald a few months ago, where we  
basically went through all the modules. Ronald,

do you have your notes handy?

Carbon itself should be fine. It is indeed undocumented within the  
Python documentation, but the transformation from the official Apple  
C documentation is pretty clear (I think).

--
Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma  
Goldman



___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


[Pythonmac-SIG] Macintosh modules/Carbon/documentation

2007-03-30 Thread Kevin Walzer
Looking at the "Macintosh Library" documentation that ships with 2.5, I 
see a lot of outdated stuff: references to the old PythonIDE, 
PackageManager, and so on. What is the process for updating these docs, 
submitting a bug report, etc.?

Also, there appears to be a lot of modules in the "Macintosh 
Library"--Carbon modules, generally--that are undocumented, or are 
broken, or (almost as bad) no one know if they work or not. Has anyone 
gone through these to sort out what works, what should be deprecated, 
etc.? Does it make sense to deprecate the entire Carbon module? What's 
the process for this?
-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] MacPython wiki "moved" to Python wiki - now it's your turn...

2007-03-30 Thread skip

Kevin> I was just looking at the new MacPython pages at the Python
Kevin> wiki--it appears nothing has been done with them since Skip moved
Kevin> them over. I'm thinking this is a terrific opportunity to bring
Kevin> them up to date: would anyone mind if I got started?  A lot of
Kevin> this stuff doesn't appear to have been touched for three or four
Kevin> years.

I say go for it.  You are correct in presuming the functional content has not
been improved.  The spammers have rediscovered it at its new home and
continue to play their silly games, but there are a group of us committed to
keeping the Python wiki cleaned up in that respect.

Skip
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] MacPython wiki "moved" to Python wiki - now it's your turn...

2007-03-30 Thread Kevin Walzer
[EMAIL PROTECTED] wrote:
> After much wailing and gnashing of teeth the past couple of days, I managed
> to move (most of?) the content from the MacPython wiki to the main Python
> wiki (*).  All pages were created as subpages of
> 
> http://wiki.python.or/moin/MacPython
> 
> The motivation for this rather hasty move was that the MacPython wiki was
> running an ancient version of MoinMoin and got spammed heavily.  Because of
> its age and vulnerability it was simply too hard to keep up with all the
> wiki spammers.  So I moved everything.
> 
> I did very little to try and fix up link references.  Moin's subpage
> references have always befuddled me, and many of the page references were
> weirded out to begin with, so there you have it: royal link spaghetti.
> 
> This is where you come in.  You can do any number of things to try to
> identify and fix problems:
> 
> * Visit http://wiki.python.org/moin/OrphanedPages and see if there are
>   any MacPython/... pages which are orphaned (hint: there are quite a
>   few).  Then see if you can find an incorrect link which should refer
>   to the orphaned page.
> 
> * Visit the MacPython pages.  Just do a title search for "MacPython" to
>   locate them.  Visit and clean up as appropriate.
> 
> * Everything got pushed down, even home pages.  One of three things can
>   reasonably be done:
>   1. Move a home page up if there isn't one at the top level.
>   2. Replace an uplevel home page with the MacPython version if the
>  latter is "better".
>   3. Merge the content from the MacPython version into the uplevel home
>  page.
>   Instead of performing #2 and #3 yourself, you might send an email to
>   the person and ask them to do the merge/replace.  In any case, this
>   operation is likely to require some link fiddling.
> 
> * There may also be non-homepage pages at the top level which should be
>   merged with or replaced by (or replace) the MacPython version.
>   VisualPython comes to mind.  Use your judgement
> 
> * There are lots of unprotected path references in the content,
>   e.g. /System/Library sitting there looking like a link when it should
>   probably be {{{/System/Library}}}.
> 
> * There may still be a bit of spam lurking in the pages.  I tried to
>   eliminate all the crap, but I might have missed some.
> 
> * Many pages could use Category references.  There are lots of pages
>   referring to scripting specific Mac applications, home pages and many
>   code samples.  Adding CategoryMac or CategoryAppScript might be
>   reasonable as well.
> 
> * Use your WikiImagination.  There are probably lots of other things
>   that can be done.  I think the MacPython wiki had fallen into a bit of
>   disrepair, even if you ignore the spam problem, so a little general
>   TLC would probably help.
> 
> Skip
> 
> (*) Thank goodness for Emacs and Mozex...
> ___
> Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig
> 
> 

I was just looking at the new MacPython pages at the Python wiki--it 
appears nothing has been done with them since Skip moved them over. I'm 
thinking this is a terrific opportunity to bring them up to date: would 
anyone mind if I got started? A lot of this stuff doesn't appear to have 
been touched for three or four years.

Any thoughts about what is most pressing? I have my own interests, and 
I'm not qualified to edit everything, but I'm open to suggestions.

-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac

2007-03-30 Thread Uche Ogbuji
Jan Erik Moström wrote:
> Reply to has <[EMAIL PROTECTED]> 07-03-30 12:30:
>
>   
>> Not sure it's what you're looking for, but are you aware of 
>> MoinX  (http://moinx.antbear.org)? It's a Twisted-based wiki 
>> packaged as a  standalone OS X app. Source is also available.
>> 
>
> Yep, but from what I understand it's would be the same as I set 
> up any wiki on my laptop, Which means that my laptop would need 
> to have connected to the net for allowing access from other computers.
>   

I'm not sure I really understand what you're after, but I'll throw in
TiddlyWiki.  It's a JavaScript tool, but you could use Python to tack on
features in any number of ways.  Important point is that it's all
in-browser, and designed so you can publish all in one file, so makes it
very easy to use it online+offline.

http://www.tiddlywiki.com/

--Uche

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac

2007-03-30 Thread Jan Erik Moström
Reply to has <[EMAIL PROTECTED]> 07-03-30 12:30:

>Not sure it's what you're looking for, but are you aware of 
>MoinX  (http://moinx.antbear.org)? It's a Twisted-based wiki 
>packaged as a  standalone OS X app. Source is also available.

Yep, but from what I understand it's would be the same as I set 
up any wiki on my laptop, Which means that my laptop would need 
to have connected to the net for allowing access from other computers.

Unless I've misunderstood anything.

 jem
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac

2007-03-30 Thread has
Jan Erik Moström wrote:

> personally what I've been missing is a wiki that can be used both  
> off-line locally and on-line on a server.

Not sure it's what you're looking for, but are you aware of MoinX  
(http://moinx.antbear.org)? It's a Twisted-based wiki packaged as a  
standalone OS X app. Source is also available.

The OP also reminded me of Phlink Web Access (http://jctcode.com/ 
phwa), which also does the web-app-as-standalone-desktop-app thing.  
Though PWA's slightly different as it's provides a remote web-based  
interface for controlling a local GUI process (Ovolab Phlink),  
whereas DjangoKit seems more about presenting a web interface as a  
local GUI process. But perhaps there's potential to go beyond that too.

Interesting times,

has
-- 
http://appscript.sourceforge.net
http://rb-appscript.rubyforge.org
http://appscript.sourceforge.net/objc-appscript.html

___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] Interesting use of Python and Django on the Mac

2007-03-30 Thread Jan Erik Moström
Reply to Tom Weir <[EMAIL PROTECTED]> 07-03-29 14:40:

>What I would love to see is a Python framework that integrates 
>with  Django, enables PyObjC apps to use Django models for data 
>storage,  with sync to a remote DB . I.e. the data is stored 
>both locally and  remotely, with sync between the two. Having 
>the webapp UI would be  useful for many applications, but I 
>think a native UI would have  advantages too.

Yep, personally what I've been missing is a wiki that can be 
used both off-line locally and on-line on a server. I've been 
thinking along these lines for the last 6 months or so but 
unfortunately haven't had any time to play with the idea.

So I would really welcome a model where I would use a Python 
framework for building an app on server and be able to build a 
native client to access and sync the same data.

 jem
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig