Re: [Pythonmac-SIG] on a tangent from new icons

2006-09-25 Thread Jacob Rus
Hi again everyone,

So a few months later, I started wondering again about some of
these things.

On April 22, Ronald Oussoren wrote:
  On 21-apr-2006, at 22:44, Jacob Rus wrote:
  While we're adding a bunch of icons to Mac Python, and editing
  Info.plist files, and so on, I think we might as well make a
  few other changes:
 
1. If it doesn't already, I think Mac Python should ship
  with a  python spotlight importer (I got one somewhere else,
  but should be default)
 
  For the moment anything in the official installer needs to be
  part of the official python.org distribution. Anything else
  needs to be installed seperately for now.
 
  That may change in the future, but not until I've had time to
  think about the issues and write down a proposal about what to
  include and what not.

Do you think it would be possible to get an mdimporter included in
the python.org distribution?  What's lacking for that to happen?
It would be good to have an importer for python

2. Let's export some UTI's for .pyc/.pyo files and .egg
  files (maybe public.python-bytecode and public.python-egg or
  something, or maybe they need to be org.python.python-bytecode,
  etc.)
 
  At least some of these are part of the OS. It can't hurt to add
  these UTIs to the Info.plist for IDLE of course.

So names seem to have gotten added to the plists, but never any
UTI's.  I still get dynamic UTI's for compiled python scripts and
eggs.  Regular python scripts have the content type tree:

public.python-script,
public.shell-script,
public.script,
public.source-code,
public.plain-text,
public.text,
public.data,
public.item,
public.content

I'm not sure exactly what the UTI's for eggs and pyc files should
be, but we should figure it out and add them.

In fact, because none of the applications which ship with official
python claim any ownership over eggs at all, we can't even get that
nice egg icon that took so long to get right. I'm not sure if
there's any GUI app which can deal with eggs, but it would maybe
even be good to assign them to an app which can't deal with them,
just for the sake of the icon.  :)

  Now that we (almost) have new icons it would be great if someone
  could have a look at IDLE and at the very least writes down what
  could be done to make it a better OSX citizen. Actual patches
  would of course even be better.
 
  Please keep in mind that IDLE is a cross-platform application
  using tkinter and that it is probably virtually impossible to
  make it a really great OSX application.

I'm not volunteering (and therefore not complaining), and I don't
use IDLE myself and am not likely to start any time, but this would
still be nice to see.  Anyone?

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


Re: [Pythonmac-SIG] on a tangent from new icons

2006-09-25 Thread Ronald Oussoren


On Sep 25, 2006, at 5:17 PM, Jacob Rus wrote:


Hi again everyone,

So a few months later, I started wondering again about some of
these things.

On April 22, Ronald Oussoren wrote:

On 21-apr-2006, at 22:44, Jacob Rus wrote:

While we're adding a bunch of icons to Mac Python, and editing
Info.plist files, and so on, I think we might as well make a
few other changes:

  1. If it doesn't already, I think Mac Python should ship
with a  python spotlight importer (I got one somewhere else,
but should be default)


For the moment anything in the official installer needs to be
part of the official python.org distribution. Anything else
needs to be installed seperately for now.

That may change in the future, but not until I've had time to
think about the issues and write down a proposal about what to
include and what not.


Do you think it would be possible to get an mdimporter included in
the python.org distribution?  What's lacking for that to happen?
It would be good to have an importer for python


Adding an mdimporter should be possible. What's lacking is someone  
that donates one ;-)





  2. Let's export some UTI's for .pyc/.pyo files and .egg
files (maybe public.python-bytecode and public.python-egg or
something, or maybe they need to be org.python.python-bytecode,
etc.)


At least some of these are part of the OS. It can't hurt to add
these UTIs to the Info.plist for IDLE of course.


So names seem to have gotten added to the plists, but never any
UTI's.  I still get dynamic UTI's for compiled python scripts and
eggs.  Regular python scripts have the content type tree:

