About desktop interface and plug-in design ideas

About Desktop Interface development:

Desktop version of the interface to change the language.

The original consideration of the JAVAFX, familiar with the one weeks.

It is a dynamic scripting language that can theoretically be developed faster and has problems with the interoperability of Java classes.

Unfortunately, the current IDE (NetBeans IDE) does not fully leverage its strengths, and even the JavaFX NetBeans Plug-ins are beta-

For comparison, swing should be selected.

So this morning I redesigned the desktop version of the interface, and the prototype is out.

In the afternoon with the Dictionary engine service, you can already search for words:-)

However, the current problem is relatively large performance problems, and the results of the last discussion, the performance problem came out.

In the experiment, I loaded two dictionaries (physical size 20.4Mb, vocabulary total 620,000 or so), the index file completely loaded after the program runs at least 50Mb memory ....

The part about the index has to be redesigned.

So far, our first iteration has basically finished (14th number Iteration 0 end, just 2 weeks), we should pay attention to the project Management Center material, tasks, defects, issue plan.

Design ideas for supporting plugins:
Now the core of the word library engine is fixed and dynamic two classes. There are currently only stardict query engines under fixed, and XML based query/edit engine under dynamic.

I think the Fixed type Thesaurus query engine can be made into a support plug-in design that allows other developers to extend the query engine. As an example:

1. John developed an engine to support the dict.org dictionary format

2. Vanessa developed an engine that could search for words on Wikipedia

Their engine implements the interface of the fixed type engine and compiles it into a jar package, and our Thesaurus framework makes it easy to choose the dictionary engine we need. For users, it is possible to download the Word Library engine jar after the point, in the Stongeage Word Library engine management interface to a "Install Query Engine", later can easily select/reverse/uninstall the various engines. As long as the word library query engine enough, what other words in the world can not find it. This greatly facilitates the user.

The above only considers the fixed type of Thesaurus query , because the fixed query method has previously had a thesaurus format/Search service interface to specify that it is impossible to edit.

However, this has at least two advantages:

1. We can concentrate our efforts on the features of Open & real-time

2. Allow other developers of the Thesaurus engine to be more focused on the fixed type search

The above is only the current idea, technical aspects have also done some research:

Osgi4.1,eclipse3.x is using this specification (based on the Equinox framework)

This is the Java plug-in design currently in the industry is said to use the best, but the complexity of the technology itself still need to continue to experiment for a certain time.

Well, today again wordy a push, or that sentence: we have to actively discuss AH, the exchange of good physical and mental health:-)