I understand now ... I think sorting by type and __then__ by id is a normal thing to do. At least, it is something I expect to be able to do easily in the shell. I think LocalFS, which (IMO) is Zope's extension of "ls" should be able to do the same. The Product is modifiable, if given sufficient foresight, and logical default values. Keith J. Farmer wrote:
Code is best when it's not a hack.
The normal default directory browsing mixes files and subdirectories. While you can sort by type and id, this isn't a particularly enthralling solution. For example, if you just want directories gathered at the top of the list, but don't want files sorted any further than id.
Also, if you give a spec of '*.jpg', this will exclude directories (which have a spec of '*/' or '*\').
Internally, LocalFS will place directories at the top, if they are included in the spec. This, however, leads to boring and stupid urls while browsing (always having to include '*/').
I could use tpValues(), but that doesn't deal with the spec, which LocalFS appends internally to the url variable for directories (that it adds this spec information without asking is a coding mistake, imho).
.. hmm.. perhaps I should remove that mistake, rewrite methodBrowse to explicitly add spec as needed, and have done with it?
As I said.. code is best when it's not a hack. Code is best when it allows modification without hackification.
---------- Keith J. Farmer kfarmer@thuban.org http://www.thuban.org
-----Original Message----- From: John Ziniti [mailto:jziniti@speakeasy.org] Sent: Tuesday, January 15, 2002 21:23
I mess around a lot with LocalFS .. but I'm not sure what you mean by "direcotories alwys at top ..." etc ...can you clarify a little bit about what you are
trying to do?
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )