My first approach was to try and duplicate the userName function used to get the name for the modifier. Then I would be able to adapt this from viewTemplate.
div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div> to something like this <div class='question'>Within your<span macro='view UnitName link'></ span>do you have enough resources to deliver that which your unit is 'intended' to provide?</div> The problem I had was that I couldn't get the variable UnitName to save like UserName does. That's when I went to explore DataTiddlerPluggin and TiddlerForm. I thought that there may be a more simple way to capture the UnitName data using something similar to the existing <<options txtUserName>> *I tried looking in the code and finding all lines of code with txtUserName and adapting them and placing them in a tiddler tagged systemConfig, but i started to get errors when I added a chunck of code which is involved in saving. It was at this point I went to look for plugins, thinking that it would be easier. I could have my tiddler titles Q1, Q2, etc and then generate the question using a similar way to the tiddler subtitle. Is this is a more sensible way to go? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
