From koffice-devel Fri Sep 15 07:43:36 2006 From: Thomas Zander Date: Fri, 15 Sep 2006 07:43:36 +0000 To: koffice-devel Subject: Re: RFD: loading/pasting/DnD in Flake? Message-Id: <200609150943.46492.zander () kde ! org> X-MARC-Message: https://marc.info/?l=koffice-devel&m=115830630703600 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1579047143==" --===============1579047143== Content-Type: multipart/signed; boundary="nextPart2353827.8RfWx9JWzH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2353827.8RfWx9JWzH Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sorry for slow reply, I was reinstalling my laptop :) On Wednesday 13 September 2006 17:12, Benjamin K. Stuhl wrote: > > So, the KoDropTool should allow sending different formats to the > > tool, but only in a very limited capacity. I surely want to avoid to > > have 'mimetypes' or other things to accommodate multiple-formats in > > the KoTool. Just in the KoTextTool. > > Hmmm... what about image/{lots of things} for the Krita shape? Or an > embedded Phonon (A/V) shape (audio/*, plus application/{whatever the > video formats are})? It seems to me that we should support people > dropping all sorts of things in their documents, but I don't really > think we should have separate shapes per _format_: shapes should > logically be per document _type_. Agreed. People dropping an image or a video technically will translate into a URL=20 being pasted. So again just one mime type. I forsee the dropTool to handle the URL mimetype by fetching the file and t= hen=20 inserting it if there is a filter (which converts it to ODF) or creating a= =20 dedicated shape for the filetype if there is no filter. In practice this means that if a user drags a jpeg to my kword canvas the=20 droptool will get a URL which it can get the real mimetype of, run it throu= gh=20 the filter-framework and end up with a krita document (which indeed is not= =20 yet ODF, but thats beside the point ;). This allows the dragTool to instantiate a new krita-flake and load it using= =20 the result of the filter-framework and 'paste' that shape into the document. Quite a similar effect will happen when the user drops a movie, except that= we=20 need to still design/create a movie-shape. As well as the fact that we can'= t=20 convert from avi to ogg on loading ;). So this means the shape will most=20 likely take a ODF doc which does nothing but reference an external URL. =2D-=20 Thomas Zander --nextPart2353827.8RfWx9JWzH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBFClmyCojCW6H2z/QRAkT7AJ4yIpoTSJHcaL8yl05FVLN2s45U9wCglPIC zFKSTdFIzl/l4F2hUfa/eEk= =urrz -----END PGP SIGNATURE----- --nextPart2353827.8RfWx9JWzH-- --===============1579047143== 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 --===============1579047143==--