Hello, let me introduce myself.<div><br></div><div>I'm a Computer Science student from the Federal University of Bahia, 3rd year. I got interested by the idea of implementing support for OpenGL in KStars, because I was previously interested in learning that API and I want KStars to look more preety.</div>
<div><br></div><div>I know C++, already know some Qt and am studying OpenGL. I think I can learn it in enough time. I cannot say exactly how and what I'll do, but I already have some ideas:</div><div> - Make a 3D ambient for the projections with perspective.</div>
<div> - Make it possible to define a SkyObject a mesh, in the case of the orbs which we can see with more detail (Solar System's planets, the moon, etc....)</div><div> - Use particles to represent the Milky Way.</div>
<div><br></div><div>I already talked to Akarsh about it, and he said it is fine for me to apply.</div><div><br><div class="gmail_quote">2010/3/30 Victor Carbune <span dir="ltr"><<a href="mailto:victor.carbune@gmail.com">victor.carbune@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello !<br>
<br>
I am student, in my 2nd year at Politehnica University of Bucharest.<br>
I'm passionate amateur astronomer as well as a programmer experienced<br>
with C++ and some basic Qt skills (developed a simple GUI some couple<br>
of moths ago).<br>
<div class="im"><br>
> Brief explanation: This feature is expected to be of use to amateur<br>
> (hobby) astronomers. The idea is that there are aspects of amateur<br>
> astronomy which are collaborative. For instance, one might want to<br>
> view observations by other amateur astronomers around the world before<br>
> making an observation of an object. Again, one would like to share<br>
> their own observations with everyone else. There are more<br>
> possibilities, and the student is encouraged to come up with them.<br>
<br>
</div>I'm very enthusiast of the idea of doing everything written above in a<br>
real-time manner too, as much as possible.<br>
I have researched a bit more into the topic and I have found qwaveclient [1].<br>
<br>
Having this client extends the OAL implementation to a collaborative<br>
experience for users with several extra code lines (of course, and<br>
some GUI specific features that can really enhance the user experience<br>
- like adding special comment fields depending on the type of the<br>
object observed, etc.). This will then be done just by simply creating<br>
a wave for the object, and further working directly on OAL xml (as<br>
wave already works with xmls we will not need any further changes or<br>
effort on making it compatible).<br>
<br>
Astronomers using their laptops at astronomy observations could<br>
simultaneously see who else is observing what, exchange information or<br>
simply get enthusiast by seeing that so many other are out there<br>
observing and get out fast in the yard with the telescope.<br>
<br>
I think this would be a unique feature, the first of it's kind in an<br>
astronomy software, and since there already exists a wave<br>
implementation for Qt I believe it is a really feasible idea for the<br>
summer, attaching it to the full OAL support.<br>
<div class="im"><br>
> 1) KStars produces observation logs in an XML format that is expected<br>
> to adhere to the OAL 2.0 schema. The project will involve extending<br>
> the existing implementation of the OAL 2.x schema and ensuring that it<br>
> is fully compatible with the schema.<br>
<br>
</div>I have researched more about the OAL schema on their website and I am<br>
currently seeing where exactly in the KStars code is the save done and<br>
I'm trying to analyze where modifications have to be made (I'd<br>
appreciate some tips, if you get the time).<br>
<div class="im"><br>
> 2) A very user friendly GUI has to be implemented for viewing imported<br>
> logs [ And a good SQL backend for accessing the information from them<br>
> efficiently ]<br>
<br>
</div>I'm not sure yet how I could detail the GUI in this stage, probably<br>
the best thing I could do would be a drawing / sketch of it,<br>
containing information that can be retrieved from logs.<br>
<div class="im"><br>
> 3) Ability to handle objects in the logs which are not there in the<br>
> current KStars database.<br>
<br>
</div>I'm thinking on a mix implementation of the this and the import<br>
catalog feature for KStars in a single project. The catalog import<br>
feature seems like a great opportunity to get really familiar with the<br>
code and everything. Currently I am having in view the community<br>
bonding period too (actually I believe that's a great opportunity on<br>
getting started with the project and after all, it is a whole month of<br>
coding time).<br>
<div class="im"><br>
> 4) Retrieval of logs from the internet (and other sources) on a filter<br>
> based query. [ Filter could be anything like, Object name or location<br>
> or observer name ]<br>
<br>
</div>From my past experience, I've seen that Qt has some great classes that<br>
can be used to efficiently implement filter function in the GUI.<br>
<br>
If anyone has the time, I would highly appreciate some feedback<br>
regarding this sketch of ideas, as I'm currently trying to detail them<br>
and looking forward to submit them through the application page.<br>
<br>
Best regards,<br>
Victor Carbune<br>
<br>
[1] <a href="http://code.google.com/p/qwaveclient/" target="_blank">http://code.google.com/p/qwaveclient/</a><br>
<div><div></div><div class="h5">_______________________________________________<br>
Kstars-devel mailing list<br>
<a href="mailto:Kstars-devel@kde.org">Kstars-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kstars-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kstars-devel</a><br>
</div></div></blockquote></div><br><br clear="all">Best Regards<br>-- <br>Luiz Romário Santana Rios<br>
</div>