Moving to AppFrameWork Sun, Dec 28. 2008
Shortly before christmas I finished the work on the prototype, tagged this version and began a major overhaul of the application structure. I based the application on Swinglab's AppFrame and SwingWorker. This Desktop-Framework allows me to have a unified multithread application with some good application guide lines.
So far I only developed my prototype around an application-structure, that a mix of the basics I learned in Java, some influences from my work with Ruby-on-rails and some evil work arounds to achieve my goals. AppFramework should optimise this and get the application in a better shape.
There are many new things I have to use with AppFramework, for example Introspection or Annotated Object creation for the Actions. So my app is changing alot at the moment.
I'm also thinking how the actual GUI will look like. I'd like to keep it clean and simple, but I have to see what will be used actually.
So far I only developed my prototype around an application-structure, that a mix of the basics I learned in Java, some influences from my work with Ruby-on-rails and some evil work arounds to achieve my goals. AppFramework should optimise this and get the application in a better shape.
There are many new things I have to use with AppFramework, for example Introspection or Annotated Object creation for the Actions. So my app is changing alot at the moment.
I'm also thinking how the actual GUI will look like. I'd like to keep it clean and simple, but I have to see what will be used actually.
« previous page
(Page 1 of 1, totaling 1 entries)
next page »
