TW into public hands

[TiddlyTweeter]

@oflg

… best thing about TWPUB is that it is dynamic and card-based, and can be put together very well, which fits well with the incremental reading proposed by SuperMemo author Piotr Wozniak.

Right. And interesting you can go more with it too. Easily adding linked “segues”. And potential to annotate to infinite transcluded (i.e. nested) note depths.

I thought your OP very interesting.

Just comments
TT

[markkerrigan]

Chiming in here with my general thoughts on TWPUB. My challenge is I would like a way to read EPUB directly in the browser, but also as typographically pleasing as possible. I would like to read them within a TiddlyWiki so I can customize the CSS as much as possible. Unfortunately most EPUBs that one might encounter aren’t always internally (HTML) or typographically consistent (em dashes for example). I’m not sure if this use case of using TWPUB as a general purpose EPUB reader is even possible.

[anon5541130]

@poc2go

Focus as a business communication product?

1. I recently wrote about creating a standard to make filters for plugins, themes etc within tiddlywiki - so that tiddlywiki is more consistent, logical and non-linear too… anyway this is the first step.

2. The second step is to have more serious governance as a community, to focus on really building more value. For this second case, some companies do things like ‘user questionnaire about user experience’, ‘some companies implement ITIL to organize services and products’, ‘other companies tried to extend the product - see Figma that works and/or integrates practically any web product like google drive to display files inside a design project etc’

[anon5541130]

each way is good or bad in some cases, but what I want to leave here would be this idea… to seek what the end user wants, in this case the people who will use the tiddlywiki software that can be developers, non-technical users or end users (companies, business partners, schools, institutions, governments, non-governmental organizations, etc.)

[TiddlyTweeter]

@anon5541130

what I want to leave here would be this idea… to seek what the end user wants, in this case the people who will use the tiddlywiki software that can be developers, non-technical users or end users (companies, business partners, schools, institutions, governments, non-governmental organizations, etc.)

Right. What is interesting in your point is the potential complexity of doing that well … What I mean is the “languaging” to those different groups might well need to vary?

For instance, in my own case I learn what a tool is by examining it “visually”, using it. But that implies it already exists–that I have something to examine .

I think that is a bit different for those users/devs who better understand the underlying tech? They are more able to “think-forward” to what an app “looks-like” even though it does not yet exist?

Just a comment
TT

[anon5541130]

@TiddlyTweeter

Right. What is interesting in your point is the potential complexity of doing that well … What I mean is the “languaging” to those different groups might well need to vary?

this I don’t find that problematic, big apps have a search category… the same could apply here - example: “plugins”, “models”, “templates”, “templates to gamers”, “plugins for developers” etc

[anon5541130]

@anon5541130

this I don’t find that problematic, big apps have a search category… the same could apply here - example: “plugins”, “models”, “templates”, “templates to gamers”, “plugins for developers” etc

another way to make tiddlywiki better in terms of GUI, user experience could be this:

• add showcase in tiddlywiki as Framework7 Showcase and/or https://threejs.org/ → https://tiddywiki.com /showcase/
• add ‘user questionnaire about user experience’
• 'implement ITIL to organize services and products’
• tried to extend the product: opensource/closed-source/public-source/foss source etc

[TiddlyTweeter]

@anon5541130

this I don’t find that problematic, big apps have a search category… the same could apply here - example: “plugins”, “models”, “templates”, “templates to gamers”, “plugins for developers” etc

Right. I’m not disagreeing with you really. I’m not anti-centralisation.
As @jeremyruston wrote—of some points I made earlier …

@jeremyruston

That way of thinking doesn’t appeal to me because it always ends up turning TiddlyWiki into something else, a lowest common denominator clone that doesn’t have the power to make people’s hearts sing.

So, I may be in a minority of one?

But it seems to me that, finally, there are TWO main routes …

1- From TW Central to find “Fitted Applications” (your cases)

2- From An Application to find TW Central (my thought case)

Both seem viable to me and could complement each other.

I think it is an empirical matter to know where & when one is better than the other?

Just a comment, TT

[anon5541130]

@anon5541130

this I don’t find that problematic, big apps have a search category… the same could apply here - example: “plugins”, “models”, “templates”, “templates to gamers”, “plugins for developers” etc

another way to make tiddlywiki better in terms of GUI, user experience could be this:

• add ‘user questionnaire about user experience’ → this could be done here on discourse or anywhere like google forms
• 'implement ITIL to organize services and products’ → this could be done here on discourse or anywhere like google forms
• tried to extend the product: opensource/closed-source/public-source/foss source etc → this could be done here on discourse or anywhere like google forms
  • add a category in discourse called integration or business partnership - where we can advertise companies that want to implement tiddlywiki

[poc2go]

TiddlyWiki foundation and philosophy is geared toward individual and personal longevity of data security and access. But in a commercial world is more about publishing timely updates of evolving and current data sets.

In the commercial world time is everything. The quicker can be implemented, the sooner, and less costly the better. Is not storage of dated information.

The real question is what is the focus of TiddlyWiki? Is it to store and preserve personal information, or to be used as a tool to publish changing information to the world? If for personal information - then TiddltWiki is pretty much complete. Is only a matter of enhancing personal access to that data, with ever more complex filter markup - with """, {{{, <<. Which is making personal data more unaccessable barring a full, indepth understanding of TiddlyWiki internals.

More and more of TiddlyWiki development has been focused on online, cloud based information presentation and synchronization. Just a quick view of all the ‘saver’ options will contest.

The number one issue with selling TiddlyWiki to the corporate ‘board’ is the learning curve. The power of JQuery and BootStrap is they are ‘dumbed’ down. JQuery allowed a single codebase to work in IE, Chrome, FireFox, Sarfari - without special coding; Bootstrap allowed menus, headers, content, and footers to be built quickly without knowledge of the underpinnings required to make it work. Want a a new font? Google Fonts - given a high level CSS (html, body) change - re-visualizes the site.

I find TiddlyWiki to be unfocused. @jeremyruston has always insured that data remain compatible from software release to release - and kudos for that, but there is a point where the software development of two decades ago - just can not compete with our quickly evolving world. Javascript now has ‘classes’ - gone is the era of 'prototype’s.

As @TiddlyTweeter would say - ‘Just a comment’

[TW_Tones]

@poc2go

Which is making personal data more unaccessable barring a full, indepth understanding of TiddlyWiki internals.

That is not true. The Data is accessible and always will be, and features allow you to make it more accessible with automation.

@poc2go

The power of JQuery and BootStrap is they are ‘dumbed’ down.

Actually TiddlyWiki is easier than those if you know, learn tiddlywiki.Its a higher level “language”.

@poc2go

work in IE, Chrome, FireFox, Sarfari -

• Tiddlywiki works in all these environments and more without difference.

@poc2go

Bootstrap allowed menus, headers, content, and footers to be built quickly without knowledge of the underpinnings required to make it work.

• Bootstrap CSS can be use in tiddlywiki along with other open source

@poc2go

Google Fonts

• Work in tiddlywiki

I am happy to “agree to disagree”, but I do

[pmario]

@poc2go

Javascript now has ‘classes’ - gone is the era of 'prototype’s.

Javascript is still a functional language, and classes us just some syntactic sugar that initializes the prototype chain.

[TiddlyTweeter]

@pmario

Javascript is still a functional language, and classes us just some syntactic sugar that initializes the prototype chain.

I have no idea what that means!

But it sounds like maybe I should?

Does it matter that @poc2go comments …

@poc2go

Javascript now has ‘classes’ - gone is the era of 'prototype’s.

Attempting to understand, TT.

[TiddlyTweeter]

@poc2go

In the commercial world time is everything. The quicker can be implemented, the sooner, and less costly the better. Is not storage of dated information.

That whole reply is fascinating to me anthropologically!

Basically the intersection of tech. with changing socio-cultural themes.
It is real.

I do think that TW history might make for a very interesting longitudinal study of changing socio-culture business imperatives and their impacts on everyone.

Regarding your OP, I do think “The TW” is perfectly suited to be (with a bit of thought) a premium info. distribution system/format.

Just a comment, TT