[pmwiki-users] New features to be enabled in the PmWiki core
Petko Yotov
5ko at 5ko.fr
Sun Sep 8 12:22:03 PDT 2019
On 31/08/2019 21:53, Simon wrote:
> see Core Candidates [1].
Some of these are planned or already committed.
> of those recipes you list I'd very much like to see DDMU,
> Attachtable (the entire kahuna), LocalTimes, PageListMultiTargets
The core (:attachlist:) feature will likely acquire the capabilities to
delete/rename/restore attachments, in a possibly sortable table, but for
the moment any other features of Attachtable are not planned for
inclusion.
You will be able to keep using your existing recipes, as I mentioned
earlier the new core features will be disabled by default and will not
conflict with existing recipes.
> Additionally I use, and would like to see considered for the core
>
> * Cookbook:Wiki footer [2] Website page footer
This already exists in the "pmwiki-responsive" skin which is
pre-selected in sample-config.php. Only it is a single page
Site.SkinElements where you can define both the header and the footer.
BTW the "Amber" skin which was based on "2016/pmwiki-responsive" also
uses a Site.PageElements page with all skin sections. Other skin
developers can do what they need, there is no problem with this.
> * Cookbook:Toggle [3] Adds links or buttons for toggling
> (hiding/showing) div sections and objects
Not at the moment, as it adds new markups, and indeed it is a complex
recipe.
If a Toggle feature is needed in the core, the UnToggle recipe provides
a progressive, unobtrusive way to add the feature while keeping the
content readable for people with JavaScript disabled.
I install this on about half of my wikis, but it is mostly used on a
custom "Site.EditQuickReference" larger, foldable cheat sheet with the
markups people from the specific wiki will probably use.
So, not right now. :-)
> * Cookbook:Rowspan in simple tables [4] Markup to add a rowspan
> attribute on a simple table [5] cell
I've added an implementation of this in Suibversion.
> * Cookbook:New page box plus [6] Adds customisable box plus button
> form for page creation
While this adds a new markup, I am considering implementing such a
feature and supporting it in the core, to keep with the PmWiki
philosophy #5 "Be easy to install, configure, and maintain".
People who do not have the ancient "wiki way" culture may have
difficulties understanding the concept "first create a link to the new
page in an existing page, then click on the link to create the new
page". This is counter-intuitive compared to most of their other
computer-aided writing where they first create a file, draft a number of
versions, and only when it is ready they send it or print it.
So, a kind of "new page form" with an easy markup and obvious
functionality will indeed make it "easy to install, configure, and
maintain" for admins.
> * Cookbook:DeltaBytesRecentChanges [7] Display the number of bytes
> (characters) added or deleted to a page in RecentChanges.
Added today, but see the notes on the styles as some skins may lack
those:
https://www.pmwiki.org/wiki/Site/AllRecentChangesShort
https://www.pmwiki.org/wiki/PmWiki/LayoutVariables#EnableRCDiffBytes
> * Cookbook:Attach links [8] Get Attach: [9] links to display by
> default without the "Attach:" prefix
I assume you don't ask this for all other InterMap links. Yes, it should
be possible to add a switch to remove the prefix.
Petko
> On Fri, 30 Aug 2019 at 08:00, Petko Yotov <5ko at 5ko.fr> wrote:
>
>> Hello,
>>
>> This is to let you know that I've added to the PmWiki core in
>> Subversion
>> a number of features from my own recipes/addons that are somewhat
>> popular and that I see myself installing on every new wiki I create.
>>
>> Because many of you already use these or similar addons, the newly
>> added
>> features will be disabled but it will be very easy to enable them
>> from
>> config.php.
>>
>> Here is the list:
>>
>> Editing a wiki:
>> * PreviewChanges - this has been enabled on PmWiki.org for years,
>> shows
>> a highlighted diff in Preview mode (already added in 2.2.118).
>> * NotSavedWarning - signal to editors when they are moving away from
>> the
>> edit form and risk losing their changes (the Author/Summary prompts
>> from
>> the recipe are not included in the core, because now it is easy to
>> add
>> "required" attributes to the edit form fields).
>> * A sub-feature from NotSavedWarning scrolling to the same position
>> when
>> pressing either Preview or Save&Edit (enabled by default).
>> * EditHelp - predictive insertion of markup like list bullets (I use
>>
>> this a lot, especially on a mobile device).
>>
>> Reading a wiki:
>> * DeObMail - obfuscating e-mail links for spam bots.
>> * PmTOC - a really basic "table of contents +/- numbered headers",
>> currently a simpler subset of the AutoTOC recipe will be included in
>> the
>> core, see:
>> https://www.pmwiki.org/wiki/PmWiki/TableOfContents
>>
>> Again, these will be disabled in the default installation, but could
>> be
>> enabled as easily as adding $EnableNotSavedWarning = 1; if you
>> decide to
>> use any of them.
>>
>> Other features planned for inclusion:
>> * PmEmbed, a subset of the Ape recipe (minus the OpenStreetMap part
>> which is too complex to include in the core at this point). The main
>>
>> embedding function is light and simple and can be easily extended.
>> As
>> more people need to include videos or other media from external
>> platforms, this recipe can do the job in a simple way.
>>
>> Other recipes (actually their feature set) under consideration:
>>
>> * DragDropMultiUpload - upload files by dropping them into the edit
>> form.
>> * LocalTimes - RecentChanges enhancements.
>> * LocalCSS - CSS in a wiki page.
>> * A small subset of the features of Attachtable - I use a very old
>> fork
>> with just rename/delete/restore.
>> * PageListMultiTargets - this allows a pagelist "link=" argument to
>> accept more than one link. We should decide if "link=Page1,Page2"
>> should
>> include pages that link to *any* of the pages or to *both* pages.
>> Currently it includes any of the pages, and you need to use
>> "link=+Page1,+Page2" to require both pages.
>>
>> * Add a set of CSS rules for editors to be able to more easily
>> create
>> nicer-looking tables -- to the default skins -- obviously other
>> skins
>> can redefine the styles of the same classname(s), like they
>> currently do
>> for the "frame" class.
>>
>> You can follow the progress of this project at:
>>
>> https://www.pmwiki.org/wiki/PmWiki/ChangeLog
>> https://www.pmwiki.org/wiki/Site/AllRecentChangesShort
>>
>> Tell me what you think. What recipes/addons do you install on your
>> wikis
>> (especially if you have installed multiple wikis)?
>>
>> I am interested in features you and your editors actually use, not
>> "might be nice", and that do help editors create better content with
>>
>> less effort.
>>
>> See how the above recipes once configured are mostly automatic, and
>> don't add new markups that people are required to learn. And they
>> considerably enhance the editing experience or the webmaster's work.
>>
>> Please comment.
>>
>> Petko
>>
>> _______________________________________________
>> pmwiki-users mailing list
>> pmwiki-users at pmichaud.com
>> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
>
>
> Links:
> ------
> [1] https://pmwiki.org/wiki/Category/CoreCandidate
> [2] https://pmwiki.org/wiki/Cookbook/WikiFooter
> [3] https://pmwiki.org/wiki/Cookbook/Toggle
> [4] https://pmwiki.org/wiki/Cookbook/RowspanInSimpleTables
> [5] https://pmwiki.org/wiki/PmWiki/Tables
> [6] https://pmwiki.org/wiki/Cookbook/NewPageBoxPlus
> [7] https://pmwiki.org/wiki/Cookbook/DeltaBytesRecentChanges
> [8] https://pmwiki.org/wiki/Cookbook/AttachLinks
> [9] https://pmwiki.org/wiki/PmWiki/Uploads
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users
More information about the pmwiki-users
mailing list