My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 5: Improve clock creator
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by gars...@gmail.com, Mar 14, 2008
Right now, as of v0.01, the epiClock takes strings of arguments, which is not elegant, or efficient, or 
the way the project should work. With the next rollout, we're going to move to an object based 
parameter system, so instead of:

epiClock.make('element_id','clock_mode','clock_view','clock_format',...);

you'll call

epiClock.make(element,{mode: 'CUR', view: 'FLIP', target: '10/10/2010 10:10 PM"});

or, conversely, you will have an autoloader function, defined through the object:

<div id="clock1" class="epiClock" display="mode: 'CUR'; view: 'FLIP';"></div>
Mar 14, 2008
Project Member #1 gars...@gmail.com
I've redone the system's creation routines, so instead of calling epiClock.make() and epiClock.preLoad(), the 
sequence for the next milestone will be:

epiClock.set('id',{param: 'value', param: 'value'});

or, for multiple clocks:

epiClock.set({id: 'ID', param: 'value'},{id: 'ID2', param: 'value'});

with an alternative syntax for multiple clocks with:

epiClock.set('id',{param1:'value'},'id2',{'param2:'value'});

If using the alternative syntax, however, be sure that you pass your params ALWAYS in the fashion: 
'id',{params},  'id',{params}
Status: Fixed

Powered by Google Project Hosting