public.python-script,
public.shell-script,
public.script,
public.source-code,
public.plain-text,
public.text,
public.data,
public.item,
public.content

I'm not sure exactly what the UTI's for eggs and pyc files should
be, but we should figure it out and add them.

In fact, because none of the applications which ship with official
python claim any ownership over eggs at all, we can't even get that
nice egg icon that took so long to get right. I'm not sure if
there's any GUI app which can deal with eggs, but it would maybe
even be good to assign them to an app which can't deal with them,
just for the sake of the icon.  :)


It would be better to have an application that knows how to deal with  
eggs. This is unlikely to get into the python distribution before  
setuptools is added there as well, but that's not necessarily a bad  
thing.





Now that we (almost) have new icons it would be great if someone
could have a look at IDLE and at the very least writes down what
could be done to make it a better OSX citizen. Actual patches
would of course even be better.

Please keep in mind that IDLE is a cross-platform application
using tkinter and that it is probably virtually impossible to
make it a really great OSX application.


I'm not volunteering (and therefore not complaining), and I don't
use IDLE myself and am not likely to start any time, but this would
still be nice to see.  Anyone?


IDLE in Python2.5 is probably as good as its get without major  
surgery (either port IDLE to Tix, a Tk extension claims to offer a  
better native LF, or replace the entire GUI layer by something better).


BTW. MacPython 2.4.3 is a minor fork of the official 2.4 tree, I'll  
port the changes for 2.5 except for the fixes to IDLE to the official  
2.4 tree for Python 2.4.4.


BTW2. We have a nice icon for a python folder and python DMG, neither  
of which are used at the moment. The folder one was used until I ran  
into an issue in creating the installer, that will be fixed before  
2.4.4 and 2.5.1 is out. The DMG one isn't used yet because I haven't  
found a way yet to programmaticly attach an icon to the DMG. Does  
anyone here have a script that attaches an icon to a DMG or creates a  
DMG with a custom icon? Preferably something that doesn't use 3th- 
party software and can be run GUI-less.


Ronald



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




smime.p7s
Description: S/MIME cryptographic signature
___
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig


Re: [Pythonmac-SIG] on a tangent from new icons

2006-04-22 Thread Ronald Oussoren

On 21-apr-2006, at 23:56, Tom Pollard wrote:


 I really don't care what anyone does with it.

That's not good enough of inclusion in the distribution ;-).

Ronald

P.S. I haven't looked at this yet

 Tom



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

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


Re: [Pythonmac-SIG] on a tangent from new icons

2006-04-21 Thread Donovan Preston

On Apr 21, 2006, at 1:44 PM, Jacob Rus wrote:

   1. If it doesn't already, I think Mac Python should ship with a  
 python
  spotlight importer (I got one somewhere else, but should be  
 default)

I'm +0 on this. I got the spotlight importer someone mentioned on  
this list a while back and it worked ok, but I don't really find  
spotlight to be that useful. Since there seems to be a lot of energy  
right now towards producing a complete Python install experience on  
the mac, installing it might be good. But it might need to get  
checked into the Python mainline for that to happen, which might be  
more trouble than it is worth.

Can the person who wrote the importer pipe up? How is it licensed?  
Can someone who has Python checkin rights volunteer to get it checked  
in and built by the normal build process? If not, then I think it  
should remain a separate download.

   2. Let's export some UTI's for .pyc/.pyo files and .egg files (maybe
  public.python-bytecode and public.python-egg or something, or  
 maybe
  they need to be org.python.python-bytecode, etc.)

+1

 3. Let's make sure that python files get useful kMDItemKind names.
  Right now, if I associate one with PythonIDE.app, I get plain  
 text
  file for .pyc, and Document for .pyo, which is not useful.

+1

   4. Let's add some spaces in the names of things like PythonIDE.app,
  BuildApplet.app, PythonLauncher.app and PackageManager.app.

