This package provides…
A simple web 2.0 look progress tracker. No need to change the wikicode, just edit the tag of the page. The tag naming is as follows : _progressX% in wich you replace x with a number form 0 to 100. I am working on a version so it can be in a ListPages module Have a look.
Instructions
To install this package in your site, include in your page the following content:
[[include :csi:include:progressindicator label=Progress Indicator|style=#f00]]
AND!!!!
give your page the tag of the percentage for example _progress67%
- label stands for the text before the indicator bar
- style changes the filling of the bar. It can be a color or it can be a style. Here is the up till now list of styles
Red
rog
lens
byg
irongiant_blue
late-harvest
green-grass
cherry-red
deep-blue
orange-juice
pretty-pink
royal-purple
tropical-seas
midnight-coal
silent-silver
pale-snow
Include files
[[table class="{$class}" style="border-collapse: collapse; width:100%; margin-bottom: 10px; font-weight:bold; background-color:#eeeeee;"]]
[[/table]]
Please don't create random categories, place all CSIs into the include: category. Thanks.
Portfolio
I had a look at the implementation… and have some comments.
Personally while I like the graphics, this seems like overkill and I'd prefer to use simple table-based techniques, especially in CSIs that we put into this central repository.
Portfolio
I thought, seeing the complexity of the calendar… it would be no problem. I'll reduce it.
what do you mean by that? <html><table>-layout?
It won't work if I change it back to passing the progress value as an argument to the CSI instead of a tag. I did it because
The CSI also looks so complex because I can't include a corresponding css to it. That is for the future.
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
The calendar is complex, yes. In the end we decided to not host that here but on a dedicated site, which acted both as a demo of the application and a repository of its CSIs. We've done that for some other complex apps like the forum-template.
That might be worth doing here too. I see you're renaming the include files - be sure to use names that are explicit, e.g. "include:progress-listpages" rather than "include:listpages". When people use the CSIs, they should know what they are using.
We'll have to write some guides on how to make good CSI packages, since we're developing a few different techniques now.
Portfolio
Yes… some procedures would be good, but I have to say I did not search for a procedure… I just started.
That's why I used my own category (PI) progress indicator.
But I can live with :csi:include:$packageName-$relatedPageName way of naming things.
Sorry for not checking if there was a procedure somewhere on how to name things.
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
this looks nice, but, why make two different csi for pretty much the same thing? instead, just use the one i made. i added an option for background images, and they can do exactly what this is doing…
ill make an example in a sec
EDIT: look now
I didn't even realize 'pi' meant 'progress indicator'… usually the word means 3.141592…
I'll start writing a few guidelines for this site then.
Portfolio