Mario, I understand the developer perspective, because I was one before, I hope to be again.
I hope I did not cause offence. I have no desire for special handling, for my current problems, my own solutions are usually systematic and with the future for all of us in mind. Perhaps this has come form my design and developer experience. In this use case I am simply trying to have additional date fields, and the way created and Modified dates have being implemented are not so transparent to me. And of course the apparent UTC Problem. When I speak of a disappointment, or need to resolve/extend TiddlyWiki I speak as "We" and are not criticising, but contributing. In fact I have given this a lot of thought, with a view to maximising utility, In many ways I am getting close to designing a solution myself, inside the constraints of the current version. Unfortunately I have YET not learned what I need to, to contribute in GitHub, and developer circles. This may be the issue where I start using Git-Hub. My Own First plugin - that still requires polishing, MyMenus leverages the Wikification of values in fields to create an extremely extensible solution, and I hope will result in a treasure trove of "Code" snipits. I for one are all about generic, non specific, open and reusable solutions. So lets see If I can contribute, perhaps even to "make an implementation, that is "generic enough" to be easily used". Possibly my greatest fear is not having the ear of those who influence the core, and the time to speak in my less than trained words about my ideas, to such people (perhaps like yourself). You may have seen my discussions in relation to making fields first class citizens, like tags are, when a Tag can also be a tiddler, I am already allowing fields to be represented by a tiddler, or field-tiddlers to be created that support many of the features your linked to in "Typed Fields" and "lookup fields" do. I expect these to be complementary, but personally I am not so sure typed fields are essential. I would be concerned if fields became stricter in definition, since their openness is already a powerful feature I am exploiting. The Lookup idea that Tobias starts the thread with is an important idea, That my solutions is endeavouring to solve along with others, the related field-tiddler can store one or more lookup "filter(s)" that that can be used to populate that field where it is used in tiddlers along with other intelligence. I am also trying to get the field tiddler to include macros, lists, create, edit and even related fields tools and even CSS data. All I hope is a little tweeking to allow to make such field manipulation a little user friendly. Thanks for your background and inside knowledge, it helps me learn. Regards Tony On Friday, March 16, 2018 at 8:03:02 PM UTC+11, PMario wrote: > > On Friday, March 16, 2018 at 2:37:54 AM UTC+1, TonyM wrote: > ... > > Without "special" field modules registered at startup we should have an >> easy to use date field mechanism, >> > > >> after all we would expect this to be a common requirement for tiddlers, >> such as due, review or expiry dates etc.. >> > > As a developer you'll never know, how your users will use your software. > Most of the time in a completely different way as you expected it. ... > > So because you as a user need "your own special handling" for the problem > you want to solve at the moment, you expect it, to be there and it should > be easy to use. > That's ok. > > On the other hand, as created, modified and so on where developed, Jeremy > implemented just enough code, to solve the problem he wanted to solve at > this point in time. > The implementation is done in a "relatively" modular way, so it can be > extended. ... BUT ... The code hasn't been cleaned up, since then. > So the implementation is not as polished as other functions in TW. ... > > That's the status quo, atm, because nobody made an implementation, that is > "generic enough" to be easily used. ... > > There have been some discussions at github about "typed fields" > > see issue: lookup-fields (or relationship-fields) #1324 > <https://github.com/Jermolene/TiddlyWiki5/issues/1324> a relatively long > discussion, and > the condensed version: typed fields #1331 > <https://github.com/Jermolene/TiddlyWiki5/issues/1331> > > So it's not only the type of a field, that is important. .. eg: If we have > a type: date, we also may want to have UI to view/edit the: date, > checkboxes, option fields, tag-like fields ... as described in the > issues. So it will be easy to be used ;) > > have fun! > mario > > -- 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/a8cd5544-17bb-4a69-8b68-3bdedd49bab2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
