[summerofcode] my project idea for soc

[Rahul Garg]

Hello People.
I have submitted a project idea for SOC. Your comments about it will be helpful.
I very much would like to work on this project regardless of SOC. So
if you are intersted in mentoring me about this one please let me
know! Some of the things and ideas required are especially complex and
I would be happy to receive help.
Second...i am currently doing an internship at a place where i have
python 2.3.3 installed and i dont have user permissions to install
python 2.4. the internship is till july 15. do you think my inability
to use python 2.4 till around july 20 can be a hindrance?
Rahul

Modified application (Third submission...second revised submission)

Title : Python visual object inspector

Details : 

We can make better use of dynamic nature of python as well as the
availability of tkinter in standard python distribution for a visual
object inspector. For example during debugging it will be helpful to
view an object.
Intended features:
1.The view of an object must display the class , attributes and documentation.
2.In absence of a view implementation by a class , the default
behaviour can be calling of view on attributes.
3.String representation can be included.
4.'Hyperlinks' to base classes should be provided.
5.String fields can be directly edited.
6.The view really enables visual programming to a certain extent.We
can even have a metaclass called viewable.We can register the creation
of viewable objects and can view the list of objects created so far.
So we get a complete snapshot of the program in a visual way.
7.I think some features are supported by CMUCL (a common lisp
compiler) as a grahical 'inspect' feature but i am not sure.
8.The feature must work correctly when being called from idle. In fact
this can be thought of as a idle extension project.
9.Some views to be implemented for things like list,dicts,sets and tuples.
10.View must be capable enough to understand about the features of new
style classes.

I am now modifying some of my earlier proposals:

1.I think my earlier proposal that view can also be used to build some
file viewers like html viewers is incorrect. It should focus only on
object property views etc which are helpful for programming.

2.If a registry of viewable objects is to be maintained it should
include some mechanism so that if there are no references other than
the registry it should be garbage collected.

3.Having a name field of an object will also be helpful. Knowing where
an object got created is helpful...but difficult task to implement
without the programmer having to write much extra code.