fltk-1.1.7-source.zip_FLTK_fltkwindo_fltk-1.1.7_轻量级ui

共1273个文件

cxx：248个

h：180个

vcproj：140个

版权申诉

fltk

5星 · 超过95%的资源 13 浏览量 2022-09-21 05:00:36 上传评论收藏 3.16MB ZIP 举报

资源推荐

资源详情

资源评论

收起资源包目录

fltk-1.1.7-source.zip_FLTK_fltk windo_fltk-1.1.7_轻量级ui （1273个子文件）

libpng.3 160KB

libpngpf.3 24KB

zlib.3 4KB

png.5 2KB

ANNOUNCE 1KB

ANNOUNCEMENT 13KB

fltk.book 2KB

fltklib.bpf 210B

fltk.bpf 202B

image.bpf 98B

tiled_image.bpf 98B

navigation.bpf 98B

doublebuffer.bpf 98B

help.bpf 98B

cube.bpf 98B

fonts.bpf 98B

curve.bpf 98B

tile.bpf 98B

subwindow.bpf 98B

bitmap.bpf 98B

resizebox.bpf 98B

pack.bpf 98B

label.bpf 98B

fltk_app_template.bpf 98B

menubar.bpf 98B

symbols.bpf 98B

clock.bpf 98B

pixmap.bpf 98B

keyboard.bpf 98B

output.bpf 98B

cursor.bpf 98B

forms.bpf 98B

line_style.bpf 98B

boxtype.bpf 98B

colbrowser.bpf 98B

iconize.bpf 98B

file_chooser.bpf 98B

shape.bpf 98B

arc.bpf 98B

checkers.bpf 98B

hello.bpf 98B

browser.bpf 98B

button.bpf 98B

fluid.bpf 98B

overlay.bpf 98B

fullscreen.bpf 98B

fractals.bpf 98B

color_chooser.bpf 98B

message.bpf 98B

input.bpf 98B

buttons.bpf 98B

minimum.bpf 98B

scroll.bpf 98B

demo.bpf 98B

ask.bpf 98B

pixmap_browser.bpf 98B

editor.bpf 98B

fltk.bpg 6KB

fltklib.bpr 29KB

fltk.bpr 26KB

fluid.bpr 6KB

fractals.bpr 4KB

pixmap_browser.bpr 4KB

fltk_app_template.bpr 4KB

color_chooser.bpr 4KB

browser.bpr 4KB

doublebuffer.bpr 4KB

file_chooser.bpr 4KB

tiled_image.bpr 4KB

navigation.bpr 4KB

fullscreen.bpr 4KB

line_style.bpr 4KB

colbrowser.bpr 4KB

subwindow.bpr 4KB

resizebox.bpr 4KB

keyboard.bpr 4KB

checkers.bpr 4KB

boxtype.bpr 4KB

minimum.bpr 4KB

buttons.bpr 4KB

menubar.bpr 4KB

overlay.bpr 4KB

message.bpr 4KB

iconize.bpr 4KB

symbols.bpr 4KB

bitmap.bpr 4KB

button.bpr 4KB

editor.bpr 4KB

scroll.bpr 4KB

pixmap.bpr 4KB

output.bpr 4KB

cursor.bpr 4KB

forms.bpr 4KB

label.bpr 4KB

image.bpr 4KB

clock.bpr 4KB

curve.bpr 4KB

fonts.bpr 4KB

shape.bpr 4KB

hello.bpr 4KB

共 1273 条

USING THE IJG JPEG LIBRARY

This file is part of the Independent JPEG Group's software.

For conditions of distribution and use, see the accompanying README file.

This file describes how to use the IJG JPEG library within an application

program. Read it if you want to write a program that uses the library.

The file example.c provides heavily commented skeleton code for calling

the

JPEG library. Also see jpeglib.h (the include file to be used by

application

programs) for full details about data structures and function parameter

lists.

The library source code, of course, is the ultimate reference.

Note that there have been *major* changes from the application interface

presented by IJG version 4 and earlier versions. The old design had

several

inherent limitations, and it had accumulated a lot of cruft as we added

features while trying to minimize application-interface changes. We have

sacrificed backward compatibility in the version 5 rewrite, but we think

the

improvements justify this.

TABLE OF CONTENTS

-----------------

Overview:

Functions provided by the library

Outline of typical usage

Basic library usage:

Data formats

Compression details

Decompression details

Mechanics of usage: include files, linking, etc

Advanced features:

Compression parameter selection

Decompression parameter selection

Special color spaces

Error handling

Compressed data handling (source and destination managers)

I/O suspension

Progressive JPEG support

Buffered-image mode

Abbreviated datastreams and multiple images

