|
|
|
|
|
|
|
| Re: 3.1RC3: Run As -> SWT Application [message #457210 is a reply to message #457190] |
Tue, 21 June 2005 17:04   |
Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
This seems a big step backward in usability. :(
Bob
Veronika Irvine wrote:
> Instead of using Run As SWT... you can do one of the following:
>
> A) Using SWT for standalone applications
>
> Download SWT for standalone applications. A standalone version of SWT is
> available on the same download page as the Eclipse SDK. Look for the section
> titled SWT Binary and Source. Do not extract the archive file, just save it
> to
> disk.
> Select Import... from the File menu.
> Select Existing Projects into Workspace and click on the Next button.
> Select Select archive file: and use the Browse button to locate the SWT
> standalone archive you have previously downloaded.
> Click on the Finish button.
> Add org.eclipse.swt to your project java build path.
>
> B) Using SWT that is shipped with Eclipse
>
> Select "Import..." from the File menu.
> Select "External Plug-ins and Fragments" in the Import wizard and click
> on the "Next" button.
> Select "Import As Binary projects" and make sure the target platform is
> correct. Click on the "Next" button.
> Select org.eclipse.swt and org.eclipse.swt.<ws>.<os>.<arch> and click
> on the "Add" button.
> (<ws>, <os>, and <arch> should be replaced with the values for the
> platform you wish to run against. e.g. org.eclipse.swt.gtk.linux.x86)
> Click on the "Finish" button.
> Select org.eclipse.swt in the Package Explorer. From the right mouse
> menu, select "Properties".
> Click on "Java Build Path" and then click on the "Libraries" tab.
> Click on the "Add Jars..." button.
> Select
> org.eclipse.swt.<ws>.<os>.<arch>/org.eclipse.swt.<ws>. <os>.<arch>_3.1.0.jar
> and click on the "OK" button.
> Expand org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar in the Libraries tab
> and select "Native library location".
> Click on the "Edit..." button.
> Click on the "Workspace..." button in the "Native Library Folder
> Configuration" dialog.
> Select org.eclipse.swt.<ws>.<os>.<arch> and click on the "OK" button.
> Click on the "OK" button in the "Native Library Folder Configuration"
> dialog.
> Click on the "Order and Export" tab in the "properties for
> org.eclipse.swt" dialog.
> Place a check against org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar.
> Click on the "OK" button.
> Add org.eclipse.swt to your project java build path.
>
>
> "Christian Hauser" <c.hauser@active.ch> wrote in message
> news:d97508$5uc$1@news.eclipse.org...
>
>>Hello
>>
>>I'm missing the SWT launcher (Run As -> SWT Application) since Eclipse
>>3.1RC3 to easily start SWT applications.
>>
>>Could someone please point me to the related bug number or an official
>>statement as to why this IMHO very useful feature has been removed?
>>
>>Thanks for any hint,
>> Christian
>
>
>
|
|
|
|
|
| Re: 3.1RC3: Run As -> SWT Application [message #457225 is a reply to message #457190] |
Tue, 21 June 2005 22:49 |
| Eclipse User |
|
|
|
Originally posted by: nospam.nospam.no
"Veronika Irvine" <veronika_irvine@oti.com> wrote in message
news:d977d7$8t5$1@news.eclipse.org...
> Instead of using Run As SWT... you can do one of the following:
> (very long recipe)
Why on earth would you think it is a good idea (or even user friendly) to
replace "Run As - SWT application" with such a enormously long and
complicated recipe?
Will users have to wait until Eclipse 3.2 in order to easily run SWT
applications again ?
|
|
|
| Re: 3.1RC3: Run As -> SWT Application [message #457293 is a reply to message #457190] |
Wed, 22 June 2005 19:40 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
+1 for having it back or (better) providing generic wizard for setting a
classpath libs from existing platform plugins.
Veronika Irvine wrote:
> Instead of using Run As SWT... you can do one of the following:
>
> A) Using SWT for standalone applications
>
> Download SWT for standalone applications. A standalone version of SWT is
> available on the same download page as the Eclipse SDK. Look for the section
> titled SWT Binary and Source. Do not extract the archive file, just save it
> to
> disk.
> Select Import... from the File menu.
> Select Existing Projects into Workspace and click on the Next button.
> Select Select archive file: and use the Browse button to locate the SWT
> standalone archive you have previously downloaded.
> Click on the Finish button.
> Add org.eclipse.swt to your project java build path.
>
> B) Using SWT that is shipped with Eclipse
>
> Select "Import..." from the File menu.
> Select "External Plug-ins and Fragments" in the Import wizard and click
> on the "Next" button.
> Select "Import As Binary projects" and make sure the target platform is
> correct. Click on the "Next" button.
> Select org.eclipse.swt and org.eclipse.swt.<ws>.<os>.<arch> and click
> on the "Add" button.
> (<ws>, <os>, and <arch> should be replaced with the values for the
> platform you wish to run against. e.g. org.eclipse.swt.gtk.linux.x86)
> Click on the "Finish" button.
> Select org.eclipse.swt in the Package Explorer. From the right mouse
> menu, select "Properties".
> Click on "Java Build Path" and then click on the "Libraries" tab.
> Click on the "Add Jars..." button.
> Select
> org.eclipse.swt.<ws>.<os>.<arch>/org.eclipse.swt.<ws>. <os>.<arch>_3.1.0.jar
> and click on the "OK" button.
> Expand org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar in the Libraries tab
> and select "Native library location".
> Click on the "Edit..." button.
> Click on the "Workspace..." button in the "Native Library Folder
> Configuration" dialog.
> Select org.eclipse.swt.<ws>.<os>.<arch> and click on the "OK" button.
> Click on the "OK" button in the "Native Library Folder Configuration"
> dialog.
> Click on the "Order and Export" tab in the "properties for
> org.eclipse.swt" dialog.
> Place a check against org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar.
> Click on the "OK" button.
> Add org.eclipse.swt to your project java build path.
>
>
> "Christian Hauser" <c.hauser@active.ch> wrote in message
> news:d97508$5uc$1@news.eclipse.org...
>
>>Hello
>>
>>I'm missing the SWT launcher (Run As -> SWT Application) since Eclipse
>>3.1RC3 to easily start SWT applications.
>>
>>Could someone please point me to the related bug number or an official
>>statement as to why this IMHO very useful feature has been removed?
>>
>>Thanks for any hint,
>> Christian
>
>
>
|
|
|
| Re: 3.1RC3: Run As -> SWT Application [message #457294 is a reply to message #457293] |
Wed, 22 June 2005 19:59 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
BTW, osgi spec provides the way to load native libraries. Why I dont see
this in current SWT plugin manifests? It also can be nicely fragmented
depending on OS...
Thx,
Alex.
Alexander Smirnoff wrote:
> +1 for having it back or (better) providing generic wizard for setting a
> classpath libs from existing platform plugins.
>
>
> Veronika Irvine wrote:
>
>> Instead of using Run As SWT... you can do one of the following:
>>
>> A) Using SWT for standalone applications
>>
>> Download SWT for standalone applications. A standalone version of SWT is
>> available on the same download page as the Eclipse SDK. Look for the
>> section
>> titled SWT Binary and Source. Do not extract the archive file, just
>> save it to
>> disk.
>> Select Import... from the File menu.
>> Select Existing Projects into Workspace and click on the Next button.
>> Select Select archive file: and use the Browse button to locate the SWT
>> standalone archive you have previously downloaded.
>> Click on the Finish button.
>> Add org.eclipse.swt to your project java build path.
>>
>> B) Using SWT that is shipped with Eclipse
>>
>> Select "Import..." from the File menu.
>> Select "External Plug-ins and Fragments" in the Import wizard and click
>> on the "Next" button.
>> Select "Import As Binary projects" and make sure the target platform is
>> correct. Click on the "Next" button.
>> Select org.eclipse.swt and org.eclipse.swt.<ws>.<os>.<arch> and click
>> on the "Add" button.
>> (<ws>, <os>, and <arch> should be replaced with the values for the
>> platform you wish to run against. e.g. org.eclipse.swt.gtk.linux.x86)
>> Click on the "Finish" button.
>> Select org.eclipse.swt in the Package Explorer. From the right mouse
>> menu, select "Properties".
>> Click on "Java Build Path" and then click on the "Libraries" tab.
>> Click on the "Add Jars..." button.
>> Select
>> org.eclipse.swt.<ws>.<os>.<arch>/org.eclipse.swt.<ws>. <os>.<arch>_3.1.0.jar
>>
>> and click on the "OK" button.
>> Expand org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar in the Libraries tab
>> and select "Native library location".
>> Click on the "Edit..." button.
>> Click on the "Workspace..." button in the "Native Library Folder
>> Configuration" dialog.
>> Select org.eclipse.swt.<ws>.<os>.<arch> and click on the "OK" button.
>> Click on the "OK" button in the "Native Library Folder Configuration"
>> dialog.
>> Click on the "Order and Export" tab in the "properties for
>> org.eclipse.swt" dialog.
>> Place a check against org.eclipse.swt.<ws>.<os>.<arch>_3.1.0.jar.
>> Click on the "OK" button.
>> Add org.eclipse.swt to your project java build path.
>>
>>
>> "Christian Hauser" <c.hauser@active.ch> wrote in message
>> news:d97508$5uc$1@news.eclipse.org...
>>
>>> Hello
>>>
>>> I'm missing the SWT launcher (Run As -> SWT Application) since
>>> Eclipse 3.1RC3 to easily start SWT applications.
>>>
>>> Could someone please point me to the related bug number or an
>>> official statement as to why this IMHO very useful feature has been
>>> removed?
>>>
>>> Thanks for any hint,
>>> Christian
>>
>>
>>
>>
|
|
|
|
| Re: 3.1RC3: Run As -> SWT Application [message #457356 is a reply to message #457354] |
Thu, 23 June 2005 20:35 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
Look into paragraph 4.6 OSGi service platform release 3 spec. Exerpt:
"If a bundle has a Bundle-NativeCode manifest header, the bundle should
contain native code libraries that must be available for the bundle to
execute. When a bundle makes a request to load a native code library,
the findLibrary method of the caller's classloader must be called to
return the file path name in which the Framework has made the requested
native library available."
This is how it should look in manifests:
"Bundle-NativeCode: /lib/http.DLL;/lib/zlib.dll ;
osname = Windows95 ;
osname = Windows98 ;
osname = WindowsNT ;
processor = x86 ;
language = en ;
language = se ,
/lib/solaris/libhttp.so ;
osname = Solaris ;
osname = SunOS ;
processor = sparc,
/lib/linux/libhttp.so ;
osname = Linux ;
processor = mips"
The question is: why it is not implemented/used in Eclipse?
Veronika Irvine wrote:
> Can you please elaborate on how OSGI supports native libraries?
>
> "Alexander Smirnoff" <alexsmr@NOJUNK.sympatico.ca> wrote in message
> news:d9cfv5$90f$1@news.eclipse.org...
>
>>BTW, osgi spec provides the way to load native libraries. Why I dont see
>>this in current SWT plugin manifests? It also can be nicely fragmented
>>depending on OS...
>>
>>Thx,
>>Alex.
>>
>
>
|
|
|
|
|
| Repost: SWT plugin does not uses OSGi native capability [message #457442 is a reply to message #457356] |
Fri, 24 June 2005 20:59 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.NOJUNK.sympatico.ca
I found why it was not used at least prior to M7: see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=90066
But now it works and it is possible to build single SWT plugin (OK, it
will weight 2-3M more) without OS depending counterparts fragments. But
the benefits:
- simplified deployment
- true multi platform (just copy & run) for Eclipse/RCP
- hided platform complexities of SWT
- shared network installations that can be run from many platforms
Do you have a plans/discussions/proposals for actually using this?
Thanks,
Alex
Alexander Smirnoff wrote:
> Look into paragraph 4.6 OSGi service platform release 3 spec. Exerpt:
>
> "If a bundle has a Bundle-NativeCode manifest header, the bundle should
> contain native code libraries that must be available for the bundle to
> execute. When a bundle makes a request to load a native code library,
> the findLibrary method of the caller's classloader must be called to
> return the file path name in which the Framework has made the requested
> native library available."
>
> This is how it should look in manifests:
>
> "Bundle-NativeCode: /lib/http.DLL;/lib/zlib.dll ;
> osname = Windows95 ;
> osname = Windows98 ;
> osname = WindowsNT ;
> processor = x86 ;
> language = en ;
> language = se ,
> /lib/solaris/libhttp.so ;
> osname = Solaris ;
> osname = SunOS ;
> processor = sparc,
> /lib/linux/libhttp.so ;
> osname = Linux ;
> processor = mips"
>
> The question is: why it is not implemented/used in Eclipse?
>
> Veronika Irvine wrote:
>
>> Can you please elaborate on how OSGI supports native libraries?
>>
>> "Alexander Smirnoff" <alexsmr@NOJUNK.sympatico.ca> wrote in message
>> news:d9cfv5$90f$1@news.eclipse.org...
>>
>>> BTW, osgi spec provides the way to load native libraries. Why I dont
>>> see this in current SWT plugin manifests? It also can be nicely
>>> fragmented depending on OS...
>>>
>>> Thx,
>>> Alex.
>>>
>>
>>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03890 seconds
] 
Search
Help
Register
Login
Home
