A Sublime Text 3 Plugin for Java Development

====

• Features
• Important Updates
• Screenshots
• Command Categories
• Javatar Builds
• Javatar Calls
• Advanced Creations
• Javatar Operations
• Default Package Detection
• Installation
• Settings
• Key Bindings
• Build System
• Javatar Snippets
• Javatar Imports
• Additional Packages
• Package Channels
• Actions History

• [+] Package, Subpackage creation
• [+] Class (also Abstract), Interface, Enumerator snippets with package/class auto-complete
• [+] Project Compile
• [+] Package path in status bar
• [*] Organize Imports
• [*] Rename/Move packages/classes
• [-] JAR file export (included executable)
• [-] Dynamic method call auto-complete

[+] Available on Stable Channel
[*] Partial available on Development Channel
[-] Planned

====

From 15 Jan 2014, Javatar will include full Java SE7 class list inside its package. This will take a little longer to install/update Javatar. For other Java version, please check out Additional Packages section.

• Full Java SE7 Imports added (Java SE8 should coming soon...)
• Javatar Imports improvements, now types separated and also backward compatible
• QuickMenu updated
• Debug command added (Javatar Util)
• Typo fixed

• Improved Class Correction
• Many RegEx has been removed, please check it out if you are using it
• Some code tweaks
• Please check out an upcoming key bindings in Key Bindings section below

====

====

• Build: Accessed via command palette only
  • Build classes within package or project
  • More details on Javatar Builds
• Call:
  • Insert class and package informations such as current class path, class name or package name
  • More details on Javatar Calls
• Creation: Accessed via command palette only
  • Packages and classes creation
  • More details on Advanced Creations
• Operation:
  • Do class or package operation such as organize imports, rename class or package
  • More details on Javatar Operations

====

Javatar use its own build system which based on default Sublime Text's JavaC build settings.

Important! When build on a project or package, Javatar cannot show any compilation error (or may show only last run built) since it builds all your classes in order. More details about build system is on Build System.

Javatar Calls are use to insert class or package informations at cursor point. Javatar supports 4 types of informations to insert which are Full Package Path, Current Package Path, Full Class Name and Class Name.

In create menu, all packages and classes will be created relative to current package unless specified by ~ (tilde) before package or class path. See examples below...

Input: Alpha
Result as Class: Class "Alpha" is created in current pacakge
Result as Package: Package "Alpha" is created in current package

Input: ~Beta
Result as Class: Class "Beta" is created in default pacakge
Result as Package: Package "Beta" is created in default package

Input: me.spywhere.Alpha
Result as Class: Class "Alpha" is created in "(current package).me.spywhere" package
Result as Package: Package "Alpha" is created in "(current package).me.spywhere" package

Input: ~me.spywhere.Beta
Result as Class: Class "Beta" is created in "me.spywhere"
Result as Package: Package "Beta" is created in "me.spywhere"

Javatar Operations help you do class or package operations, such as organize imports or rename class, easier. Currently, Javatar has 2 operations, Correct Class and Organize Imports.

Javatar will search for current package and your class name based on file name and location of current file and correct it on first class.

Javatar will automatically imports all necessary packages and remove unused packages for you. This is done within 7 sub-steps.

1. Javatar gathering imports informations from current file
2. Javatar let's you select a package that has the same class
3. Javatar imports "default imports" and Java's packages
4. Javatar asks you to enter package name for missing classes
5. Javatar asks for package name that you want to enter manually
6. Javatar clear all imports in current file
7. Javatar imports all packages that has been processed within step 1-4

====

Javatar will specify default package with these steps...

1. Project folder in your project file (when open project or folder)
2. Folder contains current file (when open file)
3. Specify current package as (Unknown Package)

Javatar will refuse to create packages or classes within unknown package. In this case, mostly because current file is not on the disk yet.

====

Open command palette and type Install Package then type Javatar and hit Enter/Return. Package Control will automatically download, install and update for you.

Open your favourite Terminal application, browse to PACKAGES_PATH and run this command.

git clone git://github.com/spywhere/Javatar.git

Download .zip file from Javatar repository and browse to PACKAGES_PATH, extract .zip file and rename folder to Javatar, restart Sublime Text if you are currently open.

Note! PACKAGES_PATH is referred to folder which can be accessed via the Preferences > Browse Packages...

====

Settings can be accessed via the Preferences > Package Settings > Javatar or via command palette by type "Preference Javatar".

Default settings should not be modified. However, you can copy the relevant settings into Javatar's user settings file.

====

Key bindings can be accessed via the preference menu or via command palette same as settings.

All commands start with Key+Shift+K then follows by their shortcut key.

• Browse Commands... : Key+Shift+K
  • This will open quick panel, showing you all commands available to use.
• Help and Support... : Key+Shift+H
  • This will open quick panel, showing you all utilities that help solve the issue. (mostly requested to do by developer)
• Builds... : Key+Shift+B
  • This will open quick panel to select which build you want to perform.
• Calls... : Key+Shift+J
  • This will open quick panel to select which information you want to insert.
• Create new... : Key+Shift+L (@deprecated)
  • This will open quick panel to select which class you want to create.
• Operations... : Key+Shift+O
  • This will open quick panel to select which operation you want to perform.
• Insert full package path : Key+Shift+P (@deprecated)
  • Example
  • Package.Subpackage
