[Kst] Fwd: Google Code-In ?

Thu Nov 3 22:51:32 UTC 2011

Kst,

Scripting should in general work on Windows.

Transferring vectors and matrices  between python and kst requires c++/qt
code on the python end which currently uses Weave and is compiled on first
run. This will not run without a Qt development setup, effectively meaning
it doesn't work on Windows. It is apparently possible to use shared
libraries instead of having it compiled on first run, but I haven't had a
chance to look into this.

Joshua
On Nov 3, 2011 5:15 PM, <nicolas.brisset at free.fr> wrote:

> Well, unfortunately now it looks like we've missed the deadline :-(
> I'll keep this list in mind for the next opportunity...
>
> For my information, why would you "hesitate" on data sinks and scripting
> under Windows? And what is the status of scripting under Windows, does it
> work? And do we know how we're going to distribute the next version if we
> activate scripting?
>
> Nicolas
>
> ----- Mail original -----
> De: "Barth Netterfield" <netterfield at astro.utoronto.ca>
> À: kst at kde.org
> Envoyé: Lundi 31 Octobre 2011 15:32:46
> Objet: Re: [Kst] Fwd: Google Code-In ?
>
> sorry for the slow reply.
>
> I think this is a good idea.
>
> I would hesitate on
> > f. Infrastructure for data sinks (modeled after the netCDF API?)
> > g. Scripting also under Windows (?)
>
> Otherwise, sounds great.
>
> Thanks!
>
> On Sun, Oct 23, 2011 at 3:52 PM,  <nicolas.brisset at free.fr> wrote:
> > Hi,
> >
> > I think I haven't seen any answer to this message, whih I find
> important. Anybody mind if I go the next step (i.e. contacting Lydia)?
> >
> > Nicolas
> >
> > ----- Mail transféré -----
> > De: "Nicolas Brisset" <Nicolas.Brisset at eurocopter.com>
> > À: kst at kde.org
> > Envoyé: Mardi 18 Octobre 2011 09:27:47
> > Objet: [Kst] Google Code-In ?
> >
> > Hi,
> >
> > I think this initiative could be very interesting for both us and the
> students:
> http://blog.lydiapintscher.de/2011/10/17/i-need-your-ideas-for-google-code-in/
> >
> > We have a lot of things which we could propose, “junior jobs” which can
> be done without too much effort or prior knowledge. Here is a first list
> sorted according to the categories in the blog post, feel free to complete:
> >
> > 1. Code:
> > a. Support for Matlab .mat files
> > b. Generic support for XML data sources
> > c. Generic support for SQL data sources
> > d. Support for binary formats with a format description (like okteta’s
> structures tool)
> > e. ASCII data source: support for date/time (config UI + code)
> > f. Infrastructure for data sinks (modeled after the netCDF API?)
> > g. Scripting also under Windows (?)
> >
> > 2. Documentation: that one is obvious, kst documentation needs to be
> refreshed. It would also be an opportunity to test all features and see
> what people understand and what not
> >
> > 3. Outreach:
> > a. Establish and structure a dedicated kst area on forum.kde.org
> > b. Try to contact high schools/universities where students have to work
> on IT projects, and see if they would contribute to kst to implement some
> of the ideas above (and more), as they’ve been doing in Toulouse for a few
> years now. Could be a real win-win situation: students can work on a real
> project and learn a lot of things in a gratifying environment, and kst gets
> more features and developers
> >
> > 4. Quality assurance:
> > a. Provide more tests (either unit-tests or high-level tests)
> > b. Various checks (from labels and tooltips to proper behavior of all
> tools/options or tab order)
> >
> > 5. Research: how to reintegrate KDE features when KDE is available. See
> recent post on the list and how marble is doing it – certainly something of
> general interest for KDE. See also
> http://bugs.kde.org/show_bug.cgi?id=248184
> >
> > 6. Training: could be combined with the documentation item. For
> instance, provide sample files and tutorials (including the video ones I
> want to do and don’t come to doing?). Though I’m not sure this is what
> code-in is about…
> >
> > 7. Translation: there were several requests around that recently,
> including a very constructive mail with recommendations on how to do it.
> So, do it!
> >
> > 8. User Interface:
> > a. Definition of what the new “table-like” vector view/edit dialog
> should be, so that we can offer a workflow a la labplot/Origin. Based on a
> comparison with qtiplot/scidavis, labplot, Origin, etc…
> > b. The salve vector discussion / alias topic which we can’t seem to
> finally solve
> > c. …
> >
> > It definitely sounds like an opportunity to me! I’d be ready to support
> with ideas and links to existing code we can reuse, and possibly even some
> code (or better code review), though for that others are probably better
> qualified.
> >
> > What do you think?
> >
> > Nicolas
> > _______________________________________________
> > Kst mailing list
> > Kst at kde.org
> > https://mail.kde.org/mailman/listinfo/kst
> > _______________________________________________
> > Kst mailing list
> > Kst at kde.org
> > https://mail.kde.org/mailman/listinfo/kst
> >
>
>
>
> --
> C. Barth Netterfield
> University of Toronto
> 416-845-0946
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kst/attachments/20111103/873f7dbd/attachment.html>