| Date Proposed |
One line description |
Idea |
Votes For |
Votes Against |
Status |
text |
| 20 Apr 2004 |
Automatically create new webs |
Currently if you got to a topic in a web that doesn't exist you get the oopsnoweb page. It would be nice if it was configurable if you get oopsnoweb (which links to ManagingWebs where it can be created) or if it created the web automagically. -- SamHasler - 10 Feb 2004 |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
Save in edit-mode should be designed more convenient |
The normal user works on documents by using the Desktop-metaphor, which can also easily be applied to TWiki by "save" and "save & close" options during editing. (see BetterSaveBehaviour) -- AndreUlrich - 09 Feb 2004 |
1 |
0 |
Patch Available |
Code for direct-save is already available -> SaveContentWithoutEdit and has only to be integrated into the TWiki-Codebase. User interaction has to be designed and translated to templates. -- AndreUlrich - 09 Feb 2004 |
| 20 Apr 2004 |
Redirect to WebTopicEditTemplate topic when clicking on question mark link |
From Support Web: I would like to let the user select a template when creating a new topic. I understand (or think ) that this can be done by editing the WebTopicEditTemplate topic and adding a combo box containing all existing templates or whatever (see PerTopicTemplates ). But what if the user does not use the "Go" box to create the new topic but by adding a WikiWord and clicking the question mark? Can I somehow redirect to the WebTopicEditTemplate topic? (I would like to see a behaviour similar to that of MoinMoin Wiki, see http://twistedmatrix.com/users/jh.twistd/moin/moin.cgi/WikiSandBox ) -- KlausNowikow - 25 Jul 2003 Should this become default behaviour? If you work with templates, then this would be a big improvement. If you do not, however, this will take an extra step. Implementation issue: if you have a combination of parent AND template selection on WebTopicEditTemplate (see DynamicEditTopicTemplate), some values have to get prefilled. -- ArthurClemens - 20 Aug 2003 |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
Set "Release edit lock" checked by default |
See comments at: PleaseUseReleaseEditLockCheckboxVariable -- ArthurClemens - 06 Jun 2003 |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
Simplify deleting a page |
As it is now, a page is deleted by 'moving' the page to the '_deleted' web. This is a little awkward. This 'move' should be hidden from the user with an action link. A 'delete' link should handle this transparently to the user. -- TomKagan - 27 Dec 2002 |
1 |
0 |
Implemented |
Patch available in DeleteTopicShouldNotFollowIt. Patch is also applied in TWikiAlphaRelease and TWiki.org. Idea can be moved to OldUsabilityIdeas. |
| 20 Apr 2004 |
Create a separate page for Delete |
Deleting a page is currently done on the same page as Move and Rename. But you will never combine these actions on a topic. Less options == less confusion and better focus on the job to be done. Suggestion: create a separate template page for deleting topics. Same goes for Moving and Renaming. -- ArthurClemens - 17 Aug 2003 See also: TrashButton and DeleteTopicShouldNotFollowIt. |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
Reveal the actual to-be-generated link targets when previewing |
Say that you are creating a link to some less trivial location, i.e. not just a wikiword, but instead using a plugin or some sort of %MACRO{foo}% to have the final target of the link resolved on-the-fly when viewing the page. Another example is when using this sort of link:
<br />[[MyCoolPage][that cool page]]<br /> What is percieved as an unneccecary extra layer of implicity is the fact that you'll never be fully assured that generated links will point to their correct location until you have actually clicked "Save" and can view the results. I think that a really slick solution for this could be to generate a simple client side script to make the "resolved" link targets show up in the status bar of the browser instead of the rather unhelpful http://twiki.org/cgi-bin/oops/Blarf?template=oopspreview when hovering the respective links in preview-mode. -- ConnyBrunnkvist - 09 Feb 2003 If you limit the problem to "Make sure I create a correct link in edit mode", you can create a link to a pop-up window where you can browse the topics in the web, or maybe other webs as well. See for instance the pop-up in http://www.visiblearea.com/cgi-bin/twiki/edit/Patterns/Test_page (link "List of all topic names"). -- ArthurClemens - 09 Jun 2003 |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
extend 'Edit' and 'Preview' to automatically unlock page when possible |
A short javascript should be included on those screens hooked to the DOM onUnload() event. The script should be smart enough to not unlock when the user hits 'Back' from within the 'Preview' screen and to warn the user if they are about to discard changes. -- TomKagan - 27 Dec 2002 Why not just set the TWiki preference for topics to be unlocked-on-save by default? ( RELEASEEDITLOCKCHECKBOX = checked ) -- MattWilkie 28 Dec 2002 Sorry, I wasn't quite clear. The suggestion is about what happens when you abandon editing, not when you save your changes. The option box to which you refer works only if you click "save." Right now, the only clean way to abandon an edit is to click "cancel". Adding the javascript hook would automatically unlock the page for the other ways a user can abandon the edit ("back" button, closing the browser, typing in new url, etc.) Currently, any other action besides "cancel" leaves the page locked. I just spotted another case where another small Javascript can help. If a user saves a page, then clicks "back" to get to the previous edit, they are now working on an unlocked page. Hooking the another DOM event - onLoad() - on the edit page could tidy this up too without breaking the the wonderful cache fixes RichardDonkin implemented. -- TomKagan - 30 Dec 2002 |
1 |
0 |
Proposed |
|
| 20 Apr 2004 |
Relative anchors (<a href="#anchorname">) should work in preview mode |
Perhaps a few other anchor types should work in preview mode as well. -- TomKagan - 27 Dec 2002 I would like to see this. I would also like relative anchors to have a different class name so they can be stylised differently from regular links using CSS. E.g. <a href="#anchorname" class="alocal"> becomes dark blue, or whatever, instead of the regular link blue. -- MattWilkie - 28 Dec 2002 You can do this right now via CSS2 selectors, plus greater flexibility via CSS3 selectors -- TomKagan - 30 Dec 2002 Can someone show how? Or give a link? -- ArthurClemens - 10 Jun 2003 Anchor links can have a small icon after the link. I will investigate this. But I am not sure why anchor links should work in preview mode, and other links not. Someone has written a patch so that links in preview open a new window. -- ArthurClemens |
1 |
0 |
Proposed |
|