Skip to content
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

Closed
Col-E opened this issue Mar 9, 2018 · 6 comments
Closed

Future changes (re-write) #45

Col-E opened this issue Mar 9, 2018 · 6 comments

Comments

@Col-E
Copy link
Owner

Col-E commented Mar 9, 2018

So I'm currently drafting up a total redesign.

  • The design / architecture is totally different, it is now primarily event-driven.
  • UI is completely reworked in JavaFX (WIP, subject to change).
  • Input (jar or class) is parsed as a virtual-file-system which will allow some new nifty features in the future.
  • Hopefully move away from MDI (multiple inner window UI), not at this point but looking into it. (Editing methods side by side is still a goal though)

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".

@Col-E
Copy link
Owner Author

Col-E commented Mar 13, 2018

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).

Should the interfaces (as a list editor) be displayed in a new window (on-button-click) or should it be in-line (replace the button)?

For other list attributes I'm thinking that a separate window would be wise since they represent more complex structures than a String.

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.

This was referenced Apr 11, 2018
@Col-E
Copy link
Owner Author

Col-E commented Apr 30, 2018

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.

@Col-E
Copy link
Owner Author

Col-E commented May 4, 2018

Some progress screenshots:

@Col-E
Copy link
Owner Author

Col-E commented May 15, 2018

New site design:

  • Index
  • Proper mobile css
    • Content adjusts to screen dimensions, unlike current layout where the whole thing scales in a not so clean way.

@Col-E
Copy link
Owner Author

Col-E commented May 23, 2018

This week's progress:

I want to finish up the docs / usage guide and I'll push to a new branch for testing.

@Col-E
Copy link
Owner Author

Col-E commented May 25, 2018

Merged early because I want the new content to be front-and-center. Old versions can be accessed via commit history / releases anyways.

@Col-E Col-E closed this as completed May 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant