/[drupal]/contributions/modules/hierarchical_select/API.txt
ViewVC logotype

Diff of /contributions/modules/hierarchical_select/API.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph | View Patch Patch

revision 1.55, Sun Oct 5 15:51:43 2008 UTC revision 1.56, Mon Dec 1 02:21:17 2008 UTC
# Line 1  Line 1 
1  $Id: API.txt,v 1.54 2008/10/05 14:21:05 wimleers Exp $  $Id: API.txt,v 1.55 2008/10/05 15:51:43 wimleers Exp $
2    
3  Terminology  Terminology
4  -----------  -----------
# Line 270  Hierarchical Select implementations: got Line 270  Hierarchical Select implementations: got
270    some magic, and AJAX updates won't work.    some magic, and AJAX updates won't work.
271    
272    
273    Why Hierarchical Select can't take advantage of Drupal 6 Form API
274    -----------------------------------------------------------------
275    There are two main things that make Hierarchical Select's FAPI code very
276    complex. But for neither one I can take advantage of Drupal 6's FAPI
277    improvements.
278    1) Hierarchical Select has its own "light" form cache (only a unique id, the
279       form_id and the parameters that are passed to the form definition function)
280       to make AJAX updates possible (in an AJAX callback only the Hierarchical
281       Select should be re-rendered and returned).
282       One would think he can use Drupal 6's shiny $form_state. But one would be
283       wrong, because Views (the exposed filters form) support is a necessity. And
284       that particular form doesn't work when $form['#cache'] is set.
285    2) add child form items based on the user's input
286    
287    
288  Hooks  Hooks
289  -----  -----
290  1) hook_hierarchical_select_params();  1) hook_hierarchical_select_params();
Legend:
Removed from v.1.55  
changed lines
  Added in v.1.56
  ViewVC Help
Powered by ViewVC 1.1.2