• Insert current package name : Key+Shift+S (@deprecated)
  • Example:
  • SubPackage
• Insert current class name : Key+Shift+C (@deprecated)
  • Example:
  • Class
• Insert full class path : Key+Shift+F (@deprecated)
  • Example:
  • Package.SubPackage.Class

To reduce unnecessary key bindings and give more key bindings to new commands, the following key bindings will be changed soon...

• Create new... : Key+Shift+N
• Create new package : Key+Shift+P
  • This will open input panel, just like when you create a new package
• Organize Imports : Key+Shift+I
  • This will organize imports on current file
• All Javatar Calls key bindings will be removed and access by default Calls... instead

====

Javatar's build system use Sublime Text execute command to build your classes. Javatar build parameters are based on default Sublime Text's JavaC build settings. You can change the build command via Javatar settings file.

Javatar snippets is a dynamic snippet which will change part of the file to correspond with package path and class name. By using macros, you can specify which part of the file you want to fill the data to.

You can make your own snippet to use within Javatar by create a new file ends with .javatar

Snippet class tags (for more informations about snippet tags, see below) will be used as a type of classes which show in input panel when create a new file (%type% Name:), on error dialog (%type% %name% already exists) and in status bar when file was created (%type% %name% is created within package %package%).

Example of Javatar's snippets is inside Javatar's snippets folder (PACKAGES_PATH/Javatar/snippets or similar)

The following tags are used inside Javatar snippet files (*.javatar) which will be used by Javatar to display proper command to the user

• %class:TYPE OF CLASS%
• %description:DESCRIPTION TO SHOW UNDER CREATION COMMAND%

The following macros are used inside Javatar snippet files (*.javatar) which will be parsed by Javatar and Sublime Text.

• %package_path% = Package path
• %class% = Class name
• %file% = File path
• %file_name% = File name (equivalent to %class%.java)
• %package% = Package code (for example package java.utils; or same as package %packages_path%;)
• All Sublime Text's snippet macros can be used within Javatar snippets. For example: ${1} or ${2://Comment}

Javatar required imports file (*.javatar-imports) to correctly import necessary Java's packages. These files contain all classes and their packages to use with Javatar.

Imports file is a JSON file and has a very simple format. It is a list of a map which each key and value has following meaning...

• type
  • Must be a list of classes inside a package
• package
  • Package that contains all above classes. Leave this key empty to bypass type checking. (Such as default import that do not have to included)
• always_import
  • Always import this package even no class is used (this will import as package.*). This key is optional.

Example of Javatar Imports is inside Javatar's Java folder (PACKAGES_PATH/Javatar/Java)

In upcoming feature, Javatar will use a new imports format which support both organize imports and (upcoming) method completion feature. By default, Javatar package will include Java SE7 class list inside its package. This will make Javatar take a little longer to install/update from Package Control. For other Java version, you can check out a link to additional package inside Help and Support -> Additional Packages menu.

Stable channel is a default channel for every user who installed Javatar. This channel will release only fully working features and hide all incomplete features.

Development channel is a optional channel for user who want to try upcoming features which may not fully working or need improvements. All upcoming features will appear in Javatar: Browse Commands > Development Section only.

Please note that stable channel update notes also apply on development channel too.

In order to notice important notes to all users, in stable channel or development channel or both, Javatar use custom notification system which will notice you only once when Javatar is ready to use. You can opt out this notification by settings message_id to -1 in Javatar's user settings file, note that you can see update notes in README file or you will miss further important update notes.

Actions History tracks how you use Javatar and helps solve the problem. By provides useful informations as request by developer (only when you submit an issue). A Javatar Action History Report will looks like this when using it properly...

## Javatar Report
### System Informations
* Javatar Version: `13.10.27.0.59b`
* Sublime Version: `3047`
* Package Path: `/Users/spywhere/Library/Application Support/Sublime Text 3/Packages`
* Javatar Channel: `dev`
* Sublime Channel: `stable`
* Platform: `osx`
* As Packages: `True`
* Package Control: `True`
* Architecture: `x64`
* Javatar's Parent Folder: `Javatar`
* Is Project: `True`
* Is File: `True`
* Is Java: `True`

### Action List
1. Startup
2. Reset all settings
3. Reset all snippets
4. Read settings
5. Load snippets
6. Javatar Snippet AbstractClass.javatar loaded
7. Analyse snippet [file=/Users/spywhere/Library/Application Support/Sublime Text 3/Packages/Javatar/snippets/AbstractClass.javatar]
8. Javatar Snippet Class.javatar loaded
9. Analyse snippet [file=/Users/spywhere/Library/Application Support/Sublime Text 3/Packages/Javatar/snippets/Class.javatar]
10. Javatar Snippet Enumerator.javatar loaded
11. Analyse snippet [file=/Users/spywhere/Library/Application Support/Sublime Text 3/Packages/Javatar/snippets/Enumerator.javatar]
12. Javatar Snippet Interface.javatar loaded
13. Analyse snippet [file=/Users/spywhere/Library/Application Support/Sublime Text 3/Packages/Javatar/snippets/Interface.javatar]
14. Check news
15. Ready

Javatar do not automatically send these informations. You have to reply an issue with these informations yourself.

Actions History can be disabled by settings enable_actions_history to false