Finally Mark, & anyone interested in Polly
I been thinking about possible ways to further leverage Polly. The .ini
settings approach + Mark's "Magic Loops" is enormously flexible. These are
ideas I'm looking at ...
1 - Using a settings file run in a new "launch" mode, i.e. -run "launch"
An optional [general] setting would be added called,
browser=
Which would be the path to a specific browser.
Without the setting the O/S default browser would be used.
This would launch the browser and open the wiki listed.
I been testing the idea in PowerShell. There are some issues in that I
haven't yet found a reliable single way to assemble a command line all
browsers accept. There are some differences between them. But perhaps its
possible.
You could then get Polly to start a session in a specific browser, open
wiki, & start monitoring.
2 - *Handling regular downloads*. Using a settings file run in
a new "fetch" mode, i.e. -run "fetch"
For example you list in a settings files you frequently
need from the net like the TW pre-release.
Fetching files is very easy in PowerShell. And you can
both rename and save places other than in downloads ...
Like this ...
function fetchTests {
# --- TT FETCH
iwr -uri https://tiddlywiki.com/prerelease/ -OutFile
..\..\P\Users\Polly\Downloads\tw_fetch\tw5-pre-$(get-date -f
yyyy-MM-dd).html
}
*IF either looks worthwhile pursuing let me know!*
It would not need to be part of standard Polly.
Maybe they could be implemented as "extension libraries"??
Thoughts!
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/447796d6-0141-4c2d-87ee-9c3a21f09372%40googlegroups.com.
