[WWdevel] [WWdevel]: Library Browser (SetMaker) question: "combining up"

[Michael G. <ga...@ma...>]

Thanks Davide and John.

I've got it.  Thanks.  I'm happy with the "Main problems" label, but  
I was puzzled that they were not toplevel problems.
  I guess I was paying attention when this improvement came through  
last September, so I was a bit
puzzled by the behavior.

Privately (but not formally) I had used the convention that when  
constructing a directory contaning a
.pg file and auxiliary files   that the  directory name was related  
to the .pg name   e.g.  prob1/prob1.pg

Would it be reasonable to add that condition to the default method  
for "combining up"?  I know the rules
I used for making these problems, but I haven't searched through the  
rest of the problem collections, so perhaps
there are reasons not to do this.

Take care,

Mike


On Aug 31, 2005, at 8:20 AM, Davide P. Cervone wrote:

>> With the extra  buttons like Rochester Library, there is the same  
>> sort of question: how should the top level directory within the  
>> Rochester Library appear in the list of directories.  They aren't  
>> "My Problems" since by design, one probably doesn't have write  
>> access to them.  So, I guess Davide called them Main Problems,  
>> probably because it is hard thinking of a good name for them.
>>
>
> Yes, that was the problem.  I still can't think of a better name,  
> can anyone else?  "Toplevel Problems"?  "Unclassified Problems"?
>
>
>> There is a way to turn off the "combine a directory up" feature  
>> for an individual directory.  If the standard Rochester library  
>> has single problem directories at its top level, then you might  
>> want to include the required file in those directories so they  
>> don't get promoted to Main Problems.
>>
>
> The CVS log entry for version 1.26 of SetMaker.pm explains the  
> method for doing this, in case anyone wants to give SetMaker these  
> extra hints about how to show their library's problems.
>
> Davide
>
>

This patch modified the Library Browser so that these single-pg-file
directories are merged with their parents, as long as they also
include other non-pg-files.

It also provides a method of controling the library browser on a
directory-by-directory basis using specially named files.  If a
directory contains a file named "=library-ignore", then the directory
is never shown in the directory menu.  If it contains a file called
"=library-combine-up", then its contents are considered to be part of
the parent directory, even if it has more than one pg file.  If it
contains one called "=library-no-combine", then the directory is
always listed separately in the menu, even if it has only one pg file.