Qestions about abegoExtensions

[wolfgang]

I am repeatedly amazed at the capabilities of the plugins of Udo.
Therefore I suspect some real gems between them. For example, I just
started to use IntelliTaggerPlugin for use with the IncludePlugin -
dropdown tagging just becomes to much when loading some big TW. And
again ... what a surprise.

Therefore my further search for gems with some basic questions:

1) Since the current version of TiddlyWiki supports parameters - what
for I still would use the TiddlerWithParamsPlugin? Does it have some
additional features not included in the core? If yes, what are they?
If not, from which TW version onward this plugin became obsolete?

2) Same about the XHTML10Plugin - since TW is XHTML compliant, what
would be this plugins use? From which TW version onward this plugin
would make sense? What are the advantages of being XHTML compliant?

3) The DataTiddlerPlugin in combination with the FormTiddlerPlugin
makes it possible to create text input fields and saves the entries -
as in the example of the ContactFormTemplate. How would it be possible
to divide this ContactFormTemplate into a edit and view version (with
just the display and no input fields)? How would the code look like,
for example with the NewPluginTemplate at TiddlyVault? (for making the
links clickable which show up after searching for a particular plugin)

4) Is there any way or trick for being able to make systemConfig
tiddlers loaded with the IncludePlugin functioning Plugins?

5) Some time ago I read in a thread about being able to edit Tiddler
of included TWs from within the main TW. Does anyone remember in which
thread this was mentioned?

Enough questions for now ;-)

Regards,

W.

[wolfgang]

Didn't lasted very long and I've got another question:

I actually prefer to have tags invisible and usually use TaggerPlugin
with a toolbar item for toggling tags instead.

How would be the code in the ViewTemplate to have IntelliTaggerPlugin
have such a toolbar command?

W.

[schilke]

> 5) Some time ago I read in a thread about being able to edit Tiddler
> of included TWs from within the main TW. Does anyone remember in which
> thread this was mentioned?

I'm quite sure you're talking about "editIncludedTiddler command"
http://groups.google.com/group/TiddlyWiki/msg/95d2990ca8388c6c

HTH

--s

[wolfgang]

No, it isn't in this thread, but was posted maybe a month or so ago.
The difference being in being able to edit an external tiddler from
within a TW and experimental stuff not placed directly on
abegoExtention's page, but a sub directory instead.

W.

[Udo Borkowski]

1) Since the current version of TiddlyWiki supports parameters - what
for I still would use the TiddlerWithParamsPlugin? Does it have some
additional features not included in the core? If yes, what are they?
If not, from which TW version onward this plugin became obsolete?

As part of my contribution to TiddlyWiki I moved the main feature of the "TiddlerWithParamsPlugin" into the TiddlyWiki core code. The plugin contains some less frequently used features like the "asText" and "prefix:" options.

2) Same about the XHTML10Plugin - since TW is XHTML compliant, what
would be this plugins use? From which TW version onward this plugin
would make sense? What are the advantages of being XHTML compliant?

I assume the XHTML10Plugin is "obsolete" now as the latest versions of TiddlyWiki store in an XHTML compliant way (since 2.2). XHMTL compliance simplifies processing the HTML file using other (XML based) tools.

4) Is there any way or trick for being able to make systemConfig
tiddlers loaded with the IncludePlugin functioning Plugins?

Not that I know of.

5) Some time ago I read in a thread about being able to edit Tiddler
of included TWs from within the main TW. Does anyone remember in which
thread this was mentioned?

As schilke already mentioned,  the only thing I can think of is the "editIncludedTiddler command"
http://groups.google.com/group/TiddlyWiki/msg/95d2990ca8388c6c.

You can have a look at http://tiddlywiki.abego-software.de/ and search for "beta": In the search you will see some tiddlers from "Beta.html". If you open one of these ( e.g. "BetaZone") and click the "goto" button you will see how the plugin behaves: it open a new Tab/window with "Beta.html" (of cause you cannot edit the online version, but you will get the idea)

Udo

----------
Udo Borkowski
http://www.abego-software.de

[FND]

> As part of my contribution to TiddlyWiki I moved the main feature of the
> "TiddlerWithParamsPlugin" into the TiddlyWiki core code.

> [snip]

> I assume the XHTML10Plugin is "obsolete" now

Would you mind adding a corresponding note to these plugins' descriptions?
Thanks!

