Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review and integrate open250 #274

Merged
merged 16 commits into from
Nov 10, 2015
Merged

Review and integrate open250 #274

merged 16 commits into from
Nov 10, 2015

Conversation

charlesh88
Copy link
Contributor

#250 and open250 address three front-end issues:

Author checklist:

  • Changes address original issue? Y
  • Unit tests included and/or updated with changes? Y
  • Command line build passes? Y
  • Expect to pass code review? Y

charlesh88 and others added 15 commits November 5, 2015 10:11
open #250
Markup mods in browse.html;
Renamed .holder-create-and-search to
.holder-treeview-elements;
TO-DO: fix search results to scroll properly;
open #250
Significant changes to flex classes, markup in
browse.html and search.html to support better
flex layout;
Search results now scrolls properly;
Significant refactoring and cleanups in search and _search.scss;
open #250
Fixed margin/spacing problems with results element;
Added transition to results display;
Begin adding # results found / no results messaging;
Moved class .off to _globals.scss;
open #250
open #260
vista#132
Major refactoring to markup and CSS to apply
flex layout strategy to object headers;
Flex necessary to fix 'overflow: hidden' setting
applied in open90 to object-browse-bar that
was preventing the view switcher menu from
appearing;
Browse, edit, mobile, frames in layouts, etc. all
visually checked in a first go round;
Mobile classes tweaked to fix left and right
margin problems resulting from open90 changes;
z-indexing of Inspector pane and splitters changed
to allow primary pane elements to overflow beneath
when primary pane width is severely constrained;
open #250
Snow theme constants missing were causing the Snow
theme CSS to not compile - this commit restores those
values;
TO-DO: values defined are a bit out of sync between Espresso
and Snow and need to be realigned;
open #250
Fixed min and max widths for panes to prevent
weird pane expand/collapse behaviors, like
Inspector covering the main view area;
Added min-width to .holder-all element;
open #250
Moved new min/max definitions into desktop-only
portion of layout.scss to not affect mobile layout;
open #250
Removed un-needed markup around treeview
includes and mct-reps; moved CSS class defs into
mct-include and mct-rep for search and tree
respectively;
open #250
Changed flex-elem to use margin-bottom instead of top;
Added margin-top to .search-results element;
open #250
open #157
Create button now hidden by default in mobile via
usage of CSS; can be re-displayed by including
'example/mobile' bundle;
open #250
open #157
Fixed CSS selector that wasn't properly
targeting the Create menu in a mobile
context;
<mct-representation key="'menu-arrow'" mct-object='domainObject'></mct-representation>
</span>
</div>
<!--<div class='object-header'> Moved up to browse-object.html and frame.html. TO-DO: make sure this is Ok!-->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has this TODO been addressed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it has. Will remove to-do.

@charlesh88
Copy link
Contributor Author

Uh, if you start looking for commented dead code in my sass, you're going to continually trip over it. This hasn't come up as a general issue previously, although Pete called me out on it in one particular instance a little while ago.

Let me go through and kill the comments in the sass in this branch, I'll push up a new version shortly. I'd really like the sass in #250 for something I'm doing in #279, so I'm highly motivated to get this integrated.

@VWoeltjen VWoeltjen assigned charlesh88 and unassigned VWoeltjen Nov 10, 2015
@VWoeltjen
Copy link
Contributor

Thanks - I'm trying to be more diligent about catching little things like that during code review (it's the only time they really get caught). Reassign to me when you're ready; I'll keep an eye out to complete the merge.

@charlesh88
Copy link
Contributor Author

No prob, and thanks. Moving forward I'll ensure that commented stuff is stamped out before doing pull reqs.

@VWoeltjen
Copy link
Contributor

Hm, so running this branch (open250) locally, I get a strange display (left pane starts collapsed):

open274

If I manually adjust the splitter next to the tree, the tree displays correctly, but I still have no inspector.

Wonder if this is a more severe case of #169? (I'm viewing on my little laptop screen)

@charlesh88
Copy link
Contributor Author

Re. "...I get a strange display...": was totally able to duplicate this in the Chrome mobile emulator: this is #169. I'm going to make fixing that a priority so you (and others with small laptops) won't be impacted by this.

open #250
open #274
scss, html scoured for commented
dead code, leftover TO-DOs and
other unnecessary comments;
@charlesh88
Copy link
Contributor Author

Ok, just pushed an updated version of open250 - should be completely cleaned up.

VWoeltjen added a commit that referenced this pull request Nov 10, 2015
Review and integrate open250
@VWoeltjen VWoeltjen merged commit 7264a71 into master Nov 10, 2015
@VWoeltjen
Copy link
Contributor

Reviewer Checklist

  1. Changes appear to address issue? Y
  2. Appropriate unit tests included? N/A *
  3. Code style and in-line documentation are appropriate? Y
  4. Commit messages meet standards? Y

* changes to CSS & templates only, out of scope for automated testing

@charlesh88
Copy link
Contributor Author

Awesome, thanks!

@larkin larkin deleted the open250 branch May 3, 2016 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants