List view
List of features we know are desired because we've had user feedback. Prioritised for rapid agile delivery.
No due date•31/58 issues closedBacklog of unprioritised ideas not linked to any milestone
No due date•0/5 issues closedFurther developer workflow improvements. These are mainly the things that will widen out the appeal of Paladin to other developers. It is a convenience set of features rather than a single big change.
No due date•0/11 issues closedSupport the writing, compiling, and executing of tests within Paladin. Also write tests for Paladin's code itself, and use Paladin to fix issues resulting from those tests.
No due date•0/10 issues closedFix things that are bound to have broken since new features were added, or low priority bugs not often encountered or with workarounds.
No due date•1/2 issues closedA small number of complex issues that will affect the long term direction of Paladin. This is where new ideas can be tried out and tested individually without affecting the core code base. E.g. support for different editors than Pe, or tighter integration of Pe (if possible).
No due date•1/10 issues closedBuild on Paladin on Paladin by supporting common Haiku developers workflows. Should focus on supporting common Haiku project types, making the workflow easy, minimising distractions, and making coding in Paladin efficient and rewarding for developers.
No due date•0/28 issues closedGet Paladin in to a state whereby a developer can successfully code, build, and test Paladin without leaving the Paladin UI itself. Features: Build system and SCM plugins. Better runtime debugging and command line options. Tutorial/in app help plugin.
No due date•18/53 issues closed