-- F.

[schilke]

> I assume the XHTML10Plugin is "obsolete" now as the latest versions of
> TiddlyWiki store in an XHTML compliant way (since 2.2). XHMTL compliance
> simplifies processing the HTML file using other (XML based) tools

probably the details belong to the dev group more or less, so I'll
just add a little comment here.
I don't know what the plugin does exactly, but regarding the "strict"
declaration in the current version there might be some work left - see
here: "This page is not Valid XHTML 1.0 Strict! Result: Failed
validation, 4 Errors"
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Ftiddlywiki.com%2F

--s

[FND]

> but regarding the "strict"
> declaration in the current version there might be some work left

There's plenty of work left; for one thing, the validator there does not
check the JavaScript-generated source.
(Not to mentions stuff like BR tags... )

However, things like custom attributes (extended fields), while not
(X)HTML-compliant, are an essential part of TiddlyWiki. That was a
conscious decision a while back, so TiddlyWiki will probably never be
fully valid (X)HTML.

But you're right; this is a discussion for [twdev] (there's probably
already something on that over there... )

-- F.

[schilke]

> There's plenty of work left; for one thing, the validator there does not
> check the JavaScript-generated source

no question - that's totally clear and

> (Not to mentions stuff like BR tags... )

aren't really critical...

> However, things like custom attributes (extended fields), while not
> (X)HTML-compliant, are an essential part of TiddlyWiki. That was a
> conscious decision a while back, so TiddlyWiki will probably never be
> fully valid (X)HTML.

yep, that's exactly what I thought. But to be honest: I don't have a
problem with it as I personally rarely would use a TiddlyWiki for true
web publishing - even not in that current web2.0 (aka-full-blown-WAI-
compliant-AJAX-javascript-hype) era ;)

TW is a perfect tool for use in controlled environments though - and
for many (endless) purposes.

--s

[wolfgang]

Thanks for the straightforward answers:

On 2 Okt., 09:21, "Udo Borkowski" <udo.borkow...@googlemail.com>
wrote:

> > 1) Since the current version of TiddlyWiki supports parameters - what
> > for I still would use the TiddlerWithParamsPlugin? Does it have some
> > additional features not included in the core? If yes, what are they?
> > If not, from which TW version onward this plugin became obsolete?
>
> As part of my contribution to TiddlyWiki I moved the main feature of the
> "TiddlerWithParamsPlugin" into the TiddlyWiki core code. The plugin contains
> some less frequently used features like the "asText" and "prefix:" options.
>
> 2) Same about the XHTML10Plugin - since TW is XHTML compliant, what
>
> > would be this plugins use? From which TW version onward this plugin
> > would make sense? What are the advantages of being XHTML compliant?
>

> I assume the XHTML10Plugin is "obsolete" now as the latest versions of
> TiddlyWiki store in an XHTML compliant way (since 2.2). XHMTL compliance

> simplifies processing the HTML file using other (XML based) tools.

>
> 4) Is there any way or trick for being able to make systemConfig
>
> > tiddlers loaded with the IncludePlugin functioning Plugins?
>
> Not that I know of.
>

I think PrinceTW of BramChen uses LoadExtPlugin:
"allows you to load external extensions from the file lists
(named .js) within those tiddlers taged with "ExtList"."

I guess this plugin actually loads external .js files as loaded
Plugin. Sadly, documentation is very sparse at PrinceTw - but maybe
there might be a similar solution for IncludePlugin? (just an idea,
without knowing about all the issues involved)

>
> 5) Some time ago I read in a thread about being able to edit Tiddler
>
> > of included TWs from within the main TW. Does anyone remember in which
> > thread this was mentioned?
>
> As schilke already mentioned, the only thing I can think of is the
> "editIncludedTiddler command"http://groups.google.com/group/TiddlyWiki/msg/95d2990ca8388c6c.
>

> You can have a look athttp://tiddlywiki.abego-software.de/and search for

> "beta": In the search you will see some tiddlers from "Beta.html". If you

> open one of these (e.g. "BetaZone") and click the "goto" button you will see

> how the plugin behaves: it open a new Tab/window with "Beta.html" (of cause
> you cannot edit the online version, but you will get the idea)
>
> Udo
>

Actually it was in the "includePlugin edit suggestion" thread.
(http://groups.google.com/group/TiddlyWiki/browse_thread/thread/
4bbc6e0191b12373/0a484ca417f5c474?lnk=gst&q=edit
%2Binclude&rnum=29#0a484ca417f5c474)
And yes, I misunderstood it then - actually it talked already there
about the editIncludedTiddler command.

So at the moment there remains only this more practical question about
IntelliTaggerPlugin:

>
> I actually prefer to have tags invisible and usually use TaggerPlugin
> with a toolbar item for toggling tags instead.
>
> How would be the code in the ViewTemplate to have IntelliTaggerPlugin
> have such a toolbar command?
>
> W.

Any suggestion?

Regards,

W.

[wolfgang]

;-)

> ... So at the moment there remains only this more practical question about...
> ...
> ... Didn't lasted very long and I've got another question:
> ...

> 3) The DataTiddlerPlugin in combination with the FormTiddlerPlugin
> makes it possible to create text input fields and saves the entries -
> as in the example of the ContactFormTemplate. How would it be possible
> to divide this ContactFormTemplate into a edit and view version (with
> just the display and no input fields)? How would the code look like,
> for example with the NewPluginTemplate at TiddlyVault? (for making the
> links clickable which show up after searching for a particular plugin)

This would be the location of NewPluginTemplate where I would want
view - instead of editable text fields - and therefore clickable:

http://tiddlyvault.tiddlyspot.com/#NewPluginTemplate

W.

[Ken Girard]

With the following setup I have editable fields from the moment the
tiddler is started, the choice of which fields utilize TW formating,
and a means to make the section look unique. It requires the
HideWhenPlugin (http://mptw.tiddlyspot.com/#HideWhenPlugin).

1) In the EditTemplate (I use <<newTiddler label:'Add new request'
title:'Req#-Co-City,State' tag:'workingOn' tag:'Training' text:'words
words words'>> to start these tiddlers):
<div macro="showWhen tiddler.tags.contains('Training') ||
tiddler.title
== 'Req#-Co-City,State'"> [[TrainingTemplateEdit]]</div>

2) In the ViewTemplate:
<div macro="showWhenTagged Training">[[TrainingTemplateView]]</div>

3) In the TrainingTemplateEdit tiddler:
<div class='ctsent'>
Assigned to: &nbsp;<span macro='edit assignedto'></span> <br />
Sent AP: &nbsp;<span macro='edit agreepackdate'></span> &nbsp; <span
macro='edit agreepack'></span><br />
Sent TM: &nbsp;<span macro='edit trainmaterialdate'></span>
&nbsp;<span macro='edit trainmaterial'> </span> <br />
Sent PM: &nbsp;<span macro='edit participantmaterialdate'> </
span>&nbsp; <span macro='edit participantmaterial'> </span>
</div>

4) In the TrainingTemplateView tiddler (Note that the 'assignedto'
field accepts TW formating):
<div class='ctsent'>
Assigned to: &nbsp;<span macro='view assignedto wikified'> </span>
<br />
Sent AP: &nbsp;<span macro='view agreepackdate'> </span> &nbsp; <span
macro='view agreepack'> </span><br />
Sent TM: &nbsp;<span macro='view trainmaterialdate'> </span> &nbsp;
<span macro='view trainmaterial'> </span><br />
Sent PM: &nbsp;<span macro='view participantmaterialdate'> </span>
&nbsp; <span macro='view participantmaterial'> </span>
</div>

5) In StyleSheet:
.ctsent {
background: ColorPalette::PrimaryPale;
color: ColorPalette::Foreground;
border: 1px solid #800;
padding: 5px}

Hope this helps answer some of your questions about custom fields.
I also hope GoggleGroups doesn't mangle the code to badly. :-)

Ken Girard

[Udo Borkowski]

> 4) Is there any way or trick for being able to make systemConfig
>
> > tiddlers loaded with the IncludePlugin functioning Plugins?
>
> Not that I know of.
>

I think PrinceTW of BramChen uses LoadExtPlugin:
"allows you to load external extensions from the file lists
(named .js) within those tiddlers taged with "ExtList"."

I guess this plugin actually loads external .js files as loaded
Plugin. Sadly, documentation is very sparse at PrinceTw - but  maybe
there might be a similar solution for IncludePlugin? (just an idea,
without knowing about all the issues involved)

If you have your plugin code in a separate .js file you may just "include" it using a standard JavaScript <script> tag in your MarkupPostBody tiddler. A script tag may look like this:

