Ciao TonyM

My understanding is that, though .hta mechanism is supported on Win10 for 
legacy, it has ceased active development.

Am I right in thinking its using Explorer 9 render engine? 
If so there may be things in TW HTML that are not supported.

My question is really this. Whilst it looks attractive in some ways, I'm 
just wondering about its real mileage now?

Best wishes
TT

On Wednesday, 26 February 2020 02:08:42 UTC+1, TonyM wrote:
>
> Folks,
>
> Saving a TiddlyWiki as a HTA file on windows machines allows immediate 
> access in its own window with saving automatic.
>
> This is a quick path to adoption, as a result I would like to explore it 
> further to support ease of adoption and its use one the local computer.
>
> HTA files activate the  mshta.exe application found in C:\Windows\SysWOW64 
> this is sometimes a vector for malware but if your computer is secure you 
> should be fine.
>
>    - Is this mshta.exe on a fresh install of Windows 10 (Without IE) or 
>    with the new edge browser?
>    - Application links want to download which reduces desktop interaction 
>    (Unlike the same in TiddlyDesktop), can we fix this?
>    - A Windows shortcut allows you to open the HTA maximised or minimised 
>    as well.
>    - The HTA application is visible in the running apps of task manager 
>    and lists the open instances. I wonder if we could use this to create a 
>    launch script that will not load the same hts file more than once?, to 
> stop 
>    on overwitiing the other.
>    - Could we introduce a user ID or lock method so these can be placed 
>    on a LAN drive and force serial editing, if so it would become a tool for 
>    teams?
>
> your thoughts or insight please
> Tony
>
>

-- 
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/bb891c85-c0bb-4024-863c-615fbcf68ecc%40googlegroups.com.

Reply via email to