[COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi all,

I am Dulanga Sashika and I am a final year undergraduate student at
Computer Science and Engineering department at University of Moratuwa, Sri
Lanka. I am really interested in java, java script, web applications,
algorithms, data mining and machine learning. I have 6 months of training
experience at Proavos (pvt) Ltd. and in there I worked on a web application
that used java, JEE and Spring Framework. My final year project also a web
related application and I used same technologies I mentioned above for
that. I am really interested in this project because I have a good
experience with web applications and I love work with javascript. I am
looking forward to contribute to this project in this summer. I like to
know more detail about this project and if you can, please guide me to
start working on this project.

Thank you.

W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Michelle Phung <mi...@apache.org>]

Hello Ayloa!

Welcome to the project! 

I see you have found our Fauxton repo (https://github.com/apache/couchdb-fauxton),
from here you are able to pull the latest code, and view pull requests for improvements. 

To get started contributing, I would fork the github repo so you have the latest copy on your local computer and github account.
Then create a new branch, for your own development, and then start to create/code the main page. As you are working on, rebase to the master branch (I do this daily, since the master branch moves fairly quickly, and can easily get diverted from your working branch, making it more difficult to merge eventually). 

This is a very exciting and fun ticket. :) 

Let us know if there is anything that is unclear, or if you would like further steps. The code is in currently being transitioned from BackboneJS to ReactJS, so there are some parts that are still in transition. Not to worry though, after a while, you will get used to it. 

Michelle



> On Sep 16, 2015, at 7:03 AM, Ayola Jayamaha <ra...@gmail.com> wrote:
> 
> Hi All,
> 
> I would like to contribute to Couchdb frontend. Hope you will all continue
> supporting.
> 
> On Sun, May 24, 2015 at 11:07 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> 
>> Hi Michelle,
>> 
>> Wow, seriously this is amazing :) I pushed this branch to my repo without
>> testing. But it is working :D. Thank you very much for your great help
>> Michelle. I'll send a PR today with few modifications. I think "Progress"
>> and "Update On" fields should be formatted.
>> 
>> And I'll switch to the CouchDB 2.0 from now on. I didn't implement any
>> test cases for this. My next step is to implement test cases for this
>> widget.
>> 
>> Thank you again for your quick reply and great help :)
>> 
>> Thanks and Regards
>> 
>> On Sat, May 23, 2015 at 12:30 AM, Michelle Phung <
>> michelle.phung@cloudant.com> wrote:
>> 
>>> Hi Dulanga,
>>> 
>>> I took a quick peek, and it looks like your widget is receiving
>>> information! Thats great :)
>>> 
>>> To get a persistent Active Task:
>>> 1. Go to Replications tab (in the left most sidebar),
>>> 2. You will see two tabs, make sure that LOCAL is highlighted in red on
>>> both
>>> 3. Choose an existing database from the dropdown,
>>> the database you choose doesn’t need to have that many documents in it
>>> (even 1 document will suffice),
>>> and type in any name you want for a new database in the other text field
>>> 4. Click both checkboxes (Continuous and Create target)
>>> 5. Click Replicate (green button)
>>> 6. Click on Active Task tab (on the far left sidebar)
>>> 7. Under the ‘Active Tasks’ tab, you should see a table for your new
>>> created continuous replication, and it will stay there until you cancel it.
>>> 
>>> I haven’t had a chance to look at the code yet, but I am glad to see that
>>> you are hitting the correct end points, with the widget.
>>> 
>>> I have attached what it looks like so far on my screen.  Awesome progress
>>> so far :)
>>> 
>>> Let me know when you want to create different types Active Tasks, to see
>>> how they would look in the widget.
>>> 
>>> Another thing I noticed is that the widget CSS in with CouchDB 2.0 in
>>> unwieldy. So, this is *optional* for you, but we are planning on releasing
>>> 2.0 soon-ish, so it would be a nice thing if you could update your system
>>> so you are coding with the most developer preview version, so that in case
>>> 2.0 gets released during the summer, you won’t have to go back and change
>>> it again. CSS is tricky enough as it is.
>>> 
>>> There are several things I can think of for you to do, but don’t want to
>>> overwhelm you, plus I think your proposal and the JIRA ticket is a good
>>> guide for the next steps. If you’re unsure, let us know what you think the
>>> next steps are, and we’ll try to guide you. There are some known pitfalls
>>> :) but don’t worry we all help each other out of them.
>>> 
>>> - Michelle
>>> 
>>> Link to the JIRA for quick reference:
>>> https://issues.apache.org/jira/browse/COUCHDB-2214
>>> This is exciting.
>>> 
>>> - Michelle
>>> 
>>> 
>>> On May 22, 2015, at 1:26 PM, Michelle Phung <mi...@cloudant.com>
>>> wrote:
>>> 
>>> Hi Dulanga,
>>> 
>>> Probably the easiest (and fastest way) way for us to give feedback would
>>> be for you to open a PR. That way we can comment on the code inline, and we
>>> can pull the repo down and see how it works in our environment faster.
>>> 
>>> I’ll pull your branch now, and take a look, but if you want more people
>>> to review and the easiest thing you can do is open a PR. That would help us
>>> out. It’s okay that it’s not an actual pull request, you can put [WIP] in
>>> the title and people are kind enough to know that work-in-progress means
>>> it’s not ready yet. Personally, as a developer, I rarely look at the WIP
>>> branches, unless I have a reason, like a request to do so.
>>> 
>>> - Michelle
>>> 
>>> 
>>> On May 21, 2015, at 3:14 PM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> I implemented the first widget in the dashboard. You can find it in
>>> 
>>> https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
>>> I didn't send a PR since I need to test the functionality more. I couldn't
>>> generate any active tasks to test this. Michelle told me about two way to
>>> generate active tasks. Now I am trying to do that. If you have any
>>> suggestions to do it in easy way, please help me. And really sorry for the
>>> late reply.
>>> 
>>> Cheers :)
>>> 
>>> On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>> 
>>> Hi Dulanga, Hi Nadeeshaan,
>>> 
>>> welcome! :)
>>> 
>>> Michelle, Ben and me will mentor this summer. And the community
>>> bonding period just started!
>>> 
>>> We will help you regarding the design of your widgets and revision
>>> browser and we will try to provide feedback on your code on a daily
>>> basis - that means that we either will comment on your branch on
>>> GitHub or an open PR on a daily basis.
>>> 
>>> You might already know that writing unit and integration tests is an
>>> absolute must for getting code merged into master.
>>> 
>>> The goal is to make small steps in an iterative way and get the MVP
>>> merged as soon as possible. After that we will iterate and can add
>>> more features. This ensures we have first results our users can make
>>> use of very early in the process and don't have to throw all code away
>>> if we run out of time.
>>> 
>>> 
>>> Please use the time to learn more about Apache CouchDB, read:
>>> 
>>> - http://couchdb.apache.org/bylaws.html
>>> - http://couchdb.apache.org/conduct.html
>>> 
>>> We will invite you to our Fauxton standup next week or the following
>>> one, I will contact you a few days before. It is 16:00 (Berlin
>>> Timezone) on Google Hangouts.
>>> 
>>> Best,
>>> Robert
>>> 
>>> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> 
>>> Dear all,
>>> 
>>> Thank you very much for supporting me to achieve this success in GSoC
>>> 
>>> 2015.
>>> 
>>> I will not get accepted for GSoC 2015 without all your great help.
>>> 
>>> Special
>>> 
>>> thanks should go to Robert and Alexander who guide me really well and
>>> 
>>> help
>>> 
>>> me to understand the project and create a good proposal for the project.
>>> 
>>> Looking forward to start the project and working with you all. Thank you
>>> very much again.
>>> 
>>> 
>>> Thank you
>>> 
>>> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> 
>>> Problem solved :) thank you very much for the help Robert.
>>> 
>>> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
>>> 
>>> wrote:
>>> 
>>> 
>>> Hi Dulanga,
>>> 
>>> Given you named your module `documents` you must have your main less
>>> file for the module in `assets/less` and name it `documents.less`.
>>> 
>>> Example:
>>> 
>>> 
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>> 
>>> 
>>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> 
>>> Hi Robert,
>>> 
>>> By following given links and playing around with the code, I could
>>> successfully implement a react component and display a text in the
>>> dashboard. I added a new dashboard.less file to apply styles for
>>> 
>>> that.
>>> 
>>> But
>>> 
>>> it didn't work. Is there any configurations to do before using those
>>> 
>>> less
>>> 
>>> files for the styles? As a next step, I am hoping to implement some
>>> 
>>> complex
>>> 
>>> components. Specially, some movable items with add and remove
>>> 
>>> features
>>> 
>>> as
>>> 
>>> Alex suggested.
>>> 
>>> Best Regards
>>> 
>>> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
>>> 
>>> wadsashika@gmail.com
>>> 
>>> 
>>> wrote:
>>> 
>>> Thank you very much for your valuable ideas Alex. As we discussed in
>>> IRC, I will move into implementing basic structure of the dashboard
>>> rather than bothering about widget design. After doing that, we can
>>> 
>>> go
>>> 
>>> into widgets.
>>> 
>>> Cheers
>>> 
>>> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>>> 
>>> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>>> 
>>> wadsashika@gmail.com>
>>> 
>>> wrote:
>>> 
>>> 
>>> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>>> 
>>> 
>>> http://i.imgur.com/FFiIpbv.png
>>> 
>>> 1. Widgets customization button shouldn't consume so much valuable
>>> 
>>> space.
>>> 
>>> 2. These buttons are duplicates sidebar menu items without giving
>>> 
>>> any
>>> 
>>> benefits.
>>> 3. 10 active replication are cool, but which are there? I to get
>>> 
>>> this
>>> 
>>> I need to click more which isn't much different from click on
>>> 
>>> Active
>>> 
>>> Tasks sidebar menu item and select filter by replication tasks.
>>> Dashboard should just works and not require any actions from use
>>> 
>>> side.
>>> 
>>> If user click on widget and leaves it - dashboard main goal is
>>> 
>>> failed.
>>> 
>>> 4. Active tasks are already running (: There couldn't be active
>>> stopped ones. Also, here you can show active replications and add
>>> 
>>> some
>>> 
>>> filter. Yes, it will duplicate an active tasks page at some
>>> 
>>> points,
>>> 
>>> but the difference is in short summary of the recent activity
>>> 
>>> shaped
>>> 
>>> into compact form.
>>> 5. Recently visited databases cool, but are they be only 4? May
>>> 
>>> be 10
>>> 
>>> or 20? How about search field to filter this list as well?
>>> 6. Again button that leads to some other page. Why not just a
>>> 
>>> simple
>>> 
>>> list users and a form to search and register new ones?
>>> 7. Same problem. Why not a form to instantly run a replication?
>>> 
>>> If it
>>> 
>>> will be a replication widget, it could also steal a part of
>>> 
>>> features
>>> 
>>> from active tasks widget to show only replications.
>>> 
>>> --
>>> ,,,^..^,,,
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>> 
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>> 
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>> 
> 
> 
> 
> -- 
> Best Regards,
> Nishani Jayamaha
> http://ayolajayamaha.blogspot.com/

Re: [COUCHDB-2214] Dashboard as main page

[Ayola Jayamaha <ra...@gmail.com>]

Hi All,

I would like to contribute to Couchdb frontend. Hope you will all continue
supporting.

On Sun, May 24, 2015 at 11:07 AM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Hi Michelle,
>
> Wow, seriously this is amazing :) I pushed this branch to my repo without
> testing. But it is working :D. Thank you very much for your great help
> Michelle. I'll send a PR today with few modifications. I think "Progress"
> and "Update On" fields should be formatted.
>
> And I'll switch to the CouchDB 2.0 from now on. I didn't implement any
> test cases for this. My next step is to implement test cases for this
> widget.
>
> Thank you again for your quick reply and great help :)
>
> Thanks and Regards
>
> On Sat, May 23, 2015 at 12:30 AM, Michelle Phung <
> michelle.phung@cloudant.com> wrote:
>
>> Hi Dulanga,
>>
>> I took a quick peek, and it looks like your widget is receiving
>> information! Thats great :)
>>
>> To get a persistent Active Task:
>> 1. Go to Replications tab (in the left most sidebar),
>> 2. You will see two tabs, make sure that LOCAL is highlighted in red on
>> both
>> 3. Choose an existing database from the dropdown,
>> the database you choose doesn’t need to have that many documents in it
>> (even 1 document will suffice),
>> and type in any name you want for a new database in the other text field
>> 4. Click both checkboxes (Continuous and Create target)
>> 5. Click Replicate (green button)
>> 6. Click on Active Task tab (on the far left sidebar)
>> 7. Under the ‘Active Tasks’ tab, you should see a table for your new
>> created continuous replication, and it will stay there until you cancel it.
>>
>> I haven’t had a chance to look at the code yet, but I am glad to see that
>> you are hitting the correct end points, with the widget.
>>
>> I have attached what it looks like so far on my screen.  Awesome progress
>> so far :)
>>
>> Let me know when you want to create different types Active Tasks, to see
>> how they would look in the widget.
>>
>> Another thing I noticed is that the widget CSS in with CouchDB 2.0 in
>> unwieldy. So, this is *optional* for you, but we are planning on releasing
>> 2.0 soon-ish, so it would be a nice thing if you could update your system
>> so you are coding with the most developer preview version, so that in case
>> 2.0 gets released during the summer, you won’t have to go back and change
>> it again. CSS is tricky enough as it is.
>>
>> There are several things I can think of for you to do, but don’t want to
>> overwhelm you, plus I think your proposal and the JIRA ticket is a good
>> guide for the next steps. If you’re unsure, let us know what you think the
>> next steps are, and we’ll try to guide you. There are some known pitfalls
>> :) but don’t worry we all help each other out of them.
>>
>> - Michelle
>>
>> Link to the JIRA for quick reference:
>> https://issues.apache.org/jira/browse/COUCHDB-2214
>> This is exciting.
>>
>> - Michelle
>>
>>
>> On May 22, 2015, at 1:26 PM, Michelle Phung <mi...@cloudant.com>
>> wrote:
>>
>> Hi Dulanga,
>>
>> Probably the easiest (and fastest way) way for us to give feedback would
>> be for you to open a PR. That way we can comment on the code inline, and we
>> can pull the repo down and see how it works in our environment faster.
>>
>> I’ll pull your branch now, and take a look, but if you want more people
>> to review and the easiest thing you can do is open a PR. That would help us
>> out. It’s okay that it’s not an actual pull request, you can put [WIP] in
>> the title and people are kind enough to know that work-in-progress means
>> it’s not ready yet. Personally, as a developer, I rarely look at the WIP
>> branches, unless I have a reason, like a request to do so.
>>
>> - Michelle
>>
>>
>> On May 21, 2015, at 3:14 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>
>> Hi all,
>>
>> I implemented the first widget in the dashboard. You can find it in
>>
>> https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
>> I didn't send a PR since I need to test the functionality more. I couldn't
>> generate any active tasks to test this. Michelle told me about two way to
>> generate active tasks. Now I am trying to do that. If you have any
>> suggestions to do it in easy way, please help me. And really sorry for the
>> late reply.
>>
>> Cheers :)
>>
>> On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>
>> Hi Dulanga, Hi Nadeeshaan,
>>
>> welcome! :)
>>
>> Michelle, Ben and me will mentor this summer. And the community
>> bonding period just started!
>>
>> We will help you regarding the design of your widgets and revision
>> browser and we will try to provide feedback on your code on a daily
>> basis - that means that we either will comment on your branch on
>> GitHub or an open PR on a daily basis.
>>
>> You might already know that writing unit and integration tests is an
>> absolute must for getting code merged into master.
>>
>> The goal is to make small steps in an iterative way and get the MVP
>> merged as soon as possible. After that we will iterate and can add
>> more features. This ensures we have first results our users can make
>> use of very early in the process and don't have to throw all code away
>> if we run out of time.
>>
>>
>> Please use the time to learn more about Apache CouchDB, read:
>>
>> - http://couchdb.apache.org/bylaws.html
>> - http://couchdb.apache.org/conduct.html
>>
>> We will invite you to our Fauxton standup next week or the following
>> one, I will contact you a few days before. It is 16:00 (Berlin
>> Timezone) on Google Hangouts.
>>
>> Best,
>> Robert
>>
>> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>
>> Dear all,
>>
>> Thank you very much for supporting me to achieve this success in GSoC
>>
>> 2015.
>>
>> I will not get accepted for GSoC 2015 without all your great help.
>>
>> Special
>>
>> thanks should go to Robert and Alexander who guide me really well and
>>
>> help
>>
>> me to understand the project and create a good proposal for the project.
>>
>> Looking forward to start the project and working with you all. Thank you
>> very much again.
>>
>>
>> Thank you
>>
>> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>
>> Problem solved :) thank you very much for the help Robert.
>>
>> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
>>
>> wrote:
>>
>>
>> Hi Dulanga,
>>
>> Given you named your module `documents` you must have your main less
>> file for the module in `assets/less` and name it `documents.less`.
>>
>> Example:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>
>>
>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>
>> Hi Robert,
>>
>> By following given links and playing around with the code, I could
>> successfully implement a react component and display a text in the
>> dashboard. I added a new dashboard.less file to apply styles for
>>
>> that.
>>
>> But
>>
>> it didn't work. Is there any configurations to do before using those
>>
>> less
>>
>> files for the styles? As a next step, I am hoping to implement some
>>
>> complex
>>
>> components. Specially, some movable items with add and remove
>>
>> features
>>
>> as
>>
>> Alex suggested.
>>
>> Best Regards
>>
>> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
>>
>> wadsashika@gmail.com
>>
>>
>> wrote:
>>
>> Thank you very much for your valuable ideas Alex. As we discussed in
>> IRC, I will move into implementing basic structure of the dashboard
>> rather than bothering about widget design. After doing that, we can
>>
>> go
>>
>> into widgets.
>>
>> Cheers
>>
>> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>>
>> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>>
>> wadsashika@gmail.com>
>>
>> wrote:
>>
>>
>> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>>
>>
>> http://i.imgur.com/FFiIpbv.png
>>
>> 1. Widgets customization button shouldn't consume so much valuable
>>
>> space.
>>
>> 2. These buttons are duplicates sidebar menu items without giving
>>
>> any
>>
>> benefits.
>> 3. 10 active replication are cool, but which are there? I to get
>>
>> this
>>
>> I need to click more which isn't much different from click on
>>
>> Active
>>
>> Tasks sidebar menu item and select filter by replication tasks.
>> Dashboard should just works and not require any actions from use
>>
>> side.
>>
>> If user click on widget and leaves it - dashboard main goal is
>>
>> failed.
>>
>> 4. Active tasks are already running (: There couldn't be active
>> stopped ones. Also, here you can show active replications and add
>>
>> some
>>
>> filter. Yes, it will duplicate an active tasks page at some
>>
>> points,
>>
>> but the difference is in short summary of the recent activity
>>
>> shaped
>>
>> into compact form.
>> 5. Recently visited databases cool, but are they be only 4? May
>>
>> be 10
>>
>> or 20? How about search field to filter this list as well?
>> 6. Again button that leads to some other page. Why not just a
>>
>> simple
>>
>> list users and a form to search and register new ones?
>> 7. Same problem. Why not a form to instantly run a replication?
>>
>> If it
>>
>> will be a replication widget, it could also steal a part of
>>
>> features
>>
>> from active tasks widget to show only replications.
>>
>> --
>> ,,,^..^,,,
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>>
>>
>>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
Best Regards,
Nishani Jayamaha
http://ayolajayamaha.blogspot.com/

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Michelle,

Wow, seriously this is amazing :) I pushed this branch to my repo without
testing. But it is working :D. Thank you very much for your great help
Michelle. I'll send a PR today with few modifications. I think "Progress"
and "Update On" fields should be formatted.

And I'll switch to the CouchDB 2.0 from now on. I didn't implement any test
cases for this. My next step is to implement test cases for this widget.

Thank you again for your quick reply and great help :)

Thanks and Regards

On Sat, May 23, 2015 at 12:30 AM, Michelle Phung <
michelle.phung@cloudant.com> wrote:

> Hi Dulanga,
>
> I took a quick peek, and it looks like your widget is receiving
> information! Thats great :)
>
> To get a persistent Active Task:
> 1. Go to Replications tab (in the left most sidebar),
> 2. You will see two tabs, make sure that LOCAL is highlighted in red on
> both
> 3. Choose an existing database from the dropdown,
> the database you choose doesn’t need to have that many documents in it
> (even 1 document will suffice),
> and type in any name you want for a new database in the other text field
> 4. Click both checkboxes (Continuous and Create target)
> 5. Click Replicate (green button)
> 6. Click on Active Task tab (on the far left sidebar)
> 7. Under the ‘Active Tasks’ tab, you should see a table for your new
> created continuous replication, and it will stay there until you cancel it.
>
> I haven’t had a chance to look at the code yet, but I am glad to see that
> you are hitting the correct end points, with the widget.
>
> I have attached what it looks like so far on my screen.  Awesome progress
> so far :)
>
> Let me know when you want to create different types Active Tasks, to see
> how they would look in the widget.
>
> Another thing I noticed is that the widget CSS in with CouchDB 2.0 in
> unwieldy. So, this is *optional* for you, but we are planning on releasing
> 2.0 soon-ish, so it would be a nice thing if you could update your system
> so you are coding with the most developer preview version, so that in case
> 2.0 gets released during the summer, you won’t have to go back and change
> it again. CSS is tricky enough as it is.
>
> There are several things I can think of for you to do, but don’t want to
> overwhelm you, plus I think your proposal and the JIRA ticket is a good
> guide for the next steps. If you’re unsure, let us know what you think the
> next steps are, and we’ll try to guide you. There are some known pitfalls
> :) but don’t worry we all help each other out of them.
>
> - Michelle
>
> Link to the JIRA for quick reference:
> https://issues.apache.org/jira/browse/COUCHDB-2214
> This is exciting.
>
> - Michelle
>
>
> On May 22, 2015, at 1:26 PM, Michelle Phung <mi...@cloudant.com>
> wrote:
>
> Hi Dulanga,
>
> Probably the easiest (and fastest way) way for us to give feedback would
> be for you to open a PR. That way we can comment on the code inline, and we
> can pull the repo down and see how it works in our environment faster.
>
> I’ll pull your branch now, and take a look, but if you want more people to
> review and the easiest thing you can do is open a PR. That would help us
> out. It’s okay that it’s not an actual pull request, you can put [WIP] in
> the title and people are kind enough to know that work-in-progress means
> it’s not ready yet. Personally, as a developer, I rarely look at the WIP
> branches, unless I have a reason, like a request to do so.
>
> - Michelle
>
>
> On May 21, 2015, at 3:14 PM, Dulanga Sashika <wa...@gmail.com> wrote:
>
> Hi all,
>
> I implemented the first widget in the dashboard. You can find it in
>
> https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
> I didn't send a PR since I need to test the functionality more. I couldn't
> generate any active tasks to test this. Michelle told me about two way to
> generate active tasks. Now I am trying to do that. If you have any
> suggestions to do it in easy way, please help me. And really sorry for the
> late reply.
>
> Cheers :)
>
> On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
> Hi Dulanga, Hi Nadeeshaan,
>
> welcome! :)
>
> Michelle, Ben and me will mentor this summer. And the community
> bonding period just started!
>
> We will help you regarding the design of your widgets and revision
> browser and we will try to provide feedback on your code on a daily
> basis - that means that we either will comment on your branch on
> GitHub or an open PR on a daily basis.
>
> You might already know that writing unit and integration tests is an
> absolute must for getting code merged into master.
>
> The goal is to make small steps in an iterative way and get the MVP
> merged as soon as possible. After that we will iterate and can add
> more features. This ensures we have first results our users can make
> use of very early in the process and don't have to throw all code away
> if we run out of time.
>
>
> Please use the time to learn more about Apache CouchDB, read:
>
> - http://couchdb.apache.org/bylaws.html
> - http://couchdb.apache.org/conduct.html
>
> We will invite you to our Fauxton standup next week or the following
> one, I will contact you a few days before. It is 16:00 (Berlin
> Timezone) on Google Hangouts.
>
> Best,
> Robert
>
> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
> Dear all,
>
> Thank you very much for supporting me to achieve this success in GSoC
>
> 2015.
>
> I will not get accepted for GSoC 2015 without all your great help.
>
> Special
>
> thanks should go to Robert and Alexander who guide me really well and
>
> help
>
> me to understand the project and create a good proposal for the project.
>
> Looking forward to start the project and working with you all. Thank you
> very much again.
>
>
> Thank you
>
> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
> Problem solved :) thank you very much for the help Robert.
>
> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
>
> wrote:
>
>
> Hi Dulanga,
>
> Given you named your module `documents` you must have your main less
> file for the module in `assets/less` and name it `documents.less`.
>
> Example:
>
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>
>
> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
> Hi Robert,
>
> By following given links and playing around with the code, I could
> successfully implement a react component and display a text in the
> dashboard. I added a new dashboard.less file to apply styles for
>
> that.
>
> But
>
> it didn't work. Is there any configurations to do before using those
>
> less
>
> files for the styles? As a next step, I am hoping to implement some
>
> complex
>
> components. Specially, some movable items with add and remove
>
> features
>
> as
>
> Alex suggested.
>
> Best Regards
>
> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
>
> wadsashika@gmail.com
>
>
> wrote:
>
> Thank you very much for your valuable ideas Alex. As we discussed in
> IRC, I will move into implementing basic structure of the dashboard
> rather than bothering about widget design. After doing that, we can
>
> go
>
> into widgets.
>
> Cheers
>
> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>
> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>
> wadsashika@gmail.com>
>
> wrote:
>
>
> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>
>
> http://i.imgur.com/FFiIpbv.png
>
> 1. Widgets customization button shouldn't consume so much valuable
>
> space.
>
> 2. These buttons are duplicates sidebar menu items without giving
>
> any
>
> benefits.
> 3. 10 active replication are cool, but which are there? I to get
>
> this
>
> I need to click more which isn't much different from click on
>
> Active
>
> Tasks sidebar menu item and select filter by replication tasks.
> Dashboard should just works and not require any actions from use
>
> side.
>
> If user click on widget and leaves it - dashboard main goal is
>
> failed.
>
> 4. Active tasks are already running (: There couldn't be active
> stopped ones. Also, here you can show active replications and add
>
> some
>
> filter. Yes, it will duplicate an active tasks page at some
>
> points,
>
> but the difference is in short summary of the recent activity
>
> shaped
>
> into compact form.
> 5. Recently visited databases cool, but are they be only 4? May
>
> be 10
>
> or 20? How about search field to filter this list as well?
> 6. Again button that leads to some other page. Why not just a
>
> simple
>
> list users and a form to search and register new ones?
> 7. Same problem. Why not a form to instantly run a replication?
>
> If it
>
> will be a replication widget, it could also steal a part of
>
> features
>
> from active tasks widget to show only replications.
>
> --
> ,,,^..^,,,
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>
>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>
>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>
>
>
>


-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Michelle Phung <mi...@cloudant.com>]

Hi Dulanga,

I took a quick peek, and it looks like your widget is receiving information! Thats great :)

To get a persistent Active Task:
	1. Go to Replications tab (in the left most sidebar),
	2. You will see two tabs, make sure that LOCAL is highlighted in red on both
	3. Choose an existing database from the dropdown, 
		the database you choose doesn’t need to have that many documents in it (even 1 document will suffice), 
		and type in any name you want for a new database in the other text field
	4. Click both checkboxes (Continuous and Create target)
	5. Click Replicate (green button)
	6. Click on Active Task tab (on the far left sidebar)
	7. Under the ‘Active Tasks’ tab, you should see a table for your new created continuous replication, and it will stay there until you cancel it.
	
I haven’t had a chance to look at the code yet, but I am glad to see that you are hitting the correct end points, with the widget. 

I have attached what it looks like so far on my screen.  Awesome progress so far :)

Let me know when you want to create different types Active Tasks, to see how they would look in the widget.

Another thing I noticed is that the widget CSS in with CouchDB 2.0 in unwieldy. So, this is *optional* for you, but we are planning on releasing 2.0 soon-ish, so it would be a nice thing if you could update your system so you are coding with the most developer preview version, so that in case 2.0 gets released during the summer, you won’t have to go back and change it again. CSS is tricky enough as it is. 

There are several things I can think of for you to do, but don’t want to overwhelm you, plus I think your proposal and the JIRA ticket is a good guide for the next steps. If you’re unsure, let us know what you think the next steps are, and we’ll try to guide you. There are some known pitfalls :) but don’t worry we all help each other out of them. 

- Michelle

Link to the JIRA for quick reference: https://issues.apache.org/jira/browse/COUCHDB-2214
This is exciting.

- Michelle

> On May 22, 2015, at 1:26 PM, Michelle Phung <mi...@cloudant.com> wrote:
> 
> Hi Dulanga,
> 
> Probably the easiest (and fastest way) way for us to give feedback would be for you to open a PR. That way we can comment on the code inline, and we can pull the repo down and see how it works in our environment faster.
> 
> I’ll pull your branch now, and take a look, but if you want more people to review and the easiest thing you can do is open a PR. That would help us out. It’s okay that it’s not an actual pull request, you can put [WIP] in the title and people are kind enough to know that work-in-progress means it’s not ready yet. Personally, as a developer, I rarely look at the WIP branches, unless I have a reason, like a request to do so.
> 
> - Michelle
> 
> 
>> On May 21, 2015, at 3:14 PM, Dulanga Sashika <wa...@gmail.com> wrote:
>> 
>> Hi all,
>> 
>> I implemented the first widget in the dashboard. You can find it in
>> https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
>> I didn't send a PR since I need to test the functionality more. I couldn't
>> generate any active tasks to test this. Michelle told me about two way to
>> generate active tasks. Now I am trying to do that. If you have any
>> suggestions to do it in easy way, please help me. And really sorry for the
>> late reply.
>> 
>> Cheers :)
>> 
>> On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>> 
>>> Hi Dulanga, Hi Nadeeshaan,
>>> 
>>> welcome! :)
>>> 
>>> Michelle, Ben and me will mentor this summer. And the community
>>> bonding period just started!
>>> 
>>> We will help you regarding the design of your widgets and revision
>>> browser and we will try to provide feedback on your code on a daily
>>> basis - that means that we either will comment on your branch on
>>> GitHub or an open PR on a daily basis.
>>> 
>>> You might already know that writing unit and integration tests is an
>>> absolute must for getting code merged into master.
>>> 
>>> The goal is to make small steps in an iterative way and get the MVP
>>> merged as soon as possible. After that we will iterate and can add
>>> more features. This ensures we have first results our users can make
>>> use of very early in the process and don't have to throw all code away
>>> if we run out of time.
>>> 
>>> 
>>> Please use the time to learn more about Apache CouchDB, read:
>>> 
>>> - http://couchdb.apache.org/bylaws.html
>>> - http://couchdb.apache.org/conduct.html
>>> 
>>> We will invite you to our Fauxton standup next week or the following
>>> one, I will contact you a few days before. It is 16:00 (Berlin
>>> Timezone) on Google Hangouts.
>>> 
>>> Best,
>>> Robert
>>> 
>>> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>>> Dear all,
>>>> 
>>>> Thank you very much for supporting me to achieve this success in GSoC
>>> 2015.
>>>> I will not get accepted for GSoC 2015 without all your great help.
>>> Special
>>>> thanks should go to Robert and Alexander who guide me really well and
>>> help
>>>> me to understand the project and create a good proposal for the project.
>>>> 
>>>> Looking forward to start the project and working with you all. Thank you
>>>> very much again.
>>>> 
>>>> 
>>>> Thank you
>>>> 
>>>> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
>>>> wrote:
>>>> 
>>>>> Problem solved :) thank you very much for the help Robert.
>>>>> 
>>>>> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
>>> wrote:
>>>>> 
>>>>>> Hi Dulanga,
>>>>>> 
>>>>>> Given you named your module `documents` you must have your main less
>>>>>> file for the module in `assets/less` and name it `documents.less`.
>>>>>> 
>>>>>> Example:
>>>>>> 
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>>>>> 
>>>>>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>>>>>> wrote:
>>>>>>> Hi Robert,
>>>>>>> 
>>>>>>> By following given links and playing around with the code, I could
>>>>>>> successfully implement a react component and display a text in the
>>>>>>> dashboard. I added a new dashboard.less file to apply styles for
>>> that.
>>>>>> But
>>>>>>> it didn't work. Is there any configurations to do before using those
>>>>>> less
>>>>>>> files for the styles? As a next step, I am hoping to implement some
>>>>>> complex
>>>>>>> components. Specially, some movable items with add and remove
>>> features
>>>>>> as
>>>>>>> Alex suggested.
>>>>>>> 
>>>>>>> Best Regards
>>>>>>> 
>>>>>>> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
>>> wadsashika@gmail.com
>>>>>>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Thank you very much for your valuable ideas Alex. As we discussed in
>>>>>>>> IRC, I will move into implementing basic structure of the dashboard
>>>>>>>> rather than bothering about widget design. After doing that, we can
>>> go
>>>>>>>> into widgets.
>>>>>>>> 
>>>>>>>> Cheers
>>>>>>>> 
>>>>>>>> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>>>>>>>>> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>>>>>> wadsashika@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>> 
>>> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>>>>>>>>> 
>>>>>>>>> http://i.imgur.com/FFiIpbv.png
>>>>>>>>> 
>>>>>>>>> 1. Widgets customization button shouldn't consume so much valuable
>>>>>> space.
>>>>>>>>> 2. These buttons are duplicates sidebar menu items without giving
>>> any
>>>>>>>>> benefits.
>>>>>>>>> 3. 10 active replication are cool, but which are there? I to get
>>> this
>>>>>>>>> I need to click more which isn't much different from click on
>>> Active
>>>>>>>>> Tasks sidebar menu item and select filter by replication tasks.
>>>>>>>>> Dashboard should just works and not require any actions from use
>>>>>> side.
>>>>>>>>> If user click on widget and leaves it - dashboard main goal is
>>>>>> failed.
>>>>>>>>> 4. Active tasks are already running (: There couldn't be active
>>>>>>>>> stopped ones. Also, here you can show active replications and add
>>>>>> some
>>>>>>>>> filter. Yes, it will duplicate an active tasks page at some
>>> points,
>>>>>>>>> but the difference is in short summary of the recent activity
>>> shaped
>>>>>>>>> into compact form.
>>>>>>>>> 5. Recently visited databases cool, but are they be only 4? May
>>> be 10
>>>>>>>>> or 20? How about search field to filter this list as well?
>>>>>>>>> 6. Again button that leads to some other page. Why not just a
>>> simple
>>>>>>>>> list users and a form to search and register new ones?
>>>>>>>>> 7. Same problem. Why not a form to instantly run a replication?
>>> If it
>>>>>>>>> will be a replication widget, it could also steal a part of
>>> features
>>>>>>>>> from active tasks widget to show only replications.
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> ,,,^..^,,,
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> W. A. Dulanga Sashika,
>>>>>>>> Undergraduate Student,
>>>>>>>> Department of Computer Science and Engineering,
>>>>>>>> University of Moratuwa.
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> W. A. Dulanga Sashika,
>>>>>>> Undergraduate Student,
>>>>>>> Department of Computer Science and Engineering,
>>>>>>> University of Moratuwa.
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> W. A. Dulanga Sashika,
>>>>> Undergraduate Student,
>>>>> Department of Computer Science and Engineering,
>>>>> University of Moratuwa.
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> W. A. Dulanga Sashika,
>>>> Undergraduate Student,
>>>> Department of Computer Science and Engineering,
>>>> University of Moratuwa.
>>> 
>> 
>> 
>> 
>> -- 
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
> 

Re: [COUCHDB-2214] Dashboard as main page

[Michelle Phung <mi...@cloudant.com>]

Hi Dulanga,

Probably the easiest (and fastest way) way for us to give feedback would be for you to open a PR. That way we can comment on the code inline, and we can pull the repo down and see how it works in our environment faster.

I’ll pull your branch now, and take a look, but if you want more people to review and the easiest thing you can do is open a PR. That would help us out. It’s okay that it’s not an actual pull request, you can put [WIP] in the title and people are kind enough to know that work-in-progress means it’s not ready yet. Personally, as a developer, I rarely look at the WIP branches, unless I have a reason, like a request to do so.

- Michelle


> On May 21, 2015, at 3:14 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> 
> Hi all,
> 
> I implemented the first widget in the dashboard. You can find it in
> https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
> I didn't send a PR since I need to test the functionality more. I couldn't
> generate any active tasks to test this. Michelle told me about two way to
> generate active tasks. Now I am trying to do that. If you have any
> suggestions to do it in easy way, please help me. And really sorry for the
> late reply.
> 
> Cheers :)
> 
> On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
> 
>> Hi Dulanga, Hi Nadeeshaan,
>> 
>> welcome! :)
>> 
>> Michelle, Ben and me will mentor this summer. And the community
>> bonding period just started!
>> 
>> We will help you regarding the design of your widgets and revision
>> browser and we will try to provide feedback on your code on a daily
>> basis - that means that we either will comment on your branch on
>> GitHub or an open PR on a daily basis.
>> 
>> You might already know that writing unit and integration tests is an
>> absolute must for getting code merged into master.
>> 
>> The goal is to make small steps in an iterative way and get the MVP
>> merged as soon as possible. After that we will iterate and can add
>> more features. This ensures we have first results our users can make
>> use of very early in the process and don't have to throw all code away
>> if we run out of time.
>> 
>> 
>> Please use the time to learn more about Apache CouchDB, read:
>> 
>> - http://couchdb.apache.org/bylaws.html
>> - http://couchdb.apache.org/conduct.html
>> 
>> We will invite you to our Fauxton standup next week or the following
>> one, I will contact you a few days before. It is 16:00 (Berlin
>> Timezone) on Google Hangouts.
>> 
>> Best,
>> Robert
>> 
>> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>> Dear all,
>>> 
>>> Thank you very much for supporting me to achieve this success in GSoC
>> 2015.
>>> I will not get accepted for GSoC 2015 without all your great help.
>> Special
>>> thanks should go to Robert and Alexander who guide me really well and
>> help
>>> me to understand the project and create a good proposal for the project.
>>> 
>>> Looking forward to start the project and working with you all. Thank you
>>> very much again.
>>> 
>>> 
>>> Thank you
>>> 
>>> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> 
>>>> Problem solved :) thank you very much for the help Robert.
>>>> 
>>>> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>>>> 
>>>>> Hi Dulanga,
>>>>> 
>>>>> Given you named your module `documents` you must have your main less
>>>>> file for the module in `assets/less` and name it `documents.less`.
>>>>> 
>>>>> Example:
>>>>> 
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>>>> 
>>>>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>>>>> wrote:
>>>>>> Hi Robert,
>>>>>> 
>>>>>> By following given links and playing around with the code, I could
>>>>>> successfully implement a react component and display a text in the
>>>>>> dashboard. I added a new dashboard.less file to apply styles for
>> that.
>>>>> But
>>>>>> it didn't work. Is there any configurations to do before using those
>>>>> less
>>>>>> files for the styles? As a next step, I am hoping to implement some
>>>>> complex
>>>>>> components. Specially, some movable items with add and remove
>> features
>>>>> as
>>>>>> Alex suggested.
>>>>>> 
>>>>>> Best Regards
>>>>>> 
>>>>>> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
>> wadsashika@gmail.com
>>>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> Thank you very much for your valuable ideas Alex. As we discussed in
>>>>>>> IRC, I will move into implementing basic structure of the dashboard
>>>>>>> rather than bothering about widget design. After doing that, we can
>> go
>>>>>>> into widgets.
>>>>>>> 
>>>>>>> Cheers
>>>>>>> 
>>>>>>> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>>>>>>>> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>>>>> wadsashika@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> 
>> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>>>>>>>> 
>>>>>>>> http://i.imgur.com/FFiIpbv.png
>>>>>>>> 
>>>>>>>> 1. Widgets customization button shouldn't consume so much valuable
>>>>> space.
>>>>>>>> 2. These buttons are duplicates sidebar menu items without giving
>> any
>>>>>>>> benefits.
>>>>>>>> 3. 10 active replication are cool, but which are there? I to get
>> this
>>>>>>>> I need to click more which isn't much different from click on
>> Active
>>>>>>>> Tasks sidebar menu item and select filter by replication tasks.
>>>>>>>> Dashboard should just works and not require any actions from use
>>>>> side.
>>>>>>>> If user click on widget and leaves it - dashboard main goal is
>>>>> failed.
>>>>>>>> 4. Active tasks are already running (: There couldn't be active
>>>>>>>> stopped ones. Also, here you can show active replications and add
>>>>> some
>>>>>>>> filter. Yes, it will duplicate an active tasks page at some
>> points,
>>>>>>>> but the difference is in short summary of the recent activity
>> shaped
>>>>>>>> into compact form.
>>>>>>>> 5. Recently visited databases cool, but are they be only 4? May
>> be 10
>>>>>>>> or 20? How about search field to filter this list as well?
>>>>>>>> 6. Again button that leads to some other page. Why not just a
>> simple
>>>>>>>> list users and a form to search and register new ones?
>>>>>>>> 7. Same problem. Why not a form to instantly run a replication?
>> If it
>>>>>>>> will be a replication widget, it could also steal a part of
>> features
>>>>>>>> from active tasks widget to show only replications.
>>>>>>>> 
>>>>>>>> --
>>>>>>>> ,,,^..^,,,
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> W. A. Dulanga Sashika,
>>>>>>> Undergraduate Student,
>>>>>>> Department of Computer Science and Engineering,
>>>>>>> University of Moratuwa.
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> W. A. Dulanga Sashika,
>>>>>> Undergraduate Student,
>>>>>> Department of Computer Science and Engineering,
>>>>>> University of Moratuwa.
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> W. A. Dulanga Sashika,
>>>> Undergraduate Student,
>>>> Department of Computer Science and Engineering,
>>>> University of Moratuwa.
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>> 
> 
> 
> 
> -- 
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi all,

I implemented the first widget in the dashboard. You can find it in
https://github.com/wadsashika/couchdb-fauxton/tree/2214-Dashboard-as-main-page
I didn't send a PR since I need to test the functionality more. I couldn't
generate any active tasks to test this. Michelle told me about two way to
generate active tasks. Now I am trying to do that. If you have any
suggestions to do it in easy way, please help me. And really sorry for the
late reply.

Cheers :)

On Thu, Apr 30, 2015 at 7:33 PM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga, Hi Nadeeshaan,
>
> welcome! :)
>
> Michelle, Ben and me will mentor this summer. And the community
> bonding period just started!
>
> We will help you regarding the design of your widgets and revision
> browser and we will try to provide feedback on your code on a daily
> basis - that means that we either will comment on your branch on
> GitHub or an open PR on a daily basis.
>
> You might already know that writing unit and integration tests is an
> absolute must for getting code merged into master.
>
> The goal is to make small steps in an iterative way and get the MVP
> merged as soon as possible. After that we will iterate and can add
> more features. This ensures we have first results our users can make
> use of very early in the process and don't have to throw all code away
> if we run out of time.
>
>
> Please use the time to learn more about Apache CouchDB, read:
>
> - http://couchdb.apache.org/bylaws.html
> - http://couchdb.apache.org/conduct.html
>
> We will invite you to our Fauxton standup next week or the following
> one, I will contact you a few days before. It is 16:00 (Berlin
> Timezone) on Google Hangouts.
>
> Best,
> Robert
>
> On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Dear all,
> >
> > Thank you very much for supporting me to achieve this success in GSoC
> 2015.
> > I will not get accepted for GSoC 2015 without all your great help.
> Special
> > thanks should go to Robert and Alexander who guide me really well and
> help
> > me to understand the project and create a good proposal for the project.
> >
> > Looking forward to start the project and working with you all. Thank you
> > very much again.
> >
> >
> > Thank you
> >
> > On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
> > wrote:
> >
> >> Problem solved :) thank you very much for the help Robert.
> >>
> >> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >>
> >>> Hi Dulanga,
> >>>
> >>> Given you named your module `documents` you must have your main less
> >>> file for the module in `assets/less` and name it `documents.less`.
> >>>
> >>> Example:
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
> >>>
> >>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
> >>> wrote:
> >>> > Hi Robert,
> >>> >
> >>> > By following given links and playing around with the code, I could
> >>> > successfully implement a react component and display a text in the
> >>> > dashboard. I added a new dashboard.less file to apply styles for
> that.
> >>> But
> >>> > it didn't work. Is there any configurations to do before using those
> >>> less
> >>> > files for the styles? As a next step, I am hoping to implement some
> >>> complex
> >>> > components. Specially, some movable items with add and remove
> features
> >>> as
> >>> > Alex suggested.
> >>> >
> >>> > Best Regards
> >>> >
> >>> > On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <
> wadsashika@gmail.com
> >>> >
> >>> > wrote:
> >>> >
> >>> >> Thank you very much for your valuable ideas Alex. As we discussed in
> >>> >> IRC, I will move into implementing basic structure of the dashboard
> >>> >> rather than bothering about widget design. After doing that, we can
> go
> >>> >> into widgets.
> >>> >>
> >>> >> Cheers
> >>> >>
> >>> >> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
> >>> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
> >>> wadsashika@gmail.com>
> >>> >> > wrote:
> >>> >> >>
> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> >>> >> >
> >>> >> > http://i.imgur.com/FFiIpbv.png
> >>> >> >
> >>> >> > 1. Widgets customization button shouldn't consume so much valuable
> >>> space.
> >>> >> > 2. These buttons are duplicates sidebar menu items without giving
> any
> >>> >> > benefits.
> >>> >> > 3. 10 active replication are cool, but which are there? I to get
> this
> >>> >> > I need to click more which isn't much different from click on
> Active
> >>> >> > Tasks sidebar menu item and select filter by replication tasks.
> >>> >> > Dashboard should just works and not require any actions from use
> >>> side.
> >>> >> > If user click on widget and leaves it - dashboard main goal is
> >>> failed.
> >>> >> > 4. Active tasks are already running (: There couldn't be active
> >>> >> > stopped ones. Also, here you can show active replications and add
> >>> some
> >>> >> > filter. Yes, it will duplicate an active tasks page at some
> points,
> >>> >> > but the difference is in short summary of the recent activity
> shaped
> >>> >> > into compact form.
> >>> >> > 5. Recently visited databases cool, but are they be only 4? May
> be 10
> >>> >> > or 20? How about search field to filter this list as well?
> >>> >> > 6. Again button that leads to some other page. Why not just a
> simple
> >>> >> > list users and a form to search and register new ones?
> >>> >> > 7. Same problem. Why not a form to instantly run a replication?
> If it
> >>> >> > will be a replication widget, it could also steal a part of
> features
> >>> >> > from active tasks widget to show only replications.
> >>> >> >
> >>> >> > --
> >>> >> > ,,,^..^,,,
> >>> >> >
> >>> >>
> >>> >>
> >>> >> --
> >>> >> W. A. Dulanga Sashika,
> >>> >> Undergraduate Student,
> >>> >> Department of Computer Science and Engineering,
> >>> >> University of Moratuwa.
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > W. A. Dulanga Sashika,
> >>> > Undergraduate Student,
> >>> > Department of Computer Science and Engineering,
> >>> > University of Moratuwa.
> >>>
> >>
> >>
> >>
> >> --
> >> W. A. Dulanga Sashika,
> >> Undergraduate Student,
> >> Department of Computer Science and Engineering,
> >> University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga, Hi Nadeeshaan,

welcome! :)

Michelle, Ben and me will mentor this summer. And the community
bonding period just started!

We will help you regarding the design of your widgets and revision
browser and we will try to provide feedback on your code on a daily
basis - that means that we either will comment on your branch on
GitHub or an open PR on a daily basis.

You might already know that writing unit and integration tests is an
absolute must for getting code merged into master.

The goal is to make small steps in an iterative way and get the MVP
merged as soon as possible. After that we will iterate and can add
more features. This ensures we have first results our users can make
use of very early in the process and don't have to throw all code away
if we run out of time.


Please use the time to learn more about Apache CouchDB, read:

- http://couchdb.apache.org/bylaws.html
- http://couchdb.apache.org/conduct.html

We will invite you to our Fauxton standup next week or the following
one, I will contact you a few days before. It is 16:00 (Berlin
Timezone) on Google Hangouts.

Best,
Robert

On Tue, Apr 28, 2015 at 6:03 AM, Dulanga Sashika <wa...@gmail.com> wrote:
> Dear all,
>
> Thank you very much for supporting me to achieve this success in GSoC 2015.
> I will not get accepted for GSoC 2015 without all your great help. Special
> thanks should go to Robert and Alexander who guide me really well and help
> me to understand the project and create a good proposal for the project.
>
> Looking forward to start the project and working with you all. Thank you
> very much again.
>
>
> Thank you
>
> On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
>> Problem solved :) thank you very much for the help Robert.
>>
>> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>
>>> Hi Dulanga,
>>>
>>> Given you named your module `documents` you must have your main less
>>> file for the module in `assets/less` and name it `documents.less`.
>>>
>>> Example:
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>>
>>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> > Hi Robert,
>>> >
>>> > By following given links and playing around with the code, I could
>>> > successfully implement a react component and display a text in the
>>> > dashboard. I added a new dashboard.less file to apply styles for that.
>>> But
>>> > it didn't work. Is there any configurations to do before using those
>>> less
>>> > files for the styles? As a next step, I am hoping to implement some
>>> complex
>>> > components. Specially, some movable items with add and remove features
>>> as
>>> > Alex suggested.
>>> >
>>> > Best Regards
>>> >
>>> > On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <wadsashika@gmail.com
>>> >
>>> > wrote:
>>> >
>>> >> Thank you very much for your valuable ideas Alex. As we discussed in
>>> >> IRC, I will move into implementing basic structure of the dashboard
>>> >> rather than bothering about widget design. After doing that, we can go
>>> >> into widgets.
>>> >>
>>> >> Cheers
>>> >>
>>> >> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>>> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>>> wadsashika@gmail.com>
>>> >> > wrote:
>>> >> >> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>>> >> >
>>> >> > http://i.imgur.com/FFiIpbv.png
>>> >> >
>>> >> > 1. Widgets customization button shouldn't consume so much valuable
>>> space.
>>> >> > 2. These buttons are duplicates sidebar menu items without giving any
>>> >> > benefits.
>>> >> > 3. 10 active replication are cool, but which are there? I to get this
>>> >> > I need to click more which isn't much different from click on Active
>>> >> > Tasks sidebar menu item and select filter by replication tasks.
>>> >> > Dashboard should just works and not require any actions from use
>>> side.
>>> >> > If user click on widget and leaves it - dashboard main goal is
>>> failed.
>>> >> > 4. Active tasks are already running (: There couldn't be active
>>> >> > stopped ones. Also, here you can show active replications and add
>>> some
>>> >> > filter. Yes, it will duplicate an active tasks page at some points,
>>> >> > but the difference is in short summary of the recent activity shaped
>>> >> > into compact form.
>>> >> > 5. Recently visited databases cool, but are they be only 4? May be 10
>>> >> > or 20? How about search field to filter this list as well?
>>> >> > 6. Again button that leads to some other page. Why not just a simple
>>> >> > list users and a form to search and register new ones?
>>> >> > 7. Same problem. Why not a form to instantly run a replication? If it
>>> >> > will be a replication widget, it could also steal a part of features
>>> >> > from active tasks widget to show only replications.
>>> >> >
>>> >> > --
>>> >> > ,,,^..^,,,
>>> >> >
>>> >>
>>> >>
>>> >> --
>>> >> W. A. Dulanga Sashika,
>>> >> Undergraduate Student,
>>> >> Department of Computer Science and Engineering,
>>> >> University of Moratuwa.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > W. A. Dulanga Sashika,
>>> > Undergraduate Student,
>>> > Department of Computer Science and Engineering,
>>> > University of Moratuwa.
>>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Dear all,

Thank you very much for supporting me to achieve this success in GSoC 2015.
I will not get accepted for GSoC 2015 without all your great help. Special
thanks should go to Robert and Alexander who guide me really well and help
me to understand the project and create a good proposal for the project.

Looking forward to start the project and working with you all. Thank you
very much again.


Thank you

On Sun, Apr 5, 2015 at 11:08 AM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Problem solved :) thank you very much for the help Robert.
>
> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Hi Dulanga,
>>
>> Given you named your module `documents` you must have your main less
>> file for the module in `assets/less` and name it `documents.less`.
>>
>> Example:
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>>
>> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi Robert,
>> >
>> > By following given links and playing around with the code, I could
>> > successfully implement a react component and display a text in the
>> > dashboard. I added a new dashboard.less file to apply styles for that.
>> But
>> > it didn't work. Is there any configurations to do before using those
>> less
>> > files for the styles? As a next step, I am hoping to implement some
>> complex
>> > components. Specially, some movable items with add and remove features
>> as
>> > Alex suggested.
>> >
>> > Best Regards
>> >
>> > On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <wadsashika@gmail.com
>> >
>> > wrote:
>> >
>> >> Thank you very much for your valuable ideas Alex. As we discussed in
>> >> IRC, I will move into implementing basic structure of the dashboard
>> >> rather than bothering about widget design. After doing that, we can go
>> >> into widgets.
>> >>
>> >> Cheers
>> >>
>> >> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >> > wrote:
>> >> >> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>> >> >
>> >> > http://i.imgur.com/FFiIpbv.png
>> >> >
>> >> > 1. Widgets customization button shouldn't consume so much valuable
>> space.
>> >> > 2. These buttons are duplicates sidebar menu items without giving any
>> >> > benefits.
>> >> > 3. 10 active replication are cool, but which are there? I to get this
>> >> > I need to click more which isn't much different from click on Active
>> >> > Tasks sidebar menu item and select filter by replication tasks.
>> >> > Dashboard should just works and not require any actions from use
>> side.
>> >> > If user click on widget and leaves it - dashboard main goal is
>> failed.
>> >> > 4. Active tasks are already running (: There couldn't be active
>> >> > stopped ones. Also, here you can show active replications and add
>> some
>> >> > filter. Yes, it will duplicate an active tasks page at some points,
>> >> > but the difference is in short summary of the recent activity shaped
>> >> > into compact form.
>> >> > 5. Recently visited databases cool, but are they be only 4? May be 10
>> >> > or 20? How about search field to filter this list as well?
>> >> > 6. Again button that leads to some other page. Why not just a simple
>> >> > list users and a form to search and register new ones?
>> >> > 7. Same problem. Why not a form to instantly run a replication? If it
>> >> > will be a replication widget, it could also steal a part of features
>> >> > from active tasks widget to show only replications.
>> >> >
>> >> > --
>> >> > ,,,^..^,,,
>> >> >
>> >>
>> >>
>> >> --
>> >> W. A. Dulanga Sashika,
>> >> Undergraduate Student,
>> >> Department of Computer Science and Engineering,
>> >> University of Moratuwa.
>> >>
>> >
>> >
>> >
>> > --
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Problem solved :) thank you very much for the help Robert.

On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga,
>
> Given you named your module `documents` you must have your main less
> file for the module in `assets/less` and name it `documents.less`.
>
> Example:
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less
>
> On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi Robert,
> >
> > By following given links and playing around with the code, I could
> > successfully implement a react component and display a text in the
> > dashboard. I added a new dashboard.less file to apply styles for that.
> But
> > it didn't work. Is there any configurations to do before using those less
> > files for the styles? As a next step, I am hoping to implement some
> complex
> > components. Specially, some movable items with add and remove features as
> > Alex suggested.
> >
> > Best Regards
> >
> > On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <wa...@gmail.com>
> > wrote:
> >
> >> Thank you very much for your valuable ideas Alex. As we discussed in
> >> IRC, I will move into implementing basic structure of the dashboard
> >> rather than bothering about widget design. After doing that, we can go
> >> into widgets.
> >>
> >> Cheers
> >>
> >> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <
> wadsashika@gmail.com>
> >> > wrote:
> >> >> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> >> >
> >> > http://i.imgur.com/FFiIpbv.png
> >> >
> >> > 1. Widgets customization button shouldn't consume so much valuable
> space.
> >> > 2. These buttons are duplicates sidebar menu items without giving any
> >> > benefits.
> >> > 3. 10 active replication are cool, but which are there? I to get this
> >> > I need to click more which isn't much different from click on Active
> >> > Tasks sidebar menu item and select filter by replication tasks.
> >> > Dashboard should just works and not require any actions from use side.
> >> > If user click on widget and leaves it - dashboard main goal is failed.
> >> > 4. Active tasks are already running (: There couldn't be active
> >> > stopped ones. Also, here you can show active replications and add some
> >> > filter. Yes, it will duplicate an active tasks page at some points,
> >> > but the difference is in short summary of the recent activity shaped
> >> > into compact form.
> >> > 5. Recently visited databases cool, but are they be only 4? May be 10
> >> > or 20? How about search field to filter this list as well?
> >> > 6. Again button that leads to some other page. Why not just a simple
> >> > list users and a form to search and register new ones?
> >> > 7. Same problem. Why not a form to instantly run a replication? If it
> >> > will be a replication widget, it could also steal a part of features
> >> > from active tasks widget to show only replications.
> >> >
> >> > --
> >> > ,,,^..^,,,
> >> >
> >>
> >>
> >> --
> >> W. A. Dulanga Sashika,
> >> Undergraduate Student,
> >> Department of Computer Science and Engineering,
> >> University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga,

Given you named your module `documents` you must have your main less
file for the module in `assets/less` and name it `documents.less`.

Example: https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/assets/less/documents.less

On Sat, Apr 4, 2015 at 7:54 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> By following given links and playing around with the code, I could
> successfully implement a react component and display a text in the
> dashboard. I added a new dashboard.less file to apply styles for that. But
> it didn't work. Is there any configurations to do before using those less
> files for the styles? As a next step, I am hoping to implement some complex
> components. Specially, some movable items with add and remove features as
> Alex suggested.
>
> Best Regards
>
> On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
>> Thank you very much for your valuable ideas Alex. As we discussed in
>> IRC, I will move into implementing basic structure of the dashboard
>> rather than bothering about widget design. After doing that, we can go
>> into widgets.
>>
>> Cheers
>>
>> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
>> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <wa...@gmail.com>
>> > wrote:
>> >> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>> >
>> > http://i.imgur.com/FFiIpbv.png
>> >
>> > 1. Widgets customization button shouldn't consume so much valuable space.
>> > 2. These buttons are duplicates sidebar menu items without giving any
>> > benefits.
>> > 3. 10 active replication are cool, but which are there? I to get this
>> > I need to click more which isn't much different from click on Active
>> > Tasks sidebar menu item and select filter by replication tasks.
>> > Dashboard should just works and not require any actions from use side.
>> > If user click on widget and leaves it - dashboard main goal is failed.
>> > 4. Active tasks are already running (: There couldn't be active
>> > stopped ones. Also, here you can show active replications and add some
>> > filter. Yes, it will duplicate an active tasks page at some points,
>> > but the difference is in short summary of the recent activity shaped
>> > into compact form.
>> > 5. Recently visited databases cool, but are they be only 4? May be 10
>> > or 20? How about search field to filter this list as well?
>> > 6. Again button that leads to some other page. Why not just a simple
>> > list users and a form to search and register new ones?
>> > 7. Same problem. Why not a form to instantly run a replication? If it
>> > will be a replication widget, it could also steal a part of features
>> > from active tasks widget to show only replications.
>> >
>> > --
>> > ,,,^..^,,,
>> >
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

By following given links and playing around with the code, I could
successfully implement a react component and display a text in the
dashboard. I added a new dashboard.less file to apply styles for that. But
it didn't work. Is there any configurations to do before using those less
files for the styles? As a next step, I am hoping to implement some complex
components. Specially, some movable items with add and remove features as
Alex suggested.

Best Regards

On Sat, Mar 28, 2015 at 12:49 AM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Thank you very much for your valuable ideas Alex. As we discussed in
> IRC, I will move into implementing basic structure of the dashboard
> rather than bothering about widget design. After doing that, we can go
> into widgets.
>
> Cheers
>
> On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <wa...@gmail.com>
> > wrote:
> >> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> >
> > http://i.imgur.com/FFiIpbv.png
> >
> > 1. Widgets customization button shouldn't consume so much valuable space.
> > 2. These buttons are duplicates sidebar menu items without giving any
> > benefits.
> > 3. 10 active replication are cool, but which are there? I to get this
> > I need to click more which isn't much different from click on Active
> > Tasks sidebar menu item and select filter by replication tasks.
> > Dashboard should just works and not require any actions from use side.
> > If user click on widget and leaves it - dashboard main goal is failed.
> > 4. Active tasks are already running (: There couldn't be active
> > stopped ones. Also, here you can show active replications and add some
> > filter. Yes, it will duplicate an active tasks page at some points,
> > but the difference is in short summary of the recent activity shaped
> > into compact form.
> > 5. Recently visited databases cool, but are they be only 4? May be 10
> > or 20? How about search field to filter this list as well?
> > 6. Again button that leads to some other page. Why not just a simple
> > list users and a form to search and register new ones?
> > 7. Same problem. Why not a form to instantly run a replication? If it
> > will be a replication widget, it could also steal a part of features
> > from active tasks widget to show only replications.
> >
> > --
> > ,,,^..^,,,
> >
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Thank you very much for your valuable ideas Alex. As we discussed in
IRC, I will move into implementing basic structure of the dashboard
rather than bothering about widget design. After doing that, we can go
into widgets.

Cheers

On 3/27/15, Alexander Shorin <kx...@gmail.com> wrote:
> On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>
> http://i.imgur.com/FFiIpbv.png
>
> 1. Widgets customization button shouldn't consume so much valuable space.
> 2. These buttons are duplicates sidebar menu items without giving any
> benefits.
> 3. 10 active replication are cool, but which are there? I to get this
> I need to click more which isn't much different from click on Active
> Tasks sidebar menu item and select filter by replication tasks.
> Dashboard should just works and not require any actions from use side.
> If user click on widget and leaves it - dashboard main goal is failed.
> 4. Active tasks are already running (: There couldn't be active
> stopped ones. Also, here you can show active replications and add some
> filter. Yes, it will duplicate an active tasks page at some points,
> but the difference is in short summary of the recent activity shaped
> into compact form.
> 5. Recently visited databases cool, but are they be only 4? May be 10
> or 20? How about search field to filter this list as well?
> 6. Again button that leads to some other page. Why not just a simple
> list users and a form to search and register new ones?
> 7. Same problem. Why not a form to instantly run a replication? If it
> will be a replication widget, it could also steal a part of features
> from active tasks widget to show only replications.
>
> --
> ,,,^..^,,,
>


-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Alexander Shorin <kx...@gmail.com>]

On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0

http://i.imgur.com/FFiIpbv.png

1. Widgets customization button shouldn't consume so much valuable space.
2. These buttons are duplicates sidebar menu items without giving any benefits.
3. 10 active replication are cool, but which are there? I to get this
I need to click more which isn't much different from click on Active
Tasks sidebar menu item and select filter by replication tasks.
Dashboard should just works and not require any actions from use side.
If user click on widget and leaves it - dashboard main goal is failed.
4. Active tasks are already running (: There couldn't be active
stopped ones. Also, here you can show active replications and add some
filter. Yes, it will duplicate an active tasks page at some points,
but the difference is in short summary of the recent activity shaped
into compact form.
5. Recently visited databases cool, but are they be only 4? May be 10
or 20? How about search field to filter this list as well?
6. Again button that leads to some other page. Why not just a simple
list users and a form to search and register new ones?
7. Same problem. Why not a form to instantly run a replication? If it
will be a replication widget, it could also steal a part of features
from active tasks widget to show only replications.

--
,,,^..^,,,

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Actually I am the one who made the mistake here. I didn't explain the
functions properly. And you didn't discourage me :) every idea coming from
you and others are really valuable to me.

My development environment is Ubuntu and I design this mock up in Windows.
So I couldn't find find the icons and fonts of fauxton :) That's the main
reason to use these icons and fonts. Anyway, we can use Fauxton's icons and
fonts in the implementation :) and Thank you very much for sharing those
detail with me.

I think it is better to explain what had in my mind when I design this at
least now :)

Recently Visited Database table - As you said, each row will link to the
database and user can go to the database by clicking on it.

Running Active Tasks table - This will only show an overview of active
tasks. (Content will finalized after talking with others)

Number of Nodes in Cluster - This will show the number of nodes in the
cluster and by clicking on "More.." link, it will direct to the Cluster
management page.

Number of Running Replications - This will show the count of running
replication. As I think we cannot see running replications in a separate
page. In that case, "More.." link should be removed. Or we direct user to
the Replication page to make replications of databases.

All the other widgets will direct to the corresponding pages except "Custom
Widgets". It will have a separate page as I described earlier.

I think we should talk more about "Custom Widgets". I am little bit
confused about that.

Thank You


On Mon, Mar 23, 2015 at 4:56 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga,
>
> exactly my opinion! I agree! Sorry if I my response sounded discouraging,
> but I think we share the exactly same opinion!
>
> Just for clarification - I hope my mail was not received in another way:
>
> Regarding the font: I just wanted to share the knowledge for the future
> (implementation step) that we have an own icon font . I already figured
> that you probably did not know about it and wanted to share the knowledge
> as it will your life a lot easier during the implementation. Maybe we can
> also add some of your icons to it if they fit better to the use case :)
>
> Custom widgets: I asked the question as I am are not sure on my own what
> could happen or how this could integrate into Fauxton at all :) We could
> probably use the addon-architecture or requireExtensions which makes
> Fauxton extensible at build time, but probably it is technically not
> possible to add them at runtime. This was not obvious to me until I saw the
> mock up, thanks again for creating it.  :)
>
>
> For the recently visited databases: I would be interested in "# of docs and
> name of the database, with a link to the database", like in your proposal
> For the Active tasks: just a short overview what is currently running, I
> also really like your proposal
>
> Maybe Alex can chime in and give some suggestion regarding the content for
> active tasks and recently visited databases, as he is a real power user :)
>
> On Sun, Mar 22, 2015 at 5:23 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
> > Hi Robert,
> >
> > I made this design using Photoshop. Therefore, I used these icons and
> fonts
> > just to show how it looks like. Since this is the first design, I thought
> > it will not be a big issue. We can change them at any time.
> > Previously we talked about "Custom Widgets". As I understand it, there
> will
> > be a option as "custom widgets" in the dashboard and if we click on that,
> > it will go to a page where we can select/remove widgets from the
> dashboard.
> > If yours and Alex's intention about "Custom Widgets" are different from
> > this, please correct me :) I might be wrong about that.
> > Another thing is that, I do not know exactly what are the important items
> > to include into "Active Tasks" and "Recently Visited Databases" tables. I
> > put items that came into my mind as important. We can change them also.
> > Actually this one is for just to get an idea about the dashboard. As you
> > said, this will help to think about problems that might occur. All we
> need
> > is the ideas from the community :) then we can come up with a better
> design
> > than this.
> >
> > Regards
> >
> > On Sun, Mar 22, 2015 at 5:28 AM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >
> > > Cool! Thank you!
> > >
> > > Creating a mock-up is a good way to get some initial feedback and
> > > helps to think about problems that might occur. Probably Sean or
> > > another designer will take a final look at the final work you create
> > > in terms of design.
> > >
> > > One question that came to my mind while looking at the dashboard was:
> > > "what happens if we click on custom widgets?"
> > >
> > > Btw have you seen our icon fonts?
> > >
> > > We have an own at
> > >
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/assets/fonts/styleguide/fauxtonicon-preview.html
> > > and additionally support the glyphicons from bootstrap 2.3:
> > > http://getbootstrap.com/2.3.2/base-css.html#icons
> > >
> > >
> > > Best,
> > > Robert
> > >
> > > On Sat, Mar 21, 2015 at 9:00 PM, Dulanga Sashika <wadsashika@gmail.com
> >
> > > wrote:
> > > > Hi Robert,
> > > >
> > > > Here is the mock up I designed for the dashboard.
> > > > https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> > > >
> > > > Please give some comments and we can change this later by discussing
> > the
> > > > important facts that we should show in the dashboard. For now I
> > designed
> > > a
> > > > mock up only for dashboard and I can make designs for each widgets
> > later.
> > > >
> > > > Thank You
> > > >
> > > >
> > > > On Fri, Mar 20, 2015 at 8:12 PM, Robert Kowalski <ro...@kowalski.gd>
> > > wrote:
> > > >
> > > >> Cool thank you!
> > > >>
> > > >> Yes I also did not know until someone told me 2 months ago :)
> > > >>
> > > >> On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <
> > wadsashika@gmail.com>
> > > >> wrote:
> > > >> > Hi Robert,
> > > >> >
> > > >> > Thank you very much for the help. I can carry on from there now.
> > > >> Actually I
> > > >> > didn't know that this mailing list does not supported for
> > attachments.
> > > >> Here
> > > >> > is the screenshots I uploaded.
> > > >> >
> > > >> > img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
> > > >> > img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
> > > >> > img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
> > > >> > img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
> > > >> > img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
> > > >> > img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
> > > >> >
> > > >> > And I will share the proposal ASAP with you.
> > > >> >
> > > >> > Thank you
> > > >> >
> > > >> > On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <rok@kowalski.gd
> >
> > > >> wrote:
> > > >> >
> > > >> >> Hi Dulanga,
> > > >> >>
> > > >> >> glad you figured it out while I was on a train! :)
> > > >> >>
> > > >> >> Can you upload the pictures to something like box.com / dropbox
> or
> > > an
> > > >> >> image hoster as the list does not support attachments?
> > > >> >>
> > > >> >> We are storing our react components in files like
> > > >> >>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
> > > >> >>
> > > >> >> To render them we still have to wrap them in Backbone Views - as
> > our
> > > >> >> framework is built for Backbone views. The backbone view files
> are
> > > >> >> usually called `views.js`. This will go away soon but currently
> it
> > is
> > > >> >> the way to go:
> > > >> >>
> > > >> >>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> > > >> >>
> > > >> >> which calls this at the bottom of
> > > >> `app/addons/cors/components.react.jsx`:
> > > >> >>
> > > >> >>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
> > > >> >>
> > > >> >>
> > > >> >> In
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> > > >> >> `this.el` references the DOM-Node of the Backbone view in which
> > then
> > > >> >> the React Component is rendered into.
> > > >> >>
> > > >> >>
> > > >> >> Regarding the proposal:
> > > >> >>
> > > >> >> I am happy to help you with your proposal it would be nice to
> have
> > an
> > > >> >> option that makes it easy to leave comments (e.g google docs)
> > > >> >>
> > > >> >> Best,
> > > >> >> Robert
> > > >> >>
> > > >> >> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <
> > > wadsashika@gmail.com>
> > > >> >> wrote:
> > > >> >> > Hi,
> > > >> >> > Here I attached the screen shots of Dashboard menu item. Now
> its
> > > >> working.
> > > >> >> > Now I want to know that, if I need to implement react
> component,
> > > where
> > > >> >> > should I put it? And how can I access that to render the view?
> > just
> > > >> give
> > > >> >> me
> > > >> >> > some hints and I can carry on from there.
> > > >> >> >
> > > >> >> > Regards
> > > >> >> >
> > > >> >> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <
> > > >> wadsashika@gmail.com>
> > > >> >> > wrote:
> > > >> >> >>
> > > >> >> >> Hey Robert, problem solved.. :)
> > > >> >> >>
> > > >> >> >>
> > > >> >> >> Regards.
> > > >> >> >>
> > > >> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <
> > > >> wadsashika@gmail.com>
> > > >> >> >> wrote:
> > > >> >> >>>
> > > >> >> >>> Hi Robert,
> > > >> >> >>>
> > > >> >> >>> Now I am trying to create a new menu item for dashboard and
> > > >> implement a
> > > >> >> >>> react component as you said. But now I am stuck in some place
> > and
> > > >> >> couldn't
> > > >> >> >>> figure out the problem yet. Here is the problem I had in
> > > process. I
> > > >> >> added
> > > >> >> >>> dashboard menu item and added route and view for that. And i
> > > change
> > > >> >> the code
> > > >> >> >>> to render dashboard when we enter http://localhost:8000 . As
> > in
> > > >> img1
> > > >> >> and
> > > >> >> >>> img2, it doesn't show the view I created. But when I click on
> > > >> another
> > > >> >> menu
> > > >> >> >>> item and come back to the dashboard, it shows the breadcrumb
> of
> > > >> >> previous
> > > >> >> >>> pages as img 3 and 4. As in
> > > >> >> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> > > >> >> >>> , I called the new Dashboard.view() which is a component in
> my
> > > >> >> view.js. But
> > > >> >> >>> in the console, it shows Uncaught Type error. Did I miss any
> > > >> >> configuration
> > > >> >> >>> thing or did I do it wrong?
> > > >> >> >>>
> > > >> >> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
> > > >> >> wadsashika@gmail.com>
> > > >> >> >>> wrote:
> > > >> >> >>>>
> > > >> >> >>>> Hi Robert,
> > > >> >> >>>>
> > > >> >> >>>> Thank you very much for the reference. I started to write
> the
> > > >> proposal
> > > >> >> >>>> today. I hope you will help to write this proposal by
> > reviewing
> > > >> it.
> > > >> >> I will
> > > >> >> >>>> share it with you after complete the draft of the proposal.
> > > >> >> >>>>
> > > >> >> >>>> Thank you
> > > >> >> >>>>
> > > >> >> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <
> > > rok@kowalski.gd>
> > > >> >> >>>> wrote:
> > > >> >> >>>>>
> > > >> >> >>>>> Some of you asked for a template for their proposals, here
> is
> > > what
> > > >> >> I've
> > > >> >> >>>>> found:
> > > >> >> >>>>>
> > > >> >> >>>>>
> > http://community.staging.apache.org/gsoc#application-template
> > > >> >> >>>>>
> > > >> >> >>>>> Best,
> > > >> >> >>>>> Robert
> > > >> >> >>>>>
> > > >> >> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <
> > > >> rok@kowalski.gd>
> > > >> >> >>>>> wrote:
> > > >> >> >>>>> > Wow you are making very good progress!
> > > >> >> >>>>> >
> > > >> >> >>>>> > We have our weekly status meetup tomorrow (see [1] for
> the
> > > time
> > > >> in
> > > >> >> >>>>> > your timezone), feel free to join, meet other project
> > members
> > > >> and
> > > >> >> >>>>> > learn what the project is currently doing next to the
> > Summer
> > > of
> > > >> >> Code.
> > > >> >> >>>>> >
> > > >> >> >>>>> > I will also be around 1hr earlier to answer all your
> > > questions
> > > >> and
> > > >> >> >>>>> > discuss our next steps.
> > > >> >> >>>>> >
> > > >> >> >>>>> >
> > > >> >> >>>>> > [1]
> > > >> >> >>>>> >
> > > >> >>
> > > >>
> > >
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > > >> >> >>>>> >
> > > >> >> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
> > > >> >> >>>>> > <wa...@gmail.com> wrote:
> > > >> >> >>>>> >> Hi Robert,
> > > >> >> >>>>> >>
> > > >> >> >>>>> >> Here is the current status of the checklist :)
> > > >> >> >>>>> >>
> > > >> >> >>>>> >>  - check out the active tasks api (linked on top of this
> > > mail)
> > > >> -
> > > >> >> >>>>> >> (finished)
> > > >> >> >>>>> >>  - a mockup showing some widgets and how they could look
> > > like -
> > > >> >> >>>>> >> (started
> > > >> >> >>>>> >> but not finished yet)
> > > >> >> >>>>> >>  - code React tutorial & read about Flux - (finished)
> > > >> >> >>>>> >>  - take a look how we are using React - (finished)
> > > >> >> >>>>> >>  - create another menu item, called "Dashboard", try to
> > > answer
> > > >> the
> > > >> >> >>>>> >> questions to route.js et al - (started but not finished
> > yet)
> > > >> >> >>>>> >>  - get familiar how we test our code - (finished)
> > > >> >> >>>>> >>  - write an hello world / hello from dulanga component
> > that
> > > is
> > > >> >> >>>>> >> rendered into a screen when opening
> > > http://localhost:8000/dash
> > > >> >> or by
> > > >> >> >>>>> >> clicking on "dashboard" in the sidebar - (started but
> not
> > > >> finished
> > > >> >> >>>>> >> yet)
> > > >> >> >>>>> >>
> > > >> >> >>>>> >> I will do my best to complete all these by tomorrow. If
> I
> > > have
> > > >> any
> > > >> >> >>>>> >> problem,
> > > >> >> >>>>> >> I will trouble you as you wished yesterday :)
> > > >> >> >>>>> >>
> > > >> >> >>>>> >> Thank You
> > > >> >> >>>>> >>
> > > >> >> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <
> > > >> rok@kowalski.gd
> > > >> >> >
> > > >> >> >>>>> >> wrote:
> > > >> >> >>>>> >>
> > > >> >> >>>>> >>> Hi Dulanga,
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> we already talked on irc and you already talked to Alex
> > > >> regarding
> > > >> >> >>>>> >>> features for our dashboard. That's great!
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Some topics will repeat in this mail, but I also would
> > like
> > > >> the
> > > >> >> ML
> > > >> >> >>>>> >>> to
> > > >> >> >>>>> >>> follow our project and additionally add some more
> > in-depth
> > > >> >> >>>>> >>> informations.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Recap & additons
> > > >> >> >>>>> >>> =====
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> As discussed we will work in an iterative approach and
> > add
> > > >> widget
> > > >> >> >>>>> >>> after widget so if we run out of time, we will have
> > > something
> > > >> to
> > > >> >> >>>>> >>> deliver and don't have to throw everything away.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Have you seen the "database" tab or the "config" tab in
> > the
> > > >> >> sidebar
> > > >> >> >>>>> >>> on the
> > > >> >> >>>>> >>> left?
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Those are modules that we can hook into the Fauxton
> > build,
> > > by
> > > >> >> >>>>> >>> configuration. I think the idea is to create a tab
> > > "dashboard"
> > > >> >> >>>>> >>> which
> > > >> >> >>>>> >>> is the default one after opening Fauxton in the
> browser.
> > So
> > > >> you
> > > >> >> >>>>> >>> would
> > > >> >> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Alex ideas so far:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue
> > > there
> > > >> are
> > > >> >> >>>>> >>> some
> > > >> >> >>>>> >>> points about showing stats and log - forget these (:
> > _stats
> > > >> isn't
> > > >> >> >>>>> >>> available for
> > > >> >> >>>>> >>>                    cluster iface and _log is removed.
> but
> > > >> >> recently
> > > >> >> >>>>> >>> visited databases, active tasks and _users/_replicator
> > > quick
> > > >> >> >>>>> >>> management is what could
> > > >> >> >>>>> >>>                    be really handy.
> > > >> >> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not
> > > >> relevant
> > > >> >> >>>>> >>> anymore after backporting some cloudant features
> > > >> >> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a
> > way
> > > >> how
> > > >> >> (:
> > > >> >> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of
> > > widgets,
> > > >> I
> > > >> >> >>>>> >>> believe you could make some builtin and leave a
> template
> > > one
> > > >> to
> > > >> >> let
> > > >> >> >>>>> >>> the end users create
> > > >> >> >>>>> >>>                    their own if they're able/would like
> > > to. in
> > > >> >> >>>>> >>> future
> > > >> >> >>>>> >>> these are could be fauxton plugins or something.
> > > >> >> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also
> nice
> > > idea
> > > >> >> for a
> > > >> >> >>>>> >>> hot
> > > >> >> >>>>> >>> widget.
> > > >> >> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely
> > > help
> > > >> with
> > > >> >> >>>>> >>> that
> > > >> >> >>>>> >>> (add custom widgets on build time) - the build is
> > > complicated,
> > > >> >> but
> > > >> >> >>>>> >>> once explained
> > > >> >> >>>>> >>>                            it should be easy
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> So we have "custom widgets", "cluster
> quick-management",
> > "
> > > >> >> recently
> > > >> >> >>>>> >>> visited databases",  "active tasks" and
> > "_users/_replicator
> > > >> quick
> > > >> >> >>>>> >>> management"
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> I think two good widgets for starting are active tasks
> > and
> > > >> >> recently
> > > >> >> >>>>> >>> visited databases.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> For active tasks we have some nice docs:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> They have an own dedicated page in Fauxton (see
> > > >> >> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick
> > > >> condensed
> > > >> >> >>>>> >>> list
> > > >> >> >>>>> >>> is probably very interesting to users.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> For the recently visited databases we would have to
> store
> > > that
> > > >> >> >>>>> >>> somewhere.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> If you want, you can take an existing page in Fauxton
> and
> > > just
> > > >> >> >>>>> >>> modify
> > > >> >> >>>>> >>> the markup for a design mockup how the widget view may
> > look
> > > >> like.
> > > >> >> >>>>> >>> But
> > > >> >> >>>>> >>> feel also free to use pen/paper or other tools if you
> > like
> > > >> that
> > > >> >> the
> > > >> >> >>>>> >>> most.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> For the mango feature I am currently working on, I took
> > the
> > > >> "edit
> > > >> >> >>>>> >>> view" template on modified the markup using the Chrome
> > > >> inspector
> > > >> >> of
> > > >> >> >>>>> >>> my
> > > >> >> >>>>> >>> browser to collect some first feedback from the project
> > > >> members
> > > >> >> and
> > > >> >> >>>>> >>> my
> > > >> >> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not
> have
> > > any
> > > >> >> >>>>> >>> functionality, but gives other folks a rough idea what
> my
> > > idea
> > > >> >> for
> > > >> >> >>>>> >>> the
> > > >> >> >>>>> >>> feature is.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> the framework and react
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> As I already mentioned we are using React.js.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> It would be nice if you can finish the tutorial at
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> > > >> >> >>>>> >>> until next friday by following the steps and writing
> that
> > > >> code.
> > > >> >> >>>>> >>> After
> > > >> >> >>>>> >>> that, read
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> > > >> >> >>>>> >>> to get a first impression how the Flux pattern works
> that
> > > we
> > > >> are
> > > >> >> >>>>> >>> using.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> After that (if you still have time left) take a look
> on a
> > > >> >> component
> > > >> >> >>>>> >>> that Garren, my coworker refactored from Backbone.js to
> > > React:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Please take a look how the data flows from the
> > Components,
> > > >> using
> > > >> >> >>>>> >>> the
> > > >> >> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to
> > > litter
> > > >> >> >>>>> >>> everything in the code with console.log to see how
> state
> > > >> changes
> > > >> >> >>>>> >>> and
> > > >> >> >>>>> >>> how the data flows.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Hint: it is that element:
> > https://cldup.com/4eCHVt9HHt.png
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> If you still have time, just try to create another menu
> > > item,
> > > >> >> >>>>> >>> called
> > > >> >> >>>>> >>> "Dashboard". Take a look at:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > >
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> to get a first idea how to do that. Some background
> > > >> information:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> base.js - the starting point of our module. basic
> > > >> configuration
> > > >> >> is
> > > >> >> >>>>> >>> done
> > > >> >> >>>>> >>> here
> > > >> >> >>>>> >>> Question: what is `base.js` used for in the case of the
> > > config
> > > >> >> >>>>> >>> module?
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> routes.js - takes care that functions injecting the
> view
> > > into
> > > >> the
> > > >> >> >>>>> >>> layout are called depending on the url given
> > > >> >> >>>>> >>> Question: What happens if I call
> > > `http:localhost:8000/_config`
> > > >> >> and
> > > >> >> >>>>> >>> what happens if you remove the function `apiUrl`?
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> views.js - contains our views - this file contains
> still
> > a
> > > lot
> > > >> >> >>>>> >>> backbone views, which we are currently migrating to
> > react.
> > > >> maybe
> > > >> >> it
> > > >> >> >>>>> >>> makes more sense to take a look at one of our react
> > > >> components:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> and how they are used currently (as we are migrating to
> > > react
> > > >> >> >>>>> >>> currently):
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> The Objects are injected into the closures using AMD:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> assets folder:
> > > >> >> >>>>> >>> contains our less which is compiled to css
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> templates folder:
> > > >> >> >>>>> >>> contains old backbone.js templates, you will not need
> > them
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> tests folder:
> > > >> >> >>>>> >>> contains unit and integration tests, every PR must have
> > > unit
> > > >> >> tests
> > > >> >> >>>>> >>> and
> > > >> >> >>>>> >>> integration tests. If you never wrote tests, we will
> > > explain
> > > >> it
> > > >> >> to
> > > >> >> >>>>> >>> you
> > > >> >> >>>>> >>> - it is easy once you wrote your first few ones.
> > Basically
> > > you
> > > >> >> are
> > > >> >> >>>>> >>> testing each time that if you put something into a
> > > function,
> > > >> the
> > > >> >> >>>>> >>> expected result happens. Or that if you take an
> action, a
> > > >> state
> > > >> >> has
> > > >> >> >>>>> >>> changed.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> You can run the unit tests using `grunt test`
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Single tests are run by:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>> grunt test
> > > >> >> >>>>> >>>
> --file="./app/addons/documents/tests/headerSpec.react.js"
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> or in the browser by test group:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> > > >> >> >>>>> >>> ```
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> (change path to your fauxton directory)
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> The corresponding code is:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> and these tests are a good example how to write a
> simple
> > > test
> > > >> for
> > > >> >> >>>>> >>> the
> > > >> >> >>>>> >>> hello world/hello from dulanga-component:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> First steps:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Create a module `dashboard` that gets displayed in the
> > > >> sidebar.
> > > >> >> The
> > > >> >> >>>>> >>> route http://localhost:8000/dash will render a small
> > React
> > > >> >> >>>>> >>> component
> > > >> >> >>>>> >>> that display "Hello World".
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> If you click on the "Hello World" it ill change the
> > content
> > > >> to:
> > > >> >> >>>>> >>> "Hello
> > > >> >> >>>>> >>> from Dulanga"
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> While we will throw the small component away afterwards
> > we
> > > >> will
> > > >> >> >>>>> >>> build
> > > >> >> >>>>> >>> upon the other code you created. If you have time left,
> > > add a
> > > >> >> test
> > > >> >> >>>>> >>> that the component changes the content.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Meeting Wednesday:
> > > >> >> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> I will be around at least one hour before so we can
> chat.
> > > >> Contact
> > > >> >> >>>>> >>> me
> > > >> >> >>>>> >>> if you would like to chat earlier/later. I am also
> around
> > > the
> > > >> >> other
> > > >> >> >>>>> >>> days on IRC / the mailinglist and feel free to contact
> me
> > > in
> > > >> >> >>>>> >>> #couchdb-dev at any time. If I am not around I will
> > answer
> > > you
> > > >> >> once
> > > >> >> >>>>> >>> I
> > > >> >> >>>>> >>> got online again, as I read the backlog.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>  - check out the active tasks api (linked on top of
> this
> > > mail)
> > > >> >> >>>>> >>>  - a mockup showing some widgets and how they could
> look
> > > like
> > > >> >> >>>>> >>>  - code React tutorial & read about Flux
> > > >> >> >>>>> >>>  - take a look how we are using React
> > > >> >> >>>>> >>>  - create another menu item, called "Dashboard", try to
> > > answer
> > > >> >> the
> > > >> >> >>>>> >>> questions to route.js et al
> > > >> >> >>>>> >>>  - get familiar how we test our code
> > > >> >> >>>>> >>>  - write an hello world / hello from dulanga component
> > > that is
> > > >> >> >>>>> >>> rendered into a screen when opening
> > > >> http://localhost:8000/dash
> > > >> >> or
> > > >> >> >>>>> >>> by
> > > >> >> >>>>> >>> clicking on "dashboard" in the sidebar
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> That was a lot of content and please don't feel
> > > discouraged if
> > > >> >> you
> > > >> >> >>>>> >>> don't get that far until Wednesday. We will have to
> find
> > a
> > > >> speed
> > > >> >> >>>>> >>> which
> > > >> >> >>>>> >>> is perfect for you and this time I tried to give enough
> > > >> >> >>>>> >>> informations
> > > >> >> >>>>> >>> that you are not blocked until Wednesday by waiting for
> > > next
> > > >> >> steps.
> > > >> >> >>>>> >>> If
> > > >> >> >>>>> >>> you are at the last step before Wednesday, drop me a
> line
> > > and
> > > >> I
> > > >> >> >>>>> >>> will
> > > >> >> >>>>> >>> prepare the next steps :)
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> I know that you all have important exams, these are
> > > definitely
> > > >> >> more
> > > >> >> >>>>> >>> important! Don't feel pressured by the amount of work /
> > the
> > > >> >> amount
> > > >> >> >>>>> >>> of
> > > >> >> >>>>> >>> informations, getting good results in the exams should
> be
> > > your
> > > >> >> >>>>> >>> first
> > > >> >> >>>>> >>> priority.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> Best,
> > > >> >> >>>>> >>> Robert
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
> > > >> >> >>>>> >>> <wa...@gmail.com>
> > > >> >> >>>>> >>> wrote:
> > > >> >> >>>>> >>> > Hi Robert,
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> > I went through the guidelines you provided and
> > > successfully
> > > >> >> >>>>> >>> > installed and
> > > >> >> >>>>> >>> > configured as you said. Everything works find and I
> > > played
> > > >> >> around
> > > >> >> >>>>> >>> > it by
> > > >> >> >>>>> >>> > creating a database and documents. I think I am ready
> > for
> > > >> the
> > > >> >> >>>>> >>> > next step
> > > >> >> >>>>> >>> and
> > > >> >> >>>>> >>> > we can start it if you are ok :)
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> > Thank You
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
> > > >> >> >>>>> >>> > <ro...@kowalski.gd>
> > > >> >> >>>>> >>> wrote:
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> >> You're welcome.
> > > >> >> >>>>> >>> >>
> > > >> >> >>>>> >>> >> I also hang out in the couchdb-dev channel for
> around
> > > >> 1-3hrs
> > > >> >> if
> > > >> >> >>>>> >>> >> you get
> > > >> >> >>>>> >>> >> stuck!
> > > >> >> >>>>> >>> >>
> > > >> >> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
> > > >> >> >>>>> >>> >> <wa...@gmail.com>
> > > >> >> >>>>> >>> >> wrote:
> > > >> >> >>>>> >>> >> > Hi Robert,
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> > Thank you very much for the quick reply. I will go
> > > >> through
> > > >> >> the
> > > >> >> >>>>> >>> guidelines
> > > >> >> >>>>> >>> >> > and contact you if I have any issue with them.
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> > Thank you
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
> > > >> >> >>>>> >>> >> > <ro...@kowalski.gd>
> > > >> >> >>>>> >>> >> wrote:
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> >> Hi Dulanga,
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> glad you found your way to the CouchDB mailing
> > list.
> > > >> >> Welcome
> > > >> >> >>>>> >>> >> >> :)
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> CouchDB is a database written in Erlang with an
> > HTTP
> > > >> API -
> > > >> >> >>>>> >>> >> >> that makes
> > > >> >> >>>>> >>> >> >> it a great fit for web applications that don't
> > need a
> > > >> >> server
> > > >> >> >>>>> >>> >> >> side
> > > >> >> >>>>> >>> >> >> layer with a database driver in between. Our
> > Project
> > > >> >> Fauxton
> > > >> >> >>>>> >>> >> >> (like a
> > > >> >> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev
> > > >> including
> > > >> >> >>>>> >>> >> >> myself.
> > > >> >> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no
> > one
> > > is
> > > >> >> >>>>> >>> >> >> online (e.g.
> > > >> >> >>>>> >>> I
> > > >> >> >>>>> >>> >> >> was travelling this week) feel free to ask on the
> > dev
> > > >> ML.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> We are all happy to help each other in the
> project
> > :)
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> If you are using windows: I am not a Windows
> > expert -
> > > >> you
> > > >> >> >>>>> >>> >> >> will
> > > >> >> >>>>> >>> >> >> probably have to use a bash emulator like "git
> > bash"
> > > to
> > > >> >> boot
> > > >> >> >>>>> >>> >> >> the dev
> > > >> >> >>>>> >>> >> >> environment.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Getting started:
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> For this project you will need to install at
> least
> > > >> CouchDB
> > > >> >> >>>>> >>> >> >> 1.x, an
> > > >> >> >>>>> >>> >> >> Ubuntu package (with installation instructions)
> is
> > at
> > > >> >> >>>>> >>> >> >>
> > > https://launchpad.net/~couchdb/+archive/ubuntu/stable
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or
> > 0.12
> > > >> >> >>>>> >>> >> >> (install from
> > > >> >> >>>>> >>> >> >> https://nodejs.org)
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Booting Fauxton and first steps (type without the
> > $):
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> booting CouchDB:
> > > >> >> >>>>> >>> >> >> $ sudo couchdb
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> in another terminal, clone the admin interface:
> > > >> >> >>>>> >>> >> >> $ git clone
> > > https://github.com/apache/couchdb-fauxton
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> go to Fauxton:
> > > >> >> >>>>> >>> >> >> $ cd couchdb-fauxton
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> install dependencies:
> > > >> >> >>>>> >>> >> >> $ npm install
> > > >> >> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> boot the app:
> > > >> >> >>>>> >>> >> >> $ grunt dev
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Then open your browser and go to
> > > http://localhost:8000
> > > >> -
> > > >> >> you
> > > >> >> >>>>> >>> >> >> should
> > > >> >> >>>>> >>> >> >> see a red/gray/black interface
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> That was a lot of input and especially if you are
> > > using
> > > >> >> Linux
> > > >> >> >>>>> >>> >> >> the
> > > >> >> >>>>> >>> >> >> first time and followed the instructions you have
> > > >> archived
> > > >> >> a
> > > >> >> >>>>> >>> >> >> lot!
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> As first step, try to create a database and a
> > > document
> > > >> now
> > > >> >> >>>>> >>> >> >> using the
> > > >> >> >>>>> >>> >> >> web interface (PS we are happy about any
> usability
> > > >> >> feedback).
> > > >> >> >>>>> >>> >> >> :)
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> I think you have your dev environment for CouchDB
> > > ready
> > > >> >> now.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> What's next:
> > > >> >> >>>>> >>> >> >> If everything works we will take a look at
> Fauxtons
> > > code
> > > >> >> >>>>> >>> >> >> structure
> > > >> >> >>>>> >>> and
> > > >> >> >>>>> >>> >> >> how it works. We will also talk about the
> features
> > of
> > > >> the
> > > >> >> >>>>> >>> >> >> dashboard.
> > > >> >> >>>>> >>> >> >> Let's find a date for a chat after you took a
> first
> > > look
> > > >> >> how
> > > >> >> >>>>> >>> >> >> Fauxton
> > > >> >> >>>>> >>> >> >> looks like.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> We are having our weekly meeting this Wednesday,
> > > >> 20:00GMT
> > > >> >> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00
> )
> > in
> > > >> IRC
> > > >> >> on
> > > >> >> >>>>> >>> >> >> freenode
> > > >> >> >>>>> >>> >> >> (see
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >>
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>>
> > > >> >>
> > > >>
> > >
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > > >> >> >>>>> >>> >> >> )
> > > >> >> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr
> before
> > > if
> > > >> you
> > > >> >> >>>>> >>> >> >> want to
> > > >> >> >>>>> >>> >> >> chat with me before.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> Looking forward to work with you,
> > > >> >> >>>>> >>> >> >> Robert
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika
> <
> > > >> >> >>>>> >>> wadsashika@gmail.com>
> > > >> >> >>>>> >>> >> >> wrote:
> > > >> >> >>>>> >>> >> >> > Hi all,
> > > >> >> >>>>> >>> >> >> >
> > > >> >> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year
> > > >> undergraduate
> > > >> >> >>>>> >>> >> >> > student at
> > > >> >> >>>>> >>> >> >> > Computer Science and Engineering department at
> > > >> University
> > > >> >> >>>>> >>> >> >> > of
> > > >> >> >>>>> >>> Moratuwa,
> > > >> >> >>>>> >>> >> >> Sri
> > > >> >> >>>>> >>> >> >> > Lanka. I am really interested in java, java
> > script,
> > > >> web
> > > >> >> >>>>> >>> applications,
> > > >> >> >>>>> >>> >> >> > algorithms, data mining and machine learning. I
> > > have 6
> > > >> >> >>>>> >>> >> >> > months of
> > > >> >> >>>>> >>> >> training
> > > >> >> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I
> > > worked
> > > >> >> on a
> > > >> >> >>>>> >>> >> >> > web
> > > >> >> >>>>> >>> >> >> application
> > > >> >> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My
> > final
> > > >> year
> > > >> >> >>>>> >>> >> >> > project
> > > >> >> >>>>> >>> also a
> > > >> >> >>>>> >>> >> >> web
> > > >> >> >>>>> >>> >> >> > related application and I used same
> technologies
> > I
> > > >> >> >>>>> >>> >> >> > mentioned above
> > > >> >> >>>>> >>> for
> > > >> >> >>>>> >>> >> >> > that. I am really interested in this project
> > > because I
> > > >> >> have
> > > >> >> >>>>> >>> >> >> > a good
> > > >> >> >>>>> >>> >> >> > experience with web applications and I love
> work
> > > with
> > > >> >> >>>>> >>> >> >> > javascript.
> > > >> >> >>>>> >>> I am
> > > >> >> >>>>> >>> >> >> > looking forward to contribute to this project
> in
> > > this
> > > >> >> >>>>> >>> >> >> > summer. I
> > > >> >> >>>>> >>> like
> > > >> >> >>>>> >>> >> to
> > > >> >> >>>>> >>> >> >> > know more detail about this project and if you
> > can,
> > > >> >> please
> > > >> >> >>>>> >>> >> >> > guide
> > > >> >> >>>>> >>> me to
> > > >> >> >>>>> >>> >> >> > start working on this project.
> > > >> >> >>>>> >>> >> >> >
> > > >> >> >>>>> >>> >> >> > Thank you.
> > > >> >> >>>>> >>> >> >> >
> > > >> >> >>>>> >>> >> >> > W. A. Dulanga Sashika,
> > > >> >> >>>>> >>> >> >> > Undergraduate Student,
> > > >> >> >>>>> >>> >> >> > Department of Computer Science and Engineering,
> > > >> >> >>>>> >>> >> >> > University of Moratuwa.
> > > >> >> >>>>> >>> >> >>
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> >
> > > >> >> >>>>> >>> >> > --
> > > >> >> >>>>> >>> >> > W. A. Dulanga Sashika,
> > > >> >> >>>>> >>> >> > Undergraduate Student,
> > > >> >> >>>>> >>> >> > Department of Computer Science and Engineering,
> > > >> >> >>>>> >>> >> > University of Moratuwa.
> > > >> >> >>>>> >>> >>
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> >
> > > >> >> >>>>> >>> > --
> > > >> >> >>>>> >>> > W. A. Dulanga Sashika,
> > > >> >> >>>>> >>> > Undergraduate Student,
> > > >> >> >>>>> >>> > Department of Computer Science and Engineering,
> > > >> >> >>>>> >>> > University of Moratuwa.
> > > >> >> >>>>> >>>
> > > >> >> >>>>> >>
> > > >> >> >>>>> >>
> > > >> >> >>>>> >>
> > > >> >> >>>>> >> --
> > > >> >> >>>>> >> W. A. Dulanga Sashika,
> > > >> >> >>>>> >> Undergraduate Student,
> > > >> >> >>>>> >> Department of Computer Science and Engineering,
> > > >> >> >>>>> >> University of Moratuwa.
> > > >> >> >>>>
> > > >> >> >>>>
> > > >> >> >>>>
> > > >> >> >>>>
> > > >> >> >>>> --
> > > >> >> >>>> W. A. Dulanga Sashika,
> > > >> >> >>>> Undergraduate Student,
> > > >> >> >>>> Department of Computer Science and Engineering,
> > > >> >> >>>> University of Moratuwa.
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>>
> > > >> >> >>> --
> > > >> >> >>> W. A. Dulanga Sashika,
> > > >> >> >>> Undergraduate Student,
> > > >> >> >>> Department of Computer Science and Engineering,
> > > >> >> >>> University of Moratuwa.
> > > >> >> >>
> > > >> >> >>
> > > >> >> >>
> > > >> >> >>
> > > >> >> >> --
> > > >> >> >> W. A. Dulanga Sashika,
> > > >> >> >> Undergraduate Student,
> > > >> >> >> Department of Computer Science and Engineering,
> > > >> >> >> University of Moratuwa.
> > > >> >> >
> > > >> >> >
> > > >> >> >
> > > >> >> >
> > > >> >> > --
> > > >> >> > W. A. Dulanga Sashika,
> > > >> >> > Undergraduate Student,
> > > >> >> > Department of Computer Science and Engineering,
> > > >> >> > University of Moratuwa.
> > > >> >>
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > W. A. Dulanga Sashika,
> > > >> > Undergraduate Student,
> > > >> > Department of Computer Science and Engineering,
> > > >> > University of Moratuwa.
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > W. A. Dulanga Sashika,
> > > > Undergraduate Student,
> > > > Department of Computer Science and Engineering,
> > > > University of Moratuwa.
> > >
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
> >
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga,

exactly my opinion! I agree! Sorry if I my response sounded discouraging,
but I think we share the exactly same opinion!

Just for clarification - I hope my mail was not received in another way:

Regarding the font: I just wanted to share the knowledge for the future
(implementation step) that we have an own icon font . I already figured
that you probably did not know about it and wanted to share the knowledge
as it will your life a lot easier during the implementation. Maybe we can
also add some of your icons to it if they fit better to the use case :)

Custom widgets: I asked the question as I am are not sure on my own what
could happen or how this could integrate into Fauxton at all :) We could
probably use the addon-architecture or requireExtensions which makes
Fauxton extensible at build time, but probably it is technically not
possible to add them at runtime. This was not obvious to me until I saw the
mock up, thanks again for creating it.  :)


For the recently visited databases: I would be interested in "# of docs and
name of the database, with a link to the database", like in your proposal
For the Active tasks: just a short overview what is currently running, I
also really like your proposal

Maybe Alex can chime in and give some suggestion regarding the content for
active tasks and recently visited databases, as he is a real power user :)

On Sun, Mar 22, 2015 at 5:23 AM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Hi Robert,
>
> I made this design using Photoshop. Therefore, I used these icons and fonts
> just to show how it looks like. Since this is the first design, I thought
> it will not be a big issue. We can change them at any time.
> Previously we talked about "Custom Widgets". As I understand it, there will
> be a option as "custom widgets" in the dashboard and if we click on that,
> it will go to a page where we can select/remove widgets from the dashboard.
> If yours and Alex's intention about "Custom Widgets" are different from
> this, please correct me :) I might be wrong about that.
> Another thing is that, I do not know exactly what are the important items
> to include into "Active Tasks" and "Recently Visited Databases" tables. I
> put items that came into my mind as important. We can change them also.
> Actually this one is for just to get an idea about the dashboard. As you
> said, this will help to think about problems that might occur. All we need
> is the ideas from the community :) then we can come up with a better design
> than this.
>
> Regards
>
> On Sun, Mar 22, 2015 at 5:28 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
> > Cool! Thank you!
> >
> > Creating a mock-up is a good way to get some initial feedback and
> > helps to think about problems that might occur. Probably Sean or
> > another designer will take a final look at the final work you create
> > in terms of design.
> >
> > One question that came to my mind while looking at the dashboard was:
> > "what happens if we click on custom widgets?"
> >
> > Btw have you seen our icon fonts?
> >
> > We have an own at
> >
> >
> https://github.com/apache/couchdb-fauxton/blob/master/assets/fonts/styleguide/fauxtonicon-preview.html
> > and additionally support the glyphicons from bootstrap 2.3:
> > http://getbootstrap.com/2.3.2/base-css.html#icons
> >
> >
> > Best,
> > Robert
> >
> > On Sat, Mar 21, 2015 at 9:00 PM, Dulanga Sashika <wa...@gmail.com>
> > wrote:
> > > Hi Robert,
> > >
> > > Here is the mock up I designed for the dashboard.
> > > https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> > >
> > > Please give some comments and we can change this later by discussing
> the
> > > important facts that we should show in the dashboard. For now I
> designed
> > a
> > > mock up only for dashboard and I can make designs for each widgets
> later.
> > >
> > > Thank You
> > >
> > >
> > > On Fri, Mar 20, 2015 at 8:12 PM, Robert Kowalski <ro...@kowalski.gd>
> > wrote:
> > >
> > >> Cool thank you!
> > >>
> > >> Yes I also did not know until someone told me 2 months ago :)
> > >>
> > >> On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <
> wadsashika@gmail.com>
> > >> wrote:
> > >> > Hi Robert,
> > >> >
> > >> > Thank you very much for the help. I can carry on from there now.
> > >> Actually I
> > >> > didn't know that this mailing list does not supported for
> attachments.
> > >> Here
> > >> > is the screenshots I uploaded.
> > >> >
> > >> > img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
> > >> > img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
> > >> > img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
> > >> > img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
> > >> > img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
> > >> > img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
> > >> >
> > >> > And I will share the proposal ASAP with you.
> > >> >
> > >> > Thank you
> > >> >
> > >> > On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd>
> > >> wrote:
> > >> >
> > >> >> Hi Dulanga,
> > >> >>
> > >> >> glad you figured it out while I was on a train! :)
> > >> >>
> > >> >> Can you upload the pictures to something like box.com / dropbox or
> > an
> > >> >> image hoster as the list does not support attachments?
> > >> >>
> > >> >> We are storing our react components in files like
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
> > >> >>
> > >> >> To render them we still have to wrap them in Backbone Views - as
> our
> > >> >> framework is built for Backbone views. The backbone view files are
> > >> >> usually called `views.js`. This will go away soon but currently it
> is
> > >> >> the way to go:
> > >> >>
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> > >> >>
> > >> >> which calls this at the bottom of
> > >> `app/addons/cors/components.react.jsx`:
> > >> >>
> > >> >>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
> > >> >>
> > >> >>
> > >> >> In
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> > >> >> `this.el` references the DOM-Node of the Backbone view in which
> then
> > >> >> the React Component is rendered into.
> > >> >>
> > >> >>
> > >> >> Regarding the proposal:
> > >> >>
> > >> >> I am happy to help you with your proposal it would be nice to have
> an
> > >> >> option that makes it easy to leave comments (e.g google docs)
> > >> >>
> > >> >> Best,
> > >> >> Robert
> > >> >>
> > >> >> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <
> > wadsashika@gmail.com>
> > >> >> wrote:
> > >> >> > Hi,
> > >> >> > Here I attached the screen shots of Dashboard menu item. Now its
> > >> working.
> > >> >> > Now I want to know that, if I need to implement react component,
> > where
> > >> >> > should I put it? And how can I access that to render the view?
> just
> > >> give
> > >> >> me
> > >> >> > some hints and I can carry on from there.
> > >> >> >
> > >> >> > Regards
> > >> >> >
> > >> >> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <
> > >> wadsashika@gmail.com>
> > >> >> > wrote:
> > >> >> >>
> > >> >> >> Hey Robert, problem solved.. :)
> > >> >> >>
> > >> >> >>
> > >> >> >> Regards.
> > >> >> >>
> > >> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <
> > >> wadsashika@gmail.com>
> > >> >> >> wrote:
> > >> >> >>>
> > >> >> >>> Hi Robert,
> > >> >> >>>
> > >> >> >>> Now I am trying to create a new menu item for dashboard and
> > >> implement a
> > >> >> >>> react component as you said. But now I am stuck in some place
> and
> > >> >> couldn't
> > >> >> >>> figure out the problem yet. Here is the problem I had in
> > process. I
> > >> >> added
> > >> >> >>> dashboard menu item and added route and view for that. And i
> > change
> > >> >> the code
> > >> >> >>> to render dashboard when we enter http://localhost:8000 . As
> in
> > >> img1
> > >> >> and
> > >> >> >>> img2, it doesn't show the view I created. But when I click on
> > >> another
> > >> >> menu
> > >> >> >>> item and come back to the dashboard, it shows the breadcrumb of
> > >> >> previous
> > >> >> >>> pages as img 3 and 4. As in
> > >> >> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> > >> >> >>> , I called the new Dashboard.view() which is a component in my
> > >> >> view.js. But
> > >> >> >>> in the console, it shows Uncaught Type error. Did I miss any
> > >> >> configuration
> > >> >> >>> thing or did I do it wrong?
> > >> >> >>>
> > >> >> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
> > >> >> wadsashika@gmail.com>
> > >> >> >>> wrote:
> > >> >> >>>>
> > >> >> >>>> Hi Robert,
> > >> >> >>>>
> > >> >> >>>> Thank you very much for the reference. I started to write the
> > >> proposal
> > >> >> >>>> today. I hope you will help to write this proposal by
> reviewing
> > >> it.
> > >> >> I will
> > >> >> >>>> share it with you after complete the draft of the proposal.
> > >> >> >>>>
> > >> >> >>>> Thank you
> > >> >> >>>>
> > >> >> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <
> > rok@kowalski.gd>
> > >> >> >>>> wrote:
> > >> >> >>>>>
> > >> >> >>>>> Some of you asked for a template for their proposals, here is
> > what
> > >> >> I've
> > >> >> >>>>> found:
> > >> >> >>>>>
> > >> >> >>>>>
> http://community.staging.apache.org/gsoc#application-template
> > >> >> >>>>>
> > >> >> >>>>> Best,
> > >> >> >>>>> Robert
> > >> >> >>>>>
> > >> >> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <
> > >> rok@kowalski.gd>
> > >> >> >>>>> wrote:
> > >> >> >>>>> > Wow you are making very good progress!
> > >> >> >>>>> >
> > >> >> >>>>> > We have our weekly status meetup tomorrow (see [1] for the
> > time
> > >> in
> > >> >> >>>>> > your timezone), feel free to join, meet other project
> members
> > >> and
> > >> >> >>>>> > learn what the project is currently doing next to the
> Summer
> > of
> > >> >> Code.
> > >> >> >>>>> >
> > >> >> >>>>> > I will also be around 1hr earlier to answer all your
> > questions
> > >> and
> > >> >> >>>>> > discuss our next steps.
> > >> >> >>>>> >
> > >> >> >>>>> >
> > >> >> >>>>> > [1]
> > >> >> >>>>> >
> > >> >>
> > >>
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > >> >> >>>>> >
> > >> >> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
> > >> >> >>>>> > <wa...@gmail.com> wrote:
> > >> >> >>>>> >> Hi Robert,
> > >> >> >>>>> >>
> > >> >> >>>>> >> Here is the current status of the checklist :)
> > >> >> >>>>> >>
> > >> >> >>>>> >>  - check out the active tasks api (linked on top of this
> > mail)
> > >> -
> > >> >> >>>>> >> (finished)
> > >> >> >>>>> >>  - a mockup showing some widgets and how they could look
> > like -
> > >> >> >>>>> >> (started
> > >> >> >>>>> >> but not finished yet)
> > >> >> >>>>> >>  - code React tutorial & read about Flux - (finished)
> > >> >> >>>>> >>  - take a look how we are using React - (finished)
> > >> >> >>>>> >>  - create another menu item, called "Dashboard", try to
> > answer
> > >> the
> > >> >> >>>>> >> questions to route.js et al - (started but not finished
> yet)
> > >> >> >>>>> >>  - get familiar how we test our code - (finished)
> > >> >> >>>>> >>  - write an hello world / hello from dulanga component
> that
> > is
> > >> >> >>>>> >> rendered into a screen when opening
> > http://localhost:8000/dash
> > >> >> or by
> > >> >> >>>>> >> clicking on "dashboard" in the sidebar - (started but not
> > >> finished
> > >> >> >>>>> >> yet)
> > >> >> >>>>> >>
> > >> >> >>>>> >> I will do my best to complete all these by tomorrow. If I
> > have
> > >> any
> > >> >> >>>>> >> problem,
> > >> >> >>>>> >> I will trouble you as you wished yesterday :)
> > >> >> >>>>> >>
> > >> >> >>>>> >> Thank You
> > >> >> >>>>> >>
> > >> >> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <
> > >> rok@kowalski.gd
> > >> >> >
> > >> >> >>>>> >> wrote:
> > >> >> >>>>> >>
> > >> >> >>>>> >>> Hi Dulanga,
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> we already talked on irc and you already talked to Alex
> > >> regarding
> > >> >> >>>>> >>> features for our dashboard. That's great!
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Some topics will repeat in this mail, but I also would
> like
> > >> the
> > >> >> ML
> > >> >> >>>>> >>> to
> > >> >> >>>>> >>> follow our project and additionally add some more
> in-depth
> > >> >> >>>>> >>> informations.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Recap & additons
> > >> >> >>>>> >>> =====
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> As discussed we will work in an iterative approach and
> add
> > >> widget
> > >> >> >>>>> >>> after widget so if we run out of time, we will have
> > something
> > >> to
> > >> >> >>>>> >>> deliver and don't have to throw everything away.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Have you seen the "database" tab or the "config" tab in
> the
> > >> >> sidebar
> > >> >> >>>>> >>> on the
> > >> >> >>>>> >>> left?
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Those are modules that we can hook into the Fauxton
> build,
> > by
> > >> >> >>>>> >>> configuration. I think the idea is to create a tab
> > "dashboard"
> > >> >> >>>>> >>> which
> > >> >> >>>>> >>> is the default one after opening Fauxton in the browser.
> So
> > >> you
> > >> >> >>>>> >>> would
> > >> >> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Alex ideas so far:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue
> > there
> > >> are
> > >> >> >>>>> >>> some
> > >> >> >>>>> >>> points about showing stats and log - forget these (:
> _stats
> > >> isn't
> > >> >> >>>>> >>> available for
> > >> >> >>>>> >>>                    cluster iface and _log is removed. but
> > >> >> recently
> > >> >> >>>>> >>> visited databases, active tasks and _users/_replicator
> > quick
> > >> >> >>>>> >>> management is what could
> > >> >> >>>>> >>>                    be really handy.
> > >> >> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not
> > >> relevant
> > >> >> >>>>> >>> anymore after backporting some cloudant features
> > >> >> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a
> way
> > >> how
> > >> >> (:
> > >> >> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of
> > widgets,
> > >> I
> > >> >> >>>>> >>> believe you could make some builtin and leave a template
> > one
> > >> to
> > >> >> let
> > >> >> >>>>> >>> the end users create
> > >> >> >>>>> >>>                    their own if they're able/would like
> > to. in
> > >> >> >>>>> >>> future
> > >> >> >>>>> >>> these are could be fauxton plugins or something.
> > >> >> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice
> > idea
> > >> >> for a
> > >> >> >>>>> >>> hot
> > >> >> >>>>> >>> widget.
> > >> >> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely
> > help
> > >> with
> > >> >> >>>>> >>> that
> > >> >> >>>>> >>> (add custom widgets on build time) - the build is
> > complicated,
> > >> >> but
> > >> >> >>>>> >>> once explained
> > >> >> >>>>> >>>                            it should be easy
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> So we have "custom widgets", "cluster quick-management",
> "
> > >> >> recently
> > >> >> >>>>> >>> visited databases",  "active tasks" and
> "_users/_replicator
> > >> quick
> > >> >> >>>>> >>> management"
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> I think two good widgets for starting are active tasks
> and
> > >> >> recently
> > >> >> >>>>> >>> visited databases.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> For active tasks we have some nice docs:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> They have an own dedicated page in Fauxton (see
> > >> >> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick
> > >> condensed
> > >> >> >>>>> >>> list
> > >> >> >>>>> >>> is probably very interesting to users.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> For the recently visited databases we would have to store
> > that
> > >> >> >>>>> >>> somewhere.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> If you want, you can take an existing page in Fauxton and
> > just
> > >> >> >>>>> >>> modify
> > >> >> >>>>> >>> the markup for a design mockup how the widget view may
> look
> > >> like.
> > >> >> >>>>> >>> But
> > >> >> >>>>> >>> feel also free to use pen/paper or other tools if you
> like
> > >> that
> > >> >> the
> > >> >> >>>>> >>> most.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> For the mango feature I am currently working on, I took
> the
> > >> "edit
> > >> >> >>>>> >>> view" template on modified the markup using the Chrome
> > >> inspector
> > >> >> of
> > >> >> >>>>> >>> my
> > >> >> >>>>> >>> browser to collect some first feedback from the project
> > >> members
> > >> >> and
> > >> >> >>>>> >>> my
> > >> >> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have
> > any
> > >> >> >>>>> >>> functionality, but gives other folks a rough idea what my
> > idea
> > >> >> for
> > >> >> >>>>> >>> the
> > >> >> >>>>> >>> feature is.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> the framework and react
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> As I already mentioned we are using React.js.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> It would be nice if you can finish the tutorial at
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> > >> >> >>>>> >>> until next friday by following the steps and writing that
> > >> code.
> > >> >> >>>>> >>> After
> > >> >> >>>>> >>> that, read
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> > >> >> >>>>> >>> to get a first impression how the Flux pattern works that
> > we
> > >> are
> > >> >> >>>>> >>> using.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> After that (if you still have time left) take a look on a
> > >> >> component
> > >> >> >>>>> >>> that Garren, my coworker refactored from Backbone.js to
> > React:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Please take a look how the data flows from the
> Components,
> > >> using
> > >> >> >>>>> >>> the
> > >> >> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to
> > litter
> > >> >> >>>>> >>> everything in the code with console.log to see how state
> > >> changes
> > >> >> >>>>> >>> and
> > >> >> >>>>> >>> how the data flows.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Hint: it is that element:
> https://cldup.com/4eCHVt9HHt.png
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> If you still have time, just try to create another menu
> > item,
> > >> >> >>>>> >>> called
> > >> >> >>>>> >>> "Dashboard". Take a look at:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> to get a first idea how to do that. Some background
> > >> information:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> base.js - the starting point of our module. basic
> > >> configuration
> > >> >> is
> > >> >> >>>>> >>> done
> > >> >> >>>>> >>> here
> > >> >> >>>>> >>> Question: what is `base.js` used for in the case of the
> > config
> > >> >> >>>>> >>> module?
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> routes.js - takes care that functions injecting the view
> > into
> > >> the
> > >> >> >>>>> >>> layout are called depending on the url given
> > >> >> >>>>> >>> Question: What happens if I call
> > `http:localhost:8000/_config`
> > >> >> and
> > >> >> >>>>> >>> what happens if you remove the function `apiUrl`?
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> views.js - contains our views - this file contains still
> a
> > lot
> > >> >> >>>>> >>> backbone views, which we are currently migrating to
> react.
> > >> maybe
> > >> >> it
> > >> >> >>>>> >>> makes more sense to take a look at one of our react
> > >> components:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> and how they are used currently (as we are migrating to
> > react
> > >> >> >>>>> >>> currently):
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> The Objects are injected into the closures using AMD:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> assets folder:
> > >> >> >>>>> >>> contains our less which is compiled to css
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> templates folder:
> > >> >> >>>>> >>> contains old backbone.js templates, you will not need
> them
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> tests folder:
> > >> >> >>>>> >>> contains unit and integration tests, every PR must have
> > unit
> > >> >> tests
> > >> >> >>>>> >>> and
> > >> >> >>>>> >>> integration tests. If you never wrote tests, we will
> > explain
> > >> it
> > >> >> to
> > >> >> >>>>> >>> you
> > >> >> >>>>> >>> - it is easy once you wrote your first few ones.
> Basically
> > you
> > >> >> are
> > >> >> >>>>> >>> testing each time that if you put something into a
> > function,
> > >> the
> > >> >> >>>>> >>> expected result happens. Or that if you take an action, a
> > >> state
> > >> >> has
> > >> >> >>>>> >>> changed.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> You can run the unit tests using `grunt test`
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Single tests are run by:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>> grunt test
> > >> >> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> or in the browser by test group:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> > >> >> >>>>> >>> ```
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> (change path to your fauxton directory)
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> The corresponding code is:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> and these tests are a good example how to write a simple
> > test
> > >> for
> > >> >> >>>>> >>> the
> > >> >> >>>>> >>> hello world/hello from dulanga-component:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> First steps:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Create a module `dashboard` that gets displayed in the
> > >> sidebar.
> > >> >> The
> > >> >> >>>>> >>> route http://localhost:8000/dash will render a small
> React
> > >> >> >>>>> >>> component
> > >> >> >>>>> >>> that display "Hello World".
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> If you click on the "Hello World" it ill change the
> content
> > >> to:
> > >> >> >>>>> >>> "Hello
> > >> >> >>>>> >>> from Dulanga"
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> While we will throw the small component away afterwards
> we
> > >> will
> > >> >> >>>>> >>> build
> > >> >> >>>>> >>> upon the other code you created. If you have time left,
> > add a
> > >> >> test
> > >> >> >>>>> >>> that the component changes the content.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Meeting Wednesday:
> > >> >> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> I will be around at least one hour before so we can chat.
> > >> Contact
> > >> >> >>>>> >>> me
> > >> >> >>>>> >>> if you would like to chat earlier/later. I am also around
> > the
> > >> >> other
> > >> >> >>>>> >>> days on IRC / the mailinglist and feel free to contact me
> > in
> > >> >> >>>>> >>> #couchdb-dev at any time. If I am not around I will
> answer
> > you
> > >> >> once
> > >> >> >>>>> >>> I
> > >> >> >>>>> >>> got online again, as I read the backlog.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>  - check out the active tasks api (linked on top of this
> > mail)
> > >> >> >>>>> >>>  - a mockup showing some widgets and how they could look
> > like
> > >> >> >>>>> >>>  - code React tutorial & read about Flux
> > >> >> >>>>> >>>  - take a look how we are using React
> > >> >> >>>>> >>>  - create another menu item, called "Dashboard", try to
> > answer
> > >> >> the
> > >> >> >>>>> >>> questions to route.js et al
> > >> >> >>>>> >>>  - get familiar how we test our code
> > >> >> >>>>> >>>  - write an hello world / hello from dulanga component
> > that is
> > >> >> >>>>> >>> rendered into a screen when opening
> > >> http://localhost:8000/dash
> > >> >> or
> > >> >> >>>>> >>> by
> > >> >> >>>>> >>> clicking on "dashboard" in the sidebar
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> That was a lot of content and please don't feel
> > discouraged if
> > >> >> you
> > >> >> >>>>> >>> don't get that far until Wednesday. We will have to find
> a
> > >> speed
> > >> >> >>>>> >>> which
> > >> >> >>>>> >>> is perfect for you and this time I tried to give enough
> > >> >> >>>>> >>> informations
> > >> >> >>>>> >>> that you are not blocked until Wednesday by waiting for
> > next
> > >> >> steps.
> > >> >> >>>>> >>> If
> > >> >> >>>>> >>> you are at the last step before Wednesday, drop me a line
> > and
> > >> I
> > >> >> >>>>> >>> will
> > >> >> >>>>> >>> prepare the next steps :)
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> I know that you all have important exams, these are
> > definitely
> > >> >> more
> > >> >> >>>>> >>> important! Don't feel pressured by the amount of work /
> the
> > >> >> amount
> > >> >> >>>>> >>> of
> > >> >> >>>>> >>> informations, getting good results in the exams should be
> > your
> > >> >> >>>>> >>> first
> > >> >> >>>>> >>> priority.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> Best,
> > >> >> >>>>> >>> Robert
> > >> >> >>>>> >>>
> > >> >> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
> > >> >> >>>>> >>> <wa...@gmail.com>
> > >> >> >>>>> >>> wrote:
> > >> >> >>>>> >>> > Hi Robert,
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> > I went through the guidelines you provided and
> > successfully
> > >> >> >>>>> >>> > installed and
> > >> >> >>>>> >>> > configured as you said. Everything works find and I
> > played
> > >> >> around
> > >> >> >>>>> >>> > it by
> > >> >> >>>>> >>> > creating a database and documents. I think I am ready
> for
> > >> the
> > >> >> >>>>> >>> > next step
> > >> >> >>>>> >>> and
> > >> >> >>>>> >>> > we can start it if you are ok :)
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> > Thank You
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
> > >> >> >>>>> >>> > <ro...@kowalski.gd>
> > >> >> >>>>> >>> wrote:
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> >> You're welcome.
> > >> >> >>>>> >>> >>
> > >> >> >>>>> >>> >> I also hang out in the couchdb-dev channel for around
> > >> 1-3hrs
> > >> >> if
> > >> >> >>>>> >>> >> you get
> > >> >> >>>>> >>> >> stuck!
> > >> >> >>>>> >>> >>
> > >> >> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
> > >> >> >>>>> >>> >> <wa...@gmail.com>
> > >> >> >>>>> >>> >> wrote:
> > >> >> >>>>> >>> >> > Hi Robert,
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> > Thank you very much for the quick reply. I will go
> > >> through
> > >> >> the
> > >> >> >>>>> >>> guidelines
> > >> >> >>>>> >>> >> > and contact you if I have any issue with them.
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> > Thank you
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
> > >> >> >>>>> >>> >> > <ro...@kowalski.gd>
> > >> >> >>>>> >>> >> wrote:
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> >> Hi Dulanga,
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> glad you found your way to the CouchDB mailing
> list.
> > >> >> Welcome
> > >> >> >>>>> >>> >> >> :)
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> CouchDB is a database written in Erlang with an
> HTTP
> > >> API -
> > >> >> >>>>> >>> >> >> that makes
> > >> >> >>>>> >>> >> >> it a great fit for web applications that don't
> need a
> > >> >> server
> > >> >> >>>>> >>> >> >> side
> > >> >> >>>>> >>> >> >> layer with a database driver in between. Our
> Project
> > >> >> Fauxton
> > >> >> >>>>> >>> >> >> (like a
> > >> >> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev
> > >> including
> > >> >> >>>>> >>> >> >> myself.
> > >> >> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no
> one
> > is
> > >> >> >>>>> >>> >> >> online (e.g.
> > >> >> >>>>> >>> I
> > >> >> >>>>> >>> >> >> was travelling this week) feel free to ask on the
> dev
> > >> ML.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> We are all happy to help each other in the project
> :)
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> If you are using windows: I am not a Windows
> expert -
> > >> you
> > >> >> >>>>> >>> >> >> will
> > >> >> >>>>> >>> >> >> probably have to use a bash emulator like "git
> bash"
> > to
> > >> >> boot
> > >> >> >>>>> >>> >> >> the dev
> > >> >> >>>>> >>> >> >> environment.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Getting started:
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> For this project you will need to install at least
> > >> CouchDB
> > >> >> >>>>> >>> >> >> 1.x, an
> > >> >> >>>>> >>> >> >> Ubuntu package (with installation instructions) is
> at
> > >> >> >>>>> >>> >> >>
> > https://launchpad.net/~couchdb/+archive/ubuntu/stable
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or
> 0.12
> > >> >> >>>>> >>> >> >> (install from
> > >> >> >>>>> >>> >> >> https://nodejs.org)
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Booting Fauxton and first steps (type without the
> $):
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> booting CouchDB:
> > >> >> >>>>> >>> >> >> $ sudo couchdb
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> in another terminal, clone the admin interface:
> > >> >> >>>>> >>> >> >> $ git clone
> > https://github.com/apache/couchdb-fauxton
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> go to Fauxton:
> > >> >> >>>>> >>> >> >> $ cd couchdb-fauxton
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> install dependencies:
> > >> >> >>>>> >>> >> >> $ npm install
> > >> >> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> boot the app:
> > >> >> >>>>> >>> >> >> $ grunt dev
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Then open your browser and go to
> > http://localhost:8000
> > >> -
> > >> >> you
> > >> >> >>>>> >>> >> >> should
> > >> >> >>>>> >>> >> >> see a red/gray/black interface
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> That was a lot of input and especially if you are
> > using
> > >> >> Linux
> > >> >> >>>>> >>> >> >> the
> > >> >> >>>>> >>> >> >> first time and followed the instructions you have
> > >> archived
> > >> >> a
> > >> >> >>>>> >>> >> >> lot!
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> As first step, try to create a database and a
> > document
> > >> now
> > >> >> >>>>> >>> >> >> using the
> > >> >> >>>>> >>> >> >> web interface (PS we are happy about any usability
> > >> >> feedback).
> > >> >> >>>>> >>> >> >> :)
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> I think you have your dev environment for CouchDB
> > ready
> > >> >> now.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> What's next:
> > >> >> >>>>> >>> >> >> If everything works we will take a look at Fauxtons
> > code
> > >> >> >>>>> >>> >> >> structure
> > >> >> >>>>> >>> and
> > >> >> >>>>> >>> >> >> how it works. We will also talk about the features
> of
> > >> the
> > >> >> >>>>> >>> >> >> dashboard.
> > >> >> >>>>> >>> >> >> Let's find a date for a chat after you took a first
> > look
> > >> >> how
> > >> >> >>>>> >>> >> >> Fauxton
> > >> >> >>>>> >>> >> >> looks like.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> We are having our weekly meeting this Wednesday,
> > >> 20:00GMT
> > >> >> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00)
> in
> > >> IRC
> > >> >> on
> > >> >> >>>>> >>> >> >> freenode
> > >> >> >>>>> >>> >> >> (see
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >>
> > >> >> >>>>> >>>
> > >> >> >>>>> >>>
> > >> >>
> > >>
> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> > >> >> >>>>> >>> >> >> )
> > >> >> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before
> > if
> > >> you
> > >> >> >>>>> >>> >> >> want to
> > >> >> >>>>> >>> >> >> chat with me before.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> Looking forward to work with you,
> > >> >> >>>>> >>> >> >> Robert
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> > >> >> >>>>> >>> wadsashika@gmail.com>
> > >> >> >>>>> >>> >> >> wrote:
> > >> >> >>>>> >>> >> >> > Hi all,
> > >> >> >>>>> >>> >> >> >
> > >> >> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year
> > >> undergraduate
> > >> >> >>>>> >>> >> >> > student at
> > >> >> >>>>> >>> >> >> > Computer Science and Engineering department at
> > >> University
> > >> >> >>>>> >>> >> >> > of
> > >> >> >>>>> >>> Moratuwa,
> > >> >> >>>>> >>> >> >> Sri
> > >> >> >>>>> >>> >> >> > Lanka. I am really interested in java, java
> script,
> > >> web
> > >> >> >>>>> >>> applications,
> > >> >> >>>>> >>> >> >> > algorithms, data mining and machine learning. I
> > have 6
> > >> >> >>>>> >>> >> >> > months of
> > >> >> >>>>> >>> >> training
> > >> >> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I
> > worked
> > >> >> on a
> > >> >> >>>>> >>> >> >> > web
> > >> >> >>>>> >>> >> >> application
> > >> >> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My
> final
> > >> year
> > >> >> >>>>> >>> >> >> > project
> > >> >> >>>>> >>> also a
> > >> >> >>>>> >>> >> >> web
> > >> >> >>>>> >>> >> >> > related application and I used same technologies
> I
> > >> >> >>>>> >>> >> >> > mentioned above
> > >> >> >>>>> >>> for
> > >> >> >>>>> >>> >> >> > that. I am really interested in this project
> > because I
> > >> >> have
> > >> >> >>>>> >>> >> >> > a good
> > >> >> >>>>> >>> >> >> > experience with web applications and I love work
> > with
> > >> >> >>>>> >>> >> >> > javascript.
> > >> >> >>>>> >>> I am
> > >> >> >>>>> >>> >> >> > looking forward to contribute to this project in
> > this
> > >> >> >>>>> >>> >> >> > summer. I
> > >> >> >>>>> >>> like
> > >> >> >>>>> >>> >> to
> > >> >> >>>>> >>> >> >> > know more detail about this project and if you
> can,
> > >> >> please
> > >> >> >>>>> >>> >> >> > guide
> > >> >> >>>>> >>> me to
> > >> >> >>>>> >>> >> >> > start working on this project.
> > >> >> >>>>> >>> >> >> >
> > >> >> >>>>> >>> >> >> > Thank you.
> > >> >> >>>>> >>> >> >> >
> > >> >> >>>>> >>> >> >> > W. A. Dulanga Sashika,
> > >> >> >>>>> >>> >> >> > Undergraduate Student,
> > >> >> >>>>> >>> >> >> > Department of Computer Science and Engineering,
> > >> >> >>>>> >>> >> >> > University of Moratuwa.
> > >> >> >>>>> >>> >> >>
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> >
> > >> >> >>>>> >>> >> > --
> > >> >> >>>>> >>> >> > W. A. Dulanga Sashika,
> > >> >> >>>>> >>> >> > Undergraduate Student,
> > >> >> >>>>> >>> >> > Department of Computer Science and Engineering,
> > >> >> >>>>> >>> >> > University of Moratuwa.
> > >> >> >>>>> >>> >>
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> >
> > >> >> >>>>> >>> > --
> > >> >> >>>>> >>> > W. A. Dulanga Sashika,
> > >> >> >>>>> >>> > Undergraduate Student,
> > >> >> >>>>> >>> > Department of Computer Science and Engineering,
> > >> >> >>>>> >>> > University of Moratuwa.
> > >> >> >>>>> >>>
> > >> >> >>>>> >>
> > >> >> >>>>> >>
> > >> >> >>>>> >>
> > >> >> >>>>> >> --
> > >> >> >>>>> >> W. A. Dulanga Sashika,
> > >> >> >>>>> >> Undergraduate Student,
> > >> >> >>>>> >> Department of Computer Science and Engineering,
> > >> >> >>>>> >> University of Moratuwa.
> > >> >> >>>>
> > >> >> >>>>
> > >> >> >>>>
> > >> >> >>>>
> > >> >> >>>> --
> > >> >> >>>> W. A. Dulanga Sashika,
> > >> >> >>>> Undergraduate Student,
> > >> >> >>>> Department of Computer Science and Engineering,
> > >> >> >>>> University of Moratuwa.
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> --
> > >> >> >>> W. A. Dulanga Sashika,
> > >> >> >>> Undergraduate Student,
> > >> >> >>> Department of Computer Science and Engineering,
> > >> >> >>> University of Moratuwa.
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >> W. A. Dulanga Sashika,
> > >> >> >> Undergraduate Student,
> > >> >> >> Department of Computer Science and Engineering,
> > >> >> >> University of Moratuwa.
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > W. A. Dulanga Sashika,
> > >> >> > Undergraduate Student,
> > >> >> > Department of Computer Science and Engineering,
> > >> >> > University of Moratuwa.
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > W. A. Dulanga Sashika,
> > >> > Undergraduate Student,
> > >> > Department of Computer Science and Engineering,
> > >> > University of Moratuwa.
> > >>
> > >
> > >
> > >
> > > --
> > > W. A. Dulanga Sashika,
> > > Undergraduate Student,
> > > Department of Computer Science and Engineering,
> > > University of Moratuwa.
> >
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

I made this design using Photoshop. Therefore, I used these icons and fonts
just to show how it looks like. Since this is the first design, I thought
it will not be a big issue. We can change them at any time.
Previously we talked about "Custom Widgets". As I understand it, there will
be a option as "custom widgets" in the dashboard and if we click on that,
it will go to a page where we can select/remove widgets from the dashboard.
If yours and Alex's intention about "Custom Widgets" are different from
this, please correct me :) I might be wrong about that.
Another thing is that, I do not know exactly what are the important items
to include into "Active Tasks" and "Recently Visited Databases" tables. I
put items that came into my mind as important. We can change them also.
Actually this one is for just to get an idea about the dashboard. As you
said, this will help to think about problems that might occur. All we need
is the ideas from the community :) then we can come up with a better design
than this.

Regards

On Sun, Mar 22, 2015 at 5:28 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Cool! Thank you!
>
> Creating a mock-up is a good way to get some initial feedback and
> helps to think about problems that might occur. Probably Sean or
> another designer will take a final look at the final work you create
> in terms of design.
>
> One question that came to my mind while looking at the dashboard was:
> "what happens if we click on custom widgets?"
>
> Btw have you seen our icon fonts?
>
> We have an own at
>
> https://github.com/apache/couchdb-fauxton/blob/master/assets/fonts/styleguide/fauxtonicon-preview.html
> and additionally support the glyphicons from bootstrap 2.3:
> http://getbootstrap.com/2.3.2/base-css.html#icons
>
>
> Best,
> Robert
>
> On Sat, Mar 21, 2015 at 9:00 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi Robert,
> >
> > Here is the mock up I designed for the dashboard.
> > https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
> >
> > Please give some comments and we can change this later by discussing the
> > important facts that we should show in the dashboard. For now I designed
> a
> > mock up only for dashboard and I can make designs for each widgets later.
> >
> > Thank You
> >
> >
> > On Fri, Mar 20, 2015 at 8:12 PM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >
> >> Cool thank you!
> >>
> >> Yes I also did not know until someone told me 2 months ago :)
> >>
> >> On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <wa...@gmail.com>
> >> wrote:
> >> > Hi Robert,
> >> >
> >> > Thank you very much for the help. I can carry on from there now.
> >> Actually I
> >> > didn't know that this mailing list does not supported for attachments.
> >> Here
> >> > is the screenshots I uploaded.
> >> >
> >> > img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
> >> > img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
> >> > img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
> >> > img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
> >> > img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
> >> > img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
> >> >
> >> > And I will share the proposal ASAP with you.
> >> >
> >> > Thank you
> >> >
> >> > On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd>
> >> wrote:
> >> >
> >> >> Hi Dulanga,
> >> >>
> >> >> glad you figured it out while I was on a train! :)
> >> >>
> >> >> Can you upload the pictures to something like box.com / dropbox or
> an
> >> >> image hoster as the list does not support attachments?
> >> >>
> >> >> We are storing our react components in files like
> >> >>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
> >> >>
> >> >> To render them we still have to wrap them in Backbone Views - as our
> >> >> framework is built for Backbone views. The backbone view files are
> >> >> usually called `views.js`. This will go away soon but currently it is
> >> >> the way to go:
> >> >>
> >> >>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> >> >>
> >> >> which calls this at the bottom of
> >> `app/addons/cors/components.react.jsx`:
> >> >>
> >> >>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
> >> >>
> >> >>
> >> >> In
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> >> >> `this.el` references the DOM-Node of the Backbone view in which then
> >> >> the React Component is rendered into.
> >> >>
> >> >>
> >> >> Regarding the proposal:
> >> >>
> >> >> I am happy to help you with your proposal it would be nice to have an
> >> >> option that makes it easy to leave comments (e.g google docs)
> >> >>
> >> >> Best,
> >> >> Robert
> >> >>
> >> >> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <
> wadsashika@gmail.com>
> >> >> wrote:
> >> >> > Hi,
> >> >> > Here I attached the screen shots of Dashboard menu item. Now its
> >> working.
> >> >> > Now I want to know that, if I need to implement react component,
> where
> >> >> > should I put it? And how can I access that to render the view? just
> >> give
> >> >> me
> >> >> > some hints and I can carry on from there.
> >> >> >
> >> >> > Regards
> >> >> >
> >> >> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <
> >> wadsashika@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> Hey Robert, problem solved.. :)
> >> >> >>
> >> >> >>
> >> >> >> Regards.
> >> >> >>
> >> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <
> >> wadsashika@gmail.com>
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> Hi Robert,
> >> >> >>>
> >> >> >>> Now I am trying to create a new menu item for dashboard and
> >> implement a
> >> >> >>> react component as you said. But now I am stuck in some place and
> >> >> couldn't
> >> >> >>> figure out the problem yet. Here is the problem I had in
> process. I
> >> >> added
> >> >> >>> dashboard menu item and added route and view for that. And i
> change
> >> >> the code
> >> >> >>> to render dashboard when we enter http://localhost:8000 . As in
> >> img1
> >> >> and
> >> >> >>> img2, it doesn't show the view I created. But when I click on
> >> another
> >> >> menu
> >> >> >>> item and come back to the dashboard, it shows the breadcrumb of
> >> >> previous
> >> >> >>> pages as img 3 and 4. As in
> >> >> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> >> >> >>> , I called the new Dashboard.view() which is a component in my
> >> >> view.js. But
> >> >> >>> in the console, it shows Uncaught Type error. Did I miss any
> >> >> configuration
> >> >> >>> thing or did I do it wrong?
> >> >> >>>
> >> >> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
> >> >> wadsashika@gmail.com>
> >> >> >>> wrote:
> >> >> >>>>
> >> >> >>>> Hi Robert,
> >> >> >>>>
> >> >> >>>> Thank you very much for the reference. I started to write the
> >> proposal
> >> >> >>>> today. I hope you will help to write this proposal by reviewing
> >> it.
> >> >> I will
> >> >> >>>> share it with you after complete the draft of the proposal.
> >> >> >>>>
> >> >> >>>> Thank you
> >> >> >>>>
> >> >> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <
> rok@kowalski.gd>
> >> >> >>>> wrote:
> >> >> >>>>>
> >> >> >>>>> Some of you asked for a template for their proposals, here is
> what
> >> >> I've
> >> >> >>>>> found:
> >> >> >>>>>
> >> >> >>>>> http://community.staging.apache.org/gsoc#application-template
> >> >> >>>>>
> >> >> >>>>> Best,
> >> >> >>>>> Robert
> >> >> >>>>>
> >> >> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <
> >> rok@kowalski.gd>
> >> >> >>>>> wrote:
> >> >> >>>>> > Wow you are making very good progress!
> >> >> >>>>> >
> >> >> >>>>> > We have our weekly status meetup tomorrow (see [1] for the
> time
> >> in
> >> >> >>>>> > your timezone), feel free to join, meet other project members
> >> and
> >> >> >>>>> > learn what the project is currently doing next to the Summer
> of
> >> >> Code.
> >> >> >>>>> >
> >> >> >>>>> > I will also be around 1hr earlier to answer all your
> questions
> >> and
> >> >> >>>>> > discuss our next steps.
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> > [1]
> >> >> >>>>> >
> >> >>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >> >>>>> >
> >> >> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
> >> >> >>>>> > <wa...@gmail.com> wrote:
> >> >> >>>>> >> Hi Robert,
> >> >> >>>>> >>
> >> >> >>>>> >> Here is the current status of the checklist :)
> >> >> >>>>> >>
> >> >> >>>>> >>  - check out the active tasks api (linked on top of this
> mail)
> >> -
> >> >> >>>>> >> (finished)
> >> >> >>>>> >>  - a mockup showing some widgets and how they could look
> like -
> >> >> >>>>> >> (started
> >> >> >>>>> >> but not finished yet)
> >> >> >>>>> >>  - code React tutorial & read about Flux - (finished)
> >> >> >>>>> >>  - take a look how we are using React - (finished)
> >> >> >>>>> >>  - create another menu item, called "Dashboard", try to
> answer
> >> the
> >> >> >>>>> >> questions to route.js et al - (started but not finished yet)
> >> >> >>>>> >>  - get familiar how we test our code - (finished)
> >> >> >>>>> >>  - write an hello world / hello from dulanga component that
> is
> >> >> >>>>> >> rendered into a screen when opening
> http://localhost:8000/dash
> >> >> or by
> >> >> >>>>> >> clicking on "dashboard" in the sidebar - (started but not
> >> finished
> >> >> >>>>> >> yet)
> >> >> >>>>> >>
> >> >> >>>>> >> I will do my best to complete all these by tomorrow. If I
> have
> >> any
> >> >> >>>>> >> problem,
> >> >> >>>>> >> I will trouble you as you wished yesterday :)
> >> >> >>>>> >>
> >> >> >>>>> >> Thank You
> >> >> >>>>> >>
> >> >> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <
> >> rok@kowalski.gd
> >> >> >
> >> >> >>>>> >> wrote:
> >> >> >>>>> >>
> >> >> >>>>> >>> Hi Dulanga,
> >> >> >>>>> >>>
> >> >> >>>>> >>> we already talked on irc and you already talked to Alex
> >> regarding
> >> >> >>>>> >>> features for our dashboard. That's great!
> >> >> >>>>> >>>
> >> >> >>>>> >>> Some topics will repeat in this mail, but I also would like
> >> the
> >> >> ML
> >> >> >>>>> >>> to
> >> >> >>>>> >>> follow our project and additionally add some more in-depth
> >> >> >>>>> >>> informations.
> >> >> >>>>> >>>
> >> >> >>>>> >>> Recap & additons
> >> >> >>>>> >>> =====
> >> >> >>>>> >>>
> >> >> >>>>> >>> As discussed we will work in an iterative approach and add
> >> widget
> >> >> >>>>> >>> after widget so if we run out of time, we will have
> something
> >> to
> >> >> >>>>> >>> deliver and don't have to throw everything away.
> >> >> >>>>> >>>
> >> >> >>>>> >>> Have you seen the "database" tab or the "config" tab in the
> >> >> sidebar
> >> >> >>>>> >>> on the
> >> >> >>>>> >>> left?
> >> >> >>>>> >>>
> >> >> >>>>> >>> Those are modules that we can hook into the Fauxton build,
> by
> >> >> >>>>> >>> configuration. I think the idea is to create a tab
> "dashboard"
> >> >> >>>>> >>> which
> >> >> >>>>> >>> is the default one after opening Fauxton in the browser. So
> >> you
> >> >> >>>>> >>> would
> >> >> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
> >> >> >>>>> >>>
> >> >> >>>>> >>> Alex ideas so far:
> >> >> >>>>> >>>
> >> >> >>>>> >>> ```
> >> >> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue
> there
> >> are
> >> >> >>>>> >>> some
> >> >> >>>>> >>> points about showing stats and log - forget these (: _stats
> >> isn't
> >> >> >>>>> >>> available for
> >> >> >>>>> >>>                    cluster iface and _log is removed. but
> >> >> recently
> >> >> >>>>> >>> visited databases, active tasks and _users/_replicator
> quick
> >> >> >>>>> >>> management is what could
> >> >> >>>>> >>>                    be really handy.
> >> >> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not
> >> relevant
> >> >> >>>>> >>> anymore after backporting some cloudant features
> >> >> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way
> >> how
> >> >> (:
> >> >> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of
> widgets,
> >> I
> >> >> >>>>> >>> believe you could make some builtin and leave a template
> one
> >> to
> >> >> let
> >> >> >>>>> >>> the end users create
> >> >> >>>>> >>>                    their own if they're able/would like
> to. in
> >> >> >>>>> >>> future
> >> >> >>>>> >>> these are could be fauxton plugins or something.
> >> >> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice
> idea
> >> >> for a
> >> >> >>>>> >>> hot
> >> >> >>>>> >>> widget.
> >> >> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely
> help
> >> with
> >> >> >>>>> >>> that
> >> >> >>>>> >>> (add custom widgets on build time) - the build is
> complicated,
> >> >> but
> >> >> >>>>> >>> once explained
> >> >> >>>>> >>>                            it should be easy
> >> >> >>>>> >>> ```
> >> >> >>>>> >>>
> >> >> >>>>> >>> So we have "custom widgets", "cluster quick-management", "
> >> >> recently
> >> >> >>>>> >>> visited databases",  "active tasks" and "_users/_replicator
> >> quick
> >> >> >>>>> >>> management"
> >> >> >>>>> >>>
> >> >> >>>>> >>> I think two good widgets for starting are active tasks and
> >> >> recently
> >> >> >>>>> >>> visited databases.
> >> >> >>>>> >>>
> >> >> >>>>> >>> For active tasks we have some nice docs:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> >> >> >>>>> >>>
> >> >> >>>>> >>> They have an own dedicated page in Fauxton (see
> >> >> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick
> >> condensed
> >> >> >>>>> >>> list
> >> >> >>>>> >>> is probably very interesting to users.
> >> >> >>>>> >>>
> >> >> >>>>> >>> For the recently visited databases we would have to store
> that
> >> >> >>>>> >>> somewhere.
> >> >> >>>>> >>>
> >> >> >>>>> >>> If you want, you can take an existing page in Fauxton and
> just
> >> >> >>>>> >>> modify
> >> >> >>>>> >>> the markup for a design mockup how the widget view may look
> >> like.
> >> >> >>>>> >>> But
> >> >> >>>>> >>> feel also free to use pen/paper or other tools if you like
> >> that
> >> >> the
> >> >> >>>>> >>> most.
> >> >> >>>>> >>>
> >> >> >>>>> >>> For the mango feature I am currently working on, I took the
> >> "edit
> >> >> >>>>> >>> view" template on modified the markup using the Chrome
> >> inspector
> >> >> of
> >> >> >>>>> >>> my
> >> >> >>>>> >>> browser to collect some first feedback from the project
> >> members
> >> >> and
> >> >> >>>>> >>> my
> >> >> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have
> any
> >> >> >>>>> >>> functionality, but gives other folks a rough idea what my
> idea
> >> >> for
> >> >> >>>>> >>> the
> >> >> >>>>> >>> feature is.
> >> >> >>>>> >>>
> >> >> >>>>> >>> the framework and react
> >> >> >>>>> >>>
> >> >> >>>>> >>> As I already mentioned we are using React.js.
> >> >> >>>>> >>>
> >> >> >>>>> >>> It would be nice if you can finish the tutorial at
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> >> >> >>>>> >>> until next friday by following the steps and writing that
> >> code.
> >> >> >>>>> >>> After
> >> >> >>>>> >>> that, read
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> >> >> >>>>> >>> to get a first impression how the Flux pattern works that
> we
> >> are
> >> >> >>>>> >>> using.
> >> >> >>>>> >>>
> >> >> >>>>> >>> After that (if you still have time left) take a look on a
> >> >> component
> >> >> >>>>> >>> that Garren, my coworker refactored from Backbone.js to
> React:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> >> >> >>>>> >>>
> >> >> >>>>> >>> Please take a look how the data flows from the Components,
> >> using
> >> >> >>>>> >>> the
> >> >> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to
> litter
> >> >> >>>>> >>> everything in the code with console.log to see how state
> >> changes
> >> >> >>>>> >>> and
> >> >> >>>>> >>> how the data flows.
> >> >> >>>>> >>>
> >> >> >>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>> If you still have time, just try to create another menu
> item,
> >> >> >>>>> >>> called
> >> >> >>>>> >>> "Dashboard". Take a look at:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> >> >> >>>>> >>>
> >> >> >>>>> >>> to get a first idea how to do that. Some background
> >> information:
> >> >> >>>>> >>>
> >> >> >>>>> >>> base.js - the starting point of our module. basic
> >> configuration
> >> >> is
> >> >> >>>>> >>> done
> >> >> >>>>> >>> here
> >> >> >>>>> >>> Question: what is `base.js` used for in the case of the
> config
> >> >> >>>>> >>> module?
> >> >> >>>>> >>>
> >> >> >>>>> >>> routes.js - takes care that functions injecting the view
> into
> >> the
> >> >> >>>>> >>> layout are called depending on the url given
> >> >> >>>>> >>> Question: What happens if I call
> `http:localhost:8000/_config`
> >> >> and
> >> >> >>>>> >>> what happens if you remove the function `apiUrl`?
> >> >> >>>>> >>>
> >> >> >>>>> >>> views.js - contains our views - this file contains still a
> lot
> >> >> >>>>> >>> backbone views, which we are currently migrating to react.
> >> maybe
> >> >> it
> >> >> >>>>> >>> makes more sense to take a look at one of our react
> >> components:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> >> >> >>>>> >>>
> >> >> >>>>> >>> and how they are used currently (as we are migrating to
> react
> >> >> >>>>> >>> currently):
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> >> >> >>>>> >>>
> >> >> >>>>> >>> The Objects are injected into the closures using AMD:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> >> >> >>>>> >>>
> >> >> >>>>> >>> assets folder:
> >> >> >>>>> >>> contains our less which is compiled to css
> >> >> >>>>> >>>
> >> >> >>>>> >>> templates folder:
> >> >> >>>>> >>> contains old backbone.js templates, you will not need them
> >> >> >>>>> >>>
> >> >> >>>>> >>> tests folder:
> >> >> >>>>> >>> contains unit and integration tests, every PR must have
> unit
> >> >> tests
> >> >> >>>>> >>> and
> >> >> >>>>> >>> integration tests. If you never wrote tests, we will
> explain
> >> it
> >> >> to
> >> >> >>>>> >>> you
> >> >> >>>>> >>> - it is easy once you wrote your first few ones. Basically
> you
> >> >> are
> >> >> >>>>> >>> testing each time that if you put something into a
> function,
> >> the
> >> >> >>>>> >>> expected result happens. Or that if you take an action, a
> >> state
> >> >> has
> >> >> >>>>> >>> changed.
> >> >> >>>>> >>>
> >> >> >>>>> >>> You can run the unit tests using `grunt test`
> >> >> >>>>> >>>
> >> >> >>>>> >>> Single tests are run by:
> >> >> >>>>> >>>
> >> >> >>>>> >>> ```
> >> >> >>>>> >>> grunt test
> >> >> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
> >> >> >>>>> >>> ```
> >> >> >>>>> >>>
> >> >> >>>>> >>> or in the browser by test group:
> >> >> >>>>> >>>
> >> >> >>>>> >>> ```
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> >> >> >>>>> >>> ```
> >> >> >>>>> >>>
> >> >> >>>>> >>> (change path to your fauxton directory)
> >> >> >>>>> >>>
> >> >> >>>>> >>> The corresponding code is:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> >> >> >>>>> >>>
> >> >> >>>>> >>> and these tests are a good example how to write a simple
> test
> >> for
> >> >> >>>>> >>> the
> >> >> >>>>> >>> hello world/hello from dulanga-component:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>> First steps:
> >> >> >>>>> >>>
> >> >> >>>>> >>> Create a module `dashboard` that gets displayed in the
> >> sidebar.
> >> >> The
> >> >> >>>>> >>> route http://localhost:8000/dash will render a small React
> >> >> >>>>> >>> component
> >> >> >>>>> >>> that display "Hello World".
> >> >> >>>>> >>>
> >> >> >>>>> >>> If you click on the "Hello World" it ill change the content
> >> to:
> >> >> >>>>> >>> "Hello
> >> >> >>>>> >>> from Dulanga"
> >> >> >>>>> >>>
> >> >> >>>>> >>> While we will throw the small component away afterwards we
> >> will
> >> >> >>>>> >>> build
> >> >> >>>>> >>> upon the other code you created. If you have time left,
> add a
> >> >> test
> >> >> >>>>> >>> that the component changes the content.
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>> Meeting Wednesday:
> >> >> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >> >>>>> >>>
> >> >> >>>>> >>> I will be around at least one hour before so we can chat.
> >> Contact
> >> >> >>>>> >>> me
> >> >> >>>>> >>> if you would like to chat earlier/later. I am also around
> the
> >> >> other
> >> >> >>>>> >>> days on IRC / the mailinglist and feel free to contact me
> in
> >> >> >>>>> >>> #couchdb-dev at any time. If I am not around I will answer
> you
> >> >> once
> >> >> >>>>> >>> I
> >> >> >>>>> >>> got online again, as I read the backlog.
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
> >> >> >>>>> >>>
> >> >> >>>>> >>>  - check out the active tasks api (linked on top of this
> mail)
> >> >> >>>>> >>>  - a mockup showing some widgets and how they could look
> like
> >> >> >>>>> >>>  - code React tutorial & read about Flux
> >> >> >>>>> >>>  - take a look how we are using React
> >> >> >>>>> >>>  - create another menu item, called "Dashboard", try to
> answer
> >> >> the
> >> >> >>>>> >>> questions to route.js et al
> >> >> >>>>> >>>  - get familiar how we test our code
> >> >> >>>>> >>>  - write an hello world / hello from dulanga component
> that is
> >> >> >>>>> >>> rendered into a screen when opening
> >> http://localhost:8000/dash
> >> >> or
> >> >> >>>>> >>> by
> >> >> >>>>> >>> clicking on "dashboard" in the sidebar
> >> >> >>>>> >>>
> >> >> >>>>> >>> That was a lot of content and please don't feel
> discouraged if
> >> >> you
> >> >> >>>>> >>> don't get that far until Wednesday. We will have to find a
> >> speed
> >> >> >>>>> >>> which
> >> >> >>>>> >>> is perfect for you and this time I tried to give enough
> >> >> >>>>> >>> informations
> >> >> >>>>> >>> that you are not blocked until Wednesday by waiting for
> next
> >> >> steps.
> >> >> >>>>> >>> If
> >> >> >>>>> >>> you are at the last step before Wednesday, drop me a line
> and
> >> I
> >> >> >>>>> >>> will
> >> >> >>>>> >>> prepare the next steps :)
> >> >> >>>>> >>>
> >> >> >>>>> >>> I know that you all have important exams, these are
> definitely
> >> >> more
> >> >> >>>>> >>> important! Don't feel pressured by the amount of work / the
> >> >> amount
> >> >> >>>>> >>> of
> >> >> >>>>> >>> informations, getting good results in the exams should be
> your
> >> >> >>>>> >>> first
> >> >> >>>>> >>> priority.
> >> >> >>>>> >>>
> >> >> >>>>> >>> Best,
> >> >> >>>>> >>> Robert
> >> >> >>>>> >>>
> >> >> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
> >> >> >>>>> >>> <wa...@gmail.com>
> >> >> >>>>> >>> wrote:
> >> >> >>>>> >>> > Hi Robert,
> >> >> >>>>> >>> >
> >> >> >>>>> >>> > I went through the guidelines you provided and
> successfully
> >> >> >>>>> >>> > installed and
> >> >> >>>>> >>> > configured as you said. Everything works find and I
> played
> >> >> around
> >> >> >>>>> >>> > it by
> >> >> >>>>> >>> > creating a database and documents. I think I am ready for
> >> the
> >> >> >>>>> >>> > next step
> >> >> >>>>> >>> and
> >> >> >>>>> >>> > we can start it if you are ok :)
> >> >> >>>>> >>> >
> >> >> >>>>> >>> > Thank You
> >> >> >>>>> >>> >
> >> >> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
> >> >> >>>>> >>> > <ro...@kowalski.gd>
> >> >> >>>>> >>> wrote:
> >> >> >>>>> >>> >
> >> >> >>>>> >>> >> You're welcome.
> >> >> >>>>> >>> >>
> >> >> >>>>> >>> >> I also hang out in the couchdb-dev channel for around
> >> 1-3hrs
> >> >> if
> >> >> >>>>> >>> >> you get
> >> >> >>>>> >>> >> stuck!
> >> >> >>>>> >>> >>
> >> >> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
> >> >> >>>>> >>> >> <wa...@gmail.com>
> >> >> >>>>> >>> >> wrote:
> >> >> >>>>> >>> >> > Hi Robert,
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> > Thank you very much for the quick reply. I will go
> >> through
> >> >> the
> >> >> >>>>> >>> guidelines
> >> >> >>>>> >>> >> > and contact you if I have any issue with them.
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> > Thank you
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
> >> >> >>>>> >>> >> > <ro...@kowalski.gd>
> >> >> >>>>> >>> >> wrote:
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> >> Hi Dulanga,
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> glad you found your way to the CouchDB mailing list.
> >> >> Welcome
> >> >> >>>>> >>> >> >> :)
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP
> >> API -
> >> >> >>>>> >>> >> >> that makes
> >> >> >>>>> >>> >> >> it a great fit for web applications that don't need a
> >> >> server
> >> >> >>>>> >>> >> >> side
> >> >> >>>>> >>> >> >> layer with a database driver in between. Our Project
> >> >> Fauxton
> >> >> >>>>> >>> >> >> (like a
> >> >> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev
> >> including
> >> >> >>>>> >>> >> >> myself.
> >> >> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one
> is
> >> >> >>>>> >>> >> >> online (e.g.
> >> >> >>>>> >>> I
> >> >> >>>>> >>> >> >> was travelling this week) feel free to ask on the dev
> >> ML.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> We are all happy to help each other in the project :)
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> If you are using windows: I am not a Windows expert -
> >> you
> >> >> >>>>> >>> >> >> will
> >> >> >>>>> >>> >> >> probably have to use a bash emulator like "git bash"
> to
> >> >> boot
> >> >> >>>>> >>> >> >> the dev
> >> >> >>>>> >>> >> >> environment.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Getting started:
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> For this project you will need to install at least
> >> CouchDB
> >> >> >>>>> >>> >> >> 1.x, an
> >> >> >>>>> >>> >> >> Ubuntu package (with installation instructions) is at
> >> >> >>>>> >>> >> >>
> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
> >> >> >>>>> >>> >> >> (install from
> >> >> >>>>> >>> >> >> https://nodejs.org)
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> booting CouchDB:
> >> >> >>>>> >>> >> >> $ sudo couchdb
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> in another terminal, clone the admin interface:
> >> >> >>>>> >>> >> >> $ git clone
> https://github.com/apache/couchdb-fauxton
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> go to Fauxton:
> >> >> >>>>> >>> >> >> $ cd couchdb-fauxton
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> install dependencies:
> >> >> >>>>> >>> >> >> $ npm install
> >> >> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> boot the app:
> >> >> >>>>> >>> >> >> $ grunt dev
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Then open your browser and go to
> http://localhost:8000
> >> -
> >> >> you
> >> >> >>>>> >>> >> >> should
> >> >> >>>>> >>> >> >> see a red/gray/black interface
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> That was a lot of input and especially if you are
> using
> >> >> Linux
> >> >> >>>>> >>> >> >> the
> >> >> >>>>> >>> >> >> first time and followed the instructions you have
> >> archived
> >> >> a
> >> >> >>>>> >>> >> >> lot!
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> As first step, try to create a database and a
> document
> >> now
> >> >> >>>>> >>> >> >> using the
> >> >> >>>>> >>> >> >> web interface (PS we are happy about any usability
> >> >> feedback).
> >> >> >>>>> >>> >> >> :)
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> I think you have your dev environment for CouchDB
> ready
> >> >> now.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> What's next:
> >> >> >>>>> >>> >> >> If everything works we will take a look at Fauxtons
> code
> >> >> >>>>> >>> >> >> structure
> >> >> >>>>> >>> and
> >> >> >>>>> >>> >> >> how it works. We will also talk about the features of
> >> the
> >> >> >>>>> >>> >> >> dashboard.
> >> >> >>>>> >>> >> >> Let's find a date for a chat after you took a first
> look
> >> >> how
> >> >> >>>>> >>> >> >> Fauxton
> >> >> >>>>> >>> >> >> looks like.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> We are having our weekly meeting this Wednesday,
> >> 20:00GMT
> >> >> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in
> >> IRC
> >> >> on
> >> >> >>>>> >>> >> >> freenode
> >> >> >>>>> >>> >> >> (see
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >>
> >> >> >>>>> >>>
> >> >> >>>>> >>>
> >> >>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >> >>>>> >>> >> >> )
> >> >> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before
> if
> >> you
> >> >> >>>>> >>> >> >> want to
> >> >> >>>>> >>> >> >> chat with me before.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> Looking forward to work with you,
> >> >> >>>>> >>> >> >> Robert
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> >> >> >>>>> >>> wadsashika@gmail.com>
> >> >> >>>>> >>> >> >> wrote:
> >> >> >>>>> >>> >> >> > Hi all,
> >> >> >>>>> >>> >> >> >
> >> >> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year
> >> undergraduate
> >> >> >>>>> >>> >> >> > student at
> >> >> >>>>> >>> >> >> > Computer Science and Engineering department at
> >> University
> >> >> >>>>> >>> >> >> > of
> >> >> >>>>> >>> Moratuwa,
> >> >> >>>>> >>> >> >> Sri
> >> >> >>>>> >>> >> >> > Lanka. I am really interested in java, java script,
> >> web
> >> >> >>>>> >>> applications,
> >> >> >>>>> >>> >> >> > algorithms, data mining and machine learning. I
> have 6
> >> >> >>>>> >>> >> >> > months of
> >> >> >>>>> >>> >> training
> >> >> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I
> worked
> >> >> on a
> >> >> >>>>> >>> >> >> > web
> >> >> >>>>> >>> >> >> application
> >> >> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My final
> >> year
> >> >> >>>>> >>> >> >> > project
> >> >> >>>>> >>> also a
> >> >> >>>>> >>> >> >> web
> >> >> >>>>> >>> >> >> > related application and I used same technologies I
> >> >> >>>>> >>> >> >> > mentioned above
> >> >> >>>>> >>> for
> >> >> >>>>> >>> >> >> > that. I am really interested in this project
> because I
> >> >> have
> >> >> >>>>> >>> >> >> > a good
> >> >> >>>>> >>> >> >> > experience with web applications and I love work
> with
> >> >> >>>>> >>> >> >> > javascript.
> >> >> >>>>> >>> I am
> >> >> >>>>> >>> >> >> > looking forward to contribute to this project in
> this
> >> >> >>>>> >>> >> >> > summer. I
> >> >> >>>>> >>> like
> >> >> >>>>> >>> >> to
> >> >> >>>>> >>> >> >> > know more detail about this project and if you can,
> >> >> please
> >> >> >>>>> >>> >> >> > guide
> >> >> >>>>> >>> me to
> >> >> >>>>> >>> >> >> > start working on this project.
> >> >> >>>>> >>> >> >> >
> >> >> >>>>> >>> >> >> > Thank you.
> >> >> >>>>> >>> >> >> >
> >> >> >>>>> >>> >> >> > W. A. Dulanga Sashika,
> >> >> >>>>> >>> >> >> > Undergraduate Student,
> >> >> >>>>> >>> >> >> > Department of Computer Science and Engineering,
> >> >> >>>>> >>> >> >> > University of Moratuwa.
> >> >> >>>>> >>> >> >>
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> >
> >> >> >>>>> >>> >> > --
> >> >> >>>>> >>> >> > W. A. Dulanga Sashika,
> >> >> >>>>> >>> >> > Undergraduate Student,
> >> >> >>>>> >>> >> > Department of Computer Science and Engineering,
> >> >> >>>>> >>> >> > University of Moratuwa.
> >> >> >>>>> >>> >>
> >> >> >>>>> >>> >
> >> >> >>>>> >>> >
> >> >> >>>>> >>> >
> >> >> >>>>> >>> > --
> >> >> >>>>> >>> > W. A. Dulanga Sashika,
> >> >> >>>>> >>> > Undergraduate Student,
> >> >> >>>>> >>> > Department of Computer Science and Engineering,
> >> >> >>>>> >>> > University of Moratuwa.
> >> >> >>>>> >>>
> >> >> >>>>> >>
> >> >> >>>>> >>
> >> >> >>>>> >>
> >> >> >>>>> >> --
> >> >> >>>>> >> W. A. Dulanga Sashika,
> >> >> >>>>> >> Undergraduate Student,
> >> >> >>>>> >> Department of Computer Science and Engineering,
> >> >> >>>>> >> University of Moratuwa.
> >> >> >>>>
> >> >> >>>>
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> --
> >> >> >>>> W. A. Dulanga Sashika,
> >> >> >>>> Undergraduate Student,
> >> >> >>>> Department of Computer Science and Engineering,
> >> >> >>>> University of Moratuwa.
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> --
> >> >> >>> W. A. Dulanga Sashika,
> >> >> >>> Undergraduate Student,
> >> >> >>> Department of Computer Science and Engineering,
> >> >> >>> University of Moratuwa.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> W. A. Dulanga Sashika,
> >> >> >> Undergraduate Student,
> >> >> >> Department of Computer Science and Engineering,
> >> >> >> University of Moratuwa.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > W. A. Dulanga Sashika,
> >> >> > Undergraduate Student,
> >> >> > Department of Computer Science and Engineering,
> >> >> > University of Moratuwa.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > W. A. Dulanga Sashika,
> >> > Undergraduate Student,
> >> > Department of Computer Science and Engineering,
> >> > University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Cool! Thank you!

Creating a mock-up is a good way to get some initial feedback and
helps to think about problems that might occur. Probably Sean or
another designer will take a final look at the final work you create
in terms of design.

One question that came to my mind while looking at the dashboard was:
"what happens if we click on custom widgets?"

Btw have you seen our icon fonts?

We have an own at
https://github.com/apache/couchdb-fauxton/blob/master/assets/fonts/styleguide/fauxtonicon-preview.html
and additionally support the glyphicons from bootstrap 2.3:
http://getbootstrap.com/2.3.2/base-css.html#icons


Best,
Robert

On Sat, Mar 21, 2015 at 9:00 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> Here is the mock up I designed for the dashboard.
> https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0
>
> Please give some comments and we can change this later by discussing the
> important facts that we should show in the dashboard. For now I designed a
> mock up only for dashboard and I can make designs for each widgets later.
>
> Thank You
>
>
> On Fri, Mar 20, 2015 at 8:12 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Cool thank you!
>>
>> Yes I also did not know until someone told me 2 months ago :)
>>
>> On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi Robert,
>> >
>> > Thank you very much for the help. I can carry on from there now.
>> Actually I
>> > didn't know that this mailing list does not supported for attachments.
>> Here
>> > is the screenshots I uploaded.
>> >
>> > img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
>> > img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
>> > img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
>> > img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
>> > img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
>> > img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
>> >
>> > And I will share the proposal ASAP with you.
>> >
>> > Thank you
>> >
>> > On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>> >
>> >> Hi Dulanga,
>> >>
>> >> glad you figured it out while I was on a train! :)
>> >>
>> >> Can you upload the pictures to something like box.com / dropbox or an
>> >> image hoster as the list does not support attachments?
>> >>
>> >> We are storing our react components in files like
>> >>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
>> >>
>> >> To render them we still have to wrap them in Backbone Views - as our
>> >> framework is built for Backbone views. The backbone view files are
>> >> usually called `views.js`. This will go away soon but currently it is
>> >> the way to go:
>> >>
>> >>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
>> >>
>> >> which calls this at the bottom of
>> `app/addons/cors/components.react.jsx`:
>> >>
>> >>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
>> >>
>> >>
>> >> In
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
>> >> `this.el` references the DOM-Node of the Backbone view in which then
>> >> the React Component is rendered into.
>> >>
>> >>
>> >> Regarding the proposal:
>> >>
>> >> I am happy to help you with your proposal it would be nice to have an
>> >> option that makes it easy to leave comments (e.g google docs)
>> >>
>> >> Best,
>> >> Robert
>> >>
>> >> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <wa...@gmail.com>
>> >> wrote:
>> >> > Hi,
>> >> > Here I attached the screen shots of Dashboard menu item. Now its
>> working.
>> >> > Now I want to know that, if I need to implement react component, where
>> >> > should I put it? And how can I access that to render the view? just
>> give
>> >> me
>> >> > some hints and I can carry on from there.
>> >> >
>> >> > Regards
>> >> >
>> >> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Hey Robert, problem solved.. :)
>> >> >>
>> >> >>
>> >> >> Regards.
>> >> >>
>> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi Robert,
>> >> >>>
>> >> >>> Now I am trying to create a new menu item for dashboard and
>> implement a
>> >> >>> react component as you said. But now I am stuck in some place and
>> >> couldn't
>> >> >>> figure out the problem yet. Here is the problem I had in process. I
>> >> added
>> >> >>> dashboard menu item and added route and view for that. And i change
>> >> the code
>> >> >>> to render dashboard when we enter http://localhost:8000 . As in
>> img1
>> >> and
>> >> >>> img2, it doesn't show the view I created. But when I click on
>> another
>> >> menu
>> >> >>> item and come back to the dashboard, it shows the breadcrumb of
>> >> previous
>> >> >>> pages as img 3 and 4. As in
>> >> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
>> >> >>> , I called the new Dashboard.view() which is a component in my
>> >> view.js. But
>> >> >>> in the console, it shows Uncaught Type error. Did I miss any
>> >> configuration
>> >> >>> thing or did I do it wrong?
>> >> >>>
>> >> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
>> >> wadsashika@gmail.com>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> Hi Robert,
>> >> >>>>
>> >> >>>> Thank you very much for the reference. I started to write the
>> proposal
>> >> >>>> today. I hope you will help to write this proposal by reviewing
>> it.
>> >> I will
>> >> >>>> share it with you after complete the draft of the proposal.
>> >> >>>>
>> >> >>>> Thank you
>> >> >>>>
>> >> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
>> >> >>>> wrote:
>> >> >>>>>
>> >> >>>>> Some of you asked for a template for their proposals, here is what
>> >> I've
>> >> >>>>> found:
>> >> >>>>>
>> >> >>>>> http://community.staging.apache.org/gsoc#application-template
>> >> >>>>>
>> >> >>>>> Best,
>> >> >>>>> Robert
>> >> >>>>>
>> >> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <
>> rok@kowalski.gd>
>> >> >>>>> wrote:
>> >> >>>>> > Wow you are making very good progress!
>> >> >>>>> >
>> >> >>>>> > We have our weekly status meetup tomorrow (see [1] for the time
>> in
>> >> >>>>> > your timezone), feel free to join, meet other project members
>> and
>> >> >>>>> > learn what the project is currently doing next to the Summer of
>> >> Code.
>> >> >>>>> >
>> >> >>>>> > I will also be around 1hr earlier to answer all your questions
>> and
>> >> >>>>> > discuss our next steps.
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > [1]
>> >> >>>>> >
>> >>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >> >>>>> >
>> >> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
>> >> >>>>> > <wa...@gmail.com> wrote:
>> >> >>>>> >> Hi Robert,
>> >> >>>>> >>
>> >> >>>>> >> Here is the current status of the checklist :)
>> >> >>>>> >>
>> >> >>>>> >>  - check out the active tasks api (linked on top of this mail)
>> -
>> >> >>>>> >> (finished)
>> >> >>>>> >>  - a mockup showing some widgets and how they could look like -
>> >> >>>>> >> (started
>> >> >>>>> >> but not finished yet)
>> >> >>>>> >>  - code React tutorial & read about Flux - (finished)
>> >> >>>>> >>  - take a look how we are using React - (finished)
>> >> >>>>> >>  - create another menu item, called "Dashboard", try to answer
>> the
>> >> >>>>> >> questions to route.js et al - (started but not finished yet)
>> >> >>>>> >>  - get familiar how we test our code - (finished)
>> >> >>>>> >>  - write an hello world / hello from dulanga component that is
>> >> >>>>> >> rendered into a screen when opening http://localhost:8000/dash
>> >> or by
>> >> >>>>> >> clicking on "dashboard" in the sidebar - (started but not
>> finished
>> >> >>>>> >> yet)
>> >> >>>>> >>
>> >> >>>>> >> I will do my best to complete all these by tomorrow. If I have
>> any
>> >> >>>>> >> problem,
>> >> >>>>> >> I will trouble you as you wished yesterday :)
>> >> >>>>> >>
>> >> >>>>> >> Thank You
>> >> >>>>> >>
>> >> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <
>> rok@kowalski.gd
>> >> >
>> >> >>>>> >> wrote:
>> >> >>>>> >>
>> >> >>>>> >>> Hi Dulanga,
>> >> >>>>> >>>
>> >> >>>>> >>> we already talked on irc and you already talked to Alex
>> regarding
>> >> >>>>> >>> features for our dashboard. That's great!
>> >> >>>>> >>>
>> >> >>>>> >>> Some topics will repeat in this mail, but I also would like
>> the
>> >> ML
>> >> >>>>> >>> to
>> >> >>>>> >>> follow our project and additionally add some more in-depth
>> >> >>>>> >>> informations.
>> >> >>>>> >>>
>> >> >>>>> >>> Recap & additons
>> >> >>>>> >>> =====
>> >> >>>>> >>>
>> >> >>>>> >>> As discussed we will work in an iterative approach and add
>> widget
>> >> >>>>> >>> after widget so if we run out of time, we will have something
>> to
>> >> >>>>> >>> deliver and don't have to throw everything away.
>> >> >>>>> >>>
>> >> >>>>> >>> Have you seen the "database" tab or the "config" tab in the
>> >> sidebar
>> >> >>>>> >>> on the
>> >> >>>>> >>> left?
>> >> >>>>> >>>
>> >> >>>>> >>> Those are modules that we can hook into the Fauxton build, by
>> >> >>>>> >>> configuration. I think the idea is to create a tab "dashboard"
>> >> >>>>> >>> which
>> >> >>>>> >>> is the default one after opening Fauxton in the browser. So
>> you
>> >> >>>>> >>> would
>> >> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
>> >> >>>>> >>>
>> >> >>>>> >>> Alex ideas so far:
>> >> >>>>> >>>
>> >> >>>>> >>> ```
>> >> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there
>> are
>> >> >>>>> >>> some
>> >> >>>>> >>> points about showing stats and log - forget these (: _stats
>> isn't
>> >> >>>>> >>> available for
>> >> >>>>> >>>                    cluster iface and _log is removed. but
>> >> recently
>> >> >>>>> >>> visited databases, active tasks and _users/_replicator quick
>> >> >>>>> >>> management is what could
>> >> >>>>> >>>                    be really handy.
>> >> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not
>> relevant
>> >> >>>>> >>> anymore after backporting some cloudant features
>> >> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way
>> how
>> >> (:
>> >> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets,
>> I
>> >> >>>>> >>> believe you could make some builtin and leave a template one
>> to
>> >> let
>> >> >>>>> >>> the end users create
>> >> >>>>> >>>                    their own if they're able/would like to. in
>> >> >>>>> >>> future
>> >> >>>>> >>> these are could be fauxton plugins or something.
>> >> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea
>> >> for a
>> >> >>>>> >>> hot
>> >> >>>>> >>> widget.
>> >> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help
>> with
>> >> >>>>> >>> that
>> >> >>>>> >>> (add custom widgets on build time) - the build is complicated,
>> >> but
>> >> >>>>> >>> once explained
>> >> >>>>> >>>                            it should be easy
>> >> >>>>> >>> ```
>> >> >>>>> >>>
>> >> >>>>> >>> So we have "custom widgets", "cluster quick-management", "
>> >> recently
>> >> >>>>> >>> visited databases",  "active tasks" and "_users/_replicator
>> quick
>> >> >>>>> >>> management"
>> >> >>>>> >>>
>> >> >>>>> >>> I think two good widgets for starting are active tasks and
>> >> recently
>> >> >>>>> >>> visited databases.
>> >> >>>>> >>>
>> >> >>>>> >>> For active tasks we have some nice docs:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>> >> >>>>> >>>
>> >> >>>>> >>> They have an own dedicated page in Fauxton (see
>> >> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick
>> condensed
>> >> >>>>> >>> list
>> >> >>>>> >>> is probably very interesting to users.
>> >> >>>>> >>>
>> >> >>>>> >>> For the recently visited databases we would have to store that
>> >> >>>>> >>> somewhere.
>> >> >>>>> >>>
>> >> >>>>> >>> If you want, you can take an existing page in Fauxton and just
>> >> >>>>> >>> modify
>> >> >>>>> >>> the markup for a design mockup how the widget view may look
>> like.
>> >> >>>>> >>> But
>> >> >>>>> >>> feel also free to use pen/paper or other tools if you like
>> that
>> >> the
>> >> >>>>> >>> most.
>> >> >>>>> >>>
>> >> >>>>> >>> For the mango feature I am currently working on, I took the
>> "edit
>> >> >>>>> >>> view" template on modified the markup using the Chrome
>> inspector
>> >> of
>> >> >>>>> >>> my
>> >> >>>>> >>> browser to collect some first feedback from the project
>> members
>> >> and
>> >> >>>>> >>> my
>> >> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>> >> >>>>> >>> functionality, but gives other folks a rough idea what my idea
>> >> for
>> >> >>>>> >>> the
>> >> >>>>> >>> feature is.
>> >> >>>>> >>>
>> >> >>>>> >>> the framework and react
>> >> >>>>> >>>
>> >> >>>>> >>> As I already mentioned we are using React.js.
>> >> >>>>> >>>
>> >> >>>>> >>> It would be nice if you can finish the tutorial at
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>> >> >>>>> >>> until next friday by following the steps and writing that
>> code.
>> >> >>>>> >>> After
>> >> >>>>> >>> that, read
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>> >> >>>>> >>> to get a first impression how the Flux pattern works that we
>> are
>> >> >>>>> >>> using.
>> >> >>>>> >>>
>> >> >>>>> >>> After that (if you still have time left) take a look on a
>> >> component
>> >> >>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>> >> >>>>> >>>
>> >> >>>>> >>> Please take a look how the data flows from the Components,
>> using
>> >> >>>>> >>> the
>> >> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>> >> >>>>> >>> everything in the code with console.log to see how state
>> changes
>> >> >>>>> >>> and
>> >> >>>>> >>> how the data flows.
>> >> >>>>> >>>
>> >> >>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>> If you still have time, just try to create another menu item,
>> >> >>>>> >>> called
>> >> >>>>> >>> "Dashboard". Take a look at:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>> >> >>>>> >>>
>> >> >>>>> >>> to get a first idea how to do that. Some background
>> information:
>> >> >>>>> >>>
>> >> >>>>> >>> base.js - the starting point of our module. basic
>> configuration
>> >> is
>> >> >>>>> >>> done
>> >> >>>>> >>> here
>> >> >>>>> >>> Question: what is `base.js` used for in the case of the config
>> >> >>>>> >>> module?
>> >> >>>>> >>>
>> >> >>>>> >>> routes.js - takes care that functions injecting the view into
>> the
>> >> >>>>> >>> layout are called depending on the url given
>> >> >>>>> >>> Question: What happens if I call `http:localhost:8000/_config`
>> >> and
>> >> >>>>> >>> what happens if you remove the function `apiUrl`?
>> >> >>>>> >>>
>> >> >>>>> >>> views.js - contains our views - this file contains still a lot
>> >> >>>>> >>> backbone views, which we are currently migrating to react.
>> maybe
>> >> it
>> >> >>>>> >>> makes more sense to take a look at one of our react
>> components:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>> >> >>>>> >>>
>> >> >>>>> >>> and how they are used currently (as we are migrating to react
>> >> >>>>> >>> currently):
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>> >> >>>>> >>>
>> >> >>>>> >>> The Objects are injected into the closures using AMD:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>> >> >>>>> >>>
>> >> >>>>> >>> assets folder:
>> >> >>>>> >>> contains our less which is compiled to css
>> >> >>>>> >>>
>> >> >>>>> >>> templates folder:
>> >> >>>>> >>> contains old backbone.js templates, you will not need them
>> >> >>>>> >>>
>> >> >>>>> >>> tests folder:
>> >> >>>>> >>> contains unit and integration tests, every PR must have unit
>> >> tests
>> >> >>>>> >>> and
>> >> >>>>> >>> integration tests. If you never wrote tests, we will explain
>> it
>> >> to
>> >> >>>>> >>> you
>> >> >>>>> >>> - it is easy once you wrote your first few ones. Basically you
>> >> are
>> >> >>>>> >>> testing each time that if you put something into a function,
>> the
>> >> >>>>> >>> expected result happens. Or that if you take an action, a
>> state
>> >> has
>> >> >>>>> >>> changed.
>> >> >>>>> >>>
>> >> >>>>> >>> You can run the unit tests using `grunt test`
>> >> >>>>> >>>
>> >> >>>>> >>> Single tests are run by:
>> >> >>>>> >>>
>> >> >>>>> >>> ```
>> >> >>>>> >>> grunt test
>> >> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
>> >> >>>>> >>> ```
>> >> >>>>> >>>
>> >> >>>>> >>> or in the browser by test group:
>> >> >>>>> >>>
>> >> >>>>> >>> ```
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>> >> >>>>> >>> ```
>> >> >>>>> >>>
>> >> >>>>> >>> (change path to your fauxton directory)
>> >> >>>>> >>>
>> >> >>>>> >>> The corresponding code is:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>> >> >>>>> >>>
>> >> >>>>> >>> and these tests are a good example how to write a simple test
>> for
>> >> >>>>> >>> the
>> >> >>>>> >>> hello world/hello from dulanga-component:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>> First steps:
>> >> >>>>> >>>
>> >> >>>>> >>> Create a module `dashboard` that gets displayed in the
>> sidebar.
>> >> The
>> >> >>>>> >>> route http://localhost:8000/dash will render a small React
>> >> >>>>> >>> component
>> >> >>>>> >>> that display "Hello World".
>> >> >>>>> >>>
>> >> >>>>> >>> If you click on the "Hello World" it ill change the content
>> to:
>> >> >>>>> >>> "Hello
>> >> >>>>> >>> from Dulanga"
>> >> >>>>> >>>
>> >> >>>>> >>> While we will throw the small component away afterwards we
>> will
>> >> >>>>> >>> build
>> >> >>>>> >>> upon the other code you created. If you have time left, add a
>> >> test
>> >> >>>>> >>> that the component changes the content.
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>> Meeting Wednesday:
>> >> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >> >>>>> >>>
>> >> >>>>> >>> I will be around at least one hour before so we can chat.
>> Contact
>> >> >>>>> >>> me
>> >> >>>>> >>> if you would like to chat earlier/later. I am also around the
>> >> other
>> >> >>>>> >>> days on IRC / the mailinglist and feel free to contact me in
>> >> >>>>> >>> #couchdb-dev at any time. If I am not around I will answer you
>> >> once
>> >> >>>>> >>> I
>> >> >>>>> >>> got online again, as I read the backlog.
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
>> >> >>>>> >>>
>> >> >>>>> >>>  - check out the active tasks api (linked on top of this mail)
>> >> >>>>> >>>  - a mockup showing some widgets and how they could look like
>> >> >>>>> >>>  - code React tutorial & read about Flux
>> >> >>>>> >>>  - take a look how we are using React
>> >> >>>>> >>>  - create another menu item, called "Dashboard", try to answer
>> >> the
>> >> >>>>> >>> questions to route.js et al
>> >> >>>>> >>>  - get familiar how we test our code
>> >> >>>>> >>>  - write an hello world / hello from dulanga component that is
>> >> >>>>> >>> rendered into a screen when opening
>> http://localhost:8000/dash
>> >> or
>> >> >>>>> >>> by
>> >> >>>>> >>> clicking on "dashboard" in the sidebar
>> >> >>>>> >>>
>> >> >>>>> >>> That was a lot of content and please don't feel discouraged if
>> >> you
>> >> >>>>> >>> don't get that far until Wednesday. We will have to find a
>> speed
>> >> >>>>> >>> which
>> >> >>>>> >>> is perfect for you and this time I tried to give enough
>> >> >>>>> >>> informations
>> >> >>>>> >>> that you are not blocked until Wednesday by waiting for next
>> >> steps.
>> >> >>>>> >>> If
>> >> >>>>> >>> you are at the last step before Wednesday, drop me a line and
>> I
>> >> >>>>> >>> will
>> >> >>>>> >>> prepare the next steps :)
>> >> >>>>> >>>
>> >> >>>>> >>> I know that you all have important exams, these are definitely
>> >> more
>> >> >>>>> >>> important! Don't feel pressured by the amount of work / the
>> >> amount
>> >> >>>>> >>> of
>> >> >>>>> >>> informations, getting good results in the exams should be your
>> >> >>>>> >>> first
>> >> >>>>> >>> priority.
>> >> >>>>> >>>
>> >> >>>>> >>> Best,
>> >> >>>>> >>> Robert
>> >> >>>>> >>>
>> >> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
>> >> >>>>> >>> <wa...@gmail.com>
>> >> >>>>> >>> wrote:
>> >> >>>>> >>> > Hi Robert,
>> >> >>>>> >>> >
>> >> >>>>> >>> > I went through the guidelines you provided and successfully
>> >> >>>>> >>> > installed and
>> >> >>>>> >>> > configured as you said. Everything works find and I played
>> >> around
>> >> >>>>> >>> > it by
>> >> >>>>> >>> > creating a database and documents. I think I am ready for
>> the
>> >> >>>>> >>> > next step
>> >> >>>>> >>> and
>> >> >>>>> >>> > we can start it if you are ok :)
>> >> >>>>> >>> >
>> >> >>>>> >>> > Thank You
>> >> >>>>> >>> >
>> >> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
>> >> >>>>> >>> > <ro...@kowalski.gd>
>> >> >>>>> >>> wrote:
>> >> >>>>> >>> >
>> >> >>>>> >>> >> You're welcome.
>> >> >>>>> >>> >>
>> >> >>>>> >>> >> I also hang out in the couchdb-dev channel for around
>> 1-3hrs
>> >> if
>> >> >>>>> >>> >> you get
>> >> >>>>> >>> >> stuck!
>> >> >>>>> >>> >>
>> >> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
>> >> >>>>> >>> >> <wa...@gmail.com>
>> >> >>>>> >>> >> wrote:
>> >> >>>>> >>> >> > Hi Robert,
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> > Thank you very much for the quick reply. I will go
>> through
>> >> the
>> >> >>>>> >>> guidelines
>> >> >>>>> >>> >> > and contact you if I have any issue with them.
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> > Thank you
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
>> >> >>>>> >>> >> > <ro...@kowalski.gd>
>> >> >>>>> >>> >> wrote:
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> >> Hi Dulanga,
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> glad you found your way to the CouchDB mailing list.
>> >> Welcome
>> >> >>>>> >>> >> >> :)
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP
>> API -
>> >> >>>>> >>> >> >> that makes
>> >> >>>>> >>> >> >> it a great fit for web applications that don't need a
>> >> server
>> >> >>>>> >>> >> >> side
>> >> >>>>> >>> >> >> layer with a database driver in between. Our Project
>> >> Fauxton
>> >> >>>>> >>> >> >> (like a
>> >> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev
>> including
>> >> >>>>> >>> >> >> myself.
>> >> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
>> >> >>>>> >>> >> >> online (e.g.
>> >> >>>>> >>> I
>> >> >>>>> >>> >> >> was travelling this week) feel free to ask on the dev
>> ML.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> We are all happy to help each other in the project :)
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> If you are using windows: I am not a Windows expert -
>> you
>> >> >>>>> >>> >> >> will
>> >> >>>>> >>> >> >> probably have to use a bash emulator like "git bash" to
>> >> boot
>> >> >>>>> >>> >> >> the dev
>> >> >>>>> >>> >> >> environment.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Getting started:
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> For this project you will need to install at least
>> CouchDB
>> >> >>>>> >>> >> >> 1.x, an
>> >> >>>>> >>> >> >> Ubuntu package (with installation instructions) is at
>> >> >>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
>> >> >>>>> >>> >> >> (install from
>> >> >>>>> >>> >> >> https://nodejs.org)
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> booting CouchDB:
>> >> >>>>> >>> >> >> $ sudo couchdb
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> in another terminal, clone the admin interface:
>> >> >>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> go to Fauxton:
>> >> >>>>> >>> >> >> $ cd couchdb-fauxton
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> install dependencies:
>> >> >>>>> >>> >> >> $ npm install
>> >> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> boot the app:
>> >> >>>>> >>> >> >> $ grunt dev
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Then open your browser and go to http://localhost:8000
>> -
>> >> you
>> >> >>>>> >>> >> >> should
>> >> >>>>> >>> >> >> see a red/gray/black interface
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> That was a lot of input and especially if you are using
>> >> Linux
>> >> >>>>> >>> >> >> the
>> >> >>>>> >>> >> >> first time and followed the instructions you have
>> archived
>> >> a
>> >> >>>>> >>> >> >> lot!
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> As first step, try to create a database and a document
>> now
>> >> >>>>> >>> >> >> using the
>> >> >>>>> >>> >> >> web interface (PS we are happy about any usability
>> >> feedback).
>> >> >>>>> >>> >> >> :)
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> I think you have your dev environment for CouchDB ready
>> >> now.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> What's next:
>> >> >>>>> >>> >> >> If everything works we will take a look at Fauxtons code
>> >> >>>>> >>> >> >> structure
>> >> >>>>> >>> and
>> >> >>>>> >>> >> >> how it works. We will also talk about the features of
>> the
>> >> >>>>> >>> >> >> dashboard.
>> >> >>>>> >>> >> >> Let's find a date for a chat after you took a first look
>> >> how
>> >> >>>>> >>> >> >> Fauxton
>> >> >>>>> >>> >> >> looks like.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> We are having our weekly meeting this Wednesday,
>> 20:00GMT
>> >> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in
>> IRC
>> >> on
>> >> >>>>> >>> >> >> freenode
>> >> >>>>> >>> >> >> (see
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >>
>> >> >>>>> >>>
>> >> >>>>> >>>
>> >>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >> >>>>> >>> >> >> )
>> >> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if
>> you
>> >> >>>>> >>> >> >> want to
>> >> >>>>> >>> >> >> chat with me before.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> Looking forward to work with you,
>> >> >>>>> >>> >> >> Robert
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>> >> >>>>> >>> wadsashika@gmail.com>
>> >> >>>>> >>> >> >> wrote:
>> >> >>>>> >>> >> >> > Hi all,
>> >> >>>>> >>> >> >> >
>> >> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year
>> undergraduate
>> >> >>>>> >>> >> >> > student at
>> >> >>>>> >>> >> >> > Computer Science and Engineering department at
>> University
>> >> >>>>> >>> >> >> > of
>> >> >>>>> >>> Moratuwa,
>> >> >>>>> >>> >> >> Sri
>> >> >>>>> >>> >> >> > Lanka. I am really interested in java, java script,
>> web
>> >> >>>>> >>> applications,
>> >> >>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
>> >> >>>>> >>> >> >> > months of
>> >> >>>>> >>> >> training
>> >> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked
>> >> on a
>> >> >>>>> >>> >> >> > web
>> >> >>>>> >>> >> >> application
>> >> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My final
>> year
>> >> >>>>> >>> >> >> > project
>> >> >>>>> >>> also a
>> >> >>>>> >>> >> >> web
>> >> >>>>> >>> >> >> > related application and I used same technologies I
>> >> >>>>> >>> >> >> > mentioned above
>> >> >>>>> >>> for
>> >> >>>>> >>> >> >> > that. I am really interested in this project because I
>> >> have
>> >> >>>>> >>> >> >> > a good
>> >> >>>>> >>> >> >> > experience with web applications and I love work with
>> >> >>>>> >>> >> >> > javascript.
>> >> >>>>> >>> I am
>> >> >>>>> >>> >> >> > looking forward to contribute to this project in this
>> >> >>>>> >>> >> >> > summer. I
>> >> >>>>> >>> like
>> >> >>>>> >>> >> to
>> >> >>>>> >>> >> >> > know more detail about this project and if you can,
>> >> please
>> >> >>>>> >>> >> >> > guide
>> >> >>>>> >>> me to
>> >> >>>>> >>> >> >> > start working on this project.
>> >> >>>>> >>> >> >> >
>> >> >>>>> >>> >> >> > Thank you.
>> >> >>>>> >>> >> >> >
>> >> >>>>> >>> >> >> > W. A. Dulanga Sashika,
>> >> >>>>> >>> >> >> > Undergraduate Student,
>> >> >>>>> >>> >> >> > Department of Computer Science and Engineering,
>> >> >>>>> >>> >> >> > University of Moratuwa.
>> >> >>>>> >>> >> >>
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> >
>> >> >>>>> >>> >> > --
>> >> >>>>> >>> >> > W. A. Dulanga Sashika,
>> >> >>>>> >>> >> > Undergraduate Student,
>> >> >>>>> >>> >> > Department of Computer Science and Engineering,
>> >> >>>>> >>> >> > University of Moratuwa.
>> >> >>>>> >>> >>
>> >> >>>>> >>> >
>> >> >>>>> >>> >
>> >> >>>>> >>> >
>> >> >>>>> >>> > --
>> >> >>>>> >>> > W. A. Dulanga Sashika,
>> >> >>>>> >>> > Undergraduate Student,
>> >> >>>>> >>> > Department of Computer Science and Engineering,
>> >> >>>>> >>> > University of Moratuwa.
>> >> >>>>> >>>
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >>
>> >> >>>>> >> --
>> >> >>>>> >> W. A. Dulanga Sashika,
>> >> >>>>> >> Undergraduate Student,
>> >> >>>>> >> Department of Computer Science and Engineering,
>> >> >>>>> >> University of Moratuwa.
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> W. A. Dulanga Sashika,
>> >> >>>> Undergraduate Student,
>> >> >>>> Department of Computer Science and Engineering,
>> >> >>>> University of Moratuwa.
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> W. A. Dulanga Sashika,
>> >> >>> Undergraduate Student,
>> >> >>> Department of Computer Science and Engineering,
>> >> >>> University of Moratuwa.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> W. A. Dulanga Sashika,
>> >> >> Undergraduate Student,
>> >> >> Department of Computer Science and Engineering,
>> >> >> University of Moratuwa.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > W. A. Dulanga Sashika,
>> >> > Undergraduate Student,
>> >> > Department of Computer Science and Engineering,
>> >> > University of Moratuwa.
>> >>
>> >
>> >
>> >
>> > --
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Here is the mock up I designed for the dashboard.
https://www.dropbox.com/s/n1q4whsd460neil/Dashboard_mockup.png?dl=0

Please give some comments and we can change this later by discussing the
important facts that we should show in the dashboard. For now I designed a
mock up only for dashboard and I can make designs for each widgets later.

Thank You


On Fri, Mar 20, 2015 at 8:12 PM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Cool thank you!
>
> Yes I also did not know until someone told me 2 months ago :)
>
> On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi Robert,
> >
> > Thank you very much for the help. I can carry on from there now.
> Actually I
> > didn't know that this mailing list does not supported for attachments.
> Here
> > is the screenshots I uploaded.
> >
> > img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
> > img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
> > img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
> > img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
> > img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
> > img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
> >
> > And I will share the proposal ASAP with you.
> >
> > Thank you
> >
> > On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >
> >> Hi Dulanga,
> >>
> >> glad you figured it out while I was on a train! :)
> >>
> >> Can you upload the pictures to something like box.com / dropbox or an
> >> image hoster as the list does not support attachments?
> >>
> >> We are storing our react components in files like
> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
> >>
> >> To render them we still have to wrap them in Backbone Views - as our
> >> framework is built for Backbone views. The backbone view files are
> >> usually called `views.js`. This will go away soon but currently it is
> >> the way to go:
> >>
> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> >>
> >> which calls this at the bottom of
> `app/addons/cors/components.react.jsx`:
> >>
> >>
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
> >>
> >>
> >> In
> >>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> >> `this.el` references the DOM-Node of the Backbone view in which then
> >> the React Component is rendered into.
> >>
> >>
> >> Regarding the proposal:
> >>
> >> I am happy to help you with your proposal it would be nice to have an
> >> option that makes it easy to leave comments (e.g google docs)
> >>
> >> Best,
> >> Robert
> >>
> >> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <wa...@gmail.com>
> >> wrote:
> >> > Hi,
> >> > Here I attached the screen shots of Dashboard menu item. Now its
> working.
> >> > Now I want to know that, if I need to implement react component, where
> >> > should I put it? And how can I access that to render the view? just
> give
> >> me
> >> > some hints and I can carry on from there.
> >> >
> >> > Regards
> >> >
> >> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <
> wadsashika@gmail.com>
> >> > wrote:
> >> >>
> >> >> Hey Robert, problem solved.. :)
> >> >>
> >> >>
> >> >> Regards.
> >> >>
> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <
> wadsashika@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi Robert,
> >> >>>
> >> >>> Now I am trying to create a new menu item for dashboard and
> implement a
> >> >>> react component as you said. But now I am stuck in some place and
> >> couldn't
> >> >>> figure out the problem yet. Here is the problem I had in process. I
> >> added
> >> >>> dashboard menu item and added route and view for that. And i change
> >> the code
> >> >>> to render dashboard when we enter http://localhost:8000 . As in
> img1
> >> and
> >> >>> img2, it doesn't show the view I created. But when I click on
> another
> >> menu
> >> >>> item and come back to the dashboard, it shows the breadcrumb of
> >> previous
> >> >>> pages as img 3 and 4. As in
> >> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> >> >>> , I called the new Dashboard.view() which is a component in my
> >> view.js. But
> >> >>> in the console, it shows Uncaught Type error. Did I miss any
> >> configuration
> >> >>> thing or did I do it wrong?
> >> >>>
> >> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
> >> wadsashika@gmail.com>
> >> >>> wrote:
> >> >>>>
> >> >>>> Hi Robert,
> >> >>>>
> >> >>>> Thank you very much for the reference. I started to write the
> proposal
> >> >>>> today. I hope you will help to write this proposal by reviewing
> it.
> >> I will
> >> >>>> share it with you after complete the draft of the proposal.
> >> >>>>
> >> >>>> Thank you
> >> >>>>
> >> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
> >> >>>> wrote:
> >> >>>>>
> >> >>>>> Some of you asked for a template for their proposals, here is what
> >> I've
> >> >>>>> found:
> >> >>>>>
> >> >>>>> http://community.staging.apache.org/gsoc#application-template
> >> >>>>>
> >> >>>>> Best,
> >> >>>>> Robert
> >> >>>>>
> >> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <
> rok@kowalski.gd>
> >> >>>>> wrote:
> >> >>>>> > Wow you are making very good progress!
> >> >>>>> >
> >> >>>>> > We have our weekly status meetup tomorrow (see [1] for the time
> in
> >> >>>>> > your timezone), feel free to join, meet other project members
> and
> >> >>>>> > learn what the project is currently doing next to the Summer of
> >> Code.
> >> >>>>> >
> >> >>>>> > I will also be around 1hr earlier to answer all your questions
> and
> >> >>>>> > discuss our next steps.
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > [1]
> >> >>>>> >
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >>>>> >
> >> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
> >> >>>>> > <wa...@gmail.com> wrote:
> >> >>>>> >> Hi Robert,
> >> >>>>> >>
> >> >>>>> >> Here is the current status of the checklist :)
> >> >>>>> >>
> >> >>>>> >>  - check out the active tasks api (linked on top of this mail)
> -
> >> >>>>> >> (finished)
> >> >>>>> >>  - a mockup showing some widgets and how they could look like -
> >> >>>>> >> (started
> >> >>>>> >> but not finished yet)
> >> >>>>> >>  - code React tutorial & read about Flux - (finished)
> >> >>>>> >>  - take a look how we are using React - (finished)
> >> >>>>> >>  - create another menu item, called "Dashboard", try to answer
> the
> >> >>>>> >> questions to route.js et al - (started but not finished yet)
> >> >>>>> >>  - get familiar how we test our code - (finished)
> >> >>>>> >>  - write an hello world / hello from dulanga component that is
> >> >>>>> >> rendered into a screen when opening http://localhost:8000/dash
> >> or by
> >> >>>>> >> clicking on "dashboard" in the sidebar - (started but not
> finished
> >> >>>>> >> yet)
> >> >>>>> >>
> >> >>>>> >> I will do my best to complete all these by tomorrow. If I have
> any
> >> >>>>> >> problem,
> >> >>>>> >> I will trouble you as you wished yesterday :)
> >> >>>>> >>
> >> >>>>> >> Thank You
> >> >>>>> >>
> >> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <
> rok@kowalski.gd
> >> >
> >> >>>>> >> wrote:
> >> >>>>> >>
> >> >>>>> >>> Hi Dulanga,
> >> >>>>> >>>
> >> >>>>> >>> we already talked on irc and you already talked to Alex
> regarding
> >> >>>>> >>> features for our dashboard. That's great!
> >> >>>>> >>>
> >> >>>>> >>> Some topics will repeat in this mail, but I also would like
> the
> >> ML
> >> >>>>> >>> to
> >> >>>>> >>> follow our project and additionally add some more in-depth
> >> >>>>> >>> informations.
> >> >>>>> >>>
> >> >>>>> >>> Recap & additons
> >> >>>>> >>> =====
> >> >>>>> >>>
> >> >>>>> >>> As discussed we will work in an iterative approach and add
> widget
> >> >>>>> >>> after widget so if we run out of time, we will have something
> to
> >> >>>>> >>> deliver and don't have to throw everything away.
> >> >>>>> >>>
> >> >>>>> >>> Have you seen the "database" tab or the "config" tab in the
> >> sidebar
> >> >>>>> >>> on the
> >> >>>>> >>> left?
> >> >>>>> >>>
> >> >>>>> >>> Those are modules that we can hook into the Fauxton build, by
> >> >>>>> >>> configuration. I think the idea is to create a tab "dashboard"
> >> >>>>> >>> which
> >> >>>>> >>> is the default one after opening Fauxton in the browser. So
> you
> >> >>>>> >>> would
> >> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
> >> >>>>> >>>
> >> >>>>> >>> Alex ideas so far:
> >> >>>>> >>>
> >> >>>>> >>> ```
> >> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there
> are
> >> >>>>> >>> some
> >> >>>>> >>> points about showing stats and log - forget these (: _stats
> isn't
> >> >>>>> >>> available for
> >> >>>>> >>>                    cluster iface and _log is removed. but
> >> recently
> >> >>>>> >>> visited databases, active tasks and _users/_replicator quick
> >> >>>>> >>> management is what could
> >> >>>>> >>>                    be really handy.
> >> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not
> relevant
> >> >>>>> >>> anymore after backporting some cloudant features
> >> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way
> how
> >> (:
> >> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets,
> I
> >> >>>>> >>> believe you could make some builtin and leave a template one
> to
> >> let
> >> >>>>> >>> the end users create
> >> >>>>> >>>                    their own if they're able/would like to. in
> >> >>>>> >>> future
> >> >>>>> >>> these are could be fauxton plugins or something.
> >> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea
> >> for a
> >> >>>>> >>> hot
> >> >>>>> >>> widget.
> >> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help
> with
> >> >>>>> >>> that
> >> >>>>> >>> (add custom widgets on build time) - the build is complicated,
> >> but
> >> >>>>> >>> once explained
> >> >>>>> >>>                            it should be easy
> >> >>>>> >>> ```
> >> >>>>> >>>
> >> >>>>> >>> So we have "custom widgets", "cluster quick-management", "
> >> recently
> >> >>>>> >>> visited databases",  "active tasks" and "_users/_replicator
> quick
> >> >>>>> >>> management"
> >> >>>>> >>>
> >> >>>>> >>> I think two good widgets for starting are active tasks and
> >> recently
> >> >>>>> >>> visited databases.
> >> >>>>> >>>
> >> >>>>> >>> For active tasks we have some nice docs:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> >> >>>>> >>>
> >> >>>>> >>> They have an own dedicated page in Fauxton (see
> >> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick
> condensed
> >> >>>>> >>> list
> >> >>>>> >>> is probably very interesting to users.
> >> >>>>> >>>
> >> >>>>> >>> For the recently visited databases we would have to store that
> >> >>>>> >>> somewhere.
> >> >>>>> >>>
> >> >>>>> >>> If you want, you can take an existing page in Fauxton and just
> >> >>>>> >>> modify
> >> >>>>> >>> the markup for a design mockup how the widget view may look
> like.
> >> >>>>> >>> But
> >> >>>>> >>> feel also free to use pen/paper or other tools if you like
> that
> >> the
> >> >>>>> >>> most.
> >> >>>>> >>>
> >> >>>>> >>> For the mango feature I am currently working on, I took the
> "edit
> >> >>>>> >>> view" template on modified the markup using the Chrome
> inspector
> >> of
> >> >>>>> >>> my
> >> >>>>> >>> browser to collect some first feedback from the project
> members
> >> and
> >> >>>>> >>> my
> >> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
> >> >>>>> >>> functionality, but gives other folks a rough idea what my idea
> >> for
> >> >>>>> >>> the
> >> >>>>> >>> feature is.
> >> >>>>> >>>
> >> >>>>> >>> the framework and react
> >> >>>>> >>>
> >> >>>>> >>> As I already mentioned we are using React.js.
> >> >>>>> >>>
> >> >>>>> >>> It would be nice if you can finish the tutorial at
> >> >>>>> >>>
> >> >>>>> >>>
> >> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> >> >>>>> >>> until next friday by following the steps and writing that
> code.
> >> >>>>> >>> After
> >> >>>>> >>> that, read
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> >> >>>>> >>> to get a first impression how the Flux pattern works that we
> are
> >> >>>>> >>> using.
> >> >>>>> >>>
> >> >>>>> >>> After that (if you still have time left) take a look on a
> >> component
> >> >>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> >> >>>>> >>>
> >> >>>>> >>> Please take a look how the data flows from the Components,
> using
> >> >>>>> >>> the
> >> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
> >> >>>>> >>> everything in the code with console.log to see how state
> changes
> >> >>>>> >>> and
> >> >>>>> >>> how the data flows.
> >> >>>>> >>>
> >> >>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>> If you still have time, just try to create another menu item,
> >> >>>>> >>> called
> >> >>>>> >>> "Dashboard". Take a look at:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> >> >>>>> >>>
> >> >>>>> >>>
> >> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> >> >>>>> >>>
> >> >>>>> >>> to get a first idea how to do that. Some background
> information:
> >> >>>>> >>>
> >> >>>>> >>> base.js - the starting point of our module. basic
> configuration
> >> is
> >> >>>>> >>> done
> >> >>>>> >>> here
> >> >>>>> >>> Question: what is `base.js` used for in the case of the config
> >> >>>>> >>> module?
> >> >>>>> >>>
> >> >>>>> >>> routes.js - takes care that functions injecting the view into
> the
> >> >>>>> >>> layout are called depending on the url given
> >> >>>>> >>> Question: What happens if I call `http:localhost:8000/_config`
> >> and
> >> >>>>> >>> what happens if you remove the function `apiUrl`?
> >> >>>>> >>>
> >> >>>>> >>> views.js - contains our views - this file contains still a lot
> >> >>>>> >>> backbone views, which we are currently migrating to react.
> maybe
> >> it
> >> >>>>> >>> makes more sense to take a look at one of our react
> components:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> >> >>>>> >>>
> >> >>>>> >>> and how they are used currently (as we are migrating to react
> >> >>>>> >>> currently):
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> >> >>>>> >>>
> >> >>>>> >>> The Objects are injected into the closures using AMD:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> >> >>>>> >>>
> >> >>>>> >>> assets folder:
> >> >>>>> >>> contains our less which is compiled to css
> >> >>>>> >>>
> >> >>>>> >>> templates folder:
> >> >>>>> >>> contains old backbone.js templates, you will not need them
> >> >>>>> >>>
> >> >>>>> >>> tests folder:
> >> >>>>> >>> contains unit and integration tests, every PR must have unit
> >> tests
> >> >>>>> >>> and
> >> >>>>> >>> integration tests. If you never wrote tests, we will explain
> it
> >> to
> >> >>>>> >>> you
> >> >>>>> >>> - it is easy once you wrote your first few ones. Basically you
> >> are
> >> >>>>> >>> testing each time that if you put something into a function,
> the
> >> >>>>> >>> expected result happens. Or that if you take an action, a
> state
> >> has
> >> >>>>> >>> changed.
> >> >>>>> >>>
> >> >>>>> >>> You can run the unit tests using `grunt test`
> >> >>>>> >>>
> >> >>>>> >>> Single tests are run by:
> >> >>>>> >>>
> >> >>>>> >>> ```
> >> >>>>> >>> grunt test
> >> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
> >> >>>>> >>> ```
> >> >>>>> >>>
> >> >>>>> >>> or in the browser by test group:
> >> >>>>> >>>
> >> >>>>> >>> ```
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> >> >>>>> >>> ```
> >> >>>>> >>>
> >> >>>>> >>> (change path to your fauxton directory)
> >> >>>>> >>>
> >> >>>>> >>> The corresponding code is:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> >> >>>>> >>>
> >> >>>>> >>> and these tests are a good example how to write a simple test
> for
> >> >>>>> >>> the
> >> >>>>> >>> hello world/hello from dulanga-component:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>> First steps:
> >> >>>>> >>>
> >> >>>>> >>> Create a module `dashboard` that gets displayed in the
> sidebar.
> >> The
> >> >>>>> >>> route http://localhost:8000/dash will render a small React
> >> >>>>> >>> component
> >> >>>>> >>> that display "Hello World".
> >> >>>>> >>>
> >> >>>>> >>> If you click on the "Hello World" it ill change the content
> to:
> >> >>>>> >>> "Hello
> >> >>>>> >>> from Dulanga"
> >> >>>>> >>>
> >> >>>>> >>> While we will throw the small component away afterwards we
> will
> >> >>>>> >>> build
> >> >>>>> >>> upon the other code you created. If you have time left, add a
> >> test
> >> >>>>> >>> that the component changes the content.
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>> Meeting Wednesday:
> >> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >>>>> >>>
> >> >>>>> >>> I will be around at least one hour before so we can chat.
> Contact
> >> >>>>> >>> me
> >> >>>>> >>> if you would like to chat earlier/later. I am also around the
> >> other
> >> >>>>> >>> days on IRC / the mailinglist and feel free to contact me in
> >> >>>>> >>> #couchdb-dev at any time. If I am not around I will answer you
> >> once
> >> >>>>> >>> I
> >> >>>>> >>> got online again, as I read the backlog.
> >> >>>>> >>>
> >> >>>>> >>>
> >> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
> >> >>>>> >>>
> >> >>>>> >>>  - check out the active tasks api (linked on top of this mail)
> >> >>>>> >>>  - a mockup showing some widgets and how they could look like
> >> >>>>> >>>  - code React tutorial & read about Flux
> >> >>>>> >>>  - take a look how we are using React
> >> >>>>> >>>  - create another menu item, called "Dashboard", try to answer
> >> the
> >> >>>>> >>> questions to route.js et al
> >> >>>>> >>>  - get familiar how we test our code
> >> >>>>> >>>  - write an hello world / hello from dulanga component that is
> >> >>>>> >>> rendered into a screen when opening
> http://localhost:8000/dash
> >> or
> >> >>>>> >>> by
> >> >>>>> >>> clicking on "dashboard" in the sidebar
> >> >>>>> >>>
> >> >>>>> >>> That was a lot of content and please don't feel discouraged if
> >> you
> >> >>>>> >>> don't get that far until Wednesday. We will have to find a
> speed
> >> >>>>> >>> which
> >> >>>>> >>> is perfect for you and this time I tried to give enough
> >> >>>>> >>> informations
> >> >>>>> >>> that you are not blocked until Wednesday by waiting for next
> >> steps.
> >> >>>>> >>> If
> >> >>>>> >>> you are at the last step before Wednesday, drop me a line and
> I
> >> >>>>> >>> will
> >> >>>>> >>> prepare the next steps :)
> >> >>>>> >>>
> >> >>>>> >>> I know that you all have important exams, these are definitely
> >> more
> >> >>>>> >>> important! Don't feel pressured by the amount of work / the
> >> amount
> >> >>>>> >>> of
> >> >>>>> >>> informations, getting good results in the exams should be your
> >> >>>>> >>> first
> >> >>>>> >>> priority.
> >> >>>>> >>>
> >> >>>>> >>> Best,
> >> >>>>> >>> Robert
> >> >>>>> >>>
> >> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
> >> >>>>> >>> <wa...@gmail.com>
> >> >>>>> >>> wrote:
> >> >>>>> >>> > Hi Robert,
> >> >>>>> >>> >
> >> >>>>> >>> > I went through the guidelines you provided and successfully
> >> >>>>> >>> > installed and
> >> >>>>> >>> > configured as you said. Everything works find and I played
> >> around
> >> >>>>> >>> > it by
> >> >>>>> >>> > creating a database and documents. I think I am ready for
> the
> >> >>>>> >>> > next step
> >> >>>>> >>> and
> >> >>>>> >>> > we can start it if you are ok :)
> >> >>>>> >>> >
> >> >>>>> >>> > Thank You
> >> >>>>> >>> >
> >> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
> >> >>>>> >>> > <ro...@kowalski.gd>
> >> >>>>> >>> wrote:
> >> >>>>> >>> >
> >> >>>>> >>> >> You're welcome.
> >> >>>>> >>> >>
> >> >>>>> >>> >> I also hang out in the couchdb-dev channel for around
> 1-3hrs
> >> if
> >> >>>>> >>> >> you get
> >> >>>>> >>> >> stuck!
> >> >>>>> >>> >>
> >> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
> >> >>>>> >>> >> <wa...@gmail.com>
> >> >>>>> >>> >> wrote:
> >> >>>>> >>> >> > Hi Robert,
> >> >>>>> >>> >> >
> >> >>>>> >>> >> > Thank you very much for the quick reply. I will go
> through
> >> the
> >> >>>>> >>> guidelines
> >> >>>>> >>> >> > and contact you if I have any issue with them.
> >> >>>>> >>> >> >
> >> >>>>> >>> >> > Thank you
> >> >>>>> >>> >> >
> >> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
> >> >>>>> >>> >> > <ro...@kowalski.gd>
> >> >>>>> >>> >> wrote:
> >> >>>>> >>> >> >
> >> >>>>> >>> >> >> Hi Dulanga,
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> glad you found your way to the CouchDB mailing list.
> >> Welcome
> >> >>>>> >>> >> >> :)
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP
> API -
> >> >>>>> >>> >> >> that makes
> >> >>>>> >>> >> >> it a great fit for web applications that don't need a
> >> server
> >> >>>>> >>> >> >> side
> >> >>>>> >>> >> >> layer with a database driver in between. Our Project
> >> Fauxton
> >> >>>>> >>> >> >> (like a
> >> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev
> including
> >> >>>>> >>> >> >> myself.
> >> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
> >> >>>>> >>> >> >> online (e.g.
> >> >>>>> >>> I
> >> >>>>> >>> >> >> was travelling this week) feel free to ask on the dev
> ML.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> We are all happy to help each other in the project :)
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> If you are using windows: I am not a Windows expert -
> you
> >> >>>>> >>> >> >> will
> >> >>>>> >>> >> >> probably have to use a bash emulator like "git bash" to
> >> boot
> >> >>>>> >>> >> >> the dev
> >> >>>>> >>> >> >> environment.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Getting started:
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> For this project you will need to install at least
> CouchDB
> >> >>>>> >>> >> >> 1.x, an
> >> >>>>> >>> >> >> Ubuntu package (with installation instructions) is at
> >> >>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
> >> >>>>> >>> >> >> (install from
> >> >>>>> >>> >> >> https://nodejs.org)
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> booting CouchDB:
> >> >>>>> >>> >> >> $ sudo couchdb
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> in another terminal, clone the admin interface:
> >> >>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> go to Fauxton:
> >> >>>>> >>> >> >> $ cd couchdb-fauxton
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> install dependencies:
> >> >>>>> >>> >> >> $ npm install
> >> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> boot the app:
> >> >>>>> >>> >> >> $ grunt dev
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Then open your browser and go to http://localhost:8000
> -
> >> you
> >> >>>>> >>> >> >> should
> >> >>>>> >>> >> >> see a red/gray/black interface
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> That was a lot of input and especially if you are using
> >> Linux
> >> >>>>> >>> >> >> the
> >> >>>>> >>> >> >> first time and followed the instructions you have
> archived
> >> a
> >> >>>>> >>> >> >> lot!
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> As first step, try to create a database and a document
> now
> >> >>>>> >>> >> >> using the
> >> >>>>> >>> >> >> web interface (PS we are happy about any usability
> >> feedback).
> >> >>>>> >>> >> >> :)
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> I think you have your dev environment for CouchDB ready
> >> now.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> What's next:
> >> >>>>> >>> >> >> If everything works we will take a look at Fauxtons code
> >> >>>>> >>> >> >> structure
> >> >>>>> >>> and
> >> >>>>> >>> >> >> how it works. We will also talk about the features of
> the
> >> >>>>> >>> >> >> dashboard.
> >> >>>>> >>> >> >> Let's find a date for a chat after you took a first look
> >> how
> >> >>>>> >>> >> >> Fauxton
> >> >>>>> >>> >> >> looks like.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> We are having our weekly meeting this Wednesday,
> 20:00GMT
> >> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in
> IRC
> >> on
> >> >>>>> >>> >> >> freenode
> >> >>>>> >>> >> >> (see
> >> >>>>> >>> >> >>
> >> >>>>> >>> >>
> >> >>>>> >>>
> >> >>>>> >>>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >>>>> >>> >> >> )
> >> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if
> you
> >> >>>>> >>> >> >> want to
> >> >>>>> >>> >> >> chat with me before.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> Looking forward to work with you,
> >> >>>>> >>> >> >> Robert
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> >> >>>>> >>> wadsashika@gmail.com>
> >> >>>>> >>> >> >> wrote:
> >> >>>>> >>> >> >> > Hi all,
> >> >>>>> >>> >> >> >
> >> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year
> undergraduate
> >> >>>>> >>> >> >> > student at
> >> >>>>> >>> >> >> > Computer Science and Engineering department at
> University
> >> >>>>> >>> >> >> > of
> >> >>>>> >>> Moratuwa,
> >> >>>>> >>> >> >> Sri
> >> >>>>> >>> >> >> > Lanka. I am really interested in java, java script,
> web
> >> >>>>> >>> applications,
> >> >>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
> >> >>>>> >>> >> >> > months of
> >> >>>>> >>> >> training
> >> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked
> >> on a
> >> >>>>> >>> >> >> > web
> >> >>>>> >>> >> >> application
> >> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My final
> year
> >> >>>>> >>> >> >> > project
> >> >>>>> >>> also a
> >> >>>>> >>> >> >> web
> >> >>>>> >>> >> >> > related application and I used same technologies I
> >> >>>>> >>> >> >> > mentioned above
> >> >>>>> >>> for
> >> >>>>> >>> >> >> > that. I am really interested in this project because I
> >> have
> >> >>>>> >>> >> >> > a good
> >> >>>>> >>> >> >> > experience with web applications and I love work with
> >> >>>>> >>> >> >> > javascript.
> >> >>>>> >>> I am
> >> >>>>> >>> >> >> > looking forward to contribute to this project in this
> >> >>>>> >>> >> >> > summer. I
> >> >>>>> >>> like
> >> >>>>> >>> >> to
> >> >>>>> >>> >> >> > know more detail about this project and if you can,
> >> please
> >> >>>>> >>> >> >> > guide
> >> >>>>> >>> me to
> >> >>>>> >>> >> >> > start working on this project.
> >> >>>>> >>> >> >> >
> >> >>>>> >>> >> >> > Thank you.
> >> >>>>> >>> >> >> >
> >> >>>>> >>> >> >> > W. A. Dulanga Sashika,
> >> >>>>> >>> >> >> > Undergraduate Student,
> >> >>>>> >>> >> >> > Department of Computer Science and Engineering,
> >> >>>>> >>> >> >> > University of Moratuwa.
> >> >>>>> >>> >> >>
> >> >>>>> >>> >> >
> >> >>>>> >>> >> >
> >> >>>>> >>> >> >
> >> >>>>> >>> >> > --
> >> >>>>> >>> >> > W. A. Dulanga Sashika,
> >> >>>>> >>> >> > Undergraduate Student,
> >> >>>>> >>> >> > Department of Computer Science and Engineering,
> >> >>>>> >>> >> > University of Moratuwa.
> >> >>>>> >>> >>
> >> >>>>> >>> >
> >> >>>>> >>> >
> >> >>>>> >>> >
> >> >>>>> >>> > --
> >> >>>>> >>> > W. A. Dulanga Sashika,
> >> >>>>> >>> > Undergraduate Student,
> >> >>>>> >>> > Department of Computer Science and Engineering,
> >> >>>>> >>> > University of Moratuwa.
> >> >>>>> >>>
> >> >>>>> >>
> >> >>>>> >>
> >> >>>>> >>
> >> >>>>> >> --
> >> >>>>> >> W. A. Dulanga Sashika,
> >> >>>>> >> Undergraduate Student,
> >> >>>>> >> Department of Computer Science and Engineering,
> >> >>>>> >> University of Moratuwa.
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> W. A. Dulanga Sashika,
> >> >>>> Undergraduate Student,
> >> >>>> Department of Computer Science and Engineering,
> >> >>>> University of Moratuwa.
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> W. A. Dulanga Sashika,
> >> >>> Undergraduate Student,
> >> >>> Department of Computer Science and Engineering,
> >> >>> University of Moratuwa.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> W. A. Dulanga Sashika,
> >> >> Undergraduate Student,
> >> >> Department of Computer Science and Engineering,
> >> >> University of Moratuwa.
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > W. A. Dulanga Sashika,
> >> > Undergraduate Student,
> >> > Department of Computer Science and Engineering,
> >> > University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Cool thank you!

Yes I also did not know until someone told me 2 months ago :)

On Fri, Mar 20, 2015 at 5:06 AM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> Thank you very much for the help. I can carry on from there now. Actually I
> didn't know that this mailing list does not supported for attachments. Here
> is the screenshots I uploaded.
>
> img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
> img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
> img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
> img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
> img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
> img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0
>
> And I will share the proposal ASAP with you.
>
> Thank you
>
> On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Hi Dulanga,
>>
>> glad you figured it out while I was on a train! :)
>>
>> Can you upload the pictures to something like box.com / dropbox or an
>> image hoster as the list does not support attachments?
>>
>> We are storing our react components in files like
>>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
>>
>> To render them we still have to wrap them in Backbone Views - as our
>> framework is built for Backbone views. The backbone view files are
>> usually called `views.js`. This will go away soon but currently it is
>> the way to go:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
>>
>> which calls this at the bottom of `app/addons/cors/components.react.jsx`:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
>>
>>
>> In
>> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
>> `this.el` references the DOM-Node of the Backbone view in which then
>> the React Component is rendered into.
>>
>>
>> Regarding the proposal:
>>
>> I am happy to help you with your proposal it would be nice to have an
>> option that makes it easy to leave comments (e.g google docs)
>>
>> Best,
>> Robert
>>
>> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi,
>> > Here I attached the screen shots of Dashboard menu item. Now its working.
>> > Now I want to know that, if I need to implement react component, where
>> > should I put it? And how can I access that to render the view? just give
>> me
>> > some hints and I can carry on from there.
>> >
>> > Regards
>> >
>> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <wa...@gmail.com>
>> > wrote:
>> >>
>> >> Hey Robert, problem solved.. :)
>> >>
>> >>
>> >> Regards.
>> >>
>> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <wa...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi Robert,
>> >>>
>> >>> Now I am trying to create a new menu item for dashboard and implement a
>> >>> react component as you said. But now I am stuck in some place and
>> couldn't
>> >>> figure out the problem yet. Here is the problem I had in process. I
>> added
>> >>> dashboard menu item and added route and view for that. And i change
>> the code
>> >>> to render dashboard when we enter http://localhost:8000 . As in img1
>> and
>> >>> img2, it doesn't show the view I created. But when I click on another
>> menu
>> >>> item and come back to the dashboard, it shows the breadcrumb of
>> previous
>> >>> pages as img 3 and 4. As in
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
>> >>> , I called the new Dashboard.view() which is a component in my
>> view.js. But
>> >>> in the console, it shows Uncaught Type error. Did I miss any
>> configuration
>> >>> thing or did I do it wrong?
>> >>>
>> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi Robert,
>> >>>>
>> >>>> Thank you very much for the reference. I started to write the proposal
>> >>>> today. I hope you will help to write this proposal by reviewing  it.
>> I will
>> >>>> share it with you after complete the draft of the proposal.
>> >>>>
>> >>>> Thank you
>> >>>>
>> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
>> >>>> wrote:
>> >>>>>
>> >>>>> Some of you asked for a template for their proposals, here is what
>> I've
>> >>>>> found:
>> >>>>>
>> >>>>> http://community.staging.apache.org/gsoc#application-template
>> >>>>>
>> >>>>> Best,
>> >>>>> Robert
>> >>>>>
>> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
>> >>>>> wrote:
>> >>>>> > Wow you are making very good progress!
>> >>>>> >
>> >>>>> > We have our weekly status meetup tomorrow (see [1] for the time in
>> >>>>> > your timezone), feel free to join, meet other project members and
>> >>>>> > learn what the project is currently doing next to the Summer of
>> Code.
>> >>>>> >
>> >>>>> > I will also be around 1hr earlier to answer all your questions and
>> >>>>> > discuss our next steps.
>> >>>>> >
>> >>>>> >
>> >>>>> > [1]
>> >>>>> >
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >>>>> >
>> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
>> >>>>> > <wa...@gmail.com> wrote:
>> >>>>> >> Hi Robert,
>> >>>>> >>
>> >>>>> >> Here is the current status of the checklist :)
>> >>>>> >>
>> >>>>> >>  - check out the active tasks api (linked on top of this mail) -
>> >>>>> >> (finished)
>> >>>>> >>  - a mockup showing some widgets and how they could look like -
>> >>>>> >> (started
>> >>>>> >> but not finished yet)
>> >>>>> >>  - code React tutorial & read about Flux - (finished)
>> >>>>> >>  - take a look how we are using React - (finished)
>> >>>>> >>  - create another menu item, called "Dashboard", try to answer the
>> >>>>> >> questions to route.js et al - (started but not finished yet)
>> >>>>> >>  - get familiar how we test our code - (finished)
>> >>>>> >>  - write an hello world / hello from dulanga component that is
>> >>>>> >> rendered into a screen when opening http://localhost:8000/dash
>> or by
>> >>>>> >> clicking on "dashboard" in the sidebar - (started but not finished
>> >>>>> >> yet)
>> >>>>> >>
>> >>>>> >> I will do my best to complete all these by tomorrow. If I have any
>> >>>>> >> problem,
>> >>>>> >> I will trouble you as you wished yesterday :)
>> >>>>> >>
>> >>>>> >> Thank You
>> >>>>> >>
>> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <rok@kowalski.gd
>> >
>> >>>>> >> wrote:
>> >>>>> >>
>> >>>>> >>> Hi Dulanga,
>> >>>>> >>>
>> >>>>> >>> we already talked on irc and you already talked to Alex regarding
>> >>>>> >>> features for our dashboard. That's great!
>> >>>>> >>>
>> >>>>> >>> Some topics will repeat in this mail, but I also would like the
>> ML
>> >>>>> >>> to
>> >>>>> >>> follow our project and additionally add some more in-depth
>> >>>>> >>> informations.
>> >>>>> >>>
>> >>>>> >>> Recap & additons
>> >>>>> >>> =====
>> >>>>> >>>
>> >>>>> >>> As discussed we will work in an iterative approach and add widget
>> >>>>> >>> after widget so if we run out of time, we will have something to
>> >>>>> >>> deliver and don't have to throw everything away.
>> >>>>> >>>
>> >>>>> >>> Have you seen the "database" tab or the "config" tab in the
>> sidebar
>> >>>>> >>> on the
>> >>>>> >>> left?
>> >>>>> >>>
>> >>>>> >>> Those are modules that we can hook into the Fauxton build, by
>> >>>>> >>> configuration. I think the idea is to create a tab "dashboard"
>> >>>>> >>> which
>> >>>>> >>> is the default one after opening Fauxton in the browser. So you
>> >>>>> >>> would
>> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
>> >>>>> >>>
>> >>>>> >>> Alex ideas so far:
>> >>>>> >>>
>> >>>>> >>> ```
>> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are
>> >>>>> >>> some
>> >>>>> >>> points about showing stats and log - forget these (: _stats isn't
>> >>>>> >>> available for
>> >>>>> >>>                    cluster iface and _log is removed. but
>> recently
>> >>>>> >>> visited databases, active tasks and _users/_replicator quick
>> >>>>> >>> management is what could
>> >>>>> >>>                    be really handy.
>> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>> >>>>> >>> anymore after backporting some cloudant features
>> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how
>> (:
>> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>> >>>>> >>> believe you could make some builtin and leave a template one to
>> let
>> >>>>> >>> the end users create
>> >>>>> >>>                    their own if they're able/would like to. in
>> >>>>> >>> future
>> >>>>> >>> these are could be fauxton plugins or something.
>> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea
>> for a
>> >>>>> >>> hot
>> >>>>> >>> widget.
>> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with
>> >>>>> >>> that
>> >>>>> >>> (add custom widgets on build time) - the build is complicated,
>> but
>> >>>>> >>> once explained
>> >>>>> >>>                            it should be easy
>> >>>>> >>> ```
>> >>>>> >>>
>> >>>>> >>> So we have "custom widgets", "cluster quick-management", "
>> recently
>> >>>>> >>> visited databases",  "active tasks" and "_users/_replicator quick
>> >>>>> >>> management"
>> >>>>> >>>
>> >>>>> >>> I think two good widgets for starting are active tasks and
>> recently
>> >>>>> >>> visited databases.
>> >>>>> >>>
>> >>>>> >>> For active tasks we have some nice docs:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>> >>>>> >>>
>> >>>>> >>> They have an own dedicated page in Fauxton (see
>> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick condensed
>> >>>>> >>> list
>> >>>>> >>> is probably very interesting to users.
>> >>>>> >>>
>> >>>>> >>> For the recently visited databases we would have to store that
>> >>>>> >>> somewhere.
>> >>>>> >>>
>> >>>>> >>> If you want, you can take an existing page in Fauxton and just
>> >>>>> >>> modify
>> >>>>> >>> the markup for a design mockup how the widget view may look like.
>> >>>>> >>> But
>> >>>>> >>> feel also free to use pen/paper or other tools if you like that
>> the
>> >>>>> >>> most.
>> >>>>> >>>
>> >>>>> >>> For the mango feature I am currently working on, I took the "edit
>> >>>>> >>> view" template on modified the markup using the Chrome inspector
>> of
>> >>>>> >>> my
>> >>>>> >>> browser to collect some first feedback from the project members
>> and
>> >>>>> >>> my
>> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>> >>>>> >>> functionality, but gives other folks a rough idea what my idea
>> for
>> >>>>> >>> the
>> >>>>> >>> feature is.
>> >>>>> >>>
>> >>>>> >>> the framework and react
>> >>>>> >>>
>> >>>>> >>> As I already mentioned we are using React.js.
>> >>>>> >>>
>> >>>>> >>> It would be nice if you can finish the tutorial at
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>> >>>>> >>> until next friday by following the steps and writing that code.
>> >>>>> >>> After
>> >>>>> >>> that, read
>> >>>>> >>>
>> >>>>> >>>
>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>> >>>>> >>> to get a first impression how the Flux pattern works that we are
>> >>>>> >>> using.
>> >>>>> >>>
>> >>>>> >>> After that (if you still have time left) take a look on a
>> component
>> >>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>> >>>>> >>>
>> >>>>> >>> Please take a look how the data flows from the Components, using
>> >>>>> >>> the
>> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>> >>>>> >>> everything in the code with console.log to see how state changes
>> >>>>> >>> and
>> >>>>> >>> how the data flows.
>> >>>>> >>>
>> >>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>> If you still have time, just try to create another menu item,
>> >>>>> >>> called
>> >>>>> >>> "Dashboard". Take a look at:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>> >>>>> >>>
>> >>>>> >>> to get a first idea how to do that. Some background information:
>> >>>>> >>>
>> >>>>> >>> base.js - the starting point of our module. basic configuration
>> is
>> >>>>> >>> done
>> >>>>> >>> here
>> >>>>> >>> Question: what is `base.js` used for in the case of the config
>> >>>>> >>> module?
>> >>>>> >>>
>> >>>>> >>> routes.js - takes care that functions injecting the view into the
>> >>>>> >>> layout are called depending on the url given
>> >>>>> >>> Question: What happens if I call `http:localhost:8000/_config`
>> and
>> >>>>> >>> what happens if you remove the function `apiUrl`?
>> >>>>> >>>
>> >>>>> >>> views.js - contains our views - this file contains still a lot
>> >>>>> >>> backbone views, which we are currently migrating to react. maybe
>> it
>> >>>>> >>> makes more sense to take a look at one of our react components:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>> >>>>> >>>
>> >>>>> >>> and how they are used currently (as we are migrating to react
>> >>>>> >>> currently):
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>> >>>>> >>>
>> >>>>> >>> The Objects are injected into the closures using AMD:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>> >>>>> >>>
>> >>>>> >>> assets folder:
>> >>>>> >>> contains our less which is compiled to css
>> >>>>> >>>
>> >>>>> >>> templates folder:
>> >>>>> >>> contains old backbone.js templates, you will not need them
>> >>>>> >>>
>> >>>>> >>> tests folder:
>> >>>>> >>> contains unit and integration tests, every PR must have unit
>> tests
>> >>>>> >>> and
>> >>>>> >>> integration tests. If you never wrote tests, we will explain it
>> to
>> >>>>> >>> you
>> >>>>> >>> - it is easy once you wrote your first few ones. Basically you
>> are
>> >>>>> >>> testing each time that if you put something into a function, the
>> >>>>> >>> expected result happens. Or that if you take an action, a state
>> has
>> >>>>> >>> changed.
>> >>>>> >>>
>> >>>>> >>> You can run the unit tests using `grunt test`
>> >>>>> >>>
>> >>>>> >>> Single tests are run by:
>> >>>>> >>>
>> >>>>> >>> ```
>> >>>>> >>> grunt test
>> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
>> >>>>> >>> ```
>> >>>>> >>>
>> >>>>> >>> or in the browser by test group:
>> >>>>> >>>
>> >>>>> >>> ```
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>> >>>>> >>> ```
>> >>>>> >>>
>> >>>>> >>> (change path to your fauxton directory)
>> >>>>> >>>
>> >>>>> >>> The corresponding code is:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>> >>>>> >>>
>> >>>>> >>> and these tests are a good example how to write a simple test for
>> >>>>> >>> the
>> >>>>> >>> hello world/hello from dulanga-component:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>> First steps:
>> >>>>> >>>
>> >>>>> >>> Create a module `dashboard` that gets displayed in the sidebar.
>> The
>> >>>>> >>> route http://localhost:8000/dash will render a small React
>> >>>>> >>> component
>> >>>>> >>> that display "Hello World".
>> >>>>> >>>
>> >>>>> >>> If you click on the "Hello World" it ill change the content to:
>> >>>>> >>> "Hello
>> >>>>> >>> from Dulanga"
>> >>>>> >>>
>> >>>>> >>> While we will throw the small component away afterwards we will
>> >>>>> >>> build
>> >>>>> >>> upon the other code you created. If you have time left, add a
>> test
>> >>>>> >>> that the component changes the content.
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>> Meeting Wednesday:
>> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >>>>> >>>
>> >>>>> >>> I will be around at least one hour before so we can chat. Contact
>> >>>>> >>> me
>> >>>>> >>> if you would like to chat earlier/later. I am also around the
>> other
>> >>>>> >>> days on IRC / the mailinglist and feel free to contact me in
>> >>>>> >>> #couchdb-dev at any time. If I am not around I will answer you
>> once
>> >>>>> >>> I
>> >>>>> >>> got online again, as I read the backlog.
>> >>>>> >>>
>> >>>>> >>>
>> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
>> >>>>> >>>
>> >>>>> >>>  - check out the active tasks api (linked on top of this mail)
>> >>>>> >>>  - a mockup showing some widgets and how they could look like
>> >>>>> >>>  - code React tutorial & read about Flux
>> >>>>> >>>  - take a look how we are using React
>> >>>>> >>>  - create another menu item, called "Dashboard", try to answer
>> the
>> >>>>> >>> questions to route.js et al
>> >>>>> >>>  - get familiar how we test our code
>> >>>>> >>>  - write an hello world / hello from dulanga component that is
>> >>>>> >>> rendered into a screen when opening http://localhost:8000/dash
>> or
>> >>>>> >>> by
>> >>>>> >>> clicking on "dashboard" in the sidebar
>> >>>>> >>>
>> >>>>> >>> That was a lot of content and please don't feel discouraged if
>> you
>> >>>>> >>> don't get that far until Wednesday. We will have to find a speed
>> >>>>> >>> which
>> >>>>> >>> is perfect for you and this time I tried to give enough
>> >>>>> >>> informations
>> >>>>> >>> that you are not blocked until Wednesday by waiting for next
>> steps.
>> >>>>> >>> If
>> >>>>> >>> you are at the last step before Wednesday, drop me a line and I
>> >>>>> >>> will
>> >>>>> >>> prepare the next steps :)
>> >>>>> >>>
>> >>>>> >>> I know that you all have important exams, these are definitely
>> more
>> >>>>> >>> important! Don't feel pressured by the amount of work / the
>> amount
>> >>>>> >>> of
>> >>>>> >>> informations, getting good results in the exams should be your
>> >>>>> >>> first
>> >>>>> >>> priority.
>> >>>>> >>>
>> >>>>> >>> Best,
>> >>>>> >>> Robert
>> >>>>> >>>
>> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
>> >>>>> >>> <wa...@gmail.com>
>> >>>>> >>> wrote:
>> >>>>> >>> > Hi Robert,
>> >>>>> >>> >
>> >>>>> >>> > I went through the guidelines you provided and successfully
>> >>>>> >>> > installed and
>> >>>>> >>> > configured as you said. Everything works find and I played
>> around
>> >>>>> >>> > it by
>> >>>>> >>> > creating a database and documents. I think I am ready for the
>> >>>>> >>> > next step
>> >>>>> >>> and
>> >>>>> >>> > we can start it if you are ok :)
>> >>>>> >>> >
>> >>>>> >>> > Thank You
>> >>>>> >>> >
>> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
>> >>>>> >>> > <ro...@kowalski.gd>
>> >>>>> >>> wrote:
>> >>>>> >>> >
>> >>>>> >>> >> You're welcome.
>> >>>>> >>> >>
>> >>>>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs
>> if
>> >>>>> >>> >> you get
>> >>>>> >>> >> stuck!
>> >>>>> >>> >>
>> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
>> >>>>> >>> >> <wa...@gmail.com>
>> >>>>> >>> >> wrote:
>> >>>>> >>> >> > Hi Robert,
>> >>>>> >>> >> >
>> >>>>> >>> >> > Thank you very much for the quick reply. I will go through
>> the
>> >>>>> >>> guidelines
>> >>>>> >>> >> > and contact you if I have any issue with them.
>> >>>>> >>> >> >
>> >>>>> >>> >> > Thank you
>> >>>>> >>> >> >
>> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
>> >>>>> >>> >> > <ro...@kowalski.gd>
>> >>>>> >>> >> wrote:
>> >>>>> >>> >> >
>> >>>>> >>> >> >> Hi Dulanga,
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> glad you found your way to the CouchDB mailing list.
>> Welcome
>> >>>>> >>> >> >> :)
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API -
>> >>>>> >>> >> >> that makes
>> >>>>> >>> >> >> it a great fit for web applications that don't need a
>> server
>> >>>>> >>> >> >> side
>> >>>>> >>> >> >> layer with a database driver in between. Our Project
>> Fauxton
>> >>>>> >>> >> >> (like a
>> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
>> >>>>> >>> >> >> myself.
>> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
>> >>>>> >>> >> >> online (e.g.
>> >>>>> >>> I
>> >>>>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> We are all happy to help each other in the project :)
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> If you are using windows: I am not a Windows expert - you
>> >>>>> >>> >> >> will
>> >>>>> >>> >> >> probably have to use a bash emulator like "git bash" to
>> boot
>> >>>>> >>> >> >> the dev
>> >>>>> >>> >> >> environment.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Getting started:
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> For this project you will need to install at least CouchDB
>> >>>>> >>> >> >> 1.x, an
>> >>>>> >>> >> >> Ubuntu package (with installation instructions) is at
>> >>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
>> >>>>> >>> >> >> (install from
>> >>>>> >>> >> >> https://nodejs.org)
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> booting CouchDB:
>> >>>>> >>> >> >> $ sudo couchdb
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> in another terminal, clone the admin interface:
>> >>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> go to Fauxton:
>> >>>>> >>> >> >> $ cd couchdb-fauxton
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> install dependencies:
>> >>>>> >>> >> >> $ npm install
>> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> boot the app:
>> >>>>> >>> >> >> $ grunt dev
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Then open your browser and go to http://localhost:8000 -
>> you
>> >>>>> >>> >> >> should
>> >>>>> >>> >> >> see a red/gray/black interface
>> >>>>> >>> >> >>
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> That was a lot of input and especially if you are using
>> Linux
>> >>>>> >>> >> >> the
>> >>>>> >>> >> >> first time and followed the instructions you have archived
>> a
>> >>>>> >>> >> >> lot!
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> As first step, try to create a database and a document now
>> >>>>> >>> >> >> using the
>> >>>>> >>> >> >> web interface (PS we are happy about any usability
>> feedback).
>> >>>>> >>> >> >> :)
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> I think you have your dev environment for CouchDB ready
>> now.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> What's next:
>> >>>>> >>> >> >> If everything works we will take a look at Fauxtons code
>> >>>>> >>> >> >> structure
>> >>>>> >>> and
>> >>>>> >>> >> >> how it works. We will also talk about the features of the
>> >>>>> >>> >> >> dashboard.
>> >>>>> >>> >> >> Let's find a date for a chat after you took a first look
>> how
>> >>>>> >>> >> >> Fauxton
>> >>>>> >>> >> >> looks like.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC
>> on
>> >>>>> >>> >> >> freenode
>> >>>>> >>> >> >> (see
>> >>>>> >>> >> >>
>> >>>>> >>> >>
>> >>>>> >>>
>> >>>>> >>>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >>>>> >>> >> >> )
>> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if you
>> >>>>> >>> >> >> want to
>> >>>>> >>> >> >> chat with me before.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> Looking forward to work with you,
>> >>>>> >>> >> >> Robert
>> >>>>> >>> >> >>
>> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>> >>>>> >>> wadsashika@gmail.com>
>> >>>>> >>> >> >> wrote:
>> >>>>> >>> >> >> > Hi all,
>> >>>>> >>> >> >> >
>> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
>> >>>>> >>> >> >> > student at
>> >>>>> >>> >> >> > Computer Science and Engineering department at University
>> >>>>> >>> >> >> > of
>> >>>>> >>> Moratuwa,
>> >>>>> >>> >> >> Sri
>> >>>>> >>> >> >> > Lanka. I am really interested in java, java script, web
>> >>>>> >>> applications,
>> >>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
>> >>>>> >>> >> >> > months of
>> >>>>> >>> >> training
>> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked
>> on a
>> >>>>> >>> >> >> > web
>> >>>>> >>> >> >> application
>> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My final year
>> >>>>> >>> >> >> > project
>> >>>>> >>> also a
>> >>>>> >>> >> >> web
>> >>>>> >>> >> >> > related application and I used same technologies I
>> >>>>> >>> >> >> > mentioned above
>> >>>>> >>> for
>> >>>>> >>> >> >> > that. I am really interested in this project because I
>> have
>> >>>>> >>> >> >> > a good
>> >>>>> >>> >> >> > experience with web applications and I love work with
>> >>>>> >>> >> >> > javascript.
>> >>>>> >>> I am
>> >>>>> >>> >> >> > looking forward to contribute to this project in this
>> >>>>> >>> >> >> > summer. I
>> >>>>> >>> like
>> >>>>> >>> >> to
>> >>>>> >>> >> >> > know more detail about this project and if you can,
>> please
>> >>>>> >>> >> >> > guide
>> >>>>> >>> me to
>> >>>>> >>> >> >> > start working on this project.
>> >>>>> >>> >> >> >
>> >>>>> >>> >> >> > Thank you.
>> >>>>> >>> >> >> >
>> >>>>> >>> >> >> > W. A. Dulanga Sashika,
>> >>>>> >>> >> >> > Undergraduate Student,
>> >>>>> >>> >> >> > Department of Computer Science and Engineering,
>> >>>>> >>> >> >> > University of Moratuwa.
>> >>>>> >>> >> >>
>> >>>>> >>> >> >
>> >>>>> >>> >> >
>> >>>>> >>> >> >
>> >>>>> >>> >> > --
>> >>>>> >>> >> > W. A. Dulanga Sashika,
>> >>>>> >>> >> > Undergraduate Student,
>> >>>>> >>> >> > Department of Computer Science and Engineering,
>> >>>>> >>> >> > University of Moratuwa.
>> >>>>> >>> >>
>> >>>>> >>> >
>> >>>>> >>> >
>> >>>>> >>> >
>> >>>>> >>> > --
>> >>>>> >>> > W. A. Dulanga Sashika,
>> >>>>> >>> > Undergraduate Student,
>> >>>>> >>> > Department of Computer Science and Engineering,
>> >>>>> >>> > University of Moratuwa.
>> >>>>> >>>
>> >>>>> >>
>> >>>>> >>
>> >>>>> >>
>> >>>>> >> --
>> >>>>> >> W. A. Dulanga Sashika,
>> >>>>> >> Undergraduate Student,
>> >>>>> >> Department of Computer Science and Engineering,
>> >>>>> >> University of Moratuwa.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> W. A. Dulanga Sashika,
>> >>>> Undergraduate Student,
>> >>>> Department of Computer Science and Engineering,
>> >>>> University of Moratuwa.
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> W. A. Dulanga Sashika,
>> >>> Undergraduate Student,
>> >>> Department of Computer Science and Engineering,
>> >>> University of Moratuwa.
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> W. A. Dulanga Sashika,
>> >> Undergraduate Student,
>> >> Department of Computer Science and Engineering,
>> >> University of Moratuwa.
>> >
>> >
>> >
>> >
>> > --
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Thank you very much for the help. I can carry on from there now. Actually I
didn't know that this mailing list does not supported for attachments. Here
is the screenshots I uploaded.

img1 - https://www.dropbox.com/s/1dwgxnfip1zgphd/img1.png?dl=0
img2 - https://www.dropbox.com/s/5chqk1smnuqaxtt/img2.png?dl=0
img3 - https://www.dropbox.com/s/ubvlno2c6r5mbpq/img3.png?dl=0
img4 - https://www.dropbox.com/s/0i6dc855vxh9x9c/img4.png?dl=0
img5 - https://www.dropbox.com/s/zvy2y2v7on4occr/img5.png?dl=0
img6 - https://www.dropbox.com/s/7nwu3an5cmgd9mu/img6.png?dl=0

And I will share the proposal ASAP with you.

Thank you

On Fri, Mar 20, 2015 at 1:33 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga,
>
> glad you figured it out while I was on a train! :)
>
> Can you upload the pictures to something like box.com / dropbox or an
> image hoster as the list does not support attachments?
>
> We are storing our react components in files like
>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx
>
> To render them we still have to wrap them in Backbone Views - as our
> framework is built for Backbone views. The backbone view files are
> usually called `views.js`. This will go away soon but currently it is
> the way to go:
>
>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
>
> which calls this at the bottom of `app/addons/cors/components.react.jsx`:
>
>
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338
>
>
> In
> https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
> `this.el` references the DOM-Node of the Backbone view in which then
> the React Component is rendered into.
>
>
> Regarding the proposal:
>
> I am happy to help you with your proposal it would be nice to have an
> option that makes it easy to leave comments (e.g google docs)
>
> Best,
> Robert
>
> On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi,
> > Here I attached the screen shots of Dashboard menu item. Now its working.
> > Now I want to know that, if I need to implement react component, where
> > should I put it? And how can I access that to render the view? just give
> me
> > some hints and I can carry on from there.
> >
> > Regards
> >
> > On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <wa...@gmail.com>
> > wrote:
> >>
> >> Hey Robert, problem solved.. :)
> >>
> >>
> >> Regards.
> >>
> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <wa...@gmail.com>
> >> wrote:
> >>>
> >>> Hi Robert,
> >>>
> >>> Now I am trying to create a new menu item for dashboard and implement a
> >>> react component as you said. But now I am stuck in some place and
> couldn't
> >>> figure out the problem yet. Here is the problem I had in process. I
> added
> >>> dashboard menu item and added route and view for that. And i change
> the code
> >>> to render dashboard when we enter http://localhost:8000 . As in img1
> and
> >>> img2, it doesn't show the view I created. But when I click on another
> menu
> >>> item and come back to the dashboard, it shows the breadcrumb of
> previous
> >>> pages as img 3 and 4. As in
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> >>> , I called the new Dashboard.view() which is a component in my
> view.js. But
> >>> in the console, it shows Uncaught Type error. Did I miss any
> configuration
> >>> thing or did I do it wrong?
> >>>
> >>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <
> wadsashika@gmail.com>
> >>> wrote:
> >>>>
> >>>> Hi Robert,
> >>>>
> >>>> Thank you very much for the reference. I started to write the proposal
> >>>> today. I hope you will help to write this proposal by reviewing  it.
> I will
> >>>> share it with you after complete the draft of the proposal.
> >>>>
> >>>> Thank you
> >>>>
> >>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
> >>>> wrote:
> >>>>>
> >>>>> Some of you asked for a template for their proposals, here is what
> I've
> >>>>> found:
> >>>>>
> >>>>> http://community.staging.apache.org/gsoc#application-template
> >>>>>
> >>>>> Best,
> >>>>> Robert
> >>>>>
> >>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
> >>>>> wrote:
> >>>>> > Wow you are making very good progress!
> >>>>> >
> >>>>> > We have our weekly status meetup tomorrow (see [1] for the time in
> >>>>> > your timezone), feel free to join, meet other project members and
> >>>>> > learn what the project is currently doing next to the Summer of
> Code.
> >>>>> >
> >>>>> > I will also be around 1hr earlier to answer all your questions and
> >>>>> > discuss our next steps.
> >>>>> >
> >>>>> >
> >>>>> > [1]
> >>>>> >
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >>>>> >
> >>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
> >>>>> > <wa...@gmail.com> wrote:
> >>>>> >> Hi Robert,
> >>>>> >>
> >>>>> >> Here is the current status of the checklist :)
> >>>>> >>
> >>>>> >>  - check out the active tasks api (linked on top of this mail) -
> >>>>> >> (finished)
> >>>>> >>  - a mockup showing some widgets and how they could look like -
> >>>>> >> (started
> >>>>> >> but not finished yet)
> >>>>> >>  - code React tutorial & read about Flux - (finished)
> >>>>> >>  - take a look how we are using React - (finished)
> >>>>> >>  - create another menu item, called "Dashboard", try to answer the
> >>>>> >> questions to route.js et al - (started but not finished yet)
> >>>>> >>  - get familiar how we test our code - (finished)
> >>>>> >>  - write an hello world / hello from dulanga component that is
> >>>>> >> rendered into a screen when opening http://localhost:8000/dash
> or by
> >>>>> >> clicking on "dashboard" in the sidebar - (started but not finished
> >>>>> >> yet)
> >>>>> >>
> >>>>> >> I will do my best to complete all these by tomorrow. If I have any
> >>>>> >> problem,
> >>>>> >> I will trouble you as you wished yesterday :)
> >>>>> >>
> >>>>> >> Thank You
> >>>>> >>
> >>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <rok@kowalski.gd
> >
> >>>>> >> wrote:
> >>>>> >>
> >>>>> >>> Hi Dulanga,
> >>>>> >>>
> >>>>> >>> we already talked on irc and you already talked to Alex regarding
> >>>>> >>> features for our dashboard. That's great!
> >>>>> >>>
> >>>>> >>> Some topics will repeat in this mail, but I also would like the
> ML
> >>>>> >>> to
> >>>>> >>> follow our project and additionally add some more in-depth
> >>>>> >>> informations.
> >>>>> >>>
> >>>>> >>> Recap & additons
> >>>>> >>> =====
> >>>>> >>>
> >>>>> >>> As discussed we will work in an iterative approach and add widget
> >>>>> >>> after widget so if we run out of time, we will have something to
> >>>>> >>> deliver and don't have to throw everything away.
> >>>>> >>>
> >>>>> >>> Have you seen the "database" tab or the "config" tab in the
> sidebar
> >>>>> >>> on the
> >>>>> >>> left?
> >>>>> >>>
> >>>>> >>> Those are modules that we can hook into the Fauxton build, by
> >>>>> >>> configuration. I think the idea is to create a tab "dashboard"
> >>>>> >>> which
> >>>>> >>> is the default one after opening Fauxton in the browser. So you
> >>>>> >>> would
> >>>>> >>> build the dashboard for Fauxton as part of Fauxton.
> >>>>> >>>
> >>>>> >>> Alex ideas so far:
> >>>>> >>>
> >>>>> >>> ```
> >>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are
> >>>>> >>> some
> >>>>> >>> points about showing stats and log - forget these (: _stats isn't
> >>>>> >>> available for
> >>>>> >>>                    cluster iface and _log is removed. but
> recently
> >>>>> >>> visited databases, active tasks and _users/_replicator quick
> >>>>> >>> management is what could
> >>>>> >>>                    be really handy.
> >>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
> >>>>> >>> anymore after backporting some cloudant features
> >>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how
> (:
> >>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
> >>>>> >>> believe you could make some builtin and leave a template one to
> let
> >>>>> >>> the end users create
> >>>>> >>>                    their own if they're able/would like to. in
> >>>>> >>> future
> >>>>> >>> these are could be fauxton plugins or something.
> >>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea
> for a
> >>>>> >>> hot
> >>>>> >>> widget.
> >>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with
> >>>>> >>> that
> >>>>> >>> (add custom widgets on build time) - the build is complicated,
> but
> >>>>> >>> once explained
> >>>>> >>>                            it should be easy
> >>>>> >>> ```
> >>>>> >>>
> >>>>> >>> So we have "custom widgets", "cluster quick-management", "
> recently
> >>>>> >>> visited databases",  "active tasks" and "_users/_replicator quick
> >>>>> >>> management"
> >>>>> >>>
> >>>>> >>> I think two good widgets for starting are active tasks and
> recently
> >>>>> >>> visited databases.
> >>>>> >>>
> >>>>> >>> For active tasks we have some nice docs:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> >>>>> >>>
> >>>>> >>> They have an own dedicated page in Fauxton (see
> >>>>> >>> http://localhost:8000/#/activetasks) but a short quick condensed
> >>>>> >>> list
> >>>>> >>> is probably very interesting to users.
> >>>>> >>>
> >>>>> >>> For the recently visited databases we would have to store that
> >>>>> >>> somewhere.
> >>>>> >>>
> >>>>> >>> If you want, you can take an existing page in Fauxton and just
> >>>>> >>> modify
> >>>>> >>> the markup for a design mockup how the widget view may look like.
> >>>>> >>> But
> >>>>> >>> feel also free to use pen/paper or other tools if you like that
> the
> >>>>> >>> most.
> >>>>> >>>
> >>>>> >>> For the mango feature I am currently working on, I took the "edit
> >>>>> >>> view" template on modified the markup using the Chrome inspector
> of
> >>>>> >>> my
> >>>>> >>> browser to collect some first feedback from the project members
> and
> >>>>> >>> my
> >>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
> >>>>> >>> functionality, but gives other folks a rough idea what my idea
> for
> >>>>> >>> the
> >>>>> >>> feature is.
> >>>>> >>>
> >>>>> >>> the framework and react
> >>>>> >>>
> >>>>> >>> As I already mentioned we are using React.js.
> >>>>> >>>
> >>>>> >>> It would be nice if you can finish the tutorial at
> >>>>> >>>
> >>>>> >>>
> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> >>>>> >>> until next friday by following the steps and writing that code.
> >>>>> >>> After
> >>>>> >>> that, read
> >>>>> >>>
> >>>>> >>>
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> >>>>> >>> to get a first impression how the Flux pattern works that we are
> >>>>> >>> using.
> >>>>> >>>
> >>>>> >>> After that (if you still have time left) take a look on a
> component
> >>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> >>>>> >>>
> >>>>> >>> Please take a look how the data flows from the Components, using
> >>>>> >>> the
> >>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
> >>>>> >>> everything in the code with console.log to see how state changes
> >>>>> >>> and
> >>>>> >>> how the data flows.
> >>>>> >>>
> >>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> If you still have time, just try to create another menu item,
> >>>>> >>> called
> >>>>> >>> "Dashboard". Take a look at:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> >>>>> >>>
> >>>>> >>> to get a first idea how to do that. Some background information:
> >>>>> >>>
> >>>>> >>> base.js - the starting point of our module. basic configuration
> is
> >>>>> >>> done
> >>>>> >>> here
> >>>>> >>> Question: what is `base.js` used for in the case of the config
> >>>>> >>> module?
> >>>>> >>>
> >>>>> >>> routes.js - takes care that functions injecting the view into the
> >>>>> >>> layout are called depending on the url given
> >>>>> >>> Question: What happens if I call `http:localhost:8000/_config`
> and
> >>>>> >>> what happens if you remove the function `apiUrl`?
> >>>>> >>>
> >>>>> >>> views.js - contains our views - this file contains still a lot
> >>>>> >>> backbone views, which we are currently migrating to react. maybe
> it
> >>>>> >>> makes more sense to take a look at one of our react components:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> >>>>> >>>
> >>>>> >>> and how they are used currently (as we are migrating to react
> >>>>> >>> currently):
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> >>>>> >>>
> >>>>> >>> The Objects are injected into the closures using AMD:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> >>>>> >>>
> >>>>> >>> assets folder:
> >>>>> >>> contains our less which is compiled to css
> >>>>> >>>
> >>>>> >>> templates folder:
> >>>>> >>> contains old backbone.js templates, you will not need them
> >>>>> >>>
> >>>>> >>> tests folder:
> >>>>> >>> contains unit and integration tests, every PR must have unit
> tests
> >>>>> >>> and
> >>>>> >>> integration tests. If you never wrote tests, we will explain it
> to
> >>>>> >>> you
> >>>>> >>> - it is easy once you wrote your first few ones. Basically you
> are
> >>>>> >>> testing each time that if you put something into a function, the
> >>>>> >>> expected result happens. Or that if you take an action, a state
> has
> >>>>> >>> changed.
> >>>>> >>>
> >>>>> >>> You can run the unit tests using `grunt test`
> >>>>> >>>
> >>>>> >>> Single tests are run by:
> >>>>> >>>
> >>>>> >>> ```
> >>>>> >>> grunt test
> >>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
> >>>>> >>> ```
> >>>>> >>>
> >>>>> >>> or in the browser by test group:
> >>>>> >>>
> >>>>> >>> ```
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> >>>>> >>> ```
> >>>>> >>>
> >>>>> >>> (change path to your fauxton directory)
> >>>>> >>>
> >>>>> >>> The corresponding code is:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> >>>>> >>>
> >>>>> >>> and these tests are a good example how to write a simple test for
> >>>>> >>> the
> >>>>> >>> hello world/hello from dulanga-component:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> First steps:
> >>>>> >>>
> >>>>> >>> Create a module `dashboard` that gets displayed in the sidebar.
> The
> >>>>> >>> route http://localhost:8000/dash will render a small React
> >>>>> >>> component
> >>>>> >>> that display "Hello World".
> >>>>> >>>
> >>>>> >>> If you click on the "Hello World" it ill change the content to:
> >>>>> >>> "Hello
> >>>>> >>> from Dulanga"
> >>>>> >>>
> >>>>> >>> While we will throw the small component away afterwards we will
> >>>>> >>> build
> >>>>> >>> upon the other code you created. If you have time left, add a
> test
> >>>>> >>> that the component changes the content.
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> Meeting Wednesday:
> >>>>> >>> Feel free to join us on our weekly couchdb meeting:
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >>>>> >>>
> >>>>> >>> I will be around at least one hour before so we can chat. Contact
> >>>>> >>> me
> >>>>> >>> if you would like to chat earlier/later. I am also around the
> other
> >>>>> >>> days on IRC / the mailinglist and feel free to contact me in
> >>>>> >>> #couchdb-dev at any time. If I am not around I will answer you
> once
> >>>>> >>> I
> >>>>> >>> got online again, as I read the backlog.
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
> >>>>> >>>
> >>>>> >>>  - check out the active tasks api (linked on top of this mail)
> >>>>> >>>  - a mockup showing some widgets and how they could look like
> >>>>> >>>  - code React tutorial & read about Flux
> >>>>> >>>  - take a look how we are using React
> >>>>> >>>  - create another menu item, called "Dashboard", try to answer
> the
> >>>>> >>> questions to route.js et al
> >>>>> >>>  - get familiar how we test our code
> >>>>> >>>  - write an hello world / hello from dulanga component that is
> >>>>> >>> rendered into a screen when opening http://localhost:8000/dash
> or
> >>>>> >>> by
> >>>>> >>> clicking on "dashboard" in the sidebar
> >>>>> >>>
> >>>>> >>> That was a lot of content and please don't feel discouraged if
> you
> >>>>> >>> don't get that far until Wednesday. We will have to find a speed
> >>>>> >>> which
> >>>>> >>> is perfect for you and this time I tried to give enough
> >>>>> >>> informations
> >>>>> >>> that you are not blocked until Wednesday by waiting for next
> steps.
> >>>>> >>> If
> >>>>> >>> you are at the last step before Wednesday, drop me a line and I
> >>>>> >>> will
> >>>>> >>> prepare the next steps :)
> >>>>> >>>
> >>>>> >>> I know that you all have important exams, these are definitely
> more
> >>>>> >>> important! Don't feel pressured by the amount of work / the
> amount
> >>>>> >>> of
> >>>>> >>> informations, getting good results in the exams should be your
> >>>>> >>> first
> >>>>> >>> priority.
> >>>>> >>>
> >>>>> >>> Best,
> >>>>> >>> Robert
> >>>>> >>>
> >>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
> >>>>> >>> <wa...@gmail.com>
> >>>>> >>> wrote:
> >>>>> >>> > Hi Robert,
> >>>>> >>> >
> >>>>> >>> > I went through the guidelines you provided and successfully
> >>>>> >>> > installed and
> >>>>> >>> > configured as you said. Everything works find and I played
> around
> >>>>> >>> > it by
> >>>>> >>> > creating a database and documents. I think I am ready for the
> >>>>> >>> > next step
> >>>>> >>> and
> >>>>> >>> > we can start it if you are ok :)
> >>>>> >>> >
> >>>>> >>> > Thank You
> >>>>> >>> >
> >>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
> >>>>> >>> > <ro...@kowalski.gd>
> >>>>> >>> wrote:
> >>>>> >>> >
> >>>>> >>> >> You're welcome.
> >>>>> >>> >>
> >>>>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs
> if
> >>>>> >>> >> you get
> >>>>> >>> >> stuck!
> >>>>> >>> >>
> >>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
> >>>>> >>> >> <wa...@gmail.com>
> >>>>> >>> >> wrote:
> >>>>> >>> >> > Hi Robert,
> >>>>> >>> >> >
> >>>>> >>> >> > Thank you very much for the quick reply. I will go through
> the
> >>>>> >>> guidelines
> >>>>> >>> >> > and contact you if I have any issue with them.
> >>>>> >>> >> >
> >>>>> >>> >> > Thank you
> >>>>> >>> >> >
> >>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
> >>>>> >>> >> > <ro...@kowalski.gd>
> >>>>> >>> >> wrote:
> >>>>> >>> >> >
> >>>>> >>> >> >> Hi Dulanga,
> >>>>> >>> >> >>
> >>>>> >>> >> >> glad you found your way to the CouchDB mailing list.
> Welcome
> >>>>> >>> >> >> :)
> >>>>> >>> >> >>
> >>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API -
> >>>>> >>> >> >> that makes
> >>>>> >>> >> >> it a great fit for web applications that don't need a
> server
> >>>>> >>> >> >> side
> >>>>> >>> >> >> layer with a database driver in between. Our Project
> Fauxton
> >>>>> >>> >> >> (like a
> >>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> >>>>> >>> >> >>
> >>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
> >>>>> >>> >> >> myself.
> >>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
> >>>>> >>> >> >> online (e.g.
> >>>>> >>> I
> >>>>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
> >>>>> >>> >> >>
> >>>>> >>> >> >> We are all happy to help each other in the project :)
> >>>>> >>> >> >>
> >>>>> >>> >> >> If you are using windows: I am not a Windows expert - you
> >>>>> >>> >> >> will
> >>>>> >>> >> >> probably have to use a bash emulator like "git bash" to
> boot
> >>>>> >>> >> >> the dev
> >>>>> >>> >> >> environment.
> >>>>> >>> >> >>
> >>>>> >>> >> >> Getting started:
> >>>>> >>> >> >>
> >>>>> >>> >> >> For this project you will need to install at least CouchDB
> >>>>> >>> >> >> 1.x, an
> >>>>> >>> >> >> Ubuntu package (with installation instructions) is at
> >>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >>>>> >>> >> >>
> >>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
> >>>>> >>> >> >> (install from
> >>>>> >>> >> >> https://nodejs.org)
> >>>>> >>> >> >>
> >>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
> >>>>> >>> >> >>
> >>>>> >>> >> >> booting CouchDB:
> >>>>> >>> >> >> $ sudo couchdb
> >>>>> >>> >> >>
> >>>>> >>> >> >> in another terminal, clone the admin interface:
> >>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
> >>>>> >>> >> >>
> >>>>> >>> >> >> go to Fauxton:
> >>>>> >>> >> >> $ cd couchdb-fauxton
> >>>>> >>> >> >>
> >>>>> >>> >> >> install dependencies:
> >>>>> >>> >> >> $ npm install
> >>>>> >>> >> >> $ npm install -g grunt grunt-cli
> >>>>> >>> >> >>
> >>>>> >>> >> >> boot the app:
> >>>>> >>> >> >> $ grunt dev
> >>>>> >>> >> >>
> >>>>> >>> >> >> Then open your browser and go to http://localhost:8000 -
> you
> >>>>> >>> >> >> should
> >>>>> >>> >> >> see a red/gray/black interface
> >>>>> >>> >> >>
> >>>>> >>> >> >>
> >>>>> >>> >> >> That was a lot of input and especially if you are using
> Linux
> >>>>> >>> >> >> the
> >>>>> >>> >> >> first time and followed the instructions you have archived
> a
> >>>>> >>> >> >> lot!
> >>>>> >>> >> >>
> >>>>> >>> >> >> As first step, try to create a database and a document now
> >>>>> >>> >> >> using the
> >>>>> >>> >> >> web interface (PS we are happy about any usability
> feedback).
> >>>>> >>> >> >> :)
> >>>>> >>> >> >>
> >>>>> >>> >> >> I think you have your dev environment for CouchDB ready
> now.
> >>>>> >>> >> >>
> >>>>> >>> >> >> What's next:
> >>>>> >>> >> >> If everything works we will take a look at Fauxtons code
> >>>>> >>> >> >> structure
> >>>>> >>> and
> >>>>> >>> >> >> how it works. We will also talk about the features of the
> >>>>> >>> >> >> dashboard.
> >>>>> >>> >> >> Let's find a date for a chat after you took a first look
> how
> >>>>> >>> >> >> Fauxton
> >>>>> >>> >> >> looks like.
> >>>>> >>> >> >>
> >>>>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
> >>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC
> on
> >>>>> >>> >> >> freenode
> >>>>> >>> >> >> (see
> >>>>> >>> >> >>
> >>>>> >>> >>
> >>>>> >>>
> >>>>> >>>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >>>>> >>> >> >> )
> >>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if you
> >>>>> >>> >> >> want to
> >>>>> >>> >> >> chat with me before.
> >>>>> >>> >> >>
> >>>>> >>> >> >>
> >>>>> >>> >> >> Looking forward to work with you,
> >>>>> >>> >> >> Robert
> >>>>> >>> >> >>
> >>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> >>>>> >>> wadsashika@gmail.com>
> >>>>> >>> >> >> wrote:
> >>>>> >>> >> >> > Hi all,
> >>>>> >>> >> >> >
> >>>>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
> >>>>> >>> >> >> > student at
> >>>>> >>> >> >> > Computer Science and Engineering department at University
> >>>>> >>> >> >> > of
> >>>>> >>> Moratuwa,
> >>>>> >>> >> >> Sri
> >>>>> >>> >> >> > Lanka. I am really interested in java, java script, web
> >>>>> >>> applications,
> >>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
> >>>>> >>> >> >> > months of
> >>>>> >>> >> training
> >>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked
> on a
> >>>>> >>> >> >> > web
> >>>>> >>> >> >> application
> >>>>> >>> >> >> > that used java, JEE and Spring Framework. My final year
> >>>>> >>> >> >> > project
> >>>>> >>> also a
> >>>>> >>> >> >> web
> >>>>> >>> >> >> > related application and I used same technologies I
> >>>>> >>> >> >> > mentioned above
> >>>>> >>> for
> >>>>> >>> >> >> > that. I am really interested in this project because I
> have
> >>>>> >>> >> >> > a good
> >>>>> >>> >> >> > experience with web applications and I love work with
> >>>>> >>> >> >> > javascript.
> >>>>> >>> I am
> >>>>> >>> >> >> > looking forward to contribute to this project in this
> >>>>> >>> >> >> > summer. I
> >>>>> >>> like
> >>>>> >>> >> to
> >>>>> >>> >> >> > know more detail about this project and if you can,
> please
> >>>>> >>> >> >> > guide
> >>>>> >>> me to
> >>>>> >>> >> >> > start working on this project.
> >>>>> >>> >> >> >
> >>>>> >>> >> >> > Thank you.
> >>>>> >>> >> >> >
> >>>>> >>> >> >> > W. A. Dulanga Sashika,
> >>>>> >>> >> >> > Undergraduate Student,
> >>>>> >>> >> >> > Department of Computer Science and Engineering,
> >>>>> >>> >> >> > University of Moratuwa.
> >>>>> >>> >> >>
> >>>>> >>> >> >
> >>>>> >>> >> >
> >>>>> >>> >> >
> >>>>> >>> >> > --
> >>>>> >>> >> > W. A. Dulanga Sashika,
> >>>>> >>> >> > Undergraduate Student,
> >>>>> >>> >> > Department of Computer Science and Engineering,
> >>>>> >>> >> > University of Moratuwa.
> >>>>> >>> >>
> >>>>> >>> >
> >>>>> >>> >
> >>>>> >>> >
> >>>>> >>> > --
> >>>>> >>> > W. A. Dulanga Sashika,
> >>>>> >>> > Undergraduate Student,
> >>>>> >>> > Department of Computer Science and Engineering,
> >>>>> >>> > University of Moratuwa.
> >>>>> >>>
> >>>>> >>
> >>>>> >>
> >>>>> >>
> >>>>> >> --
> >>>>> >> W. A. Dulanga Sashika,
> >>>>> >> Undergraduate Student,
> >>>>> >> Department of Computer Science and Engineering,
> >>>>> >> University of Moratuwa.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> W. A. Dulanga Sashika,
> >>>> Undergraduate Student,
> >>>> Department of Computer Science and Engineering,
> >>>> University of Moratuwa.
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> W. A. Dulanga Sashika,
> >>> Undergraduate Student,
> >>> Department of Computer Science and Engineering,
> >>> University of Moratuwa.
> >>
> >>
> >>
> >>
> >> --
> >> W. A. Dulanga Sashika,
> >> Undergraduate Student,
> >> Department of Computer Science and Engineering,
> >> University of Moratuwa.
> >
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga,

glad you figured it out while I was on a train! :)

Can you upload the pictures to something like box.com / dropbox or an
image hoster as the list does not support attachments?

We are storing our react components in files like
https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx

To render them we still have to wrap them in Backbone Views - as our
framework is built for Backbone views. The backbone view files are
usually called `views.js`. This will go away soon but currently it is
the way to go:

https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41

which calls this at the bottom of `app/addons/cors/components.react.jsx`:

https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/components.react.jsx#L338


In https://github.com/apache/couchdb-fauxton/blob/73bacedae20d6eaeefa0607364c79c94ad862844/app/addons/cors/views.js#L25-41
`this.el` references the DOM-Node of the Backbone view in which then
the React Component is rendered into.


Regarding the proposal:

I am happy to help you with your proposal it would be nice to have an
option that makes it easy to leave comments (e.g google docs)

Best,
Robert

On Thu, Mar 19, 2015 at 6:26 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi,
> Here I attached the screen shots of Dashboard menu item. Now its working.
> Now I want to know that, if I need to implement react component, where
> should I put it? And how can I access that to render the view? just give me
> some hints and I can carry on from there.
>
> Regards
>
> On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>>
>> Hey Robert, problem solved.. :)
>>
>>
>> Regards.
>>
>> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>>
>>> Hi Robert,
>>>
>>> Now I am trying to create a new menu item for dashboard and implement a
>>> react component as you said. But now I am stuck in some place and couldn't
>>> figure out the problem yet. Here is the problem I had in process. I added
>>> dashboard menu item and added route and view for that. And i change the code
>>> to render dashboard when we enter http://localhost:8000 . As in img1 and
>>> img2, it doesn't show the view I created. But when I click on another menu
>>> item and come back to the dashboard, it shows the breadcrumb of previous
>>> pages as img 3 and 4. As in
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
>>> , I called the new Dashboard.view() which is a component in my view.js. But
>>> in the console, it shows Uncaught Type error. Did I miss any configuration
>>> thing or did I do it wrong?
>>>
>>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Robert,
>>>>
>>>> Thank you very much for the reference. I started to write the proposal
>>>> today. I hope you will help to write this proposal by reviewing  it. I will
>>>> share it with you after complete the draft of the proposal.
>>>>
>>>> Thank you
>>>>
>>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
>>>> wrote:
>>>>>
>>>>> Some of you asked for a template for their proposals, here is what I've
>>>>> found:
>>>>>
>>>>> http://community.staging.apache.org/gsoc#application-template
>>>>>
>>>>> Best,
>>>>> Robert
>>>>>
>>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
>>>>> wrote:
>>>>> > Wow you are making very good progress!
>>>>> >
>>>>> > We have our weekly status meetup tomorrow (see [1] for the time in
>>>>> > your timezone), feel free to join, meet other project members and
>>>>> > learn what the project is currently doing next to the Summer of Code.
>>>>> >
>>>>> > I will also be around 1hr earlier to answer all your questions and
>>>>> > discuss our next steps.
>>>>> >
>>>>> >
>>>>> > [1]
>>>>> > http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>>> >
>>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika
>>>>> > <wa...@gmail.com> wrote:
>>>>> >> Hi Robert,
>>>>> >>
>>>>> >> Here is the current status of the checklist :)
>>>>> >>
>>>>> >>  - check out the active tasks api (linked on top of this mail) -
>>>>> >> (finished)
>>>>> >>  - a mockup showing some widgets and how they could look like -
>>>>> >> (started
>>>>> >> but not finished yet)
>>>>> >>  - code React tutorial & read about Flux - (finished)
>>>>> >>  - take a look how we are using React - (finished)
>>>>> >>  - create another menu item, called "Dashboard", try to answer the
>>>>> >> questions to route.js et al - (started but not finished yet)
>>>>> >>  - get familiar how we test our code - (finished)
>>>>> >>  - write an hello world / hello from dulanga component that is
>>>>> >> rendered into a screen when opening http://localhost:8000/dash or by
>>>>> >> clicking on "dashboard" in the sidebar - (started but not finished
>>>>> >> yet)
>>>>> >>
>>>>> >> I will do my best to complete all these by tomorrow. If I have any
>>>>> >> problem,
>>>>> >> I will trouble you as you wished yesterday :)
>>>>> >>
>>>>> >> Thank You
>>>>> >>
>>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd>
>>>>> >> wrote:
>>>>> >>
>>>>> >>> Hi Dulanga,
>>>>> >>>
>>>>> >>> we already talked on irc and you already talked to Alex regarding
>>>>> >>> features for our dashboard. That's great!
>>>>> >>>
>>>>> >>> Some topics will repeat in this mail, but I also would like the ML
>>>>> >>> to
>>>>> >>> follow our project and additionally add some more in-depth
>>>>> >>> informations.
>>>>> >>>
>>>>> >>> Recap & additons
>>>>> >>> =====
>>>>> >>>
>>>>> >>> As discussed we will work in an iterative approach and add widget
>>>>> >>> after widget so if we run out of time, we will have something to
>>>>> >>> deliver and don't have to throw everything away.
>>>>> >>>
>>>>> >>> Have you seen the "database" tab or the "config" tab in the sidebar
>>>>> >>> on the
>>>>> >>> left?
>>>>> >>>
>>>>> >>> Those are modules that we can hook into the Fauxton build, by
>>>>> >>> configuration. I think the idea is to create a tab "dashboard"
>>>>> >>> which
>>>>> >>> is the default one after opening Fauxton in the browser. So you
>>>>> >>> would
>>>>> >>> build the dashboard for Fauxton as part of Fauxton.
>>>>> >>>
>>>>> >>> Alex ideas so far:
>>>>> >>>
>>>>> >>> ```
>>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are
>>>>> >>> some
>>>>> >>> points about showing stats and log - forget these (: _stats isn't
>>>>> >>> available for
>>>>> >>>                    cluster iface and _log is removed. but recently
>>>>> >>> visited databases, active tasks and _users/_replicator quick
>>>>> >>> management is what could
>>>>> >>>                    be really handy.
>>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>>>>> >>> anymore after backporting some cloudant features
>>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>>>>> >>> believe you could make some builtin and leave a template one to let
>>>>> >>> the end users create
>>>>> >>>                    their own if they're able/would like to. in
>>>>> >>> future
>>>>> >>> these are could be fauxton plugins or something.
>>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a
>>>>> >>> hot
>>>>> >>> widget.
>>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with
>>>>> >>> that
>>>>> >>> (add custom widgets on build time) - the build is complicated, but
>>>>> >>> once explained
>>>>> >>>                            it should be easy
>>>>> >>> ```
>>>>> >>>
>>>>> >>> So we have "custom widgets", "cluster quick-management", " recently
>>>>> >>> visited databases",  "active tasks" and "_users/_replicator quick
>>>>> >>> management"
>>>>> >>>
>>>>> >>> I think two good widgets for starting are active tasks and recently
>>>>> >>> visited databases.
>>>>> >>>
>>>>> >>> For active tasks we have some nice docs:
>>>>> >>>
>>>>> >>>
>>>>> >>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>>>>> >>>
>>>>> >>> They have an own dedicated page in Fauxton (see
>>>>> >>> http://localhost:8000/#/activetasks) but a short quick condensed
>>>>> >>> list
>>>>> >>> is probably very interesting to users.
>>>>> >>>
>>>>> >>> For the recently visited databases we would have to store that
>>>>> >>> somewhere.
>>>>> >>>
>>>>> >>> If you want, you can take an existing page in Fauxton and just
>>>>> >>> modify
>>>>> >>> the markup for a design mockup how the widget view may look like.
>>>>> >>> But
>>>>> >>> feel also free to use pen/paper or other tools if you like that the
>>>>> >>> most.
>>>>> >>>
>>>>> >>> For the mango feature I am currently working on, I took the "edit
>>>>> >>> view" template on modified the markup using the Chrome inspector of
>>>>> >>> my
>>>>> >>> browser to collect some first feedback from the project members and
>>>>> >>> my
>>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>>>>> >>> functionality, but gives other folks a rough idea what my idea for
>>>>> >>> the
>>>>> >>> feature is.
>>>>> >>>
>>>>> >>> the framework and react
>>>>> >>>
>>>>> >>> As I already mentioned we are using React.js.
>>>>> >>>
>>>>> >>> It would be nice if you can finish the tutorial at
>>>>> >>>
>>>>> >>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>>>>> >>> until next friday by following the steps and writing that code.
>>>>> >>> After
>>>>> >>> that, read
>>>>> >>>
>>>>> >>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>>>>> >>> to get a first impression how the Flux pattern works that we are
>>>>> >>> using.
>>>>> >>>
>>>>> >>> After that (if you still have time left) take a look on a component
>>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>>>>> >>>
>>>>> >>> Please take a look how the data flows from the Components, using
>>>>> >>> the
>>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>>>>> >>> everything in the code with console.log to see how state changes
>>>>> >>> and
>>>>> >>> how the data flows.
>>>>> >>>
>>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>>>>> >>>
>>>>> >>>
>>>>> >>> If you still have time, just try to create another menu item,
>>>>> >>> called
>>>>> >>> "Dashboard". Take a look at:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>>>>> >>>
>>>>> >>> to get a first idea how to do that. Some background information:
>>>>> >>>
>>>>> >>> base.js - the starting point of our module. basic configuration is
>>>>> >>> done
>>>>> >>> here
>>>>> >>> Question: what is `base.js` used for in the case of the config
>>>>> >>> module?
>>>>> >>>
>>>>> >>> routes.js - takes care that functions injecting the view into the
>>>>> >>> layout are called depending on the url given
>>>>> >>> Question: What happens if I call `http:localhost:8000/_config` and
>>>>> >>> what happens if you remove the function `apiUrl`?
>>>>> >>>
>>>>> >>> views.js - contains our views - this file contains still a lot
>>>>> >>> backbone views, which we are currently migrating to react. maybe it
>>>>> >>> makes more sense to take a look at one of our react components:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>>>>> >>>
>>>>> >>> and how they are used currently (as we are migrating to react
>>>>> >>> currently):
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>>>>> >>>
>>>>> >>> The Objects are injected into the closures using AMD:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>>>>> >>>
>>>>> >>> assets folder:
>>>>> >>> contains our less which is compiled to css
>>>>> >>>
>>>>> >>> templates folder:
>>>>> >>> contains old backbone.js templates, you will not need them
>>>>> >>>
>>>>> >>> tests folder:
>>>>> >>> contains unit and integration tests, every PR must have unit tests
>>>>> >>> and
>>>>> >>> integration tests. If you never wrote tests, we will explain it to
>>>>> >>> you
>>>>> >>> - it is easy once you wrote your first few ones. Basically you are
>>>>> >>> testing each time that if you put something into a function, the
>>>>> >>> expected result happens. Or that if you take an action, a state has
>>>>> >>> changed.
>>>>> >>>
>>>>> >>> You can run the unit tests using `grunt test`
>>>>> >>>
>>>>> >>> Single tests are run by:
>>>>> >>>
>>>>> >>> ```
>>>>> >>> grunt test
>>>>> >>> --file="./app/addons/documents/tests/headerSpec.react.js"
>>>>> >>> ```
>>>>> >>>
>>>>> >>> or in the browser by test group:
>>>>> >>>
>>>>> >>> ```
>>>>> >>>
>>>>> >>>
>>>>> >>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>>>>> >>> ```
>>>>> >>>
>>>>> >>> (change path to your fauxton directory)
>>>>> >>>
>>>>> >>> The corresponding code is:
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>>>>> >>>
>>>>> >>> and these tests are a good example how to write a simple test for
>>>>> >>> the
>>>>> >>> hello world/hello from dulanga-component:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>>>>> >>>
>>>>> >>>
>>>>> >>> First steps:
>>>>> >>>
>>>>> >>> Create a module `dashboard` that gets displayed in the sidebar. The
>>>>> >>> route http://localhost:8000/dash will render a small React
>>>>> >>> component
>>>>> >>> that display "Hello World".
>>>>> >>>
>>>>> >>> If you click on the "Hello World" it ill change the content to:
>>>>> >>> "Hello
>>>>> >>> from Dulanga"
>>>>> >>>
>>>>> >>> While we will throw the small component away afterwards we will
>>>>> >>> build
>>>>> >>> upon the other code you created. If you have time left, add a test
>>>>> >>> that the component changes the content.
>>>>> >>>
>>>>> >>>
>>>>> >>> Meeting Wednesday:
>>>>> >>> Feel free to join us on our weekly couchdb meeting:
>>>>> >>>
>>>>> >>>
>>>>> >>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>>> >>>
>>>>> >>> I will be around at least one hour before so we can chat. Contact
>>>>> >>> me
>>>>> >>> if you would like to chat earlier/later. I am also around the other
>>>>> >>> days on IRC / the mailinglist and feel free to contact me in
>>>>> >>> #couchdb-dev at any time. If I am not around I will answer you once
>>>>> >>> I
>>>>> >>> got online again, as I read the backlog.
>>>>> >>>
>>>>> >>>
>>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
>>>>> >>>
>>>>> >>>  - check out the active tasks api (linked on top of this mail)
>>>>> >>>  - a mockup showing some widgets and how they could look like
>>>>> >>>  - code React tutorial & read about Flux
>>>>> >>>  - take a look how we are using React
>>>>> >>>  - create another menu item, called "Dashboard", try to answer the
>>>>> >>> questions to route.js et al
>>>>> >>>  - get familiar how we test our code
>>>>> >>>  - write an hello world / hello from dulanga component that is
>>>>> >>> rendered into a screen when opening http://localhost:8000/dash or
>>>>> >>> by
>>>>> >>> clicking on "dashboard" in the sidebar
>>>>> >>>
>>>>> >>> That was a lot of content and please don't feel discouraged if you
>>>>> >>> don't get that far until Wednesday. We will have to find a speed
>>>>> >>> which
>>>>> >>> is perfect for you and this time I tried to give enough
>>>>> >>> informations
>>>>> >>> that you are not blocked until Wednesday by waiting for next steps.
>>>>> >>> If
>>>>> >>> you are at the last step before Wednesday, drop me a line and I
>>>>> >>> will
>>>>> >>> prepare the next steps :)
>>>>> >>>
>>>>> >>> I know that you all have important exams, these are definitely more
>>>>> >>> important! Don't feel pressured by the amount of work / the amount
>>>>> >>> of
>>>>> >>> informations, getting good results in the exams should be your
>>>>> >>> first
>>>>> >>> priority.
>>>>> >>>
>>>>> >>> Best,
>>>>> >>> Robert
>>>>> >>>
>>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika
>>>>> >>> <wa...@gmail.com>
>>>>> >>> wrote:
>>>>> >>> > Hi Robert,
>>>>> >>> >
>>>>> >>> > I went through the guidelines you provided and successfully
>>>>> >>> > installed and
>>>>> >>> > configured as you said. Everything works find and I played around
>>>>> >>> > it by
>>>>> >>> > creating a database and documents. I think I am ready for the
>>>>> >>> > next step
>>>>> >>> and
>>>>> >>> > we can start it if you are ok :)
>>>>> >>> >
>>>>> >>> > Thank You
>>>>> >>> >
>>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski
>>>>> >>> > <ro...@kowalski.gd>
>>>>> >>> wrote:
>>>>> >>> >
>>>>> >>> >> You're welcome.
>>>>> >>> >>
>>>>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if
>>>>> >>> >> you get
>>>>> >>> >> stuck!
>>>>> >>> >>
>>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika
>>>>> >>> >> <wa...@gmail.com>
>>>>> >>> >> wrote:
>>>>> >>> >> > Hi Robert,
>>>>> >>> >> >
>>>>> >>> >> > Thank you very much for the quick reply. I will go through the
>>>>> >>> guidelines
>>>>> >>> >> > and contact you if I have any issue with them.
>>>>> >>> >> >
>>>>> >>> >> > Thank you
>>>>> >>> >> >
>>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski
>>>>> >>> >> > <ro...@kowalski.gd>
>>>>> >>> >> wrote:
>>>>> >>> >> >
>>>>> >>> >> >> Hi Dulanga,
>>>>> >>> >> >>
>>>>> >>> >> >> glad you found your way to the CouchDB mailing list. Welcome
>>>>> >>> >> >> :)
>>>>> >>> >> >>
>>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API -
>>>>> >>> >> >> that makes
>>>>> >>> >> >> it a great fit for web applications that don't need a server
>>>>> >>> >> >> side
>>>>> >>> >> >> layer with a database driver in between. Our Project Fauxton
>>>>> >>> >> >> (like a
>>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>>>>> >>> >> >>
>>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
>>>>> >>> >> >> myself.
>>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
>>>>> >>> >> >> online (e.g.
>>>>> >>> I
>>>>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
>>>>> >>> >> >>
>>>>> >>> >> >> We are all happy to help each other in the project :)
>>>>> >>> >> >>
>>>>> >>> >> >> If you are using windows: I am not a Windows expert - you
>>>>> >>> >> >> will
>>>>> >>> >> >> probably have to use a bash emulator like "git bash" to boot
>>>>> >>> >> >> the dev
>>>>> >>> >> >> environment.
>>>>> >>> >> >>
>>>>> >>> >> >> Getting started:
>>>>> >>> >> >>
>>>>> >>> >> >> For this project you will need to install at least CouchDB
>>>>> >>> >> >> 1.x, an
>>>>> >>> >> >> Ubuntu package (with installation instructions) is at
>>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>>>>> >>> >> >>
>>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
>>>>> >>> >> >> (install from
>>>>> >>> >> >> https://nodejs.org)
>>>>> >>> >> >>
>>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
>>>>> >>> >> >>
>>>>> >>> >> >> booting CouchDB:
>>>>> >>> >> >> $ sudo couchdb
>>>>> >>> >> >>
>>>>> >>> >> >> in another terminal, clone the admin interface:
>>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>>>>> >>> >> >>
>>>>> >>> >> >> go to Fauxton:
>>>>> >>> >> >> $ cd couchdb-fauxton
>>>>> >>> >> >>
>>>>> >>> >> >> install dependencies:
>>>>> >>> >> >> $ npm install
>>>>> >>> >> >> $ npm install -g grunt grunt-cli
>>>>> >>> >> >>
>>>>> >>> >> >> boot the app:
>>>>> >>> >> >> $ grunt dev
>>>>> >>> >> >>
>>>>> >>> >> >> Then open your browser and go to http://localhost:8000 - you
>>>>> >>> >> >> should
>>>>> >>> >> >> see a red/gray/black interface
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >> That was a lot of input and especially if you are using Linux
>>>>> >>> >> >> the
>>>>> >>> >> >> first time and followed the instructions you have archived a
>>>>> >>> >> >> lot!
>>>>> >>> >> >>
>>>>> >>> >> >> As first step, try to create a database and a document now
>>>>> >>> >> >> using the
>>>>> >>> >> >> web interface (PS we are happy about any usability feedback).
>>>>> >>> >> >> :)
>>>>> >>> >> >>
>>>>> >>> >> >> I think you have your dev environment for CouchDB ready now.
>>>>> >>> >> >>
>>>>> >>> >> >> What's next:
>>>>> >>> >> >> If everything works we will take a look at Fauxtons code
>>>>> >>> >> >> structure
>>>>> >>> and
>>>>> >>> >> >> how it works. We will also talk about the features of the
>>>>> >>> >> >> dashboard.
>>>>> >>> >> >> Let's find a date for a chat after you took a first look how
>>>>> >>> >> >> Fauxton
>>>>> >>> >> >> looks like.
>>>>> >>> >> >>
>>>>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on
>>>>> >>> >> >> freenode
>>>>> >>> >> >> (see
>>>>> >>> >> >>
>>>>> >>> >>
>>>>> >>>
>>>>> >>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>>> >>> >> >> )
>>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if you
>>>>> >>> >> >> want to
>>>>> >>> >> >> chat with me before.
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >> Looking forward to work with you,
>>>>> >>> >> >> Robert
>>>>> >>> >> >>
>>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>>>>> >>> wadsashika@gmail.com>
>>>>> >>> >> >> wrote:
>>>>> >>> >> >> > Hi all,
>>>>> >>> >> >> >
>>>>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
>>>>> >>> >> >> > student at
>>>>> >>> >> >> > Computer Science and Engineering department at University
>>>>> >>> >> >> > of
>>>>> >>> Moratuwa,
>>>>> >>> >> >> Sri
>>>>> >>> >> >> > Lanka. I am really interested in java, java script, web
>>>>> >>> applications,
>>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
>>>>> >>> >> >> > months of
>>>>> >>> >> training
>>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a
>>>>> >>> >> >> > web
>>>>> >>> >> >> application
>>>>> >>> >> >> > that used java, JEE and Spring Framework. My final year
>>>>> >>> >> >> > project
>>>>> >>> also a
>>>>> >>> >> >> web
>>>>> >>> >> >> > related application and I used same technologies I
>>>>> >>> >> >> > mentioned above
>>>>> >>> for
>>>>> >>> >> >> > that. I am really interested in this project because I have
>>>>> >>> >> >> > a good
>>>>> >>> >> >> > experience with web applications and I love work with
>>>>> >>> >> >> > javascript.
>>>>> >>> I am
>>>>> >>> >> >> > looking forward to contribute to this project in this
>>>>> >>> >> >> > summer. I
>>>>> >>> like
>>>>> >>> >> to
>>>>> >>> >> >> > know more detail about this project and if you can, please
>>>>> >>> >> >> > guide
>>>>> >>> me to
>>>>> >>> >> >> > start working on this project.
>>>>> >>> >> >> >
>>>>> >>> >> >> > Thank you.
>>>>> >>> >> >> >
>>>>> >>> >> >> > W. A. Dulanga Sashika,
>>>>> >>> >> >> > Undergraduate Student,
>>>>> >>> >> >> > Department of Computer Science and Engineering,
>>>>> >>> >> >> > University of Moratuwa.
>>>>> >>> >> >>
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> > --
>>>>> >>> >> > W. A. Dulanga Sashika,
>>>>> >>> >> > Undergraduate Student,
>>>>> >>> >> > Department of Computer Science and Engineering,
>>>>> >>> >> > University of Moratuwa.
>>>>> >>> >>
>>>>> >>> >
>>>>> >>> >
>>>>> >>> >
>>>>> >>> > --
>>>>> >>> > W. A. Dulanga Sashika,
>>>>> >>> > Undergraduate Student,
>>>>> >>> > Department of Computer Science and Engineering,
>>>>> >>> > University of Moratuwa.
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> W. A. Dulanga Sashika,
>>>>> >> Undergraduate Student,
>>>>> >> Department of Computer Science and Engineering,
>>>>> >> University of Moratuwa.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> W. A. Dulanga Sashika,
>>>> Undergraduate Student,
>>>> Department of Computer Science and Engineering,
>>>> University of Moratuwa.
>>>
>>>
>>>
>>>
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi,
Here I attached the screen shots of Dashboard menu item. Now its working.
Now I want to know that, if I need to implement react component, where
should I put it? And how can I access that to render the view? just give me
some hints and I can carry on from there.

Regards

On Thu, Mar 19, 2015 at 10:15 PM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Hey Robert, problem solved.. :)
>
>
> Regards.
>
> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
>> Hi Robert,
>>
>> Now I am trying to create a new menu item for dashboard and implement a
>> react component as you said. But now I am stuck in some place and couldn't
>> figure out the problem yet. Here is the problem I had in process. I added
>> dashboard menu item and added route and view for that. And i change the
>> code to render dashboard when we enter http://localhost:8000 . As in
>> img1 and img2, it doesn't show the view I created. But when I click on
>> another menu item and come back to the dashboard, it shows the breadcrumb
>> of previous pages as img 3 and 4. As in
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
>> , I called the new Dashboard.view() which is a component in my view.js. But
>> in the console, it shows Uncaught Type error. Did I miss any configuration
>> thing or did I do it wrong?
>>
>> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>>
>>> Hi Robert,
>>>
>>> Thank you very much for the reference. I started to write the proposal
>>> today. I hope you will help to write this proposal by reviewing  it. I will
>>> share it with you after complete the draft of the proposal.
>>>
>>> Thank you
>>>
>>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd>
>>> wrote:
>>>
>>>> Some of you asked for a template for their proposals, here is what I've
>>>> found:
>>>>
>>>> http://community.staging.apache.org/gsoc#application-template
>>>>
>>>> Best,
>>>> Robert
>>>>
>>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
>>>> wrote:
>>>> > Wow you are making very good progress!
>>>> >
>>>> > We have our weekly status meetup tomorrow (see [1] for the time in
>>>> > your timezone), feel free to join, meet other project members and
>>>> > learn what the project is currently doing next to the Summer of Code.
>>>> >
>>>> > I will also be around 1hr earlier to answer all your questions and
>>>> > discuss our next steps.
>>>> >
>>>> >
>>>> > [1]
>>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>> >
>>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <
>>>> wadsashika@gmail.com> wrote:
>>>> >> Hi Robert,
>>>> >>
>>>> >> Here is the current status of the checklist :)
>>>> >>
>>>> >>  - check out the active tasks api (linked on top of this mail) -
>>>> (finished)
>>>> >>  - a mockup showing some widgets and how they could look like -
>>>> (started
>>>> >> but not finished yet)
>>>> >>  - code React tutorial & read about Flux - (finished)
>>>> >>  - take a look how we are using React - (finished)
>>>> >>  - create another menu item, called "Dashboard", try to answer the
>>>> >> questions to route.js et al - (started but not finished yet)
>>>> >>  - get familiar how we test our code - (finished)
>>>> >>  - write an hello world / hello from dulanga component that is
>>>> >> rendered into a screen when opening http://localhost:8000/dash or by
>>>> >> clicking on "dashboard" in the sidebar - (started but not finished
>>>> yet)
>>>> >>
>>>> >> I will do my best to complete all these by tomorrow. If I have any
>>>> problem,
>>>> >> I will trouble you as you wished yesterday :)
>>>> >>
>>>> >> Thank You
>>>> >>
>>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd>
>>>> wrote:
>>>> >>
>>>> >>> Hi Dulanga,
>>>> >>>
>>>> >>> we already talked on irc and you already talked to Alex regarding
>>>> >>> features for our dashboard. That's great!
>>>> >>>
>>>> >>> Some topics will repeat in this mail, but I also would like the ML
>>>> to
>>>> >>> follow our project and additionally add some more in-depth
>>>> >>> informations.
>>>> >>>
>>>> >>> Recap & additons
>>>> >>> =====
>>>> >>>
>>>> >>> As discussed we will work in an iterative approach and add widget
>>>> >>> after widget so if we run out of time, we will have something to
>>>> >>> deliver and don't have to throw everything away.
>>>> >>>
>>>> >>> Have you seen the "database" tab or the "config" tab in the sidebar
>>>> on the
>>>> >>> left?
>>>> >>>
>>>> >>> Those are modules that we can hook into the Fauxton build, by
>>>> >>> configuration. I think the idea is to create a tab "dashboard" which
>>>> >>> is the default one after opening Fauxton in the browser. So you
>>>> would
>>>> >>> build the dashboard for Fauxton as part of Fauxton.
>>>> >>>
>>>> >>> Alex ideas so far:
>>>> >>>
>>>> >>> ```
>>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are
>>>> some
>>>> >>> points about showing stats and log - forget these (: _stats isn't
>>>> >>> available for
>>>> >>>                    cluster iface and _log is removed. but recently
>>>> >>> visited databases, active tasks and _users/_replicator quick
>>>> >>> management is what could
>>>> >>>                    be really handy.
>>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>>>> >>> anymore after backporting some cloudant features
>>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>>>> >>> believe you could make some builtin and leave a template one to let
>>>> >>> the end users create
>>>> >>>                    their own if they're able/would like to. in
>>>> future
>>>> >>> these are could be fauxton plugins or something.
>>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a
>>>> hot
>>>> >>> widget.
>>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with
>>>> that
>>>> >>> (add custom widgets on build time) - the build is complicated, but
>>>> >>> once explained
>>>> >>>                            it should be easy
>>>> >>> ```
>>>> >>>
>>>> >>> So we have "custom widgets", "cluster quick-management", " recently
>>>> >>> visited databases",  "active tasks" and "_users/_replicator quick
>>>> >>> management"
>>>> >>>
>>>> >>> I think two good widgets for starting are active tasks and recently
>>>> >>> visited databases.
>>>> >>>
>>>> >>> For active tasks we have some nice docs:
>>>> >>>
>>>> >>>
>>>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>>>> >>>
>>>> >>> They have an own dedicated page in Fauxton (see
>>>> >>> http://localhost:8000/#/activetasks) but a short quick condensed
>>>> list
>>>> >>> is probably very interesting to users.
>>>> >>>
>>>> >>> For the recently visited databases we would have to store that
>>>> somewhere.
>>>> >>>
>>>> >>> If you want, you can take an existing page in Fauxton and just
>>>> modify
>>>> >>> the markup for a design mockup how the widget view may look like.
>>>> But
>>>> >>> feel also free to use pen/paper or other tools if you like that the
>>>> >>> most.
>>>> >>>
>>>> >>> For the mango feature I am currently working on, I took the "edit
>>>> >>> view" template on modified the markup using the Chrome inspector of
>>>> my
>>>> >>> browser to collect some first feedback from the project members and
>>>> my
>>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>>>> >>> functionality, but gives other folks a rough idea what my idea for
>>>> the
>>>> >>> feature is.
>>>> >>>
>>>> >>> the framework and react
>>>> >>>
>>>> >>> As I already mentioned we are using React.js.
>>>> >>>
>>>> >>> It would be nice if you can finish the tutorial at
>>>> >>>
>>>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>>>> >>> until next friday by following the steps and writing that code.
>>>> After
>>>> >>> that, read
>>>> >>>
>>>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>>>> >>> to get a first impression how the Flux pattern works that we are
>>>> >>> using.
>>>> >>>
>>>> >>> After that (if you still have time left) take a look on a component
>>>> >>> that Garren, my coworker refactored from Backbone.js to React:
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>>>> >>>
>>>> >>> Please take a look how the data flows from the Components, using the
>>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>>>> >>> everything in the code with console.log to see how state changes and
>>>> >>> how the data flows.
>>>> >>>
>>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>>>> >>>
>>>> >>>
>>>> >>> If you still have time, just try to create another menu item, called
>>>> >>> "Dashboard". Take a look at:
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>>>> >>>
>>>> >>> to get a first idea how to do that. Some background information:
>>>> >>>
>>>> >>> base.js - the starting point of our module. basic configuration is
>>>> done
>>>> >>> here
>>>> >>> Question: what is `base.js` used for in the case of the config
>>>> module?
>>>> >>>
>>>> >>> routes.js - takes care that functions injecting the view into the
>>>> >>> layout are called depending on the url given
>>>> >>> Question: What happens if I call `http:localhost:8000/_config` and
>>>> >>> what happens if you remove the function `apiUrl`?
>>>> >>>
>>>> >>> views.js - contains our views - this file contains still a lot
>>>> >>> backbone views, which we are currently migrating to react. maybe it
>>>> >>> makes more sense to take a look at one of our react components:
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>>>> >>>
>>>> >>> and how they are used currently (as we are migrating to react
>>>> currently):
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>>>> >>>
>>>> >>> The Objects are injected into the closures using AMD:
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>>>> >>>
>>>> >>> assets folder:
>>>> >>> contains our less which is compiled to css
>>>> >>>
>>>> >>> templates folder:
>>>> >>> contains old backbone.js templates, you will not need them
>>>> >>>
>>>> >>> tests folder:
>>>> >>> contains unit and integration tests, every PR must have unit tests
>>>> and
>>>> >>> integration tests. If you never wrote tests, we will explain it to
>>>> you
>>>> >>> - it is easy once you wrote your first few ones. Basically you are
>>>> >>> testing each time that if you put something into a function, the
>>>> >>> expected result happens. Or that if you take an action, a state has
>>>> >>> changed.
>>>> >>>
>>>> >>> You can run the unit tests using `grunt test`
>>>> >>>
>>>> >>> Single tests are run by:
>>>> >>>
>>>> >>> ```
>>>> >>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
>>>> >>> ```
>>>> >>>
>>>> >>> or in the browser by test group:
>>>> >>>
>>>> >>> ```
>>>> >>>
>>>> >>>
>>>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>>>> >>> ```
>>>> >>>
>>>> >>> (change path to your fauxton directory)
>>>> >>>
>>>> >>> The corresponding code is:
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>>>> >>>
>>>> >>> and these tests are a good example how to write a simple test for
>>>> the
>>>> >>> hello world/hello from dulanga-component:
>>>> >>>
>>>> >>>
>>>> >>>
>>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>>>> >>>
>>>> >>>
>>>> >>> First steps:
>>>> >>>
>>>> >>> Create a module `dashboard` that gets displayed in the sidebar. The
>>>> >>> route http://localhost:8000/dash will render a small React
>>>> component
>>>> >>> that display "Hello World".
>>>> >>>
>>>> >>> If you click on the "Hello World" it ill change the content to:
>>>> "Hello
>>>> >>> from Dulanga"
>>>> >>>
>>>> >>> While we will throw the small component away afterwards we will
>>>> build
>>>> >>> upon the other code you created. If you have time left, add a test
>>>> >>> that the component changes the content.
>>>> >>>
>>>> >>>
>>>> >>> Meeting Wednesday:
>>>> >>> Feel free to join us on our weekly couchdb meeting:
>>>> >>>
>>>> >>>
>>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>> >>>
>>>> >>> I will be around at least one hour before so we can chat. Contact me
>>>> >>> if you would like to chat earlier/later. I am also around the other
>>>> >>> days on IRC / the mailinglist and feel free to contact me in
>>>> >>> #couchdb-dev at any time. If I am not around I will answer you once
>>>> I
>>>> >>> got online again, as I read the backlog.
>>>> >>>
>>>> >>>
>>>> >>> Our checklist at Wednesday (lets see how far we'll get)
>>>> >>>
>>>> >>>  - check out the active tasks api (linked on top of this mail)
>>>> >>>  - a mockup showing some widgets and how they could look like
>>>> >>>  - code React tutorial & read about Flux
>>>> >>>  - take a look how we are using React
>>>> >>>  - create another menu item, called "Dashboard", try to answer the
>>>> >>> questions to route.js et al
>>>> >>>  - get familiar how we test our code
>>>> >>>  - write an hello world / hello from dulanga component that is
>>>> >>> rendered into a screen when opening http://localhost:8000/dash or
>>>> by
>>>> >>> clicking on "dashboard" in the sidebar
>>>> >>>
>>>> >>> That was a lot of content and please don't feel discouraged if you
>>>> >>> don't get that far until Wednesday. We will have to find a speed
>>>> which
>>>> >>> is perfect for you and this time I tried to give enough informations
>>>> >>> that you are not blocked until Wednesday by waiting for next steps.
>>>> If
>>>> >>> you are at the last step before Wednesday, drop me a line and I will
>>>> >>> prepare the next steps :)
>>>> >>>
>>>> >>> I know that you all have important exams, these are definitely more
>>>> >>> important! Don't feel pressured by the amount of work / the amount
>>>> of
>>>> >>> informations, getting good results in the exams should be your first
>>>> >>> priority.
>>>> >>>
>>>> >>> Best,
>>>> >>> Robert
>>>> >>>
>>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <
>>>> wadsashika@gmail.com>
>>>> >>> wrote:
>>>> >>> > Hi Robert,
>>>> >>> >
>>>> >>> > I went through the guidelines you provided and successfully
>>>> installed and
>>>> >>> > configured as you said. Everything works find and I played around
>>>> it by
>>>> >>> > creating a database and documents. I think I am ready for the
>>>> next step
>>>> >>> and
>>>> >>> > we can start it if you are ok :)
>>>> >>> >
>>>> >>> > Thank You
>>>> >>> >
>>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <
>>>> rok@kowalski.gd>
>>>> >>> wrote:
>>>> >>> >
>>>> >>> >> You're welcome.
>>>> >>> >>
>>>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if
>>>> you get
>>>> >>> >> stuck!
>>>> >>> >>
>>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <
>>>> wadsashika@gmail.com>
>>>> >>> >> wrote:
>>>> >>> >> > Hi Robert,
>>>> >>> >> >
>>>> >>> >> > Thank you very much for the quick reply. I will go through the
>>>> >>> guidelines
>>>> >>> >> > and contact you if I have any issue with them.
>>>> >>> >> >
>>>> >>> >> > Thank you
>>>> >>> >> >
>>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <
>>>> rok@kowalski.gd>
>>>> >>> >> wrote:
>>>> >>> >> >
>>>> >>> >> >> Hi Dulanga,
>>>> >>> >> >>
>>>> >>> >> >> glad you found your way to the CouchDB mailing list. Welcome
>>>> :)
>>>> >>> >> >>
>>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API -
>>>> that makes
>>>> >>> >> >> it a great fit for web applications that don't need a server
>>>> side
>>>> >>> >> >> layer with a database driver in between. Our Project Fauxton
>>>> (like a
>>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>>>> >>> >> >>
>>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
>>>> myself.
>>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is
>>>> online (e.g.
>>>> >>> I
>>>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
>>>> >>> >> >>
>>>> >>> >> >> We are all happy to help each other in the project :)
>>>> >>> >> >>
>>>> >>> >> >> If you are using windows: I am not a Windows expert - you will
>>>> >>> >> >> probably have to use a bash emulator like "git bash" to boot
>>>> the dev
>>>> >>> >> >> environment.
>>>> >>> >> >>
>>>> >>> >> >> Getting started:
>>>> >>> >> >>
>>>> >>> >> >> For this project you will need to install at least CouchDB
>>>> 1.x, an
>>>> >>> >> >> Ubuntu package (with installation instructions) is at
>>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>>>> >>> >> >>
>>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12
>>>> (install from
>>>> >>> >> >> https://nodejs.org)
>>>> >>> >> >>
>>>> >>> >> >> Booting Fauxton and first steps (type without the $):
>>>> >>> >> >>
>>>> >>> >> >> booting CouchDB:
>>>> >>> >> >> $ sudo couchdb
>>>> >>> >> >>
>>>> >>> >> >> in another terminal, clone the admin interface:
>>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>>>> >>> >> >>
>>>> >>> >> >> go to Fauxton:
>>>> >>> >> >> $ cd couchdb-fauxton
>>>> >>> >> >>
>>>> >>> >> >> install dependencies:
>>>> >>> >> >> $ npm install
>>>> >>> >> >> $ npm install -g grunt grunt-cli
>>>> >>> >> >>
>>>> >>> >> >> boot the app:
>>>> >>> >> >> $ grunt dev
>>>> >>> >> >>
>>>> >>> >> >> Then open your browser and go to http://localhost:8000 - you
>>>> should
>>>> >>> >> >> see a red/gray/black interface
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >> That was a lot of input and especially if you are using Linux
>>>> the
>>>> >>> >> >> first time and followed the instructions you have archived a
>>>> lot!
>>>> >>> >> >>
>>>> >>> >> >> As first step, try to create a database and a document now
>>>> using the
>>>> >>> >> >> web interface (PS we are happy about any usability feedback).
>>>> :)
>>>> >>> >> >>
>>>> >>> >> >> I think you have your dev environment for CouchDB ready now.
>>>> >>> >> >>
>>>> >>> >> >> What's next:
>>>> >>> >> >> If everything works we will take a look at Fauxtons code
>>>> structure
>>>> >>> and
>>>> >>> >> >> how it works. We will also talk about the features of the
>>>> dashboard.
>>>> >>> >> >> Let's find a date for a chat after you took a first look how
>>>> Fauxton
>>>> >>> >> >> looks like.
>>>> >>> >> >>
>>>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on
>>>> freenode
>>>> >>> >> >> (see
>>>> >>> >> >>
>>>> >>> >>
>>>> >>>
>>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>> >>> >> >> )
>>>> >>> >> >> . Feel free to join us! I will be around 1hr before if you
>>>> want to
>>>> >>> >> >> chat with me before.
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >> Looking forward to work with you,
>>>> >>> >> >> Robert
>>>> >>> >> >>
>>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>>>> >>> wadsashika@gmail.com>
>>>> >>> >> >> wrote:
>>>> >>> >> >> > Hi all,
>>>> >>> >> >> >
>>>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
>>>> student at
>>>> >>> >> >> > Computer Science and Engineering department at University of
>>>> >>> Moratuwa,
>>>> >>> >> >> Sri
>>>> >>> >> >> > Lanka. I am really interested in java, java script, web
>>>> >>> applications,
>>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
>>>> months of
>>>> >>> >> training
>>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a
>>>> web
>>>> >>> >> >> application
>>>> >>> >> >> > that used java, JEE and Spring Framework. My final year
>>>> project
>>>> >>> also a
>>>> >>> >> >> web
>>>> >>> >> >> > related application and I used same technologies I
>>>> mentioned above
>>>> >>> for
>>>> >>> >> >> > that. I am really interested in this project because I have
>>>> a good
>>>> >>> >> >> > experience with web applications and I love work with
>>>> javascript.
>>>> >>> I am
>>>> >>> >> >> > looking forward to contribute to this project in this
>>>> summer. I
>>>> >>> like
>>>> >>> >> to
>>>> >>> >> >> > know more detail about this project and if you can, please
>>>> guide
>>>> >>> me to
>>>> >>> >> >> > start working on this project.
>>>> >>> >> >> >
>>>> >>> >> >> > Thank you.
>>>> >>> >> >> >
>>>> >>> >> >> > W. A. Dulanga Sashika,
>>>> >>> >> >> > Undergraduate Student,
>>>> >>> >> >> > Department of Computer Science and Engineering,
>>>> >>> >> >> > University of Moratuwa.
>>>> >>> >> >>
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> > --
>>>> >>> >> > W. A. Dulanga Sashika,
>>>> >>> >> > Undergraduate Student,
>>>> >>> >> > Department of Computer Science and Engineering,
>>>> >>> >> > University of Moratuwa.
>>>> >>> >>
>>>> >>> >
>>>> >>> >
>>>> >>> >
>>>> >>> > --
>>>> >>> > W. A. Dulanga Sashika,
>>>> >>> > Undergraduate Student,
>>>> >>> > Department of Computer Science and Engineering,
>>>> >>> > University of Moratuwa.
>>>> >>>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> W. A. Dulanga Sashika,
>>>> >> Undergraduate Student,
>>>> >> Department of Computer Science and Engineering,
>>>> >> University of Moratuwa.
>>>>
>>>
>>>
>>>
>>> --
>>> W. A. Dulanga Sashika,
>>> Undergraduate Student,
>>> Department of Computer Science and Engineering,
>>> University of Moratuwa.
>>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hey Robert, problem solved.. :)


Regards.

On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Hi Robert,
>
> Now I am trying to create a new menu item for dashboard and implement a
> react component as you said. But now I am stuck in some place and couldn't
> figure out the problem yet. Here is the problem I had in process. I added
> dashboard menu item and added route and view for that. And i change the
> code to render dashboard when we enter http://localhost:8000 . As in img1
> and img2, it doesn't show the view I created. But when I click on another
> menu item and come back to the dashboard, it shows the breadcrumb of
> previous pages as img 3 and 4. As in
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
> , I called the new Dashboard.view() which is a component in my view.js. But
> in the console, it shows Uncaught Type error. Did I miss any configuration
> thing or did I do it wrong?
>
> On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
>
>> Hi Robert,
>>
>> Thank you very much for the reference. I started to write the proposal
>> today. I hope you will help to write this proposal by reviewing  it. I will
>> share it with you after complete the draft of the proposal.
>>
>> Thank you
>>
>> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>
>>> Some of you asked for a template for their proposals, here is what I've
>>> found:
>>>
>>> http://community.staging.apache.org/gsoc#application-template
>>>
>>> Best,
>>> Robert
>>>
>>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
>>> wrote:
>>> > Wow you are making very good progress!
>>> >
>>> > We have our weekly status meetup tomorrow (see [1] for the time in
>>> > your timezone), feel free to join, meet other project members and
>>> > learn what the project is currently doing next to the Summer of Code.
>>> >
>>> > I will also be around 1hr earlier to answer all your questions and
>>> > discuss our next steps.
>>> >
>>> >
>>> > [1]
>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>> >
>>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> >> Hi Robert,
>>> >>
>>> >> Here is the current status of the checklist :)
>>> >>
>>> >>  - check out the active tasks api (linked on top of this mail) -
>>> (finished)
>>> >>  - a mockup showing some widgets and how they could look like -
>>> (started
>>> >> but not finished yet)
>>> >>  - code React tutorial & read about Flux - (finished)
>>> >>  - take a look how we are using React - (finished)
>>> >>  - create another menu item, called "Dashboard", try to answer the
>>> >> questions to route.js et al - (started but not finished yet)
>>> >>  - get familiar how we test our code - (finished)
>>> >>  - write an hello world / hello from dulanga component that is
>>> >> rendered into a screen when opening http://localhost:8000/dash or by
>>> >> clicking on "dashboard" in the sidebar - (started but not finished
>>> yet)
>>> >>
>>> >> I will do my best to complete all these by tomorrow. If I have any
>>> problem,
>>> >> I will trouble you as you wished yesterday :)
>>> >>
>>> >> Thank You
>>> >>
>>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd>
>>> wrote:
>>> >>
>>> >>> Hi Dulanga,
>>> >>>
>>> >>> we already talked on irc and you already talked to Alex regarding
>>> >>> features for our dashboard. That's great!
>>> >>>
>>> >>> Some topics will repeat in this mail, but I also would like the ML to
>>> >>> follow our project and additionally add some more in-depth
>>> >>> informations.
>>> >>>
>>> >>> Recap & additons
>>> >>> =====
>>> >>>
>>> >>> As discussed we will work in an iterative approach and add widget
>>> >>> after widget so if we run out of time, we will have something to
>>> >>> deliver and don't have to throw everything away.
>>> >>>
>>> >>> Have you seen the "database" tab or the "config" tab in the sidebar
>>> on the
>>> >>> left?
>>> >>>
>>> >>> Those are modules that we can hook into the Fauxton build, by
>>> >>> configuration. I think the idea is to create a tab "dashboard" which
>>> >>> is the default one after opening Fauxton in the browser. So you would
>>> >>> build the dashboard for Fauxton as part of Fauxton.
>>> >>>
>>> >>> Alex ideas so far:
>>> >>>
>>> >>> ```
>>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are some
>>> >>> points about showing stats and log - forget these (: _stats isn't
>>> >>> available for
>>> >>>                    cluster iface and _log is removed. but recently
>>> >>> visited databases, active tasks and _users/_replicator quick
>>> >>> management is what could
>>> >>>                    be really handy.
>>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>>> >>> anymore after backporting some cloudant features
>>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>>> >>> believe you could make some builtin and leave a template one to let
>>> >>> the end users create
>>> >>>                    their own if they're able/would like to. in future
>>> >>> these are could be fauxton plugins or something.
>>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a
>>> hot
>>> >>> widget.
>>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with
>>> that
>>> >>> (add custom widgets on build time) - the build is complicated, but
>>> >>> once explained
>>> >>>                            it should be easy
>>> >>> ```
>>> >>>
>>> >>> So we have "custom widgets", "cluster quick-management", " recently
>>> >>> visited databases",  "active tasks" and "_users/_replicator quick
>>> >>> management"
>>> >>>
>>> >>> I think two good widgets for starting are active tasks and recently
>>> >>> visited databases.
>>> >>>
>>> >>> For active tasks we have some nice docs:
>>> >>>
>>> >>>
>>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>>> >>>
>>> >>> They have an own dedicated page in Fauxton (see
>>> >>> http://localhost:8000/#/activetasks) but a short quick condensed
>>> list
>>> >>> is probably very interesting to users.
>>> >>>
>>> >>> For the recently visited databases we would have to store that
>>> somewhere.
>>> >>>
>>> >>> If you want, you can take an existing page in Fauxton and just modify
>>> >>> the markup for a design mockup how the widget view may look like. But
>>> >>> feel also free to use pen/paper or other tools if you like that the
>>> >>> most.
>>> >>>
>>> >>> For the mango feature I am currently working on, I took the "edit
>>> >>> view" template on modified the markup using the Chrome inspector of
>>> my
>>> >>> browser to collect some first feedback from the project members and
>>> my
>>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>>> >>> functionality, but gives other folks a rough idea what my idea for
>>> the
>>> >>> feature is.
>>> >>>
>>> >>> the framework and react
>>> >>>
>>> >>> As I already mentioned we are using React.js.
>>> >>>
>>> >>> It would be nice if you can finish the tutorial at
>>> >>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>>> >>> until next friday by following the steps and writing that code. After
>>> >>> that, read
>>> >>>
>>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>>> >>> to get a first impression how the Flux pattern works that we are
>>> >>> using.
>>> >>>
>>> >>> After that (if you still have time left) take a look on a component
>>> >>> that Garren, my coworker refactored from Backbone.js to React:
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>>> >>>
>>> >>> Please take a look how the data flows from the Components, using the
>>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>>> >>> everything in the code with console.log to see how state changes and
>>> >>> how the data flows.
>>> >>>
>>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>>> >>>
>>> >>>
>>> >>> If you still have time, just try to create another menu item, called
>>> >>> "Dashboard". Take a look at:
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>>> >>>
>>> >>> to get a first idea how to do that. Some background information:
>>> >>>
>>> >>> base.js - the starting point of our module. basic configuration is
>>> done
>>> >>> here
>>> >>> Question: what is `base.js` used for in the case of the config
>>> module?
>>> >>>
>>> >>> routes.js - takes care that functions injecting the view into the
>>> >>> layout are called depending on the url given
>>> >>> Question: What happens if I call `http:localhost:8000/_config` and
>>> >>> what happens if you remove the function `apiUrl`?
>>> >>>
>>> >>> views.js - contains our views - this file contains still a lot
>>> >>> backbone views, which we are currently migrating to react. maybe it
>>> >>> makes more sense to take a look at one of our react components:
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>>> >>>
>>> >>> and how they are used currently (as we are migrating to react
>>> currently):
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>>> >>>
>>> >>> The Objects are injected into the closures using AMD:
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>>> >>>
>>> >>> assets folder:
>>> >>> contains our less which is compiled to css
>>> >>>
>>> >>> templates folder:
>>> >>> contains old backbone.js templates, you will not need them
>>> >>>
>>> >>> tests folder:
>>> >>> contains unit and integration tests, every PR must have unit tests
>>> and
>>> >>> integration tests. If you never wrote tests, we will explain it to
>>> you
>>> >>> - it is easy once you wrote your first few ones. Basically you are
>>> >>> testing each time that if you put something into a function, the
>>> >>> expected result happens. Or that if you take an action, a state has
>>> >>> changed.
>>> >>>
>>> >>> You can run the unit tests using `grunt test`
>>> >>>
>>> >>> Single tests are run by:
>>> >>>
>>> >>> ```
>>> >>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
>>> >>> ```
>>> >>>
>>> >>> or in the browser by test group:
>>> >>>
>>> >>> ```
>>> >>>
>>> >>>
>>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>>> >>> ```
>>> >>>
>>> >>> (change path to your fauxton directory)
>>> >>>
>>> >>> The corresponding code is:
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>>> >>>
>>> >>> and these tests are a good example how to write a simple test for the
>>> >>> hello world/hello from dulanga-component:
>>> >>>
>>> >>>
>>> >>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>>> >>>
>>> >>>
>>> >>> First steps:
>>> >>>
>>> >>> Create a module `dashboard` that gets displayed in the sidebar. The
>>> >>> route http://localhost:8000/dash will render a small React component
>>> >>> that display "Hello World".
>>> >>>
>>> >>> If you click on the "Hello World" it ill change the content to:
>>> "Hello
>>> >>> from Dulanga"
>>> >>>
>>> >>> While we will throw the small component away afterwards we will build
>>> >>> upon the other code you created. If you have time left, add a test
>>> >>> that the component changes the content.
>>> >>>
>>> >>>
>>> >>> Meeting Wednesday:
>>> >>> Feel free to join us on our weekly couchdb meeting:
>>> >>>
>>> >>>
>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>> >>>
>>> >>> I will be around at least one hour before so we can chat. Contact me
>>> >>> if you would like to chat earlier/later. I am also around the other
>>> >>> days on IRC / the mailinglist and feel free to contact me in
>>> >>> #couchdb-dev at any time. If I am not around I will answer you once I
>>> >>> got online again, as I read the backlog.
>>> >>>
>>> >>>
>>> >>> Our checklist at Wednesday (lets see how far we'll get)
>>> >>>
>>> >>>  - check out the active tasks api (linked on top of this mail)
>>> >>>  - a mockup showing some widgets and how they could look like
>>> >>>  - code React tutorial & read about Flux
>>> >>>  - take a look how we are using React
>>> >>>  - create another menu item, called "Dashboard", try to answer the
>>> >>> questions to route.js et al
>>> >>>  - get familiar how we test our code
>>> >>>  - write an hello world / hello from dulanga component that is
>>> >>> rendered into a screen when opening http://localhost:8000/dash or by
>>> >>> clicking on "dashboard" in the sidebar
>>> >>>
>>> >>> That was a lot of content and please don't feel discouraged if you
>>> >>> don't get that far until Wednesday. We will have to find a speed
>>> which
>>> >>> is perfect for you and this time I tried to give enough informations
>>> >>> that you are not blocked until Wednesday by waiting for next steps.
>>> If
>>> >>> you are at the last step before Wednesday, drop me a line and I will
>>> >>> prepare the next steps :)
>>> >>>
>>> >>> I know that you all have important exams, these are definitely more
>>> >>> important! Don't feel pressured by the amount of work / the amount of
>>> >>> informations, getting good results in the exams should be your first
>>> >>> priority.
>>> >>>
>>> >>> Best,
>>> >>> Robert
>>> >>>
>>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <
>>> wadsashika@gmail.com>
>>> >>> wrote:
>>> >>> > Hi Robert,
>>> >>> >
>>> >>> > I went through the guidelines you provided and successfully
>>> installed and
>>> >>> > configured as you said. Everything works find and I played around
>>> it by
>>> >>> > creating a database and documents. I think I am ready for the next
>>> step
>>> >>> and
>>> >>> > we can start it if you are ok :)
>>> >>> >
>>> >>> > Thank You
>>> >>> >
>>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <rok@kowalski.gd
>>> >
>>> >>> wrote:
>>> >>> >
>>> >>> >> You're welcome.
>>> >>> >>
>>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if
>>> you get
>>> >>> >> stuck!
>>> >>> >>
>>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <
>>> wadsashika@gmail.com>
>>> >>> >> wrote:
>>> >>> >> > Hi Robert,
>>> >>> >> >
>>> >>> >> > Thank you very much for the quick reply. I will go through the
>>> >>> guidelines
>>> >>> >> > and contact you if I have any issue with them.
>>> >>> >> >
>>> >>> >> > Thank you
>>> >>> >> >
>>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <
>>> rok@kowalski.gd>
>>> >>> >> wrote:
>>> >>> >> >
>>> >>> >> >> Hi Dulanga,
>>> >>> >> >>
>>> >>> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
>>> >>> >> >>
>>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API -
>>> that makes
>>> >>> >> >> it a great fit for web applications that don't need a server
>>> side
>>> >>> >> >> layer with a database driver in between. Our Project Fauxton
>>> (like a
>>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>>> >>> >> >>
>>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
>>> myself.
>>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is online
>>> (e.g.
>>> >>> I
>>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
>>> >>> >> >>
>>> >>> >> >> We are all happy to help each other in the project :)
>>> >>> >> >>
>>> >>> >> >> If you are using windows: I am not a Windows expert - you will
>>> >>> >> >> probably have to use a bash emulator like "git bash" to boot
>>> the dev
>>> >>> >> >> environment.
>>> >>> >> >>
>>> >>> >> >> Getting started:
>>> >>> >> >>
>>> >>> >> >> For this project you will need to install at least CouchDB
>>> 1.x, an
>>> >>> >> >> Ubuntu package (with installation instructions) is at
>>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>>> >>> >> >>
>>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install
>>> from
>>> >>> >> >> https://nodejs.org)
>>> >>> >> >>
>>> >>> >> >> Booting Fauxton and first steps (type without the $):
>>> >>> >> >>
>>> >>> >> >> booting CouchDB:
>>> >>> >> >> $ sudo couchdb
>>> >>> >> >>
>>> >>> >> >> in another terminal, clone the admin interface:
>>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>>> >>> >> >>
>>> >>> >> >> go to Fauxton:
>>> >>> >> >> $ cd couchdb-fauxton
>>> >>> >> >>
>>> >>> >> >> install dependencies:
>>> >>> >> >> $ npm install
>>> >>> >> >> $ npm install -g grunt grunt-cli
>>> >>> >> >>
>>> >>> >> >> boot the app:
>>> >>> >> >> $ grunt dev
>>> >>> >> >>
>>> >>> >> >> Then open your browser and go to http://localhost:8000 - you
>>> should
>>> >>> >> >> see a red/gray/black interface
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >> That was a lot of input and especially if you are using Linux
>>> the
>>> >>> >> >> first time and followed the instructions you have archived a
>>> lot!
>>> >>> >> >>
>>> >>> >> >> As first step, try to create a database and a document now
>>> using the
>>> >>> >> >> web interface (PS we are happy about any usability feedback).
>>> :)
>>> >>> >> >>
>>> >>> >> >> I think you have your dev environment for CouchDB ready now.
>>> >>> >> >>
>>> >>> >> >> What's next:
>>> >>> >> >> If everything works we will take a look at Fauxtons code
>>> structure
>>> >>> and
>>> >>> >> >> how it works. We will also talk about the features of the
>>> dashboard.
>>> >>> >> >> Let's find a date for a chat after you took a first look how
>>> Fauxton
>>> >>> >> >> looks like.
>>> >>> >> >>
>>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on
>>> freenode
>>> >>> >> >> (see
>>> >>> >> >>
>>> >>> >>
>>> >>>
>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>> >>> >> >> )
>>> >>> >> >> . Feel free to join us! I will be around 1hr before if you
>>> want to
>>> >>> >> >> chat with me before.
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >> Looking forward to work with you,
>>> >>> >> >> Robert
>>> >>> >> >>
>>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>>> >>> wadsashika@gmail.com>
>>> >>> >> >> wrote:
>>> >>> >> >> > Hi all,
>>> >>> >> >> >
>>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
>>> student at
>>> >>> >> >> > Computer Science and Engineering department at University of
>>> >>> Moratuwa,
>>> >>> >> >> Sri
>>> >>> >> >> > Lanka. I am really interested in java, java script, web
>>> >>> applications,
>>> >>> >> >> > algorithms, data mining and machine learning. I have 6
>>> months of
>>> >>> >> training
>>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a
>>> web
>>> >>> >> >> application
>>> >>> >> >> > that used java, JEE and Spring Framework. My final year
>>> project
>>> >>> also a
>>> >>> >> >> web
>>> >>> >> >> > related application and I used same technologies I mentioned
>>> above
>>> >>> for
>>> >>> >> >> > that. I am really interested in this project because I have
>>> a good
>>> >>> >> >> > experience with web applications and I love work with
>>> javascript.
>>> >>> I am
>>> >>> >> >> > looking forward to contribute to this project in this
>>> summer. I
>>> >>> like
>>> >>> >> to
>>> >>> >> >> > know more detail about this project and if you can, please
>>> guide
>>> >>> me to
>>> >>> >> >> > start working on this project.
>>> >>> >> >> >
>>> >>> >> >> > Thank you.
>>> >>> >> >> >
>>> >>> >> >> > W. A. Dulanga Sashika,
>>> >>> >> >> > Undergraduate Student,
>>> >>> >> >> > Department of Computer Science and Engineering,
>>> >>> >> >> > University of Moratuwa.
>>> >>> >> >>
>>> >>> >> >
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > --
>>> >>> >> > W. A. Dulanga Sashika,
>>> >>> >> > Undergraduate Student,
>>> >>> >> > Department of Computer Science and Engineering,
>>> >>> >> > University of Moratuwa.
>>> >>> >>
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>> > --
>>> >>> > W. A. Dulanga Sashika,
>>> >>> > Undergraduate Student,
>>> >>> > Department of Computer Science and Engineering,
>>> >>> > University of Moratuwa.
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> W. A. Dulanga Sashika,
>>> >> Undergraduate Student,
>>> >> Department of Computer Science and Engineering,
>>> >> University of Moratuwa.
>>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Now I am trying to create a new menu item for dashboard and implement a
react component as you said. But now I am stuck in some place and couldn't
figure out the problem yet. Here is the problem I had in process. I added
dashboard menu item and added route and view for that. And i change the
code to render dashboard when we enter http://localhost:8000 . As in img1
and img2, it doesn't show the view I created. But when I click on another
menu item and come back to the dashboard, it shows the breadcrumb of
previous pages as img 3 and 4. As in
https://github.com/apache/couchdb-fauxton/blob/master/app/addons/databases/routes.js#L46
, I called the new Dashboard.view() which is a component in my view.js. But
in the console, it shows Uncaught Type error. Did I miss any configuration
thing or did I do it wrong?

On Thu, Mar 19, 2015 at 10:06 AM, Dulanga Sashika <wa...@gmail.com>
wrote:

> Hi Robert,
>
> Thank you very much for the reference. I started to write the proposal
> today. I hope you will help to write this proposal by reviewing  it. I will
> share it with you after complete the draft of the proposal.
>
> Thank you
>
> On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Some of you asked for a template for their proposals, here is what I've
>> found:
>>
>> http://community.staging.apache.org/gsoc#application-template
>>
>> Best,
>> Robert
>>
>> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>> > Wow you are making very good progress!
>> >
>> > We have our weekly status meetup tomorrow (see [1] for the time in
>> > your timezone), feel free to join, meet other project members and
>> > learn what the project is currently doing next to the Summer of Code.
>> >
>> > I will also be around 1hr earlier to answer all your questions and
>> > discuss our next steps.
>> >
>> >
>> > [1]
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >
>> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> >> Hi Robert,
>> >>
>> >> Here is the current status of the checklist :)
>> >>
>> >>  - check out the active tasks api (linked on top of this mail) -
>> (finished)
>> >>  - a mockup showing some widgets and how they could look like -
>> (started
>> >> but not finished yet)
>> >>  - code React tutorial & read about Flux - (finished)
>> >>  - take a look how we are using React - (finished)
>> >>  - create another menu item, called "Dashboard", try to answer the
>> >> questions to route.js et al - (started but not finished yet)
>> >>  - get familiar how we test our code - (finished)
>> >>  - write an hello world / hello from dulanga component that is
>> >> rendered into a screen when opening http://localhost:8000/dash or by
>> >> clicking on "dashboard" in the sidebar - (started but not finished yet)
>> >>
>> >> I will do my best to complete all these by tomorrow. If I have any
>> problem,
>> >> I will trouble you as you wished yesterday :)
>> >>
>> >> Thank You
>> >>
>> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>> >>
>> >>> Hi Dulanga,
>> >>>
>> >>> we already talked on irc and you already talked to Alex regarding
>> >>> features for our dashboard. That's great!
>> >>>
>> >>> Some topics will repeat in this mail, but I also would like the ML to
>> >>> follow our project and additionally add some more in-depth
>> >>> informations.
>> >>>
>> >>> Recap & additons
>> >>> =====
>> >>>
>> >>> As discussed we will work in an iterative approach and add widget
>> >>> after widget so if we run out of time, we will have something to
>> >>> deliver and don't have to throw everything away.
>> >>>
>> >>> Have you seen the "database" tab or the "config" tab in the sidebar
>> on the
>> >>> left?
>> >>>
>> >>> Those are modules that we can hook into the Fauxton build, by
>> >>> configuration. I think the idea is to create a tab "dashboard" which
>> >>> is the default one after opening Fauxton in the browser. So you would
>> >>> build the dashboard for Fauxton as part of Fauxton.
>> >>>
>> >>> Alex ideas so far:
>> >>>
>> >>> ```
>> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are some
>> >>> points about showing stats and log - forget these (: _stats isn't
>> >>> available for
>> >>>                    cluster iface and _log is removed. but recently
>> >>> visited databases, active tasks and _users/_replicator quick
>> >>> management is what could
>> >>>                    be really handy.
>> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>> >>> anymore after backporting some cloudant features
>> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>> >>> believe you could make some builtin and leave a template one to let
>> >>> the end users create
>> >>>                    their own if they're able/would like to. in future
>> >>> these are could be fauxton plugins or something.
>> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a
>> hot
>> >>> widget.
>> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with that
>> >>> (add custom widgets on build time) - the build is complicated, but
>> >>> once explained
>> >>>                            it should be easy
>> >>> ```
>> >>>
>> >>> So we have "custom widgets", "cluster quick-management", " recently
>> >>> visited databases",  "active tasks" and "_users/_replicator quick
>> >>> management"
>> >>>
>> >>> I think two good widgets for starting are active tasks and recently
>> >>> visited databases.
>> >>>
>> >>> For active tasks we have some nice docs:
>> >>>
>> >>>
>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>> >>>
>> >>> They have an own dedicated page in Fauxton (see
>> >>> http://localhost:8000/#/activetasks) but a short quick condensed list
>> >>> is probably very interesting to users.
>> >>>
>> >>> For the recently visited databases we would have to store that
>> somewhere.
>> >>>
>> >>> If you want, you can take an existing page in Fauxton and just modify
>> >>> the markup for a design mockup how the widget view may look like. But
>> >>> feel also free to use pen/paper or other tools if you like that the
>> >>> most.
>> >>>
>> >>> For the mango feature I am currently working on, I took the "edit
>> >>> view" template on modified the markup using the Chrome inspector of my
>> >>> browser to collect some first feedback from the project members and my
>> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>> >>> functionality, but gives other folks a rough idea what my idea for the
>> >>> feature is.
>> >>>
>> >>> the framework and react
>> >>>
>> >>> As I already mentioned we are using React.js.
>> >>>
>> >>> It would be nice if you can finish the tutorial at
>> >>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>> >>> until next friday by following the steps and writing that code. After
>> >>> that, read
>> >>>
>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>> >>> to get a first impression how the Flux pattern works that we are
>> >>> using.
>> >>>
>> >>> After that (if you still have time left) take a look on a component
>> >>> that Garren, my coworker refactored from Backbone.js to React:
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>> >>>
>> >>> Please take a look how the data flows from the Components, using the
>> >>> Actions, to the dispatcher at the Store. Feel free to litter
>> >>> everything in the code with console.log to see how state changes and
>> >>> how the data flows.
>> >>>
>> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>> >>>
>> >>>
>> >>> If you still have time, just try to create another menu item, called
>> >>> "Dashboard". Take a look at:
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>> >>>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>> >>>
>> >>> to get a first idea how to do that. Some background information:
>> >>>
>> >>> base.js - the starting point of our module. basic configuration is
>> done
>> >>> here
>> >>> Question: what is `base.js` used for in the case of the config module?
>> >>>
>> >>> routes.js - takes care that functions injecting the view into the
>> >>> layout are called depending on the url given
>> >>> Question: What happens if I call `http:localhost:8000/_config` and
>> >>> what happens if you remove the function `apiUrl`?
>> >>>
>> >>> views.js - contains our views - this file contains still a lot
>> >>> backbone views, which we are currently migrating to react. maybe it
>> >>> makes more sense to take a look at one of our react components:
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>> >>>
>> >>> and how they are used currently (as we are migrating to react
>> currently):
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>> >>>
>> >>> The Objects are injected into the closures using AMD:
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>> >>>
>> >>> assets folder:
>> >>> contains our less which is compiled to css
>> >>>
>> >>> templates folder:
>> >>> contains old backbone.js templates, you will not need them
>> >>>
>> >>> tests folder:
>> >>> contains unit and integration tests, every PR must have unit tests and
>> >>> integration tests. If you never wrote tests, we will explain it to you
>> >>> - it is easy once you wrote your first few ones. Basically you are
>> >>> testing each time that if you put something into a function, the
>> >>> expected result happens. Or that if you take an action, a state has
>> >>> changed.
>> >>>
>> >>> You can run the unit tests using `grunt test`
>> >>>
>> >>> Single tests are run by:
>> >>>
>> >>> ```
>> >>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
>> >>> ```
>> >>>
>> >>> or in the browser by test group:
>> >>>
>> >>> ```
>> >>>
>> >>>
>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>> >>> ```
>> >>>
>> >>> (change path to your fauxton directory)
>> >>>
>> >>> The corresponding code is:
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>> >>>
>> >>> and these tests are a good example how to write a simple test for the
>> >>> hello world/hello from dulanga-component:
>> >>>
>> >>>
>> >>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>> >>>
>> >>>
>> >>> First steps:
>> >>>
>> >>> Create a module `dashboard` that gets displayed in the sidebar. The
>> >>> route http://localhost:8000/dash will render a small React component
>> >>> that display "Hello World".
>> >>>
>> >>> If you click on the "Hello World" it ill change the content to: "Hello
>> >>> from Dulanga"
>> >>>
>> >>> While we will throw the small component away afterwards we will build
>> >>> upon the other code you created. If you have time left, add a test
>> >>> that the component changes the content.
>> >>>
>> >>>
>> >>> Meeting Wednesday:
>> >>> Feel free to join us on our weekly couchdb meeting:
>> >>>
>> >>>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >>>
>> >>> I will be around at least one hour before so we can chat. Contact me
>> >>> if you would like to chat earlier/later. I am also around the other
>> >>> days on IRC / the mailinglist and feel free to contact me in
>> >>> #couchdb-dev at any time. If I am not around I will answer you once I
>> >>> got online again, as I read the backlog.
>> >>>
>> >>>
>> >>> Our checklist at Wednesday (lets see how far we'll get)
>> >>>
>> >>>  - check out the active tasks api (linked on top of this mail)
>> >>>  - a mockup showing some widgets and how they could look like
>> >>>  - code React tutorial & read about Flux
>> >>>  - take a look how we are using React
>> >>>  - create another menu item, called "Dashboard", try to answer the
>> >>> questions to route.js et al
>> >>>  - get familiar how we test our code
>> >>>  - write an hello world / hello from dulanga component that is
>> >>> rendered into a screen when opening http://localhost:8000/dash or by
>> >>> clicking on "dashboard" in the sidebar
>> >>>
>> >>> That was a lot of content and please don't feel discouraged if you
>> >>> don't get that far until Wednesday. We will have to find a speed which
>> >>> is perfect for you and this time I tried to give enough informations
>> >>> that you are not blocked until Wednesday by waiting for next steps. If
>> >>> you are at the last step before Wednesday, drop me a line and I will
>> >>> prepare the next steps :)
>> >>>
>> >>> I know that you all have important exams, these are definitely more
>> >>> important! Don't feel pressured by the amount of work / the amount of
>> >>> informations, getting good results in the exams should be your first
>> >>> priority.
>> >>>
>> >>> Best,
>> >>> Robert
>> >>>
>> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >>> wrote:
>> >>> > Hi Robert,
>> >>> >
>> >>> > I went through the guidelines you provided and successfully
>> installed and
>> >>> > configured as you said. Everything works find and I played around
>> it by
>> >>> > creating a database and documents. I think I am ready for the next
>> step
>> >>> and
>> >>> > we can start it if you are ok :)
>> >>> >
>> >>> > Thank You
>> >>> >
>> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd>
>> >>> wrote:
>> >>> >
>> >>> >> You're welcome.
>> >>> >>
>> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if
>> you get
>> >>> >> stuck!
>> >>> >>
>> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >>> >> wrote:
>> >>> >> > Hi Robert,
>> >>> >> >
>> >>> >> > Thank you very much for the quick reply. I will go through the
>> >>> guidelines
>> >>> >> > and contact you if I have any issue with them.
>> >>> >> >
>> >>> >> > Thank you
>> >>> >> >
>> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <
>> rok@kowalski.gd>
>> >>> >> wrote:
>> >>> >> >
>> >>> >> >> Hi Dulanga,
>> >>> >> >>
>> >>> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
>> >>> >> >>
>> >>> >> >> CouchDB is a database written in Erlang with an HTTP API - that
>> makes
>> >>> >> >> it a great fit for web applications that don't need a server
>> side
>> >>> >> >> layer with a database driver in between. Our Project Fauxton
>> (like a
>> >>> >> >> modern PHP MyAdmin) makes use of that fact.
>> >>> >> >>
>> >>> >> >> Many of us hang out in freenode in #couchdb-dev including
>> myself.
>> >>> >> >> Whenever you get stuck, feel free to ask - if no one is online
>> (e.g.
>> >>> I
>> >>> >> >> was travelling this week) feel free to ask on the dev ML.
>> >>> >> >>
>> >>> >> >> We are all happy to help each other in the project :)
>> >>> >> >>
>> >>> >> >> If you are using windows: I am not a Windows expert - you will
>> >>> >> >> probably have to use a bash emulator like "git bash" to boot
>> the dev
>> >>> >> >> environment.
>> >>> >> >>
>> >>> >> >> Getting started:
>> >>> >> >>
>> >>> >> >> For this project you will need to install at least CouchDB 1.x,
>> an
>> >>> >> >> Ubuntu package (with installation instructions) is at
>> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>> >>> >> >>
>> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install
>> from
>> >>> >> >> https://nodejs.org)
>> >>> >> >>
>> >>> >> >> Booting Fauxton and first steps (type without the $):
>> >>> >> >>
>> >>> >> >> booting CouchDB:
>> >>> >> >> $ sudo couchdb
>> >>> >> >>
>> >>> >> >> in another terminal, clone the admin interface:
>> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>> >>> >> >>
>> >>> >> >> go to Fauxton:
>> >>> >> >> $ cd couchdb-fauxton
>> >>> >> >>
>> >>> >> >> install dependencies:
>> >>> >> >> $ npm install
>> >>> >> >> $ npm install -g grunt grunt-cli
>> >>> >> >>
>> >>> >> >> boot the app:
>> >>> >> >> $ grunt dev
>> >>> >> >>
>> >>> >> >> Then open your browser and go to http://localhost:8000 - you
>> should
>> >>> >> >> see a red/gray/black interface
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> That was a lot of input and especially if you are using Linux
>> the
>> >>> >> >> first time and followed the instructions you have archived a
>> lot!
>> >>> >> >>
>> >>> >> >> As first step, try to create a database and a document now
>> using the
>> >>> >> >> web interface (PS we are happy about any usability feedback). :)
>> >>> >> >>
>> >>> >> >> I think you have your dev environment for CouchDB ready now.
>> >>> >> >>
>> >>> >> >> What's next:
>> >>> >> >> If everything works we will take a look at Fauxtons code
>> structure
>> >>> and
>> >>> >> >> how it works. We will also talk about the features of the
>> dashboard.
>> >>> >> >> Let's find a date for a chat after you took a first look how
>> Fauxton
>> >>> >> >> looks like.
>> >>> >> >>
>> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on
>> freenode
>> >>> >> >> (see
>> >>> >> >>
>> >>> >>
>> >>>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >>> >> >> )
>> >>> >> >> . Feel free to join us! I will be around 1hr before if you want
>> to
>> >>> >> >> chat with me before.
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> Looking forward to work with you,
>> >>> >> >> Robert
>> >>> >> >>
>> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>> >>> wadsashika@gmail.com>
>> >>> >> >> wrote:
>> >>> >> >> > Hi all,
>> >>> >> >> >
>> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
>> student at
>> >>> >> >> > Computer Science and Engineering department at University of
>> >>> Moratuwa,
>> >>> >> >> Sri
>> >>> >> >> > Lanka. I am really interested in java, java script, web
>> >>> applications,
>> >>> >> >> > algorithms, data mining and machine learning. I have 6 months
>> of
>> >>> >> training
>> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a
>> web
>> >>> >> >> application
>> >>> >> >> > that used java, JEE and Spring Framework. My final year
>> project
>> >>> also a
>> >>> >> >> web
>> >>> >> >> > related application and I used same technologies I mentioned
>> above
>> >>> for
>> >>> >> >> > that. I am really interested in this project because I have a
>> good
>> >>> >> >> > experience with web applications and I love work with
>> javascript.
>> >>> I am
>> >>> >> >> > looking forward to contribute to this project in this summer.
>> I
>> >>> like
>> >>> >> to
>> >>> >> >> > know more detail about this project and if you can, please
>> guide
>> >>> me to
>> >>> >> >> > start working on this project.
>> >>> >> >> >
>> >>> >> >> > Thank you.
>> >>> >> >> >
>> >>> >> >> > W. A. Dulanga Sashika,
>> >>> >> >> > Undergraduate Student,
>> >>> >> >> > Department of Computer Science and Engineering,
>> >>> >> >> > University of Moratuwa.
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > W. A. Dulanga Sashika,
>> >>> >> > Undergraduate Student,
>> >>> >> > Department of Computer Science and Engineering,
>> >>> >> > University of Moratuwa.
>> >>> >>
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > W. A. Dulanga Sashika,
>> >>> > Undergraduate Student,
>> >>> > Department of Computer Science and Engineering,
>> >>> > University of Moratuwa.
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> W. A. Dulanga Sashika,
>> >> Undergraduate Student,
>> >> Department of Computer Science and Engineering,
>> >> University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Thank you very much for the reference. I started to write the proposal
today. I hope you will help to write this proposal by reviewing  it. I will
share it with you after complete the draft of the proposal.

Thank you

On Thu, Mar 19, 2015 at 3:21 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Some of you asked for a template for their proposals, here is what I've
> found:
>
> http://community.staging.apache.org/gsoc#application-template
>
> Best,
> Robert
>
> On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
> > Wow you are making very good progress!
> >
> > We have our weekly status meetup tomorrow (see [1] for the time in
> > your timezone), feel free to join, meet other project members and
> > learn what the project is currently doing next to the Summer of Code.
> >
> > I will also be around 1hr earlier to answer all your questions and
> > discuss our next steps.
> >
> >
> > [1]
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >
> > On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> >> Hi Robert,
> >>
> >> Here is the current status of the checklist :)
> >>
> >>  - check out the active tasks api (linked on top of this mail) -
> (finished)
> >>  - a mockup showing some widgets and how they could look like - (started
> >> but not finished yet)
> >>  - code React tutorial & read about Flux - (finished)
> >>  - take a look how we are using React - (finished)
> >>  - create another menu item, called "Dashboard", try to answer the
> >> questions to route.js et al - (started but not finished yet)
> >>  - get familiar how we test our code - (finished)
> >>  - write an hello world / hello from dulanga component that is
> >> rendered into a screen when opening http://localhost:8000/dash or by
> >> clicking on "dashboard" in the sidebar - (started but not finished yet)
> >>
> >> I will do my best to complete all these by tomorrow. If I have any
> problem,
> >> I will trouble you as you wished yesterday :)
> >>
> >> Thank You
> >>
> >> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >>
> >>> Hi Dulanga,
> >>>
> >>> we already talked on irc and you already talked to Alex regarding
> >>> features for our dashboard. That's great!
> >>>
> >>> Some topics will repeat in this mail, but I also would like the ML to
> >>> follow our project and additionally add some more in-depth
> >>> informations.
> >>>
> >>> Recap & additons
> >>> =====
> >>>
> >>> As discussed we will work in an iterative approach and add widget
> >>> after widget so if we run out of time, we will have something to
> >>> deliver and don't have to throw everything away.
> >>>
> >>> Have you seen the "database" tab or the "config" tab in the sidebar on
> the
> >>> left?
> >>>
> >>> Those are modules that we can hook into the Fauxton build, by
> >>> configuration. I think the idea is to create a tab "dashboard" which
> >>> is the default one after opening Fauxton in the browser. So you would
> >>> build the dashboard for Fauxton as part of Fauxton.
> >>>
> >>> Alex ideas so far:
> >>>
> >>> ```
> >>> 17:34:13 <+Kxepal> about from what to start...in issue there are some
> >>> points about showing stats and log - forget these (: _stats isn't
> >>> available for
> >>>                    cluster iface and _log is removed. but recently
> >>> visited databases, active tasks and _users/_replicator quick
> >>> management is what could
> >>>                    be really handy.
> >>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
> >>> anymore after backporting some cloudant features
> >>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
> >>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
> >>> believe you could make some builtin and leave a template one to let
> >>> the end users create
> >>>                    their own if they're able/would like to. in future
> >>> these are could be fauxton plugins or something.
> >>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a hot
> >>> widget.
> >>> 17:39:56 <+robertkowalski> good idea - i can definitely help with that
> >>> (add custom widgets on build time) - the build is complicated, but
> >>> once explained
> >>>                            it should be easy
> >>> ```
> >>>
> >>> So we have "custom widgets", "cluster quick-management", " recently
> >>> visited databases",  "active tasks" and "_users/_replicator quick
> >>> management"
> >>>
> >>> I think two good widgets for starting are active tasks and recently
> >>> visited databases.
> >>>
> >>> For active tasks we have some nice docs:
> >>>
> >>>
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
> >>>
> >>> They have an own dedicated page in Fauxton (see
> >>> http://localhost:8000/#/activetasks) but a short quick condensed list
> >>> is probably very interesting to users.
> >>>
> >>> For the recently visited databases we would have to store that
> somewhere.
> >>>
> >>> If you want, you can take an existing page in Fauxton and just modify
> >>> the markup for a design mockup how the widget view may look like. But
> >>> feel also free to use pen/paper or other tools if you like that the
> >>> most.
> >>>
> >>> For the mango feature I am currently working on, I took the "edit
> >>> view" template on modified the markup using the Chrome inspector of my
> >>> browser to collect some first feedback from the project members and my
> >>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
> >>> functionality, but gives other folks a rough idea what my idea for the
> >>> feature is.
> >>>
> >>> the framework and react
> >>>
> >>> As I already mentioned we are using React.js.
> >>>
> >>> It would be nice if you can finish the tutorial at
> >>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> >>> until next friday by following the steps and writing that code. After
> >>> that, read
> >>>
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> >>> to get a first impression how the Flux pattern works that we are
> >>> using.
> >>>
> >>> After that (if you still have time left) take a look on a component
> >>> that Garren, my coworker refactored from Backbone.js to React:
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
> >>>
> >>> Please take a look how the data flows from the Components, using the
> >>> Actions, to the dispatcher at the Store. Feel free to litter
> >>> everything in the code with console.log to see how state changes and
> >>> how the data flows.
> >>>
> >>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
> >>>
> >>>
> >>> If you still have time, just try to create another menu item, called
> >>> "Dashboard". Take a look at:
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> >>>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
> >>>
> >>> to get a first idea how to do that. Some background information:
> >>>
> >>> base.js - the starting point of our module. basic configuration is done
> >>> here
> >>> Question: what is `base.js` used for in the case of the config module?
> >>>
> >>> routes.js - takes care that functions injecting the view into the
> >>> layout are called depending on the url given
> >>> Question: What happens if I call `http:localhost:8000/_config` and
> >>> what happens if you remove the function `apiUrl`?
> >>>
> >>> views.js - contains our views - this file contains still a lot
> >>> backbone views, which we are currently migrating to react. maybe it
> >>> makes more sense to take a look at one of our react components:
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
> >>>
> >>> and how they are used currently (as we are migrating to react
> currently):
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
> >>>
> >>> The Objects are injected into the closures using AMD:
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
> >>>
> >>> assets folder:
> >>> contains our less which is compiled to css
> >>>
> >>> templates folder:
> >>> contains old backbone.js templates, you will not need them
> >>>
> >>> tests folder:
> >>> contains unit and integration tests, every PR must have unit tests and
> >>> integration tests. If you never wrote tests, we will explain it to you
> >>> - it is easy once you wrote your first few ones. Basically you are
> >>> testing each time that if you put something into a function, the
> >>> expected result happens. Or that if you take an action, a state has
> >>> changed.
> >>>
> >>> You can run the unit tests using `grunt test`
> >>>
> >>> Single tests are run by:
> >>>
> >>> ```
> >>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
> >>> ```
> >>>
> >>> or in the browser by test group:
> >>>
> >>> ```
> >>>
> >>>
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> >>> ```
> >>>
> >>> (change path to your fauxton directory)
> >>>
> >>> The corresponding code is:
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
> >>>
> >>> and these tests are a good example how to write a simple test for the
> >>> hello world/hello from dulanga-component:
> >>>
> >>>
> >>>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
> >>>
> >>>
> >>> First steps:
> >>>
> >>> Create a module `dashboard` that gets displayed in the sidebar. The
> >>> route http://localhost:8000/dash will render a small React component
> >>> that display "Hello World".
> >>>
> >>> If you click on the "Hello World" it ill change the content to: "Hello
> >>> from Dulanga"
> >>>
> >>> While we will throw the small component away afterwards we will build
> >>> upon the other code you created. If you have time left, add a test
> >>> that the component changes the content.
> >>>
> >>>
> >>> Meeting Wednesday:
> >>> Feel free to join us on our weekly couchdb meeting:
> >>>
> >>>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >>>
> >>> I will be around at least one hour before so we can chat. Contact me
> >>> if you would like to chat earlier/later. I am also around the other
> >>> days on IRC / the mailinglist and feel free to contact me in
> >>> #couchdb-dev at any time. If I am not around I will answer you once I
> >>> got online again, as I read the backlog.
> >>>
> >>>
> >>> Our checklist at Wednesday (lets see how far we'll get)
> >>>
> >>>  - check out the active tasks api (linked on top of this mail)
> >>>  - a mockup showing some widgets and how they could look like
> >>>  - code React tutorial & read about Flux
> >>>  - take a look how we are using React
> >>>  - create another menu item, called "Dashboard", try to answer the
> >>> questions to route.js et al
> >>>  - get familiar how we test our code
> >>>  - write an hello world / hello from dulanga component that is
> >>> rendered into a screen when opening http://localhost:8000/dash or by
> >>> clicking on "dashboard" in the sidebar
> >>>
> >>> That was a lot of content and please don't feel discouraged if you
> >>> don't get that far until Wednesday. We will have to find a speed which
> >>> is perfect for you and this time I tried to give enough informations
> >>> that you are not blocked until Wednesday by waiting for next steps. If
> >>> you are at the last step before Wednesday, drop me a line and I will
> >>> prepare the next steps :)
> >>>
> >>> I know that you all have important exams, these are definitely more
> >>> important! Don't feel pressured by the amount of work / the amount of
> >>> informations, getting good results in the exams should be your first
> >>> priority.
> >>>
> >>> Best,
> >>> Robert
> >>>
> >>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <wadsashika@gmail.com
> >
> >>> wrote:
> >>> > Hi Robert,
> >>> >
> >>> > I went through the guidelines you provided and successfully
> installed and
> >>> > configured as you said. Everything works find and I played around it
> by
> >>> > creating a database and documents. I think I am ready for the next
> step
> >>> and
> >>> > we can start it if you are ok :)
> >>> >
> >>> > Thank You
> >>> >
> >>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd>
> >>> wrote:
> >>> >
> >>> >> You're welcome.
> >>> >>
> >>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if you
> get
> >>> >> stuck!
> >>> >>
> >>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <
> wadsashika@gmail.com>
> >>> >> wrote:
> >>> >> > Hi Robert,
> >>> >> >
> >>> >> > Thank you very much for the quick reply. I will go through the
> >>> guidelines
> >>> >> > and contact you if I have any issue with them.
> >>> >> >
> >>> >> > Thank you
> >>> >> >
> >>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <
> rok@kowalski.gd>
> >>> >> wrote:
> >>> >> >
> >>> >> >> Hi Dulanga,
> >>> >> >>
> >>> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
> >>> >> >>
> >>> >> >> CouchDB is a database written in Erlang with an HTTP API - that
> makes
> >>> >> >> it a great fit for web applications that don't need a server side
> >>> >> >> layer with a database driver in between. Our Project Fauxton
> (like a
> >>> >> >> modern PHP MyAdmin) makes use of that fact.
> >>> >> >>
> >>> >> >> Many of us hang out in freenode in #couchdb-dev including myself.
> >>> >> >> Whenever you get stuck, feel free to ask - if no one is online
> (e.g.
> >>> I
> >>> >> >> was travelling this week) feel free to ask on the dev ML.
> >>> >> >>
> >>> >> >> We are all happy to help each other in the project :)
> >>> >> >>
> >>> >> >> If you are using windows: I am not a Windows expert - you will
> >>> >> >> probably have to use a bash emulator like "git bash" to boot the
> dev
> >>> >> >> environment.
> >>> >> >>
> >>> >> >> Getting started:
> >>> >> >>
> >>> >> >> For this project you will need to install at least CouchDB 1.x,
> an
> >>> >> >> Ubuntu package (with installation instructions) is at
> >>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >>> >> >>
> >>> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install
> from
> >>> >> >> https://nodejs.org)
> >>> >> >>
> >>> >> >> Booting Fauxton and first steps (type without the $):
> >>> >> >>
> >>> >> >> booting CouchDB:
> >>> >> >> $ sudo couchdb
> >>> >> >>
> >>> >> >> in another terminal, clone the admin interface:
> >>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
> >>> >> >>
> >>> >> >> go to Fauxton:
> >>> >> >> $ cd couchdb-fauxton
> >>> >> >>
> >>> >> >> install dependencies:
> >>> >> >> $ npm install
> >>> >> >> $ npm install -g grunt grunt-cli
> >>> >> >>
> >>> >> >> boot the app:
> >>> >> >> $ grunt dev
> >>> >> >>
> >>> >> >> Then open your browser and go to http://localhost:8000 - you
> should
> >>> >> >> see a red/gray/black interface
> >>> >> >>
> >>> >> >>
> >>> >> >> That was a lot of input and especially if you are using Linux the
> >>> >> >> first time and followed the instructions you have archived a lot!
> >>> >> >>
> >>> >> >> As first step, try to create a database and a document now using
> the
> >>> >> >> web interface (PS we are happy about any usability feedback). :)
> >>> >> >>
> >>> >> >> I think you have your dev environment for CouchDB ready now.
> >>> >> >>
> >>> >> >> What's next:
> >>> >> >> If everything works we will take a look at Fauxtons code
> structure
> >>> and
> >>> >> >> how it works. We will also talk about the features of the
> dashboard.
> >>> >> >> Let's find a date for a chat after you took a first look how
> Fauxton
> >>> >> >> looks like.
> >>> >> >>
> >>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
> >>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on
> freenode
> >>> >> >> (see
> >>> >> >>
> >>> >>
> >>>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >>> >> >> )
> >>> >> >> . Feel free to join us! I will be around 1hr before if you want
> to
> >>> >> >> chat with me before.
> >>> >> >>
> >>> >> >>
> >>> >> >> Looking forward to work with you,
> >>> >> >> Robert
> >>> >> >>
> >>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> >>> wadsashika@gmail.com>
> >>> >> >> wrote:
> >>> >> >> > Hi all,
> >>> >> >> >
> >>> >> >> > I am Dulanga Sashika and I am a final year undergraduate
> student at
> >>> >> >> > Computer Science and Engineering department at University of
> >>> Moratuwa,
> >>> >> >> Sri
> >>> >> >> > Lanka. I am really interested in java, java script, web
> >>> applications,
> >>> >> >> > algorithms, data mining and machine learning. I have 6 months
> of
> >>> >> training
> >>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
> >>> >> >> application
> >>> >> >> > that used java, JEE and Spring Framework. My final year project
> >>> also a
> >>> >> >> web
> >>> >> >> > related application and I used same technologies I mentioned
> above
> >>> for
> >>> >> >> > that. I am really interested in this project because I have a
> good
> >>> >> >> > experience with web applications and I love work with
> javascript.
> >>> I am
> >>> >> >> > looking forward to contribute to this project in this summer. I
> >>> like
> >>> >> to
> >>> >> >> > know more detail about this project and if you can, please
> guide
> >>> me to
> >>> >> >> > start working on this project.
> >>> >> >> >
> >>> >> >> > Thank you.
> >>> >> >> >
> >>> >> >> > W. A. Dulanga Sashika,
> >>> >> >> > Undergraduate Student,
> >>> >> >> > Department of Computer Science and Engineering,
> >>> >> >> > University of Moratuwa.
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > W. A. Dulanga Sashika,
> >>> >> > Undergraduate Student,
> >>> >> > Department of Computer Science and Engineering,
> >>> >> > University of Moratuwa.
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > W. A. Dulanga Sashika,
> >>> > Undergraduate Student,
> >>> > Department of Computer Science and Engineering,
> >>> > University of Moratuwa.
> >>>
> >>
> >>
> >>
> >> --
> >> W. A. Dulanga Sashika,
> >> Undergraduate Student,
> >> Department of Computer Science and Engineering,
> >> University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Some of you asked for a template for their proposals, here is what I've found:

http://community.staging.apache.org/gsoc#application-template

Best,
Robert

On Tue, Mar 17, 2015 at 10:39 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
> Wow you are making very good progress!
>
> We have our weekly status meetup tomorrow (see [1] for the time in
> your timezone), feel free to join, meet other project members and
> learn what the project is currently doing next to the Summer of Code.
>
> I will also be around 1hr earlier to answer all your questions and
> discuss our next steps.
>
>
> [1] http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>
> On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <wa...@gmail.com> wrote:
>> Hi Robert,
>>
>> Here is the current status of the checklist :)
>>
>>  - check out the active tasks api (linked on top of this mail) - (finished)
>>  - a mockup showing some widgets and how they could look like - (started
>> but not finished yet)
>>  - code React tutorial & read about Flux - (finished)
>>  - take a look how we are using React - (finished)
>>  - create another menu item, called "Dashboard", try to answer the
>> questions to route.js et al - (started but not finished yet)
>>  - get familiar how we test our code - (finished)
>>  - write an hello world / hello from dulanga component that is
>> rendered into a screen when opening http://localhost:8000/dash or by
>> clicking on "dashboard" in the sidebar - (started but not finished yet)
>>
>> I will do my best to complete all these by tomorrow. If I have any problem,
>> I will trouble you as you wished yesterday :)
>>
>> Thank You
>>
>> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>>
>>> Hi Dulanga,
>>>
>>> we already talked on irc and you already talked to Alex regarding
>>> features for our dashboard. That's great!
>>>
>>> Some topics will repeat in this mail, but I also would like the ML to
>>> follow our project and additionally add some more in-depth
>>> informations.
>>>
>>> Recap & additons
>>> =====
>>>
>>> As discussed we will work in an iterative approach and add widget
>>> after widget so if we run out of time, we will have something to
>>> deliver and don't have to throw everything away.
>>>
>>> Have you seen the "database" tab or the "config" tab in the sidebar on the
>>> left?
>>>
>>> Those are modules that we can hook into the Fauxton build, by
>>> configuration. I think the idea is to create a tab "dashboard" which
>>> is the default one after opening Fauxton in the browser. So you would
>>> build the dashboard for Fauxton as part of Fauxton.
>>>
>>> Alex ideas so far:
>>>
>>> ```
>>> 17:34:13 <+Kxepal> about from what to start...in issue there are some
>>> points about showing stats and log - forget these (: _stats isn't
>>> available for
>>>                    cluster iface and _log is removed. but recently
>>> visited databases, active tasks and _users/_replicator quick
>>> management is what could
>>>                    be really handy.
>>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>>> anymore after backporting some cloudant features
>>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>>> believe you could make some builtin and leave a template one to let
>>> the end users create
>>>                    their own if they're able/would like to. in future
>>> these are could be fauxton plugins or something.
>>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a hot
>>> widget.
>>> 17:39:56 <+robertkowalski> good idea - i can definitely help with that
>>> (add custom widgets on build time) - the build is complicated, but
>>> once explained
>>>                            it should be easy
>>> ```
>>>
>>> So we have "custom widgets", "cluster quick-management", " recently
>>> visited databases",  "active tasks" and "_users/_replicator quick
>>> management"
>>>
>>> I think two good widgets for starting are active tasks and recently
>>> visited databases.
>>>
>>> For active tasks we have some nice docs:
>>>
>>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>>>
>>> They have an own dedicated page in Fauxton (see
>>> http://localhost:8000/#/activetasks) but a short quick condensed list
>>> is probably very interesting to users.
>>>
>>> For the recently visited databases we would have to store that somewhere.
>>>
>>> If you want, you can take an existing page in Fauxton and just modify
>>> the markup for a design mockup how the widget view may look like. But
>>> feel also free to use pen/paper or other tools if you like that the
>>> most.
>>>
>>> For the mango feature I am currently working on, I took the "edit
>>> view" template on modified the markup using the Chrome inspector of my
>>> browser to collect some first feedback from the project members and my
>>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>>> functionality, but gives other folks a rough idea what my idea for the
>>> feature is.
>>>
>>> the framework and react
>>>
>>> As I already mentioned we are using React.js.
>>>
>>> It would be nice if you can finish the tutorial at
>>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>>> until next friday by following the steps and writing that code. After
>>> that, read
>>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>>> to get a first impression how the Flux pattern works that we are
>>> using.
>>>
>>> After that (if you still have time left) take a look on a component
>>> that Garren, my coworker refactored from Backbone.js to React:
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>>>
>>> Please take a look how the data flows from the Components, using the
>>> Actions, to the dispatcher at the Store. Feel free to litter
>>> everything in the code with console.log to see how state changes and
>>> how the data flows.
>>>
>>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>>>
>>>
>>> If you still have time, just try to create another menu item, called
>>> "Dashboard". Take a look at:
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>>>
>>> to get a first idea how to do that. Some background information:
>>>
>>> base.js - the starting point of our module. basic configuration is done
>>> here
>>> Question: what is `base.js` used for in the case of the config module?
>>>
>>> routes.js - takes care that functions injecting the view into the
>>> layout are called depending on the url given
>>> Question: What happens if I call `http:localhost:8000/_config` and
>>> what happens if you remove the function `apiUrl`?
>>>
>>> views.js - contains our views - this file contains still a lot
>>> backbone views, which we are currently migrating to react. maybe it
>>> makes more sense to take a look at one of our react components:
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>>>
>>> and how they are used currently (as we are migrating to react currently):
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>>>
>>> The Objects are injected into the closures using AMD:
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>>>
>>> assets folder:
>>> contains our less which is compiled to css
>>>
>>> templates folder:
>>> contains old backbone.js templates, you will not need them
>>>
>>> tests folder:
>>> contains unit and integration tests, every PR must have unit tests and
>>> integration tests. If you never wrote tests, we will explain it to you
>>> - it is easy once you wrote your first few ones. Basically you are
>>> testing each time that if you put something into a function, the
>>> expected result happens. Or that if you take an action, a state has
>>> changed.
>>>
>>> You can run the unit tests using `grunt test`
>>>
>>> Single tests are run by:
>>>
>>> ```
>>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
>>> ```
>>>
>>> or in the browser by test group:
>>>
>>> ```
>>>
>>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>>> ```
>>>
>>> (change path to your fauxton directory)
>>>
>>> The corresponding code is:
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>>>
>>> and these tests are a good example how to write a simple test for the
>>> hello world/hello from dulanga-component:
>>>
>>>
>>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>>>
>>>
>>> First steps:
>>>
>>> Create a module `dashboard` that gets displayed in the sidebar. The
>>> route http://localhost:8000/dash will render a small React component
>>> that display "Hello World".
>>>
>>> If you click on the "Hello World" it ill change the content to: "Hello
>>> from Dulanga"
>>>
>>> While we will throw the small component away afterwards we will build
>>> upon the other code you created. If you have time left, add a test
>>> that the component changes the content.
>>>
>>>
>>> Meeting Wednesday:
>>> Feel free to join us on our weekly couchdb meeting:
>>>
>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>>
>>> I will be around at least one hour before so we can chat. Contact me
>>> if you would like to chat earlier/later. I am also around the other
>>> days on IRC / the mailinglist and feel free to contact me in
>>> #couchdb-dev at any time. If I am not around I will answer you once I
>>> got online again, as I read the backlog.
>>>
>>>
>>> Our checklist at Wednesday (lets see how far we'll get)
>>>
>>>  - check out the active tasks api (linked on top of this mail)
>>>  - a mockup showing some widgets and how they could look like
>>>  - code React tutorial & read about Flux
>>>  - take a look how we are using React
>>>  - create another menu item, called "Dashboard", try to answer the
>>> questions to route.js et al
>>>  - get familiar how we test our code
>>>  - write an hello world / hello from dulanga component that is
>>> rendered into a screen when opening http://localhost:8000/dash or by
>>> clicking on "dashboard" in the sidebar
>>>
>>> That was a lot of content and please don't feel discouraged if you
>>> don't get that far until Wednesday. We will have to find a speed which
>>> is perfect for you and this time I tried to give enough informations
>>> that you are not blocked until Wednesday by waiting for next steps. If
>>> you are at the last step before Wednesday, drop me a line and I will
>>> prepare the next steps :)
>>>
>>> I know that you all have important exams, these are definitely more
>>> important! Don't feel pressured by the amount of work / the amount of
>>> informations, getting good results in the exams should be your first
>>> priority.
>>>
>>> Best,
>>> Robert
>>>
>>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <wa...@gmail.com>
>>> wrote:
>>> > Hi Robert,
>>> >
>>> > I went through the guidelines you provided and successfully installed and
>>> > configured as you said. Everything works find and I played around it by
>>> > creating a database and documents. I think I am ready for the next step
>>> and
>>> > we can start it if you are ok :)
>>> >
>>> > Thank You
>>> >
>>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd>
>>> wrote:
>>> >
>>> >> You're welcome.
>>> >>
>>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if you get
>>> >> stuck!
>>> >>
>>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com>
>>> >> wrote:
>>> >> > Hi Robert,
>>> >> >
>>> >> > Thank you very much for the quick reply. I will go through the
>>> guidelines
>>> >> > and contact you if I have any issue with them.
>>> >> >
>>> >> > Thank you
>>> >> >
>>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd>
>>> >> wrote:
>>> >> >
>>> >> >> Hi Dulanga,
>>> >> >>
>>> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
>>> >> >>
>>> >> >> CouchDB is a database written in Erlang with an HTTP API - that makes
>>> >> >> it a great fit for web applications that don't need a server side
>>> >> >> layer with a database driver in between. Our Project Fauxton (like a
>>> >> >> modern PHP MyAdmin) makes use of that fact.
>>> >> >>
>>> >> >> Many of us hang out in freenode in #couchdb-dev including myself.
>>> >> >> Whenever you get stuck, feel free to ask - if no one is online (e.g.
>>> I
>>> >> >> was travelling this week) feel free to ask on the dev ML.
>>> >> >>
>>> >> >> We are all happy to help each other in the project :)
>>> >> >>
>>> >> >> If you are using windows: I am not a Windows expert - you will
>>> >> >> probably have to use a bash emulator like "git bash" to boot the dev
>>> >> >> environment.
>>> >> >>
>>> >> >> Getting started:
>>> >> >>
>>> >> >> For this project you will need to install at least CouchDB 1.x, an
>>> >> >> Ubuntu package (with installation instructions) is at
>>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>>> >> >>
>>> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install from
>>> >> >> https://nodejs.org)
>>> >> >>
>>> >> >> Booting Fauxton and first steps (type without the $):
>>> >> >>
>>> >> >> booting CouchDB:
>>> >> >> $ sudo couchdb
>>> >> >>
>>> >> >> in another terminal, clone the admin interface:
>>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>>> >> >>
>>> >> >> go to Fauxton:
>>> >> >> $ cd couchdb-fauxton
>>> >> >>
>>> >> >> install dependencies:
>>> >> >> $ npm install
>>> >> >> $ npm install -g grunt grunt-cli
>>> >> >>
>>> >> >> boot the app:
>>> >> >> $ grunt dev
>>> >> >>
>>> >> >> Then open your browser and go to http://localhost:8000 - you should
>>> >> >> see a red/gray/black interface
>>> >> >>
>>> >> >>
>>> >> >> That was a lot of input and especially if you are using Linux the
>>> >> >> first time and followed the instructions you have archived a lot!
>>> >> >>
>>> >> >> As first step, try to create a database and a document now using the
>>> >> >> web interface (PS we are happy about any usability feedback). :)
>>> >> >>
>>> >> >> I think you have your dev environment for CouchDB ready now.
>>> >> >>
>>> >> >> What's next:
>>> >> >> If everything works we will take a look at Fauxtons code structure
>>> and
>>> >> >> how it works. We will also talk about the features of the dashboard.
>>> >> >> Let's find a date for a chat after you took a first look how Fauxton
>>> >> >> looks like.
>>> >> >>
>>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
>>> >> >> (see
>>> >> >>
>>> >>
>>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>> >> >> )
>>> >> >> . Feel free to join us! I will be around 1hr before if you want to
>>> >> >> chat with me before.
>>> >> >>
>>> >> >>
>>> >> >> Looking forward to work with you,
>>> >> >> Robert
>>> >> >>
>>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>>> wadsashika@gmail.com>
>>> >> >> wrote:
>>> >> >> > Hi all,
>>> >> >> >
>>> >> >> > I am Dulanga Sashika and I am a final year undergraduate student at
>>> >> >> > Computer Science and Engineering department at University of
>>> Moratuwa,
>>> >> >> Sri
>>> >> >> > Lanka. I am really interested in java, java script, web
>>> applications,
>>> >> >> > algorithms, data mining and machine learning. I have 6 months of
>>> >> training
>>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
>>> >> >> application
>>> >> >> > that used java, JEE and Spring Framework. My final year project
>>> also a
>>> >> >> web
>>> >> >> > related application and I used same technologies I mentioned above
>>> for
>>> >> >> > that. I am really interested in this project because I have a good
>>> >> >> > experience with web applications and I love work with javascript.
>>> I am
>>> >> >> > looking forward to contribute to this project in this summer. I
>>> like
>>> >> to
>>> >> >> > know more detail about this project and if you can, please guide
>>> me to
>>> >> >> > start working on this project.
>>> >> >> >
>>> >> >> > Thank you.
>>> >> >> >
>>> >> >> > W. A. Dulanga Sashika,
>>> >> >> > Undergraduate Student,
>>> >> >> > Department of Computer Science and Engineering,
>>> >> >> > University of Moratuwa.
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > W. A. Dulanga Sashika,
>>> >> > Undergraduate Student,
>>> >> > Department of Computer Science and Engineering,
>>> >> > University of Moratuwa.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > W. A. Dulanga Sashika,
>>> > Undergraduate Student,
>>> > Department of Computer Science and Engineering,
>>> > University of Moratuwa.
>>>
>>
>>
>>
>> --
>> W. A. Dulanga Sashika,
>> Undergraduate Student,
>> Department of Computer Science and Engineering,
>> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Wow you are making very good progress!

We have our weekly status meetup tomorrow (see [1] for the time in
your timezone), feel free to join, meet other project members and
learn what the project is currently doing next to the Summer of Code.

I will also be around 1hr earlier to answer all your questions and
discuss our next steps.


[1] http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E

On Tue, Mar 17, 2015 at 1:52 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> Here is the current status of the checklist :)
>
>  - check out the active tasks api (linked on top of this mail) - (finished)
>  - a mockup showing some widgets and how they could look like - (started
> but not finished yet)
>  - code React tutorial & read about Flux - (finished)
>  - take a look how we are using React - (finished)
>  - create another menu item, called "Dashboard", try to answer the
> questions to route.js et al - (started but not finished yet)
>  - get familiar how we test our code - (finished)
>  - write an hello world / hello from dulanga component that is
> rendered into a screen when opening http://localhost:8000/dash or by
> clicking on "dashboard" in the sidebar - (started but not finished yet)
>
> I will do my best to complete all these by tomorrow. If I have any problem,
> I will trouble you as you wished yesterday :)
>
> Thank You
>
> On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Hi Dulanga,
>>
>> we already talked on irc and you already talked to Alex regarding
>> features for our dashboard. That's great!
>>
>> Some topics will repeat in this mail, but I also would like the ML to
>> follow our project and additionally add some more in-depth
>> informations.
>>
>> Recap & additons
>> =====
>>
>> As discussed we will work in an iterative approach and add widget
>> after widget so if we run out of time, we will have something to
>> deliver and don't have to throw everything away.
>>
>> Have you seen the "database" tab or the "config" tab in the sidebar on the
>> left?
>>
>> Those are modules that we can hook into the Fauxton build, by
>> configuration. I think the idea is to create a tab "dashboard" which
>> is the default one after opening Fauxton in the browser. So you would
>> build the dashboard for Fauxton as part of Fauxton.
>>
>> Alex ideas so far:
>>
>> ```
>> 17:34:13 <+Kxepal> about from what to start...in issue there are some
>> points about showing stats and log - forget these (: _stats isn't
>> available for
>>                    cluster iface and _log is removed. but recently
>> visited databases, active tasks and _users/_replicator quick
>> management is what could
>>                    be really handy.
>> 17:34:56 <+Kxepal> link to the user profile is also not relevant
>> anymore after backporting some cloudant features
>> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
>> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
>> believe you could make some builtin and leave a template one to let
>> the end users create
>>                    their own if they're able/would like to. in future
>> these are could be fauxton plugins or something.
>> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a hot
>> widget.
>> 17:39:56 <+robertkowalski> good idea - i can definitely help with that
>> (add custom widgets on build time) - the build is complicated, but
>> once explained
>>                            it should be easy
>> ```
>>
>> So we have "custom widgets", "cluster quick-management", " recently
>> visited databases",  "active tasks" and "_users/_replicator quick
>> management"
>>
>> I think two good widgets for starting are active tasks and recently
>> visited databases.
>>
>> For active tasks we have some nice docs:
>>
>> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>>
>> They have an own dedicated page in Fauxton (see
>> http://localhost:8000/#/activetasks) but a short quick condensed list
>> is probably very interesting to users.
>>
>> For the recently visited databases we would have to store that somewhere.
>>
>> If you want, you can take an existing page in Fauxton and just modify
>> the markup for a design mockup how the widget view may look like. But
>> feel also free to use pen/paper or other tools if you like that the
>> most.
>>
>> For the mango feature I am currently working on, I took the "edit
>> view" template on modified the markup using the Chrome inspector of my
>> browser to collect some first feedback from the project members and my
>> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
>> functionality, but gives other folks a rough idea what my idea for the
>> feature is.
>>
>> the framework and react
>>
>> As I already mentioned we are using React.js.
>>
>> It would be nice if you can finish the tutorial at
>> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
>> until next friday by following the steps and writing that code. After
>> that, read
>> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
>> to get a first impression how the Flux pattern works that we are
>> using.
>>
>> After that (if you still have time left) take a look on a component
>> that Garren, my coworker refactored from Backbone.js to React:
>>
>>
>> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>>
>> Please take a look how the data flows from the Components, using the
>> Actions, to the dispatcher at the Store. Feel free to litter
>> everything in the code with console.log to see how state changes and
>> how the data flows.
>>
>> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>>
>>
>> If you still have time, just try to create another menu item, called
>> "Dashboard". Take a look at:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>>
>> to get a first idea how to do that. Some background information:
>>
>> base.js - the starting point of our module. basic configuration is done
>> here
>> Question: what is `base.js` used for in the case of the config module?
>>
>> routes.js - takes care that functions injecting the view into the
>> layout are called depending on the url given
>> Question: What happens if I call `http:localhost:8000/_config` and
>> what happens if you remove the function `apiUrl`?
>>
>> views.js - contains our views - this file contains still a lot
>> backbone views, which we are currently migrating to react. maybe it
>> makes more sense to take a look at one of our react components:
>>
>>
>> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>>
>> and how they are used currently (as we are migrating to react currently):
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>>
>> The Objects are injected into the closures using AMD:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>>
>> assets folder:
>> contains our less which is compiled to css
>>
>> templates folder:
>> contains old backbone.js templates, you will not need them
>>
>> tests folder:
>> contains unit and integration tests, every PR must have unit tests and
>> integration tests. If you never wrote tests, we will explain it to you
>> - it is easy once you wrote your first few ones. Basically you are
>> testing each time that if you put something into a function, the
>> expected result happens. Or that if you take an action, a state has
>> changed.
>>
>> You can run the unit tests using `grunt test`
>>
>> Single tests are run by:
>>
>> ```
>> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
>> ```
>>
>> or in the browser by test group:
>>
>> ```
>>
>> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
>> ```
>>
>> (change path to your fauxton directory)
>>
>> The corresponding code is:
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>>
>> and these tests are a good example how to write a simple test for the
>> hello world/hello from dulanga-component:
>>
>>
>> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>>
>>
>> First steps:
>>
>> Create a module `dashboard` that gets displayed in the sidebar. The
>> route http://localhost:8000/dash will render a small React component
>> that display "Hello World".
>>
>> If you click on the "Hello World" it ill change the content to: "Hello
>> from Dulanga"
>>
>> While we will throw the small component away afterwards we will build
>> upon the other code you created. If you have time left, add a test
>> that the component changes the content.
>>
>>
>> Meeting Wednesday:
>> Feel free to join us on our weekly couchdb meeting:
>>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>>
>> I will be around at least one hour before so we can chat. Contact me
>> if you would like to chat earlier/later. I am also around the other
>> days on IRC / the mailinglist and feel free to contact me in
>> #couchdb-dev at any time. If I am not around I will answer you once I
>> got online again, as I read the backlog.
>>
>>
>> Our checklist at Wednesday (lets see how far we'll get)
>>
>>  - check out the active tasks api (linked on top of this mail)
>>  - a mockup showing some widgets and how they could look like
>>  - code React tutorial & read about Flux
>>  - take a look how we are using React
>>  - create another menu item, called "Dashboard", try to answer the
>> questions to route.js et al
>>  - get familiar how we test our code
>>  - write an hello world / hello from dulanga component that is
>> rendered into a screen when opening http://localhost:8000/dash or by
>> clicking on "dashboard" in the sidebar
>>
>> That was a lot of content and please don't feel discouraged if you
>> don't get that far until Wednesday. We will have to find a speed which
>> is perfect for you and this time I tried to give enough informations
>> that you are not blocked until Wednesday by waiting for next steps. If
>> you are at the last step before Wednesday, drop me a line and I will
>> prepare the next steps :)
>>
>> I know that you all have important exams, these are definitely more
>> important! Don't feel pressured by the amount of work / the amount of
>> informations, getting good results in the exams should be your first
>> priority.
>>
>> Best,
>> Robert
>>
>> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi Robert,
>> >
>> > I went through the guidelines you provided and successfully installed and
>> > configured as you said. Everything works find and I played around it by
>> > creating a database and documents. I think I am ready for the next step
>> and
>> > we can start it if you are ok :)
>> >
>> > Thank You
>> >
>> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>> >
>> >> You're welcome.
>> >>
>> >> I also hang out in the couchdb-dev channel for around 1-3hrs if you get
>> >> stuck!
>> >>
>> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com>
>> >> wrote:
>> >> > Hi Robert,
>> >> >
>> >> > Thank you very much for the quick reply. I will go through the
>> guidelines
>> >> > and contact you if I have any issue with them.
>> >> >
>> >> > Thank you
>> >> >
>> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd>
>> >> wrote:
>> >> >
>> >> >> Hi Dulanga,
>> >> >>
>> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
>> >> >>
>> >> >> CouchDB is a database written in Erlang with an HTTP API - that makes
>> >> >> it a great fit for web applications that don't need a server side
>> >> >> layer with a database driver in between. Our Project Fauxton (like a
>> >> >> modern PHP MyAdmin) makes use of that fact.
>> >> >>
>> >> >> Many of us hang out in freenode in #couchdb-dev including myself.
>> >> >> Whenever you get stuck, feel free to ask - if no one is online (e.g.
>> I
>> >> >> was travelling this week) feel free to ask on the dev ML.
>> >> >>
>> >> >> We are all happy to help each other in the project :)
>> >> >>
>> >> >> If you are using windows: I am not a Windows expert - you will
>> >> >> probably have to use a bash emulator like "git bash" to boot the dev
>> >> >> environment.
>> >> >>
>> >> >> Getting started:
>> >> >>
>> >> >> For this project you will need to install at least CouchDB 1.x, an
>> >> >> Ubuntu package (with installation instructions) is at
>> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>> >> >>
>> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install from
>> >> >> https://nodejs.org)
>> >> >>
>> >> >> Booting Fauxton and first steps (type without the $):
>> >> >>
>> >> >> booting CouchDB:
>> >> >> $ sudo couchdb
>> >> >>
>> >> >> in another terminal, clone the admin interface:
>> >> >> $ git clone https://github.com/apache/couchdb-fauxton
>> >> >>
>> >> >> go to Fauxton:
>> >> >> $ cd couchdb-fauxton
>> >> >>
>> >> >> install dependencies:
>> >> >> $ npm install
>> >> >> $ npm install -g grunt grunt-cli
>> >> >>
>> >> >> boot the app:
>> >> >> $ grunt dev
>> >> >>
>> >> >> Then open your browser and go to http://localhost:8000 - you should
>> >> >> see a red/gray/black interface
>> >> >>
>> >> >>
>> >> >> That was a lot of input and especially if you are using Linux the
>> >> >> first time and followed the instructions you have archived a lot!
>> >> >>
>> >> >> As first step, try to create a database and a document now using the
>> >> >> web interface (PS we are happy about any usability feedback). :)
>> >> >>
>> >> >> I think you have your dev environment for CouchDB ready now.
>> >> >>
>> >> >> What's next:
>> >> >> If everything works we will take a look at Fauxtons code structure
>> and
>> >> >> how it works. We will also talk about the features of the dashboard.
>> >> >> Let's find a date for a chat after you took a first look how Fauxton
>> >> >> looks like.
>> >> >>
>> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
>> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
>> >> >> (see
>> >> >>
>> >>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >> >> )
>> >> >> . Feel free to join us! I will be around 1hr before if you want to
>> >> >> chat with me before.
>> >> >>
>> >> >>
>> >> >> Looking forward to work with you,
>> >> >> Robert
>> >> >>
>> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
>> wadsashika@gmail.com>
>> >> >> wrote:
>> >> >> > Hi all,
>> >> >> >
>> >> >> > I am Dulanga Sashika and I am a final year undergraduate student at
>> >> >> > Computer Science and Engineering department at University of
>> Moratuwa,
>> >> >> Sri
>> >> >> > Lanka. I am really interested in java, java script, web
>> applications,
>> >> >> > algorithms, data mining and machine learning. I have 6 months of
>> >> training
>> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
>> >> >> application
>> >> >> > that used java, JEE and Spring Framework. My final year project
>> also a
>> >> >> web
>> >> >> > related application and I used same technologies I mentioned above
>> for
>> >> >> > that. I am really interested in this project because I have a good
>> >> >> > experience with web applications and I love work with javascript.
>> I am
>> >> >> > looking forward to contribute to this project in this summer. I
>> like
>> >> to
>> >> >> > know more detail about this project and if you can, please guide
>> me to
>> >> >> > start working on this project.
>> >> >> >
>> >> >> > Thank you.
>> >> >> >
>> >> >> > W. A. Dulanga Sashika,
>> >> >> > Undergraduate Student,
>> >> >> > Department of Computer Science and Engineering,
>> >> >> > University of Moratuwa.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > W. A. Dulanga Sashika,
>> >> > Undergraduate Student,
>> >> > Department of Computer Science and Engineering,
>> >> > University of Moratuwa.
>> >>
>> >
>> >
>> >
>> > --
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Here is the current status of the checklist :)

 - check out the active tasks api (linked on top of this mail) - (finished)
 - a mockup showing some widgets and how they could look like - (started
but not finished yet)
 - code React tutorial & read about Flux - (finished)
 - take a look how we are using React - (finished)
 - create another menu item, called "Dashboard", try to answer the
questions to route.js et al - (started but not finished yet)
 - get familiar how we test our code - (finished)
 - write an hello world / hello from dulanga component that is
rendered into a screen when opening http://localhost:8000/dash or by
clicking on "dashboard" in the sidebar - (started but not finished yet)

I will do my best to complete all these by tomorrow. If I have any problem,
I will trouble you as you wished yesterday :)

Thank You

On Mon, Mar 16, 2015 at 3:15 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga,
>
> we already talked on irc and you already talked to Alex regarding
> features for our dashboard. That's great!
>
> Some topics will repeat in this mail, but I also would like the ML to
> follow our project and additionally add some more in-depth
> informations.
>
> Recap & additons
> =====
>
> As discussed we will work in an iterative approach and add widget
> after widget so if we run out of time, we will have something to
> deliver and don't have to throw everything away.
>
> Have you seen the "database" tab or the "config" tab in the sidebar on the
> left?
>
> Those are modules that we can hook into the Fauxton build, by
> configuration. I think the idea is to create a tab "dashboard" which
> is the default one after opening Fauxton in the browser. So you would
> build the dashboard for Fauxton as part of Fauxton.
>
> Alex ideas so far:
>
> ```
> 17:34:13 <+Kxepal> about from what to start...in issue there are some
> points about showing stats and log - forget these (: _stats isn't
> available for
>                    cluster iface and _log is removed. but recently
> visited databases, active tasks and _users/_replicator quick
> management is what could
>                    be really handy.
> 17:34:56 <+Kxepal> link to the user profile is also not relevant
> anymore after backporting some cloudant features
> 17:35:11 <+Kxepal> but still may be handy if you find a way how (:
> 17:36:54 <+Kxepal> if the implementation is a set of widgets, I
> believe you could make some builtin and leave a template one to let
> the end users create
>                    their own if they're able/would like to. in future
> these are could be fauxton plugins or something.
> 17:39:15 <+Kxepal> cluster quick-management is also nice idea for a hot
> widget.
> 17:39:56 <+robertkowalski> good idea - i can definitely help with that
> (add custom widgets on build time) - the build is complicated, but
> once explained
>                            it should be easy
> ```
>
> So we have "custom widgets", "cluster quick-management", " recently
> visited databases",  "active tasks" and "_users/_replicator quick
> management"
>
> I think two good widgets for starting are active tasks and recently
> visited databases.
>
> For active tasks we have some nice docs:
>
> https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks
>
> They have an own dedicated page in Fauxton (see
> http://localhost:8000/#/activetasks) but a short quick condensed list
> is probably very interesting to users.
>
> For the recently visited databases we would have to store that somewhere.
>
> If you want, you can take an existing page in Fauxton and just modify
> the markup for a design mockup how the widget view may look like. But
> feel also free to use pen/paper or other tools if you like that the
> most.
>
> For the mango feature I am currently working on, I took the "edit
> view" template on modified the markup using the Chrome inspector of my
> browser to collect some first feedback from the project members and my
> team (https://cloudup.com/c26xgbWb6Ur). It does not have any
> functionality, but gives other folks a rough idea what my idea for the
> feature is.
>
> the framework and react
>
> As I already mentioned we are using React.js.
>
> It would be nice if you can finish the tutorial at
> https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
> until next friday by following the steps and writing that code. After
> that, read
> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
> to get a first impression how the Flux pattern works that we are
> using.
>
> After that (if you still have time left) take a look on a component
> that Garren, my coworker refactored from Backbone.js to React:
>
>
> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602
>
> Please take a look how the data flows from the Components, using the
> Actions, to the dispatcher at the Store. Feel free to litter
> everything in the code with console.log to see how state changes and
> how the data flows.
>
> Hint: it is that element: https://cldup.com/4eCHVt9HHt.png
>
>
> If you still have time, just try to create another menu item, called
> "Dashboard". Take a look at:
>
>
> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config
>
> to get a first idea how to do that. Some background information:
>
> base.js - the starting point of our module. basic configuration is done
> here
> Question: what is `base.js` used for in the case of the config module?
>
> routes.js - takes care that functions injecting the view into the
> layout are called depending on the url given
> Question: What happens if I call `http:localhost:8000/_config` and
> what happens if you remove the function `apiUrl`?
>
> views.js - contains our views - this file contains still a lot
> backbone views, which we are currently migrating to react. maybe it
> makes more sense to take a look at one of our react components:
>
>
> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes
>
> and how they are used currently (as we are migrating to react currently):
>
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31
>
> The Objects are injected into the closures using AMD:
>
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24
>
> assets folder:
> contains our less which is compiled to css
>
> templates folder:
> contains old backbone.js templates, you will not need them
>
> tests folder:
> contains unit and integration tests, every PR must have unit tests and
> integration tests. If you never wrote tests, we will explain it to you
> - it is easy once you wrote your first few ones. Basically you are
> testing each time that if you put something into a function, the
> expected result happens. Or that if you take an action, a state has
> changed.
>
> You can run the unit tests using `grunt test`
>
> Single tests are run by:
>
> ```
> grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
> ```
>
> or in the browser by test group:
>
> ```
>
> file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
> ```
>
> (change path to your fauxton directory)
>
> The corresponding code is:
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx
>
> and these tests are a good example how to write a simple test for the
> hello world/hello from dulanga-component:
>
>
> https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61
>
>
> First steps:
>
> Create a module `dashboard` that gets displayed in the sidebar. The
> route http://localhost:8000/dash will render a small React component
> that display "Hello World".
>
> If you click on the "Hello World" it ill change the content to: "Hello
> from Dulanga"
>
> While we will throw the small component away afterwards we will build
> upon the other code you created. If you have time left, add a test
> that the component changes the content.
>
>
> Meeting Wednesday:
> Feel free to join us on our weekly couchdb meeting:
>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>
> I will be around at least one hour before so we can chat. Contact me
> if you would like to chat earlier/later. I am also around the other
> days on IRC / the mailinglist and feel free to contact me in
> #couchdb-dev at any time. If I am not around I will answer you once I
> got online again, as I read the backlog.
>
>
> Our checklist at Wednesday (lets see how far we'll get)
>
>  - check out the active tasks api (linked on top of this mail)
>  - a mockup showing some widgets and how they could look like
>  - code React tutorial & read about Flux
>  - take a look how we are using React
>  - create another menu item, called "Dashboard", try to answer the
> questions to route.js et al
>  - get familiar how we test our code
>  - write an hello world / hello from dulanga component that is
> rendered into a screen when opening http://localhost:8000/dash or by
> clicking on "dashboard" in the sidebar
>
> That was a lot of content and please don't feel discouraged if you
> don't get that far until Wednesday. We will have to find a speed which
> is perfect for you and this time I tried to give enough informations
> that you are not blocked until Wednesday by waiting for next steps. If
> you are at the last step before Wednesday, drop me a line and I will
> prepare the next steps :)
>
> I know that you all have important exams, these are definitely more
> important! Don't feel pressured by the amount of work / the amount of
> informations, getting good results in the exams should be your first
> priority.
>
> Best,
> Robert
>
> On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi Robert,
> >
> > I went through the guidelines you provided and successfully installed and
> > configured as you said. Everything works find and I played around it by
> > creating a database and documents. I think I am ready for the next step
> and
> > we can start it if you are ok :)
> >
> > Thank You
> >
> > On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >
> >> You're welcome.
> >>
> >> I also hang out in the couchdb-dev channel for around 1-3hrs if you get
> >> stuck!
> >>
> >> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com>
> >> wrote:
> >> > Hi Robert,
> >> >
> >> > Thank you very much for the quick reply. I will go through the
> guidelines
> >> > and contact you if I have any issue with them.
> >> >
> >> > Thank you
> >> >
> >> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd>
> >> wrote:
> >> >
> >> >> Hi Dulanga,
> >> >>
> >> >> glad you found your way to the CouchDB mailing list. Welcome :)
> >> >>
> >> >> CouchDB is a database written in Erlang with an HTTP API - that makes
> >> >> it a great fit for web applications that don't need a server side
> >> >> layer with a database driver in between. Our Project Fauxton (like a
> >> >> modern PHP MyAdmin) makes use of that fact.
> >> >>
> >> >> Many of us hang out in freenode in #couchdb-dev including myself.
> >> >> Whenever you get stuck, feel free to ask - if no one is online (e.g.
> I
> >> >> was travelling this week) feel free to ask on the dev ML.
> >> >>
> >> >> We are all happy to help each other in the project :)
> >> >>
> >> >> If you are using windows: I am not a Windows expert - you will
> >> >> probably have to use a bash emulator like "git bash" to boot the dev
> >> >> environment.
> >> >>
> >> >> Getting started:
> >> >>
> >> >> For this project you will need to install at least CouchDB 1.x, an
> >> >> Ubuntu package (with installation instructions) is at
> >> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >> >>
> >> >> Additionally you need to install Node.js 0.10 or 0.12 (install from
> >> >> https://nodejs.org)
> >> >>
> >> >> Booting Fauxton and first steps (type without the $):
> >> >>
> >> >> booting CouchDB:
> >> >> $ sudo couchdb
> >> >>
> >> >> in another terminal, clone the admin interface:
> >> >> $ git clone https://github.com/apache/couchdb-fauxton
> >> >>
> >> >> go to Fauxton:
> >> >> $ cd couchdb-fauxton
> >> >>
> >> >> install dependencies:
> >> >> $ npm install
> >> >> $ npm install -g grunt grunt-cli
> >> >>
> >> >> boot the app:
> >> >> $ grunt dev
> >> >>
> >> >> Then open your browser and go to http://localhost:8000 - you should
> >> >> see a red/gray/black interface
> >> >>
> >> >>
> >> >> That was a lot of input and especially if you are using Linux the
> >> >> first time and followed the instructions you have archived a lot!
> >> >>
> >> >> As first step, try to create a database and a document now using the
> >> >> web interface (PS we are happy about any usability feedback). :)
> >> >>
> >> >> I think you have your dev environment for CouchDB ready now.
> >> >>
> >> >> What's next:
> >> >> If everything works we will take a look at Fauxtons code structure
> and
> >> >> how it works. We will also talk about the features of the dashboard.
> >> >> Let's find a date for a chat after you took a first look how Fauxton
> >> >> looks like.
> >> >>
> >> >> We are having our weekly meeting this Wednesday, 20:00GMT
> >> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
> >> >> (see
> >> >>
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> >> )
> >> >> . Feel free to join us! I will be around 1hr before if you want to
> >> >> chat with me before.
> >> >>
> >> >>
> >> >> Looking forward to work with you,
> >> >> Robert
> >> >>
> >> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <
> wadsashika@gmail.com>
> >> >> wrote:
> >> >> > Hi all,
> >> >> >
> >> >> > I am Dulanga Sashika and I am a final year undergraduate student at
> >> >> > Computer Science and Engineering department at University of
> Moratuwa,
> >> >> Sri
> >> >> > Lanka. I am really interested in java, java script, web
> applications,
> >> >> > algorithms, data mining and machine learning. I have 6 months of
> >> training
> >> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
> >> >> application
> >> >> > that used java, JEE and Spring Framework. My final year project
> also a
> >> >> web
> >> >> > related application and I used same technologies I mentioned above
> for
> >> >> > that. I am really interested in this project because I have a good
> >> >> > experience with web applications and I love work with javascript.
> I am
> >> >> > looking forward to contribute to this project in this summer. I
> like
> >> to
> >> >> > know more detail about this project and if you can, please guide
> me to
> >> >> > start working on this project.
> >> >> >
> >> >> > Thank you.
> >> >> >
> >> >> > W. A. Dulanga Sashika,
> >> >> > Undergraduate Student,
> >> >> > Department of Computer Science and Engineering,
> >> >> > University of Moratuwa.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > W. A. Dulanga Sashika,
> >> > Undergraduate Student,
> >> > Department of Computer Science and Engineering,
> >> > University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga,

we already talked on irc and you already talked to Alex regarding
features for our dashboard. That's great!

Some topics will repeat in this mail, but I also would like the ML to
follow our project and additionally add some more in-depth
informations.

Recap & additons
=====

As discussed we will work in an iterative approach and add widget
after widget so if we run out of time, we will have something to
deliver and don't have to throw everything away.

Have you seen the "database" tab or the "config" tab in the sidebar on the left?

Those are modules that we can hook into the Fauxton build, by
configuration. I think the idea is to create a tab "dashboard" which
is the default one after opening Fauxton in the browser. So you would
build the dashboard for Fauxton as part of Fauxton.

Alex ideas so far:

```
17:34:13 <+Kxepal> about from what to start...in issue there are some
points about showing stats and log - forget these (: _stats isn't
available for
                   cluster iface and _log is removed. but recently
visited databases, active tasks and _users/_replicator quick
management is what could
                   be really handy.
17:34:56 <+Kxepal> link to the user profile is also not relevant
anymore after backporting some cloudant features
17:35:11 <+Kxepal> but still may be handy if you find a way how (:
17:36:54 <+Kxepal> if the implementation is a set of widgets, I
believe you could make some builtin and leave a template one to let
the end users create
                   their own if they're able/would like to. in future
these are could be fauxton plugins or something.
17:39:15 <+Kxepal> cluster quick-management is also nice idea for a hot widget.
17:39:56 <+robertkowalski> good idea - i can definitely help with that
(add custom widgets on build time) - the build is complicated, but
once explained
                           it should be easy
```

So we have "custom widgets", "cluster quick-management", " recently
visited databases",  "active tasks" and "_users/_replicator quick
management"

I think two good widgets for starting are active tasks and recently
visited databases.

For active tasks we have some nice docs:
https://couchdb.readthedocs.org/en/1.6.1/api/server/common.html#get--_active_tasks

They have an own dedicated page in Fauxton (see
http://localhost:8000/#/activetasks) but a short quick condensed list
is probably very interesting to users.

For the recently visited databases we would have to store that somewhere.

If you want, you can take an existing page in Fauxton and just modify
the markup for a design mockup how the widget view may look like. But
feel also free to use pen/paper or other tools if you like that the
most.

For the mango feature I am currently working on, I took the "edit
view" template on modified the markup using the Chrome inspector of my
browser to collect some first feedback from the project members and my
team (https://cloudup.com/c26xgbWb6Ur). It does not have any
functionality, but gives other folks a rough idea what my idea for the
feature is.

the framework and react

As I already mentioned we are using React.js.

It would be nice if you can finish the tutorial at
https://github.com/ryanflorence/react-training/tree/gh-pages/lessons
until next friday by following the steps and writing that code. After
that, read https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e
to get a first impression how the Flux pattern works that we are
using.

After that (if you still have time left) take a look on a component
that Garren, my coworker refactored from Backbone.js to React:

https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602

Please take a look how the data flows from the Components, using the
Actions, to the dispatcher at the Store. Feel free to litter
everything in the code with console.log to see how state changes and
how the data flows.

Hint: it is that element: https://cldup.com/4eCHVt9HHt.png


If you still have time, just try to create another menu item, called
"Dashboard". Take a look at:

https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8
https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config

to get a first idea how to do that. Some background information:

base.js - the starting point of our module. basic configuration is done here
Question: what is `base.js` used for in the case of the config module?

routes.js - takes care that functions injecting the view into the
layout are called depending on the url given
Question: What happens if I call `http:localhost:8000/_config` and
what happens if you remove the function `apiUrl`?

views.js - contains our views - this file contains still a lot
backbone views, which we are currently migrating to react. maybe it
makes more sense to take a look at one of our react components:

https://github.com/apache/couchdb-fauxton/tree/master/app/addons/documents/changes

and how they are used currently (as we are migrating to react currently):

https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/routes-documents.js#L195
https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L31

The Objects are injected into the closures using AMD:

https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js#L13-24

assets folder:
contains our less which is compiled to css

templates folder:
contains old backbone.js templates, you will not need them

tests folder:
contains unit and integration tests, every PR must have unit tests and
integration tests. If you never wrote tests, we will explain it to you
- it is easy once you wrote your first few ones. Basically you are
testing each time that if you put something into a function, the
expected result happens. Or that if you take an action, a state has
changed.

You can run the unit tests using `grunt test`

Single tests are run by:

```
grunt test --file="./app/addons/documents/tests/headerSpec.react.js"
```

or in the browser by test group:

```
file:///Users/robert/apache/couchdb-fauxton/test/runner.html?grep=Header%20Controller
```

(change path to your fauxton directory)

The corresponding code is:
https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx

and these tests are a good example how to write a simple test for the
hello world/hello from dulanga-component:

https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/tests/headerSpec.react.jsx#L43-61


First steps:

Create a module `dashboard` that gets displayed in the sidebar. The
route http://localhost:8000/dash will render a small React component
that display "Hello World".

If you click on the "Hello World" it ill change the content to: "Hello
from Dulanga"

While we will throw the small component away afterwards we will build
upon the other code you created. If you have time left, add a test
that the component changes the content.


Meeting Wednesday:
Feel free to join us on our weekly couchdb meeting:
http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E

I will be around at least one hour before so we can chat. Contact me
if you would like to chat earlier/later. I am also around the other
days on IRC / the mailinglist and feel free to contact me in
#couchdb-dev at any time. If I am not around I will answer you once I
got online again, as I read the backlog.


Our checklist at Wednesday (lets see how far we'll get)

 - check out the active tasks api (linked on top of this mail)
 - a mockup showing some widgets and how they could look like
 - code React tutorial & read about Flux
 - take a look how we are using React
 - create another menu item, called "Dashboard", try to answer the
questions to route.js et al
 - get familiar how we test our code
 - write an hello world / hello from dulanga component that is
rendered into a screen when opening http://localhost:8000/dash or by
clicking on "dashboard" in the sidebar

That was a lot of content and please don't feel discouraged if you
don't get that far until Wednesday. We will have to find a speed which
is perfect for you and this time I tried to give enough informations
that you are not blocked until Wednesday by waiting for next steps. If
you are at the last step before Wednesday, drop me a line and I will
prepare the next steps :)

I know that you all have important exams, these are definitely more
important! Don't feel pressured by the amount of work / the amount of
informations, getting good results in the exams should be your first
priority.

Best,
Robert

On Sat, Mar 14, 2015 at 9:14 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> I went through the guidelines you provided and successfully installed and
> configured as you said. Everything works find and I played around it by
> creating a database and documents. I think I am ready for the next step and
> we can start it if you are ok :)
>
> Thank You
>
> On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> You're welcome.
>>
>> I also hang out in the couchdb-dev channel for around 1-3hrs if you get
>> stuck!
>>
>> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi Robert,
>> >
>> > Thank you very much for the quick reply. I will go through the guidelines
>> > and contact you if I have any issue with them.
>> >
>> > Thank you
>> >
>> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd>
>> wrote:
>> >
>> >> Hi Dulanga,
>> >>
>> >> glad you found your way to the CouchDB mailing list. Welcome :)
>> >>
>> >> CouchDB is a database written in Erlang with an HTTP API - that makes
>> >> it a great fit for web applications that don't need a server side
>> >> layer with a database driver in between. Our Project Fauxton (like a
>> >> modern PHP MyAdmin) makes use of that fact.
>> >>
>> >> Many of us hang out in freenode in #couchdb-dev including myself.
>> >> Whenever you get stuck, feel free to ask - if no one is online (e.g. I
>> >> was travelling this week) feel free to ask on the dev ML.
>> >>
>> >> We are all happy to help each other in the project :)
>> >>
>> >> If you are using windows: I am not a Windows expert - you will
>> >> probably have to use a bash emulator like "git bash" to boot the dev
>> >> environment.
>> >>
>> >> Getting started:
>> >>
>> >> For this project you will need to install at least CouchDB 1.x, an
>> >> Ubuntu package (with installation instructions) is at
>> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>> >>
>> >> Additionally you need to install Node.js 0.10 or 0.12 (install from
>> >> https://nodejs.org)
>> >>
>> >> Booting Fauxton and first steps (type without the $):
>> >>
>> >> booting CouchDB:
>> >> $ sudo couchdb
>> >>
>> >> in another terminal, clone the admin interface:
>> >> $ git clone https://github.com/apache/couchdb-fauxton
>> >>
>> >> go to Fauxton:
>> >> $ cd couchdb-fauxton
>> >>
>> >> install dependencies:
>> >> $ npm install
>> >> $ npm install -g grunt grunt-cli
>> >>
>> >> boot the app:
>> >> $ grunt dev
>> >>
>> >> Then open your browser and go to http://localhost:8000 - you should
>> >> see a red/gray/black interface
>> >>
>> >>
>> >> That was a lot of input and especially if you are using Linux the
>> >> first time and followed the instructions you have archived a lot!
>> >>
>> >> As first step, try to create a database and a document now using the
>> >> web interface (PS we are happy about any usability feedback). :)
>> >>
>> >> I think you have your dev environment for CouchDB ready now.
>> >>
>> >> What's next:
>> >> If everything works we will take a look at Fauxtons code structure and
>> >> how it works. We will also talk about the features of the dashboard.
>> >> Let's find a date for a chat after you took a first look how Fauxton
>> >> looks like.
>> >>
>> >> We are having our weekly meeting this Wednesday, 20:00GMT
>> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
>> >> (see
>> >>
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> >> )
>> >> . Feel free to join us! I will be around 1hr before if you want to
>> >> chat with me before.
>> >>
>> >>
>> >> Looking forward to work with you,
>> >> Robert
>> >>
>> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <wa...@gmail.com>
>> >> wrote:
>> >> > Hi all,
>> >> >
>> >> > I am Dulanga Sashika and I am a final year undergraduate student at
>> >> > Computer Science and Engineering department at University of Moratuwa,
>> >> Sri
>> >> > Lanka. I am really interested in java, java script, web applications,
>> >> > algorithms, data mining and machine learning. I have 6 months of
>> training
>> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
>> >> application
>> >> > that used java, JEE and Spring Framework. My final year project also a
>> >> web
>> >> > related application and I used same technologies I mentioned above for
>> >> > that. I am really interested in this project because I have a good
>> >> > experience with web applications and I love work with javascript. I am
>> >> > looking forward to contribute to this project in this summer. I like
>> to
>> >> > know more detail about this project and if you can, please guide me to
>> >> > start working on this project.
>> >> >
>> >> > Thank you.
>> >> >
>> >> > W. A. Dulanga Sashika,
>> >> > Undergraduate Student,
>> >> > Department of Computer Science and Engineering,
>> >> > University of Moratuwa.
>> >>
>> >
>> >
>> >
>> > --
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

I went through the guidelines you provided and successfully installed and
configured as you said. Everything works find and I played around it by
creating a database and documents. I think I am ready for the next step and
we can start it if you are ok :)

Thank You

On Sun, Mar 15, 2015 at 12:03 AM, Robert Kowalski <ro...@kowalski.gd> wrote:

> You're welcome.
>
> I also hang out in the couchdb-dev channel for around 1-3hrs if you get
> stuck!
>
> On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi Robert,
> >
> > Thank you very much for the quick reply. I will go through the guidelines
> > and contact you if I have any issue with them.
> >
> > Thank you
> >
> > On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd>
> wrote:
> >
> >> Hi Dulanga,
> >>
> >> glad you found your way to the CouchDB mailing list. Welcome :)
> >>
> >> CouchDB is a database written in Erlang with an HTTP API - that makes
> >> it a great fit for web applications that don't need a server side
> >> layer with a database driver in between. Our Project Fauxton (like a
> >> modern PHP MyAdmin) makes use of that fact.
> >>
> >> Many of us hang out in freenode in #couchdb-dev including myself.
> >> Whenever you get stuck, feel free to ask - if no one is online (e.g. I
> >> was travelling this week) feel free to ask on the dev ML.
> >>
> >> We are all happy to help each other in the project :)
> >>
> >> If you are using windows: I am not a Windows expert - you will
> >> probably have to use a bash emulator like "git bash" to boot the dev
> >> environment.
> >>
> >> Getting started:
> >>
> >> For this project you will need to install at least CouchDB 1.x, an
> >> Ubuntu package (with installation instructions) is at
> >> https://launchpad.net/~couchdb/+archive/ubuntu/stable
> >>
> >> Additionally you need to install Node.js 0.10 or 0.12 (install from
> >> https://nodejs.org)
> >>
> >> Booting Fauxton and first steps (type without the $):
> >>
> >> booting CouchDB:
> >> $ sudo couchdb
> >>
> >> in another terminal, clone the admin interface:
> >> $ git clone https://github.com/apache/couchdb-fauxton
> >>
> >> go to Fauxton:
> >> $ cd couchdb-fauxton
> >>
> >> install dependencies:
> >> $ npm install
> >> $ npm install -g grunt grunt-cli
> >>
> >> boot the app:
> >> $ grunt dev
> >>
> >> Then open your browser and go to http://localhost:8000 - you should
> >> see a red/gray/black interface
> >>
> >>
> >> That was a lot of input and especially if you are using Linux the
> >> first time and followed the instructions you have archived a lot!
> >>
> >> As first step, try to create a database and a document now using the
> >> web interface (PS we are happy about any usability feedback). :)
> >>
> >> I think you have your dev environment for CouchDB ready now.
> >>
> >> What's next:
> >> If everything works we will take a look at Fauxtons code structure and
> >> how it works. We will also talk about the features of the dashboard.
> >> Let's find a date for a chat after you took a first look how Fauxton
> >> looks like.
> >>
> >> We are having our weekly meeting this Wednesday, 20:00GMT
> >> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
> >> (see
> >>
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> >> )
> >> . Feel free to join us! I will be around 1hr before if you want to
> >> chat with me before.
> >>
> >>
> >> Looking forward to work with you,
> >> Robert
> >>
> >> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <wa...@gmail.com>
> >> wrote:
> >> > Hi all,
> >> >
> >> > I am Dulanga Sashika and I am a final year undergraduate student at
> >> > Computer Science and Engineering department at University of Moratuwa,
> >> Sri
> >> > Lanka. I am really interested in java, java script, web applications,
> >> > algorithms, data mining and machine learning. I have 6 months of
> training
> >> > experience at Proavos (pvt) Ltd. and in there I worked on a web
> >> application
> >> > that used java, JEE and Spring Framework. My final year project also a
> >> web
> >> > related application and I used same technologies I mentioned above for
> >> > that. I am really interested in this project because I have a good
> >> > experience with web applications and I love work with javascript. I am
> >> > looking forward to contribute to this project in this summer. I like
> to
> >> > know more detail about this project and if you can, please guide me to
> >> > start working on this project.
> >> >
> >> > Thank you.
> >> >
> >> > W. A. Dulanga Sashika,
> >> > Undergraduate Student,
> >> > Department of Computer Science and Engineering,
> >> > University of Moratuwa.
> >>
> >
> >
> >
> > --
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

You're welcome.

I also hang out in the couchdb-dev channel for around 1-3hrs if you get stuck!

On Sat, Mar 14, 2015 at 7:29 PM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi Robert,
>
> Thank you very much for the quick reply. I will go through the guidelines
> and contact you if I have any issue with them.
>
> Thank you
>
> On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd> wrote:
>
>> Hi Dulanga,
>>
>> glad you found your way to the CouchDB mailing list. Welcome :)
>>
>> CouchDB is a database written in Erlang with an HTTP API - that makes
>> it a great fit for web applications that don't need a server side
>> layer with a database driver in between. Our Project Fauxton (like a
>> modern PHP MyAdmin) makes use of that fact.
>>
>> Many of us hang out in freenode in #couchdb-dev including myself.
>> Whenever you get stuck, feel free to ask - if no one is online (e.g. I
>> was travelling this week) feel free to ask on the dev ML.
>>
>> We are all happy to help each other in the project :)
>>
>> If you are using windows: I am not a Windows expert - you will
>> probably have to use a bash emulator like "git bash" to boot the dev
>> environment.
>>
>> Getting started:
>>
>> For this project you will need to install at least CouchDB 1.x, an
>> Ubuntu package (with installation instructions) is at
>> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>>
>> Additionally you need to install Node.js 0.10 or 0.12 (install from
>> https://nodejs.org)
>>
>> Booting Fauxton and first steps (type without the $):
>>
>> booting CouchDB:
>> $ sudo couchdb
>>
>> in another terminal, clone the admin interface:
>> $ git clone https://github.com/apache/couchdb-fauxton
>>
>> go to Fauxton:
>> $ cd couchdb-fauxton
>>
>> install dependencies:
>> $ npm install
>> $ npm install -g grunt grunt-cli
>>
>> boot the app:
>> $ grunt dev
>>
>> Then open your browser and go to http://localhost:8000 - you should
>> see a red/gray/black interface
>>
>>
>> That was a lot of input and especially if you are using Linux the
>> first time and followed the instructions you have archived a lot!
>>
>> As first step, try to create a database and a document now using the
>> web interface (PS we are happy about any usability feedback). :)
>>
>> I think you have your dev environment for CouchDB ready now.
>>
>> What's next:
>> If everything works we will take a look at Fauxtons code structure and
>> how it works. We will also talk about the features of the dashboard.
>> Let's find a date for a chat after you took a first look how Fauxton
>> looks like.
>>
>> We are having our weekly meeting this Wednesday, 20:00GMT
>> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
>> (see
>> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
>> )
>> . Feel free to join us! I will be around 1hr before if you want to
>> chat with me before.
>>
>>
>> Looking forward to work with you,
>> Robert
>>
>> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <wa...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > I am Dulanga Sashika and I am a final year undergraduate student at
>> > Computer Science and Engineering department at University of Moratuwa,
>> Sri
>> > Lanka. I am really interested in java, java script, web applications,
>> > algorithms, data mining and machine learning. I have 6 months of training
>> > experience at Proavos (pvt) Ltd. and in there I worked on a web
>> application
>> > that used java, JEE and Spring Framework. My final year project also a
>> web
>> > related application and I used same technologies I mentioned above for
>> > that. I am really interested in this project because I have a good
>> > experience with web applications and I love work with javascript. I am
>> > looking forward to contribute to this project in this summer. I like to
>> > know more detail about this project and if you can, please guide me to
>> > start working on this project.
>> >
>> > Thank you.
>> >
>> > W. A. Dulanga Sashika,
>> > Undergraduate Student,
>> > Department of Computer Science and Engineering,
>> > University of Moratuwa.
>>
>
>
>
> --
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Dulanga Sashika <wa...@gmail.com>]

Hi Robert,

Thank you very much for the quick reply. I will go through the guidelines
and contact you if I have any issue with them.

Thank you

On Sat, Mar 14, 2015 at 11:46 PM, Robert Kowalski <ro...@kowalski.gd> wrote:

> Hi Dulanga,
>
> glad you found your way to the CouchDB mailing list. Welcome :)
>
> CouchDB is a database written in Erlang with an HTTP API - that makes
> it a great fit for web applications that don't need a server side
> layer with a database driver in between. Our Project Fauxton (like a
> modern PHP MyAdmin) makes use of that fact.
>
> Many of us hang out in freenode in #couchdb-dev including myself.
> Whenever you get stuck, feel free to ask - if no one is online (e.g. I
> was travelling this week) feel free to ask on the dev ML.
>
> We are all happy to help each other in the project :)
>
> If you are using windows: I am not a Windows expert - you will
> probably have to use a bash emulator like "git bash" to boot the dev
> environment.
>
> Getting started:
>
> For this project you will need to install at least CouchDB 1.x, an
> Ubuntu package (with installation instructions) is at
> https://launchpad.net/~couchdb/+archive/ubuntu/stable
>
> Additionally you need to install Node.js 0.10 or 0.12 (install from
> https://nodejs.org)
>
> Booting Fauxton and first steps (type without the $):
>
> booting CouchDB:
> $ sudo couchdb
>
> in another terminal, clone the admin interface:
> $ git clone https://github.com/apache/couchdb-fauxton
>
> go to Fauxton:
> $ cd couchdb-fauxton
>
> install dependencies:
> $ npm install
> $ npm install -g grunt grunt-cli
>
> boot the app:
> $ grunt dev
>
> Then open your browser and go to http://localhost:8000 - you should
> see a red/gray/black interface
>
>
> That was a lot of input and especially if you are using Linux the
> first time and followed the instructions you have archived a lot!
>
> As first step, try to create a database and a document now using the
> web interface (PS we are happy about any usability feedback). :)
>
> I think you have your dev environment for CouchDB ready now.
>
> What's next:
> If everything works we will take a look at Fauxtons code structure and
> how it works. We will also talk about the features of the dashboard.
> Let's find a date for a chat after you took a first look how Fauxton
> looks like.
>
> We are having our weekly meeting this Wednesday, 20:00GMT
> (http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
> (see
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E
> )
> . Feel free to join us! I will be around 1hr before if you want to
> chat with me before.
>
>
> Looking forward to work with you,
> Robert
>
> On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <wa...@gmail.com>
> wrote:
> > Hi all,
> >
> > I am Dulanga Sashika and I am a final year undergraduate student at
> > Computer Science and Engineering department at University of Moratuwa,
> Sri
> > Lanka. I am really interested in java, java script, web applications,
> > algorithms, data mining and machine learning. I have 6 months of training
> > experience at Proavos (pvt) Ltd. and in there I worked on a web
> application
> > that used java, JEE and Spring Framework. My final year project also a
> web
> > related application and I used same technologies I mentioned above for
> > that. I am really interested in this project because I have a good
> > experience with web applications and I love work with javascript. I am
> > looking forward to contribute to this project in this summer. I like to
> > know more detail about this project and if you can, please guide me to
> > start working on this project.
> >
> > Thank you.
> >
> > W. A. Dulanga Sashika,
> > Undergraduate Student,
> > Department of Computer Science and Engineering,
> > University of Moratuwa.
>



-- 
W. A. Dulanga Sashika,
Undergraduate Student,
Department of Computer Science and Engineering,
University of Moratuwa.

Re: [COUCHDB-2214] Dashboard as main page

[Robert Kowalski <ro...@kowalski.gd>]

Hi Dulanga,

glad you found your way to the CouchDB mailing list. Welcome :)

CouchDB is a database written in Erlang with an HTTP API - that makes
it a great fit for web applications that don't need a server side
layer with a database driver in between. Our Project Fauxton (like a
modern PHP MyAdmin) makes use of that fact.

Many of us hang out in freenode in #couchdb-dev including myself.
Whenever you get stuck, feel free to ask - if no one is online (e.g. I
was travelling this week) feel free to ask on the dev ML.

We are all happy to help each other in the project :)

If you are using windows: I am not a Windows expert - you will
probably have to use a bash emulator like "git bash" to boot the dev
environment.

Getting started:

For this project you will need to install at least CouchDB 1.x, an
Ubuntu package (with installation instructions) is at
https://launchpad.net/~couchdb/+archive/ubuntu/stable

Additionally you need to install Node.js 0.10 or 0.12 (install from
https://nodejs.org)

Booting Fauxton and first steps (type without the $):

booting CouchDB:
$ sudo couchdb

in another terminal, clone the admin interface:
$ git clone https://github.com/apache/couchdb-fauxton

go to Fauxton:
$ cd couchdb-fauxton

install dependencies:
$ npm install
$ npm install -g grunt grunt-cli

boot the app:
$ grunt dev

Then open your browser and go to http://localhost:8000 - you should
see a red/gray/black interface


That was a lot of input and especially if you are using Linux the
first time and followed the instructions you have archived a lot!

As first step, try to create a database and a document now using the
web interface (PS we are happy about any usability feedback). :)

I think you have your dev environment for CouchDB ready now.

What's next:
If everything works we will take a look at Fauxtons code structure and
how it works. We will also talk about the features of the dashboard.
Let's find a date for a chat after you took a first look how Fauxton
looks like.

We are having our weekly meeting this Wednesday, 20:00GMT
(http://arewemeetingyet.com/UTC/2015-03-14/20:00) in IRC on freenode
(see http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3CCAJ1bcfEKOh4nvoxUqvcAcUFgg96w-JqHEefpi%2BWzazKFUPXNCg%40mail.gmail.com%3E)
. Feel free to join us! I will be around 1hr before if you want to
chat with me before.


Looking forward to work with you,
Robert

On Sat, Mar 14, 2015 at 7:55 AM, Dulanga Sashika <wa...@gmail.com> wrote:
> Hi all,
>
> I am Dulanga Sashika and I am a final year undergraduate student at
> Computer Science and Engineering department at University of Moratuwa, Sri
> Lanka. I am really interested in java, java script, web applications,
> algorithms, data mining and machine learning. I have 6 months of training
> experience at Proavos (pvt) Ltd. and in there I worked on a web application
> that used java, JEE and Spring Framework. My final year project also a web
> related application and I used same technologies I mentioned above for
> that. I am really interested in this project because I have a good
> experience with web applications and I love work with javascript. I am
> looking forward to contribute to this project in this summer. I like to
> know more detail about this project and if you can, please guide me to
> start working on this project.
>
> Thank you.
>
> W. A. Dulanga Sashika,
> Undergraduate Student,
> Department of Computer Science and Engineering,
> University of Moratuwa.