Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.2

Request #4647 collapsible reverseLinks
Submitted: 2005-06-20 18:35 UTC Modified: 2006-12-16 02:17 UTC
From: andrew dot clark at ucsb dot edu Assigned: justinpatrin
Status: Closed Package: DB_DataObject_FormBuilder
PHP Version: 4.3.11 OS: FreeBSD 4
Roadmaps: (Not assigned)    

 [2005-06-20 18:35 UTC] andrew dot clark at ucsb dot edu
Description: ------------ I'd like reverseLinks, and generically any suitable link element, to honor the collapse flag, and have the ability to spawn a LinkNewValue subform.


 [2005-06-20 19:00 UTC] justinpatrin
I could see making reverseLinks collapseable (currently this would mean making it a table, though). As for linkNewValue for other field types, that's more complicated. It works fine with links because of how they simply are. It *could* be possible to do the same thing (with a link like the 'collapse' link) for crossLinks and reverseLinks, but remember, all of these features in FormBuilder are "static". By static I mean that they are processed and created server-side every time you access the page. For linkNewValue a form for the new record is created every time you access the page, whether or not you use it. This adds extra processing time to the page generation. The reason that these things are this way is because FormBuilder is a component which has to be usable from anywhere. Basically this means that it can't rely on outside scripts to handle popups or JavaScript requests. That said These sound like ok options (and I have, indeed, implemented it for crossLinks elsewhere with my SubForm element) but it may take a little bit to get them added. I've had very little time lately for development and have been trying to get unit tests done.
 [2005-08-23 00:36 UTC] justinpatrin
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. That was much easier than I thought. I'm glad I wrote that JavaScript genric. :-)