Mailinglist Archive: yast-devel (101 mails)

< Previous Next >
Re: [yast-devel] better framework for module interaction?
  • From: Martin Vidner <mvidner@xxxxxxx>
  • Date: Wed, 16 Jan 2008 10:03:40 +0100
  • Message-id: <20080116090339.GB20509@xxxxxxxxxxxxxxxx>
On Tue, Jan 15, 2008 at 06:14:26PM +0100, Duncan Mac-Vicar Prett wrote:

feature #302961: Integrated Software Management Application, which means
basically integrate the repository editor with the package management
application makes me think we are missing something in the YaST framework
which I saw recently in the Android platform.

Android separates each view in an activity. Each Activy chains with others
generate a workflow) by generating Intents, and Activities can filter and
respond to Intents too. (

The idea is, if you wrte an application, and you need to edit a contact, or
select an geo-address. Your application don't care how you do it. It is not
hardcoded. The activity generates an intent of "edit contact", or "select
point in earth" and other activities will be launched, which of course
registered ther capabilities. This allow the workflows to perform the tasks
by selecting 1) the best 2) the user prefered, component to do the job.

So the key concepts seem to be choice and alternatives, right?

I think YaST is in the need of something similar, where modules could launch
sub activities without knowing much about them. At least this would solve
problems like integrating launching other modules from a module, and also
would allow modules to be easily replaced and avoid all the hardcoding. What
do you think?

Can you give more concrete examples?

Martin Vidner, YaST developer

Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >