Hi Tony!

I think Commander is in beta stage. It seems it is useful.  So, my aim is 
to get it working, fixing issues.
I try to keep it simple, modular and easy to understand.
By modular, I mean to be extended simply as Josiah noted above.

That is the objectives for time being.

--Mohammad


On Thursday, February 14, 2019 at 3:34:49 AM UTC+3:30, TonyM wrote:
>
> Mohammad,
>
> This question of "In the Core" is a repeating one and I believe often a 
> source of unnecessary debate. I hope I can shed a little light on it here 
> from my perspective.
>
> The key phrase I believe is "chose to remove"
>
>
>    - When something is in the core is is not removable from TiddlyWiki, 
>    even if it may be hidden by overwriting shadow tiddlers.
>    - People often confuse empty.html as representing the core, when in 
>    fact this is the minimum usable wiki, and yes, unless it is in the core it 
>    is unlikely to be seen in empty.html
>    - By popular demand anything can be included in empty.html but by 
>    definition it should remain a minimum usable wiki.
>    - I believe we should de-emphasise empty.html as a "developers minimum 
>    usable wiki" and provide other editions for new users, learners, editors 
>    etc... These editions would include the contents TOC and plugins that 
>    customise tiddlywiki for the target audience. For example commander could 
>    be in a standard.html edition or a designers.html edition.
>
> On Commander and Empty.html, I would not want Commander, ideally not even 
> tag manager and Tiddler manager in the core and thus always in empty.html 
> because what ever I build should not automatically contain components which 
> end users may use to break the designed wiki. Sure they may be included via 
> plugins in a standard.html edition, but as plugins I can "chose to remove"
>
> A new possibility I can see using designed wiki templates, (or the 
> proposed innerwiki plugin to run) is to publish a complete.html edition 
> that includes tiddlywiki.com and additional plugins like commander and 
> has a set of recipes that allows the user to export any of a set of 
> standard editions. My New User Edition is somewhat similar but adds tools 
> for the tiddlywiki student to maintain their own notes.
>
> The core is the place where if anycode is placed it becomes forever 
> committed to by the community, will always need maintenance, must be high 
> performance, must always be backwardly compatible, and is considered 
> minimum code.
>
> Only Shared Services and facilities should be in the core, and cases where 
> it is necessary for performance.
>
> Perhaps if we had deemphasised the empty.html prior to now, you would be 
> putting an argument if commander should be in empty.html or standard html 
> but in either case it should be a removable plugin and/or bundle.
>
> I do not think it should be the intention to install any optional tool in 
> the core.
>
> Regards
> Tony
>
>
> On Thursday, February 14, 2019 at 12:53:24 AM UTC+11, Mohammad wrote:
>>
>> If any feature gets into the core, then people trust it and are sure they 
>> will have long support!
>>
>> --Mohammad
>>
>> On Wednesday, February 13, 2019 at 12:47:15 AM UTC+3:30, Diego Mesa wrote:
>>>
>>> Lets not hijack this thread Josiah. Suffice it to say, I agree we should 
>>> first worry about whether it works. Then, whether it works well. I just 
>>> posed the question, as if the end goal is indeed to get into the core, it 
>>> would be logical to eventually bake this into $:/Manager's UI somehow. 
>>>
>>> Me wanting to see a plugin in the core, is the highest compliment I can 
>>> pay the plugin. 
>>>
>>> On Tuesday, February 12, 2019 at 3:09:50 PM UTC-6, @TiddlyTweeter wrote:
>>>>
>>>> what is with "core" that  so easy comes upfront?
>>>>
>>>> i'd rather know it works well. 
>>>>
>>>> "core" additions are something else. much later. IF proven for that,
>>>>
>>>> this looks like great addition--but in process.
>>>>
>>>> likely a plugin.
>>>>
>>>> let us deal with what it is dealing with first.
>>>>
>>>> On Tuesday, 12 February 2019 19:54:44 UTC+1, Diego Mesa wrote:
>>>>>
>>>>> Hey Mohammad,o a
>>>>>
>>>>> This is great! Any thoughts on getting this into core so its part of 
>>>>> `$:/Manager`?h later.
>>>>>
>>>>> Diego
>>>>>
>>>>> On Tuesday, February 12, 2019 at 9:30:53 AM UTC-6, Mohammad wrote:
>>>>>>
>>>>>> Announcement: Tiddler Commander
>>>>>> Date: Feb 12th, 2019
>>>>>> Status: beta (idea)
>>>>>>
>>>>>> Demo: *https://kookma.github.io/TW-Commander/ 
>>>>>> <https://kookma.github.io/TW-Commander/>*
>>>>>>
>>>>>>
>>>>>>
>>>>>> Referring to the discussion here: 
>>>>>> https://groups.google.com/d/msg/tiddlywiki/BxJsWuae-Uc/JapAx4mtBgAJ
>>>>>> I have prepared a small toolkit called Tiddler Commander or in short 
>>>>>> Commander. This is a proof of concept and
>>>>>> both the name and operations can be changed.
>>>>>>
>>>>>> I highly welcome any constructive idea and I hope get feedback from 
>>>>>> both users and developers.
>>>>>>
>>>>>> I also welcome any collaboration as is discussed in other posts.
>>>>>>
>>>>>> Warning: This is a beta release and is not in form of plugin! Do not 
>>>>>> import to your own wikis because of the risk of data loss.
>>>>>>
>>>>>> Cheers
>>>>>> Mohammad
>>>>>>
>>>>>>
>>>>>> likely
>>>>>>
>>>>>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6acc05be-84e8-4786-91f0-47ff6b6b33f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to