Differences

This shows you the differences between two versions of the page.

--- plugin:wrap:discussion [2018-03-30 21:07] – [Responsive float boxes] asked for example code to reproduce ach
+++ plugin:wrap:discussion [2023-06-18 00:32] (current) – help 47.54.65.213
@@ Line 5: / Line 5: @@
 Please start new requests with a new heading.
+===== Extra line of padding added at the bottom every div =====
+Every "big" box I try to create with this plugin has an extra text line's worth of vertical padding at the bottom that I can't seem to get rid of. I was previously using straight HTML div tables that worked fine. I converted the syntax and CSS classes to be used by the plugin and everything's inflated, including default classes like "div round box 200px center." Is there something silly I overlooked or might be doing wrong?
+- Sloane, 2023 Jun 17
+===== Question: Edit of nested WRAP in included pages looses target in editor ======
+If I use nested WRAP (for multiple folded sections), then editing on included page doesn't work. With simple WRAP (not nested) editing still works.
+==Example structure of pages for explanation==
+  namespace:start (page with include of page1, page2, page3)
+  namespace:page1 header-section without WRAP
+  namespace:page2 header-sections with simple WRAP (not nested)
+  namespace:page3 header-sections with simple WRAP (nested)
+To edit a header-section of start, page1 or page2, you can use the ''edit'' buttons on the start-page. If WRAP is used nested, then edit will open an empty page, if you try to edit via start-page. Opening the sub-page e. g. page3 first and then editing there will work.
+==Example structure of nested WRAP==
+  <WRAP>
+  This is the first section that should be seen all the time. But a part of it schould be folded.
+  ++++Folded part|
+  =====Header A=====
+  This will be collapsed initially but can be unfolded by mouseclick or general unfold.
+  <WRAP>
+  ++++Subdivision folded|
+  ====Header A.a ====
+  This secondary part is initially folded, even if the primary part is unfolded. I can be unfolded by mouseclick or   general unfold. In edit-mode no text will be visible, if edited via start-page. You need to open page3 and edit there.
+  ++++
+  Four plus for the end of the secondary folding, then the end of the secondary bloc by /WRAP...
+  </WRAP>
+  <WRAP>
+  ++++Another subdivision folded|
+  ====Header A.b ====
+  This secondary part is initially folded, even if the primary part is unfolded. I can be unfolded by mouseclick or   general unfold. In edit-mode no text will be visible, if edited via start-page. You need to open page3 and edit there.
+  ++++
+  Four plus for the end of the secondary folding, then the end of the secondary bloc by /WRAP...
+  </WRAP>
+   ++++
+  Four plus for the end of primary folding, then the end of the primary bloc by /WRAP...
+  </WRAP>
+AchimR 2022-06-27
+===== Question: How to style Note-Boxes in PDF export of DW2PDF plugin? =====
+I'm struggling to understand which css file I should update to change the style of the boxes/admonitions when exporting the PDF via the DW2PDF plugin.
+The ''%%userall.css%%'' file in the /conf/ folder updates my wrap boxes fine in the wiki, but does not affect the PDF export.
+I've discovered that I can update them in the PDF by editing the ''%%style.less%%'' in the ''%%/plugins/wrap/%%'' folder but surely this would be overridden if I update the wrap plugin?
+Note for others following in the same footsteps: Make sure you disable the DW2PDF cache option in admin configuration too - will save you a lot of headache :)
+===== Question: Notes-Boxes =====
+Is there a way, that the Text e.g. TIP: or WARNING: etc. for the Notes-Boxes could automatically inserted next to his Icon in the corresponding language? --- //[[roland.gantenbein@i-doit.ch|Roland Gantenbein]] 2018/11/23 14:11//
 ===== Request: Make 100% table width optional =====
@@ Line 12: / Line 66: @@
 -- pv2b 2017-10-20
