From koffice-devel  Thu Sep 17 10:44:23 2009
From: Thomas Zander <zander () kde ! org>
Date: Thu, 17 Sep 2009 10:44:23 +0000
To: koffice-devel
Subject: Re: Page variable support for kopageapp
Message-Id: <200909171244.24236.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=125318429206938
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2015596150=="

--===============2015596150==
Content-Type: multipart/signed;
  boundary="nextPart1491027.RNmje8RkHp";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1491027.RNmje8RkHp
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 17. September 2009 12.15.00 C. Boemann wrote:
> > thing you will have to prove is that its not expensive to do what you
> > want. You say "no extra code at all". Which is not true. Its only no
> > extra code for KPresenter. But instead you add extra code for each and
> > every shape that you want to have showing different. And the amount of
> > plugins is infinite.
>
> Well the patch doesn't break that principle as i see it anymore than
> looping as you suggest. If you view the contents as having a variable
> rather than absolute text, then nothing is changed That is kind of what a
> variable means.

The 'looping' is indeed very similar, the application passes a page object=
=20
to the shape so it knows where its being displayed.

The point really is that Thorsten says having one shape instance showing at=
=20
the same time on two slides (two views, for example) should allow them to=20
look different.

Thats like saying you want the same QString x =3D QString("%1").arg(myInt) =
to=20
give a different 'x' while being used at the same time.
Naturally this implies that you do the string replacement each and every=20
time the 'x' is used either on screen or anywhere else.
Imagine having a QLabel and overriding the paint method to replace the=20
actual text with the above "%1" string instead of just setting the resultin=
g=20
text for this label.

I'm arguing that insisting on changing the text on paint instead of making =
a=20
copy is the reason KPresenter needs a new public API. Since the 'copy'=20
concept (called proxy shape) already is in use and works just fine and will=
=20
work just fine for KPresenter.
=2D-=20
Thomas Zander

--nextPart1491027.RNmje8RkHp
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkqyEwgACgkQCojCW6H2z/STmgCfa8RWPNeBjccoOMCWME1jViHa
uU8An0/hQBXd5tD1ET9b9/5fzIMh+jsv
=HS9G
-----END PGP SIGNATURE-----

--nextPart1491027.RNmje8RkHp--

--===============2015596150==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============2015596150==--