Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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.ph...@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 >>> 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 >>> wrote: >>> >>> Hi all, >>> >>> I implemented the first widg
Re: [COUCHDB-2214] Dashboard as main page
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 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.ph...@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 >> 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 >> 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 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 an
Re: [COUCHDB-2214] Dashboard as main page
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.ph...@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 > 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 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 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 >
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 >> 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 >>> wrote: >>> Problem solved :) thank you very much for the help Robert. On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski >> 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 > 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 < >> wadsash...@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 wrote: On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika < > wadsash...@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
Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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 > > wrote: > > > >> Problem solved :) thank you very much for the help Robert. > >> > >> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski > 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 > >>> 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 < > wadsash...@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 wrote: > >>> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika < > >>> wadsash...@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 dif
Re: [COUCHDB-2214] Dashboard as main page
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 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 > wrote: > >> Problem solved :) thank you very much for the help Robert. >> >> On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski 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 >>> 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 >> > >>> > 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 wrote: >>> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika < >>> wadsash...@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 M
Re: [COUCHDB-2214] Dashboard as main page
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 wrote: > Problem solved :) thank you very much for the help Robert. > > On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski 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 >> 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 > > >> > 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 wrote: >> >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika < >> wadsash...@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: [GSoC 2015][COUCHDB-2214] Dashboard as main page
hani-component, example: >> >> >> 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 Nishani" >> >> 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 >> to one of the test files and test that the component changes the content >> using >> our testframework Mocha. >> >> Best, >> Robert >> >> On Wed, Apr 1, 2015 at 10:54 AM, Ayola Jayamaha >> wrote: >> > Hi, >> > >> > Since by now I have successfully submitted the proposal can you point >> out >> > some of the resources / tutorials with regard to the codebase of >> CouchDB / >> > Fauxton, Architecture and how it works? >> > >> > Also if there exists tutorials on how to create plugins, addons, widgets >> > with React.js. >> > >> > It would help me proceed with the next steps on my proposal. >> > >> > Thanks in Advance. >> > >> > Best Regards, >> > Nishani. >> > >> > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > > >> > wrote: >> >> >> >> Hi All, >> >> >> >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 >> >> Dashboard as main page project interests me as I plan to attempt GSoC >> 2015 >> >> particularly due to it's active dev-mailing lists and my previous >> experience >> >> with creating dashboards and front-end development. >> >> >> >> Under the guidance of Robert Kowalski, Alexander Shorin I successfully >> >> built it and am ready to proceed with the next steps. They will be to >> get >> >> familiarized with Fauxton Code Structure and coming up with a good and >> >> useful feature list for the dashboard.[1] >> >> >> >> I have started writing the proposal and shall share it tomorrow with >> the >> >> expectancy of some good feedback that would help me improve. >> >> >> >> Looking forward in creating a nicer looking welcome page with useful >> >> information and summaries preferably with added charting. >> >> >> >> Thanks. >> >> >> >> [1] >> >> >> https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 >> >> >> >> BR, >> >> Nishani >> > >> > >> > >> > >> > -- >> > Best Regards, >> > Ayola Jayamaha >> > http://ayolajayamaha.blogspot.com/ >> > >> > >> >> On Wed, Apr 1, 2015 at 10:54 AM, Ayola Jayamaha >> wrote: >> > Hi, >> > >> > Since by now I have successfully submitted the proposal can you point >> out >> > some of the resources / tutorials with regard to the codebase of >> CouchDB / >> > Fauxton, Architecture and how it works? >> > >> > Also if there exists tutorials on how to create plugins, addons, widgets >> > with React.js. >> > >> > It would help me proceed with the next steps on my proposal. >> > >> > Thanks in Advance. >> > >> > Best Regards, >> > Nishani. >> > >> > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > > >> > wrote: >> >> >> >> Hi All, >> >> >> >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 >> >> Dashboard as main page project interests me as I plan to attempt GSoC >> 2015 >> >> particularly due to it's active dev-mailing lists and my previous >> experience >> >> with creating dashboards and front-end development. >> >> >> >> Under the guidance of Robert Kowalski, Alexander Shorin I successfully >> >> built it and am ready to proceed with the next steps. They will be to >> get >> >> familiarized with Fauxton Code Structure and coming up with a good and >> >> useful feature list for the dashboard.[1] >> >> >> >> I have started writing the proposal and shall share it tomorrow with >> the >> >> expectancy of some good feedback that would help me improve. >> >> >> >> Looking forward in creating a nicer looking welcome page with useful >> >> information and summaries preferably with added charting. >> >> >> >> Thanks. >> >> >> >> [1] >> >> >> https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 >> >> >> >> BR, >> >> Nishani >> > >> > >> > >> > >> > -- >> > Best Regards, >> > Ayola Jayamaha >> > http://ayolajayamaha.blogspot.com/ >> > >> > >> > > > > -- > Best Regards, > Ayola Jayamaha > http://ayolajayamaha.blogspot.com/ > > > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [COUCHDB-2214] Dashboard as main page
Problem solved :) thank you very much for the help Robert. On Sat, Apr 4, 2015 at 11:54 PM, Robert Kowalski 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 > 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 > > 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 wrote: > >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika < > wadsash...@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
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 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 > 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 wrote: >> > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika >> > 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
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 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 wrote: > > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika > > 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: [GSoC 2015][COUCHDB-2214] Dashboard as main page
ha > wrote: > > Hi, > > > > Since by now I have successfully submitted the proposal can you point out > > some of the resources / tutorials with regard to the codebase of CouchDB > / > > Fauxton, Architecture and how it works? > > > > Also if there exists tutorials on how to create plugins, addons, widgets > > with React.js. > > > > It would help me proceed with the next steps on my proposal. > > > > Thanks in Advance. > > > > Best Regards, > > Nishani. > > > > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > > wrote: > >> > >> Hi All, > >> > >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 > >> Dashboard as main page project interests me as I plan to attempt GSoC > 2015 > >> particularly due to it's active dev-mailing lists and my previous > experience > >> with creating dashboards and front-end development. > >> > >> Under the guidance of Robert Kowalski, Alexander Shorin I successfully > >> built it and am ready to proceed with the next steps. They will be to > get > >> familiarized with Fauxton Code Structure and coming up with a good and > >> useful feature list for the dashboard.[1] > >> > >> I have started writing the proposal and shall share it tomorrow with the > >> expectancy of some good feedback that would help me improve. > >> > >> Looking forward in creating a nicer looking welcome page with useful > >> information and summaries preferably with added charting. > >> > >> Thanks. > >> > >> [1] > >> > https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 > >> > >> BR, > >> Nishani > > > > > > > > > > -- > > Best Regards, > > Ayola Jayamaha > > http://ayolajayamaha.blogspot.com/ > > > > > > On Wed, Apr 1, 2015 at 10:54 AM, Ayola Jayamaha > wrote: > > Hi, > > > > Since by now I have successfully submitted the proposal can you point out > > some of the resources / tutorials with regard to the codebase of CouchDB > / > > Fauxton, Architecture and how it works? > > > > Also if there exists tutorials on how to create plugins, addons, widgets > > with React.js. > > > > It would help me proceed with the next steps on my proposal. > > > > Thanks in Advance. > > > > Best Regards, > > Nishani. > > > > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > > wrote: > >> > >> Hi All, > >> > >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 > >> Dashboard as main page project interests me as I plan to attempt GSoC > 2015 > >> particularly due to it's active dev-mailing lists and my previous > experience > >> with creating dashboards and front-end development. > >> > >> Under the guidance of Robert Kowalski, Alexander Shorin I successfully > >> built it and am ready to proceed with the next steps. They will be to > get > >> familiarized with Fauxton Code Structure and coming up with a good and > >> useful feature list for the dashboard.[1] > >> > >> I have started writing the proposal and shall share it tomorrow with the > >> expectancy of some good feedback that would help me improve. > >> > >> Looking forward in creating a nicer looking welcome page with useful > >> information and summaries preferably with added charting. > >> > >> Thanks. > >> > >> [1] > >> > https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 > >> > >> BR, > >> Nishani > > > > > > > > > > -- > > Best Regards, > > Ayola Jayamaha > > http://ayolajayamaha.blogspot.com/ > > > > > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi Nishani, I wrote a small tutorial last week: 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. For an overview how Fauxton works, read: http://docs.couchdb.org/en/latest/fauxton/addons.html 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 nishani-component, example: 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 Nishani" 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 to one of the test files and test that the component changes the content using our testframework Mocha. Best, Robert On Wed, Apr 1, 2015 at 10:54 AM, Ayola Jayamaha wrote: > Hi, > > Since by now I have successfully submitted the proposal can you point out > some of the resources / tutorials with regard to the codebase of CouchDB / > Fauxton, Architecture and how it works? > > Also if there exists tutorials on how to create plugins, addons, widgets > with React.js. > > It would help me proceed with the next steps on my proposal. > > Thanks in Advance. > > Best Regards, > Nishani. > > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > wrote: >> >> Hi All, >> >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 >> Dashboard as main page project interests me as I plan to attempt GSoC 2015 >> particularly due
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi, Since by now I have successfully submitted the proposal can you point out some of the resources / tutorials with regard to the codebase of CouchDB / Fauxton, Architecture and how it works? Also if there exists tutorials on how to create plugins, addons, widgets with React.js. It would help me proceed with the next steps on my proposal. Thanks in Advance. Best Regards, Nishani. On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha wrote: > Hi All, > > I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 > Dashboard as main page project interests me as I plan to attempt GSoC 2015 > particularly due to it's active dev-mailing lists and my previous > experience with creating dashboards and front-end development. > > Under the guidance of Robert Kowalski, Alexander Shorin I successfully > built it and am ready to proceed with the next steps. They will be to get > familiarized with Fauxton Code Structure and coming up with a good and > useful feature list for the dashboard.[1] > > I have started writing the proposal and shall share it tomorrow with the > expectancy of some good feedback that would help me improve. > > Looking forward in creating a nicer looking welcome page with useful > information and summaries preferably with added charting. > > Thanks. > > [1] > https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 > > BR, > Nishani > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [jira] [Commented] (COUCHDB-2214) Dashboard as main page
Hi, I have uploaded my GSoC Proposal for CouchDB 2214 with the title as "Design a better Dashboard for CouchDB Fauxton UI with summary information ". I hope to continue working on it in par with the timeline until they announce if it's been accepted or not. Thanks. Regards, NIshani. On Fri, Mar 20, 2015 at 8:22 PM, Nishani (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371403#comment-14371403 > ] > > Nishani commented on COUCHDB-2214: > --- > > Hi Robert, > > I successfully built Couch 2.0 perview about 2 days ago and I put a > message regarding my progress. I went through the Fauxtons code structure > and also gave some thoughts on the features that needed to be added on the > dashboard. > > Unfortunately I was unable to attend the weekly meeting but I'm looking > forward to attend to the next. > > I'm currently writing my proposal and it would be great if you too can > give some feedback on it. > > I'm planing to discuss about the features of the dashboard and collect few > ideas from the community via the dev-mailing list. Hope everyone would > collaborate with it. > > So now I'm ready with proceeding with the 2 tasks you mentioned, Fauxton > code structure and how it works & discussion on features of the dashboard. > > Thanks. > > BR, > Nishani > > > > Dashboard as main page > > -- > > > > Key: COUCHDB-2214 > > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > > Project: CouchDB > > Issue Type: Improvement > > Security Level: public(Regular issues) > > Components: Fauxton > >Reporter: Alexander Shorin > > Labels: CouchDB, gsoc2015, javascript > > > > Currently, the main page of Fauxton is list of all databases on server. > While this representation is traditional and legacy from Futon, it would be > awesome to see there some dashboard of summary information. > > For instance, you're logged as admin. What Fauxton may show you on there? > > - Recently visited databases (COUCHDB-2112) > > - Active replications (+ active_tasks) > > - Some valuable stats like 500 / 401 HTTP errors > > - Recent log messages > > - Quick links for users / replicator databases, create new user/admin > > - Some field for alert message like: Fix the admin party. Warning! You > have the admin party and your CouchDB is accessible not only from > localhost. And some other recommendations (like raise max_open_databases in > case if you have a lot of dbs and stats tells that you're getting closer to > this limit), tip of the day etc. > > As for regular user there could be showed: > > - Recently visited databases > > - Link to his profile (doc in _users db) > > (whatelse may be useful for regular users?) > > In other words, it would be awesome to have nicer welcome page with > useful information as summary from other sources. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [COUCHDB-2214] Dashboard as main page
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 wrote: > On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika > 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
On Sat, Mar 21, 2015 at 11:00 PM, Dulanga Sashika 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
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 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 > 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 > 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
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, I just want to know how to extend the existing CouchDB Dashboard to include some widgets? Can we use plugins / addons to achieve such? Are there any particular tutorial for me to follow regarding the said? Which technology would you suggest suits best for my needs? Thanks. BR, Nishani http://ayolajayamaha.blogspot.com/ On Sun, Mar 22, 2015 at 11:56 PM, Ayola Jayamaha wrote: > Hi All, > > Shared here are the links to the mockup UIs that I came up with. > > (1) Image dashboard-custom-layout > > It shows you the Main Dashboard Page that you see when you run the Fauxton > Web UI. In this configuration you can see 6 widgets. The customizable > widget or the master widget is only visible to the administrator and he/she > could customize / manage the widgets that are shown to each user. It > facilitate each user having a different set of available tasks/widgets > according to his taste/permission level. > > https://www.dropbox.com/s/y6obhay0v788vp6/dashboard-custom-layout.png?dl=0 > > > (2) Image dashboard-main > > It shows all the widgets after the page is fully loaded. > >- Recently Visited Databases - Details of DB visited >- Active Tasks - DB, PID, % progress >- Cluster Quick Mgt. - Nodes, DBs, Docs, (details,resource >utilization,view,change) >- User Quick Mgt. - Groups, Permissions, Authorization Roles >- Replicator Quick Mgt. - Source, Target >- Configuration Quick Mgt. - httpd, cluster, user, stats(only on >cluster mode) > > Each widget contains a different UI component for better presentation ie > Bar charts, Trees, Maps,Tables ..etc > > https://www.dropbox.com/s/cmulskiopamqzbv/dashboard-main.png?dl=0 > > > (3) Image setting-active-task-widget > > It is shown when you click on the settings icon at the right corner of the > widget. The user have some limited control over selecting the actions > viewed on the widget. These permissions are defined by the authorization > level of the user. Based upon that the user is given the set of tasks > falling under the sub-category of that widget. > > eg: Active task widget > > > > https://www.dropbox.com/s/2kt0o2preicb5sa/setting-active-task-widget.png?dl=0 > > > (4) Image active-task > > This is the view you get when you click on a widget. The widget maximizes > and only the maximized detailed view of the Active Tasks Widget is shown > here. The rest of the widgets too can be shown this way. The other widgets > are navigated by the icons shown at the bottom. > > The task list is given and the details of the selected task is visualized > below it. Advanced Search can be done on the tasks as shown on the mockup > UI. > > Each widget have a maximized view so user can get easily identified what > they are interested. > > https://www.dropbox.com/s/1jb2o68mveiwfj4/active-task.png?dl=0 > > > Hoping to get any feedback for the mockup UIs or any suggestions for > improvement. > > Thanks. > > BR, > Nishani. > > On Sun, Mar 22, 2015 at 7:16 PM, Ayola Jayamaha > wrote: > >> Hi Alexander, >> >> Thanks for the reply. It clarifies my doubts. So I can enable _stats on >> standalone mode but keep it disable on the widget on distributed mode. >> >> Thank you. >> >> BR, >> Nishani >> >> On Sun, Mar 22, 2015 at 7:04 PM, Alexander Shorin >> wrote: >> >>> On Sun, Mar 22, 2015 at 3:34 PM, Ayola Jayamaha >>> wrote: >>> > As I understood the HTTP API supports log and stats. So can they be >>> included >>> > in my widgets? >>> > Is the GET /_log feature removed now? >>> >>> /_log is gone. Would like to say forever, but there is still a case >>> how could it come back and not in short-term. >>> /_stats is available on backdoor interface and for single node mode. >>> So stats could be included with a notice that such widget will not >>> work for cluster setup. That's easy to make with condition on /_stats >>> response status. >>> >>> -- >>> ,,,^..^,,, >>> >> >> >> >> -- >> Best Regards, >> Ayola Jayamaha >> http://ayolajayamaha.blogspot.com/ >> >> >> > > > -- > Best Regards, > Ayola Jayamaha > http://ayolajayamaha.blogspot.com/ > > > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 > > 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 > > 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 < > wadsash...@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 > > >> wrote: > > >> > > > >> >> Hi Dulanga, > > >> >> > >
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, Shared here are the links to the mockup UIs that I came up with. (1) Image dashboard-custom-layout It shows you the Main Dashboard Page that you see when you run the Fauxton Web UI. In this configuration you can see 6 widgets. The customizable widget or the master widget is only visible to the administrator and he/she could customize / manage the widgets that are shown to each user. It facilitate each user having a different set of available tasks/widgets according to his taste/permission level. https://www.dropbox.com/s/y6obhay0v788vp6/dashboard-custom-layout.png?dl=0 (2) Image dashboard-main It shows all the widgets after the page is fully loaded. - Recently Visited Databases - Details of DB visited - Active Tasks - DB, PID, % progress - Cluster Quick Mgt. - Nodes, DBs, Docs, (details,resource utilization,view,change) - User Quick Mgt. - Groups, Permissions, Authorization Roles - Replicator Quick Mgt. - Source, Target - Configuration Quick Mgt. - httpd, cluster, user, stats(only on cluster mode) Each widget contains a different UI component for better presentation ie Bar charts, Trees, Maps,Tables ..etc https://www.dropbox.com/s/cmulskiopamqzbv/dashboard-main.png?dl=0 (3) Image setting-active-task-widget It is shown when you click on the settings icon at the right corner of the widget. The user have some limited control over selecting the actions viewed on the widget. These permissions are defined by the authorization level of the user. Based upon that the user is given the set of tasks falling under the sub-category of that widget. eg: Active task widget https://www.dropbox.com/s/2kt0o2preicb5sa/setting-active-task-widget.png?dl=0 (4) Image active-task This is the view you get when you click on a widget. The widget maximizes and only the maximized detailed view of the Active Tasks Widget is shown here. The rest of the widgets too can be shown this way. The other widgets are navigated by the icons shown at the bottom. The task list is given and the details of the selected task is visualized below it. Advanced Search can be done on the tasks as shown on the mockup UI. Each widget have a maximized view so user can get easily identified what they are interested. https://www.dropbox.com/s/1jb2o68mveiwfj4/active-task.png?dl=0 Hoping to get any feedback for the mockup UIs or any suggestions for improvement. Thanks. BR, Nishani. On Sun, Mar 22, 2015 at 7:16 PM, Ayola Jayamaha wrote: > Hi Alexander, > > Thanks for the reply. It clarifies my doubts. So I can enable _stats on > standalone mode but keep it disable on the widget on distributed mode. > > Thank you. > > BR, > Nishani > > On Sun, Mar 22, 2015 at 7:04 PM, Alexander Shorin > wrote: > >> On Sun, Mar 22, 2015 at 3:34 PM, Ayola Jayamaha >> wrote: >> > As I understood the HTTP API supports log and stats. So can they be >> included >> > in my widgets? >> > Is the GET /_log feature removed now? >> >> /_log is gone. Would like to say forever, but there is still a case >> how could it come back and not in short-term. >> /_stats is available on backdoor interface and for single node mode. >> So stats could be included with a notice that such widget will not >> work for cluster setup. That's easy to make with condition on /_stats >> response status. >> >> -- >> ,,,^..^,,, >> > > > > -- > Best Regards, > Ayola Jayamaha > http://ayolajayamaha.blogspot.com/ > > > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi Alexander, Thanks for the reply. It clarifies my doubts. So I can enable _stats on standalone mode but keep it disable on the widget on distributed mode. Thank you. BR, Nishani On Sun, Mar 22, 2015 at 7:04 PM, Alexander Shorin wrote: > On Sun, Mar 22, 2015 at 3:34 PM, Ayola Jayamaha > wrote: > > As I understood the HTTP API supports log and stats. So can they be > included > > in my widgets? > > Is the GET /_log feature removed now? > > /_log is gone. Would like to say forever, but there is still a case > how could it come back and not in short-term. > /_stats is available on backdoor interface and for single node mode. > So stats could be included with a notice that such widget will not > work for cluster setup. That's easy to make with condition on /_stats > response status. > > -- > ,,,^..^,,, > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
On Sun, Mar 22, 2015 at 3:34 PM, Ayola Jayamaha wrote: > As I understood the HTTP API supports log and stats. So can they be included > in my widgets? > Is the GET /_log feature removed now? /_log is gone. Would like to say forever, but there is still a case how could it come back and not in short-term. /_stats is available on backdoor interface and for single node mode. So stats could be included with a notice that such widget will not work for cluster setup. That's easy to make with condition on /_stats response status. -- ,,,^..^,,,
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, As I tried out the API does not cater for User Management relevant information. Such as GET /_users. Details such as edit user information, add/remove user, changing authorization level...etc are needed for one of the widgets.Is there any other way I can retrieve them in order to show them on User Quick Management Widget? Thanks. BR, Nishani On Sun, Mar 22, 2015 at 6:04 PM, Ayola Jayamaha wrote: > Hi All, > > As I understood the HTTP API supports log and stats. So can they be > included in my widgets? > Is the GET /_log feature removed now? > > Thanks. > > Best Regards, > Nishani. > https://ayolajayamaha.blogspot.com > > > On Fri, Mar 20, 2015 at 11:28 PM, Ayola Jayamaha > wrote: > >> Hi All, >> >> I went through the thread on dev-mailing list and also followed the IRC >> Meeting.[1] >> >> The summarized information I got is as follows. >> >> The featured list of Widgets are given below as proposed. >> >> >>- Cluster Quick Management >>- Recently Visited Databases >>- Active Tasks >>- _users/_replicator >>- customizable widgets >>- optional : user profile >> >> I also plan to follow and complete the tutorial [2] >> And read [3] for Flux pattern >> For React.js [4] >> Look at how data flow >> Try and create menu item called 'Dashboard'[5-6] >> Create a module dashboard >> >> Am I correct here or did I miss anything? >> >> [1] >> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3ccaj1bcferumj+ctajvoepnu4up3dyiskmbvbvnveqdkhqee5...@mail.gmail.com%3E >> [2] https://github.com/ryanflorence/react-training/tree/gh-pages/lessons >> [3] >> https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e >> [4] >> https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602 >> [5] >> https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8 >> [6] >> https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config >> >> >> On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha >> wrote: >> >>> Hi All, >>> >>> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 >>> Dashboard as main page project interests me as I plan to attempt GSoC 2015 >>> particularly due to it's active dev-mailing lists and my previous >>> experience with creating dashboards and front-end development. >>> >>> Under the guidance of Robert Kowalski, Alexander Shorin I successfully >>> built it and am ready to proceed with the next steps. They will be to get >>> familiarized with Fauxton Code Structure and coming up with a good and >>> useful feature list for the dashboard.[1] >>> >>> I have started writing the proposal and shall share it tomorrow with the >>> expectancy of some good feedback that would help me improve. >>> >>> Looking forward in creating a nicer looking welcome page with useful >>> information and summaries preferably with added charting. >>> >>> Thanks. >>> >>> [1] >>> https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 >>> >>> BR, >>> Nishani >>> >> >> >> >> -- >> Best Regards, >> Ayola Jayamaha >> >> >> >> > > > -- > Best Regards, > Ayola Jayamaha > > > > -- Best Regards, Ayola Jayamaha http://ayolajayamaha.blogspot.com/
Re: [GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, As I understood the HTTP API supports log and stats. So can they be included in my widgets? Is the GET /_log feature removed now? Thanks. Best Regards, Nishani. https://ayolajayamaha.blogspot.com On Fri, Mar 20, 2015 at 11:28 PM, Ayola Jayamaha wrote: > Hi All, > > I went through the thread on dev-mailing list and also followed the IRC > Meeting.[1] > > The summarized information I got is as follows. > > The featured list of Widgets are given below as proposed. > > >- Cluster Quick Management >- Recently Visited Databases >- Active Tasks >- _users/_replicator >- customizable widgets >- optional : user profile > > I also plan to follow and complete the tutorial [2] > And read [3] for Flux pattern > For React.js [4] > Look at how data flow > Try and create menu item called 'Dashboard'[5-6] > Create a module dashboard > > Am I correct here or did I miss anything? > > [1] > http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3ccaj1bcferumj+ctajvoepnu4up3dyiskmbvbvnveqdkhqee5...@mail.gmail.com%3E > [2] https://github.com/ryanflorence/react-training/tree/gh-pages/lessons > [3] > https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e > [4] > https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602 > [5] > https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8 > [6] > https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config > > > On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha > wrote: > >> Hi All, >> >> I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 >> Dashboard as main page project interests me as I plan to attempt GSoC 2015 >> particularly due to it's active dev-mailing lists and my previous >> experience with creating dashboards and front-end development. >> >> Under the guidance of Robert Kowalski, Alexander Shorin I successfully >> built it and am ready to proceed with the next steps. They will be to get >> familiarized with Fauxton Code Structure and coming up with a good and >> useful feature list for the dashboard.[1] >> >> I have started writing the proposal and shall share it tomorrow with the >> expectancy of some good feedback that would help me improve. >> >> Looking forward in creating a nicer looking welcome page with useful >> information and summaries preferably with added charting. >> >> Thanks. >> >> [1] >> https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 >> >> BR, >> Nishani >> > > > > -- > Best Regards, > Ayola Jayamaha > > > > -- Best Regards, Ayola Jayamaha
Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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 > 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 > >> 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 > >> 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:2
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 >> 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 >> 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 >> >> 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 < >> wadsash...@gmail.com> >> >> > wrote: >> >> >> >> >> >> Hey Robert, problem solved.. :) >> >> >> >> >> >> >> >> >> Regards. >> >> >> >> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika < >> wadsash...@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
Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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 > 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 > >> 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 < > wadsash...@gmail.com> > >> > wrote: > >> >> > >> >> Hey Robert, problem solved.. :) > >> >> > >> >> > >> >> Regards. > >> >> > >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika < > wadsash...@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 < > >> wadsash...@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 > >> > >> >
[GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, I went through the thread on dev-mailing list and also followed the IRC Meeting.[1] The summarized information I got is as follows. The featured list of Widgets are given below as proposed. - Cluster Quick Management - Recently Visited Databases - Active Tasks - _users/_replicator - customizable widgets - optional : user profile I also plan to follow and complete the tutorial [2] And read [3] for Flux pattern For React.js [4] Look at how data flow Try and create menu item called 'Dashboard'[5-6] Create a module dashboard Am I correct here or did I miss anything? [1] http://mail-archives.apache.org/mod_mbox/couchdb-dev/201503.mbox/%3ccaj1bcferumj+ctajvoepnu4up3dyiskmbvbvnveqdkhqee5...@mail.gmail.com%3E [2] https://github.com/ryanflorence/react-training/tree/gh-pages/lessons [3] https://medium.com/brigade-engineering/what-is-the-flux-application-architecture-b57ebca85b9e [4] https://github.com/apache/couchdb-fauxton/commit/8cbf95d34a191770cfaadf7df98e07b5652e7602 [5] https://github.com/apache/couchdb-fauxton/blob/master/settings.json.default#L8 [6] https://github.com/apache/couchdb-fauxton/tree/master/app/addons/config On Fri, Mar 20, 2015 at 9:05 PM, Ayola Jayamaha wrote: > Hi All, > > I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 > Dashboard as main page project interests me as I plan to attempt GSoC 2015 > particularly due to it's active dev-mailing lists and my previous > experience with creating dashboards and front-end development. > > Under the guidance of Robert Kowalski, Alexander Shorin I successfully > built it and am ready to proceed with the next steps. They will be to get > familiarized with Fauxton Code Structure and coming up with a good and > useful feature list for the dashboard.[1] > > I have started writing the proposal and shall share it tomorrow with the > expectancy of some good feedback that would help me improve. > > Looking forward in creating a nicer looking welcome page with useful > information and summaries preferably with added charting. > > Thanks. > > [1] > https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 > > BR, > Nishani > -- Best Regards, Ayola Jayamaha
[GSoC 2015][COUCHDB-2214] Dashboard as main page
Hi All, I'm Nishani. I'm a Student at University of Moratuwa. COUCHDB-2214 Dashboard as main page project interests me as I plan to attempt GSoC 2015 particularly due to it's active dev-mailing lists and my previous experience with creating dashboards and front-end development. Under the guidance of Robert Kowalski, Alexander Shorin I successfully built it and am ready to proceed with the next steps. They will be to get familiarized with Fauxton Code Structure and coming up with a good and useful feature list for the dashboard.[1] I have started writing the proposal and shall share it tomorrow with the expectancy of some good feedback that would help me improve. Looking forward in creating a nicer looking welcome page with useful information and summaries preferably with added charting. Thanks. [1] https://issues.apache.org/jira/browse/COUCHDB-2214?focusedCommentId=14361863&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14361863 BR, Nishani
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[ https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371403#comment-14371403 ] Nishani commented on COUCHDB-2214: --- Hi Robert, I successfully built Couch 2.0 perview about 2 days ago and I put a message regarding my progress. I went through the Fauxtons code structure and also gave some thoughts on the features that needed to be added on the dashboard. Unfortunately I was unable to attend the weekly meeting but I'm looking forward to attend to the next. I'm currently writing my proposal and it would be great if you too can give some feedback on it. I'm planing to discuss about the features of the dashboard and collect few ideas from the community via the dev-mailing list. Hope everyone would collaborate with it. So now I'm ready with proceeding with the 2 tasks you mentioned, Fauxton code structure and how it works & discussion on features of the dashboard. Thanks. BR, Nishani > Dashboard as main page > -- > > Key: COUCHDB-2214 > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: CouchDB, gsoc2015, javascript > > Currently, the main page of Fauxton is list of all databases on server. While > this representation is traditional and legacy from Futon, it would be awesome > to see there some dashboard of summary information. > For instance, you're logged as admin. What Fauxton may show you on there? > - Recently visited databases (COUCHDB-2112) > - Active replications (+ active_tasks) > - Some valuable stats like 500 / 401 HTTP errors > - Recent log messages > - Quick links for users / replicator databases, create new user/admin > - Some field for alert message like: Fix the admin party. Warning! You have > the admin party and your CouchDB is accessible not only from localhost. And > some other recommendations (like raise max_open_databases in case if you have > a lot of dbs and stats tells that you're getting closer to this limit), tip > of the day etc. > As for regular user there could be showed: > - Recently visited databases > - Link to his profile (doc in _users db) > (whatelse may be useful for regular users?) > In other words, it would be awesome to have nicer welcome page with useful > information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 >> 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 >> > wrote: >> >> >> >> Hey Robert, problem solved.. :) >> >> >> >> >> >> Regards. >> >> >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika >> >> 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 < >> wadsash...@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 >> 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 >> > 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 al
Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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 > > wrote: > >> > >> Hey Robert, problem solved.. :) > >> > >> > >> Regards. > >> > >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika > >> 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 < > wadsash...@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 > 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 > > 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:
Re: [COUCHDB-2214] Dashboard as main page
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 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 > wrote: >> >> Hey Robert, problem solved.. :) >> >> >> Regards. >> >> On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika >> 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 >>> 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 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 > 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 > > 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 t
Re: [COUCHDB-2214] Dashboard as main page
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 wrote: > Hey Robert, problem solved.. :) > > > Regards. > > On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika > 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 >> 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 >>> 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 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 < wadsash...@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 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 >
Re: [COUCHDB-2214] Dashboard as main page
Hey Robert, problem solved.. :) Regards. On Thu, Mar 19, 2015 at 9:52 PM, Dulanga Sashika 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 > 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 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 >>> 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 >>> 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 >>> 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 o
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 >> 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 >> 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 >> 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 so
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 > 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 > 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
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 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/c26xgbWb
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[
https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367528#comment-14367528
]
Nishani commented on COUCHDB-2214:
---
Hi,
I followed the instructions given and was able to build CouchDB 2 and Fauxton.
I also followed other threads regarding CouchDB for installation. But I got the
following error message,
Join nodes into cluster... ('Failed to join node1 into cluster', 'Object Not
Found')
failed
when trying to run.
Then I referred [1] and the same issue had been solved for Windows. After
successfully following the solution steps I managed to run it with no errors
Join nodes into cluster... ok
Developers cluster is set up at http://127.0.0.1:15984.
Currently I'm going through the REST API.
To collect more ideas about the feature list I'm hoping to include on the
dashboard, I will put a message to dev-mail list asking community requirements
and ideas.
Thanks.
Best Regards,
Nishani
[1] https://issues.apache.org/jira/browse/COUCHDB-2605
> Dashboard as main page
> --
>
> Key: COUCHDB-2214
> URL: https://issues.apache.org/jira/browse/COUCHDB-2214
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
> Labels: CouchDB, gsoc2015, javascript
>
> Currently, the main page of Fauxton is list of all databases on server. While
> this representation is traditional and legacy from Futon, it would be awesome
> to see there some dashboard of summary information.
> For instance, you're logged as admin. What Fauxton may show you on there?
> - Recently visited databases (COUCHDB-2112)
> - Active replications (+ active_tasks)
> - Some valuable stats like 500 / 401 HTTP errors
> - Recent log messages
> - Quick links for users / replicator databases, create new user/admin
> - Some field for alert message like: Fix the admin party. Warning! You have
> the admin party and your CouchDB is accessible not only from localhost. And
> some other recommendations (like raise max_open_databases in case if you have
> a lot of dbs and stats tells that you're getting closer to this limit), tip
> of the day etc.
> As for regular user there could be showed:
> - Recently visited databases
> - Link to his profile (doc in _users db)
> (whatelse may be useful for regular users?)
> In other words, it would be awesome to have nicer welcome page with useful
> information as summary from other sources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [COUCHDB-2214] Dashboard as main page
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 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 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 n
Re: [COUCHDB-2214] Dashboard as main page
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 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 ho
Re: [COUCHDB-2214] Dashboard as main page
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
Re: [COUCHDB-2214] Dashboard as main page
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 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 > 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 > 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 > >> 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
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 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 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 >> 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
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 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 > 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.
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[
https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361949#comment-14361949
]
Robert Kowalski commented on COUCHDB-2214:
--
Hi Nishani,
wow sounds good! CouchDB is a database with HTTP API. I really love the
project, it is really inclusive and full of nice people!
We are using Fauxton [1] as our dashboard interface, you would build the
dashboard there. You will probably have to use "git bash" to make it run on
Windows, if you are a windows user.
For running CouchDB 2.x with the Fauxton dev environment you will addtionally
need to install haproxy.
boot the load balancer:
{code}
$ cd couchdb
$ haproxy -f rel/haproxy.cfg
{code}
installing and running fauxton:
{code}
$ git clone https://github.com/apache/couchdb-fauxton
$ cd couchdb-fauxton
$ npm install
$ npm install -g grunt grunt-cli
$ grunt dev
{code}
You will need Couch 2, Fauxton and haproxy running. You should then have our
webinterface running on port 8000 :)
As first step, try out to create a DB and a document using Fauxton :)
I am happy to help, the 2.0 preview installation is not that easy. I hang out
in freenode in #couchdb-dev
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 but depending
[1] https://github.com/apache/couchdb-fauxton
> Dashboard as main page
> --
>
> Key: COUCHDB-2214
> URL: https://issues.apache.org/jira/browse/COUCHDB-2214
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
> Labels: CouchDB, gsoc2015, javascript
>
> Currently, the main page of Fauxton is list of all databases on server. While
> this representation is traditional and legacy from Futon, it would be awesome
> to see there some dashboard of summary information.
> For instance, you're logged as admin. What Fauxton may show you on there?
> - Recently visited databases (COUCHDB-2112)
> - Active replications (+ active_tasks)
> - Some valuable stats like 500 / 401 HTTP errors
> - Recent log messages
> - Quick links for users / replicator databases, create new user/admin
> - Some field for alert message like: Fix the admin party. Warning! You have
> the admin party and your CouchDB is accessible not only from localhost. And
> some other recommendations (like raise max_open_databases in case if you have
> a lot of dbs and stats tells that you're getting closer to this limit), tip
> of the day etc.
> As for regular user there could be showed:
> - Recently visited databases
> - Link to his profile (doc in _users db)
> (whatelse may be useful for regular users?)
> In other words, it would be awesome to have nicer welcome page with useful
> information as summary from other sources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [COUCHDB-2214] Dashboard as main page
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 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.
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[ https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361863#comment-14361863 ] Nishani commented on COUCHDB-2214: --- Hi, I'm Nishani, a Student at University of Moratuwa. I'm very much interested in this project as it appears under gsoc 2015 project list particularly since my former experiences with creating dashboards[1], hawt.io [2], REST API, JSON, AngularJS, nvd3 libraries, html5 etc. The dashboard I created for Apache Helix - Cluster Management System, can be found in my github as well as a screenshot of it is on my blog. [3,4] I'm following https://couchdb.apache.org/developer-preview/2.0 inorder to install CouchDB. What would be a good place to get familiarize with CouchDB Code Base and could anyone suggest some good resouces to go through regarding implementing a dashboard for a similar system? The dashboard I'm planing to implement will have, 1. Summary Status 2. View customized for CouchDB 3. Support good diagnosis 4. Simple data presentation 5. Granular View 6. Timestamp 7. Alerts 8. Facilitate taking appropriate actions [1] https://github.com/AyolaJayamaha/helix/tree/master/helix-hawtio-plugin [2] https://github.com/AyolaJayamaha/helix-hawtio-plugins [3] https://github.com/AyolaJayamaha/helix [4] http://ayolajayamaha.blogspot.com/2014/08/helix-dashboard-features.html > Dashboard as main page > -- > > Key: COUCHDB-2214 > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: CouchDB, gsoc2015, javascript > > Currently, the main page of Fauxton is list of all databases on server. While > this representation is traditional and legacy from Futon, it would be awesome > to see there some dashboard of summary information. > For instance, you're logged as admin. What Fauxton may show you on there? > - Recently visited databases (COUCHDB-2112) > - Active replications (+ active_tasks) > - Some valuable stats like 500 / 401 HTTP errors > - Recent log messages > - Quick links for users / replicator databases, create new user/admin > - Some field for alert message like: Fix the admin party. Warning! You have > the admin party and your CouchDB is accessible not only from localhost. And > some other recommendations (like raise max_open_databases in case if you have > a lot of dbs and stats tells that you're getting closer to this limit), tip > of the day etc. > As for regular user there could be showed: > - Recently visited databases > - Link to his profile (doc in _users db) > (whatelse may be useful for regular users?) > In other words, it would be awesome to have nicer welcome page with useful > information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[COUCHDB-2214] Dashboard as main page
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.
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[ https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361705#comment-14361705 ] Dulanga Sashika commented on COUCHDB-2214: -- Hi, I am an 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. If you can, please guide me to start working on this project. Thank you. > Dashboard as main page > -- > > Key: COUCHDB-2214 > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: CouchDB, gsoc2015, javascript > > Currently, the main page of Fauxton is list of all databases on server. While > this representation is traditional and legacy from Futon, it would be awesome > to see there some dashboard of summary information. > For instance, you're logged as admin. What Fauxton may show you on there? > - Recently visited databases (COUCHDB-2112) > - Active replications (+ active_tasks) > - Some valuable stats like 500 / 401 HTTP errors > - Recent log messages > - Quick links for users / replicator databases, create new user/admin > - Some field for alert message like: Fix the admin party. Warning! You have > the admin party and your CouchDB is accessible not only from localhost. And > some other recommendations (like raise max_open_databases in case if you have > a lot of dbs and stats tells that you're getting closer to this limit), tip > of the day etc. > As for regular user there could be showed: > - Recently visited databases > - Link to his profile (doc in _users db) > (whatelse may be useful for regular users?) > In other words, it would be awesome to have nicer welcome page with useful > information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2214) Dashboard as main page
[ https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kowalski updated COUCHDB-2214: - Labels: CouchDB gsoc2015 javascript (was: ) > Dashboard as main page > -- > > Key: COUCHDB-2214 > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: CouchDB, gsoc2015, javascript > > Currently, the main page of Fauxton is list of all databases on server. While > this representation is traditional and legacy from Futon, it would be awesome > to see there some dashboard of summary information. > For instance, you're logged as admin. What Fauxton may show you on there? > - Recently visited databases (COUCHDB-2112) > - Active replications (+ active_tasks) > - Some valuable stats like 500 / 401 HTTP errors > - Recent log messages > - Quick links for users / replicator databases, create new user/admin > - Some field for alert message like: Fix the admin party. Warning! You have > the admin party and your CouchDB is accessible not only from localhost. And > some other recommendations (like raise max_open_databases in case if you have > a lot of dbs and stats tells that you're getting closer to this limit), tip > of the day etc. > As for regular user there could be showed: > - Recently visited databases > - Link to his profile (doc in _users db) > (whatelse may be useful for regular users?) > In other words, it would be awesome to have nicer welcome page with useful > information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2214) Dashboard as main page
[ https://issues.apache.org/jira/browse/COUCHDB-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351798#comment-14351798 ] Robert Kowalski commented on COUCHDB-2214: -- The project is using React.js for the Admin-Interface. You will use JavaScript, CSS, HTML and the HTTP API of CouchDB. > Dashboard as main page > -- > > Key: COUCHDB-2214 > URL: https://issues.apache.org/jira/browse/COUCHDB-2214 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > > Currently, the main page of Fauxton is list of all databases on server. While > this representation is traditional and legacy from Futon, it would be awesome > to see there some dashboard of summary information. > For instance, you're logged as admin. What Fauxton may show you on there? > - Recently visited databases (COUCHDB-2112) > - Active replications (+ active_tasks) > - Some valuable stats like 500 / 401 HTTP errors > - Recent log messages > - Quick links for users / replicator databases, create new user/admin > - Some field for alert message like: Fix the admin party. Warning! You have > the admin party and your CouchDB is accessible not only from localhost. And > some other recommendations (like raise max_open_databases in case if you have > a lot of dbs and stats tells that you're getting closer to this limit), tip > of the day etc. > As for regular user there could be showed: > - Recently visited databases > - Link to his profile (doc in _users db) > (whatelse may be useful for regular users?) > In other words, it would be awesome to have nicer welcome page with useful > information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2214) Dashboard as main page
Alexander Shorin created COUCHDB-2214: - Summary: Dashboard as main page Key: COUCHDB-2214 URL: https://issues.apache.org/jira/browse/COUCHDB-2214 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Alexander Shorin Currently, the main page of Fauxton is list of all databases on server. While this representation is traditional and legacy from Futon, it would be awesome to see there some dashboard of summary information. For instance, you're logged as admin. What Fauxton may show you on there? - Recently visited databases (COUCHDB-2112) - Active replications (+ active_tasks) - Some valuable stats like 500 / 401 HTTP errors - Recent log messages - Quick links for users / replicator databases, create new user/admin - Some field for alert message like: Fix the admin party. Warning! You have the admin party and your CouchDB is accessible not only from localhost. And some other recommendations (like raise max_open_databases in case if you have a lot of dbs and stats tells that you're getting closer to this limit), tip of the day etc. As for regular user there could be showed: - Recently visited databases - Link to his profile (doc in _users db) (whatelse may be useful for regular users?) In other words, it would be awesome to have nicer welcome page with useful information as summary from other sources. -- This message was sent by Atlassian JIRA (v6.2#6252)
