xswt-developer — Talk about developing/developing with XSWT

[Xswt-developer] handling uris for locating styles

[<ha...@id...>]

Hi,

I'm trying to integrate XSWT with a GMF (EMF+GEF++)-based tool, and one =
of
the problems I've come across is that of resolving URIs of styles. This =
is
currently done using either full URLs or URLs relative to a class (in =
the
project). This may work well for pure Java projects, but not necessarily =
for
others, e.g. I would like to refer to plugins and projects in the =
workspace.

What I would like to propose is a uri mapping interface, that handles =
two
things: 1) the mapping from an uri to an input stream: InputStream
getInputStream(String uri), and 2) resolving a relative uri in the =
context
of a base uri: String resolve(String uri, String base). A default
implementation would support the current mechanism (URLs and class =
names),
while I would be able to write a different one, e.g. utilizing EMFs URI.

Hallvard

---
Hallvard Tr=E6tteberg (ha...@id..., http://www.idi.ntnu.no/~hal)
Associate Professor, IS group, Dept. of Computer and Information =
Sciences at
the Norwegian Univ. of Science and Technology

Re: [Xswt-developer] problems accessing CVS

[David J. O. <dj...@co...>]

Hi Hallvard,=20

About SF.net: Ouch! We'll have to move to a different repository somewhere.=
 :(=20

More details to follow. Suggestions welcome.=20


Best regards,=20

Dave Orme=20
----- Original Message -----=20
From: Hallvard Tr=C3=A6tteberg <ha...@id...>=20
To: xsw...@li...=20
Sent: Friday, December 1, 2006 11:37:44 AM GMT-0600=20
Subject: [Xswt-developer] problems accessing CVS=20

David,=20

I've had problems accessing the CVS repository for long time, now. I get th=
e=20
same error message when trying to e.g. update:=20

Problems reported while synchronizing CVS Workspace. 0 of 1 resources were=
=20
synchronized.=20
An error occurred synchronizing /com.swtworkbench.community.xswt: Could=20
not connect to :ext:hal...@xs...:/cvsroot/xswt: I/O=20
exception occurred: CreateProcess: ssh -l hallvard xswt.cvs.sourceforge.net=
=20
cvs server error=3D2=20
Could not connect to=20
:ext:hal...@xs...:/cvsroot/xswt: I/O exception=20
occurred: CreateProcess: ssh -l hallvard xswt.cvs.sourceforge.net cvs serve=
r=20
error=3D2=20
CreateProcess: ssh -l hallvard xswt.cvs.sourceforge.net cvs server=20
error=3D2=20

I would like to take a look at your XSWT editor, but what can I do to=20
retrieve it?=20

Hallvard=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

[Xswt-developer] problems accessing CVS

[<ha...@id...>]

David,

I've had problems accessing the CVS repository for long time, now. I get =
the
same error message when trying to e.g. update:=20

Problems reported while synchronizing CVS Workspace. 0 of 1 resources =
were
synchronized.
  An error occurred synchronizing /com.swtworkbench.community.xswt: =
Could
not connect to :ext:hal...@xs...:/cvsroot/xswt: I/O
exception occurred: CreateProcess: ssh -l hallvard =
xswt.cvs.sourceforge.net
cvs server error=3D2
    Could not connect to
:ext:hal...@xs...:/cvsroot/xswt: I/O exception
occurred: CreateProcess: ssh -l hallvard xswt.cvs.sourceforge.net cvs =
server
error=3D2
    CreateProcess: ssh -l hallvard xswt.cvs.sourceforge.net cvs server
error=3D2

I would like to take a look at your XSWT editor, but what can I do to
retrieve it?

Hallvard

---
Hallvard Tr=E6tteberg (ha...@id..., http://www.idi.ntnu.no/~hal)
Associate Professor, IS group, Dept. of Computer and Information =
Sciences at
the Norwegian Univ. of Science and Technology

Re: [Xswt-developer] FormToolkit support

[David J. O. <dj...@co...>]

Markus, 

I just committed this code to the main XSWT plugin. Thanks much! 

This isn't an ideal solution though. Currently, we have the following dependencies: 

- XSWT Library: Just SWT 
- XSWT Plugin: SWT and org.eclipse.ui 

We currently don't depend on org.eclipse.ui.forms and I don't think we should force this dependency on folks. The choices right now seem to be: (a) add another plugin that depends on XSWT and org.eclipxe.ui.forms and includes only this one class; (b) put this class in XSWT proper and if folks want to use it, they'll have to copy it into their own project. In the meantime, this one file will always have compile errors due to the unsatisfied dependency. 

For now, I've chosen (b). If someone comes up with a better solution, please let me (us) know. :-) 


Best regards, 

Dave Orme 

----- Original Message ----- 
From: Markus Wolf <ma...@em...> 
To: xsw...@li... 
Sent: Monday, October 16, 2006 4:30:22 PM GMT-0600 
Subject: Re: [Xswt-developer] FormToolkit support 

-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 

Hi, 

I've attached a slightly modified variant of the 
FormToolkitLayoutBuilder which enabled support to reuse the FormToolkit. 
There are two options: 

1. Get the toolkit from the LayoutBuilder and use it. Then one should 
not dispose the toolkit, just as the SWT policy recommend to only 
dispose what you've created by yourself. 
2. Set a tookit with the constructor and let the LayoutBuilder use your 
precreated one. Then one should dispose the toolkit. 

With this simple extensions it is relative easy to implement a 
FormEditor using the org.eclipse.ui.forms classes and a ManagedForm. 

Feel free to contribute this to the codebase. 

Markus Wolf 
- -- 
> 
> emedia-solutions wolf 
> Wedeler Landstrasse 63 
> 22559 Hamburg 
> (040) 550 083 70 
> 
>> web: http://www.emedia-solutions-wolf.de 
>> mail: ma...@em... 
>> pgp: http://wwwkeys.de.pgp.net 
> 
-----BEGIN PGP SIGNATURE----- 
Version: GnuPG v1.4.3 (GNU/Linux) 
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 

iD8DBQFFM/nueyJE91ndMG4RAnpfAJ9lVdv2ftQs8xM+1zedyKED24Cp0wCcDBxA 
inV1B3DsLrW/HtQmysVtWnk= 
=stzx 
-----END PGP SIGNATURE----- 

Re: [Xswt-developer] XSWT Embedding error

[David J. O. <dj...@co...>]

Hi Olivier,=20

Yeah, that's the 1.0 API. We had to change it in 1.5 to fix a couple of obs=
cure but sometimes nasty bugs.=20

I'm sorry for the confusion. I'm working franticly to clear my plate so I c=
an get back to working on shipping the next version of this thing. :-)=20


Best regards,=20

Dave Orme=20

----- Original Message -----=20
From: Olivier Parisy <ml....@fr...>=20
To: xsw...@li...=20
Sent: Friday, October 20, 2006 3:21:07 PM GMT-0600=20
Subject: Re: [Xswt-developer] XSWT Embedding error=20

David,=20

Thank to your detailed walk through, I've been able to fix my problem.=20

I was hinted by the difference in API: you are using the=20
XSWT.create(flux).parse(shell) call, while I was using the=20
XSWT.create(shell, flux) one.=20

It turned out that I did not use the plugin xswt.jar archive, but=20
another jar I probably downloaded somewhere on sourceforge. Using the=20
plugin jar lead to the calling convention change and to a working piece=20
of code. Did I use an old jar using an obsolete xswt syntax or something=20
similar?=20

Thanks anyway for your involvement.=20

Regards,=20
Olivier Parisy.=20

David J. Orme a =C3=A9crit :=20
> Apologies for the delay at getting back to you. I forgot I was going=20
> to be out of town for the weekend. :-( But I've had a chance to try=20
> your example. My results follow:=20
>=20
> I created a new Plug-in project, added XSWT and SWT as dependencies,=20
> created a "com.cps.test" package, and copied XSWTTest from the=20
> com.swtworkbench.community.xswt.examples.newsyntax package of the XSWT=20
> plugin into the new project. For reference, this is the code I copied=20
> into the project:=20
>=20
> public class XSWTTest {=20
>=20
> public static void main(String[] args) throws IOException {=20
> Display display =3D new Display();=20
> Shell shell =3D new Shell(display);=20
> Map results =3D null;=20
>=20
> try {=20
> results =3D=20
> XSWT.create(XSWTTest.class.getResourceAsStream("Test.xswt"))=20
> .parse(shell);=20
> } catch (XSWTException e) {=20
> Logger.log().error(e, "Unable to parse XSWT file");=20
> }=20
>=20
> shell.setSize(600, 600);=20
> shell.open();=20
> while (!shell.isDisposed()) {=20
> if (!display.readAndDispatch())=20
> display.sleep();=20
> }=20
> display.dispose();=20
> }=20
> }=20
>=20
> I created an XSWT file named Test.xswt with your XSWT code right next=20
> to the XSWTTest.java class. Then I right-clicked XSWTTest.java, chose=20
> "Run as > SWT Application" from the menu, and it worked fine.=20
>=20
> Hopefully, this is enough to get you running again too.=20
>=20
> You can do it using a regular Java project too, but then you have to=20
> manually add the SWT libraries to the classpath, and so on.=20
>=20
> Please let me know if you can't get it going and I'll try to help.=20
>=20
>=20
> Best regards,=20
>=20
> Dave Orme=20



-------------------------------------------------------------------------=
=20
Using Tomcat but need to do more? Need to support web services, security?=
=20
Get stuff done quickly with pre-integrated technology to make your job easi=
er=20
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo=
=20
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642=20
_______________________________________________=20
Xswt-developer mailing list=20
Xsw...@li...=20
https://lists.sourceforge.net/lists/listinfo/xswt-developer=20

Re: [Xswt-developer] XSWT Embedding error

[Olivier P. <ml....@fr...>]

David,

Thank to your detailed walk through, I've been able to fix my problem=
.

I was hinted by the difference in API: you are using the=20
XSWT.create(flux).parse(shell) call, while I was using the=20
XSWT.create(shell, flux) one.

It turned out that I did not use the plugin xswt.jar archive, but=
=20
another jar I probably downloaded somewhere on sourceforge. Using the=
=20
plugin jar lead to the calling convention change and to a working pie=
ce=20
of code. Did I use an old jar using an obsolete xswt syntax or someth=
ing=20
similar?

Thanks anyway for your involvement.

Regards,
Olivier Parisy.

David J. Orme a =C3=A9crit :
> Apologies for the delay at getting back to you.  I forgot I was goi=
ng=20
> to be out of town for the weekend. :-(  But I've had a chance to tr=
y=20
> your example.  My results follow:
>
> I created a new Plug-in project, added XSWT and SWT as dependencies=
,=20
> created a "com.cps.test" package, and copied XSWTTest from the=20
> com.swtworkbench.community.xswt.examples.newsyntax package of the X=
SWT=20
> plugin into the new project.  For reference, this is the code I cop=
ied=20
> into the project:
>
> public class XSWTTest {
>
>    public static void main(String[] args) throws IOException {
>       Display display =3D new Display();
>       Shell shell =3D new Shell(display);
>       Map results =3D null;
>
>       try {
>          results =3D=20
> XSWT.create(XSWTTest.class.getResourceAsStream("Test.xswt"))
>                .parse(shell);
>       } catch (XSWTException e) {
>          Logger.log().error(e, "Unable to parse XSWT file");
>       }
>
>       shell.setSize(600, 600);
>       shell.open();
>       while (!shell.isDisposed()) {
>          if (!display.readAndDispatch())
>             display.sleep();
>       }
>       display.dispose();
>    }
> }
>
> I created an XSWT file named Test.xswt with your XSWT code right ne=
xt=20
> to the XSWTTest.java class.  Then I right-clicked XSWTTest.java, ch=
ose=20
> "Run as > SWT Application" from the menu, and it worked fine.
>
> Hopefully, this is enough to get you running again too.
>
> You can do it using a regular Java project too, but then you have t=
o=20
> manually add the SWT libraries to the classpath, and so on.
>
> Please let me know if you can't get it going and I'll try to help.
>
>
> Best regards,
>
> Dave Orme

Re: [Xswt-developer] FormToolkit support

[David J. O. <dj...@co...>]

Thank you Markus! 


Regards, 

Dave Orme 
----- Original Message ----- 
From: Markus Wolf <ma...@em...> 
To: xsw...@li... 
Sent: Monday, October 16, 2006 4:30:22 PM GMT-0600 
Subject: Re: [Xswt-developer] FormToolkit support 

-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 

Hi, 

I've attached a slightly modified variant of the 
FormToolkitLayoutBuilder which enabled support to reuse the FormToolkit. 
There are two options: 

1. Get the toolkit from the LayoutBuilder and use it. Then one should 
not dispose the toolkit, just as the SWT policy recommend to only 
dispose what you've created by yourself. 
2. Set a tookit with the constructor and let the LayoutBuilder use your 
precreated one. Then one should dispose the toolkit. 

With this simple extensions it is relative easy to implement a 
FormEditor using the org.eclipse.ui.forms classes and a ManagedForm. 

Feel free to contribute this to the codebase. 

Markus Wolf 
- -- 
> 
> emedia-solutions wolf 
> Wedeler Landstrasse 63 
> 22559 Hamburg 
> (040) 550 083 70 
> 
>> web: http://www.emedia-solutions-wolf.de 
>> mail: ma...@em... 
>> pgp: http://wwwkeys.de.pgp.net 
> 
-----BEGIN PGP SIGNATURE----- 
Version: GnuPG v1.4.3 (GNU/Linux) 
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 

iD8DBQFFM/nueyJE91ndMG4RAnpfAJ9lVdv2ftQs8xM+1zedyKED24Cp0wCcDBxA 
inV1B3DsLrW/HtQmysVtWnk= 
=stzx 
-----END PGP SIGNATURE----- 

Re: [Xswt-developer] FormToolkit support

[Markus W. <ma...@em...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've attached a slightly modified variant of the
FormToolkitLayoutBuilder which enabled support to reuse the FormToolkit.
There are two options:

1. Get the toolkit from the LayoutBuilder and use it. Then one should
not dispose the toolkit, just as the SWT policy recommend to only
dispose what you've created by yourself.
2. Set a tookit with the constructor and let the LayoutBuilder use your
precreated one. Then one should dispose the toolkit.

With this simple extensions it is relative easy to implement a
FormEditor using the org.eclipse.ui.forms classes and a ManagedForm.

Feel free to contribute this to the codebase.

Markus Wolf
- --
>
> emedia-solutions wolf
> Wedeler Landstrasse 63
> 22559 Hamburg
> (040) 550 083 70
>
>>  web: http://www.emedia-solutions-wolf.de
>> mail: ma...@em...
>>  pgp: http://wwwkeys.de.pgp.net
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFM/nueyJE91ndMG4RAnpfAJ9lVdv2ftQs8xM+1zedyKED24Cp0wCcDBxA
inV1B3DsLrW/HtQmysVtWnk=
=stzx
-----END PGP SIGNATURE-----

Re: [Xswt-developer] XSWT Embedding error

[David J. O. <dj...@co...>]

Apologies for the delay at getting back to you. I forgot I was going to be out of town for the weekend. :-( But I've had a chance to try your example. My results follow: 

I created a new Plug-in project, added XSWT and SWT as dependencies, created a "com.cps.test" package, and copied XSWTTest from the com.swtworkbench.community.xswt.examples.newsyntax package of the XSWT plugin into the new project. For reference, this is the code I copied into the project: 

public class XSWTTest { 

public static void main(String[] args) throws IOException { 
Display display = new Display(); 
Shell shell = new Shell(display); 
Map results = null; 

try { 
results = XSWT.create(XSWTTest.class.getResourceAsStream("Test.xswt")) 
.parse(shell); 
} catch (XSWTException e) { 
Logger.log().error(e, "Unable to parse XSWT file"); 
} 

shell.setSize(600, 600); 
shell.open(); 
while (!shell.isDisposed()) { 
if (!display.readAndDispatch()) 
display.sleep(); 
} 
display.dispose(); 
} 
} 

I created an XSWT file named Test.xswt with your XSWT code right next to the XSWTTest.java class. Then I right-clicked XSWTTest.java, chose "Run as > SWT Application" from the menu, and it worked fine. 

Hopefully, this is enough to get you running again too. 

You can do it using a regular Java project too, but then you have to manually add the SWT libraries to the classpath, and so on. 

Please let me know if you can't get it going and I'll try to help. 


Best regards, 

Dave Orme 
----- Original Message ----- 
From: Olivier Parisy <ml....@fr...> 
To: xsw...@li... 
Sent: Monday, October 9, 2006 4:07:01 PM GMT-0600 
Subject: [Xswt-developer] XSWT Embedding error 

Hi, 

I successfully designed a small xswt layout using the XSWT preview plugin: 

<?xml version="1.0" encoding="UTF-8"?> 
<xswt xmlns:x="http://sweet_swt.sf.net/xswt"> 
<import xmlns="http://sweet_swt.sf.net/xswt"> 
<package name="java.lang"/> 
<package name="org.eclipse.swt.widgets"/> 
<package name="org.eclipse.swt.layout"/> 
<package name="org.eclipse.swt.graphics"/> 
</import> 
<layout x:class="gridLayout" marginHeight="0" marginWidth="0" 
numColumns="1"/> 
<x:children> 
<composite> 
<layoutData x:class="gridData" 
grabExcessHorizontalSpace="true" grabExcessVerticalSpace="true" 
horizontalAlignment="GridData.FILL" verticalAlignment="GridData.FILL"/> 
<layout x:class="formLayout" marginHeight="0" 
marginWidth="0"/> 
<label text="Link Entry Editor" x:id="title"> 
<layoutData x:class="formData"> 
<top x:p0="0" offset="5"/> 
<left x:p0="0" offset="5"/> 
</layoutData> 
</label> 
<!-- (...) --> 
</composite> 
</x:children> 
</xswt> 


I am now trying to embed it in an java program, but at execution time, I 
get the following error: 

com.swtworkbench.community.xswt.XSWTException: Property/method/field not 
found: label 
Row:14, Column:59 
at 
com.swtworkbench.community.xswt.XSWT.processNodeProperty(XSWT.java:1125) 
at com.swtworkbench.community.xswt.XSWT.processSubNodes(XSWT.java:1040) 
at com.swtworkbench.community.xswt.XSWT.processChild(XSWT.java:727) 
at 
com.swtworkbench.community.xswt.XSWT.processChildControls(XSWT.java:681) 
at com.swtworkbench.community.xswt.XSWT.processXSWTNode(XSWT.java:655) 
at 
com.swtworkbench.community.xswt.XSWT.processTopLevelElement(XSWT.java:627) 
at com.swtworkbench.community.xswt.XSWT.parse(XSWT.java:378) 
at com.swtworkbench.community.xswt.XSWT.create(XSWT.java:254) 
at tray.LinkWindow2.<init>(LinkWindow2.java:21) 

As I understand it, this mean the <label> tag has not been recognized as 
an SWT widget, and is hence considered ad either a property, method or 
field of <composite>. Which of course it is not. 

Any hint? 


My invokation code is: 

InputStream flux = 
getClass().getResourceAsStream("/forms/linkeditor2.xswt"); 
results = XSWT.create(shell, flux); 

I imported the following jars in my project: 
- swt and associated native library 
- xswt.jar 
- xmlpull_1_1_3_1.jar 
- kxml2-min.jar 


Regards, 
Olivier Parisy. 


------------------------------------------------------------------------- 
Take Surveys. Earn Cash. Influence the Future of IT 
Join SourceForge.net's Techsay panel and you'll get the chance to share your 
opinions on IT & business topics through brief surveys -- and earn cash 
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV 
_______________________________________________ 
Xswt-developer mailing list 
Xsw...@li... 
https://lists.sourceforge.net/lists/listinfo/xswt-developer 

Re: [Xswt-developer] XSWT Embedding error

[Olivier P. <ml....@fr...>]

David J. Orme a =C3=A9crit :
> Yoouch!  Has it really been 3 days since I got this?  Man, I must b=
e=20
> busy or something.
>
> Tomorrow...  Unless someone from the community beats me to it. :)

Hey, thanks for your interest anyway!

I did not progress on this problem since my previous post. If those=
=20
informations are not sufficient, I will write a small, complete examp=
le=20
reproducing it.

Regards,
Olivier Parisy.

Re: [Xswt-developer] XSWT Embedding error

[David J. O. <dj...@co...>]

Yoouch! Has it really been 3 days since I got this? Man, I must be busy or something. 

Tomorrow... Unless someone from the community beats me to it. :) 


Regards, 

Dave Orme 
----- Original Message ----- 
From: Olivier Parisy <ml....@fr...> 
To: xsw...@li... 
Sent: Monday, October 9, 2006 4:07:01 PM GMT-0600 
Subject: [Xswt-developer] XSWT Embedding error 

Hi, 

I successfully designed a small xswt layout using the XSWT preview plugin: 

<?xml version="1.0" encoding="UTF-8"?> 
<xswt xmlns:x="http://sweet_swt.sf.net/xswt"> 
<import xmlns="http://sweet_swt.sf.net/xswt"> 
<package name="java.lang"/> 
<package name="org.eclipse.swt.widgets"/> 
<package name="org.eclipse.swt.layout"/> 
<package name="org.eclipse.swt.graphics"/> 
</import> 
<layout x:class="gridLayout" marginHeight="0" marginWidth="0" 
numColumns="1"/> 
<x:children> 
<composite> 
<layoutData x:class="gridData" 
grabExcessHorizontalSpace="true" grabExcessVerticalSpace="true" 
horizontalAlignment="GridData.FILL" verticalAlignment="GridData.FILL"/> 
<layout x:class="formLayout" marginHeight="0" 
marginWidth="0"/> 
<label text="Link Entry Editor" x:id="title"> 
<layoutData x:class="formData"> 
<top x:p0="0" offset="5"/> 
<left x:p0="0" offset="5"/> 
</layoutData> 
</label> 
<!-- (...) --> 
</composite> 
</x:children> 
</xswt> 


I am now trying to embed it in an java program, but at execution time, I 
get the following error: 

com.swtworkbench.community.xswt.XSWTException: Property/method/field not 
found: label 
Row:14, Column:59 
at 
com.swtworkbench.community.xswt.XSWT.processNodeProperty(XSWT.java:1125) 
at com.swtworkbench.community.xswt.XSWT.processSubNodes(XSWT.java:1040) 
at com.swtworkbench.community.xswt.XSWT.processChild(XSWT.java:727) 
at 
com.swtworkbench.community.xswt.XSWT.processChildControls(XSWT.java:681) 
at com.swtworkbench.community.xswt.XSWT.processXSWTNode(XSWT.java:655) 
at 
com.swtworkbench.community.xswt.XSWT.processTopLevelElement(XSWT.java:627) 
at com.swtworkbench.community.xswt.XSWT.parse(XSWT.java:378) 
at com.swtworkbench.community.xswt.XSWT.create(XSWT.java:254) 
at tray.LinkWindow2.<init>(LinkWindow2.java:21) 

As I understand it, this mean the <label> tag has not been recognized as 
an SWT widget, and is hence considered ad either a property, method or 
field of <composite>. Which of course it is not. 

Any hint? 


My invokation code is: 

InputStream flux = 
getClass().getResourceAsStream("/forms/linkeditor2.xswt"); 
results = XSWT.create(shell, flux); 

I imported the following jars in my project: 
- swt and associated native library 
- xswt.jar 
- xmlpull_1_1_3_1.jar 
- kxml2-min.jar 


Regards, 
Olivier Parisy. 


------------------------------------------------------------------------- 
Take Surveys. Earn Cash. Influence the Future of IT 
Join SourceForge.net's Techsay panel and you'll get the chance to share your 
opinions on IT & business topics through brief surveys -- and earn cash 
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV 
_______________________________________________ 
Xswt-developer mailing list 
Xsw...@li... 
https://lists.sourceforge.net/lists/listinfo/xswt-developer 

Re: [Xswt-developer] FormToolkit support

[David J. O. <dj...@co...>]

Thanks 

Dave 
----- Original Message ----- 
From: Markus Wolf <ma...@em...> 
To: xsw...@li... 
Sent: Wednesday, October 11, 2006 1:41:06 AM GMT-0600 
Subject: Re: [Xswt-developer] FormToolkit support 

-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 


> If you agree to your contribution being licensed under the Eclipse 
> Public License, please reply and say so. :-) (It's less than 100 lines 
> so I don't have to ask you to fill out a committer agreement.) 
> 
Sure it is ok. 
I've already added the EPL text to the top of the file. 

> 
> Best regards, 
> 
> Dave Orme 
> ----- Original Message ----- 
> From: Markus Wolf <ma...@em...> 
> To: xsw...@li... 
> Sent: Tuesday, October 10, 2006 5:55:07 PM GMT-0600 
> Subject: [Xswt-developer] FormToolkit support 
> 
> Hi, 
> 
> after recognizing that there is no FormToolkit support and reading the 
> mailing archives I decided to grab the idea of Phillip Bairds and 
> implement a extended SWTLayoutBuilder which is FormToolkit aware. 
> 
> Attached are the LayoutBuilder class (read for contribution). Some 
> widgets are a bit hacky, because there are properties and methods which 
> could not be set throught xml and therefore has to be configured 
> afterwards throught the result Map from the parser. 
> 
> Also I attached two more files. A view and a xml used by it. The view 
> contains most widgets shown in 'Eclipse Forms: Rich UI for the Rich 
> Client' (http://www.eclipse.org/articles/Article-Forms/article.html). 
> 
> I'll continue to work on this when my time allows it to remove the 
> 'hacky' parts and maybe add multipage editor support to it as well as 
> support for the XSWT-Preview-View for FormToolkit. 
> 
> There is not much more to say but: XSWT is a great tool. :) Keep going. 
> 
> Markus Wolf 

- ------------------------------------------------------------------------ 

- ------------------------------------------------------------------------- 
Using Tomcat but need to do more? Need to support web services, security? 
Get stuff done quickly with pre-integrated technology to make your job 
easier 
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo 
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 


- ------------------------------------------------------------------------ 

_______________________________________________ 
Xswt-developer mailing list 
Xsw...@li... 
https://lists.sourceforge.net/lists/listinfo/xswt-developer 


- -- 
> 
> emedia-solutions wolf 
> Wedeler Landstrasse 63 
> 22559 Hamburg 
> (040) 550 083 70 
> 
>> web: http://www.emedia-solutions-wolf.de 
>> mail: ma...@em... 
>> pgp: http://wwwkeys.de.pgp.net 
> 
-----BEGIN PGP SIGNATURE----- 
Version: GnuPG v1.4.3 (GNU/Linux) 
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 

iD8DBQFFLJICeyJE91ndMG4RAgBbAJ0SSb//ZrQ5+FrQtd8qwO996fxy2wCfQ/L4 
Ro4Vg0RYwagWW+mvjVZQsDk= 
=BpQ+ 
-----END PGP SIGNATURE----- 

------------------------------------------------------------------------- 
Using Tomcat but need to do more? Need to support web services, security? 
Get stuff done quickly with pre-integrated technology to make your job easier 
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo 
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
_______________________________________________ 
Xswt-developer mailing list 
Xsw...@li... 
https://lists.sourceforge.net/lists/listinfo/xswt-developer 

Re: [Xswt-developer] FormToolkit support

[Markus W. <ma...@em...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> If you agree to your contribution being licensed under the Eclipse
> Public License, please reply and say so. :-)  (It's less than 100 lines
> so I don't have to ask you to fill out a committer agreement.)
> 
Sure it is ok.
I've already added the EPL text to the top of the file.

> 
> Best regards,
> 
> Dave Orme
> ----- Original Message -----
> From: Markus Wolf <ma...@em...>
> To: xsw...@li...
> Sent: Tuesday, October 10, 2006 5:55:07 PM GMT-0600
> Subject: [Xswt-developer] FormToolkit support
> 
> Hi,
> 
> after recognizing that there is no FormToolkit support and reading the
> mailing archives I decided to grab the idea of Phillip Bairds and
> implement a extended SWTLayoutBuilder which is FormToolkit aware.
> 
> Attached are the LayoutBuilder class (read for contribution). Some
> widgets are a bit hacky, because there are properties and methods which
> could not be set throught xml and therefore has to be configured
> afterwards throught the result Map from the parser.
> 
> Also I attached two more files. A view and a xml used by it. The view
> contains most widgets shown in 'Eclipse Forms: Rich UI for the Rich
> Client' (http://www.eclipse.org/articles/Article-Forms/article.html).
> 
> I'll continue to work on this when my time allows it to remove the
> 'hacky' parts and maybe add multipage editor support to it as well as
> support for the XSWT-Preview-View for FormToolkit.
> 
> There is not much more to say but: XSWT is a great tool. :) Keep going.
> 
> Markus Wolf

- ------------------------------------------------------------------------

- -------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


- ------------------------------------------------------------------------

_______________________________________________
Xswt-developer mailing list
Xsw...@li...
https://lists.sourceforge.net/lists/listinfo/xswt-developer


- --
>
> emedia-solutions wolf
> Wedeler Landstrasse 63
> 22559 Hamburg
> (040) 550 083 70
>
>>  web: http://www.emedia-solutions-wolf.de
>> mail: ma...@em...
>>  pgp: http://wwwkeys.de.pgp.net
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLJICeyJE91ndMG4RAgBbAJ0SSb//ZrQ5+FrQtd8qwO996fxy2wCfQ/L4
Ro4Vg0RYwagWW+mvjVZQsDk=
=BpQ+
-----END PGP SIGNATURE-----

Re: [Xswt-developer] FormToolkit support

[David J. O. <dj...@co...>]

Thanks! This is wonderful. 

If you agree to your contribution being licensed under the Eclipse Public License, please reply and say so. :-) (It's less than 100 lines so I don't have to ask you to fill out a committer agreement.) 


Best regards, 

Dave Orme 
----- Original Message ----- 
From: Markus Wolf <ma...@em...> 
To: xsw...@li... 
Sent: Tuesday, October 10, 2006 5:55:07 PM GMT-0600 
Subject: [Xswt-developer] FormToolkit support 

-----BEGIN PGP SIGNED MESSAGE----- 
Hash: SHA1 

Hi, 

after recognizing that there is no FormToolkit support and reading the 
mailing archives I decided to grab the idea of Phillip Bairds and 
implement a extended SWTLayoutBuilder which is FormToolkit aware. 

Attached are the LayoutBuilder class (read for contribution). Some 
widgets are a bit hacky, because there are properties and methods which 
could not be set throught xml and therefore has to be configured 
afterwards throught the result Map from the parser. 

Also I attached two more files. A view and a xml used by it. The view 
contains most widgets shown in 'Eclipse Forms: Rich UI for the Rich 
Client' (http://www.eclipse.org/articles/Article-Forms/article.html). 

I'll continue to work on this when my time allows it to remove the 
'hacky' parts and maybe add multipage editor support to it as well as 
support for the XSWT-Preview-View for FormToolkit. 

There is not much more to say but: XSWT is a great tool. :) Keep going. 

Markus Wolf 
- -- 
> 
> emedia-solutions wolf 
> Wedeler Landstrasse 63 
> 22559 Hamburg 
> (040) 550 083 70 
> 
>> web: http://www.emedia-solutions-wolf.de 
>> mail: ma...@em... 
>> pgp: http://wwwkeys.de.pgp.net 
> 
-----BEGIN PGP SIGNATURE----- 
Version: GnuPG v1.4.3 (GNU/Linux) 
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org 

iD8DBQFFLCTLeyJE91ndMG4RAp+bAJ4lc0ZYjVTyptJhNA5s0CSl7huz5wCbB9mG 
g3q3dBmP3MVgSW0lvkdXwlc= 
=qnie 
-----END PGP SIGNATURE----- 

[Xswt-developer] FormToolkit support

[Markus W. <ma...@em...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

after recognizing that there is no FormToolkit support and reading the
mailing archives I decided to grab the idea of Phillip Bairds and
implement a extended SWTLayoutBuilder which is FormToolkit aware.

Attached are the LayoutBuilder class (read for contribution). Some
widgets are a bit hacky, because there are properties and methods which
could not be set throught xml and therefore has to be configured
afterwards throught the result Map from the parser.

Also I attached two more files. A view and a xml used by it. The view
contains most widgets shown in 'Eclipse Forms: Rich UI for the Rich
Client' (http://www.eclipse.org/articles/Article-Forms/article.html).

I'll continue to work on this when my time allows it to remove the
'hacky' parts and maybe add multipage editor support to it as well as
support for the XSWT-Preview-View for FormToolkit.

There is not much more to say but: XSWT is a great tool. :) Keep going.

Markus Wolf
- --
>
> emedia-solutions wolf
> Wedeler Landstrasse 63
> 22559 Hamburg
> (040) 550 083 70
>
>>  web: http://www.emedia-solutions-wolf.de
>> mail: ma...@em...
>>  pgp: http://wwwkeys.de.pgp.net
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLCTLeyJE91ndMG4RAp+bAJ4lc0ZYjVTyptJhNA5s0CSl7huz5wCbB9mG
g3q3dBmP3MVgSW0lvkdXwlc=
=qnie
-----END PGP SIGNATURE-----

[Xswt-developer] XSWT Embedding error

[Olivier P. <ml....@fr...>]

Hi,

I successfully designed a small xswt layout using the XSWT preview plugin:

<?xml version="1.0" encoding="UTF-8"?>
<xswt xmlns:x="http://sweet_swt.sf.net/xswt">
    <import xmlns="http://sweet_swt.sf.net/xswt">
        <package name="java.lang"/>
        <package name="org.eclipse.swt.widgets"/>
        <package name="org.eclipse.swt.layout"/>
        <package name="org.eclipse.swt.graphics"/>
    </import>
    <layout x:class="gridLayout" marginHeight="0" marginWidth="0" 
numColumns="1"/>
    <x:children>
            <composite>
                <layoutData x:class="gridData" 
grabExcessHorizontalSpace="true" grabExcessVerticalSpace="true" 
horizontalAlignment="GridData.FILL" verticalAlignment="GridData.FILL"/>
                <layout x:class="formLayout" marginHeight="0" 
marginWidth="0"/>
                <label text="Link Entry Editor" x:id="title">
                    <layoutData x:class="formData">
                        <top x:p0="0" offset="5"/>
                        <left x:p0="0" offset="5"/>
                    </layoutData>
                </label>
<!-- (...) -->
            </composite>
    </x:children>
</xswt>


I am now trying to embed it in an java program, but at execution time, I 
get the following error:

com.swtworkbench.community.xswt.XSWTException: Property/method/field not 
found: label
Row:14, Column:59
    at 
com.swtworkbench.community.xswt.XSWT.processNodeProperty(XSWT.java:1125)
    at com.swtworkbench.community.xswt.XSWT.processSubNodes(XSWT.java:1040)
    at com.swtworkbench.community.xswt.XSWT.processChild(XSWT.java:727)
    at 
com.swtworkbench.community.xswt.XSWT.processChildControls(XSWT.java:681)
    at com.swtworkbench.community.xswt.XSWT.processXSWTNode(XSWT.java:655)
    at 
com.swtworkbench.community.xswt.XSWT.processTopLevelElement(XSWT.java:627)
    at com.swtworkbench.community.xswt.XSWT.parse(XSWT.java:378)
    at com.swtworkbench.community.xswt.XSWT.create(XSWT.java:254)
    at tray.LinkWindow2.<init>(LinkWindow2.java:21)

As I understand it, this mean the <label> tag has not been recognized as 
an SWT widget, and is hence considered ad either a property, method or 
field of <composite>. Which of course it is not.

Any hint?


My invokation code is:

        InputStream flux = 
getClass().getResourceAsStream("/forms/linkeditor2.xswt");
        results = XSWT.create(shell, flux);

I imported the following jars in my project:
- swt and associated native library
- xswt.jar
- xmlpull_1_1_3_1.jar
- kxml2-min.jar


Regards,
Olivier Parisy.

Re: [Xswt-developer] XSWT wiki

[Olivier P. <ml....@fr...>]

David J. Orme a =C3=A9crit :
> Sourceforge changed their web infrastructure and made it impossible=
 to=20
> run the kind of Wiki I was running, so I took the content and moved=
 it=20
> to my blog.
>
> The home page is reachable from http://xswt.sourceforge.net and the=
n=20
> click the entries in the side bar.
OK. I was under the impression the the wiki contained more pages, tho=
ugh.

> If you have any questions, please ask here, we're small and somewha=
t=20
> quiet, but active. :-)
Thank you, I'd be pleased to! For now, the list archive fulfulled my =
needs.

