New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future changes (re-write) #45
Comments
Beginning to allow modification through the UI. This is the current layout. I currently am choosing how to represent class properties in the UI. Right now as a placeholder the interfaces attribute is seen as a button (that does nothing).
Decided to go with button -> new window approach for non-simple types. Edit: April 2018, still working. I will push to github whenever its at a release-worthy point. |
Only major features missing until the rewrite is release worthy is the bytecode list and associated features (block saving/writing). Everything else (Config / searching / exporting / non-opcode editable attributes) is done. I'll be pushing to a new branch when these things are added. Then when absolutely everything is back 100% I'll merge into master. |
New site design:
|
This week's progress: I want to finish up the docs / usage guide and I'll push to a new branch for testing. |
Merged early because I want the new content to be front-and-center. Old versions can be accessed via commit history / releases anyways. |
So I'm currently drafting up a total redesign.
Since I'm doing things from the ground up now would be the best time to implement some wild changes (suggestions?), that were previously impossible. When these changes are done the next release will be
1.0
and will no longer be classified as a "pre-release".The text was updated successfully, but these errors were encountered: