Splitting Content into multiple TiddlyWiki Files

[H]

I feel like an idiot for even having to ask this question, but I've
been searching and reading and can't find the solution.

I have two family websites, one started with my first child, then the
second child got another one. Each has a page/tiddler with links to
photo albums, but some photo albums contain both children. Rather
than having to update the [[Photos]] tiddler in both File1.html and
File2.html, is it possible to move the [[Photos]] tiddler to
File3.html and then just have File1 and File2 pull the content from
File3?

I'm also looking to do this as a solution to keep the initial load
times down for folks by keeping "current" content in a primary
tiddler, and keep older content in a different tiddler that only gets
loaded if it's needed.

Thanks in advance.

- H

[Amzg]

I'm not 100% sure I understand your question, (is "a website" a TW, or
perhaps a tiddler? Is a file.html also a TW? etc) but here are some
bits that just might be of value anyway:

You could perhaps use the IncludePlugin. This allows you to view (but
not edit) tiddlers from another TW.

You could create a new TW (I guess this is what you refer to as
"File3.html") and simply import all the tiddlers you want from the
other two TWs.

Maybe you'd have some use of the <<tiddler>> command, i.e you could
create a new tiddler and write <<tiddler [[photos1]]>><<tiddler
[[photos2]]>> to display the contents of both those tiddlers in the
new tiddler.

If you have separate files, maybe FramedLinksPlugin would be of value.
It allows you to open an iframe directly in the tiddler content, i.e
you could display another full separate TW from within a tiddler.

Hope that provided at least something.

/Mat

[H]

Sorry for the confusion, but yes,each "web site" is a TW. And after
going to tiddlytools.com and poking around I think I found the
solution -- ExternalTiddlersPlugin.

IncludePlugin is what I was thinking or and searching for originally,
but I couldn't remember the name or seem to hit on the correct search
terms. After going to Eric's site I stumbled upon
ExternalTiddlersPlugin today along with FramedLinksPlugin, the latter
being VERY cool.

I was originally thinking of sharing a tiddler from TW3 with TW1 and
TW2, but with the ExternalTiddlersPlugin it got even easier. I will
just add the line <<tiddler "http://xxx.com/TW1.htm#Photos''>> to
[[Photos]] in TW2 and vice versa, then both will share each other's
content without needing to even introduce or share a third TW. Adding
TW3 is still an option for keeping file sizes down, but for the moment
ExternalTiddlersPlugin gets it done perfectly -- and with one line of
'code'.

I love TiddlyWiki and the extensions folks have developed and shared.
Thanks for the help.

[Eric Weir]

I haven't' been paying close attention, but I understand there are some
problems using TiddlyWiki in Firefox 3.0. I'm using 2.0.0.16 at the
moment, and it keeps pestering me to upgrade to 3.0.

I'm just starting to seriously use TiddlyWiki, I'm not a techie, and at
this point I'd like to avoid any unnecessary challenges. Should I
upgrade or not?

Thanks,
------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eew...@bellsouth.net

[Eric Shulman]

> I was originally thinking of sharing a tiddler from TW3 with TW1 and
> TW2, but with the ExternalTiddlersPlugin it got even easier.  I will
> just add the line <<tiddler "http://xxx.com/TW1.htm#Photos''>> to
> [[Photos]] in TW2 and vice versa, then both will share each other's
> content without needing to even introduce or share a third TW.

This won't work, and will, in fact, create an infinite recursion that
will require you to 'kill' and restart your browser process...

Consider: starting with the <<tiddler>> macro in TW1#Photos, the
ExternalTiddlerPlugin transcludes content from TW2#Photos and renders
it. However, TW2#Photos also contains a <<tiddler>> macro that
transcludes and renders TW1#Photos... which, once again, transcludes
and renders TW2#Photos... etc, ad infinitum.

Unfortunately, automatically detecting and preventing these kinds of
circular references between tiddlers in separate files is extremely
difficult (but perhaps not completely impossible).... I have to think
about it for a bit...

In any event, for the time being you should go with your first idea...
i.e., TW1#Photos and TW2#Photos both transclude and render content
from a separate, shared TW3#Photos tiddler.

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[Anthony Muscio]

No problems for me with the portableFirefox see portableapps.com, little bit of fiddling for tiddlysnip, but otherwise fine.

 

Using portable firefox will allow you to avoid instalation or replacement of your current version and live it before commiting.

 

Tony

 

[Simon Baird]

As far as I know there are two issues:

1. Every time you save it asks you to "allow unsafe actions" for script. If you tick "remember this decision" it doesn't remember. It's annoying but not a show stopper.

2. If you import from a local TW file the "Browse" dialog for selecting a file is broken in such a way that it discards the path of the file you select. The work around is to type the path in manually or to only import from files in the same folder.

