GNUZoo-Talk 🇺🇸I can find very little info in PmWiki about some types of fonts such as Wingdings.
Is there some reason not to use Font Wingdings ?
For example - here are some nice arrows from Wingdings 3: 🡠 🡢 🡡 🡣
I just copied and pasted them here.
Would it not be better to use 🡡 for the PmWiki TOC rather than an underlined up carrot ?
Related encodings: Webdings, Zapf Dingbats, Bookshelf Symbol 7
No recipes used, no font websites downloads, no config.php, just copy and paste.
I think these even work in Vim.
--gnuzoo
Thanks for not responding - seriously, I needed to study more about fonts.
Those arrow keys maybe look normal on ubuntu in firefox, but on an ipad and
probably other devices they look like empty rectangles - also referred to as "tofu".
If I want to do this right I would have to load a font. I have learned a few things.
gnuzoo
Normally when I display an image I just enter the "Attach:filename.png" and it displays like an image and nothing else.
When an image is displayed as a reduced size link to itself at normal size, Pmwiki adds an upload delta symbol.
%width=200px%[[Attach:[=some PHP Code=].png|Attach:[=some PHP Code=].png"Click this image to see the full beautiful PHP code colors"]]%%
Please look at the lower image at Cookbook/hltPHPLikeVim.
Is there a way to not show the delta symbol and keep using "Attach:"?
I added the "nodelta" classname to local.css, see how I wrapped your picture. --Petko
Oh! I see in the local.css
.nodelta a.createlink[href*="?action=upload&upname="] {
display: none;
}
Did you like this recipe?
Do you mean HltPHPLikeVim or nodelta? I like when people share open source recipes if they demonstrate understanding of the code they upload, and willingness+ability to support their users when there are questions and feature requests. I don't like when their behavior suggests the opposite. --Petko
I wanted to process the code more like Vim does, and it appears
that "token_get_all" does not really work for it.
Not sure what "proess" and "token_get_all" are. If I wanted a different color theme, I'd still use Cookbook:CodeHighlight and select one of the dozens of color themes it has, or add my own theme, very short CSS with my own colors. This would work for all other programming languages not only PHP. --Petko
Sorry bout that, fixed the spelling error. token_get_all is a PHP function. --gnuzoo
This solution works great, but I do not like that it adds a div and 2 lines page code for a link.
I do not think I will ever understand divs and layout.
A wikistyle to a div container would apply to all links in it. Alternatively, you can prefix each link with the wikistyle. --Petko
Will that become part of the core or a recipe?
Neither. In fact including pub/local.css when it exists is already part of the core, anyone can add styles to it on their wikis. I don't think anyone other than you will need the nodelta class. --Petko
Maybe adjust links so if an image links to itself it would not display the delta?
Maybe adjust links so an image that links to itself would not have to repeat the same filename?
I don't need an image to link to itself. If I wanted to open the same image in a new tab, I could right-click on it and select "Open image in new tab". I also hate when links open a new tab or window without my consent -- when I want that I can middle-click or right-click to open a new tab. Also I would expect the "external" 
icon to appear near links to "external" websites, not to a resource on the "same" website. But the standard allows all these so people abuse them. --Petko
Thanks! --gnuzoo
- - - - - - - - - - - - - - - - - - - - - - - -
> I'd still use Cookbook:CodeHighlight
Good. I have been trying to get the highlight for PHP to look like my recollections
of vim for like 30 years. Vim itself will output html with its colors, but the
colors never matched they, always looked off, faded, just wrong.
Nothing seemed to work. Vim used some kind of palette that depended on the terminal
that depended on the OS and the colors were always wrong. Every color out there I looked
at and never seen one that came close. Some looked promising, but the colors were wrong.
Some would not markup colors, like a variable would have a yellow $ and the name would
be cyan. Nothing worked. Some only had 5 colors, and vim used at least 8 AFAIK.
This is the first time I could see output that looked good to me. I do not think
CodeHighlight would be able to output this kind of syntax coloring and get the colors
right. Some might consider this somewhat subjective. Part of this problem is that
I do not know what the actual colors are. I just know that this works better than
anything I have tried in the last 30 years. If you got a better solution, please point
me to it, but I have tried a lot and nothing ever worked. --gnuzoo
- - - - - - - - - - - - - - - - - - - - - - - -
Adding this to the core css even as a one liner would not hurt anything:
.nodelta a.createlink[href*="?action=upload&upname="] { display: none; }
It would be simpler for authors who want to hide that triangle thing.
Who is the target audience? Is it only for people who are techies?
I bet 99% of people out there on the internet do not know what a css file is.
If they want to do this, they would have a steep learning curve.
Figure out what a css file is, try to find the css file, if its not there, create a css file,
find out they dont have permissions, contact the administrator to see if they
can add a css file, the administrator requires payment to add a css file, you have to pay the
admin some money, then you have to tell him what to put into the css file, then
add %nodelta% in front of text of the file/whatever, and add %% after it, then save, then
refresh the browser with ctrl-f5 (which most people don't know either), and hope it works.
I might think someone would just forget about using PmWiki and just go use WordPress (which I hate).
It is much simpler to just say to them "add %nodelta% in front of text of the file/whatever,
and add %% after it, save, then press ctrl-f5" and they would do that and it would work and
they would be happy.
In summary, adding this as a feature is simple. IMHO Pmwiki needs to become more feature rich.
More people will use it if it becomes simpler to use. Non techies or less techy users do not
want to edit css, do not want to edit a config.php, do not want to download, unzip, copy,
set permissions, add css, cookbook whatever else needed. They want to create content.
Content is king -- you can put great content into a poor interface, but it is still good content.
Poor content in a great interface is still bad. If developing content is simpler then people
will devote more time to creating good content rather than trying to make a triangle disappear.
--gnuzoo
- - - - - - - - - - - - - - - - - - - - - - - -
This does not appear to work for a download link in the cookbook:
.nodelta a.createlink[href*="?action=upload&upname="] { display: none; }
This not hiding triangle:
Downloads: %nodelta%Attach:hltPHPLikeVim.php%%
Downloads: %nodelta%Attach:hltPHPLikeVim.php %%
--gnuzoo
You are good Petko!
> 00:50 by Petko - space between link and %%, we talked about this in Ape-Talk (+2)
Can we add this to the Ape page documentation? I am not sure how to explain this
or I might do so myself. I think this could be an issue with all filename references?
Maybe this needs to be noted: and documented in other places in PmWiki so
others might not make this mistake like I have done at least twice now.
--gnuzoo
I like talk pages
--gnuzoo