Re: [Xswt-developer] repository, stylesheets and data binding
Brought to you by:
dvorme
|
From: David J. O. <dj...@co...> - 2006-10-06 03:33:53
|
Hallvard,=20 1) Regarding SourceForge: Ugh. They've been having issues lately. Please tr= y again tomorrow.=20 2) Regarding style sheets: I agree that both behaviors can be useful. Do yo= u prefer one over the other? Which do you think should be the default? Mayb= e we should add an x:include meta-attribute for the include behavior? I thi= nk that the usual semantic for styles is that the style sheet supplies defa= ults that can be overridden, so I think that might be an argument for keepi= ng the x:style attribute as a default appearance attribute. Do you agree?= =20 3) We just finished a conference call and decided on the API style for data= binding. You can find the details in bug #147563.=20 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D147563)=20 Regarding XSWT data binding, I'm going to revisit this once the JFace data = binding API settles down, probably in a week or two. I'm glad you're using = it because then I'll be able to get your feedback on it. :-)=20 Regards,=20 Dave Orme=20 PS: Yeah; now that we've got the data binding API fish fried, I might be ab= le to get some cycles to look at that editor again. :-)=20 ----- Original Message -----=20 From: Hallvard Tr=C3=A6tteberg <ha...@id...>=20 To: xsw...@li...=20 Sent: Thursday, October 5, 2006 7:31:43 AM GMT-0600=20 Subject: [Xswt-developer] repository, stylesheets and data binding=20 Hi,=20 Three topics today:=20 - CVS repository: I'm having problems connecting to the repository. I get a= =20 server errer when trying to connect (happens for all CVS operations to=20 xswt.cvs.sourceforge.net).=20 - stylesheets: The current stylesheet mechanism allows an element to=20 reference another with the x:style attribute. First the control for the=20 element is created, then it is "filled" in with the style's attributes and= =20 content, before its own attributes and content are used. This lets the styl= e=20 provide a set of defaults. When experimenting with the stylesheet mechanism= =20 I found that it could be useful for an element with a x:style attribute to= =20 use the style's element instead of its own, when creating the control in th= e=20 first place. I.e. you could use <control x:style=3D"styles.labelStyle"/> to= =20 create a label, if the styles.labelStyle refer to a label element. This=20 makes the x:style attribute be used more as an include than a defaulting=20 mechanism.=20 - data binding: I've been looking at the data binding packages and using it= =20 for my own data flow model, lately. I've already become very fond of it, bu= t=20 I'm worried since there's so many deprecated classes I need to use. I=20 understand they may be marked as such because the design hasn't been=20 completely settled, but would like ask (David) about the status of the=20 package, e.g. what parts can be relatively safely be used and what parts=20 that may be redesigned before becoming official.=20 Hallvard=20 P.S. I haven't looked at the editor, yet, but I'm becoming more interested= =20 than before, since my own dialog modelling project now generates xswt files= =20 that the developer would want to edit to fill in the details not covered by= =20 the model.=20 ---=20 Hallvard Tr=C3=A6tteberg (ha...@id..., http://www.idi.ntnu.no/~hal)=20 Associate Professor, IS group, Dept. of Computer and Information Sciences a= t=20 the Norwegian Univ. of Science and Technology=20 -------------------------------------------------------------------------= =20 Take Surveys. Earn Cash. Influence the Future of IT=20 Join SourceForge.net's Techsay panel and you'll get the chance to share you= r=20 opinions on IT & business topics through brief surveys -- and earn cash=20 http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE= VDEV=20 _______________________________________________=20 Xswt-developer mailing list=20 Xsw...@li...=20 https://lists.sourceforge.net/lists/listinfo/xswt-developer=20 |