>
> Ciao Simon,
>
> I mean, simply, different TW illustrating the different aspects. For
> instance AUTO-POPULATE is brilliant but likely best in a TW orientated to
> that end (e.g. image gallery, or bulk Tweet rep). If its mixed in with
> other stuff it gets confusing. BUT the gizmos do
On Monday, January 22, 2018 at 6:41:56 PM UTC+1, @TiddlyTweeter wrote:
>
> I noticed that several main contributors of original stuff are UNconcerned
> with licensing.
>
Yea, ... I like those "I don't care, do what ever you want" licenses. ...
BUT why should I care about code, that was created
On Monday, January 22, 2018 at 6:41:56 PM UTC+1, @TiddlyTweeter wrote:
...
> TBH, since no one here is known or cared for, so what is the Ultimate
> Difference?
>
I think, adding an open source license to my code, just shows everyone, who
is interested to read, use and modify the code, how it
On Monday, January 22, 2018 at 4:08:30 PM UTC+1, BurningTreeC wrote:
> I can live well with the MIT license on this. I forgot to include the
> other licenses in the plugin, they will be there in the next release.
> popmotion also uses MIT,
> the Icons though, they're material icons with
Brilliant pointer for sophisticated longer survival ...
Mark S... One (or more) of the extensions that you could get for Firefox
> was one to change the browser identification string presented to web sites.
>
--
You received this message because you are subscribed to the Google Groups
If you're sticking with an older browser, then you should probably be
downloading extensions left and right while you can still get them!
One (or more) of the extensions that you could get for Firefox was one to
change the browser identification string presented to web sites. Possibly
search
Ciao Simon,
I mean, simply, different TW illustrating the different aspects. For
instance AUTO-POPULATE is brilliant but likely best in a TW orientated to
that end (e.g. image gallery, or bulk Tweet rep). If its mixed in with
other stuff it gets confusing. BUT the gizmos do illuminate what
On Monday, January 22, 2018 at 9:20:43 PM UTC+1, ste...@gmail.com wrote:
>
>
> Of course, this won't work with links from within your tiddlers. In this
> case, the other tiddlers will remain open, unless you use the code from
> above for all your internal links.
>
One additional thought: Is
>
>
> I'm looking and will comment in a couple of days after I played with it.
>
> One point I can make right away is that the various "gizmos" you took out
> for this version---I understand why--however, for a new user, they are
> extremely helpful in illustrating what it can do.
>
> I guess
Hi,
On Friday, January 19, 2018 at 5:59:17 PM UTC+1, TheDiveO wrote:
>
> I'm looking for a single tiddler storyview and I'm aware of the "zoomin"
> storyview. I've experimented with the zoomin storyview, but I see some
> obstacles to my particular usecase.
>
In addition to the suggestions
Ciao Birthe
I don't think so. Not shorter term. I don't think its an issue.
J.
Birthe C wrote:
>
> Will access to certain websites be restricted for browsers that does not?
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from
Hi Jeremy,
that sounds very much like what I would like to achieve! Like other have
replied here, I very much prefer your second approach, and for the same
reasons you list. Overloading close button semantic doesn't sound right for
something that's not intended to be a quick hack. As for the
One of the licences missing in the discussion is the "I Don't Want A
License License" :-).
I noticed that several main contributors of original stuff are UNconcerned
with licensing.
TBH, since no one here is known or cared for, so what is the Ultimate
Difference?
Is this a hot sweat over
Twederation is a pipe dream for this. Its not ready.
IMO, I think that a plugin architecture could build in "Announcement" that
is neutral on its specific sponsor.
The point is to GET ON WITH IT before we all expire.
Josiah
Ste Wilson wrote:
>
> I think that should be be an opt out option on
I think that should be be an opt out option on the getting started tiddler
along with twederation (once the unique date thing is sorted ;)) so that the
community links and grows.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe
Hello Josiah,
the gizmos will live on in the "AddOns" section and on the demo page, which
is now using the new plugin version an gets the gizmos back one by one.
I've changed many small things in the meantime, so some things need to be
updated in those tiddlers, too
Generally, I want to use
Ciao Dave
Like the Reddit Effort to list plugins...
https://www.reddit.com/r/TiddlyWiki5/wiki/pluginsandresources
... you are illustrating the NEED for TiddlyWiki to CENTRALISE plugins. FOR
TIDDLYWIKI to get USED MORE. A huge amount of its utility is in PLUGINS.
They are still second-class
Hi, it's me .. Mario.
Hope I'm also allowed to respond ;)
Disclaimer: I'm not a lawyer, so the following comments reflect my personal
opinion and may be wrong ;)
> I've recently made a plugin for TiddlyWiki (tiddlytouch.tiddlyspot.com
>
Ciao Jeremy & TheDiveO
I'm thinking here from the surface level of what would be useful to me.
Single (whole viewport) Tiddlers would seriously ease Slide Shows, Graphics
Galleries, Presentations.
I can't conceive of these without *Previous* & *Next* navigation buttons.
I DO understand these
Ciao Simon
I'm looking and will comment in a couple of days after I played with it.
One point I can make right away is that the various "gizmos" you took out
for this version---I understand why--however, for a new user, they are
extremely helpful in illustrating what it can do.
I guess with
Hello,
Is there a way to transclude <>'s text or <$set> its text to
a variable?
Since <> is short-lived, in that it's created on drag and
destroyed on drop, I assume that transcluding and setting its text to a
variable would need to be performed using some kind of an <$action> within
the
>
> Simon,
>
> Love your work and look forward to the 0.1.2 that includes readme, docs
> etc. I am sure you are on top of it but just want to point out that for
> TiddlyTouch and Muuri, understanding what can be achieved, its purpose and
> function is only present in pieces in the discussion
Hello Abraham,
I've recently made a plugin for TiddlyWiki (tiddlytouch.tiddlyspot.com) and
added an MIT license.
Now I'm thinking about what would be the proper license choice for my
plugin.
There's the BSD-2 license or the MIT license, what if people get interested
of using it in a
23 matches
Mail list logo
