[tw5] Re: Volant update: Volant-Rapid Add-on Announcement

[admls]

Hi @TiddlyTweeter,

But my point is in all modes, in all combos, your gizmo functions. Good 
> news!
>

That is good news! Though, perhaps we should amend that to: "... your gizmo 
functions... for the time being." As I'll no doubt break everything as the 
lot of plugins go on changing and developing!

I'm glad you're getting some use out of it!

Best wishes,

admls

On Tuesday, March 26, 2019 at 7:22:21 PM UTC, @TiddlyTweeter wrote:
>
> I have an interesting situation that is interesting.
>
> Windows 10 pure touchscreen tablet + keyboard + mouse. Yeah. I have too 
> much money. 
>
> I tested the 3 combos of tablet only, + keys + mouse.
>
> But my point is in all modes, in all combos, your gizmo functions. Good 
> news!
>
> On Monday, 25 March 2019 18:59:22 UTC+1, admls wrote:
>>
>> Hi Everybody,
>>
>> Per Mohammad's request, I've added the ability for volant tiddlers to 
>> snap to the edges. Simply move position the tiddler so that it overlaps an 
>> edge of the screen. I thought this was an interesting idea when Mohammad 
>> suggested it but wasn't prepared for just how much I would like it. 
>>
>> The Volant-Rapid add-on will probably see some development in the future. 
>> But for now, even the simple implementation is pretty handy. 
>>
>> The repo is here: https://github.com/admls/Mentat
>> And the demo is here: https://admls.github.io/Mentat/
>>
>> Best wishes,
>>
>> Adam (admls)
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e41b052d-f185-4c5b-bf83-23e44674924b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Volant update: Volant-Rapid Add-on Announcement

[admls]

Hi Jan,

I think I may have misunderstood about the snapping issue. I thought you 
were referring to snapping to the edges of the viewport but it seems like 
you are referring to the snap-to-grid native to the Volant plugin. If you 
want to turn off the snapping to grid, go to the Volant config menu and 
enter 0 in the boxes that talk about grid-size (and maybe also grid-gap).

Hi Mohammad,

I only experienced JS red window error if left or right border cross the 
> the other one, means when you try to make widow width zero!
> I think this should not be that difficult to be resolved!
>

I think I've got those errors resolved now. Should be out for the next 
release.

When you double clicked anything inside a window, a new tiddler is created 
> with the below title:
> $:/plugins/admls/volant-rapid/ui/rapid-menu-popup
>

This is something I've been experimenting with but is far from ready for 
release. I thought I'd taken it out, but I guess I missed a tiddler or two. 
The next release will expunge it. Thanks for raising the issue on github!

When a lot number of tiddlers in a window, it seems the window title bar 
> cannot handles them correctly!
>

 From a performance standpoint, I would recommend not having too many open 
at once or setting the default storyview inside of window tiddlers to 
'zoomin'. You can do that in the Mentat config menu. That said, maybe your 
machine handles it just fine. I think you're probably right that a 
scrolling window tab bar would be better. I'm a little bit concerned with 
how it will affect dragging and dropping the tabs, but I'll experiment with 
it. Again, thanks for raising it on github!

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/db445ba7-0650-47f8-abe2-443e1e6670f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Volant update: Volant-Rapid Add-on Announcement

[admls]

Hi Mohammad,

I hope it works well for you!

Hi Julio,

Thank you! There will likely continue to be changes to these plugins for a 
while. So I hope that doesn't end up being too disruptive.

Hi Jan,

The snapmechanism causes an error when dragging corners out of the window 
>

Good catch. I should have that fixed for the next release.



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a7458da1-5e64-46ec-8857-0cea0ef9b719%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Repopup, Volant, Mentat

[admls]

Hi @TiddlyTweeter,

The pointy finger toggle for activating move/resize is AMBIGUOUS in that 
> its not entirely clear from its colour what state you actually activated.
>

In the latest release, the pointy finger toggle gets a border around it 
when its engaged. Good catch!

Ciao admls (tip: get a better name? :),
>

I'll have to think about that. 

-- On basic startup I can MOVE  "Welcome" with both finger and pen.
>
>
> -- I can RESIZE it with finger and pen. 
>
>
> -- Activate via Finger Pointer in floating sidebar and I can move and 
> resize the Sidebar too, though not before.
>
>
I've only done a really naive touch implementation at this point. I tried 
Hammerjs and it really bogged down my machine, so I just did something 
simple in the interim. But this is an issue that I'm very concerned with 
addressing when I get the time.

Hi Jan,

I just tried to start a blank Wiki with the Mentat-plugin only. 
>

At this point, Mentat depends on Volant, Engine depends on Volant, and 
Volant depends on Repopup. Mentat uses Engine as well, but I don't think it 
has to have it. I'll update the docs to make these dependencies clear.

Honestly, I did not anticipate the way you're using Mentat. So it wasn't 
made with that sort of thing in mind. I think that to do what you seem to 
be trying to do would require totally restructuring Mentat, probably 
splitting it into two plugins. I'm not sure what the best way to do that 
might be at this point or what the costs might be if I do. I need to give 
it some thought. I'd like to enable the kind of pinboard stuff you're 
doing, though I didn't make mentat with that in mind. I was thinking more 
along the lines of browser window instances inside of TW. So restructuring 
stuff to allow for pinboards within the classic storyview may take a bit of 
work, but I'll see what I can do when I get the chance!

Hi Birthe,

In the latest release, you have to go to Mentat Config, to Enable window 
> tabs. I really think they should be on by default, it makes everything 
> easier to understand.
>

I think you're right. The latest release has them turned on.

Best wishes,

admls (Adam)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5ce01704-82df-45a6-b554-a72aec948d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Volant update: Volant-Rapid Add-on Announcement

[admls]

Hi Everybody,

Per Mohammad's request, I've added the ability for volant tiddlers to snap 
to the edges. Simply move position the tiddler so that it overlaps an edge 
of the screen. I thought this was an interesting idea when Mohammad 
suggested it but wasn't prepared for just how much I would like it. 

The Volant-Rapid add-on will probably see some development in the future. 
But for now, even the simple implementation is pretty handy. 

The repo is here: https://github.com/admls/Mentat
And the demo is here: https://admls.github.io/Mentat/

Best wishes,

Adam (admls)

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b4cc67f9-dace-4add-9e2c-f89a6a4b3e57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Repopup, Volant, Mentat

[admls]

ut what you're doing? I don't really 
understand the use case; so I don't know how to design for that.

PS: Deciphering Names...Mentat is clear now ... is Volant inspired by 
> Mikhail *Bulgakov's The Master and Margerita?*
>

It's from Gene Wolfe's Book of the New Sun. I've heard The Maste and 
Margerita is an interesting one, but I've never read it, unfortunately.


Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5e407ba8-df0b-479a-a8fd-24a8681ea34a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Repopup, Volant, Mentat

[admls]

Hi Mohammad,

I've been using the history tiddlers of each plugin to track their changes. 
Do you mean one changelog for the whole system as well? That's a good idea. 
I could then simplify the history tiddler of each plugin and simply 
reference the main changelog. I'll get on that! Thanks, Mohammad!

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/59f425b6-9338-4389-a050-05fde797d29c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Selectable input fields - a work in progress

[admls]

Hi BTC,

This is fantastic! Is this coming to the core? It's such an intuitive ui 
feature that the lack of it in the core is pretty jarring.

Best wishes,

admls

On Monday, March 18, 2019 at 1:49:42 PM UTC, BurningTreeC wrote:
>
> BTC,
>>
>> I like it a lot because it simplifies coding. I'm an amateur. Give me a 
>> macro already.
>>
>
> everyone likes simple things
>
> there is a macro, it's called selectable-input, you call it 
> <> or <$macrocall $name="selectable-input"/>, the params 
> are described at the page, examples are given, the most complex example are 
> the $:/core/macros/tag-picker and the $:/core/ui/SideBarSegments/search 
> tiddlers which are customized to make use of the selectable-input macro
>
> I'm sure other useful macros can be built around it
>
>
>> Good things
>> Josiah
>>
>>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0abbaa9b-eac7-4997-810d-43baaccc09dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Repopup, Volant, Mentat

[admls]

Hi Everybody,

The new release of the Volant plugins are here. There are a number of bug 
fixes and added configurability in the Mentat config menu (if you're 
missing the resizers or window tabs, that's the place to look).

The biggest change is the addition of some very simple touch events. I 
haven't worked on adding other features yet. It may be a bit buggy as I 
haven't tested it thoroughly, but I thought I'd put it out there and let 
people take it out for a test drive. I also haven't updated the demo/docs 
to match the changes, yet. So beware.

By the nature of the thing, it still isn't suited to mobile. But it ought 
to be okay on something tablet sized.

The code is at https://github.com/admls/Mentat
And the demo is at https://admls.github.io/Mentat/

If there are any bugs, or feature requests, please raise them as issues on 
the github repo. That's a more convenient place for me to address them.

Best wishes,

admls


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fa62d5fd-e581-4279-8a6e-2eee28bf3a7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Everybody,

Here's the repo where you can raise these issues/bugs/feature requests on 
github: https://github.com/admls/Mentat

Sorry I neglected to post that earlier.

It would really help me if you could raise issues over there. This thread 
is getting bloated and it is sort of difficult to keep track of the 
separate issues, let alone reply to them separately. So please, if you have 
already raised an issue or a bug, or if you have any new issues or bugs or 
feature requests (and you have a github account), raise the issue on 
https://github.com/admls/Mentat

Best wishes,

admls



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b195a89e-acbb-4a4b-b5e7-1bede6a3d612%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi @Mohammad,

Many thanks on this admls. Please do not forget to have a look at 
w3.org (https://www.w3.org/TR/css-scroll-snap-1/)


Are you referencing this in connection to getting the volant tiddlers to 
snap to the side/top/bottom or is this a different feature you're looking 
for? I'm sorry, I don't entirely understand what you're getting at. Could 
you give me a description?

Also could you raise this as an issue on github if you have a github 
account? This thread is just starting to get cluttered.
Here's the repo:
https://github.com/admls/Mentat

Hi @Tony,

all for maximise, if you have a restore or intermediate window size so on 
> multi screen as maximise would consume both screens.
>

Maximize with volant would probably be similar to the way it is for Mentat. 
In mentat, you can maximize and restore down window tiddlers. You can also 
easily configure the location and dimensions of maximized windows. Just 
open $:/plugins/admls/mentat/config/set-maximized-values, position it 
(default volant functionality must be enabled), and hit the button. Then 
you can close that tiddler and any window you maximize will be maximized to 
that position. You can then hit restore down and it will return to its 
previous position. You can only have one maximized tiddler at a time 
however. 

In any case, you can set the maximized values to occupy just one screen. 
Any window you maximize will end up there.

However if I have tiddlers tagged as windows, but not in mentat view the 
> story river is as wide as the three screens (less the sidebar if displayed).
>
> It would be nice to be able to limit this width to one screen or less so 
> we can see both the left and right hand side of the story tiddlers in that 
> screen and leave the rest as a playground for other window tiddlers.
>

I just wanted to return to this issue you raised earlier. Mentat is 
intended to completely encapsulate all the other storyviews. If you are in 
mentat storyview, you can have your main story river in one window tiddler, 
and position that window to fill one monitor viewport. This will leave the 
other monitors open for whatever you want. You can archive your main story 
window in the mentat tab and return to it later. Or you can archive the 
layout or session to be able to switch to them quickly. In the mentat 
config, you can set the default storyview (classic, pop, zoomin) that will 
take place in new windows you create.

If you have Engine engaged as well, you can have the $:/Sidebar tiddler 
positioned wherever you see fit. The most basic configuration in Mentat 
would be one fullscreen window tiddler with the $:/Sidebar tiddler open to 
the side. This pretty much replicates the default page template.

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b6047908-ebce-49ff-ab2a-9f88836f7eb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi @TiddlyTweeter,

I originally came to TW as a solution for writing as well. In a lot of 
ways, that has driven the development of Mentat. Like you say, it still has 
a ways to go. But It would be great to get your feedback throughout the 
process.

Hi @Mohammad,

I was just planning on adding some hooks to the main plugins and then 
hooking in with addons. The mechanism you linked to is really fascinating. 
I'll have to give it a more thorough look.

I think the snap idea is great. It shouldn't be hard to add the minimal 
snap behaviors. Some of the more complex stuff will be trickier.

Hi @BTC,

I forgot to link to the repository!! https://github.com/admls/Mentat

Hi @Jan,

I think some of the editing problems will go away when maximize is added to 
volant. You'll be able to quickly maximize the tiddler to edit, then return 
it to its normal size.

$:/VolantAbsolute needs a lot of love. I've basically been focusing on the 
fixed $:/Volant functionality. But extended $:/VolantAbsolute functionality 
is coming.

I haven't experienced the resizing issues, but making the button bigger on 
hover sounds like a good idea. I'll check it out.


Best wishes,

admls


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e5692227-bec2-46af-8a26-0c0f71da74bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Tony,

I'm a little concerned about using a commenting solution like bimlas' 
disqus due to how much the plugins might change in the near future. I don't 
understand bimlas' plugin very well, but I'm a concerned about comments and 
threads getting lost if tiddlers get renamed/deleted. Do you think it would 
work to have it all on github, both formal and informal issues? Or do you 
see problems with that?

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/03aeedcd-89fd-470c-b500-341cb8a58284%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi BurningTreeC,

I hope I can bring a bit of my knowledge in where it's needed
>

That sounds excellent! There's no pressure of course, but if you want to 
collaborate on this, I'd really welcome it. The code is in an unfortunate 
state of not being well-commented, which may make it difficult to 
contribute to at the moment, but I need to resolve that anyway. Having 
looked at and admired your tiddlywiki work, I think we have similar enough 
ui instincts that we could probably collaborate pretty effectively. I have 
a notion of how to implement your dashboard-style 
drawing-a-new-tiddler-into-existence idea as an add-on to volant, for 
example. And I'm sure you see lots of things in volant, mentat, etc that 
could be improved upon. I'm very open to having my ideas and 
implementations critiqued; so don't be concerned on that score. I want to 
make as useful a piece of software as possible and learn as much as 
possible in the process. Collaborating with someone with a lot more 
experience than myself would be quite the boon.

In any case, no pressure. But if there's a way you can think of that I can 
facilitate your collaboration on this, I'd be happy to do so!

Best wishes,

admls



On Tuesday, March 19, 2019 at 10:40:16 AM UTC, BurningTreeC wrote:
>
> Hi Simon, Hi admls,
>> great, volant looks pretty like movable. You know how I longed for that!
>> Yours Jan
>>
>
> Movable is more a trial in finding usecases, volant achieves making the 
> functionality usable right away, the direction these plugins are going is 
> very pro-user, which I failed to achieve
>
> I hope I can bring a bit of my knowledge in where it's needed
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dc10dc92-a0bd-466e-a793-3ff021566850%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Jan,

Thank you! It has a long way to go yet, but I think it is promising! 

At the moment it doesn't seem to get touch-gestures (or is this my 
> browser/my tablet fault?)
>

You're right. That's definitely on my to-do list. I thought it would be 
best to get the desktop version out and see if there is enough interest 
before diving into mobile/touch features (as it is further outside my 
wheelhouse). 

Did you already explain on what mechanism you built this?
>

It's a widget that gets transcluded into tiddlers. The widget finds what 
tiddler it is in and adds a couple of eventListeners. Then there are some 
global modules that handle the event system. Then there's a storyview and 
another global to handle navigation in that storyview (since it is fairly 
complex). There's some unfortunate template mangling that happens along the 
way (hopefully, a more easily configurable template system will come along 
and this won't be necessary). And there's a hacky plugin for managing 
popups and dropdowns. That's the whole thing in a nutshell!

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d2013545-3fd5-485a-a7fe-6105046d1e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

 Hi Everybody,

Actually, if everybody with a github account could raise the issues on 
https://github.com/admls/Mentat that would be helpful. I'm already losing 
track of what needs to be looked at. Fine to raise it here too, of course, 
but please link to the issue on github. That will make it a bit easier for 
me to keep track and to keep the conversations separate instead of 
bombarding everyone with my responses to everyone else. If you don't have a 
github account, no worries. Just keep raising issues here in the forum. All 
issues welcome: bugs, feature requests, etc.

Best wishes,

adamls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7e91bc8e-88a2-4c66-b3ca-0cdf3dd9cadb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

es on them heavily, the ground might 
just shift beneath your feet. I know this isn't an ideal, but I think if 
something needs restructured in a big way, I'd rather do it sooner than 
later.

Also, remember to back up your wikis! I make no guarantees on that front 
(or any front).

Thanks for using my plugins!

Best wishes,

admls



-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/71c18f8d-564b-40ce-aaaf-8233d8cd3b9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Birthe,

The tagpill dropdown is hm let's say enormous. 
>
Wow. Yeah. You weren't kidding. That stylesheet makes some of the scrolling 
a little bit nicer on some of the dropdown boxes. The issue can be fixed by 
making width and height into max-width and max-height. 

The repopup plugin is a sort of hacked together thing. I think the core 
popup mechanism is in need of an overhaul, particularly if it is going to 
be used in tiddlers of a fixed size (due to overflow: scroll). Hopefully, 
the repopup plugin will get to be retired at some point. 

Importing your plugins to another Tiddlywiki using another palette makes 
> the plugin buttons invisible. ($:/Topbar and $:/Sidebar)
>
I don't understand exactly what is going on. Could you elaborate? I'm not 
sure what to do to reproduce the problem. What palette is it and which 
buttons?

As far as I can see, you have very few places that could be translated, but 
> even so it would be nice to have an easy way of doing that. You see, your 
> plugins are going to be VERY popular ;-)
>
Thank you! I hope they can be useful! I have given the issue of translation 
little to no thought. But I'll look into how that works!

Keep the issues comin', Birthe! I may not be very quick to correct them, 
but I hope to be able to keep improving things little by little! Thanks for 
running this thing through its paces!

Hi @BurningTreeC,

Thank you! I've really enjoyed and admired your work. As such, I'd love to 
hear what you think could be improved; what might make the Volant plugin, 
in particularly, stable and dependable enough to be a base for other 
plugins.

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/db8a42d7-10ca-401b-8c16-b9e14a706620%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Elijah,

I'm using TheDiveO's ThirdFlow plugin for the plugin development. 
<https://thediveo.github.io/ThirdFlow/> On the whole, it has been really 
awesome. But packaging up the tiddlers has been a bit buggy. I am working 
on getting it sorted out. Amongt other issues, the ThirdFlow automatically 
packages every tiddler prefixed with $:/plugins/admls/mentat into 
$:/plugins/admls/mentat, which includes $:/plugins/admls/mentat. The other 
issue is that it isn't packaging in some of the things I'm trying to 
include since they don't begin with $:/plugins/admls/mentat. That's why 
they're missing some of the tiddlers they need to have. 

I just pushed a new release. It's better. It's got the tiddlers it needs. 
There are still a few bugs, so make sure you backup your data. I'll keep 
squashing bugs in the meantime.

Best wishes,

admls


On Friday, March 15, 2019 at 10:49:32 PM UTC, Elijah wrote:
>
> Why are you packaging each plugin's plugin-tiddler into itself? 
> $:/plugins/admls/mentat doesn't need to contain $:/plugins/admls/mentat, 
> and none of the others need contain their own respective plugin-tiddlers. 
> Doing so is causing an issue when importing your plugins into other 
> Tiddlywikis, whereby they do not appear at all. I don't know how packaging 
> works on Node.js, but when I repackage each plugin, using the Web Console, 
> in Firefox, without including the main plugin-tiddlers, everything works 
> fine for the most-part, though I do notice some of your plugins are missing 
> a few tiddlers in their packages.
>
> I'm very new to creating plugins for Tiddlywiki, so I may be missing 
> something, but thought I'd mention it anyway, in case it helps.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/3b4ca425-791f-4add-9d00-3f07d60ac926%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Yep. That sounds like it's working.
Thanks, Birthe!

On Friday, March 15, 2019 at 2:19:59 PM UTC, Birthe C wrote:
>
> Sorry, I am not sure, what shift is supposed to do. If I have a tiddler 
> title in one window and the link to the same title in another window. Shift 
> click the link will open the title in a tab in the same window as the link. 
> Clicking goes to the original window with the title.
>
> Birthe
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/df40dec5-7c14-4b84-a50e-5db7d50b170b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

ctrl+alt opens the link in a new window tiddler? That's excellent. How 
about the shiftkey modifier? Any luck there?

On Friday, March 15, 2019 at 11:36:52 AM UTC, Birthe C wrote:
>
> Okay. in Chromium on Linux, Ctrl+Alt click link works.
>
>
> Birthe
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/5986c67e-af05-4e69-923e-0b70adba8435%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Birthe,

I'm trying Chromium in windows and it seems to be working fine, mostly. The 
first click on the first link that is modified with altkey doesn't do 
anything. But then, if I click it again with the altkey, it works fine. 
Shiftkey seems to work fine, too.

I did a bit of reading about it. The modifier key behavior seems to be 
different for Chromium when it is running on Linux. I'm not sure how to 
address this exactly. Do the alt and shift modifier keys work when you are 
on some other page? I think shift opens a new window and alt downloads the 
link (or at least, that's what they do in Windows).

Best wishes,

admls

Do the shiftkey and altkey modifiers work outside of tiddlywiki?

On Friday, March 15, 2019 at 8:49:19 AM UTC, Birthe C wrote:
>
> Hi Admis,
>
> Oh, I guess that is the reason. I am using Linux Mint and my browser is 
> Chromium.
>
>
> Birthe
>
> fredag den 15. marts 2019 kl. 09.03.24 UTC+1 skrev admls:
>>
>>
>> Hmm. I'm unable to reproduce the bug. Are you on Mac or Windows? What 
>> browser are you using? I don't know if that will make a difference or not, 
>> but it would be good to know if there's some sort of pattern. Is anyone 
>> else getting this bug?
>>
>> Best wishes,
>>
>> admls
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/bd95e093-47ab-4b29-a0ed-9373736cb86f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hmm. I'm unable to reproduce the bug. Are you on Mac or Windows? What 
browser are you using? I don't know if that will make a difference or not, 
but it would be good to know if there's some sort of pattern. Is anyone 
else getting this bug?

Best wishes,

admls


-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/424cfebe-e361-4109-b845-b456b4802601%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi TonyM,

Imagine you are in a Vector diagram editor, Photoshop etc... you can move 
> items between layers.
>
> That we could select a tiddler and "Move to Back" would be like placing it 
> on the background such that other "Floating" tiddlers, even standard 
> tiddlers, would be in the midground. 
>

Gotcha. Okay. Interesting idea. I'm not sure about incorporating standard 
tiddlers. I sort of feel that same effect is achievable in a story window 
tiddler, but it gives you other options as well. But moving to the back 
could be nice. Trying to think of a nice way that could be accessible in 
the UI without creating clutter. Food for thought.

Of course when we click on a tiddler it will be displayed fully, clicking 
> another it will return to the position. Your pileup does this according to 
> the active tiddler, but when we are focused on another perhaps they could 
> move to their set position.
>

Is that a set position in depth? That's interesting. I took an approach 
that favors recency. I think adding a set depth to each tiddler is 
certainly possible. But it might start to get troublesome if you have 
various configurations that you like to flip through. If it is in Mentat, 
the depth of windows could be configured by session just as the other 
position information is. But if we are just dealing with vanilla Volant 
tiddlers, that might not work without adding a fairly complex system. 

If you aren't talking about a set position in depth, the maximize system 
does just that. But it has only been configured to work with window 
tiddlers. That could be changed however. Are you talking about having the 
change occur whenever you click on a tiddler? Or just when you use a button 
like the maximize button?

Perhaps we could "minimise" a tiddler to a row at the bottom of the screen 
> such that clicking will open it "Restore" in the previous positions, and 
> full screen the tiddler as well.
>

This is a great idea. The Mentat plugin has an Engine tiddler that holds 
windows at the bottom of the viewport, but they're just buttons. 
Interesting to think about making a sort of icon of the window. It might be 
costly in terms of performance, I don't rightly know, but that would make 
Mentat feel more like a desktop, which was a big inspiration for the 
interface. 


>- Provide a larger virtual wiki space, large than the physical screen 
>in which we can arrange tiddlers, with mouse or arrow keys scrolling 
>left/right up/down.
>   - This would allow those popular and "sexy" presentations that move 
>   the perspective not the content - if you know what I mean
>   - With a zoom out option to see them all.
>
> That's what $:/VolantAbsolute tiddlers are for. Eventually. Engine and 
Mentat are explorations of the fixed $:/Volant tiddlers. But the 
$:/VolantAbsolute tiddlers will get their time in the sun, too, I think. I 
need to take a break and work on some other projects, but that's very much 
on my radar. In part, the easy drag mode was put in place with this in 
mind. If you zoom out, you're not going to be able to grab the margins. 
You'll want to be able to simply grab the whole tiddler.

I would be keen to see a filter based and "multiple engines" option, for 
> example when I change projects be able to display the key tiddlers for that 
> project.
>

Yes. I think that's a good idea at some point. I erred on the side of 
having things quickly configurable but simple with the Engine plugin. There 
were already so many new systems to grapple with. But yeah, I think that 
could be useful.

There has being a proposed feature for "Stacked" story view that is 
> continuously held back for later release, see bottom of 
> https://tiddlywiki.com/prerelease/#TiddlyWiki%20Pre-release this may be 
> able to be implemented in your solution but may require more levels than 
> background, middleground and foreground.
>

I think the Volant plugin might be overkill for that. But I should think it 
would be possible. 

I am really looking forward to the potential of your solution when using 
> tiddlers with internal navigation or iframes to other sites and wikis. It 
> may behave like a Wiki of Wikis
>

Wiki of Wikis sounds really cool. To my mind, ideally Tiddlywiki would be a 
one-stop-shop for all a person's notes and information. Having the ability 
to seamlessly navigate from wiki to wiki would be amazing.  

Thanks for all the suggestions. It may be a few months before I have the 
chance to take on any of this stuff. I'm trying to get job ready with the 
programming at the moment, and I'm a bit behind where I want to be. But I 
definitely plan on returning to this stuff!

Best wishes,

Admls



On Wednesday, March 13, 2019 at 1:00:06 AM UTC, TonyM wrote:
>
> Admls,
>
> I apologize for asking for new 

[tw5] Re: Announcing 4 New Plugins (sort of)

[admls]

Hi Everybody!

Thank you all for your kind words. I worked really hard on this and it is a 
huge relief that it might add something to the community!

With the help of several people on this forum, the plugin packaging issues 
I have had have been sorted. Here's the link to the demo again: Mentat Demo 
<https://admls.github.io/Mentat/>. Please backup your wikis! And keep in 
mind that, unfortunately, the Volant plugin overwrites 
$:/core/ui/EditTemplate and $:/core/ui/ViewTemplate. I couldn't find any 
other way to make the popups work correctly. 

That said, enjoy!

@TonyM:

Perhaps you could also think of enabling move to back, but I am not sure of 
> the best way to find them again, perhaps using the link in the open sidebar 
> tab.
>

I'm not sure I understand what you mean about moving back. Could you 
elaborate a bit? Like a back button for the story window tiddlers?

Best wishes,

Admls


On Tuesday, March 12, 2019 at 11:29:45 AM UTC, JD wrote:
>
> Hi admls,
>
> Wow! This is so cool! The tiddlers stay within the browser when resizing 
> the window, and it looks so easy to style! 
>
> This will change my desktop tw-ing habits. No longer do I need to keep a 
> separate notepad.exe running as a clipboard when I can use a tiddler served 
> through Mentat instead! Aah... am already thinking of the efficiency this 
> will add to my workflow...
>
> Thank you so much for sharing!
>
> -jd
>
>
> On Tuesday, March 12, 2019 at 11:23:34 AM UTC+9, admls wrote:
>>
>> Hi Folks,
>>
>> I'm sort of publishing 4 plugins that create a flexible, customizable ui:
>>
>> * Repopup
>> * Volant
>> * Engine
>> * Mentat
>>
>> You can go check them out over here https://admls.github.io/Mentat/
>>
>> Why "sort of"? Because I'm having trouble with the packaging from node, 
>> is why. In any case, I wanted to put these out there so that anyone who 
>> wishes to may experiment with them a bit. I'll work on figuring out how to 
>> get them packaged correctly in the coming days. I hope you enjoy them!
>>
>> Best wishes,
>>
>> admls
>>
>> P.s. Please let me know if there is anything I can do to improve them. 
>> This is my first sort of major programming project, so I'd love to learn 
>> how to polish it a bit.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0c2679d9-19c3-4b4f-854d-a7cd7e8f3f39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: Plugin tiddlers non-functional until opened and saved

[admls]

Hi Jeremy and Mohammad,

That was the problem. I had one filter that was all[system+tiddlers] 
instead of all[shadows+tiddlers]. Thanks, Jeremy! It would have taken me 
days to think of that.

Best wishes,

Admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9f3ebb93-fd8f-4f05-a2bf-2a245b5de68f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Plugin tiddlers non-functional until opened and saved

[admls]

Brilliant. The filters would never have occurred to me. I'll give that a look 
in a bit and see if that solves it. 

Cheers!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e1d6eadc-082c-4661-930a-01e0bcf6dc13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Plugin tiddlers non-functional until opened and saved

[admls]

Hi Jeremy,
My plugins have some tiddlers of type text/vnd.tiddlywiki and some of type 
application/javascript. I don't really understand what rawmarkup is. Could you 
explain a bit more?

Best wishes,
Admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4bbbfc2c-4e5c-498f-ac04-a7a32bac6478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Announcing 4 New Plugins (sort of)

[admls]

Oh yeah. Not suited to mobile. I've only worked on the desktop side of it thus 
far. Cheers!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/fff49284-bd5c-4ecd-a56d-8176b8527bbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Announcing 4 New Plugins (sort of)

[admls]

Hi Folks,

I'm sort of publishing 4 plugins that create a flexible, customizable ui:

* Repopup
* Volant
* Engine
* Mentat

You can go check them out over here https://admls.github.io/Mentat/

Why "sort of"? Because I'm having trouble with the packaging from node, is 
why. In any case, I wanted to put these out there so that anyone who wishes 
to may experiment with them a bit. I'll work on figuring out how to get 
them packaged correctly in the coming days. I hope you enjoy them!

Best wishes,

admls

P.s. Please let me know if there is anything I can do to improve them. This 
is my first sort of major programming project, so I'd love to learn how to 
polish it a bit.

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/68b90a81-017b-41e0-aefe-79fda495fadd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Plugin tiddlers non-functional until opened and saved

[admls]

Hi Folks,

I came across a really weird problem. I've been developing some plugins on 
node, and they work fine there. But when I build the release, a few of the 
tiddlers in the plugin simply don't work until I open them and save them 
again. I don't make any changes, just open, close. And then they function.

Has anyone seen anything like this before? I'm out of my depth here.

Best wishes,

admls

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f6a10006-cd60-4eb1-8527-7983dc87b401%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Re: StartupActions: maximise browser window based on screen width?

[admls]

Thanks for the feedback everybody!

On Thursday, March 7, 2019 at 9:15:45 AM UTC, Jeremy Ruston wrote:
>
> I believe that the problem here is browser security: they think nobody 
> would want a website that fullscreens itself without permission when it 
> opens, and so they implement a restriction whereby fullscreen can only be 
> entered within a user-triggered event handler (e.g. a button). 
>
> Best wishes 
>
> Jeremy. 
>
>
> -- 
> Jeremy Ruston 
> jer...@jermolene.com  
> https://jermolene.com 
>
> > On 7 Mar 2019, at 09:05, 'Andreas Hahn' via TiddlyWiki <
> tiddl...@googlegroups.com > wrote: 
> > 
> > Hi Adam, 
> > 
> > unfortunately, the simple answer to this is: `tm-full-screen` will never 
> work as a startup action, as these actions run before the rootwidget is 
> initialized to listen for and handle these messages. 
> > 
> > It could work if you figure out a way to delay the action, but I'm not 
> sure how one would go about that. 
> > 
> > /Andreas 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "TiddlyWiki" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to tiddlywiki+...@googlegroups.com . 
> > To post to this group, send email to tiddl...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/tiddlywiki. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/44ca7e9c-d560-7290-8bda-151901524fd2%40googlemail.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/77389bdd-6bed-4139-80d1-59543a8023bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: StartupActions: maximise browser window based on screen width?

[admls]

Hi Hubert,

Just wanted to see if you ever got this to work. I'm running into a similar 
problem at the moment with StartupActions. I could use a bit of insight 
into its workings.

Best wishes,

Adam

On Wednesday, June 27, 2018 at 11:27:07 AM UTC+1, Hubert wrote:
>
> Hi,
>
> I'm trying to make use of the new *StartupActions* 
>  functionality.
>
> I'm using TW on multiple computers with different screen sizes and what 
> I'm trying to do is maximise the browser window on startup IF the current 
> screen width ($:/info/browser/screen/width) matches 1366 pixels (laptop).
>
> I've created a tiddler named StartUp and tagged it with 
> $:/tags/StartupAction/Browser
>
> In the tiddler's text area, I've typed in the following code (the 
> dependency here is Evan Balster's formula macro):
>
> \define BlaBla()
> <$set name=screen_width value={{$:/info/browser/screen/width}}>
> <>
> 
> \end
>
> \define Conditionals()
> <$formula formula="if(($(screen_width)$=1366), 
> '<>', '')"/>
> \end
>
> \define MaximiseBrowserWindow()
> <$action-sendmessage $message="tm-full-screen"/>
> \end
>
> <>
>
> Unfortunately this does nothing.
>
> For testing purposes, I've removed most of the above code and left out 
> just the action line:
>
> <$action-sendmessage $message="tm-full-screen"/>
>
> This does nothing either.
>
> I know it is strange just to place actions in tiddlers on their own but I 
> would have assumed that the trigger here is startup itself and the code 
> should be executed just because the tiddler is tagged as it should, as if 
> the whole snippet was a button action (?)
>
> Is there anything I'm missing here or is it just that, by design, actions 
> cannot be executed conditionally?
>
> Thank you for your input.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9927b507-4a7f-4fa0-a58a-01d3a47044ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5]Macro interactions

[admls]

Hi Jeremy,

Thanks! That's marvelously concise.


On Thursday, February 14, 2019 at 10:01:19 AM UTC, Jeremy Ruston wrote:
>
> Hi Mark
>
> The following version works.
>
> \define concatStateTiddler()
> <$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]] 
> +[addprefix[$:/state/]]" name="kitty"><$text text=<>/>
> \end
>
> \define backup(value)
> <$wikify text=<> name=cst>
> <$view tiddler=<> field="""$value$"""/>
> 
> \end
>
>
> I think that this can be done much more concisely and efficiently.
>
> At the moment concatStateTiddler is using the "filter" attribute of the 
> set widget. That means that the result of will be a list of titles, using 
> double square brackets to quote titles containing spaces.
>
> I don't fully understand the original problem, but unless you definitely 
> need to have that quoting, it would be more concise to write this:
>
> <$text text={{{ [all[current]get[draft.of]] ~[all[current]] 
> +[addprefix[$:/state/]] }}}/>
>
> In the backup macro you're using the wikify widget on the result of the 
>  concatStateTiddler macro. Perhaps it's because you want to get the result 
> of concatStateTiddler into a variable? But that doesn't make sense, because 
> the substance of concatStateTiddler is to assign a value to a variable and 
> then return it as text.
>
> Stepping back, it looks like this should work:
>
> \define backup(value)
> <$view tiddler={{{ [all[current]get[draft.of]] ~[all[current]] 
> +[addprefix[$:/state/]] }}} field=<<__value__>>/>
> \end
>
> Best wishes
>
> Jeremy
>
>
>
>
>
> You can't concatenate a <> inside text like that ... well ... 
> maybe with a lot of patient application of wikify (which I needed anyways). 
> Instead, I used the "addprefix" operator to do the concatenation, following 
> up on a suggestion by Jeremy in an earlier post today.
>
> Note, all the extra space and line feeds had to be squeezed out of 
> concatStateTiddler -- if GG puts them back in ... take them out. 
>
> The <$text> widget was used to convert the resulting item (which would 
> otherwise have been a link because *filter* generates a title list) into 
> plain text, and <$wikify> was used to make the entire result of 
> concatStateTiddler into a single variable.
>
> Hope this was something like what you wanted!
>
> -- Mark
>
>
>
> On Tuesday, February 12, 2019 at 4:58:14 PM UTC-8, admls wrote:
>>
>> Hi Folks,
>>
>> I'm trying to populate a stylesheet, but I'm having trouble getting these 
>> macros to work together. The concatStateTiddler macro is supposed to give 
>> me the name of a state tiddler tacked composed of a prefix and the name of 
>> the currentTiddler. The backup macro is supposed to fetch some value from 
>> the state tiddler if it is present. And if it is not present, it should 
>> fetch it from a set of backup values.
>>
>> \define concatStateTiddler()
>> <$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]]">
>> "$:/state/<>"
>> 
>> \end
>>
>> \define backup(value)
>> <$view tiddler=$(concatStateTiddler)$ field="""$value$""">
>>  <$view tiddler="$:/config/backup-values" field="""backup-$value$""">
>> 
>> 
>> \end
>>
>> I can get it to work if concatStateTiddler looks like this:
>> \define concatStateTiddler()
>> "$:/state/$(currentTiddler)$"
>> \end
>>
>> But I want the view and edit mode versions of the tiddler to use the same 
>> state tiddler. Hence the first version of concatStateTiddler. But the first 
>> version doesn't play nice with the backup macro. Any ideas of what I'm 
>> doing wrong here?
>>
>> The only thing I can think is that the set widget is creating a list, 
>> even if it is a list consisting of only one element (on account of the use 
>> of [all[current]]). That list format may be playing havoc with the backup 
>> macro. But I really don't have any idea beyond that. Any help would be 
>> greatly appreciated.
>>
>> Best regards,
>>
>> Adam
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+...@googlegroups.com .
> To post to this group, send email to tiddl...@googlegroups.com 
> .
> Vis

Re: [tw5]Macro interactions

[admls]

Hi S.S.,

I just got the chance to test out your code. I had to massage it just a 
smidge, but it works great! Thank you. I have bashed my head against this 
problem for too long. I'm always amazed at how concise well-written 
tiddlywiki code can be. The solution to my problems is often achieved in 
half the code I thought would be required. 

Thank you everybody!

Best wishes,
Adam

On Wednesday, February 13, 2019 at 1:28:04 PM UTC, S. S. wrote:
>
> Adam, not sure if this is what you want.
>
> In tiddler : NewTiddler
> \define concatStateTiddler(value)
> <$list filter="[all[current]get[draft.of]] [all[current]!has[draft.of]] 
> +[addprefix[$:/state/]]">
> <$view field=backup-$value$/>
> 
> \end
>
> In tiddler: 
> *$:/state/NewTiddler*has field: *backup-1*
> field backup-1 has value : *somevalue*
>
> When *NewTiddler* is being viewed or edited, this macro in its text field 
> *< 1>>*  should give a result of : *somevalue*
>
>
> On Wednesday, February 13, 2019 at 7:58:14 AM UTC+7, admls wrote:
>>
>> Hi Folks,
>>
>> I'm trying to populate a stylesheet, but I'm having trouble getting these 
>> macros to work together. The concatStateTiddler macro is supposed to give 
>> me the name of a state tiddler tacked composed of a prefix and the name of 
>> the currentTiddler. The backup macro is supposed to fetch some value from 
>> the state tiddler if it is present. And if it is not present, it should 
>> fetch it from a set of backup values.
>>
>> \define concatStateTiddler()
>> <$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]]">
>> "$:/state/<>"
>> 
>> \end
>>
>> \define backup(value)
>> <$view tiddler=$(concatStateTiddler)$ field="""$value$""">
>>  <$view tiddler="$:/config/backup-values" field="""backup-$value$""">
>> 
>> 
>> \end
>>
>> I can get it to work if concatStateTiddler looks like this:
>> \define concatStateTiddler()
>> "$:/state/$(currentTiddler)$"
>> \end
>>
>> But I want the view and edit mode versions of the tiddler to use the same 
>> state tiddler. Hence the first version of concatStateTiddler. But the first 
>> version doesn't play nice with the backup macro. Any ideas of what I'm 
>> doing wrong here?
>>
>> The only thing I can think is that the set widget is creating a list, 
>> even if it is a list consisting of only one element (on account of the use 
>> of [all[current]]). That list format may be playing havoc with the backup 
>> macro. But I really don't have any idea beyond that. Any help would be 
>> greatly appreciated.
>>
>> Best regards,
>>
>> Adam
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e7b4d9b9-acf6-453b-99d7-24f1229c0a53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5]Macro interactions

[admls]

The tiddlywiki.com documentation on the set widget says this about the name 
parameter: 'The name of the variable to assign (defaults to "currentTiddler")'.

Does that just need updated or something? Or am I misunderstanding it?

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/44695e55-ac26-430b-8d06-5846fd008970%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5]Macro interactions

[admls]

Hi Tony,

My understanding is that if the name parameter is left out of the set 
widget, the variable name defaults to "currentTiddler". I could be 
mistaken, of course.


Hi Mark,

That doesn't seem to be working for me. It's acting like there is nothing 
at those fields, but I've made sure that there are some values there.


Best wishes,
Adam

On Wednesday, February 13, 2019 at 4:02:42 AM UTC, Mark S. wrote:
>
> Hello Adam,
>
> The following version works.
>
> \define concatStateTiddler()
> <$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]] 
> +[addprefix[$:/state/]]" name="kitty"><$text text=<>/>
> \end
>
> \define backup(value)
> <$wikify text=<> name=cst>
> <$view tiddler=<> field="""$value$"""/>
> 
> \end
>
>
> You can't concatenate a <> inside text like that ... well ... 
> maybe with a lot of patient application of wikify (which I needed anyways). 
> Instead, I used the "addprefix" operator to do the concatenation, following 
> up on a suggestion by Jeremy in an earlier post today.
>
> Note, all the extra space and line feeds had to be squeezed out of 
> concatStateTiddler -- if GG puts them back in ... take them out. 
>
> The <$text> widget was used to convert the resulting item (which would 
> otherwise have been a link because *filter* generates a title list) into 
> plain text, and <$wikify> was used to make the entire result of 
> concatStateTiddler into a single variable.
>
> Hope this was something like what you wanted!
>
> -- Mark
>
>
>
> On Tuesday, February 12, 2019 at 4:58:14 PM UTC-8, admls wrote:
>>
>> Hi Folks,
>>
>> I'm trying to populate a stylesheet, but I'm having trouble getting these 
>> macros to work together. The concatStateTiddler macro is supposed to give 
>> me the name of a state tiddler tacked composed of a prefix and the name of 
>> the currentTiddler. The backup macro is supposed to fetch some value from 
>> the state tiddler if it is present. And if it is not present, it should 
>> fetch it from a set of backup values.
>>
>> \define concatStateTiddler()
>> <$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]]">
>> "$:/state/<>"
>> 
>> \end
>>
>> \define backup(value)
>> <$view tiddler=$(concatStateTiddler)$ field="""$value$""">
>>  <$view tiddler="$:/config/backup-values" field="""backup-$value$""">
>> 
>> 
>> \end
>>
>> I can get it to work if concatStateTiddler looks like this:
>> \define concatStateTiddler()
>> "$:/state/$(currentTiddler)$"
>> \end
>>
>> But I want the view and edit mode versions of the tiddler to use the same 
>> state tiddler. Hence the first version of concatStateTiddler. But the first 
>> version doesn't play nice with the backup macro. Any ideas of what I'm 
>> doing wrong here?
>>
>> The only thing I can think is that the set widget is creating a list, 
>> even if it is a list consisting of only one element (on account of the use 
>> of [all[current]]). That list format may be playing havoc with the backup 
>> macro. But I really don't have any idea beyond that. Any help would be 
>> greatly appreciated.
>>
>> Best regards,
>>
>> Adam
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/809bf23b-c06c-4b39-9b85-ebf2fa863942%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5]Macro interactions

[admls]

Hi Folks,

I'm trying to populate a stylesheet, but I'm having trouble getting these 
macros to work together. The concatStateTiddler macro is supposed to give 
me the name of a state tiddler tacked composed of a prefix and the name of 
the currentTiddler. The backup macro is supposed to fetch some value from 
the state tiddler if it is present. And if it is not present, it should 
fetch it from a set of backup values.

\define concatStateTiddler()
<$set filter="[all[current]get[draft.of]] [all[current]!has[draft.of]]">
"$:/state/<>"

\end

\define backup(value)
<$view tiddler=$(concatStateTiddler)$ field="""$value$""">
 <$view tiddler="$:/config/backup-values" field="""backup-$value$""">


\end

I can get it to work if concatStateTiddler looks like this:
\define concatStateTiddler()
"$:/state/$(currentTiddler)$"
\end

But I want the view and edit mode versions of the tiddler to use the same 
state tiddler. Hence the first version of concatStateTiddler. But the first 
version doesn't play nice with the backup macro. Any ideas of what I'm 
doing wrong here?

The only thing I can think is that the set widget is creating a list, even 
if it is a list consisting of only one element (on account of the use of 
[all[current]]). That list format may be playing havoc with the backup 
macro. But I really don't have any idea beyond that. Any help would be 
greatly appreciated.

Best regards,

Adam

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/50e6d96a-ab1d-4597-905c-3b7e7334246b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [tw5] Sanitizing JS

[admls]

Hi Jeremy,

Thanks for the info. I guess I'm just wondering if there is a convenient 
way to filter out some features of JS and allow others to go through. I see 
lots of plugins that provide atomized functionality of simple capabilities 
of javascript. It just seems to me that if it were possible to build an 
effective filter, one might be able to have all that functionality in the 
core without bloating tw.

The Secure EcmaScript is really interesting. Though I wonder if there is a 
simpler way to do this without executing the code in a sandbox environment. 
Is it possible to, in the parsing stage, identify blacklisted keywords, and 
if those words appear, don't make a script tag out of the code? Or maybe 
(if a blacklist would be too large) just have a list of whitelisted words 
and symbols (including a set of allotted variable names). If the code is 
built only of these parts, then a script tag is made of it. Else, it 
doesn't run. Or it throws an error or something.

I'm fairly new to JS and programming generally; so this may all be 
hopelessly naive of me. I just wonder if the bloat of multiple (and 
sometimes overlapping) plugins to perform string, numerical, JSON, or array 
manipulation could be reduced. 

Best wishes,

Adam

On Friday, January 18, 2019 at 9:16:31 PM UTC, Jeremy Ruston wrote:
>
> Hi Adam
>
> As others have said, the primary goal of the current arrangement is to 
> make it easier to detect/filter JS content by requiring it to be in a 
> module tiddler. A secondary benefit of excluding inline JS is that it 
> discourages blindly copying and pasting the kind of old-style DOM-based JS 
> snippets that don’t work in TW5.
>
> Funnily enough, I’ve just come across Secure EcmaScript which seems a good 
> snapshot of the state of the art of safely executing untrusted JavaScript:
>
> https://github.com/Agoric/SES
>
> Here’s a demo:
>
> https://github.com/jimpick/cabal-ses-bot
>
> Best wishes
>
> Jeremy
>
> On 16 Jan 2019, at 23:25, AdamS > 
> wrote:
>
> Thank you all. That's a lot of good information for my to look through and 
> cogitate on!
>
> Best wishes,
> Adam
>
> On Wednesday, January 16, 2019 at 5:01:07 PM UTC, Matthew Lauber wrote:
>>
>> Another issue with inline javascript specific to TW is that it interferes 
>> with the parse/render/update loop.  Let's say you include some inline 
>> javascript in your tiddler.  When is it supposed to execute?  When 
>> rendered?  How often?  Keep in mind that TW rerenders tiddlers if any of 
>> the state they depend on changes (like the React Virtual DOM).  These 
>> renders may not be visible to you the user.  And what happens when your 
>> javascript is executed twice?  Overall, it is a lot simpler to reason 
>> about, and less bug prone, to require all javascript calls to be part of 
>> the parse/render/update loop.  
>>
>> On Monday, January 14, 2019 at 8:09:46 PM UTC-5, AdamS wrote:
>>>
>>> Hi Folks,
>>>
>>> I know it has been discussed a few times, but I keep coming back to the 
>>> idea of inline javascript. Or at least something javascript-ish 
>>> (javascript-esque?). I know the reason this capability isn't standard is 
>>> because of security issues. I don't have much experience with this sort of 
>>> thing, but I'm wondering how significant are the barriers to sanitizing 
>>> inline javascript. What would need to be stripped out of a script tag to 
>>> ensure that it would be safe? I'm guessing any DOM manipulation would be 
>>> right out, as well as access to the window object. But even if we could 
>>> just get a safe inline javascript for control flow, array, string, and 
>>> number manipulation, that could be pretty cool. Could this be securely done?
>>>
>>> Best wishes,
>>>
>>> Adam
>>>
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to tiddlywiki+...@googlegroups.com .
> To post to this group, send email to tiddl...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/tiddlywiki.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywiki/8ddce635-574b-4a79-8ccd-027ef0fd6c17%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1726d702-9a30-4682-92f1-fe0427743abb%40googlegroups.com.
For more options, visit 

