Just pushed the latest, rewritten version of #taproot live!
Trying out note posting on a fresh install of the new #taproot
sandeepshetty yep, this is certainly something I need to document on the wiki.
In fact most of the machine tags were a hack to add schemaless data to my MySQL-managed schema, but as I move to flat files + ad hoc indexes I might migrate some of my machine tags to “real” data — it’s not like they’re doing much good where they are at the moment.
The main benefit is easy editing — I just use my tag editing UI instead of building another UI for each different bit of data.
This morning’s #taproot update: ditched the crappy old DRY-violating tags module and replaced it with a super lightweight #hypermedia one. Soon I’ll add the ability to store tag descriptions, synonyms/related tags as well as dynamically pull content in from the URLs it lists so the tag pages aren’t quite as boring.
I’m noticing a #taproot pattern emerge whilst writing the simplified auth code: multiple event listeners which don’t know about each other working on the same object, augmenting and changing it.
E.G. RememberMeListener looks for an encrypted cookie with a URL (my user ID of choice) in — if it finds one it makes an ActivityStream person object and puts it in request.attributes.user.
Then, in the same event chain but at a lower priority level, the Contacts module looks in request.attributes.user for a URL. It looks up the URL in my people DB and, if there is anyone, augments request.attributes.user with all the extra info (full name, roles, photo URL, rel value, etc.)
Then, another listener could run, looking for request.attributes.user with only URL — and look the URL up on identengine.com, caching the response.
Other example is @-name autolinking, working on a similar basis of: basic transformation (raw data => common data format), then progressive augmentation adding URLs, names and rel values.
I think this a very powerful and flexible pattern and something I will make a founding principle of Taproot.
Finally decided that symfony Security component is way too complicated for my little #taproot, so ditching it — but I’ve learnt a lot from digging through it and my further efforts will try to provide some of the amazing flexibility it gives whilst being more performant and easier to understand #php #dev #meta
Anna Debenham in your style guide researches, have you come across any great open source project styleguides? I’m looking into making myself more design-accountable for a project I’m releasing soon.
Spent a productive morning at the workshop making #gurdy keys (these keyboards are much bulkier than my previous one and should be more substantial and satisfying to play as a result), then toddled off to Dartington to be a stage hand for Devon Baroque w/ Robin Andrews. Now working on #taproot music module, might have a go with Glenn Jones’ microformatshiv.com later.
Rolled out usage of the
menu element on #taproot. I’m looking forward to more browser support for HTML context menus, that will really open up the possibilities for cross-browser extensions