[Kde-silk] Introducing Project Silk

Peter Schiffer schiffer at zoznam.sk
Fri Oct 16 00:02:49 CEST 2009


On 10/15/2009 11:09 PM, Richard Moore wrote:
> On Wed, Oct 14, 2009 at 10:21 AM, Sebastian Kügler<sebas at kde.org>  wrote:
>    
>> Hey,
>>
>> How about we meet on IRC to discuss details a bit and come to a plan we can then
>> follow? I'm on a business trip right now, but will be back on Friday. Friday
>> afternoon would suit me well, otherwise, next week I'll be very flexible in terms of
>> time.
>>      
> I can't do Friday (I'm working monday to friday) but i can do
> weekends. Would that work for you guys?
>
> Cheers
>
> Rich.
>
>    
This weekend I'll be home, so some evening could work for me.

Peter

>> On Monday 12 October 2009 23:56:37 Peter Schiffer wrote:
>>      
>>> On 10/11/2009 02:16 PM, Sebastian Kügler wrote:
>>>        
>>      
>>>> Have you had a look over the techbase Silk page? There's a large number
>>>> of ideas there, some easier to do, some harder and more involved. Can you
>>>> pick maybe three ideas that match your motivation and skillset? Then we
>>>> can discuss what it takes to implement them, and how you can exploit this
>>>> to write a sound thesis report. It's best if you decide what to work on,
>>>> since you'll be the one working on it (and it'll better be something
>>>> interesting to you).
>>>>          
>>      
>>> Actually I have and I saw many interesting things there. But to choose 3
>>> I would say:
>>> That picture side of Alessandros part of the project could be..
>>> Or some parts of libweb, e.g: webpage metadata class with preview;
>>> Monitor webpages + change notifications; SOAP API (useful for corporate
>>> web apis) and maybe this - public transport API (standardized way of
>>> getting at this information, different backends to get at the data)
>>> And from the Silk integration components could it be web identity
>>> configuration?
>>>        
>> The web identify is I think more a "write code thing", and I think less interesting
>> from a research point of view. Abstracting existing webservices to a common API seems
>> like good thing to tackle, the public transport API is a really good candidate and
>> probably very easy to explain to others. Should we focus on that one?
>> --
>> sebas
>>
>> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
>>
>> _______________________________________________
>> Kde-silk mailing list
>> Kde-silk at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-silk
>>
>>
>>      
>    



More information about the Kde-silk mailing list