No CloudWall runtime, it would be too limiting in this particular case.

ermouth

2017-08-24 8:08 GMT+03:00 Johs Ensby <j...@b2w.com>:

> ermouth,
> you are doing this as a cloudwell app with the cloudwall runtime
> supporting the single ddoc app, right?
> Johs
> > On 23 Aug 2017, at 21:56, ermouth <ermo...@gmail.com> wrote:
> >
> > Good idea, however I gonna start with CouchDB )
> >
> > I‘ve recordered 5min screencast about JSON editor for CN Photon
> > https://youtu.be/OQ_YJ0EZQjE
> >
> > ermouth
> >
> > 2017-08-23 9:10 GMT+03:00 Martin Broerse <martin.broe...@gmail.com>:
> >
> >> Perhaps also include pouchdb databases in Photon. You would need to type
> >> the database name you like to connect to because there is no index
> >> implemented. See https://github.com/w3c/IndexedDB/issues/31 . Caching
> the
> >> pouchdb database names would be be a nice feature for Photon. If Photo
> is
> >> build in Ember we can use https://github.com/pouchdb-
> community/ember-pouch
> >> to connect to the pouchdb databases.
> >>
> >> On Tue, Aug 22, 2017 at 5:09 PM, ermouth <ermo...@gmail.com> wrote:
> >>
> >>> Several sketches http://jquerymy.com/kod/photon1.pdf
> >>>
> >>> ermouth
> >>>
> >>> 2017-08-20 15:07 GMT+03:00 ermouth <ermo...@gmail.com>:
> >>>
> >>>> Seems that Fauxton experiencing some troubles with React unfriendly
> >>>> licensing. It‘s a pity taking in account CouchDB 2 moved to fairly
> >> stable
> >>>> state, and Fauxton itself received a lot of great improvements since
> >> last
> >>>> year.
> >>>>
> >>>> However, in new circumstances, what do you think about re-creating
> >>>> something like Futon+ (for Couch 2) as a single ddoc? So you copy
> >>>> open-sourced ddoc json to any DB, run index.html attachment from the
> >>> ddoc –
> >>>> and you‘re in.
> >>>>
> >>>> Basically, the idea is to re-create Futon-like app as a couchapp.
> >>>>
> >>>> If an idea is reasonable, is it reasonable to make the process openly
> >>>> funded in some way, to make it more rapid and controllable?
> >>>>
> >>>> ermouth
> >>>>
> >>>
> >>
>
>

Reply via email to