X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<1471984429.18763.30.camel@oscopy.org>
Subject:	Re: [geda-user] Oscopy
From:	Arnaud Gardelein <arnaud AT oscopy DOT org>
To:	geda-user AT delorie DOT com
Date:	Tue, 23 Aug 2016 22:33:49 +0200
In-Reply-To:	<20160801102246.GA2561@localhost.localdomain>
References:
	<CANqhZFwC48g07MUY411a20C5oipkmmkzUimhz8OgvL2Thi-yDg AT mail DOT gmail DOT com>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

 <1470000765 DOT 3607 DOT 17 DOT camel AT oscopy DOT org>
	 <20160801102246 DOT GA2561 AT localhost DOT localdomain>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.3-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u7NKY1AX022936

Le lundi 01 août 2016 à 13:22 +0300, Vladimir Zhbanov (vzhbanov AT gmail DOT c
om) [via geda-user AT delorie DOT com] a écrit :
...
> Your presentation looks nice. However I tried it before several
> times and it never worked for me.
> 
Currently oscopy is in the stage "feature freeze", after a long
transition period. It is planned to test it on fresh debian, ubuntu and
fedora, and update the documentation and website.

> I've tried to compile it just now. First some notes on your
> download page:
> - it mentions python-gtk, it should be python-gtk2, at least for
>   the experimental branch;
> - ipython should be replaced with ipython3 for the experimental
>   branch
> - python-gobject & python-gobject-dev since version 3.14 is needed
>   (there are other packages python-gobject-2 and
>   python-gobject-2-dev in Debian)
> 
This now shall be fixed, with a note to warn that transition to new
release is ongoing; this shall be applicable to all the website in
fact.

> Besides, I've installed python3-numpy (and python3-numpy-dev),
> python3-dbus, and python3-matplotlib to avoid some unclear
> ./configure messages and to make 'make' work.
> 
Those dependencies are now added.

> It would be nice if you also add the link to the page describing
> how to set up oscopy for gschem on the download page or/and just
> notice the line that has to be added into gschemrc to make it work
> in gschem.
> 
It shall now appear [1].

> Apart from what has been already said, there are other things to
> improve:
> - your keymap seems to conflict with gschem's default one,
>   e.g. "l" is used for adding lines; I would suggest to use
>   something like "<Shift>O L" where the prefix "<Shift>O" could
>   mean Oscopy menu and would be easily to remember for users.
> - your oscopy.scm is obsolete for gschem 1.9.x.
>   I had to change your keymap to make it work in the recent
>   version. The patch set is attached. It would be better, if you
>   had a check of gschem version in Makefile.am to choose a proper
>   version of oscopy.scm. The suggested changes include gettext
>   support so your new menus are automatically translated if they
>   have corresponding records in the geda-gaf *.po files.
> - I have no $COLORTERM defined, and thus your oscopy:oscopy-cmd
>   did not work for me. I've rewritten it to make it work using
>   the function system*. Defining your preferred terminal using
>   some variable in gschemrc before loading your script would be
>   convenient. Anyway, you have to mention this variable (I mean
>   COLORTERM) somewhere in your docs.
> 
The patchs are applied. It seems I misinterpreted the meaning of
$COLORTERM several years ago. Now it shall help to select between xterm
and gnome-terminal, would this way be suitable ? Or maybe it could be
only gnome-terminal ?
To select which version of oscopy.scm to use, I was wondering whether
it could be performed either at install time of at execution time.
Would there be a way to get the gschem version ? It seems that gschem
does not implement the command line option like '--version'. If needed
I could submit a patch to implement this option.
For the time being, the user has to modify manually the Makefile.am. I
hope to find a better way before the release of oscopy.

> Now, I'm on the stage when something is launched if I "launch
> Oscopy" though I see the message as follows in the background
> terminal gschem was launched from:
> 
> Error org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Oscopy was not provided by any .service files
> 
> I tried to add "/usr/lib/python3/" and
> "/usr/lib/python3/dist-packages/" to $PYTHONPATH with no success.
> 
> Any hints?
> 
Eventually I fixed the communication between gschem and oscopy. I took
me some time to figure out how to activate actions from gschem, as
dbus-send do not support complex datasets. I was not able to find
suitable DBus bindings with Guile, although it seems that Chicken has
[2]. Maybe someone here could point me to the right direction ?
In the meantime I implemented actions activation through a dedicated
script, called from oscopy.scm. Therefore now it shall be possible to
run the netlister and the simulator from gschem through oscopy.

Thanks a lot for your feedback. The experimental branch [3] is up to
date with those changes, maybe you want to give it a try ?

Arnaud.

[1] http://oscopy.org/dokuwiki/doku.php?id=install&#additional_notes
[2] http://wiki.call-cc.org/eggref/4/dbus
[3] https://github.com/agardelein/oscopy/tree/experimental

- Raw text -