Regards,
Olivier Parisy.

Re: [Xswt-developer] XSWT wiki

[David J. O. <dj...@co...>]

Sourceforge changed their web infrastructure and made it impossible to run the kind of Wiki I was running, so I took the content and moved it to my blog. 

The home page is reachable from http://xswt.sourceforge.net and then click the entries in the side bar. 

If you have any questions, please ask here, we're small and somewhat quiet, but active. :-) 


Regards, 

Dave Orme 

----- Original Message ----- 
From: Olivier Parisy <ml....@fr...> 
To: xsw...@li... 
Sent: Sunday, October 8, 2006 1:27:53 PM GMT-0600 
Subject: [Xswt-developer] XSWT wiki 

Hi all, 

I'm discovering XSWT, and reading any documentation I can find. 

The following Google search returns some hits about an xswt wiki : 
http://www.google.fr/search?hl=fr&lr=&q=+site:xswt.sourceforge.net++xswt+ProjectDocumentation 

But those links seems dead. Is this wiki still used, somewhere else perhaps? 

Best regards, 
Olivier Parisy. 

------------------------------------------------------------------------- 
Take Surveys. Earn Cash. Influence the Future of IT 
Join SourceForge.net's Techsay panel and you'll get the chance to share your 
opinions on IT & business topics through brief surveys -- and earn cash 
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV 
_______________________________________________ 
Xswt-developer mailing list 
Xsw...@li... 
https://lists.sourceforge.net/lists/listinfo/xswt-developer 