+> Yeah, I think that makes sense. Initially I planned to only have 100% wide tables in columns but made them 100% in every single wrap (probably out of laziness, I can't remember). I have just made a change that makes changing table widths optional by adding a new 'tablewidth' class. That will be in the next release. --- [[user>ach|Anika Henke]] //2018-04-04 01:47//
 ===== Request: new "sucess" note =====
@@ Line 162: / Line 218: @@
 Is there a way to make the emulated headlines contain "a name=..." anchors, similar to how the regular headlines have such anchors?
-> No, this is currently not possible and is also not planned. As a work-around you can use the [[bookmark]] plugin. --- //[[anika@selfthinker.org|Anika Henke]] 2010/01/31 15:34//
+> No, this is currently not possible and is also not planned. As a work-around you can use the [[plugin:bookmark]] plugin. --- //[[anika@selfthinker.org|Anika Henke]] 2010/01/31 15:34//
 >> I now implemented **experimental** support for regular headlines, so those will contain the anchors and will also be added to the TOC. --- [[user>ach|Anika Henke]] //2011/05/15 18:12//
@@ Line 236: / Line 292: @@
 > The initial reasoning was to make it similar to DokuWiki's core  [[:wiki:syntax#embedding_html_and_php|html and php embedding]] (''%%<html|HTML>%%'' and ''%%<php|PHP>%%'').
 > Adding anything to the configuration options is a bad idea, as it would make the syntax different in every installation and could potentially break many things (other plugins, for example). (Although it would be beneficial for internationalization.)
-> I updated the code to use ''%%<block>%%'' and ''%%<div>%%'' additionally to ''%%<WRAP>%%'' and ''%%<inline>%%'' and ''%%<span>%%'' additionally to ''%%<wrap>%%''. (Using ''%%<box>%%'' would conflict with the [[box|box plugin]] which is quite popular.) It will be in the next release (coming soon). --- [[user>ach]] //2010/11/20 17:03//
+> I updated the code to use ''%%<block>%%'' and ''%%<div>%%'' additionally to ''%%<WRAP>%%'' and ''%%<inline>%%'' and ''%%<span>%%'' additionally to ''%%<wrap>%%''. (Using ''%%<box>%%'' would conflict with the [[plugin:box|box plugin]] which is quite popular.) It will be in the next release (coming soon). --- [[user>ach]] //2010/11/20 17:03//
 ===== Picker images=====
@@ Line 344: / Line 400: @@
 - Lar
+> ODT export is partly supported since June 2015. There is better support on the way (to be released soon), although a minority of wrap classes are still not supported. --- [[user>ach|Anika Henke]] //2018-03-30 21:29//
 ===== Not working, default template in 2012-01-25 "Angua" =====
@@ Line 705: / Line 762: @@
 </WRAP>
 </code>
+> The example page which comes with the Wrap plugin (and which is shown in the big screen shot on the [[plugin:wrap|plugin page]]) explains this a bit:
+>> :!: Attention: What is the difference between widths and width keywords and when is it best to use which? **Widths** can cause problems and will never fully add up, therefore will break the layout under some circumstances. (See [[http://en.wikipedia.org/wiki/Internet_Explorer_box_model_bug|box model]] for a technical explanation.) So, getting widths right will need some fiddling around and testing in various browsers. **Width keywords** on the other hand fit automatically and work better on mobile devices. But the drawback is that they need an extra wrap around them and don't work properly in older browsers (IE8 and under).
 Second issue is:
@@ Line 726: / Line 786: @@
 </code>
+> [[https://github.com/dokufreaks/plugin-blog/issues/82|This bug report]] says it's an issue between the the blog and wrap plugins. But I don't understand if the "extra flag [...] for overriding the automatic level detection" mentioned in there already exists and if yes, which one it is, or if it would still need to be developed. --- [[user>ach|Anika Henke]] //2018-03-30 21:12//
 ===== Collapsible boxes =====
 It would be really nice if the wrap plugin's many default boxes (box, info, alert, etc) came with an option to make them collapsible, which would add a [hide] link in the upper right which would collapse them down to just the title and a [show] link, sort of how the table of contents on wikipedia articles currently work. Possibly also with the option of having these boxes either collapsed or expanded by default.
@@ Line 831: / Line 892: @@
      * Firefox debugger: Style sheet could not be loaded. ''http:/internal link/dw/lib/exe/css.php?t=dokuwiki&tseed=c18e4....''
+> I cannot reproduce any of that. Does that also happen with the default 'dokuwiki' template and other plugins deactivated? If no, I would activate plugins and switch the template one by one to see which culprit it might be. If yes, can you please post some code examples? --- [[user>ach|Anika Henke]] //2018-03-30 21:46//
+>> I have one other idea. What does your `noPrefix` config option say? It should include 'tabs' in order for the tabs to be styled properly. --- [[user>ach|Anika Henke]] //2018-03-31 12:56//
+===== Question: Poem/Music lyrics styling =====
+I find WRAP very useful (so thank you!), and recently almost successfully added this to my userstyles.css:
+<code css>
+.wrap_poem {
+	white-space: pre;
+}
+</code>
+However, I find that while this does preserve line breaks as I want, it also results in huge gaps between verses. Inspecting the HTML, it looks like each verse becomes a ''<P>'' with a line break at the start and end. Is there any way to prevent this, or some other way using the WRAP plugin to display poems/song lyrics?
+===== Question: Dynamic Loading of Dark Template Mode =====
+Is there a way to load the ''darkTpl'' config option dynamically, so we could use it together with the [[plugin:loadskin|Loadskin Plugin]]?
+I tried simply putting ''$conf['plugin']['wrap']['darkTpl'] = 1;'' somewhere in the template's code but I guess it's not that simple.
+ --- [[user>phl|phl]] //2021-02-16 14:13//
+===== XML support =====
+Thank you for the plugin! Would it be possible to add support for export to XML (with the [[plugin:xml | XML plugin]])? To elaborate on that, I am writing a chronicle in Dokuwiki that I want to export to XML and subsequently Latex and print a book out of it eventually. I assign to some elements (span/divs or tables) classses that I want to format in a certain way. What I need from the wrap plugin is to preserve the classes in the XML output.
+ --- [[user>galapah|galapah]] //2021-07-11 12:15//