Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi Andrzej,

thanks a lot for looking into this!

On Tue, 2012-04-03 at 15:51 +0200, Andrzej J. R. Hunt wrote:
Hi,

I'm currently working on adding categories to the transitions viewable 
in the Impress GUI (https://bugs.freedesktop.org/show_bug.cgi?id=36946).

I'm not sure how best to assign categories to the transitions. The list 
of transitions is in xml/transitions.xml, which is loaded by 
source/core/TransitionPreset.cxx. Initially I used the transition-type 
(mnTransition) as the category, which does work, but results in too many 
categories, many of which should be joined into one. Therefore I'd like 
to create new UI categories, but don't know where I should do this.

Yup, having fewer categories makes sense. Powerpoint 2010 has only 3
categories too.

I could assign the categories directly in the transitions.xml file 
(which would require some changes to the code importing this file, 
including changes in xmloff), or I could write a new method in the 
TransitionPreset class that contains a list of which transition types 
map to which UI categories (much simpler to write, but less elegant in 
the case that someone adds more transitions to the file).

Which of these options should I choose, or is there a better way that I 
could do this?

I would prefer adding the information into transitions.xml. Otherwise it
would be less clear when adding new transitions.

Cheers
Radek



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.