Advertisement
Juc1

Fubhy talking about Panels vs Context Module

Dec 6th, 2013
122
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.13 KB | None | 0 0
  1. http://www.youtube.com/watch?v=CmTuvzbPduI
  2.  
  3. (about 2hrs 5)
  4.  
  5. The context module is conceptually problematic – biggest use was to place blocks using hook_page_alter – but this is not the right hook (should be block_list_alter); very slow (blindly executes context rules on every page = overhead), conceptually wrong.
  6.  
  7. ================================
  8.  
  9. irc #drupal-omega
  10.  
  11.  
  12. [21:45] <b0x> fubhy: so you _always_ use panels?
  13. [21:45] <fubhy> yes
  14. [21:45] <fubhy> always
  15. [21:45] <b0x> doesnt it have a fairly large overhead
  16. [21:45] <fubhy> panels, panels everywhere
  17. [21:45] <b0x> compared to standard layouts
  18. [21:45] <fubhy> no
  19. [21:45] <fubhy> context has a crazy overhead
  20. [21:45] <fubhy> context module is slow as f**k
  21. [21:45] <b0x> yah
  22. [21:45] <Guest77213> lol
  23. [21:45] <fubhy> panels has pretty good caching
  24. [21:46] <fubhy> if you configure it, even better so
  25. [21:46] <fubhy> and, let's be honest, the fact that context module is named context moduile can only be a bad joke
  26. [21:46] <fubhy> because... it has no clue about contexts
  27. [21:46] <b0x> hehe
  28. [21:47] <fubhy> while with panels you can manage contexts in quite complex ways
  29. [21:47] <fubhy> and forward them to other stuff
  30. [21:47] <fubhy> like views contextual filters
  31. [21:47] <fubhy> or the token system
  32. [21:47] <b0x> so you dont actually need context
  33. [21:47] <b0x> but can make context based changes, using panels alone
  34. [21:48] <b0x> or..?
  35. [21:48] <fubhy> i don't use context
  36. [21:48] <fubhy> i dont' use the block module
  37. [21:48] <fubhy> block module == one of the first things i uninstall on a new site
  38. [21:48] <b0x> thats interesting
  39. [21:48] <b0x> though panels would take over that functionality
  40. [21:48] <b0x> so makes sense
  41. [21:49] <fubhy> yes
  42. [21:49] <fubhy> panels takes over that functionality
  43. [21:49] <fubhy> and more
  44.  
  45.  
  46. ---------------------------------
  47.  
  48. <fubhy> if you want to have different regions than what's defined in the .info file of the base theme you have to add them in your own theme's .info file
  49. <fubhy> otherwise they are inherited
  50. <apacheQTJ> fubhy: ok thanks - but I think if you are using panels / panels everywhere then the theme's regions can be irrelevant?
  51. <fubhy> yes
  52. <fubhy> definitely
  53. <fubhy> and that's what i do too
  54. <apacheQTJ> ok thanks
  55.  
  56. -------------------------
  57.  
  58. <monk_> I think fubhy has it setup where he does EVERYTHING in code except for contexts, content etc
  59. <monk_> correct me if not accurate
  60. <fubhy> yes thats correct
  61. <apacheQTJ> monk_: you mean that panels layout can be in code or in database and code is better?
  62. <monk_> yea, you can have code/ files that define panels layout
  63. <apacheQTJ> fubhy: I think you don't use panels layout designer = http://i.imgur.com/07zYpIz.png because it goes in the database?
  64. <monk_> custom layouts actually defined in tpl and scss
  65. <fubhy> yes
  66. <fubhy> flexibuilder layouts are crap
  67. <fubhy> avoid at all cost
  68.  
  69. ------------
  70.  
  71. [15:51:00] <fubhy> create your own panels layouts
  72. [15:51:04] <fubhy> no need to hack existing ones
  73. [15:51:08] <fubhy> it's fairly simple to create custom layouts
  74. [15:51:12] <fubhy> and if you want clean markup
  75. [15:51:17] <fubhy> stay far far away from the panels provided ones
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement