~matsubara/juju-gui/merge-fail : changes

~matsubara/juju-gui/merge-fail » Changes from revision 756

From Revision 756 to 737

Rev	Summary	Authors	Tags	Date
756	Tarmac test merge. Tarmac test merge.	Richard Harding		10 years ago
755	Add support for related charm loading and display Add support for related charm loading and display - Adds a new store endpoint for the related charm api call - Adds the idea of relatedCharms for model ATTRS - Adds two helpers to take the api response data into something we can use in the app - Renders out the related charms in the template in fullscreen as an ajax request - Updates the charm details to handle click events on charm tokens - Adds tests for the model helpers and the details view - Updates a bunch of tests. There were left over testing Nodes that caused stray tests to fail. I fixed those and also went back and cleaned up the stray test mess. - Updates the css to work out so that the tokens can fit. There's a redesign-a-coming so the work was to fit in currently and the redesign will move the layout at a later date. Notes: - This does not currently add the related charm display to the interfaces tab. It's a slightly different UX and this branch was taking too long as is. - I'm not happy with the relatedCharms ATTR. It's not really an ATTR but I wanted this cached into the model because we'll use that when we add related charms to the interfaces tab. We don't want to re-request the data. However, in sidebar move it will not have been requested yet. My plan is to re-evaluate and possibly refactor when doing the interfaces tab display. R= CC= https://codereview.appspot.com/10416044	Richard Harding		10 years ago
754	Set version back to unreleased. Set version back to unreleased.	Gary Poster		10 years ago
753	Set version for release. Set version for release.	Gary Poster		10 years ago
752	Creates the basic sharing widget Creates the basic sharing widget -Sharing moved behind feature flag while it's ugly and partially functional -Sharing widget with images and basic layout -Share button shows/hides the widget R=rharding, jeff.pihach CC= https://codereview.appspot.com/10352045	j.c.sackett	0.6.1	10 years ago
751	Add SetCharm to Go sandbox Add SetCharm to Go sandbox This adds the new functionality from core of setting a service's charm (primarily for the purpose of upgrading) to the Go environment, sandbox, and fakebackend. This isn't implemented anywhere in the GUI yet, as there is no UX definition yet. Additionally, this doesn't address the concern of this functionality missing in the python backend (a card has been created for that). R=benji, bac CC= https://codereview.appspot.com/10401043	Matthew Scott		10 years ago
750	Prototype of data binding conflict resolution Prototype of data binding conflict resolution This branch changes the way we implement data binding by moving the bind keys into a data-attribute on the elements. This makes it easy to have dynamic templates bound to dynamic attributes on a model. When changes come in from Juju the databinding engine checks for dirty fields, a field becomes dirty if the YUI valueChange event would fire on it. If it finds that a change has come in for a dirty field it calls the viewlets conflict method which handles the conflict resolution UI. After the user has resolved the conflict the field it then returns to a clean state and can be updated automatically by the databinding engine. Please QA Steps to QA: Load the application with the flag `serviceInspector` Deploy the `glance` charm. Click the service and `view` to open the new inspector Click `Config` to display the configuration properties Open the console, paste and run:: g = app.db.services.item(0);gc = g.get('config');gc['db-user'] = 'asdf';g.set('config', gc); You'll notice that the db-user field is updated with the new value Edit the db-user field and run the script again You'll now see that the field is dirty Resolve the conflict change the value to set in the above script and then run again You'll see that the field changes as intended. R=benjamin.saller, teknico CC= https://codereview.appspot.com/10397045	Jeff Pihach		10 years ago
749	Add annotations to service to prevent jumping. Add annotations to service to prevent jumping. Services would jump to the middle of the canvas in the period of time before the RPC call from juju and the delta containing the updated annotations. This is prevented by preemptively setting the annotations on the service in the RPC callback before the x/y attrs are removed. R=gary.poster, jeff.pihach, benji CC= https://codereview.appspot.com/10444043	Matthew Scott		10 years ago
748	Add feedback box. Add feedback box. Per the design at http://ubuntuone.com/2dNEIxVwZ4qfVcsiTclmAE R=frankban, teknico, luca.paulina CC= https://codereview.appspot.com/10407044	Brad Crittenden		10 years ago
747	Fix drag problems on service creation Fix drag problems on service creation This bug affected FF and Chrome, causing relation lines to be mis-aligned and services to jump when dragged. I believe it was due to lingering attributes on the service boxes after creation. To QA, add MySQL and Wordpress, relate them, then drag them around a bunch. The relation line should follow the service blocks, and the service blocks shouldn't jump to any position when you start to drag them. R=jeff.pihach, teknico CC= https://codereview.appspot.com/10309044	Matthew Scott		10 years ago
746	Further improve test independence. Further improve test independence. Remove many test interdependencies by giving local window.flags variables to modules that need it. Use loadFixture everywhere instead of duplicating code, including in the jujuTests.utils object itself. Mark the remaining test interdependencies and defects, to be fixed later. Remove a meaningless test at the bottom of test_startup.js.bottom . Add removal of generated test_startup.js file to Makefile "clean" entry. R= CC= https://codereview.appspot.com/10383047	Nicola Larosa		10 years ago
745	Further improve test independence. Further improve test independence. Remove many test interdependencies by giving local window.flags variables to modules that need it. Use loadFixture everywhere instead of duplicating code, including in the jujuTests.utils object itself. Mark the remaining test interdependencies and defects, to be fixed later. Remove a meaningless test at the bottom of test_startup.js.bottom . Add removal of generated test_startup.js file to Makefile "clean" entry. R=gary.poster, bac CC= https://codereview.appspot.com/10383047	Nicola Larosa		10 years ago
744	Fix CI deploy failures. Fix CI deploy failures. The cookie policy message box prevented to click the zoom out button. Close the cookie message before zooming out. R= CC= https://codereview.appspot.com/10384045	Francesco Banconi		10 years ago
743	Add CI tests exercising notifications. Add CI tests exercising notifications. Ensure no initial errors are displayed. R=gary.poster, teknico CC= https://codereview.appspot.com/10383043	Francesco Banconi		10 years ago
742	Restore test modules alphabetical order. Restore test modules alphabetical order. Fix some interdipendencies among test modules by improving the cleaning up after tests. The branch name is a misnomer, from the first hypothesis that tried to explain the incorrect behavior: it revealed itself as a red herring. More cleanup will be performed in future branches. R=bac, frankban CC= https://codereview.appspot.com/10360044	Nicola Larosa		10 years ago
741	add missing file add missing file	Benji York		10 years ago
740	Fix the charm tests harder. Trivial, self-reviewed Fix the charm tests harder. Trivial, self-reviewed	Benji York		10 years ago
739	Fix the charm tests. Trivial, self-reviewed Fix the charm tests. Trivial, self-reviewed	Benji York		10 years ago
738	Use the virtualevn for bin/test-charm. Use the virtualevn for bin/test-charm. The python-selenium package in Raring is not new enough, so we will use the virtualenv with an updated version instead. R=gary.poster, bac CC= https://codereview.appspot.com/10387043	Benji York		10 years ago
737	Set version back to unreleased. Set version back to unreleased.	Benji York		10 years ago

Older »