Glamkit Event-tools 1.0 roadmap.

[Greg Turner]

Hi,

I'm opening up this thread to discuss and track progress towards Event-tools 1.0. Event-tools sites have been in the wild in various forms for coming up to a year now, and the main areas for improvement are becoming clear. The most critical of these are:

• Database queries are inefficient
• Event Generators are difficult to grok for site administrators
• Installation and integration is difficult, due to lack of documentation or examples

Happily the strengths are also apparent:

• Deals well with potentially complex events models.
• Deals with a variety of navigation patterns (multi-institution vs. single-institution)
• 'Djangonic' approach to modelling events. There's still a bit of magic which can be reduced, but most things are simple and explicit, and not overbearing on the developer.

Anyway, we at the Interaction Consortium are currently embarking on a couple of projects which, together, give us the opportunity to update EventTools to get us to a stable 1.0 release. We are aiming for a straightforward, but probably not automatic, migration process for sites implementing the newtools branch (most recently at https://github.com/ixc/glamkit-eventtools/commits/newtools, soon to become the glamkit master branch).

A draft roadmap is on the wiki at https://github.com/glamkit/glamkit-eventtools/wiki/Event-tools-1.0-roadmap, and comments and questions (and offers of assistance) are gratefully received.

Because this is a client-led project for us, we will be cracking on with this at quite a pace. We're using these projects as proofs-of-concept for a proposed stable API, and we'll release a demo for review in the next couple of weeks.

Greg.

--

Dr Greg Turner

Director, Technical Information Architect

the Interaction Consortium

http://interaction.net.au
Phone: +61 2 8060 1067

skype: gregturner
Follow us on twitter:
@theixc
@gsta

Be green! Read from the screen.

[J. Heasly]

Greg,

Thanks for the update and, of course, thanks for all the work!

Any/all improvements to Query efficiency would be especially appreciated.

Onward,

John

[Patrick Taylor]

Hi Greg (et al),

I'm very interested in trying out Glamkit Event-tools for one of our
projects, is using the ixc newtools branch still the suggested pre-1.0
release?

best regards
Patrick

On Aug 8, 10:12 pm, Greg Turner <g...@interaction.net.au> wrote:
> Hi,
>
> I'm opening up this thread to discuss and track progress towards Event-tools
> 1.0. Event-tools sites have been in the wild in various forms for coming up
> to a year now, and the main areas for improvement are becoming clear. The
> most critical of these are:
>

>    - Database queries are inefficient
>    - Event Generators are difficult to grok for site administrators
>    - Installation and integration is difficult, due to lack of documentation

>    or examples
>
> Happily the strengths are also apparent:
>

>    - Deals well with potentially complex events models.
>    - Deals with a variety of navigation patterns (multi-institution vs.
>    single-institution)
>    - 'Djangonic' approach to modelling events. There's still a bit of magic

>    which can be reduced, but most things are simple and explicit, and not
>    overbearing on the developer.
>
> Anyway, we at the Interaction Consortium are currently embarking on a couple
> of projects which, together, give us the opportunity to update EventTools to
> get us to a stable 1.0 release. We are aiming for a straightforward, but
> probably not automatic, migration process for sites implementing the

> newtools branch (most recently athttps://github.com/ixc/glamkit-eventtools/commits/newtools, soon to become
> the glamkit master branch).
>
> A draft roadmap is on the wiki athttps://github.com/glamkit/glamkit-eventtools/wiki/Event-tools-1.0-ro...,

> and comments and questions (and offers of assistance) are gratefully
> received.
>
> Because this is a client-led project for us, we will be cracking on with
> this at quite a pace. We're using these projects as proofs-of-concept for a
> proposed stable API, and we'll release a demo for review in the next couple
> of weeks.
>
> Greg.
>
> --
>
> Dr Greg Turner
> Director, Technical Information Architect
> the Interaction Consortium
>
> http://interaction.net.au
> Phone: +61 2 8060 1067
> skype: gregturner
> Follow us on twitter:

> @theixc <http://twitter.com/theixc>
> @gsta <http://twitter.com/gsta>

[Greg Turner]

Hi Patrick,

If I were you, I'd wait 12 hours and I'll have checked in the last major change to:

https://github.com/ixc/glamkit-eventtools/tree/api-tidy

I'll post here when done.

Greg.

@gsta

[Greg Turner]

That change is now committed. Enjoy!

https://github.com/ixc/glamkit-eventtools/tree/api-tidy

[Patrick Taylor]

Brilliant! I'll check it out.

cheers,
Patrick

On Sep 7, 7:23 am, Greg Turner <g...@interaction.net.au> wrote:
> That change is now committed. Enjoy!
>
> https://github.com/ixc/glamkit-eventtools/tree/api-tidy
>

> On 7 September 2011 15:10, Greg Turner <g...@interaction.net.au> wrote:
>
>
>
>
>
>
>
>
>
> > Hi Patrick,
>
> > If I were you, I'd wait 12 hours and I'll have checked in the last major
> > change to:
>
> >https://github.com/ixc/glamkit-eventtools/tree/api-tidy
>
> > I'll post here when done.
>
> > Greg.
>