Hi all,
I am trying to make a template which contains syntax highlighting.
I made a template:
http://www.vtk.org/Wiki/Template:VTKCMakeLists
I then tried to use this template with:
{{VTKCMakeLists|Thing1|Thing2}}
But you can see here:
http://www.vtk.org/Wiki/VTK/Sandbox/UseCMakeListsTemplate
that it does not trigger the source code to be highlighted, but rather
actually includes the source tag as part of the text on the page.
Is there any way to do this?
Thanks!
David
Hi,
I am at the mozilla drumbeat event, and I met some of the enthusiastic
peopel of the wikimedia there. I discussed the following idea with
them.
The following simple idea, I think, can create a huge impact in using
wikipedia for education as well as for navigation. I seek your
comments.
* Proposal
A new infobox item for every page.
** What other pages the learner should read/learn before the current page?
The idea is to build a specific link between pages that will
generate a learning sequence (or you wish a teaching sequence or a
navigation sequence).
The authors of wikipedia pages will add the names of the pages that
they think the reader of the page may need to read, if they fail to
understand the content of the page.
** How to do this?
http://atlas.gnowledge.org started hacking a model that generates
dependencies between activities or topics (concepts). For example,
you may look at the page:
http://atlas.gnowledge.org/view_concept_activity?objid=12675&maptype=depmap…
The top links of the node are the links the user could visit, and
the bottom links are those that the user could viist after visiting
the current page.
** How to generate a learning sequence?
The set of all the dependency links will generate a sequence or a
road map for
learning.
This paper http://gnowledge.org/~nagarjun/collaborative-LTS-published-version.pdf
introduces the idea and what are the motivations and inspirations
of doing this.
** What wikimedia can do?
Currently http://atlas.gnowledge.org supports the following format
for adding the dependency links between the nodes.
#+BEGIN_EXAMPLE
factors < multiplication;
subtraction < difference;
product < multiplication;
factors < product;
division < factors; product;
fraction < division; multiplication;
division > remainder; divisor; quotient; dividend;
brackets > order of operations;
#+END_EXAMPLE
* '<' indicates 'dependson' whereas '>' indicates 'isrequiredfor'.
* Multiple relations in a single line are separated by semicolons ';'.
* Do not use word processors for creating the files. Use text
editors like notepad, emacs, gedit, vi etc.
The proposal is to introduce a similar encoding that is easy for the
authors of wikipedia to suggest while they edit or create a page.
-
gn
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
Hi,
I have a mediawiki installation at:
http://wiki.koolsolutions.com/
I would like to share documents like .doc, .ppt, .pdf, .xls file with my
clients through the "upload File" section. This is what I am looking for:
1. Each client will have separate permissions i.e. a file uploaded by client
1 cannot be accessed (view/modify/delete) by client 2.
2. As an Administrator if I upload a file I can specifically assign which
client has access to the file.
3. A client can also see what files are uploaded on the wiki to which they
have access only.
4. Not anybody can register on the wiki. I specifically create user accounts
for my clients and send them their login info.
5. Similarly for the pages on the wiki, I would like to assign specific
permission to my clients to access them. I guess the best thing would be to
create a separate ground for each client?
What all extensions will I need in order to achive the above? Is there any
best practice for this kind of a scenario?
Your thoughts/inputs are highly appreciated.
Thanks!
Hello all,
So, I created a wiki and installed the Semantic Bundle. The last
step involved announcing my wiki, which I did. I don't see it anywhere in
any list though. It just started so there isn't much to see but I am
curious about the smw submission process and how to get listed.
Thanks,
Bruce