Exception in thread “main” java.lang.UnsatisfiedLinkError: /…/gwt-linux-1.7.0/libswt-pi-gtk-3235.so: /…/gwt-linux-1.7.0/libswt-pi-gtk-3235.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
To solve the problem, install a 32bit version of jre
sudo aptitude install ia32-sun-java5-bin
Then follow the steps
Also install a 32-bit JVM; you can download directly from Sun and install somewhere on your system http://java.sun.com/javase/downloads/index.jsp
Register this JVM with Eclipse: Windows -> Preferences Java -> Installed JREs Add… -> (Use a name like “jdk1.6.0_07 32-bit”)
Modify your *.launch files to explicitly use a 32-bit JRE Run -> Run Configurations… Java Application -> (Your launch config) JRE -> Alternate JRE -> (select 32-bit JVM setup in previous step)
Modify your “-shell” scripts to explicitly use the 32-bit JVM. Your “-compile” scripts can continue to use the default 64-bit Java
(see also http://code.google.com/p/google-web-toolkit/issues/detail?id=134#c39 )
]]>more at http://www.techieblogger.com/2009/09/online-image-editing-tools-websites.html
this is probably the best https://www.photoshop.com/
]]>In order to set environment variables in a way that effects a user’s entire desktop session, one may place commands to set their values in one of the “hidden” script files in the user’s home directory. The more common such files are outlined below.
~/.profile - This is probably the best file for placing environment variable assignments in, since it gets executed automatically by the DisplayManager during the startup process desktop session as well as by the login shell when one logs-in from the textual console.
~/.bashprofile or ~./bashlogin - If one of these file exist, bash executes it rather then “~/.profile” when it is started as a login shell. (Bash will prefer “~/.bashprofile” to “~/.bashlogin”). However, these files won’t influence a graphical session by default.
~/.bashrc - Because of the way Ubuntu currently sets up the various script files by default, this may be the easiest place to set variables in. The default configuration nearly guarantees that this file will be executed in each and every invocation of bash as well as while logging in to the graphical environment. However, performance-wise this may not be the best thing to do since it will cause values to be unnecessarily set many times.
Environment variable settings that effect the system as a whole (rather then just a particular user’s desktop session) can be placed in any of the many system-level scripts that get executed when the system or the desktop session are loaded. Ubuntu defines several locations dedicated to placing such settings:
/etc/profile - This file gets executed whenever a bash login shell is entered (e.g. when logging in from the console or over ssh), as well well as by the DisplayManager when the desktop session loads. This is probably the file you will get referred to when asking veteran UNIX system administrators about environment variables. In Ubuntu, however this file does little more then invoke the /etc/bash.bashrc file.
/etc/bash.bashrc - This is is the system-wide version of the ~/.bashrc file. Ubuntu is configured by default to execute this file whenever a user enters a shell or the desktop environment.
/etc/environment - This file is specifically meant for system-wide environment variable settings. It is not a script file, but rather consists of assignment expressions, one per line. Specifically, this file stores the system-wide locale and path settings.
See also
]]>If your running Ubuntu Server Edition you can install a KDE or Gnome graphical desktop with a couple of apt installation. For a bare minimal install, you will be able to login to a full desktop with one of the following:
sudo apt-get install gnome-core
sudo apt-get install kde-core
For a baseline set of package you can install the following:
sudo apt-get install gnome
sudo apt-get install kde
For the entire package set released with either Kubuntu or Ubuntu you can install:
sudo apt-get install ubuntu-desktop
sudo apt-get install kubuntu-dekstop
These commands will install all the files associated with the default graphical desktop that comes with either Ubuntu or Kubuntu.
See also
]]>| Properties | Description |
|---|---|
|
We will use the URL "http://www.mysite.com/good.htm#section2" as basis below to explain the various properties. |
|
| hash | Specifies the anchor portion of the URL, including the leading hash. (ie: "#section2"). |
| host | Specifies the hostname and port (if available) of a URL. (ie: "www.mysite.com" or "www.mysite.com:563"). |
| hostname | Specifies the hostname portion of the URL (ie: "www.mysite.com"). |
| href | Specifies the entire URL. |
| pathname | Specifies the path name of the URL (ie: "/good.htm"). |
| port | Specifies the port portion of the URL (ie: "563" within the host "www.mysite.com:563"). |
| protocol | Specifies the protocol portion of the URL, including the trailing colon (ie: "http:" or "https:"). |
| search | Specifies the query portion of the URL, including the question mark (ie: "?sort=alpha") |
URL示意
<protocol>//<hostname>[:<port>]/<pathname>[<search>][<hash>]
方法
| Methods | Description |
|---|---|
| reload([forceGet]) | Reloads the current document. If "forceGet" set to true, document is completely reloaded even if server reports it hasn’t been modified since last reload. Default is false. |
| replace(url) | Loads the specified URL over the current history entry. Example(s) |
ApplicationContext context = WebApplicationContextUtils.getWebApplicationContext(getServletContext());
Object myDao = context.getBean(“daoBeanName”);
参见
]]>Maven
]]>Read these, and be armed with another javascript extension.
MAYSCRIPT is not required for ie 8 and firefox 3 to allow applet to access js. While it is for opera. See Google result on “Applet not allowed to access javascript”
]]>