couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Orr (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-950) Futon2!
Date Thu, 18 Nov 2010 05:46:14 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933314#action_12933314
] 

Nicholas Orr commented on COUCHDB-950:
--------------------------------------

issues I've found (git commit: ef29a70)

on the views screen (overview > database > _views)
- i click on a design doc, get a list of views on the right, no matter which one I click on
the screen only loads the last view in the list. if I change the url in the address bar i
can access the other views
- even though reduce is not ticked it is true, changing the url to reduce=false produces a
non-reduced list of rows
- getting rid of the dropdown for group_level means we have to click the field, highlight/clear
the current value, type a number, then press tab to get a response - this seems like a one
step back sort of thing, clicking a dropdown and by selecting a value a result produced straight
away is responsive in comparison
-- suggest, making this a dropdown or fire event onkeyup instead of onblur/onchange. this
of course would mean two operations if the person wants a double digit group, though futon1
only goes up to 9, is that a limit? then just make the field maxlength=1 
- there is a disconnect between pressing "edit" on a view and the textarea updating with the
view functions and the rest of the controls, the controls are connected to the view in the
addressbar, pressing save gets everything back in sync, however this seems like a step back
as well. in the current futon, the whole screen is synced to the view in the dropdown, in
futon2 all views are visible, the current one is not obvious and we can click edit on any
of the views
-- suggest clicking edit make the view that we want to edit change the screen to that view
and bold this view's text so it is clear we are now dealing with this view.
--- alternative, only expose edit link on the current view, want to edit a view not being
looked at, click it, then click edit. doing this will also prevent an issue i found that when
i create a new view, by pressing new, typing text i can click edit on the other views and
when i press save, the new view gets the code in the textareas, the view is calculated and
result is returned, however now when i click edit on a different view and press save the view
the code is saved to is the new one i created... if i do enough of this random clicking on
edit I can create an "underfined" view...
- only enable group/group_level if reduce is true
- clicking an ID in the results doesn't open the document, in futon1 it opens the document

This is what I've noticed so far.
Really like all the extra info you have exposed and it does feel responsive in comparison
to futon1 - awesome sauce ;)

Nicholas


> Futon2!
> -------
>
>                 Key: COUCHDB-950
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-950
>             Project: CouchDB
>          Issue Type: New Feature
>         Environment: All.
>            Reporter: mikeal
>         Attachments: futon2.diff
>
>
> This is a complete rewrite of Futon as a single page app using sammy.js.
> I've been working on it for some time at 
> https://github.com/mikeal/couchdb/tree/sammy
> Changes
> -------------
> - Everything expect for session.html is loaded dynamically as a content replace to index.html.

> - The total amount of javascript loaded at any time is about 1/3, a combination of removing
abstractions and some very large jQuery plugins.
> - Load times for all pages is dramatically reduced
> - URL structure of futon now mimics the CouchDB REST API except at #/
> - An intended side-effect of the new URL structure is that the button to pull up the
current page as a request to CouchDB works *everywhere*
> - Unified error handling (Any network or HTTP error is now displayed as error bubbled
at the top of the page content)
> - All "paging" is now done inline making the loads faster and more usable
> - Many dialogs have been removed in favor of simpler UI elements (as a side effect it's
more mobile friendly).
> - All dbinfo is in database page as well as the "total size" calculated from the db size
and the size of all the views.
> - db page includes support for start/end queries against _all_docs
> - Stats page now includes all info from _stats
> - added _changes page
> - Cleaned up loading of test files (faster and parallelized now). The test are now automatically
sorted alpha regardless of the order in the array definition.
> - New Document viewer/editor
> -- In-line "auto-save"
> -- Full revision information and restoration
> -- New UI shows all arrays and objects as initially collapsed to improve handling of
large docs.
> -- Load time, even with incredibly large objects, is almost instance (a combination of
not using a table and only creating elements in the expanded view after you click to expand
them)
> - New Views Page
> -- Emphasis is now on building queries with building view functions a secondary function.
> -- All view options exposed, options now allowed are disabled.
> -- All queries can be built in this view and then 
> -- Creating new views, and editing views, is now a process of editing and saving design
documents, all usage of temp views has been removed.
> -- include_docs expand/collapse when in query

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message