On Wed, Jan 7, 2015, at 05:50 PM, Marcus Denker wrote:
On 06 Jan 2015, at 15:13, MartinW w...@fastmail.fm wrote:
Whenever I reply to an issue or resolve an issue, everybody gets
automatically removed from assigned to this issue and I am set as the only
one the issue is assigned to.
On Thu, Oct 2, 2014, at 01:28 AM, Sven Van Caekenberghe wrote:
ZnClient is your friend (it is a builder) :
ZnClient new
url: 'http://some/thing';
formAt: #foo put: #bar;
formAt: 'baz' put: 'quux';
post.
Ah, that's indeed perfect. I think I discounted ZnClient initially
because
Hey all,
This is probably me missing something, but: for an upcoming
presentation, I wanted to find the tersest way to demonstrate making an
HTTP POST. Something equivalent to Python's
requests.post('http://some/thing', data={'foo': 'bar', 'baz':
'quux'})
The closest I could come up
On Aug 7, 2014, at 9:47 AM, stepharo steph...@free.fr wrote:
It’s up to the community to be involved with the tools they love and to
submit patches, and you’re totally right to remind everyone that it’s up to
us to improve Pharo if we want to keep it alive, but it’s up to the core
team to
On Aug 4, 2014, at 3:51 PM, stepharo steph...@free.fr wrote:
Hi guys
I'm sure that most of you did not realize it, but Pharo does not magically
improve. It improves because some of us are looking
at the tracker issues and looking at the code and improving it.
Since Pharo is yours I
I hate to bust this old evilness out, but is it feasible to abuse
#become: for this purpose? I haven't used it in so long I don't
actually remember whether that's feasible semantics with ivars.
On Thu, Apr 3, 2014, at 09:08 AM, Levente Uzonyi wrote:
On Thu, 3 Apr 2014, Igor Stasenko wrote:
On Tue, Mar 18, 2014, at 07:06 PM, Esteban A. Maringolo wrote:
I don't know the exact difference between the clients of Couchbase and
CouchDB.
I know Couchbase forked from CouchDB, and the REST API is the same.
Hopefully the CouchDB client will work.
It probably won't. Couchbase's protocol
