swtxml - Project Hosting on Google Code

Older Nov 10, 2009 issue 40 (No orientation property values for SashForm) Status changed by ralf.ebert - Status: Fixed Status: Fixed Nov 10, 2009 issue 40 (No orientation property values for SashForm) commented on by ralf.ebert - Fixed with http://github.com/ralfebert/swtxml/commit/2bec59dae514263f5cfda3dc2876998f5fc99c84 I will push a new build in a few days Fixed with http://github.com/ralfebert/swtxml/commit/2bec59dae514263f5cfda3dc2876998f5fc99c84 I will push a new build in a few days Oct 28, 2009 UpdateSite (Eclipse Update Site for installing SWT/XML) Wiki page edited by ralf.ebert - Revision r69 Edited wiki page through web user interface. Revision r69 Edited wiki page through web user interface. Jun 18, 2009 issue 40 (No orientation property values for SashForm) reported by amazuzu - What steps will reproduce the problem? 1. <SashForm orientation="?????" /> 2. 3. What is the expected output? What do you see instead? should provide "horizontal" and "vertical" possible values What version of the product are you using? On what operating system? 0.0.7 win32 Please provide any additional information below. What steps will reproduce the problem? 1. <SashForm orientation="?????" /> 2. 3. What is the expected output? What do you see instead? should provide "horizontal" and "vertical" possible values What version of the product are you using? On what operating system? 0.0.7 win32 Please provide any additional information below. May 28, 2009 issue 39 (Add org.eclipse.jface.preference.PreferencePage as a supercl...) commented on by PieBandit - This is probably an enhancement. I'm unsure how to apply the Type-Enhancement label. This is probably an enhancement. I'm unsure how to apply the Type-Enhancement label. May 28, 2009 issue 39 (Add org.eclipse.jface.preference.PreferencePage as a supercl...) reported by PieBandit - org.eclipse.jface.preference.PreferencePage is a superclass for eclipse preference pages. right now, this cannot be the superclass. org.eclipse.jface.preference.PreferencePage is a superclass for eclipse preference pages. right now, this cannot be the superclass. Mar 24, 2009 ChangeLog (Changes / What's new and noteworthy?) Wiki page edited by ralf.ebert Mar 24, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Mar 24, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Mar 24, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Mar 24, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Mar 11, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by ralf.ebert - No, that would be crap indeed :) At runtime on top of the RCP framework you only need to have the com.swtxml and org.apache.commons.lang plug-ins. Both are pretty small and commons.lang is quite helpful anyway. The WST plugins are only needed for the IDE. The SWT/XML editor with code completion and preview is built upon the XML editor from Web Standard Tools and this is only included since Eclipse 3.4 in the standard Eclipse IDE build. No, that would be crap indeed :) At runtime on top of the RCP framework you only need to have the com.swtxml and org.apache.commons.lang plug-ins. Both are pretty small and commons.lang is quite helpful anyway. The WST plugins are only needed for the IDE. The SWT/XML editor with code completion and preview is built upon the XML editor from Web Standard Tools and this is only included since Eclipse 3.4 in the standard Eclipse IDE build. Mar 11, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by sgandon - You mean if I want to use SWT/XML in my RCP application base on eclipse 3.3 framework, I also need to add WST plugins as well as org.apache.commons.lang? This seems to me to big a constraint that really would stop me from using it. Can you give a precise list of plugin that need to be added on top of the basic RCP framework. Thanks. You mean if I want to use SWT/XML in my RCP application base on eclipse 3.3 framework, I also need to add WST plugins as well as org.apache.commons.lang? This seems to me to big a constraint that really would stop me from using it. Can you give a precise list of plugin that need to be added on top of the basic RCP framework. Thanks. Mar 11, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by ralf.ebert - SWT/XML 0.0.7 works with Eclipse 3.3 now. You need to install Web Standard Tools (WST) (using the update site) and the "org.apache.commons.lang" plug-in (you can copy it from Eclipse 3.4). SWT/XML 0.0.7 works with Eclipse 3.3 now. You need to install Web Standard Tools (WST) (using the update site) and the "org.apache.commons.lang" plug-in (you can copy it from Eclipse 3.4). Mar 11, 2009 ChangeLog (Changes / What's new and noteworthy?) Wiki page edited by ralf.ebert Mar 11, 2009 ChangeLog (Changes / What's new and noteworthy?) Wiki page edited by ralf.ebert Mar 11, 2009 swtxml_0.0.7.zip (SWT/XML 0.0.7) file uploaded by ralf.ebert - Labels: Featured Labels: Featured Mar 08, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by sgandon - Thanks for this quick answer. I have imported the project in an eclipse 3.3 instance and there are problems with some plugin dependencies that do not exists in Eclipse 3.3 such as org.apache.commons.lang I do not have much time to spend on that as I am working on another project but I hope you'll find a way to make your plugin compatible with the 3.3 plateform. Thanks for this quick answer. I have imported the project in an eclipse 3.3 instance and there are problems with some plugin dependencies that do not exists in Eclipse 3.3 such as org.apache.commons.lang I do not have much time to spend on that as I am working on another project but I hope you'll find a way to make your plugin compatible with the 3.3 plateform. Mar 08, 2009 issue 20 (Provide documentation on how to extend SWT/XML) commented on by ralf.ebert - Adding own components will be the first thing properly supported and documented. I have some patches ready for extension support already, but they are not stable enough to go in the release right now. Adding own components will be the first thing properly supported and documented. I have some patches ready for extension support already, but they are not stable enough to go in the release right now. Mar 08, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by ralf.ebert - Theoretically everything should work in Eclipse 3.3 as well, but I never tested it as all my projects already are on 3.4. Probably the specified required bundle versions are the only thing which prevent usage on 3.3 at the moment. I'll investigate this the next days. If you'd like to try it now: Import the plug-in projects from the download zip (or source repository) into your Eclipse 3.3 workspace and check what errors you get. Shouldn't be hard to fix. If you send me a patch, I can integrate it very soon, as I plan to release a new version next week. Theoretically everything should work in Eclipse 3.3 as well, but I never tested it as all my projects already are on 3.4. Probably the specified required bundle versions are the only thing which prevent usage on 3.3 at the moment. I'll investigate this the next days. If you'd like to try it now: Import the plug-in projects from the download zip (or source repository) into your Eclipse 3.3 workspace and check what errors you get. Shouldn't be hard to fix. If you send me a patch, I can integrate it very soon, as I plan to release a new version next week. Mar 08, 2009 issue 20 (Provide documentation on how to extend SWT/XML) commented on by sgandon - Yes I vote for this one, as I have made some SWT specific components I would like to use in swtxml. Yes I vote for this one, as I have made some SWT specific components I would like to use in swtxml. Mar 08, 2009 issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by sgandon - And what about Eclipse 3.3, all documentation state Eclipse 3.4 is required. I lead an RCP application at work base on the Eclipsee 3.3 RCP framework and we would like to use swtxml. And what about Eclipse 3.3, all documentation state Eclipse 3.4 is required. I lead an RCP application at work base on the Eclipsee 3.3 RCP framework and we would like to use swtxml. Jan 28, 2009 issue 38 (Support for dynamic UIs) reported by mikkel.t.andersen - Provide a mode attribute in the xml elements. <Button mode="doShowApply" text="apply"/> Then pass a list of strings to the parser, like "doShowApply" and others and then when parsing the xml determine if the widget should be created or not based on matching the passed in strings with the mode. This will allow the doShowApply to appear in the IDE editor/preview as a toggle button and you can then test your dynamic layouts by toggling the different modes. Provide a mode attribute in the xml elements. <Button mode="doShowApply" text="apply"/> Then pass a list of strings to the parser, like "doShowApply" and others and then when parsing the xml determine if the widget should be created or not based on matching the passed in strings with the mode. This will allow the doShowApply to appear in the IDE editor/preview as a toggle button and you can then test your dynamic layouts by toggling the different modes. Jan 16, 2009 issue 37 (Provide PDF user guide) reported by ralf.ebert - - - Jan 16, 2009 issue 36 (Provide nextTabControl-attribute syntax for Composite.setTab...) reported by ralf.ebert - - - Jan 09, 2009 r61 (updated ide screenshot) committed by ralf.ebert - updated ide screenshot updated ide screenshot Jan 08, 2009 issue 23 (Create superclass constructor for the view base classes whic...) Labels changed by ralf.ebert - Labels: Type-Defect −Type-Enhancement Labels: Type-Defect −Type-Enhancement Jan 08, 2009 issue 33 (Automatically create dependency to SWT/XML plugin when .swtx...) Labels changed by ralf.ebert - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Jan 08, 2009 issue 34 (Provide template for "New plug-in wizard" which contains a s...) Labels changed by ralf.ebert - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Jan 08, 2009 issue 35 (Strip test classes from release build to reduce plugin footp...) Labels changed by ralf.ebert - Labels: Type-Task −Type-Defect Labels: Type-Task −Type-Defect Jan 08, 2009 issue 35 (Strip test classes from release build to reduce plugin footp...) reported by ralf.ebert - - - Jan 08, 2009 issue 34 (Provide template for "New plug-in wizard" which contains a s...) reported by ralf.ebert - - - Jan 08, 2009 issue 33 (Automatically create dependency to SWT/XML plugin when .swtx...) reported by ralf.ebert - - - Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 ChangeLog (Changes / What's new and noteworthy?) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 UpdateSite (Eclipse Update Site for installing SWT/XML) Wiki page edited by ralf.ebert Jan 08, 2009 UpdateSite (Eclipse Update Site for installing SWT/XML) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 08, 2009 swtxml_0.0.6.zip (SWT/XML 0.0.6) file uploaded by ralf.ebert - Labels: Featured Labels: Featured Jan 08, 2009 ChangeLog (Changes / What's new and noteworthy?) Wiki page edited by ralf.ebert Jan 08, 2009 issue 18 (Provide a local update site with packaged downloads + source...) Status changed by ralf.ebert - c3caf4f... source plugin for com.swtxml configured builder scripts updated to generate source plugins + dropins/update-site folder in distribution zip Status: Fixed c3caf4f... source plugin for com.swtxml configured builder scripts updated to generate source plugins + dropins/update-site folder in distribution zip Status: Fixed Jan 08, 2009 issue 27 (Compile swt/xml with line numbers) Status changed by ralf.ebert - build scripts updated to include debug info Status: Fixed build scripts updated to include debug info Status: Fixed Jan 02, 2009 DeveloperGuide (Tutorial and guide for developers) Wiki page edited by ralf.ebert Jan 02, 2009 SideBar Wiki page deleted by ralf.ebert Jan 02, 2009 SideBar Wiki page added by ralf.ebert

issue 4 (Test/backport runtime plug-in to Eclipse 3.2) commented on by ralf.ebert - Theoretically everything should work in Eclipse 3.3 as well, but I never tested it as all my projects already are on 3.4. Probably the specified required bundle versions are the only thing which prevent usage on 3.3 at the moment. I'll investigate this the next days. If you'd like to try it now: Import the plug-in projects from the download zip (or source repository) into your Eclipse 3.3 workspace and check what errors you get. Shouldn't be hard to fix. If you send me a patch, I can integrate it very soon, as I plan to release a new version next week.

Theoretically everything should work in Eclipse 3.3 as well, but I never tested it as all my projects already are on 3.4. Probably the specified required bundle versions are the only thing which prevent usage on 3.3 at the moment. I'll investigate this the next days. If you'd like to try it now: Import the plug-in projects from the download zip (or source repository) into your Eclipse 3.3 workspace and check what errors you get. Shouldn't be hard to fix. If you send me a patch, I can integrate it very soon, as I plan to release a new version next week.

Older