Special markers

Raw (downsampled) image data

Really raw data: DCT coefficients

Progress monitoring

Memory management

Memory usage

Library compile-time options

Portability considerations

Notes for MS-DOS implementors

You should read at least the overview and basic usage sections before

trying

to program with the library. The sections on advanced features can be

read

if and when you need them.

OVERVIEW

========

Functions provided by the library

---------------------------------

The IJG JPEG library provides C code to read and write JPEG-compressed

image

files. The surrounding application program receives or supplies image

data a

scanline at a time, using a straightforward uncompressed image format.

All

details of color conversion and other preprocessing/postprocessing can be

handled by the library.

The library includes a substantial amount of code that is not covered by

the

JPEG standard but is necessary for typical applications of JPEG. These

functions preprocess the image before JPEG compression or postprocess it

after

decompression. They include colorspace conversion,

downsampling/upsampling,

and color quantization. The application indirectly selects use of this

code

by specifying the format in which it wishes to supply or receive image

data.

For example, if colormapped output is requested, then the decompression

library automatically invokes color quantization.

A wide range of quality vs. speed tradeoffs are possible in JPEG

processing,

and even more so in decompression postprocessing. The decompression

library

provides multiple implementations that cover most of the useful tradeoffs,

ranging from very-high-quality down to fast-preview operation. On the

compression side we have generally not provided low-quality choices, since

compression is normally less time-critical. It should be understood that

the

low-quality modes may not meet the JPEG standard's accuracy requirements;

nonetheless, they are useful for viewers.

A word about functions *not* provided by the library. We handle a subset

the ISO JPEG standard; most baseline, extended-sequential, and progressive

JPEG processes are supported. (Our subset includes all features now in

common

use.) Unsupported ISO options include:

* Hierarchical storage

* Lossless JPEG

* Arithmetic entropy coding (unsupported for legal reasons)

* DNL marker

* Nonintegral subsampling ratios

We support both 8- and 12-bit data precision, but this is a compile-time

choice rather than a run-time choice; hence it is difficult to use both

precisions in a single application.

By itself, the library handles only interchange JPEG datastreams --- in

particular the widely used JFIF file format. The library can be used by

surrounding code to process interchange or abbreviated JPEG datastreams

that

are embedded in more complex file formats. (For example, this library is

used by the free LIBTIFF library to support JPEG compression in TIFF.)

Outline of typical usage

------------------------

The rough outline of a JPEG compression operation is:

Allocate and initialize a JPEG compression object

Specify the destination for the compressed data (eg, a file)

Set parameters for compression, including image size & colorspace

jpeg_start_compress(...);

while (scan lines remain to be written)

jpeg_write_scanlines(...);

jpeg_finish_compress(...);

Release the JPEG compression object

A JPEG compression object holds parameters and working state for the JPEG

library. We make creation/destruction of the object separate from

starting

or finishing compression of an image; the same object can be re-used for a

series of image compression operations. This makes it easy to re-use the

same parameter settings for a sequence of images. Re-use of a JPEG object

also has important implications for processing abbreviated JPEG

datastreams,

as discussed later.

The image data to be compressed is supplied to jpeg_write_scanlines() from

in-memory buffers. If the application is doing file-to-file compression,

reading image data from the source file is the application's

responsibility.

The library emits compressed data by calling a "data destination manager",

which typically will write the data into a file; but the application can

provide its own destination manager to do something else.

Similarly, the rough outline of a JPEG decompression operation is:

Allocate and initialize a JPEG decompression object

Specify the source of the compressed data (eg, a file)

Call jpeg_read_header() to obtain image info

Set parameters for decompression

jpeg_start_decompress(...);

while (scan lines remain to be read)

jpeg_read_scanlines(...);

jpeg_finish_decompress(...);

Release the JPEG decompression object

This is comparable to the compression outline except that reading the

datastream header is a separate step. This is helpful because information

about the image's size, colorspace, etc is available when the application

selects decompression parameters. For example, the application can choose

output scaling ratio that will fit the image into the available screen

size.

The decompression library obtains compressed data by calling a data source

manager, which typically will read the data from a file; but other

behaviors

can be obtained with a custom source manager. Decompressed data is

delivered

into in-memory buffers passed to jpeg_read_scanlines().

It is possible to abort an incomplete compression or decompression

operation

by calling jpeg_abort(); or, if you do not need to retain the JPEG object,

simply release it by calling jpeg_destroy().

JPEG compression and decompression objects are two separate struct types.

However, they share some common fields, and certain routines such as

jpeg_destroy() can work on either type of object.

The JPEG library has no static variables: all state is in the compression

or decompression object. Therefore it is possible to process multiple

compression and decompression operations concurrently, using multiple JPEG

objects.

Both compression and decompression can be done in an incremental memory-

to-

memory fashion, if suitable source/destination managers are used. See the

section on "I/O suspension" for more details.

BASIC LIBRARY USAGE

===================

Data formats

------------

Before diving into procedural details, it is helpful to understand the

image data format that the JPEG library expects or returns.

The standard input image format is a rectangular array of pixels, with

each

pixel having the same number of "component" or "sample" values (color

channels). You must specify how many components there are and the

colorspace

interpretation of the components. Most applications will use RGB data

(three components per pixel) or grayscale data (one component per pixel).

PLEASE NOTE THAT RGB DATA IS THREE SAMPLES PER PIXEL, GRAYSCALE ONLY ONE.

A remarkable number of people manage to miss this, only to find that their

programs don't work with grayscale JPEG files.

There is no provision for colormapped input. JPEG files are always full-

color

or full grayscale (or sometimes another colorspace such as CMYK). You can

feed in a colormapped image by expanding it to full-color format. However

JPEG often doesn't work very well with source data that has been

colormapped,

because of dithering noise. This is discussed in more detail in the JPEG

FAQ

and the other references mentioned in the README file.

Pixels are stored by scanlines, with each scanline running from left to

right. The component values for each pixel are adjacent in the row; for

example, R,G,B,R,G,B,R,G,B,... for 24-bit RGB color. Each scanline is an

array of data type JSAMPLE --- which is typically "unsigned char", unless

you've changed jmorecfg.h. (You can also change the RGB pixel layout, say

to B,G,R order, by modifying jmorecfg.h. But see the restrictions listed

that file before doing so.)

A 2-D array of pixels is formed by making a list of pointers to the starts

scanlines; so the scanlines need not be physically adjacent in memory.

Even

if you process just one scanline at a time, you must make a one-element

pointer array to conform to this structure. Pointers to JSAMPLE rows are

type JSAMPROW, and the pointer to the pointer array is of type JSAMPARRAY.

The library accepts or supplies one or more complete scanlines per call.

It is not possible to process part of a row at a time. Scanlines are

always

processed top-to-bottom. You can process an entire image in one call if

you

have it all in memory, but usually it's simplest to process one scanline

a time.

For best results, source data values should have the precision specified

评论收藏

内容反馈

版权申诉

西山樵夫

2024-04-01

资源内容总结地很全面，值得借鉴，对我来说很有用，解决了我的燃眉之急。

weixin_42651887

粉丝: 76
资源: 1万+

fltk-1.1.7-source.zip_FLTK_fltk windo_fltk-1.1.7_轻量级ui

fltk-1.1.7-source.zip_FLTK_FLTK 1.1_vega

fltk-1.1.6-source.zip_FLTK_FLTK 1.1.x_FLTK-1.1_fltk 跨平台_开发包

fltk-1.0.11-source.zip_Fltk-1.3.2_UI 嵌入式_fltk editer_嵌入式系统_轻量级u

fltk-1.1.10-source.zip

fltk-static-1.3.4-2.el7.x86_64.rpm

fltk-1.3.3-source.tar.gz

fltk-2.0.x-r5764.tar.gz_FLTK 2.0_FLTK2 linux_fltk-2.0.x-r4773_n

fltk-2.0.x-r6403.tar.gz

fltk-1.3.1-source.tar.gz_开源GUI

fltk-2.0.x-r6671.tar.gz_FLTK_fltk-2.0

fltk-static-1.3.4-2.el7.i686.rpm

编译PTAM所需要的库

fltk-fluid-1.3.4-2.el7.x86_64(1) (1).rpm

fltk-1.3.4-2-source.tar.gz

fltk-1.3.x-r9933.tar.bz2

fltk-1.1.9-gcc3.x-1bibosoft.DevPak

fltk-1.3.4-5.el8.x86_64.rpm

fltk-devel-1.3.4-5.el8.x86_64.rpm

fltk-1.3.4-2.el7.x86_64(1) (1).rpm

冰河的渗透实战笔记-冰河.pdf

大灰狼远控2021最新版，解压密码222

J-LINK V10 V11固件.rar

ISO21434.pdf

Web安全漏洞扫描工具-AWVS14

CTF 竞赛入门指南（ctf-all-in-one）.pdf

Web中间件常见漏洞总结.pdf

stm32f103 adc采样+dma传输+fft处理 频率计_fft处理_stm32_ADCFFT_频率计_ADC采样_

jts-1.14.zip

CobaltStrike4.4.zip

最新资源

stm32f103 adc采样+dma传输+fft处理频率计_fft处理_stm32_ADCFFT_频率计_ADC采样_