[ww-devel] webwork-devel Digest, Vol 41, Issue 1

[Peter Staab]

I was thinking of just some javascript in the compound Problem PG macro, so this could satisfy you.  Currently there’s a bit of javascript there to open/close the individual sections and my thought was to react to those open/close events and show/hide the appropriate rows in the table.  

I think this wouldn’t be too hard to do if the row in Problem.pm encoded the answer name in a data attribute, like “data-answer=AnSwEr0001” for example, then when a section is open, the inputs in that section could be determined and the rows shown.  

I’d be happy to try such a solution, but am willing to see what Davide comes up with too. 

Peter
On Aug 12, 2014, at 4:08 PM, Geoff Goehle <goehle at gmail.com> wrote:

> I don't know how Davide is implementing the "dimming" rows, but I'm a
> little wary of things that require Problem.pm and PG.pm to work in
> concert.  Especially when it depends on a particular problem library.
> This is mainly because the idea is still that PG will operate pretty
> much independently of the thing calling it.  Is there anything that
> could be done only (or almost entirely) on the PG side.  I was thinking
> that PG could just not provide answer hash data for parts of the problem
> that are not available.  This way Problem.pm would print a shorter table
> just as a matter of course.  (The problem could still provide the total
> status for all of the sections, of course.)  
> 
> Geoff.
> 
> _______________________________________________
> webwork-devel mailing list
> webwork-devel at webwork.maa.org
> http://webwork.maa.org/mailman/listinfo/webwork-devel