Kreport has dropped kross for qjsengine, as part of being wrong, so it
would be preferable to convert python to js
On Sat, 2 Jul 2016, 19:37 Dag, <dand...@get2net.dk> wrote:
> Preliminary input for Plan. Note that I have not even open all views
> much less tried much functionality, so there may be (a lot) more...
> Also, I'm on vacation 2 last weeks of july and 3. week of august, so
> expecting to be release ready in 1 month would be a bit optimistic ;)
> That said, this is what I know of now:
> Locale/datetime: This could be a difficult problem. A possible solution
> could be to use time_t internally/for calculations etc and convert to
> QDateTime for ui.
> Locale/currency: Should not be a problem, just needs a way to set the
> currency to use for a project so it does not follow the users locale.
> Kross/python: Scripting is used for some functionallity so python
> Scripting is used for getting data from Project and ScheduleManager.
> Alternative to fix KReport is to implement a different way to get this
> info in Plan.
> Report items Chart and Web has not afaics been ported yet.
> Expects to know more on monday,
> Camilla Boemann skrev den 2016-07-02 08:17:
> > Hi
> > I think it's time we get a release out. We are stuck with not much work
> > going
> > on so inspired by Dag's return let's do a push to get ready.
> > I think we should cut down on the number of applications so we have
> > something
> > manageble left. It's tough but the alternative is that Calligra dies
> > completely. And nothing prevents us from bringing apps back later.
> > So my question is: What is missing for us to have a release. I am not
> > talking
> > about all the nice to have features and bug fixes. I am asking what
> > would
> > create huge problems for our users if we release.
> > Let's get things listed. I'll start:
> > Words: Nothing blocking
> > Stage: Nothing I'm aware of
> > Sheets: ???
> > Plan: the locale thing? how much would a quick fix take or should we
> > just
> > exclude Plan from first release?
> > Karbon: let's exclude from first release
> > Flow: let's exclude from first release
> > Kexi: are they even a part of the release schedule anymore
> > Braindump: let's drop it completely
> > Common stuff: ???
> > please fill in
> > and let's get ready for a release in a month or so ? We need to set a
> > short
> > deadline to keep motivation high
> > best regards
> > Camilla
> > _______________________________________________
> > calligra-devel mailing list
> > email@example.com
> > https://mail.kde.org/mailman/listinfo/calligra-devel
> calligra-devel mailing list