I have most nodelets switched off for faster surfing, but every once in a while, I'd like to see the contents of a nodelet that I have switched off (e.g. "Other users"). However, it's too much of a hassle to go and switch it on, view it, then switch it off, so most of the time I just don't bother.
How about creating a special page that just shows the contents of all nodelets, maybe even in a different (wider) format? Something not quite like all nodelets ;-) |
Re: Page showing all nodelets?
by Corion (Patriarch) on Apr 07, 2003 at 07:20 UTC
|
As I mainly surf Perlmonks via the Newest Nodes, I did set up The Monastery Gates as my alternative node page, as I can select the nodelets displayed there differently from the nodelets displayed otherwise. The poll nodelet for example lives only on the Monastery Gates node, as it isn't necessary for my daily PM habit.
perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The
$d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider
($c = $d->accept())->get_request(); $c->send_response( new #in the
HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web
| [reply]
[d/l] |
|
|
| [reply] |
Re: Page showing all nodelets?
by VSarkiss (Monsignor) on Apr 06, 2003 at 23:31 UTC
|
You could do that, partially, for some nodelets. As I write this, there are 57 nodelets defined, but not all of them are "in use", and some of them can only be accessed by particular groups, such as editors or gods. Some nodelets are also "context sensitive", in that their content changes based on the main node being displayed (like Approval Nodelet).
It would be difficult to change them so they displayed as body nodes rather than nodelets, though. An All nodelets page would still have them down the side.
Other than that, I think it's doable. (This after thinking about it for all of a couple minutes. ;-) If enough people think it'd be useful, it's a matter of talking someone in pmdev to cook up the page, and talking one of the gods into installing it.
| [reply] |
|
|
| [reply] |
|
|
Oh, OK. I'm still a little fuzzy on the details of how display pages, containers, and nodetypes relate: I thought a nodelet would alway use the same container, so you would have to set up a new document-type node with a duplicate of the nodelet's logic.
So if I understand you correctly, you would set up a new node with a main container (possibly a new type of container) and put the nodelets in that?
Maybe I should go read your documents again. ;-)
| [reply] |
Re: Page showing all nodelets?
by JayBonci (Curate) on Apr 07, 2003 at 08:55 UTC
|
all nodelets is a system default nodeletgroup. There are many nodelets; some are what you see, some are used for development purposes, and some are used for the timed-update feature of nodelets as a poor-man's cron job. The nodeletgroup that the system uses to define what you can pick from is: sidebar nodelets. Typically nodeletgroups are set up to restrict what a user can choose between, but clever users may be able to jimmy unauthorized nodelets (such as old admin nodelet) into their VARS.
In ecore 1.0 currently in CVS, you need execute permission to be able to add in a nodelet. (I think. I could be wrong)
--jaybonci
| [reply] |
Re: Page showing all nodelets?
by Louis_Wu (Chaplain) on Apr 08, 2003 at 05:41 UTC
|
I keep Nodelet Nodelet active, so that I can add any nodelet at any time - all you do is pick from the drop-down box.
And if you want a description of a nodelet, you could check out the FAQ - What are Nodelets?.
And there is always the wonderful Nodelet Settings, which lets you select and order all of your nodelets in one fell swoop. Thanks tye.
Perl programming and scheduling in the corporate world, as explained by dragonchild:
"Uhh ... that'll take me three weeks, broken down as follows: 1 day for coding, the rest for meetings to explain why I only need 1 day for coding."
| [reply] |
|
|