[Xswt-developer] XSWT wiki

[Olivier P. <ml....@fr...>]

Hi all,

I'm discovering XSWT, and reading any documentation I can find.

The following Google search returns some hits about an xswt wiki :
http://www.google.fr/search?hl=fr&lr=&q=+site:xswt.sourceforge.net++xswt+ProjectDocumentation

But those links seems dead. Is this wiki still used, somewhere else perhaps?

Best regards,
Olivier Parisy.

Re: [Xswt-developer] repository, stylesheets and data binding

[David J. O. <dj...@co...>]

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

[Xswt-developer] repository, stylesheets and data binding

[<ha...@id...>]

Hi,

Three topics today:

- CVS repository: I'm having problems connecting to the repository. I =
get a
server errer when trying to connect (happens for all CVS operations to
xswt.cvs.sourceforge.net).

- stylesheets: The current stylesheet mechanism allows an element to
reference another with the x:style attribute. First the control for the
element is created, then it is "filled" in with the style's attributes =
and
content, before its own attributes and content are used. This lets the =
style
provide a set of defaults. When experimenting with the stylesheet =
mechanism
I found that it could be useful for an element with a x:style attribute =
to
use the style's element instead of its own, when creating the control in =
the
first place. I.e. you could use <control x:style=3D"styles.labelStyle"/> =
to
create a label, if the styles.labelStyle refer to a label element. This
makes the x:style attribute be used more as an include than a defaulting
mechanism.

