RE: file info feature

> > An alternative would be to have the description appear as a tooltip
> instead
> > of adding a column, this would work better with the new file view.
> 
> Columns are nicer because you can sort by them and you can take
> screenshots.

Ok, columns it is (not sure how I'll do this in the directory tree view,
maybe have to add the columns back in).

Would an option to enable this information make sense? I am thinking of a
right click menu checked item like "Enable detail view".

> > I have some ideas about implementation, but I'd like to make sure that
> the
> > ideas and features are OK before going into those details.
> 
> Sounds good to me.  I suggest a file in the resource directory.  If you
> want
> to fluff up your resume you can use XML format.  Try writing a non-trivial
> amount of the file before doing any code.  Here is a starter using mailbox
> header format with commentary after pound signs:=

I was thinking to use the existing PACKET definitions for decoding files
rather than defining new ones. 
I have not looked closely as the prototypes compiler, but a requirement
would be the ability to walk through the fields of the PACKET so that the
analyzer would not have to be coded for each different packet. The comments
on each field would be used (if available) to label the contents.
Using XML is OK, is expat an OK parser, there is a python version available,
it uses the BSD license.

Simon



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click