don't tag new realm with current realm (process menu) #35
Conversation
|
i originally opened this pull request with the master branch of my fork, which I'm now maintaining, so closing this PR as no longer valid. |
|
Hi Eric, Sorry for the lack of response. I don't have much time for maintaining mGSD any more, (no big news there). Glad to see it's still useful though and I think it's cool you're maintaining it and fixing it for TiddlySpace. Recently I've been looking at a TW5 rewrite by @roma0104 callsed GSD5. Have you seen it? Perhaps we can talk about updating the mGSD website at some point, at least to provide some current information for users. Cheers, Simon. |
|
Hi Simon, no worries! I found @roma0104's TW5 app after I'd already done some maintenance work on mGSD. It looks really interesting, at the very least as a proof and template for making something like mGSD within TW5. Previously I hadn't really looked at TW5 closely and had been more focused on the idea of making a SPA for TiddlyWeb. My main concern with GSD5 is that it uses a different representation of the data model - one field per semantic relationship rather than "everything is a tag" as in original mGSD. I really like the simplicity of the mGSD representation, and want to make something which is bidirectionally-compatible with data created using mGSD (at least until the new product is complete enough to replace mGSD, then backwards-compatibility is enough). Also just want an excuse to pour through TWC code and understand how it works before closing that door forever 😢 I know TW5 can read TWC tiddlers (including their tags), and by default displays a warning. Not sure yet if the warning can be disabled and if it can write them back out, but I don't see why not. I'm currently doing some experimentation with @cdent's tank to see if I can get mGSD working well there. Once things are stabilized and I'm satisfied with the documentation I was thinking to send out an email announce to the lists. |
fixes #34