Advertisement
Guest User

Untitled

a guest
Apr 27th, 2017
83
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.17 KB | None | 0 0
  1. Hi Mentee,
  2. I would strongly recommend you get some kind of notebook where you can keep your doodles organized. How ever you are most creative is fine, but keeping your sketches organized is going to help you in many ways and allow you to share and demonstrate things in a more professional manner. It's hard for me to communicate with you which one works best because they are so scattered and mixed with the printed content on the paper. Your Logo + Brand Name Brainstorming 1.pdf is a nicely organized example. If you're happy with one of the potential logo options, you should sketch a larger, better, cleaner version on a clean blank workspace so we can see your design really stand out and improve it from there.
  3.  
  4. Dan
  5. ______________________________________________________________________________
  6.  
  7. Hi Mentee,
  8. I think these are useful questions to have answers to, but it's going to be very difficult to get anyone to answer them all or accurately with such a huge number of them, especially the open ended ones. You need to keep the questions multiple choice and limit them to a total of only a handful of questions. Answer data that a user was willing to take the time to answer accurately will be much more valuable to you than questions that were submitted in a rush with the user simply intending to get through it as quickly as possible. More than 5 questions, and I would say many users will not even want to participate. Having quantifiable data in the form of multiple choice questions, instead of open ended answers will also help to be able to programmatically analyze the data that was received.
  9.  
  10. Dan
  11. ______________________________________________________________________________
  12.  
  13. Hi Mentee,
  14. The reason that is happening is because the way you have it currently set up, each individual menu is not currently designed to affect the other menus. I think what you're looking for is to have specific states where the other 3 menus are hidden while the one you are interacting with is open. Here's an example of what you're looking to accomplish based on your description:
  15.  
  16. $("#sub-nav-set").hide();
  17. $("#sub-nav-search").hide();
  18. $("#sub-nav-view").hide();
  19. $("#sub-nav-new").hide();
  20.  
  21. $(".setbutton").on("click", function(){
  22. $("#sub-nav-set").toggle();
  23.  
  24. $("#sub-nav-search").hide();
  25. $("#sub-nav-view").hide();
  26. $("#sub-nav-new").hide();
  27. });
  28. $(".searchbutton").on("click", function(){
  29. $("#sub-nav-search").toggle();
  30.  
  31. $("#sub-nav-set").hide();
  32. $("#sub-nav-view").hide();
  33. $("#sub-nav-new").hide();
  34. });
  35. $(".viewbutton").on("click", function(){
  36. $("#sub-nav-view").toggle();
  37.  
  38. $("#sub-nav-set").hide();
  39. $("#sub-nav-search").hide();
  40. $("#sub-nav-new").hide();
  41. });
  42. $(".newbutton").on("click", function(){
  43. $("#sub-nav-new").toggle();
  44.  
  45. $("#sub-nav-set").hide();
  46. $("#sub-nav-search").hide();
  47. $("#sub-nav-view").hide();
  48. });
  49.  
  50. ______________________________________________________________________________
  51.  
  52. Hi Mentee,
  53.  
  54. There are multiple ways to handle this. It's not a fun issue, and I've experienced it myself, but we can resolve it!
  55.  
  56. Assuming this is the chain of events you performed:
  57. git checkout master
  58. git checkout mentor
  59. - work
  60. git commit
  61. git pull origin master
  62. - merge conflicts
  63.  
  64. Since there are merge conflicts and your code is already committed, you need to reset your working tree and index to your last commit, removing any merge commits or changes since then.
  65.  
  66. This command will reset your working tree and index to the last commit, removing the merge commit and subsequent uncommitted changes:
  67. git reset --hard HEAD
  68.  
  69. After this, the repository should be in the state you had it at before you pulled the master branch into mentor. Now you have to pull your changes out of mentor and into master. To do this, you will need to soft reset your branch to the commit made before your commit:
  70.  
  71. git reset --soft HEAD^
  72.  
  73. This places your changes into the index and removes the commit from your branch's local history. Now you need to change branches and commit it properly:
  74.  
  75. git checkout master
  76. git commit
  77.  
  78. At this time, you can pull the remote master branch into your local one:
  79. git pull origin master
  80.  
  81. Then push your changes (and any merge commits) up:
  82. git push origin master
  83.  
  84. Your repo should be in the state you want now. :)
  85.  
  86. Dan
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement