We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
Index › Discussion › General Discussion,  Status › jolicloud blues
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1
jolicloud blues (Read 3217 times)
Andrew Jones
jolicloud blues
May 28th, 2010, 7:54am  
I get the feeling my OS isn't what they had in mind by linux, but anyway I'm running jolicloud a netbook remix of ubuntu jaunty. when I open up processing it just flickers I see the interface for a second and then bam it flickers out and then again. any idea how to fix the display?
Back to top
 
 
koogy
Re: jolicloud blues
Reply #1 - May 28th, 2010, 10:50am  
run it from a terminal window to capture the error message.




do people not use a cli anymore?

http://www.cryptonomicon.com/beginning.html
Back to top
 
 
Andrew Jones
Re: jolicloud blues
Reply #2 - May 28th, 2010, 8:42pm  
strange, when I run it from terminal it works fine. thanks for the idea though.
Back to top
 
 
koogy
Re: jolicloud blues
Reply #3 - May 30th, 2010, 4:44am  
that suggests, to me anyway, problems with the path or environment. but i could be wrong.

i have a gnome menu item for processing that calls it using full pathname (in my case /opt/processing/processing ) and that's fine. but rather than adding /opt/processing to my PATH i have a /home/kooogy/bin/processing script that does a cd to /opt/processing and then runs the processing script. can't remember why...
Back to top
 
 
martin_p
Re: jolicloud blues
Reply #4 - May 30th, 2010, 8:08am  
koogy wrote on May 30th, 2010, 4:44am:
that suggests, to me anyway, problems with the path or environment. but i could be wrong.

i have a gnome menu item for processing that calls it using full pathname (in my case /opt/processing/processing ) and that's fine. but rather than adding /opt/processing to my PATH i have a /home/kooogy/bin/processing script that does a cd to /opt/processing and then runs the processing script. can't remember why...


I do the same, I think it saves doing classpath stuff  (you can also specify your own SDK home). I also find it pretty useful (to have a custom script) to run different versions of processing eg development, or when there's a new version.
Back to top
 
WWW  
Page Index Toggle Pages: 1
‹ Previous Topic | Next Topic ›