- data binding: I've been looking at the data binding packages and using =
it
for my own data flow model, lately. I've already become very fond of it, =
but
I'm worried since there's so many deprecated classes I need to use. I
understand they may be marked as such because the design hasn't been
completely settled, but would like ask (David) about the status of the
package, e.g. what parts can be relatively safely be used and what parts
that may be redesigned before becoming official.

Hallvard

P.S. I haven't looked at the editor, yet, but I'm becoming more =
interested
than before, since my own dialog modelling project now generates xswt =
files
that the developer would want to edit to fill in the details not covered =
by
the model.

---
Hallvard Tr=E6tteberg (ha...@id..., http://www.idi.ntnu.no/~hal)
Associate Professor, IS group, Dept. of Computer and Information =
Sciences at
the Norwegian Univ. of Science and Technology

Re: [Xswt-developer] FormToolkit

[David J. O. <dj...@co...>]

> you've done a great job. I'm really impressed. 

Thanks! 

> Theres just one thing I don't get. On the XSWT homepage is support for 
> FormToolkit mentioned and in the mailinglist archive is an example for 
> FormTookit, but I see no use of FormTookit in it and can't find any 
> example in the sourceforge CVS. 

Actually, the home page example is for the FormLayout layout manager. :-) We've discussed FormToolkit on the mailing list and one person has implemented it but was unable to get IP clearance to release the source code back to the project. So while FormToolkit doesn't look to be that hard to support, we don't support it yet. 


