dovyski / codebot Goto Github PK

Create a cool icon for Codebot and use it 😃

Create a set of scripts to build and deploy Codebot. Simplicity is key: the less stuff, the better.

Implement the shortcut mod+w to close the currently tab.

This task depends on #13 and #7.

There is no overflow in text, images are not being displayed properly. It needs a lot of love.

Implemente the project navigation/creation dropdown. The name of the currently open project must be displayed at the top of the files panel, followed by an icon. When the user clicks the project name, a dropdown presents all recent projects. Clicking any of them makes Codebot load the project.

The icon can be something like a + sign. If the user clicks the button, the new project dialog appears.

Implement the required development environment for "HTML5". This task depends on #29.

Implement a sliding panel to add SFX/music to a game. This task depends on #26.

Implement the SmartTypes API, which allows Codebot to show "mini-editors" for different file types. e.g. CSV files representing a tilemap are rendered using a spritesheet.

The tab system doesn't provide any mechanism to show/hide content. It should transparently hide content based on the currently active tab. Maybe use something like z-index to achieve that.

This task depends on #7.

Implement the project environment required for OUYA development. This task depends on #35.

Complete code editing tool, with a small but essential set of features, such as code completion, find, replace, preferences, projects, etc. No fancy sliding panels or project environments yet.

Implement the "Find" functionality for in-project search.

Make font bigger, maybe adjust background color, those kind of things.

Create Codebot website. Below is a few inspirational sites:

• http://www.frida.re/
• http://cordova.apache.org/
• http://www.awesomebox.co/
• http://www.codewars.com/?language=javascript

CodeMirror and mousetrap are conflicting. If the user is interacting outside the CodeMirror area, mousetrap works fine. If the cursor is within the CodeMirror area, mousetrap is unable to handle any key events.

Some files/dirs should not be displayed in the files panel, such as .git and Thumbs.db. Codebot must filter those files based on the user preferences, because if you want to see _everything_ in the editor, you can!

Implement a sliding panel to add assets, by category or package, to a game. This task depends on #26.

Files panel is not working properly. If new content is loaded (e.g. new project folder), the panel doesn't refresh its content.

Add tern.js to CodeMirror which enables the code completion.

FancyTree produces a LOT of debug/log messages. The minified version should suppress that, but for some reason it doesn't work with Codebot.

Those messages must be suppressed and/or the minified version must be fixed to work properly.

This is the current state of Codebot.

The current plugin system is extremely simple, archaic and hardcoded. A new one is required to create the foundation for several features, such as sliding panels.

Implement the required development environment for Java/Android. This task depends on #29.

Implement the required development environment for Haxe. This task depends on #29.

Add the option "new file" to the files panel context menu.

Codebot should remember what tabs/folders were open when it is re-launched. It's not a killer feature, but it helps.

Currently the editor mode is set to javascript no matter the file extension. Codebot should choose the editor mode based on the file being edited, e.g. css mode for .css files.

Work on Codebot layout to make it decent. Right now there are several sharp edges, e.g. tab bar is gray, editor is dark, etc.

I'm planning to mimic this awesome layout:

Add a sliding panel with Codebot preferences. Using those preferences, a user can fine tune everything in the application, such as theme, tab size, shortcuts, etc. All preferences must be stored in a JSON file.

Adjust content height based on window height. I don't know if I can do that with CSS, but the way to go now is with JS.

Implement the shortcut mod+q to quit the application.

This task depends on #13 and #7.

The asset finder, for instance, has a sub sliding panel that shows info about the selected asset. It cannot be closed directly, the user must click the X on the assets finder sliding panel instead.

Implement the shortcut mod+s to save the content of the current tab.

This task depends on #13 and #7.

The rename feature is not working properly in files panel when running on node-webkit. When running in the browser, it works (most of the time), but it's not deterministic.

Right now I'm using a FancyTree extension to enable the rename feature. A better approach is to re-implement everything from ground up without a extension.

Move config file from /ide-web/api/* to /ide-web/*.

Implement the shortcut mod+n to create a new file.

This task depends on #13 and #7.

Design and implement a project creation dialog/flow. I think the best approach present the user with two options: a simple and an advanced one, both as tabs in the dialog.

In the simple option, the user just choose a template, type in a few words (e.g. package name) and done. It's pretty much what Flashdevelop does.

The advanced option allows the user to make small choices and progress during the creation. E.g. choose platform, choose engine, tweak any details, done. Here Codebot can provide the user with more content e.g. if engine is Starling, create a basic skeleton for a Starling project.

Implement the required development environment for Flash/AIR. This task depends on #29.

Implement in-file "replace".

Implement the tilemap (.CSV, etc) smarttype.

Implement "Find" for in-file content.

All sliding panels should have the option to stack content, for instance when the user is using a sliding panel and must do something that requires a new sliding panel.

iOS does it pretty well. This demo by codedrops shows a really nice stackable menu too.

Right now both options are disabled.

The current tab code is a combination of chrome-tabs and Codebot code. It should be encapsulated in a new class, dispatching some events related to the tabs (focus, blur, etc).

The tab data should be standardized through all the API.

Project environment is a set of tools/plugins that Codebot uses to allow the development for an specific platform. For Flash gamedev, for instance, we need Flex/AIR SDK; HTML5 needs a web server, a JS minifier, etc.