Re: [Xswt-developer] Xswt-developer Digest, Vol 2, Issue 5
Brought to you by:
dvorme
|
From: <ha...@id...> - 2006-08-15 13:44:04
|
David, > -----Original Message----- > From: "David J. Orme" <dj...@co...> > Subject: [Xswt-developer] New task list > > (I know you won't get this right away, but I'm writing to the > list for everyone's benefit and as a central place to keep > these thoughts.) I'm back now. > I had a chance to look at the new code that just landed. > Great work! I'm especially impressed with the scripting and style sheet work. :-) > - Error handling and reporting: > > a) In addition to pushing line and column information into > the nodes so that we can just output the tree nodes as you > suggest, script syntax errors are silently ignored, but the > layout isn't built either. I've now changed the code to using a context object (element) for error reporting. The standard element implementation outputs line and column for the element (should be enough to identify a faulty attribute). I'll look into the problem of ignored script syntax errors. > b) There seem to be situations where other syntax errors > result in a layout not being built, but no error reported either. Can you give some hints for when? > - Style sheets: > > a) I didn't attempt to cascade across two or more files, but > I did try to cascade within a file. i.e: define a style that > references two other styles in the same file. That refused > to build, but also didn't display any error. I've now included some fixes and a test that cascades styles (in the same sheet file). > b) I've extended the style sheet test, and added comments > about additional style sheet things it would be nice to support. I think I understand what you want the XML to do, but could you anyway write the test case (java) code to make it clear? > - Editor / preview view: > > a) I'm about 95% done migrating the preview code to the new > editor framework. Hopefully that will get finished this week > and we can: I understand you had to temporarily stop working on XSWT and work in EclipseWorld presentations instead. How far have you come with the editor? > - See if we can get XSWT brought back into Eclipse in the 3.3 > time frame. There is some mild interest being expressed by > the Platform team, and I think we have a shot at it. This > would get us quite a bit more exposure. That would be great! Hallvard |