Best regards, 

Dave Orme 

[Xswt-developer] FormToolkit

[Markus W. <ma...@em...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi XSWT developers,

you've done a great job. I'm really impressed.
Theres just one thing I don't get. On the XSWT homepage is support for
FormToolkit mentioned and in the mailinglist archive is an example for
FormTookit, but I see no use of FormTookit in it and can't find any
example in the sourceforge CVS.
Is there another repository? Or is there a nightly build available to
see it in action?

Thanks
Markus Wolf
- --
>
> emedia-solutions wolf
> Wedeler Landstrasse 63
> 22559 Hamburg
> (040) 550 083 70
>
>>  web: http://www.emedia-solutions-wolf.de
>> mail: ma...@em...
>>  pgp: http://wwwkeys.de.pgp.net
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFG3lZeyJE91ndMG4RAqYjAJ9Exic3xn4NUwQr418q6q7Bl2qwVgCeKcoA
X7G3oTWIcR1OIcgj3S56TMk=
=Pm2B
-----END PGP SIGNATURE-----

Re: [Xswt-developer] Xswt-developer Digest, Vol 4, Issue 1

[<ha...@id...>]

> -----Original Message-----
> Raphael Bosshard wrote:
> Hello there,
>
> I know that XSWT is able to handle images. I saw Hans 
> Baiers Mail and the hint with ImageDataParser.

The ImageDataParser parses the syntax "<class> <class-relative-path>". E.g.
in the test project for XSWT I have a class named
com.swtworkbench.community.xswt.dataparser.DataParserTest and in the same
folder I have an image file named xswt.gif. In the test the string
"com.swtworkbench.community.xswt.dataparser.DataParserTest xswt.gif" is
correctly parsed as a reference to xswt.gif relative to the DataParserTest
class. In general, XSWT looks for the class and resolves the file relative
to the class. This means you must be careful with the folder classpath and
structure.

> Yet I'm unable to make it work.

What have you tried?

Hallvard

Re: [Xswt-developer] Images with XSWT

[David J. O. <dj...@co...>]

Hallvard, Yu, or Jan,

I can't answer this right now--we have a delivery next week.  Could one 
of you handle it please?


Thanks,

Dave Orme

Raphael Bosshard wrote:
> Hello there,
>
> I know that XSWT is able to handle images. I saw Hans Baiers Mail and 
> the hint with ImageDataParser. Yet I'm unable to make it work.
>
> Can someone point me to an example where I can find out how to do it?
>
>
> Thanks,
> Raphael
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Xswt-developer mailing list
> Xsw...@li...
> https://lists.sourceforge.net/lists/listinfo/xswt-developer
>