From kde-kiosk Wed Jan 04 19:37:24 2006 From: James Stout Date: Wed, 04 Jan 2006 19:37:24 +0000 To: kde-kiosk Subject: Re: [Kde-kiosk] Multimedia Kiosk - Marketing Display Message-Id: X-MARC-Message: https://marc.info/?l=kde-kiosk&m=113640362115552 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1277962706==" --===============1277962706== Content-Type: multipart/alternative; boundary="----=_Part_34122_8652909.1136403444356" ------=_Part_34122_8652909.1136403444356 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline ---------- Forwarded message ---------- From: James Stout Date: Jan 4, 2006 1:55 PM Subject: Re: [Kde-kiosk] Multimedia Kiosk - Marketing Display To: Martijn Klingens I apologize for my lack of sufficient description. I am subscribed to this mailing list. As with you, the rest is inline: On 1/4/06, Martijn Klingens < klingens@kde.org> wrote: > > Hi James, > > A couple of questions before I (or someone else) can give your mail a > stab... > > First of all: are you subscribed to this list or do we need to keep you o= n > CC? > > I added the rest inline below: > > On Wednesday 04 January 2006 17:07, James Stout wrote: > > Each display shows content independent of the other, i.e. one is not an > > extension of the other nor are they clones. The content also is in a > loop. > > Have you got that working without applying any kiosk restrictions? In > general > it's best to first get all bits and pieces working as if it's a "normal" > desktop and only then apply the lockdown options of KDE's Kiosk framework > to > it. > > Of course you should probably keep the eventual use case (kiosk) in mind > for a > couple of design decisions, but initially it isn't too much different fro= m > a > normal setup yet. I've not yet gotten this part working. As this is a fairly new concept for me, I had no real idea where to begin, which you've now provided. Getting it running on multiple displays as a 'normal' desktop does seem like the obvious idea, but I wanted to consult the experts, as it were, before getting very deep. Especially since I have no real initial idea of how large a project this will be. > We are currently able to schedule the content (i.e. start playing on X > date > > / stop playing on Y date). > > Are you able to do this on the existing Windows systems or do you also > have > this working on Linux already? And if you don't, do you have any idea > where > to look for information, since this isn't really the scope of the Kiosk > framework and/or this mailing list. This is currently working on the windows setup. As I stated above, I've no= t really gone far past the 'planning' stages. As far as this functionality goes, I'm not overly concerned. If the system were able to basically creat= e a play queue using all files in particular directory, then this same contro= l can be exercised manually by adding/removing files to that directory. I understand that some of these features will be beyond what I can get from this list, I only meant to describe how our system currently operates as a basis for what we would like, not an expectation for exact duplication of each function. > We are able to schedule what hours per day the kiosk is in operation. i.= e. > > > it displays content from 6 am to 11:59 pm. > > Same here, does "we are able" refer to Windows or Linux? This, again refers to our current Windows installation. -- > Martijn > Thanks, James -- To understand recursion, we must first understand recursion. -- To understand recursion, we must first understand recursion. ------=_Part_34122_8652909.1136403444356 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

---------- Forwarded message ----------
From: James Stout <james.stout@gmail.com>
Date: Jan 4, 200= 6 1:55 PM
Subject: Re: [Kde-kiosk] Multimedia Kiosk - Marketing Display
To: Ma= rtijn Klingens <klingens@kde.org= >

I apologize for m= y lack of sufficient description.

I am subscribed to this mailing list= .  As with you, the rest is inline:

On 1/4/06, Mar= tijn Klingens < klingens@kde.org> wrote:
Hi James,

A couple of questions before I (or so= meone else) can give your mail a stab...

First of all: are you subscribed to this list or do we need to keep= you on CC?

I added the rest inline below:

On Wednesday 04 Ja= nuary 2006 17:07, James Stout wrote:
> Each display shows content ind= ependent of the other,=20 i.e. one is not an
> extension of the other nor are they clones. = ; The content also is in a loop.

Have you got that working with= out applying any kiosk restrictions? In general
it's best to first get a= ll bits and pieces working as if it's a "normal"
desktop and only then apply the lockdown options of KDE's Kiosk framewo= rk to
it.

Of course you should probably keep the eventual use cas= e (kiosk) in mind for a
couple of design decisions, but initially it isn= 't too much different from a
normal setup yet.

I've not yet gotten this part working.  As this is a fairly new concept for me, I had no real idea where to begin, which you've now provided.  Getting it running on multiple displays as a 'normal' desktop does seem like the obvious idea, but I wanted to consult the experts, as it were, before getting very deep.  Especially since I have no real initial idea of how large a project this will be.
 

> We are currently able to schedule the content (i.e.= start playing on X date
> / stop playing on Y date).

Are you able to do this on the e= xisting Windows systems or do you also have
this working on Linux alread= y? And if you don't, do you have any idea where
to look for information,= since this isn't really the scope of the Kiosk
framework and/or this mailing list.

This is currently working on the windows setup.  As I stated above, I've not really gone far past the 'planning' stages.  As far as this functionality goes, I'm not overly concerned.  If the system were able to basically create a play queue using all files in particular directory, then this same control can be exercised manually by adding/removing files to that directory.  I understand that some of these features will be beyond what I can get from this list, I only meant to describe how our system currently operates as a basis for what we would like, not an expectation for exact duplication of each function.
 

> We are able to schedule what hours per day the kios= k is in operation.   i.e.
> it displays content from 6 am to 11:59 pm.

Same here, does = "we are able" refer to Windows or Linux?
=
This, again refers to our current Wi= ndows installation.

--
M= artijn



Thanks,

James

-- To understand recursion, we must first understand recursion.


--
To understand recursion, we must = first understand recursion. ------=_Part_34122_8652909.1136403444356-- --===============1277962706== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-kiosk mailing list kde-kiosk@kde.org https://mail.kde.org/mailman/listinfo/kde-kiosk --===============1277962706==--