Hi!
The 'plugin' view usually only is set when a plugin uses the "external_plugin" event hook. Seldom plugins use this to take over "page control"; typical external_plugins are the blogpdf plugin or the RSS aggregator or popfetcher.
I'd agree that creating a verbose list of that would be fine. I think everybody could create that list, since the index.php is virtually all you need to check where the view is set. I think this is also a great task for someone who wants to gain some insight into Serendipity, or a great task for someone looking to contribute to Serendipity?
There is little point providing the $view variable if we don't also have some standards on how its applied so that template designers or users who want to modify a template know exactly what each view is supposed to do.
I fully agree, standards need to be made. Serendipity only provides the basic facility, IMHO its up to template creators to deploy "best usage" scenarios that can then be documented? I'd really like for the people needing to work with standards to define those standards bottom-up, instead of dicating them top-to-bottom. Carl, you and Costa and Hippo and others already seem to get a good grasp of this, so maybe you'd all together like to create some kind of "task force"? I understand you are extremely busy, so I hope that others will join in on your efforts?
Surely results like Hemingway or Costas recent template show much much benefit there will be.
Timbalu's new guestbook seems to set $view as startpage but I can't find anything in the sourcecode that does this, and startpage is NOT the appropriate view for it to be setting.
I agree. Maybe since we also discussed this recently, a good view would be "plugin_content" or something like that? We can freely use that, as far as I know no plugin makes use of setting $view until now.
HTH,
Garvin