On Tue, Oct 2, 2012 at 3:14 PM, Benoit Chesneau wrote:
>
> - web editor/viewer
>
Is this something that could be rolled into Futon? (Just spitballin here.)
(As a side note, I love the idea of being able to suck down a DD, see the
files, edit them, and blow it back. And, like you said, this does
On Wed, Oct 3, 2012 at 10:31 PM, Benjamin Young wrote:
>
> If a Design Doc is what's expected as output, then I think the current
> couchapp.py format has what's needed. couchapp.py itself needs further
> extension to support multiple docs and "attach these files to this couchdb
> doc" but that's
On 9/25/2012 10:02 AM, Dale Harvey wrote:
On 25 September 2012 14:39, Benoit Chesneau wrote:
On Tue, Sep 25, 2012 at 3:29 PM, Dale Harvey wrote:
Just wanted to chime in on a few points
I think Couch should definitely ship with a tool to upload a design doc,
I
think we pretty much all agr
On 2 October 2012 16:14, Benoit Chesneau wrote:
> On Wed, Sep 26, 2012 at 1:36 PM, Dave Cottlehuber wrote:
>> TL;DR +1 for including erica[1] into CouchDB proper.
>>
>> To summarise a bit:
>>
>> There are about 3 key things that all couchy tools do [1]….[5]:
>>
>> - transform local js and erlang
On Wed, Sep 26, 2012 at 1:36 PM, Dave Cottlehuber wrote:
> TL;DR +1 for including erica[1] into CouchDB proper.
>
> To summarise a bit:
>
> There are about 3 key things that all couchy tools do [1]….[5]:
>
> - transform local js and erlang functions in separate files, into
> design doc format
> -
Okay, thanks Benoit!
On Sat, Sep 29, 2012 at 9:52 AM, Benoit Chesneau wrote:
> On Sat, Sep 29, 2012 at 10:46 AM, Noah Slater
> wrote:
> > Benoit, who do you need to help you solve these problems? Let's kick this
> > into gear.
>
> Just sent a mail about the build system. It's quite long to read,
On Sat, Sep 29, 2012 at 10:46 AM, Noah Slater wrote:
> Benoit, who do you need to help you solve these problems? Let's kick this
> into gear.
Just sent a mail about the build system. It's quite long to read,
sorry for that.
Imo you, dave & paul can help me on that. And probably other too. At
lea
Benoit, who do you need to help you solve these problems? Let's kick this
into gear.
On Sat, Sep 29, 2012 at 8:16 AM, Benoit Chesneau wrote:
> On Fri, Sep 28, 2012 at 9:06 PM, Noah Slater wrote:
> > +1 on what Dave said.
> >
> > Additionally, Benoit, can you remind me why RCouch has not been mer
On Fri, Sep 28, 2012 at 9:06 PM, Noah Slater wrote:
> +1 on what Dave said.
>
> Additionally, Benoit, can you remind me why RCouch has not been merged in.
It is using a build not based on autotools (only makefile) like
bigcouch. Also it was easier to hack on it instead of waiting for
feedback tha
+1 on what Dave said.
Additionally, Benoit, can you remind me why RCouch has not been merged in.
And what are our current plans for it? And how does that play with the
BigCouch merge that we have planned?
On Wed, Sep 26, 2012 at 12:36 PM, Dave Cottlehuber wrote:
> TL;DR +1 for including erica[1]
TL;DR +1 for including erica[1] into CouchDB proper.
To summarise a bit:
There are about 3 key things that all couchy tools do [1]….[5]:
- transform local js and erlang functions in separate files, into
design doc format
- include necessary libraries and attachments into those ddocs
- upload tha
On 25/09/12 18:41, Wendall Cada wrote:
Thanks for the commentary Benoit, very useful. I've read all of the discussion
up through today and I think there are some really great points made that are
missed in the discussion. I want to respond to both the first and second emails
here, as they are
Yes, typically design doc attachments (the html / css / static js / images
that make up the couchapp), its been a part of every tool that generates
the design doc from the filesystem as well, kanso, nodecouchapp, couchapppy
and erica all do the same thing, just with some differing (and some
matchin
Right. Give it a directory and a doc URL and put the contents of the dir onto
the doc.
On Wednesday, 26 September 2012 at 10:19, Noah Slater wrote:
> I was thinking this myself, but wasn't sure. Are you just talking about a
> tool that uploads a directory structure into doc attachments? That
I was thinking this myself, but wasn't sure. Are you just talking about a
tool that uploads a directory structure into doc attachments? That's a
different tool to something that assembles a design doc from a directory,
right?
On Wed, Sep 26, 2012 at 10:11 AM, Simon Metson wrote:
> Hi
>
>
> On We
Hi
On Wednesday, 26 September 2012 at 10:07, Dale Harvey wrote:
> Making it simple to pick a directory to upload as a set of attachments
> doesnt exclude including all the extra functionality of couchapps, as
> node.couchapp + kanso show
IMHO that's another tool to what Noah wants. It's one th
It wouldnt be(much of) a problem if CouchDB was aiming to compete / replace
with Rails or Django, but I think that imho is misguided. If CouchDB wants
to play nice with applications that do use Django / Rails / plain HTML apps
that happen to use CouchDB as a backing store then it is a problem, not
There's a simple solution to this; have two ways to define where data is. One
is the file system following the couchapp layout, the other is a file that says
where resources are (which is what node.couchapp.js does, give or take). I
think both approaches are valid in different use cases - the fo
I don't see the problem with this.
If you were doing a Rails project, you wouldn't complain that you had to
move your Ruby files into a specific structure. Nor would you if you were
doing a Django project. In fact, for any system that uses the filesystem as
state, it is fairly common to have struc
I have a folder here with an index.html file in it
Can I upload it to CouchDB as an attachment without moving it? last time
remember (admittedly a long time ago) I couldnt do that with erica nor the
couchapppy tool
If not, I think that is one of the primary use cases that should be kept in
mind,
On Wed, Sep 26, 2012 at 10:32 AM, Noah Slater wrote:
> Benoit, that is FUCKING cool. Seriously cool shit. Did you write that??
>
Thanks. Yes I wrote that sometimes ago. It need to be perfected though.
- benoît
Benoit, that is FUCKING cool. Seriously cool shit. Did you write that??
On Wed, Sep 26, 2012 at 9:07 AM, Benoit Chesneau wrote:
> On Wed, Sep 26, 2012 at 10:05 AM, Benoit Chesneau
> wrote:
> > On Wed, Sep 26, 2012 at 7:58 AM, Eli Stevens (Gmail)
> > wrote:
> >> On Tue, Sep 25, 2012 at 10:25 PM,
On Wed, Sep 26, 2012 at 10:05 AM, Benoit Chesneau wrote:
> On Wed, Sep 26, 2012 at 7:58 AM, Eli Stevens (Gmail)
> wrote:
>> On Tue, Sep 25, 2012 at 10:25 PM, Ryan Ramage wrote:
>>> 1) We have to decide on the directory structure. Based on what benoit
>>> and dale have brought up. I have opinions
On Wed, Sep 26, 2012 at 7:58 AM, Eli Stevens (Gmail)
wrote:
> On Tue, Sep 25, 2012 at 10:25 PM, Ryan Ramage wrote:
>> 1) We have to decide on the directory structure. Based on what benoit
>> and dale have brought up. I have opinions, along with others. Lets not
>> rattle sabres around this yet.
On Tue, Sep 25, 2012 at 10:25 PM, Ryan Ramage wrote:
> 1) We have to decide on the directory structure. Based on what benoit
> and dale have brought up. I have opinions, along with others. Lets not
> rattle sabres around this yet. But pick something relatively user
> friendly, and straightforward
On Tue, Sep 25, 2012 at 2:09 AM, Noah Slater wrote:
> Ryan,
>
> If you had to pick between bundling the afformentioned reference
> implementation (a tool that just uploads a dir structure to a design doc,
> and pretty much nothing else) and Benoit's erica, which would you pick, and
> why? And whic
Thanks for the commentary Benoit, very useful. I've read all of the
discussion up through today and I think there are some really great
points made that are missed in the discussion. I want to respond to both
the first and second emails here, as they are related in my mind.
1. OTP couchdb - Fo
On 25 September 2012 14:39, Benoit Chesneau wrote:
> On Tue, Sep 25, 2012 at 3:29 PM, Dale Harvey wrote:
> > Just wanted to chime in on a few points
> >
> > I think Couch should definitely ship with a tool to upload a design doc,
> I
> > think we pretty much all agreed on that in Boston, its not
On Tue, Sep 25, 2012 at 5:52 AM, Dirkjan Ochtman wrote:
> organized around CouchApps. I think that currently, the swirling
> vortex of CouchApp-like projects is more of a distraction to the
> CouchDB community than a force for constructive feedback.
>
Yes, couchapps can be criticized for being v
On Tue, Sep 25, 2012 at 3:29 PM, Dale Harvey wrote:
> Just wanted to chime in on a few points
>
> I think Couch should definitely ship with a tool to upload a design doc, I
> think we pretty much all agreed on that in Boston, its not even particular
> to couchapps but a fairly basic requirement fo
Just wanted to chime in on a few points
I think Couch should definitely ship with a tool to upload a design doc, I
think we pretty much all agreed on that in Boston, its not even particular
to couchapps but a fairly basic requirement for anyone that has to manage
their map reduce code.
I do have
On Tue, Sep 25, 2012 at 1:17 PM, Benjamin Young wrote:
>
> The common denominator of the filesystem-to-design-doc mapping [1] among
> the Python "couchapp", erica, and kanso's "traditional-couchapp" dependency
> [2] is an advantage and that shouldn't be given up lightly.
> node.couchapp.js could c
On 9/24/2012 6:53 AM, Noah Slater wrote:
Making Futon a CouchApp would be a great first step.
Other good first steps would be trashing couchapp.com and redirecting to
c.a.o/couchapp like you say.
Also, creating a...@couchdb.apache.org or similar, to indicate a more
official, and broad, focus.
On Tue, Sep 25, 2012 at 1:30 PM, Octavian Damiean wrote:
>> I guess we could define a schema.
>>
>> This dir for map functions, this dir for reduce functions, this dir for
>> HTML, or whatever.
>>
>
> You mean a directory structure like the Python-based CouchApp has?
erica and couchapp (py the o
On Tue, Sep 25, 2012 at 1:08 PM, Noah Slater wrote:
> I think the multiple language thing is a slippery slope. By extension, we
> should ship client libraries too then. No way.
>
> The goal is to bootstrap Futon, and to provide a simple tool to demo in our
> docs.
This whole discussion makes me e
> I guess we could define a schema.
>
> This dir for map functions, this dir for reduce functions, this dir for
> HTML, or whatever.
>
You mean a directory structure like the Python-based CouchApp has?
> The goal is to bootstrap Futon, and to provide a simple tool to demo in our
> docs.
>
This
I think the multiple language thing is a slippery slope. By extension, we
should ship client libraries too then. No way.
On Tue, Sep 25, 2012 at 12:02 PM, Simon Metson wrote:
> Hi,
> > Not sure we should ship more than one "reference implementation."
> >
> >
>
> My thinking was that a reference
Hi,
> Not sure we should ship more than one "reference implementation."
>
>
My thinking was that a reference implementation in python might be different to
one in java, erlang or javascript. By "a bunch" I meant "one per language". If
you want to provide this as a base to build third party app
Agreed.
Not sure we should ship more than one "reference implementation."
And just to be clear, I think the primary goal of this effort, if somebody
undertakes it, is to provide a tool that can bootstrap Futon during the
install process. A secondary goal should be that we can talk about the tool
On Tue, Sep 25, 2012 at 10:34 AM, wrote:
>>
>> Just to come back to your user mindset argument. I would argue that the
>> people we really need to convince ARE the developers. Because the
>> developers are the people who pick the tooling. And if CouchDB/apps do not
>> look attractive, they will b
>
> Just to come back to your user mindset argument. I would argue that the
> people we really need to convince ARE the developers. Because the
> developers are the people who pick the tooling. And if CouchDB/apps do not
> look attractive, they will be ignored.
I'd just like to jump in and echo t
On Tue, Sep 25, 2012 at 10:16 AM, Simon Metson wrote:
> I was thinking about this "reference implementation" this morning. I think
> having a bunch, in multiple languages might not be a bad idea. So a
> simplified erica, couchapp.py, the node.js couchapp tool etc could all be
> there. That woul
Hey,
On Tuesday, 25 September 2012 at 09:09, Noah Slater wrote:
> If you had to pick between bundling the afformentioned reference
> implementation (a tool that just uploads a dir structure to a design doc,
> and pretty much nothing else) and Benoit's erica, which would you pick, and
> why? An
Ryan,
If you had to pick between bundling the afformentioned reference
implementation (a tool that just uploads a dir structure to a design doc,
and pretty much nothing else) and Benoit's erica, which would you pick, and
why? And which one of those tools do you think it would be easier to wrap a
3
> Erica is the follows traditional couchapp, it's the most native,
> requires no additional runtime or install, ...
I mean that it can be easily bundled with couch, and would work
everywhere couch did with no additional cruft.
> python, just vim ...) and real good docs to go with that
>
Forget vim, way too complicated :)
Ok this is more of an opinionated post.
If I was to pick sides, I would go with. erica. (I bet you all
thought I was going to say Kanso)
Erica is the follows traditional couchapp, it's the most na
we tried last winter to do a couchapp - gave up after never really
getting it to work - forget kanso - forget the "garden" thing someone
mentioned - they are all too complicated
all we wanted was straight forward design docs to load up (no node, no
python, just vim ...) and real good docs to
Hi All,
I'm pretty new to the Couch community. I recently starting using Couchdb for my
first web app product, and found it a fantastic fit. The only thing I found
frustrating, as a newbie to Couchdb, was using Futon to try create and test
views. I then started working with @bigbluehat and @dch
Hey,
I think if your user knows they're using a couchapp you've made a mistake. As a
user I shouldn't care about what technology stack my app is built upon, just
that I like it and it works (by magic). You're thinking like a developer, while
advocating thinking like a user ;)
IMHO a lot of the
Hey all, I am glad this topic is resurfacing and with some great
discussion. I have some irons in the fire with this with garden20.com
as many of you have seen. Here is my perspective.
I find most of the discussion above is backwards. Backwards in terms
of perspective. We are thinking as developer
+1
dir structure to json to design doc in couch would be nice. I think if you
phrase it as "reference implementation" and make it clear that other tools that
do more exist you side step the "which should we pick discussion".
On Monday, 24 September 2012 at 12:08, Robert Newson wrote:
> We c
On Mon, Sep 24, 2012 at 1:07 PM, Noah Slater wrote:
> I actually had not heard of Erica before today, Benoit. Perhaps this is
> part of the problem??
Well I mailed the ml, twitter and thought every devs was aware about
it. My fault I guess. I'm using it in place of couchapp. Partly
because I dis
Thanks Bob, I think you get what I'm trying to suggest. I am doing a poor
job of communication today.
On Mon, Sep 24, 2012 at 12:08 PM, Robert Newson wrote:
> +1 for a bundled tool that can upload a directory of files into a
> design document.
>
> One consequence of the BigCouch merge is that er
+1 for a bundled tool that can upload a directory of files into a
design document.
One consequence of the BigCouch merge is that erlang will not be a
runtime dependency; a proper erlang release is self-contained in that
respect, and that's essential to hot upgrades. Adding erica makes
sense if erl
On Mon, Sep 24, 2012 at 1:03 PM, Noah Slater wrote:
> Your mail amuses me.
>
> In the first bit you say we have Futon as a CouchApp but no way to
> bootstrap it in the build.
>
> Then in your next bit you ask why we'd need Erica in the source. ;) ;) ;)
No I said some code based on. erica isn't ne
I actually had not heard of Erica before today, Benoit. Perhaps this is
part of the problem??
Like most users, all I know is what I happen to bump in to and try. This
weekend it was Kanso. A while ago it was some other thing.
Let's make sure that the first thing a user bumps in to is a
reference
My goal is to have a simple command line tool that can take a directory and
upload it to a design doc. As simple as you can make that while still
having it functional as a basic CouchApp tool. And in a way that could be
used or embedded in other tools, or be used as a reference implementation.
On
On Mon, Sep 24, 2012 at 12:57 PM, Noah Slater wrote:
> I also want to clarify my two points in this whole discussion.
>
> You say it's not about the tooling, but that is short sighted. Existing
> CouchApp tooling is fractured and broken. The CouchApp website is the
> epitome of this. I spent the w
Your mail amuses me.
In the first bit you say we have Futon as a CouchApp but no way to
bootstrap it in the build.
Then in your next bit you ask why we'd need Erica in the source. ;) ;) ;)
If Erica is:
* Dead simple, and
* Lets you bootstrap CouchApps without any attendant fuss/framework, and
*
On Mon, Sep 24, 2012 at 12:53 PM, Noah Slater wrote:
> Making Futon a CouchApp would be a great first step.
>
> Other good first steps would be trashing couchapp.com and redirecting to
> c.a.o/couchapp like you say.
>
> Also, creating a...@couchdb.apache.org or similar, to indicate a more
> offici
I also want to clarify my two points in this whole discussion.
You say it's not about the tooling, but that is short sighted. Existing
CouchApp tooling is fractured and broken. The CouchApp website is the
epitome of this. I spent the whole weekend trying to install Kanso, with no
luck, I might add
On Mon, Sep 24, 2012 at 12:22 PM, Simon Metson wrote:
> Hey Benoit, all,
>
> I agree that this isn't about tools. The tools themselves are simple, and the
> last change to CouchDB that effected CouchApps would be in 0.10.0. While
> there are bugs, the tools are relatively stable and usable. I th
Making Futon a CouchApp would be a great first step.
Other good first steps would be trashing couchapp.com and redirecting to
c.a.o/couchapp like you say.
Also, creating a...@couchdb.apache.org or similar, to indicate a more
official, and broad, focus.
If we made Futon a CouchApp, how would that
Hey Benoit, all,
I agree that this isn't about tools. The tools themselves are simple, and the
last change to CouchDB that effected CouchApps would be in 0.10.0. While there
are bugs, the tools are relatively stable and usable. I think diversity is good
here.
There's a lot of bad documentati
Couchapps.
This isn't about tools. I think what @nslater experienced is the lack of
clear direction coming partly from frustration from some devs, and the
need for some to act in competition with other tools. Today what is the
situation:
- couchapp.org I ask since a long time to have the control
65 matches
Mail list logo
