Pictures

[Luiza Kipper]

Hello, I am just starting to use TiddlyWiki and just downloaded Quine 2 (and I have no programming experience at all). My question is how can I add a picture to the tiddlers in Quine 2 using iPhone or iPad? I don’t get the usual camera roll when I click on “insert picture” (see image). Thank you very much in advance.

[Quine]

Hi,

This is mostly a TiddlyWiki question, for which the best source of information is always TiddlyWiki.com, I still go there daily at least, but I'll try to answer here from a general perspective...

1. The button you are using in your screen shots, in the edit window of a tiddler, is strictly for pasting an existing image tiddler into your current tiddler. It looks through you wiki for images (you apparently have none); you pick one; and TiddlyWiki creates "wikiText" to present your picture in the tiddler. The resulting wikitext will look something like: [img[your-image.png]] in the editor, which you can always type for yourself rather than using the button. When you save your tiddler it will render the image in place, as part of your tiddler.

2. To make that work you need to get some images into the wiki. There are two ways:

a. Drag and Drop - It looks as if you are on an iPad, so the easiest is to open up either the Files App, or the Photos App side by side with Quine using split screen; drag the picture(s) or picture file(s) you want from Photos or Files across to your open wiki; drop it into your wiki. You should see the standard TiddlyWiki "import tiddler" open; there you can finish importing your image file(s).

b. Import Tool - For this method, use the "import" tool under the TiddlyWiki Tools menu, as shown in the attached screenshot. Use any of the three options: "Photo Library", "Take Photo or Video", "Browse". Follow the ensuing dialog to get the image you want into your wiki.

Once you have your images into your wiki, go back to step 1. to create the wiki text needed to render your images inside of a tiddler.

Hope this helps - Chris.

[Quine]

Slight correction - "Take Photo or Video" does not yet work - but is on my list.

[Luiza Kipper]

Thanks, your answer was really helpful! I realize I should go to TiddlyWIki.com to learn more.

Keep up the good work :)

Luiza

[Quine]

"Take Photo or Video" is now implemented, and will be available in the next release; it allows you to select "import" from TiddlyWiki tools inside of a wiki, and from there to use your devices camera directly; to take a photo, and save it into a new tiddler.

That next release is v1.2.6; contains a lot of core changes, requiring beta testing; will be opened up for beta testing as soon as I am confident in its performance through my own testing.

Cheers - Chris.

[Ed Heil]

Holy moly, taking pictures right into your wiki?  That's cool.  I doubt I'd use it much because smartphone photos are so heavyweight.

Will it also allow upload of images from camera rolls, or uploads from the files app?

--

You received this message because you are subscribed to the Google Groups "Quine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to quine-app+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/a7b7449d-7ed6-4d46-9418-b138543d34c7n%40googlegroups.com.

[Linda Bayley]

Ed, by “heavyweight” do you mean a large file size? I’ve been wondering how others handle photos in their tiddlywikis, especially now that we’ll have this nifty option via Quine 2. 

Chris, by any chance will Quine 2 allow the user to select a size or format to use when importing/taking a photo through the wiki? Or is it still better to resize a photo using another app before importing it? I had some “regular” sized photos in my first wiki files and crashed Quine pretty quick as a result.

Thanks!

-Linda Bayley

Sent from my iPad

On Nov 24, 2020, at 2:13 PM, Ed Heil <edh...@fastmail.fm> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/f3218735-bc6b-4273-a7d2-b3f90643332c%40www.fastmail.com.

[Quine]

Hi Ed - Good to hear from you again. You should be able to pull images in directly from Photos App, and from other files sources today. The net add I'm working on is simply the option of launching the Camera as well; Luiza's question made me realize that I'd never activated the Camera option in the Quine 2. The hard part is movies - for which you make the good point re size. Movies in wikis are ill-advised. But an occasional snap - it might be handy sometimes. Chris.

[Quine]