Anyway I'm using FF3 and TW and it's not so bad. Presumably these will be fixed in FF 3.1. Anyone got more? Is this info in the wiki somewhere?

Simon.

--
simon...@gmail.com

[Eric Shulman]

> 2. If you import from a local TW file the "Browse" dialog for selecting a
> file is broken in such a way that it discards the path of the file you
> select. The work around is to type the path in manually or to only import
> from files in the same folder.

I have a *fix* for this
http://www.TiddlyTools.com/#CoreTweaks
(see tweaks for tickets #683 and #604)
Basically, the tweak automatically replaces the standard "browse"
button in the ImportTiddlers wizard, so that it uses a secure, FireFox-
native 'file picker' dialog that *does* allow TW to have full access
to the selected path/filename. Note that this tweak is only applied
for FireFox... IE, Safari, and other 'non-Gecko' browsers continue to
use the standard "browse" button, which still works properly in those
browsers.

> Anyway I'm using FF3 and TW and it's not so bad. Presumably these will be
> fixed in FF 3.1.

The FireFox developers made the "browse" button change deliberately,
in order to address a potential security risk in which a remote
website could 'probe' your local filesystem by tricking you into
selecting a file, thereby revealing information about the directory
structure on your hard drive. I really don't expect them to change
their minds in a future release.

Even so, regardless of these minor issues, I recommend upgrading to
FF3, if only for two reasons:
* MUCH faster javascript execution
* MUCH better memory management

-e

[FND]

> ExternalTiddlersPlugin [...] IncludePlugin

FWIW, those are also listed on the community wiki:
http://www.tiddlywiki.org/wiki/Including_External_Content

-- F.

[FND]

> Discussion subject changed to "Firefox 3" by Eric Weir

Please don't reply to an existing thread when creating a new topic.

> Every time you save it asks you to "allow unsafe actions" for script.
> If you tick "remember this decision" it doesn't remember. It's annoying
> but not a show stopper.

I'm not experiencing this issue (FF3 on Ubuntu).

> Is this info in the wiki somewhere?

Yup:
http://www.tiddlywiki.org/wiki/Firefox_3

-- F.

[M)]

> > Every time you save it asks you to "allow unsafe actions" for script.
> > If you tick "remember this decision" it doesn't remember. It's annoying
> > but not a show stopper.

I believe ticking "remember this decision" is a good idea. It feels
like FF3 is recognizing different script actions by TW (e.g., save
changes, import plugin and there could be more (I am not a programmer
thus unable to understand it well)). By ticking the selection, the
next time that same script is called, it will be remembered.

M)

[M)]

> the next time that same script is called, it will be remembered

*during that session.

[IanO]

The best reason not to go to FF 3.0 is that it breaks the add in
FireBug.
Other addins are also broken by this version.
I wish there had been a warning of which Add-ons would not work
before I did the upgrade.

ymmv,
IanO

[FND]

> The best reason not to go to FF 3.0 is that it breaks the add in
> FireBug.

It does not; there's been a working beta pretty much right from the
start, and v1.2 final has now been officially released:
http://ejohn.org/blog/firebug-12-released/

-- F.

[danie...@gmail.com]

On 8/30/08, IanO <Ian...@gmail.com> wrote:
>
> The best reason not to go to FF 3.0 is that it breaks the add in
> FireBug.
>

I really miss RePaginate too.

--
Daniel Baird
/to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/
...optimise your regexes, people!

[DrCory]

I have had this problem with the Firefox 3 also. Thanks for the heads-
up. I had actually gone back and downloaded Firefox 2 because it
didn't have that problem. I will still use 2 to download from the web
till 3 is fixed

DrCory
drcory.tiddlyspot.com

On Aug 28, 7:32 pm, "Simon Baird" <simon.ba...@gmail.com> wrote:
> As far as I know there are two issues:

[Eric Weir]

On 8/28/2008 Eric Shulman wrote:

> > 2. If you import from a local TWfile the "Browse" dialog for selecting a

> >> file is broken in such a way that it discards the path of the file you
> >> select. The work around is to type the path in manually or to only
import
> >> from files in the same folder.
>
> I have a *fix* for this
> http://www.TiddlyTools.com/#CoreTweaks
> (see tweaks for tickets #683 and #604)
>
> Basically, the tweak automatically replaces the standard "browse"
> button in the ImportTiddlers wizard, so that it uses a secure,
> FireFox-> native 'file picker' dialog that *does* allow TW to have full
> access to the selected path/filename.

So, Eric, how do I use this?

I take it I'm not meant to install all the tweaks in the CoreTweaks
tiddler, just the ones needed to fix this problem. #604 looks like a
plugin. I put it in a tiddler, give it the title of the plugin, tag it
with systemConfig? Not sure about #683.