Making my feet wet with PICO, to present markdown files in templates.
In this relation, I have a small issue linking to (local) images. If I follow documentation, which states that I should places images in assets directory and link  all works.
But I would like to places images next to each document, in the Content folder. This seems more logical to me.
I tried  and variants thereof, but none would link to the right place. Apparently there is no %document_url% I can use.
What is the right way to link from document to image in same directory ?
content
|----- document.md
|----- image.png
Related
I read the following posts: JavaFX: Display PDF in WebView, Displaying pdf in JavaFX
But there occur some problems for me:
The links of JPedalFX do not work any more and I can't find example codes on the web.
I don't want to use Swing-components in an JavaFX-application.
The solution with PDF JS doesn't work either, because Maven is used in the project and I don't want to put the library in the resources folder.
JxBrowser would be a possible solution but cost too much.
Any ideas?
I replaced the original images with my own images in the simple-slider-source.html file in the non-jquery example folder and uploaded into the server along with the image folder and .js files but it doesn't work. It just running the slider without the images. Before uploading into my server, I have compiled it with the simple-slider.compress batch file. In case of original images it's working fine but not with the replaced images.
Is there anybody who can suggest any clue why it is happening and how to fix it? Providing sourcecode snippet would be much appreciated.
The src attribute (url) of the <img> element is incorrect.
I'm using Xcode 6 and Assets Catalogue to manage my App Icons. Or at least so I thought!
I'm trying to validate my Archive, but keep getting this message:
I have an image of 120x120 in the Assets Catalogue under AppIcon (although labeled as CarPlay iOS8). In fact I have lots and lots of images under AppIcon. I know the 120x120 is there. I promise.
To check, I have deleted it. Added it again. Deleted all the AppIcons, added them again. Clean built.
Still the same error message.
I really am at a loss as to know what to do.
I've looked in the plist and there is no mention of CFBundleIcons in there ..
So, any help would be gratefully received.
Remove the CarPlay icon from your AppIcon image assets.
If you actually want or need a 120x120 icon anyway, this can also be fixed by including a 120x120 icon named AppIcon120x120.png in your bundle as a regular file (outside of the asset catalog), in addition to the CarPlay entry in the icon asset.
In the Package.appxmanifest on my Windows 8.1 project, the Visual Assets has a section called Square 30x30 Logo in the Tile Images and Logos category.
I know how to upload the Scale images and how to name them (imageName.scale-180.png etc), but I don't know what the Target Size images are for, or how to name them in the assets folder.
Where and when are Target Size images used? Are they used instead of the Scaled images? Any insight in this would be greatly appreciated.
(I can't post an image to clearly illustrate the assets in the manifest, as I require more points, so apologises for the lack of image.)
I had the same question, then found this;
http://msdn.microsoft.com/en-us/library/windows/apps/hh965372.aspx#target_size
These images are primarily used outside of WinRT/the Windows Store, for things like file association icons and protocol icons. That's why the sizes map to the usual sizes for older Win32 icons.
You can apparently name the images like this for automatic inclusion/assignment in the manifest file;
targetsize-
Examples:
targetsize-16
targetsize-96
We have been using Google Drive SDK for our app.
Since 2 October, when our app tries to create a Google Docs native document by uploading a html file contains img tags, the result become partly corrupted. Although the upload request finishes without error, all the images in the html are lost in the created document.
The behavior is not usual. For nearly two years, basically, the conversion for document insertion had interpreted the img tags and created embedded images. It seems like a server side problem exists.
Is it a known issue and would be fixed?
Or, is there something I'm missing and it is correct behavior?
[About the htmls we use]
The htmls for upload are based on exported "text/html" files from existing Google Docs documents.
All the img tags have src attribute with absolute url. They start with https and all of them are links on googleusercontent.com.
Apart from the img tags, all the html tags seems to be handled as before.
[How to reproduce the problem]
This problem can be reproduced by using DriveSample app in "Google APIs Client Library for Objective-C". Modify "DriveSampleWindowController.m" to force document conversion turned on (i.e., query.convert=YES;) just before uploading a file to Drive.
Download an existing Docs document with images as html.
Upload it as a new document to Google Drive (with document conversion turned on).
Open the uploaded document in 2 with Google Docs web editor. All images would be lost in the document. Also, no spinning wheels will be shown for the lost image areas.
The problem seems fixed on the server side within the last half day. Thank you for fixing it, Google.