Thanks for the comments, I will summarize the questions and answers below.
1) Page 5, line 9~13
What means that "no node is matched"? Does it mean that there is no desktop
entry existed under proper folder or the entry file not recognized by Daemon?
If so, why we support to start up such applications in Genesis?
If an application has been executed, can I start up another instance for same
application?
[Horace] 'no node is matched' case is particularly for starting up application
by application binary path. In theory, Genesis will preload all of the desktop
files that are installed in OS, and manage them. When developers start up an
application by giving the application binary path, that application binary
might be managed in Genesis. Following that, Genesis will create a new app
entry node for it, filling in proper values, like exec and name, and append it
to the applications list.
Genesis only allows application running as single instance handle, so that if
application has been already running, genesis will simply bring up its window
on the top.
I will add these descriptions in my design doc. Thanks.
2) Page 5, line 14~16
How to monitor and handle the status of running applications and what are the
reactions to the unexpected situation?
Does any mechanism to update process id if a process was killed by user or by
some exceptions?
[Horace]Currently, With PID returned, Genesis will add a watch function to get
process exit status notification. I am still figuring out the way to acquire
process runtime status. When the running process exits, Genesis will get
notified and then update the recorded PID to its default value.
3) Page 5, line 18~21
What are the expected actions if find applications (which is running)
updated/uninstalled?
[Horace]This is a good question, I didn't think of this situation. As far what
I can think of is to record the updated/uninstalled event, which is handled by
FS monitor, and wait for the running application exiting. After running
application exits, Genesis daemon could then update the correponding
application entry data structure, or removing the application entry node from
applications list if application is uninstalled.
4) Page 5, 5.5 Unit Test
Do you think of using some unit test framework, like "check", to wrapper all
test cases and run them automatically?
[Horace] I am not quite sure about "check" and unit test framework. At current
stage, I am planning to simply test the APIs that are exposed to developers. I
will think of automatic testing if it is available.
5) Page 6, 5.3 Goals
The #2 goal:
2. Gracefully acquiring and managing metadata from non-freedesktop
aligned applications
What kind of the non-freedesktop application's metadata can be managed?
[Horace] This feature is done like what I described to answer question 1, like
when developers giving a single binary path, Genesis will fill in the
application entry data structure for it and append it to the applications list.
I will post the revised design document later with all your suggestions
included.
Thanks,
Horace
-----Original Message-----
From: Yang, Lei A
Sent: 2008年9月2日 15:53
To: Yang, Lei A; Li, Horace
Cc: [email protected]
Subject: RE: [Moblin Dev] RE: Application life-cycle manager design doc draft
isattached.
One more thing:
5) Page 6, 5.3 Goals
The #2 goal:
2. Gracefully acquiring and managing metadata from non-freedesktop
aligned applications
What kind of the non-freedesktop application's metadata can be managed?
Lei Y
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yang, Lei A
Sent: 2008年9月2日 14:15
To: Li, Horace
Cc: [email protected]
Subject: [Moblin Dev] RE: Application life-cycle manager design doc draft
isattached.
Horace,
I just reviewed the design doc.
Here I provide my feedbacks to you about this document:
1) Page 5, line 9~13
What means that "no node is matched"? Does it mean that there is no desktop
entry existed under proper folder or the entry file not recognized by Daemon?
If so, why we support to start up such applications in Genesis?
If an application has been executed, can I start up another instance for same
application?
2) Page 5, line 14~16
How to monitor and handle the status of running applications and what are the
reactions to the unexpected situation?
Does any mechanism to update process id if a process was killed by user or by
some exceptions?
3) Page 5, line 18~21
What are the expected actions if find applications (which is running)
updated/uninstalled?
4) Page 5, 5.5 Unit Test
Do you think of using some unit test framework, like "check", to wrapper all
test cases and run them automatically?
Thanks,
Lei Y
-----Original Message-----
From: Li, Horace
Sent: 2008年9月1日 23:48
To: [email protected]
Subject: Application life-cycle manager design doc draft is attached.
Hi, All,
I completed a design document draft of application life-cycle manager, codename
Genesis. Application life-cycle manager is part of application framework in
Moblin 2.0 software stack, and you could find more detailed description in the
document.
Please help to review the document and see if the information included in the
document is adequate and clear. Any comments are welcome.
Application life-cycle manager project is currently available at
http://test.moblin.org/projects/genesis-application-lifecycle-manager.
Thanks,
Horace
_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
https://www.moblin.org/mailman/listinfo/dev
