<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN
class=921471818-20032009>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=921471818-20032009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=921471818-20032009>today I elaborated a
bit on my GSoC idea, so I thought it might be good to have it on the ML,
too.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=921471818-20032009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=921471818-20032009>/Andreas</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><pierremarc> a_vox: i’ve been unable to find
the mail where you exposed your ideas about editable text frames from MP, vipz
is interested<BR><a_vox> I just edited the wiki page<BR><pierremarc>
ok cool<BR><vipz> a-vox: hi<BR>* inkpot hat die Verbindung getrennt
("ChatZilla 0.9.84 [Firefox 3.0.7/2009021910]")<BR><a_vox> vipz, Scribus
documents consist of pageitems which are placed on the canvas. Pages are also
placed on the canvas, and pageitems which overlap with a page belong to that
page<BR><a_vox> (just giving a very general picture here)<BR><vipz>
ok<BR><a_vox> currently all pageitems on masterpages are just rendered as
an extra background layer on each page that is associated with that
masterpage.<BR><vipz> can tell me more about it<BR><a_vox> So my
plan was a) give master pageitems a flag "prototype"<BR><vipz>
ok<BR><a_vox> b) when associating a masterpage to a page (ie. "apply
masterpage"), make copies of all prototype master pageitems on that
page.<BR><a_vox> c) only render the masterpage items with "prototype ==
false" as background<BR><vipz> ok<BR><a_vox> once that is running,
we can figure out what should happen when re-applying another masterpage or what
happens if the masterpage is edited :-)<BR><vipz>
ok.<BR><vipz> i will study that and reply to you<BR><a_vox>
cool. dont be shocked by the source code :-)<BR><vipz> ok
:-)<BR><dhan> very impressive idea<BR><vipz> a_vox: i will reply to
you tomorrow<BR><dhan> a_vox : can you explain "copies of all prototype
master pageitems"<BR><vipz> that was a great idea<BR>* ludo2 hat die
Verbindung getrennt (Remote closed the connection)<BR><a_vox> dhan: we
wont use those masterpageitems as background (see c) ), but instead use them as
a prototype for new items on the regular page (maybe locking its size +
position, too)<BR><a_vox> These copy are fully editable then (except for
locking)<BR><dhan> oh i see<BR><dhan> please explain about
locking?<BR><a_vox> It's a really simple scheme. Synching isn't addressed
at all and must be sorted out later. But I guess this would still be usable,
even if prototype on master and regular item on page aren't synched all the
time<BR><a_vox> locking: in Scribus you can lock an items position and/or
size. I thought that should be done by default for masterpage
items</FONT></DIV></BODY></HTML>