My favorites | Sign in
Project Logo
       
Search
for
Updated Feb 04, 2010 by chris87
Labels: Phase-Design, Component-Actions
ActionsFormat  
Plans for alteration of the actions file format

Introduction

At the minute the actions system uses a Properties back end, which isn't particularly well suited to the job. A custom format would probably be quicker to read/write, much more flexible, and easier for users to edit.

Current format

trigger=CHANNEL_MESSAGE
conditions=1

condition0-arg=2
condition0-component=STRING_STRING
condition0-comparison=STRING_CONTAINS
condition0-target=${SERVER_MYNICKNAME}

response=/notify $highlightcolour
format=channelHighlight

Proposed replacement

%pack:
  version=0
  author=Chris Smith
  description=My uber action pack

$triggers:
  CHANNEL_MESSAGE
  ADDITIONAL_TRIGGER
  ETC

%condition 0:
  component=STRING_STRING
  comparison=STRING_CONTAINS
  target=${SERVER_MYNICKNAME}

%condition x:
  component=STRING_STRING
  comparison=STRING_CONTAINS
  target=${SERVER_MYNICKNAME}

$condition tree:
  (0|x)

$response:
  /notify $highlightcolour
  /etc

$format:
  channelHighlight

Sign in to add a comment
Powered by Google Project Hosting