New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

Eclipse w Ubuntu Karmic Koala - problem z przyciskami.

By K -
Po uaktualnieniu systemu do wersji Karmic Koala Eclipse zaczęło sprawiać problemy:
1: Nie były wyświetlane ikony
2: Kliknięcie na przyciski np. w opcjach, albo oknie instalacji wtyczek nie powodowało ich wywoływania. Krótko: przyciski nie działały.

Rozwiązania:
1: Gnome domyślnie wyłącza ikony menu oraz przycisków. Należy włączyć wyświetlanie ikon Gnome.
Jeśli ktoś radzi sobie z angielskim to można poczytać tutaj: http://www.omgubuntu.co.uk/2009/10/missing-system-icons-ubuntu-karmic.html
Jest to jednak zarówno proste jak i dość zrozumiałe jak już zrozumie się problem. Ja z początku obwiniałem proces aktualizacji.

2: Winne jest samo Eclipse 3.5, w nowszej wersji 3.6 powinno już być wszystko w porządku. Jeśli ktoś jak ja uruchamia Eclipse z dodatkowego pliku eclipse.sh należy dodać do niego dodatkową linijkę: export GDK_NATIVE_WINDOWS=1

Tak więc całość tego pliku powinna wyglądać np. tak: 

 #!/bin/sh 
 	export GDK_NATIVE_WINDOWS=1 	/opt/eclipse-3.5/eclipse
Ostatnia linijka oczywiście musi się odnosić do pliku/folderu gdzie masz zainstalowanego Eclipse w systemie.

Rozwiązanie znalezione : http://www.norio.be/blog/2009/10/problems-eclipse-buttons-ubuntu-910

Posted via email from krzychukula's posterous

Comments

  1. AnonymousNovember 16, 2009 at 6:35 PM

    Dzięki, drugi problem był strasznie wkurzający :))

    ReplyDelete

Post a Comment

Comments:

Popular posts from this blog

How to use NPM packages from private repositories on bitbucket

By K -
Image
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Read more

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Read more