<br><br>
<div class="gmail_quote">2008/3/5 Aaron J. Seigo <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>>:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">hi..<br><br>so we already have one SoC student looking to propose a mobile device project<br>for plasma, and today i've received two possible offers for relevant hardware<br>
from manufacturers.</blockquote>
<div> </div>
<div>Which devices? While I'm not a SoC candidate my progress in this area has been hindered by my access to only one device (N770) which has limited resources.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span id=""></span><br><br>Plasma is at the point now where it's probably time to really start exploring<br>
it's possibilities on these devices. they pack a good amount of horsepower,<br>so the initial work will be build env and UI related (such as Nathan<br>Eckenrode's SoC project proposal).<br><br>now, i don't want to collect various bits o hardware here at the house. not<br>
only will i not have the time to use more than one or two devices, i think it<br>would make a lot more sense to get as many interested hands as possible on<br>these things.<br><br>so i'm looking for people who have some experience with plasma (you don't have<br>
to be a ninja, just have poked at some of the code, such as written widget or<br>dataengine plugins, for example) who would realistically have interest, time<br>and energy to explore plasma on these devices.</blockquote>
<div> </div>
<div>Sign me up. That's the main reason that I've been writing these dataengines to interface with Solid. It will give us a way to write control applets that will easily scale down to embedded devices.</div>
<div>I see the following as necessary:</div>
<div>- Device Engine: feature complete and reworked to make it more memory efficient.</div>
<div>- NetworkManager Engine - ironing out the bugs to make it feature complete.</div>
<div>- BluetoothManager Engine - not started.</div>
<div>- Decibel Engines: - Has been started and introduced into playground.</div>
<div> </div>
<div>The applets that interface with these engine will thus be able to work not matter the device (PC, phone, laptop, etc.)</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span id=""></span><br><br>if that's you, please let me know what you'd want to do with the device (it's<br>
easier to convince people to mail hardware off if there's a concrete<br>project/goal to go along with that) and i'll try to start hooking people up<br>with the opportunity to play with some (free! =) hardware.<br>
</blockquote>
<div>I have a lot of ideas that I think are achievable and will make KDEmbedded a viable UI platform.</div>
<div>Some of these include:</div>
<div>- Media Player - to be implemented as a containment and integrate phonon that will enable you to play all media files.</div>
<div>- Decibel Integration - will be made possible via the decibel engines and eventually enable it to work with all IM services and VOIP</div>
<div>- Marble Integration - this will require tiling and will be made better by open maps.</div>
<div> </div>
<div>I believe all of these, while not trivial, are attainable goals that will outstrip other existing UI offerings and will be built on already existing KDE technologies.</div>
<div>Chris</div></div>