Hi Linda, Yes, I think Ed was referring to the potential file size for images in wikis: it might (will quickly) get to be too much, especially with constant saves. Personally, I leave photos on "disk" and link to them in WikiText using "[img[<relative path to photo>]]". The gotcha is that you external file links only work if you have folder level access to the place where you are storing your images. The easiest is iCloud, but I know not everyone likes iCloud. Elsewhere, it's best just to try to see what works. Cheers - Chris.

[ed....@gmail.com]

Yes, that was my concern.  It's a really neat capability but if used very much your wiki would baloon in size very quickly!

[Patrice Neff]

Hi Chris

On Tue, Nov 24, 2020 at 02:03:08PM -0800, Quine wrote:

> Hi Linda, Yes, I think Ed was referring to the potential file size for
> images in wikis: it might (will quickly) get to be too much, especially
> with constant saves. Personally, I leave photos on "disk" and link to them
> in WikiText using "[img[<relative path to photo>]]". The gotcha is that you
> external file links only work if you have folder level access to the place
> where you are storing your images. The easiest is iCloud, but I know not
> everyone likes iCloud. Elsewhere, it's best just to try to see what works.
> Cheers - Chris.

I personally work with large attachments using the `_canonical_uri` field in
Tiddlywiki. Would that be an option for this new feature?

However given the pain you have had working with the files in the other
contexts (loading, backup) that may not actually be possible.

Best,
Patrice

[Quine]

Hi Patrice - good to hear from again too,

Canonicals work well, under the same condition of needing folder level access. In fact, it was you who alerted me to canonicals originally; I’d never used them until you asked for them back in early beta days of Quine 2. Since then, canonicals have been a key test scenario for every release; and I’m using them for some of my own image libraries.

For my sins, my happiest landing zone for wikis is iCloud still, where canonicals work well; after that Working Copy, and Shellfish.

If I had the time then I’d sit down and write a universal File Provider, so that all of our other favorite cloud file services would have all of our favorite features. I have been hoping that those favorite cloud file services would catch up and improve their Apps and help us all, but obviously hope isn’t getting us very far, yet.  If I ever retire from my day job then I’ll take it on, but meanwhile I must resist.

Meanwhile, I’ve not given up on continuous improvement in this area.

Shout if you’d like to beta test again in the future,

Chris.

[Patrice Neff]

Hi Chris

On Wed, Nov 25, 2020 at 04:44:14PM -0800, Quine wrote:
> Canonicals work well, under the same condition of needing folder level
> access. In fact, it was you who alerted me to canonicals originally; I’d
> never used them until you asked for them back in early beta days of Quine
> 2. Since then, canonicals have been a key test scenario for every release;
> and I’m using them for some of my own image libraries.

Indeed. In this context I was mostly wondering if it makes sense for the images
to be stored onto the file system, and then simply referenced in the wiki using
`_canonical_uri`. But as I haven't seen the new feature in practice yet, I'm
not sure this even makes sense.

> For my sins, my happiest landing zone for wikis is iCloud still, where
> canonicals work well; after that Working Copy, and Shellfish.

Selfishly it's a good thing then that iCloud and Working Copy are the two
systems I have my primary wikis on.

> Shout if you’d like to beta test again in the future,

Always happy to. I had originally removed TestFlight when you released Quine2,
as I didn't realise you might still provide further tests. But please feel free
to re-invite me at any time and also mention specific components that need
testing.

Best,
Patrice

[Linda Bayley]

Chris!

 

I came across an image on the web that I wanted to be able to refer to from my wiki. the "[img[<relative path to photo>]]" method worked perfectly for this, and seems to still work even if I take my device offline, exit Quine, and re-open it again.

 

I really appreciate the tip!

 

-Linda B.

---

From: Quine [mailto:quin...@googlegroups.com]
Sent: Tuesday, November 24, 2020 5:03 PM
To: Quine
Subject: Re: [quine] Re: Taking photos directly from Quine....

To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/d3e10f40-b558-4914-b574-c91d80e26053n%40googlegroups.com.

[Lmba...@bell.net]

Patrice, Chris, and everyone,

I THINK I’m starting to understand the use of the ‘_canonical_uri’ field for external images. I tried creating an image tiddler using this field and the full path to a photograph, and was then able to include an [img[phototiddlername]] reference into a different tiddler without difficulty.

What I’m stumbling on is understanding the <relative path to photo> idea. 

For example, if I store a photo in the Quine 2 folder on my iPad, the app is telling me that the path to it is: 

On My iPad/Quine 2/IMG_3982.JPG

How do I translate this into what needs to go into the ‘_canonical_uri’ field? Just pasting it in as such doesn’t work.

I’m having the same trouble getting the path to a JPG that I’ve stored on the iCloud Drive. 

The way I was finally able to get a “proper” pathname into the ‘_canonical_uri’ field was to open iCloud Drive in my Safari browser and copy the full pathname of the photo from there. That worked like a charm, but the link text is a lot longer than I think it should be. (The length of the link text may be a red herring though!!)

May I have a hint or two, please?

Thanks,

-Linda B.

[Linda Bayley]

Maki Aea, thanks for your reply! I think I’m missing something major though.

Using your instructions and paying closer attention to the “permissions”, I was able to create an image tiddler like so:

This displays the photograph when I click on the check mark.

But in attempting to reference my Standing Goose tiddler, the photo is rendering as a little blank square:

The photo in question is currently stored in the Quine 2 folder of my iPad. I still haven’t figured out how to reference the iCloud without copying the link from within the Safari browser.

This method worked perfectly with an image where the full path (as copied from Safari) is plugged into the _canonical_uri field.

What am I missing? I feel like it must be something obvious.

-Linda B.

Sent from my iPad

On Dec 19, 2020, at 4:08 AM, maki aea <ma...@makiaea.org> wrote:

hi linda, i've a demo of the relative path method at http://makiaea.org/00045/20201205makiaea-anwiki#images%20in%20tiddlywiki

hth, i was recently trying to find out the same thing as you too and the relative path method, as chris says, seems to be the easiest as you and are both using icloud

--
You received this message because you are subscribed to a topic in the Google Groups "Quine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/quine-app/5NQ1WnP0NSw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to quine-app+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quine-app/9ca2b25c-c1d2-464c-9804-55806490efbcn%40googlegroups.com.

[Quine]

Hi Linda, Maki,

Links to external files are implemented using the “relative path” for a two major reasons:

1. The full file paths on most systems are too long to be practical in full - so it hard to get them right

2. The full file paths will change from system to system - so they won’t work as links as you go from system to system

“Relative path” is the path of the file “relative” to your wiki, using notation like “myImage.png” or “./myImage.png“ to refer to a file in the same folder as your wiki; or “images/myImage.png“ and “./images/myImage.png” to refer to a file in an “images” sub-folder of the folder where you wiki resides.

In testing this now I realize that I should have allowed you to use “/myImage.png” and “/images/myImage.png” also. For now those won’t work - but I’m in the middle of a new code revision, so I’ll add support for those as part of the revision.

For Linda’s “Standing Goose” example, be careful not to confuse [ext[...]] with [img[...]].  See https://tiddlywiki.com/#Linking%20in%20WikiText and https://tiddlywiki.com/#Images%20in%20WikiText - and make sure that you are referencing a valid file or tiddler. It appears that you are trying to reference an image tiddler, rather than an external file (since you don’t include a file extension in [img[Standing Goose]].

Does this help?

Chris.

P.S  and FYI - the “Full Path” shown in the “File Information” window is NOT the “absolute” path; because the “absolute” path would be too long, and not useful. As in the Files App, I’ve shortened the “absolute” path, and I use a similar notation to that in Files App. Those strings cannot be used to link to a file; they are just there to help you know where your wiki resides, in terms of which file system, and which sandbox. 

[Quine]

Linda,

I just re-read your “Standing Goose”...you should be able to transclude the “Standing Goose” canonical tiddler, provided that “Standing Goose” is working. 

Here’s my version:

Chris.