Menu
▾
▴
phpwiki-talk
|
From: Peter <li...@gm...> - 2003-12-17 13:53:28
|
Hi,
I would like to have a set of special pages on top of all pages. I do
it with copying that "header" to all wiki pages. Obviously this is not
very good, because if I want to change that "menu", I must touch every
single page I used it...
Is there a better way to get some kind of include("menu") on every
wikipage??? The menu-pages are wikipages themselves.
Thank you very much for your attention!
|
|
From: Norberto M. <nu...@me...> - 2003-12-17 14:29:41
|
Hi Peter,
why not use templates? start off the default template and edit @ will.
making the menu part of the content of each wiki page is definitely the
wrong way to go about it.
maybe there is a 'menu' plugin that can create this on parsing? or maybe
an include plugin (not sure, haven't reviewed all the plugins available yet
Beto
Peter wrote:
>Hi,
>
>I would like to have a set of special pages on top of all pages. I do
>it with copying that "header" to all wiki pages. Obviously this is not
>very good, because if I want to change that "menu", I must touch every
>single page I used it...
>
>Is there a better way to get some kind of include("menu") on every
>wikipage??? The menu-pages are wikipages themselves.
>
>
>Thank you very much for your attention!
>
>
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
>Free Linux Tutorials. Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
>_______________________________________________
>Phpwiki-talk mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwiki-talk
>
>
>
--
Norberto Meijome | numard at meijome dot net
"Everything is interesting if you go into it deeply enough." - Richard Feynman
|
|
From: Carsten K. <car...@us...> - 2003-12-17 20:16:48
|
Peter wrote:
> Hi,
>
> I would like to have a set of special pages on top of all pages. I do
> it with copying that "header" to all wiki pages. Obviously this is not
> very good, because if I want to change that "menu", I must touch every
> single page I used it...
>
> Is there a better way to get some kind of include("menu") on every
> wikipage??? The menu-pages are wikipages themselves.
>
>
> Thank you very much for your attention!
On Wednesday, December 17, 2003, at 09:29 am, Norberto Meijome wrote:
> Hi Peter,
> why not use templates? start off the default template and edit @ will.
>
> making the menu part of the content of each wiki page is definitely
> the wrong way to go about it.
>
> maybe there is a 'menu' plugin that can create this on parsing? or
> maybe an include plugin (not sure, haven't reviewed all the plugins
> available yet
>
> Beto
Yes templates would be the best approach. Add a line into
phpwiki/themes/default/templates/top.tmpl to call your menu template:
diff -U2 -r1.25 top.tmpl
--- top.tmpl 5 Mar 2003 21:38:15 -0000 1.25
+++ top.tmpl 17 Dec 2003 20:09:13 -0000
@@ -14,4 +14,5 @@
<!-- The top navigation/search bar -->
<div class="toolbar"><?= Template('navbar') ?></div>
+<div class="toolbar"><?= Template('menu') ?></div>
<?php } ?>
Then create a new file menu.tmpl, put your html and php in there,
something like this:
<?php // -*-html-*-
$s = $Theme->getButtonSeparator();
?>
<!-- The menu bar -->
<?= WikiLink(_("RecentEdits"), "button") ?>
<?=$s?><?= WikiLink(_("MyPage"), "button") ?>
<?=$s?><?= WikiLink(_("AnotherPage"), "button") ?>
<!-- End menu bar -->
Carsten
|
|
From: russ <rl...@rl...> - 2003-12-17 20:55:55
|
I'm not actually a newbie, but I'm afeared this question is. I've been following and using PHPWiki for years; I spent a long time hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few installations, and I'm sure some customization and tweaking will follow. This time, however, I want to do it right. I want to be able to upgrade as the product changes. I want to be able to isolate and save my changes. I want the option of submitting my work back to the project. However, I'm not 100% sure how to go about it. I looked into the inner workings of diff and patch a bit months ago. Is that the place to start? Does anyone have a pointer to a good reference for someone who is not a necessarily a coding newbie but is a project newbie? How about my own code? Should I use source control for that? Any other best practices I should look into? Sorry if this is ramantly off-topic (can't be worse than the administrivia reply-to thread :), but any pointers (reply-to just me is fine, too :) would be much appreciated. russ |
|
From: Carsten K. <car...@us...> - 2003-12-17 21:46:15
|
On Wednesday, December 17, 2003, at 03:55 pm, russ wrote: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will > follow. This time, however, I want to do it right. I want to be able > to upgrade as the product changes. I want to be able to isolate and > save my changes. I want the option of submitting my work back to the > project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to > start? Does anyone have a pointer to a good reference for someone who > is not a necessarily a coding newbie but is a project newbie? How > about my own code? Should I use source control for that? Any other > best practices I should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me > is fine, too :) would be much appreciated. > > russ Hi Russ, I think the best way to keep your PhpWikis absolutely up-to-date is through CVS. Learning diff and patch is a very good place to start. Next, learn the basics of CVS: how to check out a project, how to do diffs with CVS, how to update files to the latest revisions from the server, and how to resolve conflicts between modifications of your personal copy with similar changes newly added to the copy on the server. (Hopefully conflicts don't happen too often but they are usually pretty easy to fix with a text editor). Even when you make modifications to your local files, CVS can keep your files up-to-date by automatically merging your own changes with any changes in the code published/checked in at the SF server, using built-in diff and patch functions. If there is a conflict between your mods and a new change on the server, cvs will tell you where the conflict is. Say you don't always want to run "cvs -q up" etc. every day to keep your PhpWiki code *absolutely* current, that's fine too (and probably a good idea on a production PhpWiki). In that case CVS is still handy for doing things like: "cvs diff index.php". Then cvs will display a patch which shows how your copy of that file differs from that particular revision of the same file on the SF server. Sourceforge has some O.K. docs about how to use CVS. It's been a while since I first learned CVS, does anyone have a link to a good CVS getting started tutorial? Carsten |
|
From: Joby W. <joby@u.washington.edu> - 2003-12-17 22:36:43
|
The Sourceforge documents are pretty good, and an easy read. The Cederqvist (CVS Offical Manual) is a bit dense but very informative for an end user. http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs.html jbw Carsten Klapp wrote: > > On Wednesday, December 17, 2003, at 03:55 pm, russ wrote: > >> I'm not actually a newbie, but I'm afeared this question is. >> >> I've been following and using PHPWiki for years; I spent a long time >> hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few >> installations, and I'm sure some customization and tweaking will >> follow. This time, however, I want to do it right. I want to be able >> to upgrade as the product changes. I want to be able to isolate and >> save my changes. I want the option of submitting my work back to the >> project. >> >> However, I'm not 100% sure how to go about it. I looked into the inner >> workings of diff and patch a bit months ago. Is that the place to >> start? Does anyone have a pointer to a good reference for someone who >> is not a necessarily a coding newbie but is a project newbie? How >> about my own code? Should I use source control for that? Any other >> best practices I should look into? >> >> Sorry if this is ramantly off-topic (can't be worse than the >> administrivia reply-to thread :), but any pointers (reply-to just me >> is fine, too :) would be much appreciated. >> >> russ > > > Hi Russ, > > I think the best way to keep your PhpWikis absolutely up-to-date is > through CVS. > > Learning diff and patch is a very good place to start. Next, learn the > basics of CVS: how to check out a project, how to do diffs with CVS, how > to update files to the latest revisions from the server, and how to > resolve conflicts between modifications of your personal copy with > similar changes newly added to the copy on the server. (Hopefully > conflicts don't happen too often but they are usually pretty easy to fix > with a text editor). > > Even when you make modifications to your local files, CVS can keep your > files up-to-date by automatically merging your own changes with any > changes in the code published/checked in at the SF server, using > built-in diff and patch functions. If there is a conflict between your > mods and a new change on the server, cvs will tell you where the > conflict is. > > Say you don't always want to run "cvs -q up" etc. every day to keep your > PhpWiki code *absolutely* current, that's fine too (and probably a good > idea on a production PhpWiki). In that case CVS is still handy for doing > things like: "cvs diff index.php". Then cvs will display a patch which > shows how your copy of that file differs from that particular revision > of the same file on the SF server. > > Sourceforge has some O.K. docs about how to use CVS. It's been a while > since I first learned CVS, does anyone have a link to a good CVS getting > started tutorial? > > Carsten > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
|
From: Peter <li...@gm...> - 2003-12-18 12:08:03
|
Hi, please one cvs-question that I never got answered anywhere:=20 HOW can i see which modules do exist on a cvs-server after login?=20 Is there something like "cvs list modules" i did not find anything about that... sorry for ot, but i take the chance to jump on that basic-project-info-thread... Thanks for your attention! Peter |
|
From: Norberto M. <nu...@me...> - 2003-12-18 12:32:18
|
Hi Peter et al, [quickly moving the off topic discussion somewhere else]... http://www.cvshome.org is the home of CVS. Please refer to the extensive documentation found there. Cheers, Beto Peter wrote: >Hi, > >please one cvs-question that I never got answered anywhere: > >HOW can i see which modules do exist on a cvs-server after login? > >Is there something like "cvs list modules" > >i did not find anything about that... > >sorry for ot, but i take the chance to jump on that >basic-project-info-thread... > >Thanks for your attention! > >Peter > > >------------------------------------------------------- >This SF.net email is sponsored by: IBM Linux Tutorials. >Become an expert in LINUX or just sharpen your skills. Sign up for IBM's >Free Linux Tutorials. Learn everything from the bash shell to sys admin. >Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click >_______________________________________________ >Phpwiki-talk mailing list >Php...@li... >https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > -- Norberto Meijome | numard at meijome dot net "Everything is interesting if you go into it deeply enough." - Richard Feynman |
|
From: Reini U. <ru...@x-...> - 2003-12-18 00:05:31
|
method 1: # remark: always diff old to new # but you want your changes from 1.2 back into cvs...: diff -rbu phpwiki-cvs phpwiki-1.2 > phpwiki-1.2.patch # now you can apply the patches blindly cd phpwiki-cvs; patch -p1 < phpwiki-1.2.patch method 2: or better check the patch file in a editor which can do diff's, such as XEmacs or emacs: C-x 2 M-x ediff-buffers split the window, load the patch and file-wise both files. and see what's different. you can also apply the diff's, but manually. that's preferred ,but needs more time. russ schrieb: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will follow. > This time, however, I want to do it right. I want to be able to upgrade > as the product changes. I want to be able to isolate and save my > changes. I want the option of submitting my work back to the project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to start? > Does anyone have a pointer to a good reference for someone who is not a > necessarily a coding newbie but is a project newbie? How about my own > code? Should I use source control for that? Any other best practices I > should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me is > fine, too :) would be much appreciated. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
|
From: Steve W. <sw...@pa...> - 2003-12-20 14:03:22
|
Time and again, I turn to the Red Bean book, free and online: http://cvsbook.red-bean.com/cvsbook.html It's a great combination of tutorial and cookbook. ~swain On Dec 17, 2003, at 3:55 PM, russ wrote: > I'm not actually a newbie, but I'm afeared this question is. > > I've been following and using PHPWiki for years; I spent a long time > hacking up 1.2.* for personal use. I'm eagerly awaiting 1.4 for a few > installations, and I'm sure some customization and tweaking will > follow. This time, however, I want to do it right. I want to be able > to upgrade as the product changes. I want to be able to isolate and > save my changes. I want the option of submitting my work back to the > project. > > However, I'm not 100% sure how to go about it. I looked into the inner > workings of diff and patch a bit months ago. Is that the place to > start? Does anyone have a pointer to a good reference for someone who > is not a necessarily a coding newbie but is a project newbie? How > about my own code? Should I use source control for that? Any other > best practices I should look into? > > Sorry if this is ramantly off-topic (can't be worse than the > administrivia reply-to thread :), but any pointers (reply-to just me > is fine, too :) would be much appreciated. > > russ > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
|
From: Arnaud F. <ar...@cr...> - 2003-12-18 07:41:20
|
Right, Templates would be the best. But you can do something more ...
wiki driven :)
Le mer 17/12/2003 =E0 21:16, Carsten Klapp a =E9crit :
> Yes templates would be the best approach. Add a line into=20
> phpwiki/themes/default/templates/top.tmpl to call your menu template:
[...]
> <?php // -*-html-*-
> $s =3D $Theme->getButtonSeparator();
> ?>
> <!-- The menu bar -->
> <?=3D WikiLink(_("RecentEdits"), "button") ?>
> <?=3D$s?><?=3D WikiLink(_("MyPage"), "button") ?>
> <?=3D$s?><?=3D WikiLink(_("AnotherPage"), "button") ?>
> <!-- End menu bar -->
Here, just define the "hard links" to some pages like the RecenChanges,
FindPage, etc.
And add a line like this one to your template :
<?plugin IncludePage page=3D"Menu" quiet=3D1?>
Then, create a wiki page named Menu where you'll just write the
Wikiwords and links you want to have in your menu.
Then you're free to lock the Menu page or not ....
I use this trick to add a "News" box on my wikis. News are taken from
the "!News" section of a wiki page.
--=20
Arnaud Fontaine
Jabber: sh...@ra...
ICQ: 3504789
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X