create new tag
, view all tags

Archive of QuickMenuSkinDev

Nice looking skin, thanks for contributing!

I have taken the liberty of adding the skin to SVN, this makes it easier for developers running a SVN install to try it out.

(That the skin is now in SVN doesn't mean future updates have to be done in SVN - but if you would like to, you can visit PluginsInSubversion to get started).

Can the menu have expandable items (sub-levels)?

-- SteffenPoulsen - 13 Jun 2006

That looks nice! Thanks Vernon for sharing your skin with the TWikiCommunity!

-- PeterThoeny - 13 Jun 2006

Yes the menu can have sub menus, I'll be adding some more docs to the package shortly. I'll be looking into SVN too, not sure what that is yet.

-- VernonLyon - 14 Jun 2006

This looks good.

A quick menu... this could be used with any skin... so I'd say this is different to a skin.

What category does this fit into? If there is no category does TWiki need a new one?

-- MartinCleaver - 15 Jun 2006

I would say a SkinAddOn.

Because the main contribution is the menu bar, so there would need to be only a couple of files to bring this functionality.

-- ArthurClemens - 15 Jun 2006

There are a few problems: the templates call javascript functions that are defined in pattern skin templates and scripts. But because pattern skin is not required, the functions do not work (do not get called) (example: the text area buttons in edit).

The conditional IF context TwistyPluginEnabled can be removed from twiki.quickmenu.tmpl, because this is default behaviour for plugins: the lines will only be put in if the skin is enabled.

rdiff.quickmenu.tmpl has %TMPL:DEF{"epeatedsearchblock"}% so that won't work smile

-- ArthurClemens - 15 Jun 2006

I'm still working on those, need to clean code up a bit, but it shouldn't require the pattern skin to work at all. Any code needed from pattern skin could be "borrowed" and copied into this skin.

-- VernonLyon - 16 Jun 2006

Well I think it would be better if the menu could be "overlayed" on top of other skins. So to make it less a skin.

-- ArthurClemens - 16 Jun 2006

And to be able to use it if using a different skin, which would be a very good thing.

-- MeredithLesly - 16 Jun 2006

Thanks for the update, submenus are working just fine!

I presume you are using this in an LDAP or anonymous environment, since the login/register/welcome part of patternskin is left out.

Any ideas on how to best include this part in the skin? As a personal webleftbar doesn't make much sense with this skin, I'm just thinking of the central part of the login, i.e.:

%IF{"context authenticated" then='%MAKETEXT{"Hello [_1]!" args="[[%WIKIUSERNAME%][%SPACEOUT{%WIKINAME%}%]]"}%%BR%%LOGOUT%' else='%LOGIN% %MAKETEXT{"or"}% [[%TWIKIWEB%.TWikiRegistration][%MAKETEXT{"Register"}%]]'}%

I have tried adding an extra "line" with room for tags also (TagMePlugin), but couldn't make it look quite the way I wanted. Inspiration appreciated smile

-- SteffenPoulsen - 20 Jun 2006

A good way to include it in the skin is to add it to the "Options" menu in the templates or maybe by adding a new menu "Welcome" with Login & Register as the menu items.

-- VernonLyon - 20 Jun 2006

Thanks, I'm fiddling a bit more with it!

PatternSkin supports "per web" menus using the WebLeftBar mechanishm, which is quite handy - perhaps for a future release this kind of web dependent functionality could be thought in also per default (for now I simply include a local WebQuickMenu topic in QuickMenuBar and let this topic include the two default topics where needed).

A few things I noticed:

  • WebTopicCreator: Create button is not set active / inactive on entering new page name.
  • Attach screen turns up black with 4.0.3rc2

-- SteffenPoulsen - 20 Jun 2006

I'll look into those, btw I can't upload a new zip file as twiki seems to have run out of disk space!?? So the new code is only in the SVN repository for now.

-- VernonLyon - 21 Jun 2006

See Support.LostLogoutLink.

-- ArthurClemens - 21 Jun 2006

I think it would be better if the menu could be "overlayed" on top of other skins. So to make it less a skin.

-- ArthurClemens - 16 Jun 2006

And to be able to use it if using a different skin, which would be a very good thing.

-- MeredithLesly - 16 Jun 2006

Minor issue with WebTopicCreator: Create button is not set visible active / inactive on entering new page name ("Create new topic" in menu)

-- SteffenPoulsen - 20 Jun 2006

Thanks for all your work, Vernon.

TWiki had a temporary issue with uploading (ran out of inodes in /tmp), uploading is now ok again. Synced skin topic with SVN (perl build.pl upload).

-- SteffenPoulsen - 27 Jun 2006

Hi Vernon, I notice you are adding more and more templates. Which will make it more difficult to lift out the quick menu part for other skins. Is it your intention to make this a full featured skin?

-- ArthurClemens - 04 Jul 2006

It would be good to have a full featured skin for now, but I'm also looking at a way that it can be "overlayed" on other skins if they just want to make use of the menu. To make that possible though it might need to be a plugin instead or some other package. Any Ideas?

-- VernonLyon - 05 Jul 2006

You could create a contrib for the menu code. See code of TwistyContrib for an example.

-- ArthurClemens - 05 Jul 2006

Hi Vernon - great work - can you state what your intentions re: packaging this are?

-- MartinCleaver - 09 Jul 2006

Hey Vernon. This skin is nearly perfect for my needs. I am looking for a skin that maximizes the width of the browser display for topic content and, at the same time, is not confusing to new users. You got it. Now, the WYSIWYG editor (installed) does not show. Is that my responsiblility to figure out how to make it a menu item?

-- LorenEvey - 12 Jul 2006

I haven't been using the WYSIWYG editor, but I've included it in this release today.

-- VernonLyon - 13 Jul 2006

If the line Set WEBBGCOLOR = #FFFFC0 in the WebPreferences for a web has a space at the end (e.g. "#FFFFC0 "), then a js error occurs when loading the web on IE. The web loads fine under FF.

-- AndyMauro - 17 Aug 2006

Thanx for spotting that Andy, this is now fixed.

-- VernonLyon - 14 Sep 2006

I was trying out a nested structure tonight, but my menu seems to break on more than one submenu level.

Can the menu be altered to support more than one sublevel of menus?

(The JavaScript error I get when I am trying to add to Level2 is: "menu.Level1.Level2 has no properties").

-- SteffenPoulsen - 15 Oct 2006

Ah, you're right, it is a bug! Thanx for finding that. I've fixed it.

-- VernonLyon - 03 Nov 2006

Thanks Vernon, works nicely smile

-- SteffenPoulsen - 03 Nov 2006

I installed QuickMenuSkin 1.05 on a fresh TWiki 4.0.5 installation. I really really like this skin, it is clean, powerful and customizable. Not to downtalk the pattern skin, or other skins, this is the one for me.

Our internal installation uses a similar javascript menu system, based on the Philips corporate templates. I just want to mention, in our 80+ webs, users tend to define customized menus in their webs. TWiki is used a.o. as "poor man's" CMS. For that purpose, the edit/upload buttons are only displayed for people with change rights. The javascript menu is only included when group membership is determined in the following way:

var in_admin_group = %SEARCH{ "%WIKIUSERNAME%" web="Main" topic="....AdminGroup" nosearch="on" format="1" nototal="on"}% + 0;
if (in_admin_group) {...}
This customizable javascript menu has contributed to TWiki's popularity.

I have a number of remarks on this skin:

  • Backlinks do not look pretty. The template file "oops.quickmenu.tmpl" seems to missing in the disribution. See the screenshot. (Or did I do something wrong?)
  • I would appreciate an Edit button in the menu bar. I added this to the QuickMenuBar topic:
new QuickMenu.Menu(menuBar, "Home", "%SCRIPTURLPATH{"view"}%/%BASEWEB%");
new QuickMenu.Menu(menuBar, "Edit", "%EDITURL%");
For this to work, you need to change the EDITURL as well:
  • Set EDITURL = /cgi-bin/edit/Plugins/QuickMenuSkinDevArchive?t=1163581120 Otherwise, you always edit the menubar topic, not too productive.... It may be a good idea to change this is the base TWiki release.
  • I would like to be able to set the entire menu from the QuickMenuBar* topics. So, my preference would be to remove the Options definitions from the tmpl files and put them in QuickMenuBarOptions. By the way, would it be an idea to call this menu Topic, and include backlinks, history, and more as well?

With TWiki, you can put the result of searches in a pull down menu bar. E.g.:

changesMenu = new QuickMenu.Menu(menuBar,"%MAKETEXT{"Changes"}%","","%SCRIPTURL{"view"}%/$web/WebChanges","%MAKETEXT{"Latest Changes"}%");
%SEARCH{".*" web="%BASEWEB%" regex="on" nosearch="on" nototal="on" order="modified" reverse="on" limit="10" format="changesMenu.Add(\"$topic\", \"%SCRIPTURLPATH{view}%/$web/$topic\",\"\");"}%

Excellent work.

-- PeterHuisken - 15 Nov 2006

Btw, I noticed a small irregularity in the history. The javascript menu definition is visible in the history output.

-- PeterHuisken - 20 Nov 2006

Does this menu have a graceful fallback if JS is not enabled? Ideally, in that case the menu would be shown as the WebLeftBar, rather than nothing being shown at all.

One design would be to take the WebLeftBar as the definition of the menu and prevent it from showing when JS is enabled, but show the WebLeftBar when JS is not enabled.

-- ThomasWeigert - 20 Nov 2006

I've released a new version today that I've been working on for a while. The main differences are that it can now use a cleaner interface to build menus and uses real links in the menu. It has bugged me for a while that in Firefox, Safari... you couldn't open a menu item in a new tab or window. That is now possible! smile

Thanx SteffenPoulsen and PeterHuisken for your comments, I've added those into this version

I'll look into a fallback for browsers that don't have javascript enabled, but might not be feasable since this is a javascript menu...

-- VernonLyon - 22 Nov 2006

Hi Vernon, thank you for the quick smile update. The layout bugs on history and changes seem to be fixed quite nicely. Thanks for that! Btw, when using the CGI script changes, the javascript code is still there.

I can see why you put the Options menu elsewhere, visibility depends on the context. As soon as we upgrade our internal site to 4.0.5, I'll install this skin.

-- PeterHuisken - 22 Nov 2006

Applying this to TWiki 4.1.0 seems to break things, or I missed something.

TWiki Skin Browser claims:

" TWiki Installation Error Incorrect format of searchformat template (missing sections? There should be 4 %SPLIT% tags)"

Looking for the mentioned template yields no results. smile I'm guessing this is a simple thing to get included in the next rev.

I get the Options menu, but no other menus. Not edited anything at this point, just pointing out the obvious error I'm getting. smile

-- AndersHolm - 23 Jan 2007

I haven't tried it with 4.1.0 yet. Will look into it shortly and update it with a new working version.

-- VernonLyon - 24 Jan 2007

I got the same error. Fixed it by copying the searchformat.pattern.tmpl; renamed searchformat.quickmenu.tmpl.

Also having an issue with Twisty - JS error on certain pages and it is not working on edit topics. Trying to debug.

-- JimBishopp - 25 Jan 2007

Didn't see this trick mentioned, but like the recent changes having a menu item that displays child topics has really helped improve my navigation (I use hierarchical navigation heavily). This will add a child menu:

with (new QuickMenu.Menu(menuBar,"Children","","","Topic Children")) {


-- JimBishopp - 25 Jan 2007

rookie mistake...

with (new QuickMenu.Menu(menuBar,"%MAKETEXT{"Children"}%","","","%MAKETEXT{"Topic Children"}%")) { 
  %SEARCH{ "META\:TOPICPARENT.*\"%BASETOPIC%\"" type="regex" nonoise="on" nototal="on"  limit="50"  format="  Add(\"$topic\", \"%SCRIPTURLPATH{view}%/$web/$topic\",\"\");" }%

-- JimBishopp - 25 Jan 2007

The "More topic actions" page is broken in 4.1.0 and 4.1.1, unless I am missing something after upgrading from 4.0.4. You get a blank page, and worse - nothing shows up in the apache logs or the twiki logs. I also duplicated the problem in the standard "Main" web by setting it to use the quickmenu skin - same result, so I know it is now my custom web. Any clue on how to debug this?

-- AlexSchuilenburg - 14 Feb 2007

Hmm, that's weird! I'll try to fix it.

-- VernonLyon - 16 Feb 2007

The lastest distribution is missing many templates. I see only 15 in the latest distribution. The oops* templates seem to be missing. I find if I get a messed up web page I have to add "?skin=pattern" or "&skin=pattern" to the URL to get something to display.

I am using SKIN=quickmenu. Should I add other skins to this list?

-- WalterFergusson - 21 Feb 2007

I like my webs to have different background colors. The quickmenu template default is just white. I made the following changes to twiki.quickmenu.tmpl and got the colors back. Others may find this useful.

< %TMPL:DEF{"bodystart"}%<body bgcolor="#ffffff">
> %TMPL:DEF{"bodystart"}%<body bgcolor=%WEBBGCOLOR%>

-- WalterFergusson - 21 Feb 2007

I have found that I have to disable the templates attach.quickmenu.tmpl and renamebase.quickmenu.tmpl and list a second skin (pattern, in my case) in the SKIN preferences setting; that makes TWiki use e.g. attach.pattern.tmpl and renamebase.pattern.tmpl. If I don't do that, then I get a blank page when I hit the attach or rename scripts, respectively. I disable the templates by renaming them to .bad.

Walter, try Set SKIN = quickmenu,pattern; that's what I was just referring to.

  • If you are using the fixed templates (attached), do not set this option! -- MikkoLaakso - 15 Mar 2007

Regarding Alex's '"More topic actions" page is broken' problem, I am running a fresh install of 4.1.1 and I have no problem with that page. It displays using pattern skin, so this probably goes back once again to the fact that I have pattern listed after quickmenu. Considering that there are no oops* templates for quickmenu, I think you would have to have another skin listed or TWiki wouldn't have a skin to use for that page.

In fact, I find myself thinking the documentation ought to recommend that you specify a backup skin, since this skin doesn't provide templates for all occasions.

-- JohnWorsley - 28 Feb 2007

John has hit the nail on the head. Renaming attach.quickmenu.tmpl and renamebase.quickmenu.tmpl and adding a fallback skin Set SKIN = quickmenu,pattern at least gives the users a method to rename and attach until the quickmenu skin is fixed. I was simply resorting to adding ;skin=pattern to the URL, which effectively did the same but not as user friendly.

-- AlexSchuilenburg - 01 Mar 2007

Just reinstalled Twiki4.0.5 on MacOsx 10.3.9 with the QuickMenu skin without any of the parafernalia quoted above and I stopped getting this problem. I do still get it in my windows 2000 installation and it doesn't go away even when renaming the templates and setting the the skins to quickmenu, pattern as described above. Can it be that this is only a windows/Cygwin bug?

-- FernandoEblagon - 01 Mar 2007

Defintely not windows only. The server is running RHELV4 and clients are FF1.5 on FC5.

-- AlexSchuilenburg - 02 Mar 2007

QuickMenuSkin uses older syntax from TwistyContrib. I've created a bug entry Bugs:Item3711.

-- ArthurClemens - 03 Mar 2007

Fernando, you didn't specify what problem you're referring to, or which TWiki version you're running on Windows, but it looks like one of the changes between TWiki 4.0.5 and 4.1 was the addition of TwistyPlugin to the list of plugins TWiki comes with; 4.0.5 doesn't come with TwistyPlugin, but 4.1.x does. The presence of TwistyPlugin affects the way QuickMenuSkin behaves. Hopefully Vernon will get Arthur's bug fixed soon, and fix the attach and renamebase templates.

-- JohnWorsley - 05 Mar 2007

Sorry, my fault. I'm indeed using 4.1.1 on windows and the problem that got solved was that the screen would go blank when attempting to access "More topic actions" or other pages that didn't have a QuickMenu template attached to it. Cannot confirm that this is the case for ALL of the pages since after seeing that I couldn't leave it running like that I had to quickly move back to the classic skin. Been back and forth between 4.0.5 and 4.1.1 since I had problems getting MacOs to work happily with the upgraded Perl that the 4.1.x version demands. Eventually got it flying but by heart I'm not sure which version I ended up with. Will confirm as soon as I can. Confirmed 4.0.5 on Mac Os X 10.3.9 -- FernandoEblagon - 07 Mar 2007

-- FernandoEblagon - 06 Mar 2007

FIX: I made a new attachtables template that uses TwistyPlugin properly. If your attachments dont fold anymore after updating to the latest 4.1.x, just copy this to the twiki/templates folder and it should work if you have the TwistyPlugin installed properly.

-- MikkoLaakso - 11 Mar 2007

I have found two bugs in the attachetables for quickmenu.

  • Each attachement was in its own table. MikkoLaakso fixed this on 11 Mar 2007. Thanks.
  • The header for the attachement table seems to match the background white colour. The attached fix for 4.1.2 specifies a color so that it shows up. This incorporates all the fixes of 11 Mar 2007. If someone can explain to me where the header color default should come from then I will use that colour.
-- WalterFergusson - 12 Mar 2007

I have TWiki 4.1.1, and when I try the attach.quickmenu.tmpl dated 11 Mar 2007 - 17:44, my attach page is blank (which also happens to me with the attach.quickmenu.tmpl that comes with the current version of QuickMenuSkin).

Is anyone else having this problem with that version of attach.quickmenu.tmpl, or is it just me?

-- JohnWorsley - 13 Mar 2007

I also have the same problem with attach.quickmenu.tmpl on TWiki 4.1.2. If you specify the skin ?skin=quickmenu it displays correctly. If you specify the skin ?skin=quickmenu,pattern then the page is blank. I have set the SKIN = quickmenu,plain and now have no problems. There seems to be an interaction between QuickMenuSkin and PatternSkin.

-- WalterFergusson - 13 Mar 2007

This is related to which template TWiki chooses. With ?skin=quickmenu the chosen template is attach.quickmenu.tmpl, which it should. It seems Twiki is trying to load a different template instead. I am currently using the previous version of QuickMenuSkin, and I don't have this problem.

-- MikkoLaakso - 13 Mar 2007

Further debugging tells me that the attach script for TWiki 4.1.2 calls the template attachagain and not attach. So for ?skin=quickmenu,pattern the templates that are read are: attachagain.pattern.tmpl, attach.quickmenu.tmpl, twiki.quickmenu.tmpl, ccs.tmpl, and attachtables.quickmenu.tmpl. I suspect that the attachagain.pattern.tmpl relies on something that attach.pattern.tmpl provides but attach.quickmenu.tmpl does not.

-- WalterFergusson - 14 Mar 2007

Walter, are you sure? Couldn´t find anything on this from the TWiki releasen notes page, so I would imagine nothing has changed. Try to create a attach.quickmenu.tmpl template which only contains these rows:




See if you get "test" in the upper left corner.

-- MikkoLaakso - 14 Mar 2007

attach provides base modules for attachnew and attachagain.

-- ArthurClemens - 14 Mar 2007

I test the debug this problem by running perl -T -d attach -filename '' -user WalterFergusson -topic WebPreferences -skin quickmenu,pattern. I also test the TWiki using the firefox browser on Linux. I find the $name passed to the subroutine TWiki::Templates::_readTemplateFile and use this to trace what templates are read. I believe this is the only routine that reads templates. These are the results of the tests that I have run.

skins template 1 template 2 template 3 template 4 template 5 prints "Test" page generated
quickmenu,pattern attachagain attach twiki ccs.tmpl attachtables no no
quickmenu attachagain attach twiki ccs.tmpl - yes yes
quickmenu,classic attachagain attach twiki ccs.tmpl - no yes
quickmenu,plain attachagain attach twiki ccs.tmpl - yes yes

-- WalterFergusson - 15 Mar 2007

Are you sure you havent set SKIN = quickmenu.pattern ? This would disable the attach -template. To test this, insert the following line to the page:

   * Set SKIN = quickmenu

If you have my attach.quickmenu.tmpl file in place, you will probably see it display normally.

-- MikkoLaakso - 15 Mar 2007

Ok, guys to answer a lot of Qs... Here goes:

It seems there has been a lot of changes with TWiki since 4.0.5 which includes some changes to the Twisty stuff. This skin was relying on those things not changing for the skin to continue working without having to be updated every time a new release came out. So After spenidng a lot of time playing around with and looking at the broken code etc, I've come to the realization that QuickMenuSkin needs a rewrite!

Since I'm in the middle of writting QuickMenuPlugin which would have made things easier and simpler (and would make the menu available to other skins) I've been delaying from fixing this old skin. But It's in a mess since the 4.1.x releases sooo I'm gonna release a new one this week (I hope). This should fix the bugs and make the templates a lot cleaner.

-- VernonLyon - 20 Mar 2007

That´s great news, I´m looking forward for your plugin.

-- MikkoLaakso - 11 Apr 2007

I have been using this skin for the first time recently. Very clean look, nice menus!

Small suggestion: A wiki is meant to be edited. Nothing you see "above the fold" suggests that you can edit the page. It is hidden in the Options menu. It would be nice to have a big colored "Edit" button (with icon) somewhere in the menu bar (to the left of the Jump box?), soliciting a "please edit me!" smile

-- PeterThoeny - 13 Apr 2007

Report in Support web: OopsTemplatesNotShowingAnymore in TWiki 4.1.2. This should be fixed (core or skin, I do not know.)

-- PeterThoeny - 15 Apr 2007

QuickMenuSkin preview

(moved to the end of topic)

-- MikkoLaakso - 28 Apr 2007

Hi Mikko, great work. I've tested the "next generation" QuickMenuSkin and it would be nice if:

  • "Options" menu is easy to configure like the "Webs" menu (all menus and the menubar should be configurable without edititing templates/css/js on file level)
  • colors are easy to setup, e.g. the surrounding color should be the WEBBGCOLOR (and I don't like the green menus :-/)
  • "Edit" button is not hidden in the Options menu (it should be placed on the menuBar by default)

Thanx in advance ...

-- DanielRohde - 14 May 2007


  • My understanding from previous posts here is that the Options menu is in the template because some of the content is contextual and that context can only be determined in the template. But I don't know much beyond that; maybe someone else can explain better.
  • While I agree that many people benefit when visual factors like color are easy to change, I disagree that it should necessarily be WEBBGCOLOR. I would think preferences settings would be a good place to store information like that; you could set that preference to WEBBGCOLOR, and I could set it to something else just as easily.
  • To add an obvious Edit button to my menu, I did the following:
1) Created a topic containing the following:
editMenu = new QuickMenu.Menu(menuBar, "%MAKETEXT{"Edit"}%", "%SCRIPTURLPATH{"edit"}%/%BASEWEB%/%BASETOPIC%?t=%GMTIME{"$epoch"}%","","");
2) Added that topic to my QuickMenuBar topic like this:
%INCLUDE{"%TWIKIWEB%.QuickMenuBarEdit" raw="on" warn="off"}%

I hope that helps.

-- JohnWorsley - 16 May 2007

Thank you for the feedback! Please pitch in any improvement suggestions / faults you can find, I will try and take it like a man :). About the suggestions: There is an (yet) undocumented feature that you could use to define custom styles (or overload old ones). Here goes: AttachContentPlugin allows you to define css files that automatically get attached to the current topic. QuickMenuSkin can load a css file named customstyle.css attached in (Main.) TWikiPreferences (located here for safety reasons). Do the following:

   margin: 0px;
   padding: 0px;
   line-height: 1.3em;
   font-family: Verdana, "Lucida Grande", sans-serif;
   font-size: medium;
   text-align: center;
   height: 100%;
   border: none;
        background: #008899;

Here we have redefined the HTML and BODY. The only thing that is changed, is the background color. You can enclose this section to html comments so the preferences page will look less ugly. Then:

  • Save the page
  • Refresh so the new css takes effect (if cached, empty browser cache)
You should see your background color has changed, plus the gradient has disappeared.

This is suitable for making small changes to the skin (if you cannot access the QuickMenuSkin style.css itself) and quick tests/additions to style. For larger changes, you should modify the style.css itself (this will reduce the size of the stylesheets).

You cannot use dynamic styles here, the stylesheet will be written to file as you save the prefernces topic. For dynamic styles, you have to edit the twiki.quickmenu.tmpl and insert your style definitions there.

-- MikkoLaakso - 19 May 2007

Of course, you could make the attachcontent dynamic, in the sense that it would contain some variable calls. Something like putting %BGCOLOR% in place of background color, then

  • #Set BGCOLOR = #123456
This should work (havent tested).

-- MikkoLaakso - 21 May 2007

Refactored: KlaasHolwerda had a problem of not being able to use attach properly. The further investigation of this issue requires re-installing the quickmenuskin, without modifications to .css or any other files, and setting the ownerships/access rights appropriately.

If i try to attach to the next, it is exactly as you say, no Upload button! http://wxart2d.klaasholwerda.nl/cgi-bin/twiki/bin/view/Main/TrialTopic but on your topic: http://wxart2d.klaasholwerda.nl/cgi-bin/twiki/bin/attach/Sandbox/TestTopic0 it is oke.

-- KlaasHolwerda - 11 Jun 2007

-- MikkoLaakso - 29 Jun 2007

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2008-02-25 - MikkoLaakso
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.