Easy-language writing support library can also play "Flowers" (easy-to-write Library (exek) Progress 5)

In easy language, you can use the "Easy-to-write (exek)" function to develop easy-to-language support libraries. Not only are there no functional limitations, but you can also play with the "Flowers, even the "Flowers" that others cannot play.

 

I. Do not use command Classification

Commands in the supported libraries are generally divided into several categories. For example, commands in the core library of easy language are divided into "process control", "arithmetic operation", "logical comparison", "bit operation", "variable operation", and "array operation. This is of course necessary for the core library. After all, there are hundreds of commands in it. Only clear classification makes it easier for users to search and remember.

However, if the number of commands in the supported database is small, or the Logic belongs to the same category, is it necessary to classify the commands? In this case, the command classification is another option? There are many examples, such as "Easy wizard support library", "executable file data conversion support library", "encoding conversion support library", and "multi-thread support library". The command function, it is redundant to separate a command category because the names of supported databases are redundant and redundant.

In such cases, can we avoid command classification? The answer is yes. The following is a supported database developed using the "Easy-to-write (exek)" function. It does not have a command classification. All commands support direct branches of the Database Root Node:

Haha, we can still play like this. I'm afraid Wu didn't even think of it. I used some tips. I usually don't tell him/her. OthersProgramming LanguageThe easy-language support library developed requires a lot of effort to achieve this effect. So far, I have not seen any supported database that has commands but no command classification (who has seen it? Please advise ). (The specific practices in the easy-to-write Library have been written in the "Easy-to-write Library (exek) Development Manual". In this blog, you can find the progress of the easy-to-write Library (exek) (3) (2008.8.26 )).

 

2. Provides command classification icons and command icons

In the easy language core library, many command categories have their own icons, and many commands have their own icons. These icons are displayed in the "support library" sub-folder of the easy language ide work folder, before the command category and before the command name, see:

Except for the core library, I have not seen any other support library that defines command classification icons or command icons. They all use the default icons, Which is boring. It is easy to define these icons in the support libraries developed using "easy to write (exek)". See:

Some changes will make people shine. The problem is, we have a very low cost. Why?

In addition, the easy-to-write Library (exek) also supports dynamic icons (animation icons) for commands and command parameters. However, this feature can be extracted only in IDE of easy language version 3.x.

 

Summary:

The above "Flowers" may not be the patents of "easy to write (exek)", but they seldom see other support libraries to play with such "Flowers"-in addition to the core library, almost no. Why? Why don't they play "Flowers? C/C ++, Delphi, and assembly are not all super Nb programming languages? I guess this is probably not the reason: it is very time-consuming to develop an easy-language support library in those programming languages, so that the support library developers are reluctant to spend extra energy on "spending; in easy language, it is too easy to use the "easy to write (exek)" development support library. If you don't want to play with the "Flowers", you feel that the energy is nowhere to release. (Of course, I am the only bored person in the world .)