[tw5] Re: Filter/subfilter syntax and variables

[admls]

That seems to do the opposite. It works for [[Some Tiddler]], but not for 
SomeTiddler.

On Friday, January 18, 2019 at 12:04:30 AM UTC, Matthew Lauber wrote:
>
> Try $subfilter="-[enlist]"
>
> On Thursday, January 17, 2019 at 12:46:56 PM UTC-5, admls wrote:
>>
>> Hi Mark,
>>
>> I've tried to get the simplest setup that still features the weird 
>> behavior. It is using the draggable widget.
>>
>> \define startactions()
>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>> \end
>>
>> <$list filter="[list[List 1]]">
>> <$draggable tiddler=<> startactions=<>>
>> <$text text=<>/>
>> 
>> 
>>
>>
>> And List 1 consists of "[[Link Tiddler]] [[Missing Link]] FakeTid 
>> [[FakeTiddler]]".
>> FakeTid and [[FakeTiddler]] get removed. The others do not.
>> Any ideas?
>>
>> Best wishes,
>> Adam
>>
>>
>> On Thursday, January 17, 2019 at 3:28:18 PM UTC, Mark S. wrote:
>>>
>>> I think we need to know more about your setup. Are you using the macro 
>>> in draggable, or in droppable? When I use it in droppable, it works right 
>>> out of the box, no matter how many spaces are in the title.
>>>
>>> Good luck!
>>> -- Mark
>>>
>>> On Thursday, January 17, 2019 at 1:50:25 AM UTC-8, AdamS wrote:
>>>>
>>>> Hello all,
>>>>
>>>> I've got this action that is supposed to remove a tiddler from a list 
>>>> of tiddler titles:
>>>>
>>>> \define startactions()
>>>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>>>> \end
>>>>
>>>> However, it doesn't seem to work if the tiddler title appears in the 
>>>> list in this format [[Two Words]]. It works fine with [[OneWord]] and with 
>>>> OneWord, though. Anyone have any idea what I'm doing wrong here?
>>>>
>>>> Best wishes,
>>>> Adam
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/78ae2b13-599a-46c3-8e54-5446b80db3a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Filter/subfilter syntax and variables

[admls]

I've got a workaround:

\define startactions()
<$wikify name="actionT" text=<>>
<$action-listops $tiddler="List 1" $subfilter="-[]"/>

\end

<$list filter="[list[List 1]]">
<$draggable tiddler=<> startactions=<>>
<>



$draggable adds a set of brackets and $action-listops also adds a set of 
brackets. So you have to wikify the actionTiddler after it has come out of 
$draggable and before it goes into $action-listops. That way it has at most 
one set of brackets on the other side of whatever $action-listops does to 
it. Phew!

