Template talk:Objectives

From WikiEducator
Jump to: navigation, search

tweaked the colours a bit and added a margin-bottom: 40px. brent 02:31, 18 December 2006 (CET)

Thanks mate - helps having a professional on board! I prefer the colours - more subtle. Noticed that the background behind the heading cell must still be specified.

I'd like to have a subtle distinction between information idevices (eg objectives, key points, definitions) and iDevices requiring learner activity (eg activity, self assessment, reading). Could you have a look, say at the activity iDevice and suggest a subtle differentiation - eg a hue of green for those iDevices requiring action on the part of the learner. Just do one example - I'll cut & past the rest. Sunday evening here and will now take a little time out! --Mackiwg 03:45, 18 December 2006 (CET)

template GUI

yep, sounds good. will work on that. we really need to get some programming work done on getting a kind of gui solution for new people to add iDevice templates into content. i could probably work w/ david on a solution - we can install MediaWiki and give it a shot. I'll ask him and perhaps we can set up a dev version of mediawiki, do a little brainstorming and give it a shot. i have some ideas of how it might easily work. brent 12:01, 18 December 2006 (CET)

That would be pretty cool - let me know how you progress on the brainstorming, perhaps we should Skype pretty soon? Re my earlier comment - While I like the ideas associated with a template GUI - Could you have a look at say the activity template and tweak for a subtle green outline and background colour. I'll adjust the other templates when I get a gap. --Mackiwg 21:31, 18 December 2006 (CET)

Generic template

Please note that this is a generic template for Objectives, Not course specific

Broadcasting to TOC

Added a second argument called header = {0,1,2,3} that allows the user to choose if and where the template appears in the TOC. The default 0 which does not list the template in the TOC (see Template:Activity) for more details. -- Kruhly 23:00, 17 March 2007 (CET)

Having the header inside the decoration was causing the edit link to get confused. I have moved the #switch statement outside the decoration and made the header's visibility=hidden so that the TOC is alerted and the text does not show up above the decoration. Please note the <h1 ...> in the decoration must have a carriage return after it and before "Objectives" otherwise there will be an extra listing in the TOC and the edit link will be confused. -- Kruhly 07:13, 19 March 2007 (CET)

This is actually a cool hack, but a hack nonetheless. We really ought to consider what sort of meta-data needs to be associated with these templates. In this case if we define a micro-format, the name of the Activity and its hierarchical level have to be extracted from the <H#> tag, which is semantically reasonable, but I would put all of this in a DIV of class="OER" or somthing, and have adequate css in the wikied.css (or whatever it's actually called) to hide it; style="visibility: hidden" in templates is too fragile, me thinks.

--Phsi 07:28, 19 March 2007 (CET)


Thread titleRepliesLast modified
Template Margins123:08, 18 January 2008
Broadcasting to TOC123:06, 18 January 2008

Template Margins

Added parameters for TopMargin and BottomMargin. Added an #if statement around the PutInTOC template so that the parameters for the margins work. Set the default as -10px and -20px for the Top and Bottom margins respectively. There seem to be two reasonable choices for the top margin default:

  1. around 10px when the template is called immediately after a section heading <H#>
  2. around -10px when the template is called after wikitext

So far it looks like a toss up as to which occurs most often. Thoughts?

Kruhly (talk)23:57, 27 December 2007

Decided to go with the -10px default. The only case that I can find that is a problem is when the pedagogical template follows a section see Template:iDeviceFollowingASection

Kruhly (talk)23:08, 18 January 2008

Broadcasting to TOC

Putting it into the css sounds like a good idea -- it would be common.css that we would want to be in. I will have a play.

Kruhly (talk)23:59, 27 December 2007

Style added to common.css and it seems to be working

Kruhly (talk)23:06, 18 January 2008