Heading and bullets misbehaving
I'm on XP and Internet Explorer. I can have only one heading and bullet set per card. Subsequent headings load at the bottom of the card with it's bullets above it. Anything I can do about this? Thanks. -- You received this message because you are subscribed to the Google Groups GTD TiddlyWiki group. To post to this group, send email to gtd-tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to gtd-tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gtd-tiddlywiki?hl=en.
[tw] EditSectionPlugin scroll back problem
Dear all, The short subject title could not precisely describe the problem. Actually EditSection[1] works perfect. When the edit button is clicked, a small edit window is poped up around the section of interest. It is undoubtedly a wonderful plugin for long tidder editing. But when I install both EditSection and TiddlersBarPlugin[2], it seems that the browser window is scrolled back to the top of tiddler when edit button is clicked. I do the experiment on an empty tiddlywiki, so certainly the scrolling back is not induced by other plugins. Is it possible to fix the problem? Any thought is appreciated. [1]http://www.tiddlytools.com/#EditSectionPlugin [2]http://visualtw.ouvaton.org/VisualTW.html -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] Not Understanding EditFieldPlugin TaggedTemplateTweakPlugin
The Tagged templatetweek is for the view and edit templates. See the Shadow
tiddlers ViewTemplate and EditTemplate which use a different formatting to
inside tiddlers.
This command
newTiddler
label:New Person
tag:person
Tagged Template Tweek Would thus tagged person,
apply the template in personViewTemplate when viewing a tiddler tagged
person
apply the template in personEditTemplate when editing a tiddler tagged
person
- These templates determine the layout of the viewing and editing process
not the content you are thinking about. You may not need the tagged template
tweek at all.
As you want to pre-populate the new tiddler with your above content put it
in a tiddler called personContent and use the following to create the new
tiddler.
newTiddler
label:New Person
tag:person
text:{{store.getTiddlerText(personContent)}}
personContent will contain your Template above.
I have not tested this again to ensure that the newtiddler command populates
the new tiddler with the content of personContent without first evaluating
it but you will see fairly quickly.
Regards Tony
Anthony Muscio
LaSourceProjects.org Open Source Sustainability Projects
LaSource.com.au http://www.LaSource.com.au Sustainable Products and
Business
SerendipityIdeas.com IT hints and Tips and Website hosting
Like personal Web 2.0 ? see www.tiddlywiki.com
On Fri, Nov 19, 2010 at 17:47, Keith Silva keith.si...@gmail.com wrote:
Hi:
I have a tiddlywiki with only the EditFieldPlugin and
TaggedTemplateTweakPlugin installed. I have a tiddler titled
personViewTemplate as follows:
|Prefix, First Name Middle Namebredit fname|Last Name
Suffixbredit lname|
|Titlebredit persontitle|
|Organizationbredit org|
|Desk Phonebredit phone|Extensionbredit ext|
|Cell Phonebredit cellphone|
|Emailbredit email|
|Notesbredit notes 6|
This tiddler correctly displays a simple input form in view mode and
the EditFieldPlugin correctly asks for confirmation as text is entered
in the input boxes.
What is the proper syntax in a macro button to open this form as a
template in view mode ready to accept user data entry? This macro
opens a new tiddler in edit mode rather than view mode:
newTiddler
label:New Person
text:{{store.getTiddlerText(personViewTemplate)}}
I thought this version would trigger the TaggedTemplateTweakPlugin:
newTiddler
label:New Person
tag:person
Instead, it produces an empty new tiddler in edit mode which when
closed produces this raw text in view mode:
|Prefix, First Name Middle Name
|Last Name Suffix
| |Title
| |Organization
| |Desk Phone
|Extension
| |Cell Phone
| |Email
| |Notes
|
The above text in view mode seems to indicate that the
TaggedTemplateTweakPlugin is being called, however the text is not
accompanied by a tiddler command menu.
I hope this is an adequate explanation of my problem. I'm just trying
to open an input form ready for user input. However, I will have 3 or
4 different input forms and I'd like to use the
TaggedTemplateTweakPlugin to open the appropriate form base on a
tiddler's tag (tags such as: person, project, issue). I have looked at
UdoBorkowski's form and data plugins, but I would like to have this
work with custom fields rather than JSON data because I think the
custom fields will be easier to work with as my tiddlywiki grows.
Thanks, Keith Silva
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.comtiddlywiki%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: two-levels main menu
Is it possible to set a two-levels main menu? And if yes, how? Would be possible to hide the level-two items and show them only when the first is selected? I don't quite get it - Do you want to hide and show both at the same time or do you want to show one and hide the other? I use Eric's (http://www.tiddlytools.com/#NestedSlidersPlugin) NestedSlidersPlugin to do things like collapsing other sliders when opening a slider... Take a look to the left panel in the followin TW: http://tw-abc.tiddlyspot.com/ This is exactly what I wish: a more-than-one-level main menu which explodes the subitems when the parent-item is selected. Should be possible to have all the subitems shown as an option? Thanks. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] You need to save this tiddlywiki to a file before you can save changes. suddenly appeared
I started building a TW on tiddlyspot.com. Everything worked fine. When I choose save changes in the menu on the right, the error message You need to save this tiddlywiki to a file before you can save changes. appears, but I think it's normal: I have to do save to web instead. Now, things changed suddenly. Now every time I edit a tiddler and then choose done the error message appears. Even if I do not modify anything! My last day in TW I installed SinglePageMode plugin, but I'm not sure its fault, because even if I delete it the error still exists. I am totally disoriented. I can continue to work on my TW, but the error messages and beeps when editing are very annoying. What have I to do? Thanks. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: style for images
You can write
/*{{{*/
.mainMenu { color: red; }
.evid img {
border: 3px dashed red;
}
/*}}}*/
so that the CSS become preformatted if you want to.
I tried to use the string you suggest but the CSS code was displayed
without any carriage return and when it is very long it becomes
difficult to read... am I wrong?
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlyw...@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: You need to save this tiddlywiki to a file before you can save changes. suddenly appeared
Now, things changed suddenly. Now every time I edit a tiddler and then choose done the error message appears. Even if I do not modify anything! I apologize for the disturb, it was my fault! I have checked autosave checkbox! Please forgive me. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Announcement of 2.6.2 beta release of TiddlyWiki
This is a very nice enhancement indeed. The syntax however is i.m.h.o. somewhat confusing. Why append the option-name with _cookie:? a) to me it looks like an unnecessary complication of the syntax. b) the syntax more or less suggests (because of the closing colon) that you could still provide a value, which is illogical. So why not simply stick to the original syntax of option-name: value or option-name=value in which value can be cookie, true, false or a real value (like e.g. in txtUserName). W.r.t. the discussion about the preference: cookie vs SystemSettings I would like to suggest 2 possible solutions. Either: SystemSettings take preference when viewed over HTTP, whilst when opened from a local file the cookies take preference. This gives maximum control for the author/owner. Or: The SystemSettings enhancement is even further enhanced by being able to have 2 sets of system-settings: one options-set for viewing over HTTP and one for local use from a file. I fully support the earlier suggestions from AlanBCohen and whatever, to make cookies dependent on the filename of the TW-file. So every TW-file gets its own cookies. P.S. This whole contribution is written based on experience with independent TWs; I have no knowledge of or experience with TiddlySpace. Thanks to all involved for again having a great TW release. On 18 nov, 14:06, Martin Budden mjbud...@gmail.com wrote: I'm pleased to announce the TiddlyWiki 2.6.2 beta release. This release consists of a number of minor usability and hackability enhancements, as described athttp://trac.tiddlywiki.org/wiki/History, and one fairly major enhancement. The major enhancement is the addition of persistent options, also known as 'baked cookies'. This is the ability of TiddlyWiki to store some of its options in a tiddler, the SystemSettings tiddler, so that these options are retained even if the user deletes all their cookies, or moves the TiddlyWiki to another computer. The persistent options are more fully described at: http://tiddlywiki.com/beta/#PersistentOptions We are soliciting feedback about Persistent Options as part of this beta release, in particular: 1) Which options do you think should be persistent, and which options should be in cookies? 2) Do you think the persistent options have been explained properly, and do you have any suggestions to improve the explanation? 3) Which should take precedence a persistent option or a cookie? That is should a persistent option overwrite an option previously set in a cookie, or should the cookie value take precedence? This has been the subject of some discussion, and we are by no means sure which is the better option. In the beta the persistent option overwrites the cookie option. Note that for a standalone TiddlyWiki, the impact of the difference in precedence is not that great, but for TiddlySpace the impact is more significant: it means an option set locally by a user in a cookie can be overwritten by another user of the TiddlySpace, if that option is persistent. Martin -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: two-levels main menu
That site uses TreeviewPlugin (1). The plugin creates a graphical representation of tiddlers based on the TagglyTagging principle (2). I successfully implemented that for my bookmarks solution. w (1) http://treeview.tiddlyspot.com/ (2) http://mptw.tiddlyspot.com/ On 19 nov., 11:34, Ciofegates ciofega...@mailinater.com wrote: Is it possible to set a two-levels main menu? And if yes, how? Would be possible to hide the level-two items and show them only when the first is selected? I don't quite get it - Do you want to hide and show both at the same time or do you want to show one and hide the other? I use Eric's (http://www.tiddlytools.com/#NestedSlidersPlugin) NestedSlidersPlugin to do things like collapsing other sliders when opening a slider... Take a look to the left panel in the followin TW:http://tw-abc.tiddlyspot.com/ This is exactly what I wish: a more-than-one-level main menu which explodes the subitems when the parent-item is selected. Should be possible to have all the subitems shown as an option? Thanks. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] How to connect Tags (only) with Parts of Tiddler
Hello, I know that tiddlywiki is tagbased on specific tiddlers and their content. 1.) Is it possible to tag also parts of tiddler (with the PartPlugin installed before), so that a tiddler have different tags in content and in the parts ?? Example : Tiddler Content different Parts in Content (Tags there ??) Tags 2.) How about reseletable Tags fields that filters Tags by Parent Child Structurs to falilate to select them ? Example A 1 2 a b c B C How to set the select field to filter the Tags after select frist A only to show 1 and 2, and so on ?? Regards -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: EditSectionPlugin scroll back problem
Hi itcmsp, I had a similar problem, and fixed TiddlersBarPlugin, according to my needs. The changings are markt MP in the source. Try: http://freestyle.tiddlyspace.com/#TiddlersBarPluginMP -m On Nov 19, 9:06 am, itcmsp itc...@gmail.com wrote: Dear all, The short subject title could not precisely describe the problem. Actually EditSection[1] works perfect. When the edit button is clicked, a small edit window is poped up around the section of interest. It is undoubtedly a wonderful plugin for long tidder editing. But when I install both EditSection and TiddlersBarPlugin[2], it seems that the browser window is scrolled back to the top of tiddler when edit button is clicked. I do the experiment on an empty tiddlywiki, so certainly the scrolling back is not induced by other plugins. Is it possible to fix the problem? Any thought is appreciated. [1]http://www.tiddlytools.com/#EditSectionPlugin [2]http://visualtw.ouvaton.org/VisualTW.html -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Sorting ShowLocalDirectory
Hi All I'm using Eric Shulman's ShowLocalDirectory plugin (http:// www.TiddlyTools.com/#ShowLocalDirectory) which gives me all the files in a directory, sorted alphabetically, with last modified date and size, and the filename as a link to the file. If I keep all work products for a student in one folder (which is in the same directory as the tiddlywiki), I can make a tiddler named after the student, and this plugin provides a nifty way to show a listing of all their work drafts. I modified it a little to show the filename, modification date, and a link to a tiddler with the file name where I can put notes. I tried having it show the tiddler contents instead of the tiddler link (tiddler [[%1]]\\). If the tiddler exists, the contents show up fine, but if the tiddler is nonexistant, it seems to show the directory file listing twice more. I'm not sure why. I'd like to use this to track drafts of students' work, and sorting by the modification date would be really useful - ideally newest to oldest. By default, the results are sorted by file name (I'm guessing the OS default is the determining factor here). Questions: 1) Do any of you know a way to sort by modification date as the default? OR Eric would this be something simple to add in? (I'm guessing not but I thought I'd ask)... 2) Any ideas on how to prevent the file listing from showing up more than once if the tiddler is nonexistant? If it helps, I'm using version TiddlyWiki 2.6.0 in Firefox 3.6.12 but the issue appears in IE 8.0.7600 too. Thanks! Rich -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: tags vs field values
Hi, I think, it is a matter of supporting software, its usability and documentation. Tags are highly supported by the core and exposed to the standard user. Easy to use, displayed by the default layout. Allmost every listing core macro supports it. There are many plugins, that extend the core functionality. Most of them are well documented. Fields are highly supported by the core but are not exposed to the user. There is a hidden button in the toolbar to display them. Propper editing needs a plugin. Viewing is easy, but needs more advanced knowledge. Programmers like them to create meta or hidden information :) Slices are supported by the core in form of transclusions. eg: tiddler macro. Sections are supported by core in form of transclusions. eg: tiddler macro Slices and Sections are very well known. They are human readable. They are human editable, without any additional macro. But except of transclusions, they are allmost not used by programms to programmatically store human readable Information there. May be, because of human editing in the wrong way, will break the structure a programm needs to work propperly. May be, because the core doesn't expose easy to use edit functions like forms, radio buttons, drop down lists, to programmers and users. There are some well documented plugins, that expose easy to use edit functions like forms, radio buttons, drop down lists to the user. And it seems, many of them write to custom fields instead of sections and slices. And that's the reason why Michel says: For instance, I have an application on a TW that could no be done easily without tags or without fields! ...snip... 3. These items are easy to fill in (radio buttons, drop-down boxes, text-boxes for notes, etc.. 4. Each of the input is associated with a field In my opinion it should be: 4. Each of the input is associated with a slice, or section content. But the easy to use Interface is missing. I also don't know any core functions that makes it easy to eg: list slice:sliceName ..., because a full text search is considered to be slow. In my opinion usefull user data shouldn't be written to extended/ hidden fields. This data is to valueable. It should be in the tiddler content. Nicely formatted and exposed to the reader in a usefull way. I think all programmers should look for good usability in this area. Extended fields can hold metadata written by plugins, to get there job done. It shouldn't be mixed. Copy/paste a tiddler + tags from one TW to an other, should contain the whole information needed to work with the content. Loosing extended fields shouldn't make the content useless, or worse human readable. my 2 €ents mario On Nov 12, 5:29 pm, rakugo jdlrob...@gmail.com wrote: I guess the benefit of using tags is they are a TiddlyWiki concept thus lots of plugins exist around them. Work with fields and you may find there is a plugin that does what you want but relies on tags. However TW (unfortunately) uses tags for system things like systemConfig. And users use tags to attach extra metadata. Out of interest why is that an unfortunate thing? Is it because they show up in the UI? If so you can hide them by creating a tiddler systemConfig tagged excludeLists Jon -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: EditSectionPlugin scroll back problem
PMario, So amazing, it works! With your advise the two excellent plugin now cooperate nicely. Thanks very much. On 11月20日, 上午1時53分, PMario pmari...@gmail.com wrote: Hi itcmsp, I had a similar problem, and fixed TiddlersBarPlugin, according to my needs. The changings are markt MP in the source. Try:http://freestyle.tiddlyspace.com/#TiddlersBarPluginMP -m On Nov 19, 9:06 am, itcmsp itc...@gmail.com wrote: Dear all, The short subject title could not precisely describe the problem. Actually EditSection[1] works perfect. When the edit button is clicked, a small edit window is poped up around the section of interest. It is undoubtedly a wonderful plugin for long tidder editing. But when I install both EditSection and TiddlersBarPlugin[2], it seems that the browser window is scrolled back to the top of tiddler when edit button is clicked. I do the experiment on an empty tiddlywiki, so certainly the scrolling back is not induced by other plugins. Is it possible to fix the problem? Any thought is appreciated. [1]http://www.tiddlytools.com/#EditSectionPlugin [2]http://visualtw.ouvaton.org/VisualTW.html -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] Re: The Great TiddlyWiki Viral Mass Interview Challenge
On Tue, Nov 16, 2010 at 12:13 AM, PMario pmari...@gmail.com wrote: hi, I think the groupie mechanism can create a summary of all answeres to your interview questions. Without the need of adding anyone to the interview space. Thanks pmario, that is now done, with a lot of help from Jon Robson. I've updated the instructions too: http://interview.tiddlyspace.com// Many thanks, Jeremy. -m http://groupie.tiddlyspace.com On Nov 15, 6:32 pm, Jeremy Ruston jeremy.rus...@gmail.com wrote: So, further to some discussion last month[1], I'd like to kick off a project to gather together peoples views and feelings about TiddlyWiki. The hope is that by exploring how TiddlyWiki works in the minds of users we can learn something about teaching it to others, and perhaps get some insight into how to improve and develop it. The interview project lives at: http://interview.tiddlyspace.com/ There are instructions for how to participate, please do let me know if it's not clear what you need to do. The presentation of the answers is quite primitive at the moment because it just re-uses the existing UI for following. I shall try to improve it so that there's a bit less clicking to do to get at the good stuff. Cheers Jeremy [1]http://groups.google.com/group/tiddlywiki/browse_thread/thread/089ae1... -- Jeremy Ruston mailto:jer...@osmosoft.comhttp://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en. -- Jeremy Ruston mailto:jer...@osmosoft.com http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
