Hey Sam,
I checked your PR but I think I found a simpler way [1] to handle this. The
logic goes like this:
1. assume you have tubes.
2. if everything goes OK, then you do have tubes.
3. but, if tubes creation fails, and the reason is lack of support, then
you don't have tubes (sort of
On Mon, Dec 28, 2015 at 02:37:20PM -0300, Martin Abente wrote:
> @Sam:
>
> • Using GSettings is definitely a decent workaround instead of going for
> detection, I checked your PR and I will send some comments, but we will
> have to push it for as a feature freeze exception / Bug Fix.
>
*@Sam:*
- Using GSettings is definitely a decent workaround instead of going for
detection, I checked your PR and I will send some comments, but we will
have to push it for as a feature freeze exception / Bug Fix.
- I don't agree we should add it to the toolkit yet, still too early to
Hi, Jonas
Yet more examples of this broken software problem. I have scripts which
provide the 'bad and ugly' codecs for GStreamer 0.10 which work very
well. I have
had to regress to Jukebox 26 in order for this to work, but it performs
well. I have been unable to find where these codecs go
Hi, Sam
Thanks. That sounds like enough to get me going. Sadly, this also means
porting to gtk3 but it will need to be done anyway.
Yours,
Tony
On 12/26/2015 11:57 AM, Sam P. wrote:
Hi Tony,
Sorry that I was a bit vague in the previous email. The collab
wrapper is not yet merged into
Hi Gonzalo,
I agree with your perspective that we do need to make the wrapper the best
it can be before locking ourselves into it. That is a good plan.
I'm not sure what you mean about adding a parameter to the setup method.
Could you please elaborate?
Thanks,
Sam
On Sat, Dec 26, 2015 at
Hi Tony,
Sorry that I was a bit vague in the previous email. The collab wrapper is
not yet merged into sugar-toolkit-gtk3, however can be used by activities
by copying a script and including it in their activity.
The collabwrapper script is available here:
Hi James,
On Sat, Dec 26, 2015 at 2:28 PM, James Cameron wrote:
> Thanks all for the thread and replies.
>
> I'm not sure I understand the situation fully yet, but I'll make some
> comments regardless. Hopefully any disconnect between my comments and
> your understanding will
Quoting Tony Anderson (2015-12-26 15:31:16)
> Thanks. That sounds like enough to get me going. Sadly, this also
> means porting to gtk3 but it will need to be done anyway.
Thanks - a hassle indeed, but urgently needed not only for
collaboration:
* GStreamer 0.10 (tied to GTK+ 2.x) is
Tony,
I have been lurking on these mailing lists for the past few years but
haven't made any contribution to Sugar in that time. You may recall that I
wrote a couple of FLOSS manuals for OLPC, and strangely enough that led me
away from the project, because it convinced me I had a future as an
IMHO, the bottom line is that we are currently dependent on a protocol that
has been deprecated for 7+ years. It will undoubtedly become more and more
difficult to maintain as time goes on. We need to be focused on the things
that are core to our mission and that means letting others, ie. the
[dropping Cc's, assuming all are subscribed to -devel]
Quoting James Cameron (2015-12-26 08:58:13)
> Pull request 282 mentions 0.17.25, but of what package? When did the
> Tubes API get removed from the Telepathy packages? Yes, for Fedora it
> was 22, but we care about other downstreams.
Quoting James Cameron (2015-12-26 10:07:11)
> On Sat, Dec 26, 2015 at 09:52:56AM +0530, Jonas Smedegaard wrote:
>> telepathy-gabble is where Tubes interface was dropped.
>
> Thanks!
>
> I wasn't sure it was, because Gabble is only used when operating with
> Jabber/XMPP servers, and we also use
Hi Sam,
I am still not clear on the status. I have a long-dormant activity
'bingo' which depends on the caller sending 'bingo cards', receiving a
'bingo call', and being able to check the card via collaboration. In
developing those features, should I use the collab wrapper? Is it
available
Hi Martin,
I like your proposal of use the wrapper in the activities by at least one
cycle, before include it in the toolkit.
In our experience, once the code is included in the toolkit, is difficult
make changes without breaking activities in
unexpected ways.
I didn't have time to make tests with
On Sat, Dec 26, 2015 at 09:52:56AM +0530, Jonas Smedegaard wrote:
> [dropping Cc's, assuming all are subscribed to -devel]
>
> Quoting James Cameron (2015-12-26 08:58:13)
> > Pull request 282 mentions 0.17.25, but of what package? When did the
> > Tubes API get removed from the Telepathy
Hi, Sam
Thanks for your response. I used 'deliberate' to express my frustration.
From the wiki pages, I assume that the collaboration wrapper is
supported in 0.106 although activities that use it must port to sugar3.
The current version of
chat is using this and can act as a tutorial
Hi Martin,
On Thu, Dec 24, 2015 at 6:52 AM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:
> Hello everyone,
>
> I have been reviewing the current state of the collaboration proposals and
> I am afraid it is still too early for merging it. We need to explore more
> use cases, and this
Hello everyone,
I have been reviewing the current state of the collaboration proposals and
I am afraid it is still too early for merging it. We need to explore more
use cases, and this will only happens when we start porting more Activities
that actually use TUBES. Therefore, i want to share some
Hi,
It would really be helpful for us to get an explanation when working
activities are deliberately broken ('deprecated') as in this case. What
is the new means to implement collaboration? What advantage does it
offer to the 'tubes' method we have been using from the beginning? Is
this
Hi Tony,
On Thu, Dec 24, 2015 at 5:35 PM, Tony Anderson
wrote:
> Hi,
>
> It would really be helpful for us to get an explanation when working
> activities are deliberately broken ('deprecated') as in this case. What is
> the new means to implement collaboration? What
21 matches
Mail list logo