search

TiddlyWiki / TiddlyWiki5

A self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc.
https://tiddlywiki.com/
Other
8.09k stars 1.19k forks source link

Export as plugin in export options #1232

Open danielo515 opened 9 years ago

danielo515 commented 9 years ago

Adding the ability to export a list of tiddlers as a plugin tiddler will address many problems, and makes perfect sense:

tobibeer commented 9 years ago

For theme creation: people without coding or node skills can just export their customizations as a theme

Perhaps difficult to manage in the long run. Where did you (/ I) get that theme from? Does the author maintain it? Updates?

For content sharing: you can export a bunch of tiddlers from any wiki and then can import them without polluting your wiki because they are all contained within a plugin tiddler.

That's a good usecase, especially for things like "let me bundle all those wikitext tiddlers on TiddlyWiki.com and give that bundle a name". I'll test what happens with shadows that are not under $:/foo ...and if they show up on the timeline, etc... I'd think they probably do.

This is also useful as snapshot mechanism. We can also add a button to this kind of plugins called "unpack plugin tiddlers" to make those tiddlers part of your tw.

I think that sounds like a good idea, if only to get rid of that "bundle" / plugin you no longer need in its original form, as you want to so heavily modify it, that the original shadows are of no use to you. Not sure if that needs to be part of the core and where to put that functionality / how... as an $action?

It will resolve the problem of not being able to export multiple tid files

That doesn't sound correct, though. With 5.1.5 you can export multiple tids from the Advanced Search / filter tab.

danielo515 commented 9 years ago

Perhaps difficult to manage in the long run. Where did you (/ I) get that theme from? Does the author maintain it? Updates?

Why that even matters? I'm talking about a export feature, not a "themes sharing platform". I used to create themes for myself. Is that enough reason?

That doesn't sound correct, though. With 5.1.5 you can export multiple tids from the Advanced Search / filter tab.

If you select to export a bunch of tiddlers as .tid format you onle get ONE. Try it out.

tobibeer commented 9 years ago

If you select to export a bunch of tiddlers as .tid format you onle get ONE. Try it out.

  1. http://tiddlywiki.com/#%24%3A%2FAdvancedSearch
    • tab: Filter
  2. enter [tag[WikiText]]
  3. click export button
    • chose format of your liking
  4. view neat static results or import as json into another wiki

  5. works just fine

    I used to create themes for myself. Is that enough reason?

It is, and I believe the above method does make it rather easy to achieve within TiddlyWiki 5.1.5.

Jermolene commented 9 years ago

Hi @danielo515 that's an excellent idea. The only detail to figure out is how the user would configure the fields that go on the plugin tiddler itself (title, description, type, plugin-type, plugin-priority etc.). The approach taken by the current support for building plugins in the browser is to use a sort of skeleton tiddler:

http://tiddlywiki.com/dev/#How%20to%20create%20plugins%20in%20the%20browser

It's not clear how the user would choose the skeleton tiddler when performing the export.

danielo515 commented 9 years ago

Hello @Jermolene

The only detail to figure out is how the user would configure the fields that go on the plugin tiddler itself

I find that TW tends to do too many things in "background" for my taste. Looks we are scared of forms, popups or any kind of UI. This is a good example. Rather than having an options panel or a simple form for selecting those values we have to configure a skeleton tiddler that TW will use. You will only do that if someone tell you, there is no way to figure it out. This happens in many places like the codemirror plugin, how stylesheets are managed... Seems like tiddlywiki prefers a tacit interaction with the user, where the user "leaves something at some place" and tiddlywiki "takes it at somepoint and do something with it".

In my opinion is nothing wrong in using a modal popup with a simple and user friendly form with some drop-downs. Click on export as plugin, fill the form, you have it!

tobibeer commented 9 years ago

In my opinion is nothing wrong in using a modal popup with a simple and user friendly form with some drop-downs. Click on export as plugin, fill the form, you have it!

Sounds neat... but I hink there's a good chance you want to save that as some form of configuration so that you an rerun that packaging job again later.

pmario commented 7 years ago

@Jermolene .. imo should be labeled "feature request"