As of 2016-02-26, there will be no more posts for this blog. s/blog/pba/
Showing posts with label Java. Show all posts

A week ago, I removed all packages relating to Java from my system. I thought I had absolutely no need of them until I tried to minify CSS, via Makefile, using YUI Compressor which is written in Java. The same situation would have happened when I need to minify JavaScript files, I use Google Closure Compiler, same, written in Java.

Oh, right, thats why I still kept the Java runtime environment, the open source one, IcedTea, I thought to myself.

At this point, you can bet that I want to get rid of Java for real. For IcedTea binary package, its about 30+ MB plus near 9 MB of YUI Compressor and Google Closure Compiler. To be fair, they dont use a lot of space, but I just dont like to have Java on my system since there are only two programs need it. Besides, in order to have IcedTea installed, it pulls two virtual packages and two more packages for configurations.

So, my choice was to use online ones as I already know Google hosted one at http://closure-compiler.appspot.com/ and there is also a popular Online YUI Compressor hosted by Mike Horn.

Its only a matter of commands for achieving Java-less, using curl, first one is for YUI Compressor, second one is for Google Closure Compiler:

curl -L -F type=CSS -F redirect=1 -F 'compressfile[]=input.css; filename=input.css' -o output.min.css http://refresh-sf.com/yui/
curl --data output_info=compiled_code --data-urlencode js_codeinput.js http://closure-compiler.appspot.com/compile > output.min.js

Replace the input and output filenames for yours. If you need to pipe, then use - instead of inputfile, - indicates the content comes from standard input.

Although YUI Compressor can also minify JavaScript, however I found Google Closure Compiler does better job by only a little. If you use YUI Compressor for JavaScript as well, simply change to type=JS.

Both (Online) YUI Compressor and Google Closure Compiler have some options, you can simply add to the command. It shouldnt be hard since you have a command template to work from. I only use the default compression options, they are good enough for me.

I have upgraded to Fedora 10 with DVD. Honesty, I don't feel many changes. The booting process has a little bit different. It's now always in graphical mode but still the same text-mode message (I don't use RHGB), that looks great. The logging-in sound is different.



The problems I have:

  • If enable gcin (an input method editor) in IM Chooser, system will extremely slow response.


  • Woopra client doesn't run well, it hangs. Could be a Java problem.

  • Flash (64 Bit) doesn't render well.

  • Saw a message "Could not detect stabilization, waiting 10 seconds." at booting, not sure what does that mean. After searched, I got this thread.


  • Amarok is 1.94, but UI has big problem and it can't play.


I ran yum to check if there is updates and hoped they would fix the problems above. I need to disable few repos, e.g. freshrpms and jpackage. Right now, I have 143 updates about 203 MB. After updated, those problems remain.



I am trying to resolve:

  • freshrpms is ready for Fedora 10.


Updated on 2008-11-27



After a day, I still didn't see anyone has same problems as I have. I decided to do a fresh installation, yea, I don't have much patience. I think all problems are caused by very fundamental thing but I don't know what it is.



Post closed.

Firstly, I only took 9 days to get approved by Woopra, some posts on the forums say that may take weeks.



Installing Woopra on Linux is simple and it is a graphical process. Look at the screenshot below.

You can download the installer here and install it with sh woopra.sh. I installed it at my home pathes: /home/username/lib/Woopra for Woopra program, and /home/username/bin for symbolic link.



When I tried to run it, I got an error:

 
My JRE is from Sun and it's 64 Bit, you can check yours by running java -version, which outputs like:

java version "1.6.0_06"

Java(TM) SE Runtime Environment (build 1.6.0_06-b02)

Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode)
The solutions are two, both are easy. First one is to remove sun-java6-bin package and install ia32-sun-java6-bin package.



Second one is easy, too, and better. Install ia32-sun-java6-bin package, first. Then test with this newly install 32 bit JRE with

INSTALL4J_JAVA_HOME_OVERRIDE=/usr/lib/jvm/ia32-java-6-sun/jre Woopra
This forces the startup script, /home/username/bin/Woopra in my case, to use specified Java JRE not the one that it can find on your system.



Once Woopra runs successfully and with no error, close it. Find the startup script, if you don't know where it is, you can run whereis Woopra or type Woopra (in Bash). If none of both get result, use find / -name Woopra.



Find it, and open it with editor, and put the following line at second line (an empty line):

INSTALL4J_JAVA_HOME_OVERRIDE=/usr/lib/jvm/ia32-java-6-sun/jre
Now, simply run Woopra in terminal or from main menu.



Here is a screenshot after logging in:

Subscribe to: Posts (Atom)