<br><br><div class="gmail_quote">2010/5/24 santosh kumar <span dir="ltr"><<a href="mailto:santosh.k66@gmail.com">santosh.k66@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hey Bryan<br>
<br>
I am a novice as a developer and man going by the nature of your<br>
suggestions ,you ought to be a geek. I spend a lot of time on your<br>
messages since they are so erudite.<br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I was not aware about this "real time " dilemma.<br>
Any suggestions as to methods to go around this prob?<br>
<br></blockquote><div>I definitely agree with you on this being a big issue... still need to look into getting around it... I guess my thoughts are we get the core functionality working, even if it may be using delayed quotes to start, but try to make it easy to add "download plugins" or whatever so that people from the community can add their own custom downloaders. Maybe they could be shared through get hot new stuff? Haha I can't say I know how to write code that has that ability so that's all dreams for now, but, I'm sure we'll get something worked out :)<br>
Brian<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Scope: the idea is the utility.Any real time data on stocks and<br>
derivatives reaching you as soon as it happens would be of immense<br>
value to investors,if it is on sms(internet independent on the<br>
fly)great and may be even broking istes may be willing to deploy it..<br>
<br>
Blaah blaah..<br>
<br>
the thing is we enable open source with a new capability and then see<br>
how it takes shapes.<br>
<font color="#888888">_santosh<br>
</font><div><div></div><div class="h5"><br>
On 5/21/10, Brian Cappello <<a href="mailto:briancappello@gmail.com">briancappello@gmail.com</a>> wrote:<br>
> On Fri, May 21, 2010 at 10:19 AM, santosh kumar<br>
> <<a href="mailto:santosh.k66@gmail.com">santosh.k66@gmail.com</a>>wrote:<br>
><br>
>> thanks Alavaro and Cristian<br>
>> mid august is a great time frame.<br>
>> suits me .<br>
>> one question though can I do it with one source and one notification<br>
>> initially.<br>
>> We can build on it later on .<br>
>> I found by blogs and all that yahoo cvs is the thing that comes<br>
>> closest to real time .<br>
>><br>
><br>
> I was able to do some research too on this, and it appears real-time is<br>
> dependent upon whatever exchange the asked-for symbol is on. For example,<br>
> you're lucky, it appears the National Stock Exchange of India always<br>
> provides real-time quotes (as long as you're signed into Yahoo). For more or<br>
> less the rest of the world quotes are delayed by anywhere from 10-30<br>
> minutes, or real-time must be paid for (and again the user must be logged<br>
> in). See here for details:<br>
> <a href="http://help.yahoo.com/l/us/yahoo/finance/quotes/fitadelay.html" target="_blank">http://help.yahoo.com/l/us/yahoo/finance/quotes/fitadelay.html</a><br>
><br>
><br>
>><br>
>> it's reliable .<br>
>><br>
>> free<br>
>><br>
>> and there are no srtrings attached.<br>
>><br>
>> since dbus application is so critical to the format of our work we may<br>
>> like dbus people to keep updating on it's evolution and their<br>
>> expectations.<br>
>> thanks bryan for your help with that yahoo script.<br>
>><br>
><br>
> No problem :) It seems you have *many* more years of programming experience<br>
> than I, so I shall be the one calling you SIR ;)<br>
><br>
>><br>
>><br>
>> On 5/21/10, Alvaro Soliverez <<a href="mailto:asoliverez@gmail.com">asoliverez@gmail.com</a>> wrote:<br>
>> > On Fri, May 21, 2010 at 10:44 AM, Cristian Onež <<a href="mailto:onet.cristian@gmail.com">onet.cristian@gmail.com</a><br>
>> ><br>
>> > wrote:<br>
>> >> On Fri, May 21, 2010 at 4:08 PM, Alvaro Soliverez <<a href="mailto:asoliverez@gmail.com">asoliverez@gmail.com</a><br>
>> ><br>
>> >> wrote:<br>
>> >>> Hello,<br>
>> >>> this is just so that we can organize ourselves. Here's my proposal for<br>
>> >>> the work on Alkimia that came up during this week.<br>
>> >>><br>
>> >>> Mukesh and Santosh are students of Season of KDE, so their scope of<br>
>> >>> work should be well defined. Brian, I'll check later with you if you<br>
>> >>> are interested in getting into SoK, which I think fits your case.<br>
>> >>><br>
>> >>> Mukesh will focus on getting a DBus service up and running that will<br>
>> >>> allow to input transactions and store them, and then retrieve them by<br>
>> >>> a number of parameters.<br>
>> >>> Mentors for Mukesh are Klaas and myself.<br>
>> >>><br>
>> >>> Santosh's work should be mainly focused on retrieving quotes from a<br>
>> >>> storage and then throwing notifications based on a global and<br>
>> >>> per-stock configuration. The storage could be a DBus service, a plasma<br>
>> >>> datasource, or a file. The notifications could be a systray<br>
>> >>> notification (KNotify?), an email or a sms message. The configuration<br>
>> >>> should allow to configure notifications when a stock is above/below a<br>
>> >>> certain value or percentage of in-day value change, etc. My main point<br>
>> >>> is that the storage should be flexible, eg. the application shouldn't<br>
>> >>> care much where it gets its data from, and notifications too, eg. we<br>
>> >>> don't know what options other people might come up with, so allowing<br>
>> >>> for at least 2 or 3 options will help iron out the design.<br>
>> >>> Cristian is Santosh's mentor.<br>
>> >>><br>
>> >>> Brian, if you are interested, you could work on a DBus service that<br>
>> >>> retrieves stock values via web or an import file and stores them for<br>
>> >>> later use (that same storage as Mukesh has to use). That DBus service<br>
>> >>> should allow for queries (so that Santosh can use it for his<br>
>> >>> application). Also, a GUI could be available to show the stored<br>
>> >>> stocks, with charts, sheets, et al.<br>
>> >>> Cristian, would you agree to co-mentor Brian with me? We have both<br>
>> >>> done some work on these areas, so we can help out.<br>
>> >><br>
>> >> Sure, if Brian is willing to participate.<br>
>> >><br>
>> >>> Questions, suggestions, and even nitpicking is welcome. :)<br>
>> >><br>
>> >> It seems to me that you have isolated each task pretty well so work<br>
>> >> can be done independently on each module this is a good plan. I've got<br>
>> >> a few questions though. Is the development going to take place in<br>
>> >> playground/office? Do the students have SVN access? What is the<br>
>> >> time-frame of 'Season of KDE'?<br>
>> >><br>
>> ><br>
>> > They will have SVN access. When there's code to commit, we'll ask for<br>
>> > that. Usually, it only takes a couple of days. And we can commit for<br>
>> > them if need be.<br>
>> > And yes, it will go into playground/office/alkimia.<br>
>> > The timeframe starts about now and ends mid-August.<br>
>> > _______________________________________________<br>
>> > Kde-finance-apps mailing list<br>
>> > <a href="mailto:Kde-finance-apps@kde.org">Kde-finance-apps@kde.org</a><br>
>> > <a href="https://mail.kde.org/mailman/listinfo/kde-finance-apps" target="_blank">https://mail.kde.org/mailman/listinfo/kde-finance-apps</a><br>
>> ><br>
>><br>
>><br>
>> --<br>
>> encore<br>
>> _______________________________________________<br>
>> Kde-finance-apps mailing list<br>
>> <a href="mailto:Kde-finance-apps@kde.org">Kde-finance-apps@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/kde-finance-apps" target="_blank">https://mail.kde.org/mailman/listinfo/kde-finance-apps</a><br>
>><br>
><br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5">encore<br>
_______________________________________________<br>
Kde-finance-apps mailing list<br>
<a href="mailto:Kde-finance-apps@kde.org">Kde-finance-apps@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-finance-apps" target="_blank">https://mail.kde.org/mailman/listinfo/kde-finance-apps</a><br>
</div></div></blockquote></div><br>