<script src="plugins/MySamplePlugin.js" language="javascript" type="text/javascript"></script>

This approach should work fine for most plugins.

[Udo Borkowski]

> I actually prefer to have tags invisible and usually use TaggerPlugin
> with a toolbar item for toggling tags instead.
>
> How would be the code in the ViewTemplate to have IntelliTaggerPlugin
> have such a toolbar command?
>
> W.

Any suggestion?

I just added a new "IntelliTagsEdit" command plugin to my website to cover this.

Have a look at:

     http://tiddlywiki.abego-software.de/#IntelliTagsEditCommandPlugin

Install that plugin (beside the IntelliTaggerPlugin ( http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin)).

Then add the command intelliTagsEdit into the 'macro' attribute of the 'toolbar' <div...> in your ViewTemplate.

Example:

<div class='toolbar' 
        macro='toolbar -closeTiddler closeOthers +editTiddler intelliTagsEdit permalink references jump'>
</div>

This adds a "tags" button to the toolbar of the tiddlers (next to the edit button). Pressing the "tags" button will open the input field for the tiddler's tags and let you edit the tags with all the IntelliTaggerPlugin features.

[wolfgang]

Thanks Ken, for this detailed explanation. Though till now I solved
this difficulty by converting data fields into slices. Still - I'll
try your suggestion, once I find the time..

Regards,

W.

[wolfgang]

On 3 Okt., 12:39, "Udo Borkowski" <udo.borkow...@googlemail.com>
wrote:

> > > 4) Is there any way or trick for being able to make systemConfig
>
> > > > tiddlers loaded with the IncludePlugin functioning Plugins?
>
> > > Not that I know of.
>
> > I think PrinceTW of BramChen uses LoadExtPlugin:
> > "allows you to load external extensions from the file lists
> > (named .js) within those tiddlers taged with "ExtList"."
>
> > I guess this plugin actually loads external .js files as loaded
> > Plugin. Sadly, documentation is very sparse at PrinceTw - but maybe
> > there might be a similar solution for IncludePlugin? (just an idea,
> > without knowing about all the issues involved)
>

> If you have your plugin code in a separate .js file you may just "include"
> it using a standard JavaScript <script> tag in your MarkupPostBody tiddler.
> A script tag may look like this:
>
> <script src="plugins/MySamplePlugin.js" language="javascript"
> type="text/javascript"></script>
>
> This approach should work fine for most plugins.
>
> Udo

So does this mean to include Plugins functioning is only possible with
a file ending as .js?
Though there might be the same content as with a html?

On 3 Okt., 16:08, "Udo Borkowski" <udo.borkow...@googlemail.com>
wrote:

> > > I actually prefer to have tags invisible and usually use TaggerPlugin
> > > with a toolbar item for toggling tags instead.
>
> > > How would be the code in the ViewTemplate to have IntelliTaggerPlugin
> > > have such a toolbar command?
>
> > > W.
>
> > Any suggestion?
>
> I just added a new "IntelliTagsEdit" command plugin to my website to cover
> this.
>
> Have a look at:
>
> http://tiddlywiki.abego-software.de/#IntelliTagsEditCommandPlugin
>

> Install that plugin (beside the IntelliTaggerPlugin (http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin)).

>
> Then add the command intelliTagsEdit into the 'macro' attribute of the

> 'toolbar' <div...> in your ViewTemplate <javascript:;>.
>
> *Example:*

>
> <div class='toolbar'
> macro='toolbar -closeTiddler closeOthers +editTiddler
> intelliTagsEdit permalink references jump'>
> </div>
>
> This adds a "tags" button to the toolbar of the tiddlers (next to the

> *edit*button). Pressing the "tags" button will open the input field

> for the
> tiddler's tags and let you edit the tags with all the

> IntelliTaggerPlugin<http://tiddlywiki.abego-software.de/#IntelliTaggerPlugin>features.
>
> Udo
>

Great! Thanks for this fast addition to the IntelliTaggerPlugin.

Regards,

W.

[Udo Borkowski]

So does this mean to include Plugins functioning is only possible with
a file ending as .js?

Theoretically the file does not need the ".js" ending, but can have any ending (like ".txt" or so). It is just necessary the file contains valid JavaScript code.

Practically most times these files will end with ".js", just to indicate they contain "JavaScript" contents.