have a connect button in the input dialog

To make tested code accessible without making everything public

Some of the exceptions are already handled and not necessary to print out the trace.
E.g. the RepoResponse exception when testing the branches with an imcomplete URL

Opening a file in a browser editor when a file is clicked without syntaxhighlighting, which is a consequent story.

we need to automatically build code_faces and deploy it to tomcat. potential technology is to use JRuby (http://jruby.org/).

1. build manually according to the RAP book or any articles online
2. deploy manually to the tomcat and test it out
3. automate the build process with JRuby (http://rake.rubyforge.org/)
4. automate the deployment process with JRuby (http://www.capify.org/index.php/Capistrano)

To disable this on the UI side instead of the server side.

We need an icon for the connect button.

We could just provide a gif in a html that saying the page is loading. It's in the branding -> body extension point. Details in http://www.ajaxload.info/.

Refactored github implementation to another plugin and use extension for corresponding service query.

we want it to wait for a certain amount of time and then release it back the client.

To populate RepoFile using the RepoService.getRepoFile(RepoFileLite)

steps to reproduce:

1. open the repo with http://github.com/jingweno/ruby_grep
2. expand the files and click on the RakeFile file (http://github.com/jingweno/ruby_grep/blob/master/Rakefile)
3. it's not highlighted even if the lang attribute is correctly input

The problem may be related to highlighter.js

acceptance criteria

1. A button to pop up a dialog to connect to the repo
2. A dialog to input all the required info, including http/git url, username and password
3. The input info is hooked up with the project explorer

this includes:

• handled the ExecutionException(wrapper of MalformedURL, RepoResponse, and RepoConnection) in ShowReposioryDialog
• handled and group the "impossible exceptions" (NotDefinedException, NotEnabledException, NotHandledException) in ShowReposioryDialog and SwitchBranchDropDownButton

some of the css/html/javascript files in the public folder are still obfuscated

for the consideration of performance.

RepoService.getRepo takes git URL as well, e.g., [email protected]:jingweno/ruby_grep.git

put the build in a folder called target along with other source project folder

The user is able to put in the restful URL in the address with all the info instead of manually type them in the branch selection dialog.

For example, http://codefaces.org/navigate?url=https://github.com/jingweno/code_faces&user=jingweno&password=password

may extend to Restful later

Create a public GitHub repo for unit testing. All kinds of file types should be included.

put context.xml in build/configs or build/tempate and include it in the war file. http://wiki.eclipse.org/RAP/FAQ#How_to_run_a_RAP_application_in_multiple_browser_tabs.2Fwindows.3F

we need a file management system that connects file extension, mime type, and editor to open.

currently it is done by:
newRepoBranch.getParent().getName().equals(workingRepo.getName())

move the raw files to /private, create the production version in the /public

Form here http://softwaremaniacs.org/media/soft/highlight/test.html, GitHub, IDEA(InteliJ) and Visual Studio all look good.

acceptance criteria:

• display folder/file tree structure in order to reduce navigation cost

We need exceptions that provide more information, e.g., messages that tell us what goes wrong. We only have RepoServiceException. Potential improvement could be adding messages to RepoServiceException and having GitHubServiceException

Wrapping over the Object API to create corresponding RepoFile and RepoFolder (http://develop.github.com/p/object.html).

The GitHub restful URL is http://github.com/api/v2/json/tree/show/:user_name/:repo_name/:SHA. An example is http://github.com/api/v2/json/tree/show/jingweno/ruby_grep/7b12ed0f174aaf84e426209986665c13d1170706.

for extension purpose.

1. Wrap the workbench window components with custom variant CSS tag
2. Reuse the existing StackPresentation by extending ConfigurableStack and implementing AbstractStackPresentation using composition (the methods are final)
3. The default stack presentation should be TabbedStackPresentation

Steps to reproduce:
[1] Show the import repository dialog
[2] Disconnect the network
[3] Unable to show the branch information and no indication that there is a connection problem