PythonIDE and PackageManager are dead. Build Applet and Python  
Launcher seem like nice names, but I really don't care that much. +0.

 Some other questions:

* What's the difference between PythonIDE.app and IDLE.app?  Should
  they get different icons?  Is one of them preferred to the  
 other?  I
  just use TextMate and iPython from terminal, so I don't really  
 know
  what all they do.

IDLE is written in Tkinter and is cross-platform. It is maintained by  
the core Python developers. PythonIDE is written using the ancient  
Mac OS Python bindings (Toolbox, now Carbon) and hasn't really worked  
very well for about 5 years. It's going away in the next release.  
Continue to use TextMate and IPython, it's what every Python  
developer does anyway :-) (I use Aquamacs and regular python in  
Terminal)

* What exactly do python eggs do?  Are they just extra modules
  packaged up, or can you run them as standalone apps?

They are zipfiles of the kinds of things you normally see in your  
site-packages directory, either Python modules or packages. You can't  
run them.

* If the latter, how exactly do eggs differ from the applet's  
 created
  by BuildApplet.app?

BuildApplet takes the script you drop on it and puts it inside of an  
Application bundle as the main script. When you double-click the  
resulting application, it starts python and executes your main script.

* Do we want different icons for py2applet.app and BuildApplet.app?
  What exactly is the difference between these?

No idea. If there's a py2applet, it probably deprecates BuildApplet.  
I wasn't aware of this. I always just used py2app from the command  
line to build standalone Python applications, I don't see much value  
in offering drag-and-drop solutions, but I don't see the harm in  
offering them.

 Basically, I'm confused by the seemingly endless official or
 semi-official ways to package up python code and edit it on the Mac.
 Are any of these deprecated?

Yeah. Let's finally remove all the confusing deprecated crap.

dp

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


Re: [Pythonmac-SIG] on a tangent from new icons

2006-04-21 Thread Jacob Rus
Bob Ippolito wrote:
 Jacob Rus wrote:
* Do we want different icons for py2applet.app and BuildApplet.app?
  What exactly is the difference between these?
 
 BuildApplet isn't any good at creating self-contained applications.
 py2applet is.  py2app does not ship with Python.

Ok, well neither of the apps has an icon yet, but I [updated][1] some of 
the icons.  I think that the applet icon can be the default for 
applets created by BuildApplet, and the generic python app icon can be 
the default for apps created with py2app or py2applet.  How does that 
sound?  Is it possible to give py2app a default icon?

-Jacob

[1]: http://hcs.harvard.edu/~jrus/python/prettified-py-icons.png

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


Re: [Pythonmac-SIG] on a tangent from new icons

2006-04-21 Thread Bob Ippolito

On Apr 21, 2006, at 3:08 PM, Jacob Rus wrote:

 Bob Ippolito wrote:
 Jacob Rus wrote:
* Do we want different icons for py2applet.app and  
 BuildApplet.app?
  What exactly is the difference between these?

 BuildApplet isn't any good at creating self-contained applications.
 py2applet is.  py2app does not ship with Python.

 Ok, well neither of the apps has an icon yet, but I [updated][1]  
 some of
 the icons.  I think that the applet icon can be the default for
 applets created by BuildApplet, and the generic python app icon  
 can be
 the default for apps created with py2app or py2applet.  How does that
 sound?  Is it possible to give py2app a default icon?

Yes, of course we can give py2app-built apps a default icon.   
py2applet should probably have a different icon though, so it's  
distinguishable from the apps it generates.  When/if you come up with  
them, just shoot them over my way and I'll see about tossing them in!

-bob

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


Re: [Pythonmac-SIG] on a tangent from new icons

2006-04-21 Thread Bill Janssen
 http://hcs.harvard.edu/~jrus/python/prettified-py-icons.png

The egg icon looks odd to me.  I think it's that the highlights on the
logo don't seem to match the lighting direction on the egg.  Or maybe
the narrow end of the egg is just too wide.  Not sure.

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