GithubHelp home page GithubHelp logo

cleebp / csc-510-group-g Goto Github PK

View Code? Open in Web Editor NEW
1.0 1.0 2.0 26.3 MB

Group G's main repository for CSC 510 Spring 2016.

TeX 80.28% CoffeeScript 12.25% CSS 0.68% Python 4.59% Shell 1.14% R 1.06%

csc-510-group-g's Introduction

Hi there, I'm Brian Clee

  • πŸ“š I received my B.S. in Computer Science from Appalachian State Univerity in 2015
    • πŸ‘¨β€πŸ”¬ Minored in Mathematics, Russian Language, and Global Studies: Russian Studies
  • πŸ” I received my M.S. in Computer Science from North Carolina State University in 2018
    • πŸ–±οΈ My graduate research focused on Human Computer Interaction with non-traditional displays
  • πŸ—ΊοΈ I currently work as a Python Developer for Esri helping support Python across our platform primarily through anaconda environments
    • 🐍 I help manage and develop the 250+ conda packages on our Esri conda channel supporting python in ArcGIS Pro
    • πŸ•ΈοΈ Core maintainer of Esri's deep-learning-frameworks and the additional 100+ deep learning packages

Connect with me:

Brian Clee | LinkedIn



csc-510-group-g's People

Contributors

arjunmadan avatar cleebp avatar effat avatar reachspirit avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

angelyn sbalakr2

csc-510-group-g's Issues

package.json

Hey guys,

Looking through the package.json file it looks like this is where we setup simple description type data.

To make sure we are all kinda on the same page I'm proposing we sort of follow the following conventions:

"name": "clipit-FEATURE_NAME" => here for example the command line feature would be "clipit-cmd"
"author": "name": "Brian Clee, Effat Farhana, Arjun Madan, and Ran Tan"
"author": "url": "https://github.com/cleebp/csc-510-group-g"
...
"repository": "https://github.com/cleebp/csc-510-group-g"
...

The rest of this file can sort of change as needed for each feature, if you want to change the names from "clipboard-history" to "clipit-FEATURE_NAME" that could be a good idea but might cause a lot of dependency errors that will need fixing.

Posts on data persistence

Adding favorite reservations requires persistent data support. There are basically two ways: Using the serialize method provided by atom API or read and write to a file. Post supporting materials here.

System wide copying

Add support to the clipboard manager to allow copying from external programs/sources.

Debugging/Testing Clipit-cmd

Bulk development on clipit-cmd is done, this issue is a placeholder for my debugging/testing of the plug-ing.

Problem with the relative position of PREVIEW

Something went wrong with the interface.
image
Two critical sections are:

      if atom.config.get 'baseorder.showSnippetForLargeItems'
        @div class: 'preview hidden panel-bottom padded', =>
          @pre text.initial


preview = view.find '.preview'
if preview.length isnt 0 and preview.text().length > 65 and atom.config.get 'baseorder.showSnippetForLargeItems'
  if view.position().top isnt 0
    preview.css({ 'top': (view.position().top - 5) + 'px'})
  preview.removeClass 'hidden'

Literature Review

To justify our development of a clipboard manager we need to either create and test a user group (12 hour rule), or complete a literature review on our topic which justifies our software.

This can be a place where we keep track of promising literature related to clipboard managers, copy and paste habits, code cloning, etc.

Sharelatex

Hey so I made the sharelatex document and am adding everyone as collaborators.

Unfortunately because of the way the Github syncing works for sharelatex I had to create a new repo for our report. Here is the link: https://github.com/cleebp/group-g-feb1-report

I guess what we can do is make separate repos anytime we want to make a report in Sharelatex, and then when we are ready to get our deliverables together for a deadline we will just make a folder inside our main repo here, name it something like 'Feb 1 Deliverables' and copy over our final pdf from our Sharelatex workspace.

Really the github features of sharelatex aren't even needed since we will all be collaborators on the project, but all the same I will add all of us to the new repo just in case Dr. Menzies wants it.

Wednesday Meeting 2/10/2016

Hey all,

Not sure if we remembered to book a room for this week, I just checked and our normal room is booked so I grabbed 3315 from 2pm-4pm!

Feb 17th Meeting Notes

Going to try and start making weekly issue just on our meeting notes, maybe put them up ahead of time so if there are relevant links for the meeting you can post them for all to see!

So here is the issue for this week's meeting (albeit a bit late, but better late than never).

atom-space-pen-views

I created a new package with package generator and modified the original source code to make it work. The debugger showed a dependency problem with 'atom-space-pen-views', while I did included this package in dependencies in the file of package.json. Did anyone ever run into this problem?

Clipit-panel additions

Hey all,

I'm fiddling with Effat's clipit-panel today and just wanted to log what I'm trying out, if we don't like the changes we can always revert my changes, just thought I'd try to make the interaction a little more seamless!

I'll just post on this issue what I'm trying out...

  1. I have made it so that when you copy an item it immediately shows up on the panel, rather than showing up only after hitting the paste command (note for items copied outside of atom they will only show up on the panel after you paste them into atom)

Telemetry

  • Log where stuff is copied from
  • Timestamps
  • Anything else??

Final Demo

Right now we are scheduled to demo with Dr. Menzies on Thurs March 3rd at 4pm, and also with Shaown on Wed. March 2nd at 3:30pm here is the link for sign-ups.

We will find out if we need both or just one and then cancel or what not...

Intelligent contextual ordering

  • Best way to order items?
  • Group items by source?

Different ways of ordering:

  • based on usage
  • chronological
  • reverse chronological
  • something else?

DEMO TIME SWITCH

Hey guys, Dr. Menzies had something come up during our slot for the demo, so he moved us to 3pm on Thursday with Shaown, can everyone make this time?

I know I can but if someone else can't they should speak up with a time that does work thats still open.

xD

Meeting Mar 9th

Sorry for the late notice, but is it possible to meet at 4pm instead of the usual 2pm tomorrow? I have some work I have to get done in the afternoon.

Problem with sorting array of objects by properties

I have a problem with sorting copied items. Since @history is an array of object and I put count, source as properties of the object of each copied item, I need to sort an array of objects by their properties. According to javascript, a sort method is provided to array, so what I need to do is like this:

history.sort(function(a, b) {
    return a.count - b.count;
});

translated to coffeescript, we get:

@history.sort (a, b) ->
    a.count - b.count

Yet, it showed that a is not defined. I'm not sure whether there are any syntax errors. Any suggestions?

Feb1 report reorganization

I think we should consider reorganizing section 2 (Project Goals) and 4 (Copy and Paste in Practice), so that the different ideas we had for the clipboard manager come after section 4, which builds up to the need for one, and how it could help programmers.

What do you all think about this?

A List of Tasks

Here are some tasks to do based on the requirements of the project:

  1. Clearly define PUTG and try to justify the definition:

P(problem): Why simple operations like copying and pasting may cause a problem to users? What are the most common behavior patterns that lead to these problems? What are the problems with existing clipboard managers(In what aspects they need to be improved)?

U(user group): What are the targeted users(How to category a user group)? Who are affected most by the problem we mentioned above? What are typical environments and what are the behavior patterns of the targeted users in that particular environment?

T(software tools): Eclipse IDE itself is a software tool. What are the features of the IDE? What specific design principles or rules we need to follow when developing the plug-in(How to make it consistent with the platform)? What is possible with the IDE and what may be impractical given the time? What tools are we going to use for the management of the project and why we choose them(Git-Github, shareLatex)?

G(goal): What functions will the plug-in include and what will not? How to define the usability of a clipboard manager? How to prove that our design is really better than other clipboard managers?

  1. Data collection:
    Were the review documents' inclusion and exclusion criteria described and appropriate?
    What's the relationship between our project to code clone and what's the difference?

Is the literature search likely to have covered all relevant studies(How can we prove that it's a thorough study of the problem)?

Did the reviewers assess the quality/validity of the included studies? (e.g. citations counts, recency)

Were the basic data/studies adequately described? Are we able to get the original data instead of second hand analysis?

  1. Start up exercise and competency proof:
    Create a Hello-World eclipse plug-in/plug-in extension and push it to the branch.

Final Edits

Hey all, I'll be reading through the paper multiple times today and just making general edits/cleaning up grammar if I notice anything.

If we have anything discussion wise we want to bring up to the group we can post those here!

Baseorder (clipit-order) not working on mac

So I'm trying to get Ran's baseorder working on my mac and am running into an error whenever I try to do anything with it.

The error is usually formatted like so:

Uncaught TypeError: Cannot read property of 'length' of undefined

Any ideas what might be causing this? It seems like it has to do with the history variable, maybe something with the serialization?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.