Hi Tristan,
Thanks for your continued support and encouragement of this project. We're
reaching the end of the Alpha Phase of development, as the *{{DesignWrite}}*
MOOC course comes to an end for this current semester in a few weeks. Once
our semester project (TiddlyCRM v0.0.1-alpha) has been submitted and
assessed as part of the course, we'll be beginning the Beta Phase of
development of TiddlyCRM. At that time we'll be inviting wider contribution
from the TiddlyWiki user community.
My co-conspirator on the semester project, Andrew Myers, has developed that
awesome new collaboration method, as a hybrid between Dropbox and GitHub.
We'll probably open that up so more collaborators can participate in the
project once we reach Beta Phase.
I like how you managed to create all those sample data for testing
>
Thanks, I was quite proud of how that turned out, particularly when a
certain member of the TW user community accused me of breaching privacy and
confidentiality
<https://groups.google.com/d/msg/tiddlywiki/SyLaBW_5UTU/b3ovgKhFBQAJ>. That
gave me a real sense of achievement, that the random SampleData clearly
looks very realistic!
> and by playing around with the Playground, I get a pretty good impression
> of where TiddlyCRM is heading to.
>
Thanks, my own observation is that it seems fairly straightforward at this
point. I hope it stays that way! Haha.
> I did however not manage to add a new contact via the interface. I figure
> you did not yet implement this functionality?
>
There is much that isn't properly working yet. Take a look at our other
playground <https://tiddlytest.github.io/>, and you'll see where we're
playing with Eric Shulman's *<<combobox>>* macro to help us design the Add
and Edit functionality.
> And I got another problem, which is not TiddlyCRM-only (contact management
> in TW is tricky here) as I know a hand full of people, that have exactly
> the same names. Maybe some sort of UUID would be good for person or
> organisation tiddlers to avoid collisions? I think Tobi has a plugin or
> macro which creates UUIDs.
>
> Then you could store the name in another field and use the UUID for
> linking etc.
>
Interesting that you should mention this. We've had a big discussion
internally about this very issue over the last couple of weeks. We've
settled on avoiding UUIDs for now, but I do agree with you that there are
huge benefits in using that approach. I have the feeling that we may have
to revise our decision on this matter in the future.
Kind regards,
Hegart.
--
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/30995f90-db25-45c1-b8f2-e3bc3aa9409a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
