Finally, a correct version of classic “Hello world!” program.Continue reading
After over one year use and collecting pretty big document base (over 1G) I can measure/profile running application.
Each server round-trip takes more than 1.5 MB traffic. All the scripts and other static resources are being downloaded over and over again. Browser cache doesn’t really work because of secure connection limitations. HTTPS requests are not being cached on client side. Probably because of custom SSL certificate.
Anyway, I have decided to give a try to Vue.js and dramatically refactor whole application front end.
Long story short: I have successfully managed it. Performance has been definitely increased. Back end API improved, better structured and even simplified at important points.
Here are the problems to solve when switching from classic web to SPA (single-page application):
- An SPA framework required for front-end. UI programming is more complicated
- Server should be organised to deliver 3 types of resources:
- Static resources (images, styles, scripts)
- Dynamic API (for communication over AJAX/REST requests)
- Page addresses (specially configured for SPA) – which are visible URLs in browser
Problems to solve
- Missing tools for repository management, backup, inconsistency problems solving
- Multi-user access
- Versioning (history of changes)
- Cross-linking, referencing repository objects from/to other repository objects
- Off-line access
- Quick search
Solutions so far
Now I have a web application with some text output.
It’s time to find The Front-end Framework!
- Create new empty project in Bitbucket repository. Name: mizoine
- Create new Jira story “Mizoine – Issue tracking”
- IDE: Eclipse Oxygen
- Mylyn: Select task – Jira “Mizoine – Issue tracking”
- Project: Maven based
- Create new Maven project. Name: mizoine. Package: com.gratchev. Version: 0.0.1-SNAPSHOT
- Check Maven generated all appropriate folders, etc.
- Bind project with git repository from Bitbucket
Tools used so far
Create an issue tracking system inspired by Jira™.
Actually, same as Jira™, but with improvements:
- Completely based on file system:
- Simple and transparent back-ups, cloning, and everything what file system is good for
- Easy to setup, repair or monitor with existing tools
- Version tracking using git™
- Use only open and well-community-supported frameworks for everything
- Add features, missing in Jira
- Rename attachments
- Meta for attachments (description, dates)
- Move comments between issues
- Edit comments meta (creation date, etc.)
- Move attachments between issues
- Search by file name and description
- Improved previews and thumbnails for attachments (for example PDF thumbnails)
Step 1: Project identity
Use existing open tools for name generation. Do not invent a name.
Species name generator → Mizoine
Use existing open tools for icon generation.
Identicon generator: generate your identicon avatar
Project (in Eclipse)
Create new Maven project or open a Java project and add Maven Nature to it.
When you add new dependencies to the project (in pom.xml), Eclipse automatically downloads all required libraries (in JAR files) into Maven repository and sets appropriate links to the files in the project build path.
We will not use “Export to runnable JAR file” function of the Eclipse to create a JAR for our application. We will create this file using Maven ‘install’ goal instead. Continue reading
SWT and QT are excluded from the review because they’re not pure Java and require special installation of native components/libraries.