Cool stuff, this is essentially what koreport does for kexi and plan
reports. Access to the report internals and on* events.
--
Sent from my Nokia N9
On 15/11/2011 10:44 Sebastian Sauer wrote:
**
On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
On 11/14/2011 09:54 PM, Adam Pigg wrote:
On a simil
On 15 November 2011 11:45, Sebastian Sauer wrote:
> On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
>
> On 11/14/2011 09:54 PM, Adam Pigg wrote:
>
> On a similar note, imagine the possibility of embedding JS in a document,
> and defining a function such as
> function calligra_version() { return "2
On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
On 11/14/2011 09:54 PM, Adam Pigg wrote:
On a similar note, imagine the possibility of embedding JS in a
document, and defining a function such as
function calligra_version() { return "2.6"; }
then, having some kind of user field that contained
On 11/14/2011 09:54 PM, Adam Pigg wrote:
On a similar note, imagine the possibility of embedding JS in a
document, and defining a function such as
function calligra_version() { return "2.6"; }
then, having some kind of user field that contained
'=calligra_version()' that would display the app
On 11/14/2011 10:13 PM, Jaroslaw Staniek wrote:
On 14 November 2011 21:30, Sebastian Sauer wrote:
On 11/14/2011 01:51 PM, Pierre Stirnweiss wrote:
Background: I indeed think that is a rather important feature
cause it's the only way to get content into a document that
can be in a centralized w
On Monday 14 November 2011 23:44:27 Jaroslaw Staniek wrote:
> On 14 November 2011 23:02, Markus Slopianka wrote:
> > On Sonntag 13 November 2011 12:39:02 C. Boemann wrote:
> >> RoadMap
> >>
> >> The goal is to be ready for 2.6 for regular usage without having all the
> >> more special
On 14 November 2011 23:02, Markus Slopianka wrote:
> On Sonntag 13 November 2011 12:39:02 C. Boemann wrote:
>
>> RoadMap
>>
>> The goal is to be ready for 2.6 for regular usage without having all the
>> more special features that are just nice-to-have.
>>
>> Qt 5 patches (boemann, pie
On Sonntag 13 November 2011 12:39:02 C. Boemann wrote:
> RoadMap
>
> The goal is to be ready for 2.6 for regular usage without having all the
> more special features that are just nice-to-have.
>
> Qt 5 patches (boemann, pierreSt)
With Calligra also being an engine provider for othe
On 14 November 2011 21:30, Sebastian Sauer wrote:
> On 11/14/2011 01:51 PM, Pierre Stirnweiss wrote:
>
> Background: I indeed think that is a rather important feature
> cause it's the only way to get content into a document that
> can be in a centralized way edited/updated. Means you for
> example
On 14 November 2011 21:54, Adam Pigg wrote:
> On a similar note, imagine the possibility of embedding JS in a document,
> and defining a function such as
> function calligra_version() { return "2.6"; }
> then, having some kind of user field that contained '=calligra_version()'
> that would displa
On a similar note, imagine the possibility of embedding JS in a document,
and defining a function such as
function calligra_version() { return "2.6"; }
then, having some kind of user field that contained '=calligra_version()'
that would display the appropriate content/
On Mon, Nov 14, 2011 at 8
On 11/14/2011 01:51 PM, Pierre Stirnweiss wrote:
Background: I indeed think that is a rather important feature
cause it's the only way to get content into a document that
can be in a centralized way edited/updated. Means you for
example a document describing the features of Call
>
> Background: I indeed think that is a rather important feature
> cause it's the only way to get content into a document that
> can be in a centralized way edited/updated. Means you for
> example a document describing the features of Calligra as
> released and then add a user-variable field for t
On 11/13/2011 12:39 PM, C. Boemann wrote:
During todays meeting it became apparent that we all more or less agree on the
mission statement and roadmap, so I was tasked to write something down on
paper.
Mission statement
Calligra Words is for creating word processing docu
14 matches
Mail list logo