Notices

the dogs bollocks.. I havn't heard that in years.. I used to be on the litestep development team, and most of the guys where from england/Australia/
Sweden.. only a few of us State side guys. They used to say bollocks and dogs bollocks all the time. I had to ask my wife, who lived in england for years, what it meant.. thats was funny

Hello,
just wondering: Would the WM install work on IT2005? At least in principle?
I'd be really interested to install the Citrix client on my N770. As far as I've heard the Citrix client cannot be installed on IT2006 or above due to EABI compatibility issues.
Cheers, VolX_G.

Hello... I got my install working. Love the app... thanks. Here is my question:

There is an application that I would like to install on the n800. It is in arm.deb format. How would I go about installing it? I get a message that package architechure (arm) does not match systems (armel).

Thanks
Michael

Thanks man, that is a real great proof of concept!

Works great on the 770, but i first had to reboot into WM to make ist work.

Now i need to recompile stuff...theres no excuse left for not "porting" apps to my 770

Hi,
sorry, it won't work. it has to be recompiled. Nokia changed in second (i think) OS 2006 Release the binary format.
Maybe there is already a armel version of your app floating around?

Rachid

Okay, I've tried this for fun on my 770, and it *is* fun, althought it only "sort of" works for me... I'd never used this window manager before, so maybe I'm just not understanding or doing things right.

Install went well. I can reboot to WM or Hildon without any problems, but the Hildon menu command "switch to WM" leads to a white screen as mentioned here by others. I couldn't conclude from the discussion in this thread if this is supposed to work (and how), or if it's broken and must not be used for the time being ?

When I'm in WM mode I can play around with the icons, but I have two problems :

- I can launch the virtual keyboard, but silly me can't figure how to direct its input to the current window, so no typing yet :-)

- the xterm item in the main menu doesn't work ("program not found" or something), so even if I could type I wouldn't know how to launch all those other applets I installed from the second tar file...

If I'm missing something simple and obvious, please lead me to enlightenment ! (yes, pun intended :-)

PS: one thing is already clear though - the WM interface feels incredibly "snappy" and fluid compared to to Hildon's sluggishness...

Thanks for the fun penguinbait !

fpp, did you install the missing library the other user posted as missing for the 770? This may be why xterm will not work.

Additionally anyone who can not switch to the WM back and forth from the menus. Check your sudoers file, did you update this as stated in the install instructions? I have not had any problems switching back and forth, some others have and some others have not?

The wmapps can be launched from the command line. Once they are launched, WM will bring them back when you login again, This may be a problem inside WM if your xterm is not working. First you must fix your library problem.

Login to hildon and run osso-xterm, then try to run xterm inside osso-xterm, just type xterm and hit enter, if you are missing a lib it will tell you what it is, if xterm is not in your path it will fail, with command not found

Sorry I have not spent anytime on this, I am working on other fun stuff. I was able to get gnome session, panel, desktop, games, but still many issues. This runs so nice though, we need some development done. I see no reason we could not have Gnome and KDE available for maemo. That being said, they have to run from MMC/SD, compiling QT and kdelibs alone were 400MB, Gnome was a bit smaller. At this point I am continuing to try to complete compilation of a full featured window manager/desktop environment. But errors fly constantly, imake issues, x header issues. I considered trying to setup qt-embedded, but with no X it is very limiting.

Oh, right. I read this entire thread a dozen times and managed to miss that one.

xterm is in the path, but is missing libSM.so.6. He (eggsy) doesn't say where he found it though... I don't have connectivity here, will look around at home tonight.

I wonder if this is related to the switching from menus problem ? I do have the modified sudoers. And when I run swm.sh from xterm I get the exact same messsage as midiwall and the others (matchbox still running, or restarted).

Great work on this penguinbait - and others - and good luck on the gnome part. I personally think KDE and maybe even Gnome is too bloated for it to be any good on low-end hardware. However, I used to play around with a windowmanager called 'blackbox' (out of development methinks, but think 'fluxbox' took over) for low-end systems, and it works great. It starts up so fast with such a nice minimal panel, that I actually missed it the first time and though X had crashed on me - and this was on a P166!

So, if you want to play around with something really fast and still compatible take a look at *box - hosted at sourceforge AFAIR.

For the more adventurous, you should look into Enlightenment - it is designed, bottom up to be scalable all the way to cell-phones and their limited hardware, as well as having enough eye-candy to rival MacOS X. It is a windowmanager, but also a large backing of libraries, that are extremely optimized. Even though it is a developer release still, DR17 runs quite stable and extremely fast on my Gentoo laptop. DR16 is already available for ARM on Debian:

http://packages.debian.org/cgi-bin/s...=enlightenment


Once I get my own N800 I will look into compiling at least a *box flavor to it, and maybe take a brief excursion into Enlightenment.

OK, I got ask 166? Libretto?

I had a libretto, 166mmx :-) ran Window Maker great, that was my reason for wanting to set it up on maemo. WM is very fast, and works really well on this hardware. I agree with the bloated gnome/kde, but I still want to get it going.

What I do have working in gnome runs really well, without killing the CPU. I was very surprised at this. It does take longer to boot with gnome though, I had to go into R&D mode and turn off lifeguard reset, this allowed the extra time needed to start gnome up on boot. But it boots up to gnome.