[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: KSpread script
From: Dag Andersen <danders () get2net ! dk>
Date: 2008-11-12 7:16:32
Message-ID: 200811120816.32540.danders () get2net ! dk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tuesday 11 November 2008 21:31:24 Thomas Zander wrote:
> On Friday 7. November 2008 11:33:07 Dag wrote:
> > Hi,
> > I've had a script sitting on my harddisk for some time that can imoprt
> > data from kplato into kspread. It basically works similar to kexiimport.
> > The question is, it is ok to commit to kspread or should it go somewhere
> > else?
>
> I'm just catching up with mail and I'm not entirely sure what a 'script'
> is.
This is a python script similar to those found in
/plugins/scripting/scripts in all apps.
The special thing with this is that it is run from kspread but opens a kplato
file. If kplato isn't installed it will fail.
(The same with kexiimport.py, it needs kexi installed to run)
>
> Its important to make sure we have minimal dependencies between
> applications and previous strategies of moving stuff to /filters/ didn't
> help much since packagers didn't package a filter that depended on both
> kword and kspread separately and another filter that depended on both kexi
> and kspread all went into the same package. Having the lovely result that
> installing kword auto-installed kspread and kexi :(
Yeah, not so smart.
I see that the script manager (is meant to) offer possibilities for the user
to add scripts manually, from a local file or from the net. It's just not
implemented yet. Setting up a GHNS server could be a way to handle scripts
like these in the future. It's also a way to open for nasty stuff, of course.
Is there a 'policy' on this?
>
> Maybe you can post the script on this mailinglist for others to comment on?
> Or at minimum as a way to archive the work so if your harddrive dies we
> still have it :)
I'll just commit it to kplato svn for now.
>
> Might be an easy way to work around the feature freeze ;)
--
Mvh.
Dag Andersen
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" \
content="1" /><style type="text/css">p, li { white-space: pre-wrap; \
}</style></head><body style=" font-family:'Sans Serif'; font-size:10pt; \
font-weight:400; font-style:normal;">On Tuesday 11 November 2008 21:31:24 Thomas \
Zander wrote:<br> > On Friday 7. November 2008 11:33:07 Dag wrote:<br>
> > Hi,<br>
> > I've had a script sitting on my harddisk for some time that can imoprt<br>
> > data from kplato into kspread. It basically works similar to \
kexiimport.<br> > > The question is, it is ok to commit to kspread or should it \
go somewhere<br> > > else?<br>
><br>
> I'm just catching up with mail and I'm not entirely sure what a 'script'<br>
> is.<br>
This is a python script similar to those found in<br>
/plugins/scripting/scripts in all apps.<br>
The special thing with this is that it is run from kspread but opens a kplato file. \
If kplato isn't installed it will fail.<br> (The same with kexiimport.py, it needs \
kexi installed to run)<br> ><br>
> Its important to make sure we have minimal dependencies between<br>
> applications and previous strategies of moving stuff to /filters/ didn't<br>
> help much since packagers didn't package a filter that depended on both<br>
> kword and kspread separately and another filter that depended on both kexi<br>
> and kspread all went into the same package. Having the lovely result that<br>
> installing kword auto-installed kspread and kexi :(<br>
Yeah, not so smart.<br>
I see that the script manager (is meant to) offer possibilities for the user to add \
scripts manually, from a local file or from the net. It's just not implemented yet. \
Setting up a GHNS server could be a way to handle scripts like these in the future. \
It's also a way to open for nasty stuff, of course. Is there a 'policy' on this?<br> \
><br> > Maybe you can post the script on this mailinglist for others to comment \
on?<br> > Or at minimum as a way to archive the work so if your harddrive dies \
we<br> > still have it :)<br>
I'll just commit it to kplato svn for now.<br>
><br>
> Might be an easy way to work around the feature freeze ;)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>-- <br> Mvh.<br>
Dag Andersen</p></body></html>
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic