You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The library would be more useful to projects if the ATDL parsing into Java classes was split from the UI code and the project available via Maven repositories:
My proposal would be:
1 . Split the code into Maven submodes:
atdl-core - the ATDL parsing core
atdl-ui - the UI abstraction layer
atdl-swt - just the SWT specific code
atdl-swing - just the Swing specific code
atdl-all - the drop-in replacement for the current project.
Move the unmarshalling logic from AbstractAtdl4jCompositePanel#parseFixatdlFile to AtdlParser in atdl-core
Publish to Maven Central
I'm happy to prepare some PRs to work toward this if it'd be upstreamed.
The text was updated successfully, but these errors were encountered:
philipwhiuk
changed the title
Split ATDL parsing into Java from UI
Split the "ATDL parsing into Java" from the UI
Jun 8, 2022
Also, please use the following package names if possible:
atdl4j-core - the ATDL parsing core
atdl4j-ui - the UI abstraction layer
atdl4j-swt - just the SWT specific code
atdl4j-swing - just the Swing specific code
atdl4j - the drop-in replacement for the current project.
The library would be more useful to projects if the ATDL parsing into Java classes was split from the UI code and the project available via Maven repositories:
My proposal would be:
1 . Split the code into Maven submodes:
Move the unmarshalling logic from AbstractAtdl4jCompositePanel#parseFixatdlFile to AtdlParser in atdl-core
Publish to Maven Central
I'm happy to prepare some PRs to work toward this if it'd be upstreamed.
The text was updated successfully, but these errors were encountered: