[vidalia-users] Vidalia and IRIX

[Matthew Saunier]

	Hello, all. I've been working on porting Vidalia to IRIX, and have a  
patch that allows Vidalia to compile with MIPSPro.

	It turns out to be pretty trivial, there's one spot where a variable  
is redeclared in a foreach, which was no good - the fix there was to  
change the variable name in the foreach. The other issue is that  
SGI's math library handles floor differently, so I had to change  
floor to trunc in the 4 places where it's used.

	The larger issue is that while Vidalia compiles and runs, our window  
manager, 4Dwm, is pretty close to being plain X11, and as such has no  
concept of a notification area. I've poked around some, and it looks  
like Vidalia wants to minimize to the tray / dock upon startup. The  
result is that while any initial dialogs (could not connect to Tor,  
etc) pop up and Vidalia starts Tor properly, there's no way to get to  
the GUI. Our Qt implementation simply gets rid of the window, with no  
way to get it back.

	I think that the hack for this is to hard-set the "Show this window  
on start" pref in the code that reads the preferences, but the proper  
solution would be either to check the host type for IRIX at startup  
and have an if-then at every point in the code that minimizes to the  
notification area , or to add the option when Vidalia is invoked from  
the commandline while it is already running to connect to the  
existing instance. In other words, change the window from "There is  
another instance of Vidalia running, are you sure you want to start  
another one?" to  "There is another instance of Vidalia running, do  
you want to start another one or do you want to connect to the  
running instance?", which would send a signal to the running Vidalia  
to pop up the GUI. (Sidebar: Is SIGHUP used in Vidalia? That'd seem  
to be a logical choice...)

	Anyway, I don't know if this is the right place to discuss code  
changes - if it isn't, let me know. I'd like to join as a  
contributor, but all I'd want to do is get it running properly on  
IRIX and test new releases. The patch I've put together is quite  
harmless, I don't see any reason why it couldn't be added to the  
codebase. Of course, I also don't have a Linux box to test it on,   
and it doesn't solve any usability problems, just compilation errors.

	I've attached a diff of my changes. Let me know what you guys decide...

	-Matt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: neko_vidalia-0.1.10_irix.patch
Type: application/octet-stream
Size: 2581 bytes
Desc: not available
Url : http://lists.vidalia-project.net/pipermail/vidalia-users/attachments/20090217/e7508bba/attachment.obj