Hi Ed, Mat, Good to see you back, and good luck with your recovery. Your concerns echo some of my mine over the years, but happily I don’t think they apply to most of the conversation here.
The context is that we use system tags as a common extensibility mechanism throughout the core user interface, and it has proven to work successfully. From Mat’s question arises the proposal of bringing that same extensibility mechanism to the way that plugin information panels are displayed. I’ll respond to Mat’s specific questions momentarily. Best wishes Jeremy > On 11 Jul 2019, at 14:18, Ed Dixon <[email protected]> wrote: > > Hi all. > > Been a long time since I have done anything with TW5 or anything else for > that matter, still recovering from brain surgery where damage was definitely > done but I have been lurking both forums all along (for years now without a > word!) and regretfully find trying to use even the most basic functionality > of TW a challenge due to its already built-in amazing flexibility and > functionality. So I may be way off on this and want to say up front, first > and foremost, I mean absolutely no disrespect to anyone involved here. > However, as I am understanding this, I simply can not stand to watch this > thread continue much longer. I can picture Jeremy right now trying to figure > out how to allow an end user turn his fine-tuned jet airplane into a space > station at the cost of other useful functionality he may be trying to add, He > has proven to work very diligently on feature requests (usually very > successfully) to provide needs that also meet the applications goals but this > one is simply too much to ask IMHO and I do hope Jeremy seriously gives that > consideration. I made a similar request years ago to meet a specific need > that I no longer have, and couldn't implement now even if he gave me > supervised directions complete with pictures on how to do so. Despite all > that he probably did add that functionality (I can't even remember what it > was at this point) and hope it didn't cost him too much time or if so it did > turn out to be of use to the project as a whole. > > That said, My first instinct to a thread suggesting a core change would be to > fork it and go for it yourself (which is what I wish I had done while I still > had the chops to try to do so) I am a little surprised this hasn't already > been suggested. He can always implement those changes back into the core if > it meets his requirements without the cost of a lot of his own time (GOD > bless GIT). But be prepared to meet all the needs of his overall goals with > TW5 and ALL the complexities that imply. Such as the Internal mechanisms that > other core mechanisms may rely on that are based on the one you intend to > change, the responsiveness of the application, clarity, and functionality for > the typical and advanced end-user, testing to make sure changes have not > broken any other functionality, any and all security implications involved, > and everything else that Jeremy so diligently provides us with this amazing > tool. > > I can understand a need to add special functionality a specific project might > require at the cost of some of this (as I think was my case, my memory is > shot) but given that the core has been built with the ability to transclude > even itself providing what I feel is as much flexibility as one could expect > and should allow almost anything within reason to be possible,. perhaps at > this point, TW5 has reached a point of maximum returns in regards to adding > new plugin programming features (especially if they are for specific needs > and not the project as a whole)? (again all IMHO and yes I admit I am a total > fanboy, his work on this is and was totally mind-blowing at least for me > anyway LOL!). > > Thanks for taking the time to read all this if you made it this far I tend to > rant on and on at this point... > > On Friday, July 5, 2019 at 2:51:08 PM UTC-5, Mat wrote: > So I'm working on a plugin that, among other things, will give plugin update > alerts. (never mind how) > > I want to show this alert in the regular plugin list, ideally in the > $:/core/ui/Components/plugin-info tiddler which is the one showing each > separate plugin as a "row" in the plugin list. > > How should one approach manipulating core components? It is one matter for > personal tweaking but not so good when making public plugins. ...besides, > whose shadow tiddler wins? Once my overwrite is in a plugin it is no longer > an overwrite but a shadow, so which one should the system choose? > > Jeremy has mentioned putting in hooks which I interpret to mean things for > these sort of matters... so should I just "request a hook" and specify > exactly where? Or maybe I'm using the term "hook" in a faul way. > > <:-) > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/2183b04d-fdea-4e0e-a990-38dc8411cf0d%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/2183b04d-fdea-4e0e-a990-38dc8411cf0d%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/4FC9C9B9-B369-4D49-B33C-B8101173F15D%40gmail.com. For more options, visit https://groups.google.com/d/optout.
