On 10/10/06, <b class="gmail_sendername">Anne-Marie Mahfouf</b> <<a href="mailto:annemarie.mahfouf@free.fr">annemarie.mahfouf@free.fr</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 10 October 2006 12:21, RalfGesellensetter wrote:<br>> <a href="http://qt4lab.org">qt4lab.org</a><br><br>Hi,<br><br>I cleaned physiKs in kde3 svn and ported physiKs to kde4 in<br>branches/work/kde4/playground/edu/physiks
<br>in KDE svn.</blockquote><div><br>Thank you. There was indeed much cleaning to do.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At the moment<br>- the Physicsdrawer does not compile in kde3, it is coded against qt4 while<br>the other code was against qt3 - it's a qt only code. It also does not<br>compile in kde4, should be easy to fix though.</blockquote>
<div><br>I've been testing the entire code on KDE 3.5.2 with the Qt 4.1.1 libraries installed as well. I was trying to move everything over to Qt4 towards the end of my Summer of Code time, but I've apparently missed quite a bit.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">- the swig and ruby scripts don't run</blockquote><div><br>The SWIG error has kept me busy for countless hours. Scripts in any language are dependent upon SWIG's generated wrapper code, so if we can get SWIG to parse the two problematic files successfully, it would be theoretically possible to create a variety of bindings by just changing one compilation argument.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">- there is no binary to run, the scripts should demonstrate a sample run.<br>In short: I am lost on what to do about it.
</blockquote><div><br>That was the plan with physikstest.cpp and PhysiksDrawer.(cpp | h). I'm not sure why neither of them compile - what are the error messages? <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So for me, there's nothing to test and nothing to show. I had hoped that<br>physiKs was a bit more avanced in order to start a KDE4 app from its code. I<br>am not sure we can do anything with it, to be frank.</blockquote>
<div><br>No, most probably not. It is still in a very messy state, as you have unfortunately experienced first-hand. Functionalilty is also severely lacking. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The <a href="http://qt4lab.org">qt4lab.org</a> provides widgets for physics apps so I think this should be<br>used. There is also a KDE app on <a href="http://kde-apps.org">kde-apps.org</a>, eduKator, which seems<br>unmaintained now but could be a good base for a physics app.
<br><a href="http://kde-apps.org/content/show.php?content=17602">http://kde-apps.org/content/show.php?content=17602</a></blockquote><div><br>Interesting. I had never heard of qt4lab until today. It seems very useful for this project.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am waiting for a wiki for KDE-Edu in order to open a debate on physiKs and<br>
to see if it answers people's needs.<br>Ralf, do you have requests for such an app?<br><br>Anne-Marie<br><br></blockquote></div><br>