Mer/Packages/powerlaunch - Revision history

imported_>amigadave: {{Mer}}

2010-09-22T11:12:54Z

← Older revision		Revision as of 11:12, 22 September 2010
Line 1:		Line 1:
			{{Mer}}

	Powerlaunch Re-implementation		Powerlaunch Re-implementation

Line 27:		Line 29:

	Initial implementation of the outline design using a python launcher and even plugins then review the use cases and see how it impacts memory usage. If we find we can keep it simple then we port it to vala.		Initial implementation of the outline design using a python launcher and even plugins then review the use cases and see how it impacts memory usage. If we find we can keep it simple then we port it to vala.

	~~[[Category:Mer]]~~

imported_>amigadave: Category:Mer

2010-02-11T15:21:11Z

Category:Mer

← Older revision		Revision as of 15:21, 11 February 2010
Line 27:		Line 27:

	Initial implementation of the outline design using a python launcher and even plugins then review the use cases and see how it impacts memory usage. If we find we can keep it simple then we port it to vala.		Initial implementation of the outline design using a python launcher and even plugins then review the use cases and see how it impacts memory usage. If we find we can keep it simple then we port it to vala.

			[[Category:Mer]]

imported_>lbt: Added implementation proposal

2009-06-27T13:19:44Z

Added implementation proposal

← Older revision		Revision as of 13:19, 27 June 2009
Line 23:		Line 23:

	The daemon doesn't have all the complex config parsing stuff resident all the time; also need to avoid inventing a scripting language on top that wires together the stuff.		The daemon doesn't have all the complex config parsing stuff resident all the time; also need to avoid inventing a scripting language on top that wires together the stuff.

			==Implementation Proposal==

			Initial implementation of the outline design using a python launcher and even plugins then review the use cases and see how it impacts memory usage. If we find we can keep it simple then we port it to vala.

imported_>lbt: draft

2009-06-27T12:58:28Z

draft

New page

Powerlaunch Re-implementation

suggestion: very simple vala daemon which is essentially a object/plugin loader, providing some degree of conflict-prevention, run a glib main loop and let the behaviour implement themselves as they want

== Use Cases ==
Needed

Eg
Dim screen on Idle
when the device is 'locked' the key handling connections aren't made *apart* from long press on the power

conditional and grouped instructions

==Proposed Design==

Vala based daemon which is driven by a validated machine parseable config
(cf http://live.gnome.org/Vala/DBusClientSamples)

Glib plugins to this daemon present UI-facing methods.

Python config parser to generate validated machine parseable config from a human readable (or gui managed) description. Essentially joining signals and slots from the plugins; possibly with conditionals.

The daemon doesn't have all the complex config parsing stuff resident all the time; also need to avoid inventing a scripting language on top that wires together the stuff.