[scribus-dev] Inline objects as framework for dynamic text?

[Craig Bradney]

On 4/29/11 4:51 PM, Andreas Vox wrote:
>
>> -----Ursprüngliche Nachricht-----
>> Von: Craig Bradney [mailto:cbradney at scribus.info]
>> Gesendet: Freitag, 29. April 2011 16:26
>> An: Scribus Development Mailing List
>> Cc: Scribus Development Mailing List
>> Betreff: Re: [scribus-dev] Inline objects as framework for dynamic
>> text?
>>
>>
>>
>>
>>
>> On 29/04/2011, at 15:59, "Andreas Vox" <andreas.vox at googlemail.com>
>> wrote:
>>
>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Cezary Grabski [mailto:czarek at oferuje.pl]
>>>> Gesendet: Freitag, 29. April 2011 12:39
>>>> An: Scribus Development Mailing List
>>>> Betreff: Re: [scribus-dev] Inline objects as framework for dynamic
>>>> text?
>>> ...
>>>
>>>
>>>> From dev side as I wrote before - I thought about use and extend
>> inline
>>>> objects class (by add to it kind of insertion and new rendering
>> ways),
>>>> but
>>>> also new class for that puprposes can be created.
>>>> But I am not thinking about inserting text dynamically created by
>>>> markers and
>>>> references into inline frames! It should be like normal text with
>>>> respect for
>>>> styles, but not editable by typing (even cursor should jump over
>> such
>>>> dynamic
>>>> text like it was in a frame).
>>> Current text code only supports simple markers like "pagenr".
>>> SpecialChars::OBJECT is tightly linked to Inline frames, so Scribus
>> expects
>>> an InlineFrame at those positions which reports a given width and
>> height
>>> *before* Scribus starts layouting the text. You will not be able to
>> use
>>> Scribus' layout code from within the InlineFrame.
>>>
>>> You could introduce a new SpecialChar and expand it in the
>> "expandTokens"
>>> subroutine. Then you need to find a place where to store the attached
>> text;
>>> with 1.4 code the best place would probably a QString field in ScText
>> (or
>>> some other pointer-type –- don't use anything big there).
>>>
>>> Please note that the text structure is going to radically change in
>> 1.5. It
>>> will support many XML-like features which would make implementation
>> of
>>> dynamic text features much easier.
>>>
>> When? :)
> Duh! When it's ready, of course ;-)
>
> /Andreas
>
Then its not for 1.5.0.. action action action...

Craig