Skip to content

Commit

Permalink
Create gh-pages branch via GitHub
Browse files Browse the repository at this point in the history
  • Loading branch information
@thucdtran
thucdtran committed Apr 20, 2015
1 parent 0a757f6 commit 46efe48
Show file tree
Hide file tree
Showing 5 changed files with 399 additions and 27 deletions.
83 changes: 57 additions & 26 deletions index.html
View file
Original file line number Diff line number Diff line change
@@ -1,25 +1,34 @@
<!DOCTYPE html>
<html lang="en-us">
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>aztex by thuctran289</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="stylesheets/normalize.css" media="screen">
<link href='http://fonts.googleapis.com/css?family=Open+Sans:400,700' rel='stylesheet' type='text/css'>
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen">
<link rel="stylesheet" type="text/css" href="stylesheets/github-light.css" media="screen">

<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<section class="page-header">
<h1 class="project-name">aztex</h1>
<h2 class="project-tagline">AZimpler Text editor. </h2>
<a href="https://github.com/thuctran289/aztex" class="btn">View on GitHub</a>
<a href="https://github.com/thuctran289/aztex/zipball/master" class="btn">Download .zip</a>
<a href="https://github.com/thuctran289/aztex/tarball/master" class="btn">Download .tar.gz</a>
</section>

<section class="main-content">
<h1>
<div class="wrapper">
<header>
<h1>aztex</h1>
<p>AZimpler Text editor. </p>

<p class="view"><a href="https://github.com/thuctran289/aztex">View the Project on GitHub <small>thuctran289/aztex</small></a></p>


<ul>
<li><a href="https://github.com/thuctran289/aztex/zipball/master">Download <strong>ZIP File</strong></a></li>
<li><a href="https://github.com/thuctran289/aztex/tarball/master">Download <strong>TAR Ball</strong></a></li>
<li><a href="https://github.com/thuctran289/aztex">View On <strong>GitHub</strong></a></li>
</ul>
</header>
<section>
<h1>
<a id="project-proposal" class="anchor" href="#project-proposal" aria-hidden="true"><span class="octicon octicon-link"></span></a>Project Proposal</h1>

<h3>
Expand Down Expand Up @@ -365,15 +374,37 @@ <h4>
<li>3 minutes - Key questions</li>
</ul>

<footer class="site-footer">
<span class="site-footer-owner"><a href="https://github.com/thuctran289/aztex">aztex</a> is maintained by <a href="https://github.com/thuctran289">thuctran289</a>.</span>
<h2>
<a id="feedback-and-decisions-1" class="anchor" href="#feedback-and-decisions-1" aria-hidden="true"><span class="octicon octicon-link"></span></a>Feedback and decisions</h2>

<span class="site-footer-credits">This page was generated by <a href="https://pages.github.com">GitHub Pages</a> using the <a href="https://github.com/jasonlong/cayman-theme">Cayman theme</a> by <a href="https://twitter.com/jasonlong">Jason Long</a>.</span>
</footer>
<p>The feedback we received mainly had to do with errors found in tokenizing our code and including other features. We also received a lot of feedback about whether or not we should use a library to generate LaTeX output. Not using the library might be a good idea since we already know how to write code in python, but we do not yet know how to efficiently implement this library into our code. From the feedback, we have also learned that we definitely should provide the user with the actual LaTeX code (not just the final pdf) in case they want to edit the LaTeX document themselves in order to add more customization to their pdf than aztex can allow. Furthermore, if we complete our MVP and still have time to spare, working on a GUI that users can chose to use would be nice. </p>

</section>
<p>Also we heard that we should include the following features:</p>


</body>
</html>
<ul>
<li>list with subelements (DONE) </li>
<li>list with sublists or indents </li>
<li>add argument for file name </li>
<li>one item list </li>
<li>nested elements (bold italicized things) </li>
<li>equations -&gt; tables (DONE) </li>
<li>check if library supports all things </li>
<li>if we write to a tex file people can learn latex </li>
<li>add test suite of example files </li>
<li>gui with equation buttons and side by side would be nice</li>
</ul>

<h3>
<a id="review-process-reflection-1" class="anchor" href="#review-process-reflection-1" aria-hidden="true"><span class="octicon octicon-link"></span></a>Review process reflection</h3>

<p>The review went well. We were able to follow our agenda, and we did get answers to our key questions, especially in regards to our question about if any of our features do not work or what other features we should include. Although we provided a lot of background context about how compilers work and are built, we probably should have provided an example to show people how to use our program. Although people eventually figured out what our program was supposed to output, some people were confused about what the output of our program was supposed to look like (apparently we did not clearly explain that the output was not supposed to be a nice looking pdf document). As a result, the actual process of getting people to test our code went differently than expected. We probably would have been able to get more feedback/test cases if they had more information on what to type and what the output was. Considering that this was also a code review, we probably should come in with more questions and content on actual coding decisions in the future. </p>
</section>
<footer>
<p>This project is maintained by <a href="https://github.com/thuctran289">thuctran289</a></p>
<p><small>Hosted on GitHub Pages &mdash; Theme by <a href="https://github.com/orderedlist">orderedlist</a></small></p>
</footer>
</div>
<script src="javascripts/scale.fix.js"></script>

</body>
</html>
17 changes: 17 additions & 0 deletions javascripts/scale.fix.js
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
var metas = document.getElementsByTagName('meta');
var i;
if (navigator.userAgent.match(/iPhone/i)) {
for (i=0; i<metas.length; i++) {
if (metas[i].name == "viewport") {
metas[i].content = "width=device-width, minimum-scale=1.0, maximum-scale=1.0";
}
}
document.addEventListener("gesturestart", gestureStart, false);
}
function gestureStart() {
for (i=0; i<metas.length; i++) {
if (metas[i].name == "viewport") {
metas[i].content = "width=device-width, minimum-scale=0.25, maximum-scale=1.6";
}
}
}
Loading

0 comments on commit 46efe48

Please sign in to comment.