JINZO Viewer 0.03

• Details
• Compatibility
• Download

Description

JINZO Viewer's trajectory

1. The beginning

One day, I received a message from BAB, who was using JINZO Paint.

"I want a viewer for pictures drawn with JINZO Paint"

Since I had acquired most of the programming know-how using JINZO Paint, I asked him to do the most troublesome thing for me, and he readily agreed.

Formulation of specifications for operation mode
Creating icon pictures (I think you can understand my lack of artistic talent by looking at JINZO Paint icons...(bitter smile)

As expected, determining the specifications is the most difficult.
2. Programming

I received the specifications and icon pictures from BAB, so I started programming right away. I don't remember having much trouble programming. I just messed around with the JINZO Paint source program. However, the dirtyness of the program is also inherited from JINZO Paint...
3. File specification

The only thing I was particular about was the file specification part. I use the file open dialog provided by WinCE standard in JINZO Paint, but it is still too difficult to use.

For the time being, I think the current method is the smartest for PsPC, but what do you think?
4. Color compatible

In addition to the E-55, which has 4 shades of gray, I also have the Jornada 680, which can produce color, so I made it compatible with color. The only image formats that can be handled are uncompressed BMP, 1bpp (2 colors) / 2bpp (4 colors) / 4bpp (16 colors) / 8bpp (256 colors) / 16bpp (65536 colors) / 24bpp (16.77 million colors). In the introduction on my homepage, I only introduce sample images with 4 shades of gray, so some people may not know that JINZO Viewer can also display color images.

In fact, he is a major player in Windows CE, and uses 2bpp (4 levels of gray) and 16bpp (65536 colors), both of which are not in the BMP standard. And both have problems...

In 2bpp, 1 pixel (1 dot) is treated as 2 bits. In other words, there are four colors: 00/01/10/11 in binary. For each color, 8-bit RGB color information is embedded in the BMP file. In other words, it can handle 4 out of 16.77 million colors. However, since E-55 and other models have four shades of gray (black, dark gray, light gray, and white), when looking at the four colors individually, the RGB values are the same.

For WindowsCE services and development environments (Visual C++ for WinCE), the values are as follows.
black { 0x00, 0x00, 0x00 }
Dark { 0x80, 0x80, 0x80 }
Thin { 0xC0, 0xC0, 0xC0 }
White { 0xFF, 0xFF, 0xFF }

However, some applications adopt the following values.
black { 0x00, 0x00, 0x00 }
Dark { 0x55, 0x55, 0x55 }
Thin { 0xAA, 0xAA, 0xAA }
White { 0xFF, 0xFF, 0xFF }

Apparently, in Microsoft's early development environment, the lower value was used. As expected from MS, I guess it's something.

At 16bpp (65536 colors), RGB values are expressed in 16 bits. If each RGB is 5 bits, there is 1 bit left over, but how to combine this 1 bit with the 5 bits of RGB (x3) to make 16 bits varies depending on the application.

Pocket IE palette information



Palette information for certain Win95/NT graphics tools

JINZO Viewer has no choice but to match PocketIE, but which one is correct...?
5. Cooperation with JINZO Paint

We received an inquiry from a user asking if it is possible to link with JINZO Paint. As mentioned above, JINZO Paint's file selection uses the WinCE standard file open dialog, so I was thinking that I had to do something about it, so I decided to mess things up by calling JINZO Paint from JINZO Viewer. I did (laughs).

Calling it is easy, but the problem is passing the file name. When I look at program books, I see complicated things like inter-process communication, but I don't feel like reading anything that seems like such a hassle. I decided to use the registry to easily transfer the information. It was easy because I used the source file of a program that manipulates the registry written by Mr. Ito as a reference.

6. Future plans

As a PsPC image viewer, there is nothing more to do. Supporting JPEG is troublesome. In HPC, perhaps we should stop displaying shortened file names and instead display the entire file name...

If you have any requests, please let me know. I would like to respond as much as possible.

Tags

Open Sourceviewerimage

Comments

No comments have been submitted against this application. Be the first!

You must be signed-in to post comments in the SCL. Not registered? Join our community.