[twdev] Re: background: url("external") - why doesn't it work?

Mario, Given your well stated "internet citizen" ethics is this still true if that image is delivered through a CDN Content Delivery Network such as CloudFlair ? Some resources are "publish that way" and encourage people to include them in their own websites. Regards Tony On Friday,

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

Mat, I am not sure if this helps People wiser than me can set me strait If I have it wrong, but after packaging a few plugins under the $:/plugins I also started including tiddlers outside this name but Ensured they have a reasonable chance of not colliding, I include tiddlers in my own

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

Ok, so the plugin prefix is to prevent conflicts. That makes sense. > > (BTW, I wish we could control what tab to open). The tiddler that is opened, is the first one in the plugin.info list-field. > see: >

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

On Monday, September 17, 2018 at 12:25:15 PM UTC+2, Mat wrote: > > Ok, so the plugin prefix is to prevent conflicts. That makes sense. > > > >> > (BTW, I wish we could control what tab to open). > > > > The tiddler that is opened, is the first one in the plugin.info >> list-field. see: >>

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

On Monday, September 17, 2018 at 12:25:15 PM UTC+2, Mat wrote: > > > Interesting and good to know. Seems like an under-used opportunity. Even > if they are "thrown away", they're still there so maybe they could be > interpreted as paths to all tiddlers in the plugin so that we could really >

[twdev] Re: [TWX] Pretty shadow tid titles

> The important thing is. plugins are only containers. The tiddlers are > expanded into shadow tiddlers and then they are executed. That means even > if you use a prefix and "short-name" you still end up with the long name > for every tiddler. > Yes, the idea is however that users don't

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

> > Actually not quite; it is exclusively "readme" that is opened by default. >> No other tab is presented open by default even if first in list. Instead >> the user sees a somewhat silly looking row of *closed* tabs (#1902 >> ) >> > > >

[twdev] Re: [TWX] Pretty shadow tid titles

Hi, The important thing is. plugins are only containers. The tiddlers are expanded into shadow tiddlers and then they are executed. That means even if you use a prefix and "short-name" you still end up with the long name for every tiddler. -m -- You received this message because you are

[twdev] Re: [TWX] Pretty shadow tid titles

PMario wrote: > > The following structue is invalid and will result in a RSOD. > Is that a limitation caused by TW or is it something more fundamental e.g to json? I must assume the former so/but in TWX anything is possible ;-) <:-) -- You received this message because you are

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

On Monday, September 17, 2018 at 12:42:35 PM UTC+2, PMario wrote: > > > It's an implementation detail. The core code dealing with the json > structure is simpler and may be more efficient this way. I would strongly > recommend, to _not_ "mis-use" it. > edited the last post :) -- You received

[twdev] [TWX] Pretty shadow tid titles

The overall point with this idea is to make it easier to create tiddlers. It loosely describes a UI and a workflow but starts with an observation about the current way a plugin is defined. ... In another thread PMario explained the reason why plugins appear like so: { "tiddlers": {

[twdev] Re: Benefits/drawbacks with shadow tids using plugin path

On Sunday, September 16, 2018 at 10:54:01 PM UTC+2, Mat wrote: ... > One specific tiddler that requires the full path is the *"readme"* for it > to show as opened by default in the the plugin library. (BTW, I wish we > could control what tab to open). Other than this one tiddler I know of no

[twdev] Re: Need help with FireFox-specific UTF-8 conversion

Hi Yakov, I think the code you mentioned, was used to fix some implementation specific browser-glitches. ... IMO this part can be rewritten, with "up-to-date" browsers in mind. eg: I'm sure we can safely remove Netscape compatibility :) -m -- You received this message because you are

[twdev] Re: Need help with FireFox-specific UTF-8 conversion

Thanks Mario, that's a good point. Like I said, there are still active users of FF 3.x but I can probably provide a plugin for them instead. понедельник, 17 сентября 2018 г., 12:15:00 UTC+3 пользователь PMario написал: > > Hi Yakov, > > I think the code you mentioned, was used to fix some