On Thursday, January 17, 2019 at 10:50:26 PM UTC, admls wrote:
>
> I think I may have spotted where the issue may be arising.
>
>
> This is how the actions are invoked by the droppable widget:
>
> this.invokeActionString(this.droppableActions,this,event,{actionTiddler: 
> title, modifier: modifierKey})
>
> In contrast, the draggable widget calls 
> $:/core/modules/utils/dom/dragndrop.js which invokes startActions like this:
> options.widget.invokeActionString(startActions,options.widget,event,{
> actionTiddler: titleString});
> The titleString variable is:
> var titleString = $tw.utils.stringifyList(titles);
> So the droppable widget is passing one title and the draggable widget is 
> passing a list of titles. 
>
> In the course of making that list, $tw.utils.stringifyList (in 
> $:/boot/boot.js), does this:
> if(entry.indexOf(" ") !== -1) { result.push("[[" + entry + "]]"); } else { 
> result.push(entry); }
>
> So if there is whitespace, as in the case of [[Missing Tiddler]], it gets 
> an extra set of brackets in the draggable widget versus the droppable 
> widget.
> I guess a workaround would require being able to remove brackets? But at 
> what point in the process?
>
> On Thursday, January 17, 2019 at 9:13:36 PM UTC, admls wrote:
>>
>> Hi Mark,
>>
>> I created an issue on github. I've tried wikifying the list items in 
>> various ways but I'm not having any luck making a workaround.
>>
>> Best wishes,
>> Adam
>>
>> On Thursday, January 17, 2019 at 7:12:36 PM UTC, Mark S. wrote:
>>>
>>> I'm thinking it may be an actual bug. The actionTiddler works as 
>>> expected inside of droppable, as mentioned before.
>>>
>>> By changing your case to use filter instead of subfilter, you can see 
>>> what the macro sees. When I run it this way, I get
>>>
>>> Missing Link
>>>
>>> I think it's seeing the entire passed text as the literal string 
>>> "Missing Link" If you add "Missing Link" to your list, then 
>>> dragging [[Missing List]] will cause Missing Link to disappear.
>>>
>>> If that's not a bug, I'd like to know the incantation that would make it 
>>> work ;-)
>>>
>>> -- Mark
>>>
>>> On Thursday, January 17, 2019 at 9:46:56 AM UTC-8, AdamS wrote:
>>>>
>>>> Hi Mark,
>>>>
>>>> I've tried to get the simplest setup that still features the weird 
>>>> behavior. It is using the draggable widget.
>>>>
>>>> \define startactions()
>>>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>>>> \end
>>>>
>>>> <$list filter="[list[List 1]]">
>>>> <$draggable tiddler=<> startactions=<>>
>>>> <$text text=<>/>
>>>> 
>>>> 
>>>>
>>>>
>>>> And List 1 consists of "[[Link Tiddler]] [[Missing Link]] FakeTid 
>>>> [[FakeTiddler]]".
>>>> FakeTid and [[FakeTiddler]] get removed. The others do not.
>>>> Any ideas?
>>>>
>>>> Best wishes,
>>>> Adam
>>>>
>>>>
>>>> On Thursday, January 17, 2019 at 3:28:18 PM UTC, Mark S. wrote:
>>>>>
>>>>> I think we need to know more about your setup. Are you using the macro 
>>>>> in draggable, or in droppable? When I use it in droppable, it works right 
>>>>> out of the box, no matter how many spaces are in the title.
>>>>>
>>>>> Good luck!
>>>>> -- Mark
>>>>>
>>>>> On Thursday, January 17, 2019 at 1:50:25 AM UTC-8, AdamS wrote:
>>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I've got this action that is supposed to remove a tiddler from a list 
>>>>>> of tiddler titles:
>>>>>>
>>>>>> \define startactions()
>>>>>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>>>>>> \end
>>>>>>
>>>>>> However, it doesn't seem to work if the tiddler title appears in the 
>>>>>> list in this format [[Two Words]]. It works fine with [[OneWord]] and 
>>>>>> with 
>>>>>> OneWord, though. Anyone have any idea what I'm doing wrong here?
>>>>>>
>>>>>> Best wishes,
>>>>>> Adam
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/31fb1e1f-3d0f-44a2-9119-210420b9f331%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[tw5] Re: Filter/subfilter syntax and variables

[admls]

I think I may have spotted where the issue may be arising.


This is how the actions are invoked by the droppable widget:

this.invokeActionString(this.droppableActions,this,event,{actionTiddler: 
title, modifier: modifierKey})

In contrast, the draggable widget calls 
$:/core/modules/utils/dom/dragndrop.js which invokes startActions like this:
options.widget.invokeActionString(startActions,options.widget,event,{
actionTiddler: titleString});
The titleString variable is:
var titleString = $tw.utils.stringifyList(titles);
So the droppable widget is passing one title and the draggable widget is 
passing a list of titles.

In the course of making that list, $tw.utils.stringifyList (in 
$:/boot/boot.js), does this:
if(entry.indexOf(" ") !== -1) { result.push("[[" + entry + "]]"); } else { 
result.push(entry); }

So if there is whitespace, as in the case of [[Missing Tiddler]], it gets 
an extra set of brackets in the draggable widget versus the droppable 
widget.



On Thursday, January 17, 2019 at 9:13:36 PM UTC, admls wrote:
>
> Hi Mark,
>
> I created an issue on github. I've tried wikifying the list items in 
> various ways but I'm not having any luck making a workaround.
>
> Best wishes,
> Adam
>
> On Thursday, January 17, 2019 at 7:12:36 PM UTC, Mark S. wrote:
>>
>> I'm thinking it may be an actual bug. The actionTiddler works as expected 
>> inside of droppable, as mentioned before.
>>
>> By changing your case to use filter instead of subfilter, you can see 
>> what the macro sees. When I run it this way, I get
>>
>> Missing Link
>>
>> I think it's seeing the entire passed text as the literal string 
>> "Missing Link" If you add "Missing Link" to your list, then 
>> dragging [[Missing List]] will cause Missing Link to disappear.
>>
>> If that's not a bug, I'd like to know the incantation that would make it 
>> work ;-)
>>
>> -- Mark
>>
>> On Thursday, January 17, 2019 at 9:46:56 AM UTC-8, AdamS wrote:
>>>
>>> Hi Mark,
>>>
>>> I've tried to get the simplest setup that still features the weird 
>>> behavior. It is using the draggable widget.
>>>
>>> \define startactions()
>>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>>> \end
>>>
>>> <$list filter="[list[List 1]]">
>>> <$draggable tiddler=<> startactions=<>>
>>> <$text text=<>/>
>>> 
>>> 
>>>
>>>
>>> And List 1 consists of "[[Link Tiddler]] [[Missing Link]] FakeTid 
>>> [[FakeTiddler]]".
>>> FakeTid and [[FakeTiddler]] get removed. The others do not.
>>> Any ideas?
>>>
>>> Best wishes,
>>> Adam
>>>
>>>
>>> On Thursday, January 17, 2019 at 3:28:18 PM UTC, Mark S. wrote:
>>>>
>>>> I think we need to know more about your setup. Are you using the macro 
>>>> in draggable, or in droppable? When I use it in droppable, it works right 
>>>> out of the box, no matter how many spaces are in the title.
>>>>
>>>> Good luck!
>>>> -- Mark
>>>>
>>>> On Thursday, January 17, 2019 at 1:50:25 AM UTC-8, AdamS wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I've got this action that is supposed to remove a tiddler from a list 
>>>>> of tiddler titles:
>>>>>
>>>>> \define startactions()
>>>>> <$action-listops $tiddler="List 1" $subfilter="-[]"/>
>>>>> \end
>>>>>
>>>>> However, it doesn't seem to work if the tiddler title appears in the 
>>>>> list in this format [[Two Words]]. It works fine with [[OneWord]] and 
>>>>> with 
>>>>> OneWord, though. Anyone have any idea what I'm doing wrong here?
>>>>>
>>>>> Best wishes,
>>>>> Adam
>>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9b7ac87c-3058-4eed-8804-f6d346f40b4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.