[scribus-dev] Plans for 1.3.6

Craig Bradney cbradney at scribus.info
Sat Sep 27 23:41:06 CEST 2008


On Saturday 27 September 2008 23:05:10 Andreas Vox wrote:
> Am 27.09.2008 um 22:09 schrieb Craig Bradney:
> > On Saturday 27 September 2008 16:04:59 Andreas Vox wrote:
> >> Am 27.09.2008 um 15:23 schrieb Christoph Schäfer:
> >>> Hi all,
> >>>
> >>> I'm currently writing an article about Scribus 1.3.5 and beyond.
> >>> For that purpose I'm very interested about individual developers'
> >>> goals for 1.3.6. I know some Craig's and Jean's plans, but no
> >>> details.
> >>>
> >>> If anyone has a specific set of goals that's going to be achieved
> >>> during the 1.3.6 development cycle, it would be great if I received
> >>> a list in a personal email.
> >>
> >> Textframes:
> >> - work with Pierre to integrate Harfbuzz
> >> - integrate a complex script shaper, probably in cooperation with
> >> Rajeev Sebastian
> >> - prepare textframes for external XML
> >> - provide scripter bindings for more textframe features
> >>
> >> Styles:
> >> - extend style system to other types of styles (object styles, line
> >> styles)
> >> - clean up style manager / properties palette (I guess that's where
> >> everyone should help out)
> >>
> >> Fonts:
> >> - maybe include customizable and virtual fonts
> >>
> >> Canvas:
> >> - clean up canvas code
> >>
> >> At the end of 1.3.6, the work I started with 1.3.4 should be stable
> >> and presented by a finished GUI.
> >> I guess Pierre will state his goals resp. OpenType font features.
> >
> > This looks like more than 3 months work.. you ONLY have 3 months.
> > If at 3
> > months there are things not done, they will not be waited for but
> > pushed to
> > 1.3.7. You need to define these goals more before they can be
> > included. Items
> > that will take 6 months need to have plans for splitting across two
> > releases.
>
> Well, the central goal is to rewrite textframes to allow for Harbuzz
> and shaper
> integration. No idea how that can be split into two.

Once 1.3.5 is done it'll be time to start deciding, you will have about 2 
months to implement, 1 month to test per release. If that means in 1.3.6 you 
have unused code in the user visible GUI (ie it is only used for testing on 
your side), that should also be fine.

Craig



More information about the scribus-dev mailing list