Timeline


and .

08/05/09:

18:44 Changeset [40] by rsm
18:43 Changeset [39] by rsm
18:43 Changeset [38] by rsm

More models for Access

18:42 Changeset [37] by rsm

Send stringified data in EEML, Added partOfPlugin in API code etc

18:40 Changeset [36] by rsm

More completions on the robot side code

18:39 Changeset [35] by rsm

Adding partOfPlugin tag, changing resource generic options from milli-seconds to seconds etc.

18:00 Ticket #11 (The combination of Features and plugins together: Is it handled correctly?) created by rsm

Each feature can have more than plugin (can it?) and more importantly, multiple features can have the same plugin (again, can it?).

Should make sure, if such combination make sense in the real world and if yes, need to make sure it works.

14:18 Ticket #10 (handle multiple instances of the same feature) created by rsm

Currently, one feature can be listed only once within the robot. And we do not support multiple instances of the same robot (mainly due to EEML limitations).

See  http://web.goodrobot.com/blog/2009/08/howto-handle-multiple-instances-of-the-same-feature/

11:07 Setup.exe attached to DevSetupCreation by ashokc
11:06 DevGettingStarted edited by ashokc
(diff)
11:05 DevSetupCreation created by ashokc

08/03/09:

18:12 Changeset [34] by rsm
18:11 Changeset [33] by rsm

This time it is all about Feature Mappings

08/01/09:

22:41 Changeset [32] by rsm

Plugin XML files

22:39 Changeset [31] by rsm

It's all about plugin mappings

07/30/09:

20:06 Changeset [30] by rsm
19:59 Changeset [29] by rsm
16:35 DevWindowsService edited by rsm
(diff)
16:16 DevGettingStarted edited by ashokc
(diff)
13:47 DevWindowsService created by ashokc
05:48 Ticket #9 (Have to handle RobotConfig Additions/Deletions, when Robot is modified too) created by rsm

07/29/09:

12:40 HowtoGetFeatureDef edited by rsm
(diff)
10:57 DevGettingStarted edited by rsm
(diff)
10:52 DevGettingStarted created by rsm
10:43 WikiStart edited by rsm
(diff)
10:43 WikiStart edited by rsm
(diff)
09:35 Changeset [28] by rsm

Minor changes to xsd/xml

07/28/09:

13:11 Ticket #8 (Handle data storage at the server end and make it viewable) created by rsm

1. Record required sensor data (take hints and inputs from Feature XML)

-- Design and implementation on which data to store, how long to store and how actually to store them (for easy retrieval)

2. Ability to view historical sensor data (graphs, CSV)

-- API changes as well as web page changes

13:02 Ticket #2 (Merge Model ComponentsOfRobot with RobotConfig) closed by rsm
fixed: Done. Now the models are: Robot RobotUserACL Feature RobotFeatures? …
12:49 Ticket #7 (Twitter and Pachube support) created by rsm

Support for Twitter and Pachube for GoodRobot..

The basic idea is to allow "control" inputs from Twitter and Pachube environments and also provide "feeds" for Pachube from "resource" outputs.

Need a clear design in terms of what should be accomplished, and how to accomplish the same. Followed with an implementation.

There is likely to be a component, that sits on the server, and talks to the server using the API and interfaces with Twitter and Pachube.

12:34 Ticket #6 (Public key based signature authentication for every API call) created by rsm

This is similar to Amazon AWS signature

12:32 Ticket #5 (Setup Robot end Python packaging tasks) created by rsm

Robot end:

1) Python packaging, Qt packaging
2) Setup installer for Windows (Setup.zip --> click, next, next, Installed). Inno Setup is a good such tool.
3) Setup installer for Linux -- only Debian packaging .deb
4) Setup "service" for Windows -- where Python scripts can run on bootup
5) Setup "service" for Linux -- simple /etc/init.d shell script to start/stop/status

07/26/09:

23:05 Changeset [27] by rsm

New XML files for feature

23:04 Changeset [26] by rsm

web -> www

23:04 Changeset [25] by rsm

Several changes in eemlx and feature XSD

23:02 Changeset [24] by rsm

Make changes to support new redesign on component,feature and implement initial parts of getFeatures

23:01 Changeset [23] by rsm

Redesign component, features - renamed several models and changes related to that

23:00 Changeset [22] by rsm

Implement initial parts of getFeatures

07/22/09:

18:47 Ticket #1 (Change type as input and output to control and sensor data) closed by rsm
fixed: It is now handled as "control" and "resource" data.. Again, the term …
18:39 Changeset [21] by rsm

initial commit of EEMLx XML schema 001

18:38 Changeset [20] by rsm
18:38 Changeset [19] by rsm

1) type parameter is not anymore 'data' specific, but Feature specific 2) Add plugins parameter

18:35 Changeset [18] by rsm

1) Sort changes so XML output is in expected sequence 2) Support for handling EEMLx

18:25 Ticket #4 (api.py: toXML() should return on order as expected by EEML schema) closed by rsm
fixed: Fixed the problem, by adding a self._array, while adding elements - so …
16:13 EEMLx edited by rsm
(diff)
13:32 WikiStart edited by rsm
(diff)
13:27 WikiStart edited by rsm
(diff)
13:26 HowtoGetFeatureDef created by rsm
13:26 WikiStart edited by rsm
(diff)
13:07 EEMLx edited by rsm
(diff)
13:07 HowtoGetConfig edited by rsm
(diff)
12:53 HowtoGetFeatureList created by rsm
12:51 EEMLx edited by rsm
(diff)
12:05 WikiStart edited by rsm
(diff)
12:03 EEMLx edited by rsm
(diff)
12:03 HowtoGetConfig created by rsm
11:47 WikiStart edited by rsm
(diff)
09:02 EEMLx edited by rsm
(diff)
09:01 EEMLx edited by rsm
(diff)
08:18 Components edited by rsm
(diff)
08:15 WikiStart edited by rsm
(diff)
08:13 EEMLx edited by rsm
(diff)
07:43 EEML created by rsm
07:35 WikiStart edited by rsm
(diff)
07:32 GoodRobot edited by rsm
(diff)

07/21/09:

21:54 GoodRobot created by rsm
21:53 EEMLx created by rsm
21:47 WikiStart edited by rsm
(diff)
21:05 WikiStart edited by rsm
(diff)
21:04 WikiStart edited by rsm
(diff)
21:04 WikiStart edited by rsm
(diff)
21:02 WikiStart edited by rsm
(diff)
16:35 Changeset [17] by rsm
16:34 Changeset [16] by rsm

updated for mapping

16:34 Changeset [15] by rsm

updated for mapping

07/13/09:

11:28 Milestone 2 completed
By the end of this milestone, following would be …
Note: See TracTimeline for information about the timeline view.