Messages

31

Zaurus - pdaXrom / Xfce4 Finetuning

« on: October 18, 2005, 07:15:51 am »

I have written a script that can move the panel between the bottom and the right hand side.  I just need to integrate it with the rotate script and this will be done.

If someone could explain how the function keys and other events work, I could try and fix some of those as well.

32

Zaurus - pdaXrom / Xfce4 Finetuning

« on: October 15, 2005, 10:43:03 pm »

I am really enjoying xfce4.

I would like to make the rotation work better:

- It does not rotate when I switch from portait to landscape

- It would be cool if I had the option to move the panel to the right side when I rotate (it is too long to work well on the bottom)

If someone is knowledgeable enough to tell me how to do these things/ I can write the scripts myself.

Thanks.

33

5x00 Hardware / Streaming Video (tv)

« on: October 15, 2005, 10:22:50 pm »

If you put your video file in a directory accessible through your web server/ you don't need vlc on the server.  You can use mplayer on the client and access the video file over http.

34

Zaurus - pdaXrom / Nxrun

« on: October 14, 2005, 05:09:46 pm »

Did you see my notes above?  How far did you get?

35

Zaurus - pdaXrom / Nxrun

« on: October 14, 2005, 02:05:13 pm »

Ok - Here is a quick how-to that I hope will allow someone other than me to use nx.

1.  Getting the gui working
   a.  You need a few python files in addition to nxrun-gui.py.  I am attaching them here: subprocess.py and pickle.py.  NOTE: I had to change the extensions to upload them so you need to change them from .txt to .py.  All of these files should be placed in /usr/NX/bin
   b.  You need to create the config directory.  mkdir /usr/NX/bin/config/

2.  You need to export a HOSTNAME variable or else it fails.  I will change this code to use a default in the future.  For now, you need to export HOSTNAME="zaurus" or something similar

3.  You need to have the client authentication key.  I have attached the standard nomachine client key.   NOTE: I had to change the extension to upload it so you need to change it from .txt to .key. It needs to be placed in /usr/NX/share/client.id_dsa.key

4.  You should ssh into your server at least once before attempting to connect.  There is code that is supposed to intercept the warning when you connect to a new server and agree to add the key.  This is not working consistently so it is better to check yourself.

5.  Once you have this done you can start the gui ./nxrun-gui.py.  If you are familiar with the nomachine client you should know how it works.  There is a tutorial on linuxjournal.com right now that may help.  Just type the name of a config into the Service entry field and hit Configure...  When you are prompted, select the Create button and create a new configuration.

6.  If you are having trouble, use nxrun directly and post the log file.  You can type nxrun config/<your session name>.conf  -i -fide.  This will create nxcompsh.log with all the details.

36

Zaurus - pdaXrom / Nxrun

« on: October 13, 2005, 07:23:23 am »

Thanks to pgas!

I have used these binaries to successfully connect to some nx servers!

I definitely need to write a how-to because there were some tweaks I had to make to get it going.

I will post the steps here soon.

Also, I had trouble connecting to a 1.5.0 nomachine server, but it worked fine against a couple of 1.4.x FreeNX servers.  I will try and track the issue down.

Thanks again for your help!

37

General Discussion / Please Help!

« on: August 30, 2005, 05:21:05 pm »

I thought I had this problem one time.  It turned out that I had not slid the battery lock all the way over.  It acted completely dead.  Once I clicked it into place, it worked fine.

I hope your problem is this simple.

38

Zaurus - pdaXrom / Compiling Apache

« on: August 30, 2005, 03:04:17 pm »

Just curious - who cares about buffer overflows on their Z?  I wouldn't think you would use it for a public website.  I don't think security would be an issue.

Maybe stability would be a problem?

39

Zaurus - pdaXrom / Nxrun

« on: August 22, 2005, 07:43:17 pm »

Sounds like some good progress!

They have switched the server over to svn, but all my client stuff is still in cvs.

There is another python client in svn but it is incomplete and does not use the nxdriver library that implements most of the protocol.  I have never looked at it but it may be interesting.

40

Zaurus - pdaXrom / Nxrun

« on: August 22, 2005, 04:42:49 pm »

Hey, Jason.  Good to here from you.  I hope the girls are doing well.

The main info on compiling the core nx client libraries are here:

http://web01.nomachine.com/documentation/b...-components.php

We need:

nxssh
nxcomp
nxproxy

Then, you need the nxc libraries:

nxcompsh
nxdriver
nxrun

These files are in CVS on the freenx site.  The gui can also be downloaded there.

freenx.berlios.de

The nxc components and the NX libraries are not linked together so they can be built separately.

- L

41

Zaurus - pdaXrom / Nxrun

« on: August 22, 2005, 09:04:47 am »

Now with a gui!

I have posted nxrun-gui.py on the freenx website.  It is a gui that mimics the main features of the NXClient gui.

I know it runs on pdaxrom because I wrote it on my zaurus.

This is a *bump*.  I am still looking for someone who has experience compiling for pdaxrom to compile the client.

42

Zaurus - pdaXrom / Killer Applications For Pdaxrom

« on: August 22, 2005, 08:25:36 am »

I rarely use firefox to browse on my zaurus - way too slow.

I use dillo for anything that will render.

Most of the time, I ssh -X into one of my linux boxes and run firefox off of it remotely.  The performance is much better than running firefox locally.

I like TuxCards as a hierarchical notes application.

I use python/pygtk for development.  the SciTE editor is pretty basic but it does syntax highlighting.  Most of the time I just use vi.  

mxrvt is a good terminal application because it supports multiple tabs (but the transparency doesn't work).

43

Zaurus - pdaXrom / Keep Pdaxrom Alive

« on: August 18, 2005, 08:06:47 am »

TheWalt makes all very good points.

I suggested bounties as an additional process in addition to contributing to the core ROM.

I suggested it because as an open source developer I like bounties.  it gives me an incentive but also a choice.  I don't have to go for the bounty but if I do then I get the incentive.  Or maybe someone else will and that is just as good.  It doesn't put money in my pockets but it advances the software.

I also think that setting up a process where other developers (as you suggest) can fill in the blanks around the ROM would help stimulate the community (though as omro says it doesn't help Sash pay the bills).

For those of you who haven't maintained an open source project, you don't realize the constant barrage of requests.  Some come on the forums or mailing lists but often they are just emails that say someone can't compile or ask if it is possible to add some feature.  Many of these people never contribute and when you help them change the code half the time they go away and never even provide patches back.  You need to have the flexibility to work on your own vision or else you just end up in support mode all the time.

44

Zaurus - pdaXrom / Keep Pdaxrom Alive

« on: August 17, 2005, 12:44:37 pm »

A ROM is not just the sum of a bunch of individual requests.  The developers should have flexibility in how the ROM develops.

I would propose two ways to contribute:

- A general contribution with the ability to indicate what features are a priority to you

- A bounty system where users commit that if certain features are implemented - by the core team or others - they will pay out the bounty.

45

Zaurus - pdaXrom / Treeline

« on: August 10, 2005, 04:20:15 pm »

I should say thank you!