Re: here's an alpha12 debian package

[Marc Downie]

Wonderful!

For the Linuxly challenged (like myself), can we have the sequence of
command lines that installs this package written out long form, I want
to make sure that I'm actually testing this, and not the Field that I,
of course, currently have on my machine.

best,

Marc

On Tue, Apr 19, 2011 at 9:30 AM, revast <rev...@operamail.com> wrote:
> http://openartisthq.org/debian/maverick/field_12-alpha~openArtist1_all.deb
>
> let me know if it works.
> greets, revast
>
> --
> You received this message because you are subscribed to the Google Groups "Field-development" group.
> To post to this group, send email to field-de...@googlegroups.com.
> To unsubscribe from this group, send email to field-developm...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/field-development?hl=en.
>
>

[Joseph Gray]

Hi All,

Been subscribed to this list for a bit and just saw this download.  I'm a newbie to this as well, so I'm really interested in finding an easy way to install Field on Ubuntu, mostly to get at the ability to combine timeline style editing with Processing code, at least to start.

Just tried installing the .deb below on Ubuntu 10.04 using a package manager. 

Field now appears along with the other apps in the "Ubuntu menu" but makes an attempt to launch and then fails silently.  Any suggestions?

[Marc Downie]

Actually, there's a good chance that it's actually silently succeeding when you click the icon. Field 12 needs a command line argument to open any document right now:

~/field_linux.sh -field.scratch nameOfDocument.field

Needless to say, Field 13 won't do this (it will open your last document or a new one by default).

Marc.

[Joseph Gray]

ok, makes sense.  I did just type "field" into the terminal (without arguments (no .field file to test.. ) ) and got this:

user@user-desktop:~$ field
we are on 64bit
Exception in thread "main" java.lang.UnsatisfiedLinkError: Cannot load 64-bit SWT libraries on 32-bit JVM
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.C.<clinit>(Unknown Source)
    at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
    at org.eclipse.swt.internal.Converter.wcsToMbcs(Unknown Source)
    at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)
    at field.launch.Launcher.main(Launcher.java:60)

So something to do with 32 bit JVM?  Sorry, I'm totally new to this, but any help appreciated. 

[Marc Downie]

So something to do with 32 bit JVM?  Sorry, I'm totally new to this, but any help appreciated. 

Well, I'm pretty new to Linux myself.

Firstly, many thanks to revast for sending this out of the blue — seeing Field as an actual .deb package is a great provokation to get Field on Linux cleaned up a little. And, to answer my earlier question, just clicking on the link in Ubuntu is sufficient — no intricate command line knowledge required.

Revast:

1. Architecture detection in your /usr/bin/field seems busted (at least on 32 bit machines). If I replace your if clause with:

if $(uname -a | grep 'x86_64'); then

then I have a working /usr/bin/field (Joseph — this is the problem you are having).

2. /usr/bin/field should probably pass in $* rather than "-field.scratch helloWorld.field", or ideally something that checks to see if there are any command line arguments and if not, passes "-field.scratch default.field"

3. The icon in the applications / programming doesn't appear to do anything — but it could be another architecture detection issue; I only have access to a 32 bit install of Ubuntu right now.

Me:

1. I really do need to fix that File -> Open... dialog on Linux (SWT on Linux happily drills right into what on OS X is a special "package" directory rendering the whole dialog box useless).

best,

Marc.

 

[Marc Downie]

1. I really do need to fix that File -> Open... dialog on Linux (SWT on Linux happily drills right into what on OS X is a special "package" directory rendering the whole dialog box useless).

(This is now fixed in the repository).

Marc.

[Joseph Gray]

On Tue, Apr 19, 2011 at 6:01 PM, Marc Downie <ma...@openendedgroup.com> wrote:

1. Architecture detection in your /usr/bin/field seems busted (at least on 32 bit machines). If I replace your if clause with:

if $(uname -a | grep 'x86_64'); then

Thanks!

Just changed this in /usr/bin/field and Field launched right up from the icon in the Ubuntu menu, initially there was a message to install Mercurial, did that with Synaptic Package Manager, then launched it again and the GUI started up no problem!

Now to learn how to use the thing.

Cheers,
-Joe

[Al Matthews]

> Nevertheless I would suggest to make a PPA (PersonalPackageArchive)
for field on Launchpad. Many Projects have done this, its a cool way
of getting packages to the people, and let them stay up-to-date, as
the ppa is a repository. Repositories is where ubuntu gets its
software from. So when a user has added this ppa on his ubuntu and a
new field version is publiched in the PPA, he will get it
automatically. I haven't dealt with that really, maybe there is
somebody out there who has more experience with it and is willing to
help.
http://ubuntuforums.org/showthread.php?t=929498 would be a good
starting point I guess...
Or you could set up your own repository and host it yourself, which is
easier, but people will not find it easily. The Puredyne guys e.g.
also do have a ppa.

I wish I knew more here. Is the idea of working with Puredyne that

a) Field gets exposure via Puredyne
b) (In-gallery-)installation becomes simpler

Does Field then have to shrink in this case? Or evolve a defined
"core"? I'm used to thinking of Puredyne as fitting on a stick.

[Joseph Gray]

On Apr 25, 2011, at 7:43 AM, Al Matthews wrote:

>> Nevertheless I would suggest to make a PPA (PersonalPackageArchive)
> for field on Launchpad. Many Projects have done this, its a cool way
> of getting packages to the people, and let them stay up-to-date, as
> the ppa is a repository. Repositories is where ubuntu gets its
> software from. So when a user has added this ppa on his ubuntu and a
> new field version is publiched in the PPA, he will get it
> automatically.

I second this. It would be great if Field was available via the Ubuntu menu's "get software" interface. I'm not familiar with this level of coding and code distribution (hence my interest in Field) but it would be awesome to have a graphics coding environment easily available there for the only moderately tech creative types who focus more on artistic production.

Interestingly neither Processing or Arduino IDE's are available there - well an older version of Arduino's is.

> I haven't dealt with that really, maybe there is
> somebody out there who has more experience with it and is willing to
> help.
> http://ubuntuforums.org/showthread.php?t=929498 would be a good
> starting point I guess...
> Or you could set up your own repository and host it yourself, which is
> easier, but people will not find it easily. The Puredyne guys e.g.
> also do have a ppa.
>
> I wish I knew more here. Is the idea of working with Puredyne that
>
> a) Field gets exposure via Puredyne
> b) (In-gallery-)installation becomes simpler
>
> Does Field then have to shrink in this case? Or evolve a defined
> "core"? I'm used to thinking of Puredyne as fitting on a stick.
>

[Jean-Baptiste Mestelan]

On 20 April 2011 12:05, revast <rev...@operamail.com> wrote:

From commandline:
wget http://openartisthq.org/debian/maverick/field_12-alpha~openArtist1_all.deb
sudo dpkg -i field_12-alpha~openArtist1_all.deb

Hello Revast.
Thanks very much for the .deb.

Field starts OK if I launch
sh /opt/field/field_linux.sh


Yet, there seems to be a glitch with /usr/bin/field.
To get it working here, I had to replace (line 4)
if [ "$is64"=="x86_64" ] ; then

with
if [ "$is64" == "x86_64" ] ; then

i.e. surround == with spaces


Thanks for sharing your package.