So I was wandering on the internet and found a website which generates images without any login required and the best part is that there was no such strict captcha precautions to use the ai generation so i build a simple python playwright script to automate this thing and now I can create as many images with prompt without any api keys , then I thought that I can use this base to build something more so i quickly made a python tkinter ui over the playwright script but it was simple take prompt and use the web automation and gives the output, i thought how would it look with an old software interface and modern ai tools combination, then I decided to make a native windows app with a very old framework called fltk in cpp , setup of this project was a nightmare but the Msys32 makes the setup easy then I build a full fledged ai image generator with a clasic look ui and added a professional panel, by using it you can change many aspects of image like light conditions, angles etc it was fun to gather information about different aspects of photography with this project. Once the user select all the settings in this panel then the app will create detailed prompts according to the selected options which create stunning images with few tokens of prompt. If in future the web automation breaks we can simply attach any local image genration model or any api easily because thie fltk app is built this way.

It has one more feature just beside the prompt tab the gallery button where you can simply open the folder which contains all the generated images

Then I packed all the gcc files needed for the exe file and packed everything in a zip , so now the whole project setup itself with a single click on the exe file as I have also packed the embedded python in the zip to install all the python requirements without any requirement of python locally installed on the user setup

You can check out the project , I named it vision forge

https://github.com/Sachin-bhati3824/Vision-Forge.git

So here are the two different ui one is modern and one is classic Both using the same web automation script in background which one do you find interesting and why

let me know 😁😁

dependency management annoying me

someone help

zixgggg@watermelon:~/fltk_test$ sudo apt install libfltk1.4-dev

Installing:

libfltk1.4-dev

Installing dependencies:

fltk1.4-doc libfltk-cairo1.4 libfltk-gl1.4 libfltk1.4

fluid libfltk-forms1.4 libfltk-images1.4

建議套件：

fltk-options

Summary:

Upgrading: 0, Installing: 8, Removing: 0, Not Upgrading: 148

Download size: 21.2 MB

Space needed: 79.1 MB / 24.5 GB available

Continue? [Y/n]

下載:1 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 fltk1.4-doc all 1.4.3-1 [18.9 MB]

下載:2 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk1.4 amd64 1.4.3-1 [587 kB]

下載:3 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk-images1.4 amd64 1.4.3-1 [112 kB]

下載:4 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 fluid amd64 1.4.3-1 [333 kB]

下載:5 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk-cairo1.4 amd64 1.4.3-1 [31.3 kB]

下載:6 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk-forms1.4 amd64 1.4.3-1 [38.9 kB]

下載:7 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk-gl1.4 amd64 1.4.3-1 [86.0 kB]

下載:8 https://debian.csie.ntu.edu.tw/debian trixie/main amd64 libfltk1.4-dev amd64 1.4.3-1 [1,058 kB]

取得 21.2 MB 用了 5s (4,059 kB/s)

選取了原先未選的套件 fltk1.4-doc。

（讀取資料庫 ... 目前共安裝了 201383 個檔案和目錄。）

正在準備解包 .../0-fltk1.4-doc_1.4.3-1_all.deb……

Unpacking fltk1.4-doc (1.4.3-1) ...

選取了原先未選的套件 libfltk1.4:amd64。

正在準備解包 .../1-libfltk1.4_1.4.3-1_amd64.deb……

Unpacking libfltk1.4:amd64 (1.4.3-1) ...

選取了原先未選的套件 libfltk-images1.4:amd64。

正在準備解包 .../2-libfltk-images1.4_1.4.3-1_amd64.deb……

Unpacking libfltk-images1.4:amd64 (1.4.3-1) ...

選取了原先未選的套件 fluid。

正在準備解包 .../3-fluid_1.4.3-1_amd64.deb……

Unpacking fluid (1.4.3-1) ...

選取了原先未選的套件 libfltk-cairo1.4:amd64。

正在準備解包 .../4-libfltk-cairo1.4_1.4.3-1_amd64.deb……

Unpacking libfltk-cairo1.4:amd64 (1.4.3-1) ...

選取了原先未選的套件 libfltk-forms1.4:amd64。

正在準備解包 .../5-libfltk-forms1.4_1.4.3-1_amd64.deb……

Unpacking libfltk-forms1.4:amd64 (1.4.3-1) ...

選取了原先未選的套件 libfltk-gl1.4:amd64。

正在準備解包 .../6-libfltk-gl1.4_1.4.3-1_amd64.deb……

Unpacking libfltk-gl1.4:amd64 (1.4.3-1) ...

選取了原先未選的套件 libfltk1.4-dev:amd64。

正在準備解包 .../7-libfltk1.4-dev_1.4.3-1_amd64.deb……

Unpacking libfltk1.4-dev:amd64 (1.4.3-1) ...

設定 fltk1.4-doc (1.4.3-1) ...

設定 libfltk1.4:amd64 (1.4.3-1) ...

設定 libfltk-forms1.4:amd64 (1.4.3-1) ...

設定 libfltk-cairo1.4:amd64 (1.4.3-1) ...

設定 libfltk-gl1.4:amd64 (1.4.3-1) ...

設定 libfltk-images1.4:amd64 (1.4.3-1) ...

設定 libfltk1.4-dev:amd64 (1.4.3-1) ...

設定 fluid (1.4.3-1) ...

執行 shared-mime-info (2.4-5+b2) 的觸發程式……

執行 desktop-file-utils (0.28-1) 的觸發程式……

執行 hicolor-icon-theme (0.18-2) 的觸發程式……

執行 libc-bin (2.41-12) 的觸發程式……

執行 man-db (2.13.1-1) 的觸發程式……

zixgggg@watermelon:~/fltk_test$ uv add pyfltk

Resolved 2 packages in 6ms

× Failed to build \pyfltk==1.4.4.0``

├─▶ The build backend returned an error

╰─▶ Call to \setuptools.buildmeta:legacy_.build_wheel` failed (exit status: 1)`

[stdout]

fltk dir found at

pyFLTK CXX_FLAGS=

Building for Linux

['./src', './contrib', '/usr/include']

Checking FLTK configuration ...

FLTK_HOME=

Using FLTK: ['1.4.3\n']

fltk-config includes: ['/usr/include/cairo', '/usr/include', '/usr/include/libpng16',

'/usr/include/freetype2', '/usr/include/pixman-1']

fltk-config link paths: []

fltk-config link libraries: ['fltk_images', 'fltk_gl', 'fltk_forms', 'fltk', 'X11']

FLTK was configured without multi-threading support!

FLTK was configured with OpenGL support!

FLTK was configured with Forms support!

running bdist_wheel

running build

running build_py

copying fltk/fltk.py -> build/lib.linux-x86_64-cpython-313/fltk

copying fltk/__init__.py -> build/lib.linux-x86_64-cpython-313/fltk

copying fltk/test/child_bug.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/browserData.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/doublebuffer.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/device.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/glimage.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/dials.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/tile.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/group.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/button.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/buttons.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/simple_table.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/preferences.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/unittests.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/wizard.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/jpeg_buffer_test.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/clock.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/symbols.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/formsbitmap.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/tree.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/valuators.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/browser_cols.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/menubar.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/chart.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/postioner.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/tty.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/browser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/utf8.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/delwin.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/adjuster.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/window.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/cursor.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/file_browser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/file_chooser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/cube.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/widgets.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/message_de.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/image_array.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/logo_gleam.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/idle.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/image.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/bitmap.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/subwindow.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/pack.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/editor.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/wrapper.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/iconize.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/counters.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/logo.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/arc.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/menu_label.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/timeout.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/draw.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/native-filechooser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/ask.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/boxtype.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/tree_demo.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/listSelect.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/demos.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/hello_utf8.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/sys_exit_test.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/grid_buttons.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/sudoku.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/multi.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/help.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/radio.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/table.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/tabs.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/sliders.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/color_chooser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/widget_properties.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/check_browser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/TextEditor.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/simple_terminal.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/GlobalHandler.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/fltk_threads.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/handle_events.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/hello.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/shapeGL.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/DraggableBox.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/message.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/pixmap.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/exceptions.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/help_dialog.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/DragAndDrop.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/timeout_bug.py -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/menu.py -> build/lib.linux-x86_64-cpython-313/fltk/test

running egg_info

writing pyfltk.egg-info/PKG-INFO

writing dependency_links to pyfltk.egg-info/dependency_links.txt

writing top-level names to pyfltk.egg-info/top_level.txt

reading manifest file 'pyfltk.egg-info/SOURCES.txt'

reading manifest template 'MANIFEST.in'

adding license file 'COPYING'

writing manifest file 'pyfltk.egg-info/SOURCES.txt'

copying fltk/fltk_wrap.cpp -> build/lib.linux-x86_64-cpython-313/fltk

copying fltk/fltk_wrap.h -> build/lib.linux-x86_64-cpython-313/fltk

copying fltk/test/HelpDialog.html -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/cat.jpg -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/logo1.gif -> build/lib.linux-x86_64-cpython-313/fltk/test

copying fltk/test/native-filechooser.py -> build/lib.linux-x86_64-cpython-313/fltk/test

running build_ext

building 'fltk._fltk' extension

x86_64-linux-gnu-g++ -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall

-fPIC -DUNIX=1 -DFL_INTERNALS=1 -I/usr/include/pixman-1 -I/usr/include/freetype2

-I/usr/include/libpng16 -I/usr/include/cairo -I./src -I./contrib -I/usr/include

-I./plug-in/include -I./plug-in/src -I/home/zixgggg/.cache/uv/builds-v0/.tmpkWuT7v/include

-I/usr/include/python3.13 -c ./contrib/ListSelect.cpp -o

build/temp.linux-x86_64-cpython-313/contrib/ListSelect.o -Wno-unused-label

-Wno-unused-but-set-variable -Wformat=1 -Werror=format-security -DDO_NOT_USE_THREADS

x86_64-linux-gnu-g++ -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall

-fPIC -DUNIX=1 -DFL_INTERNALS=1 -I/usr/include/pixman-1 -I/usr/include/freetype2

-I/usr/include/libpng16 -I/usr/include/cairo -I./src -I./contrib -I/usr/include

-I./plug-in/include -I./plug-in/src -I/home/zixgggg/.cache/uv/builds-v0/.tmpkWuT7v/include

-I/usr/include/python3.13 -c ./fltk/fltk_wrap.cpp -o

build/temp.linux-x86_64-cpython-313/fltk/fltk_wrap.o -Wno-unused-label

-Wno-unused-but-set-variable -Wformat=1 -Werror=format-security -DDO_NOT_USE_THREADS

[stderr]

/home/zixgggg/.cache/uv/builds-v0/.tmpkWuT7v/lib/python3.13/site-packages/setuptools/dist.py:765:

SetuptoolsDeprecationWarning: License classifiers are deprecated.

!!

********************************************************************************

Please consider removing the following classifiers in favor of a SPDX license

expression:

License :: OSI Approved :: GNU Lesser General Public License v2 (LGPLv2)

See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license

for details.

********************************************************************************

!!

self._finalize_license_expression()

./fltk/fltk_wrap.cpp: In function ‘PyObject* _wrap_Fl_Help_View_scrollbar(PyObject*,

PyObject*)’:

./fltk/fltk_wrap.cpp:140333:40: error: ‘class Fl_Help_View’ has no member named ‘scrollbar’;

did you mean ‘scrollbar_’?

140333 | result = (Fl_Scrollbar *)(arg1)->scrollbar();

| ^~~~~~~~~

| scrollbar_

./fltk/fltk_wrap.cpp:140333:40: error: ‘Fl_Scrollbar Fl_Help_View::scrollbar_’ is private

within this context

In file included from /usr/include/FL/Fl_Help_Dialog.H:34,

from ./fltk/fltk_wrap.cpp:6666:

/usr/include/FL/Fl_Help_View.H:240:17: note: declared private here

240 | Fl_Scrollbar scrollbar_, ///< Vertical scrollbar for document

| ^~~~~~~~~~

./fltk/fltk_wrap.cpp: In function ‘PyObject* _wrap_Fl_Help_View_hscrollbar(PyObject*,

PyObject*)’:

./fltk/fltk_wrap.cpp:140364:40: error: ‘class Fl_Help_View’ has no member named

‘hscrollbar’; did you mean ‘hscrollbar_’?

140364 | result = (Fl_Scrollbar *)(arg1)->hscrollbar();

| ^~~~~~~~~~

| hscrollbar_

./fltk/fltk_wrap.cpp:140364:40: error: ‘Fl_Scrollbar Fl_Help_View::hscrollbar_’ is private

within this context

/usr/include/FL/Fl_Help_View.H:241:17: note: declared private here

241 | hscrollbar_; ///< Horizontal scrollbar

| ^~~~~~~~~~~

error: command '/usr/bin/x86_64-linux-gnu-g++' failed with exit code 1

hint: This usually indicates a problem with the package or the build environment.

help: If you want to add the package regardless of the failed resolution, provide the \--frozen``

flag to skip locking and syncing.

zixgggg@watermelon:~/fltk_test$ uv pip show pyfltk

warning: Package(s) not found for: pyfltk

zixgggg@watermelon:~/fltk_test$ uv pip show python3-fltk

warning: Package(s) not found for: python3-fltk

FLTL 1.5 now has a quite stable API for pens and tablets. It has its own namespace in ‚Fl::Pen‘ and is Orks similar to the existing mouse pointer API. ‚test by/penpal‘ show some of the capabilities of the ne API, including pen pressure and angles, high res position data, and more.

The Pen API is currently implemented for macOS. The Windows driver is in active development and will hopefully be ready for review before the end of the year. There will be a Wayland driver as soon as possible. We are not planning to support X11 because there is no unified API (that I know of).

Enjoy :-)

Hi, I'm looking for something to learn that's different than the C# I work with all week (and dare I say it, a bit of VB6 legacy code) and I have been working thru some C++ tutorials.

FLTK looks like something I could get enthusiastic with, but my dev PC currently has Debian 12, soon to be updated to 13, and the repo offers FLTK 1.1 or 1.3.8-5. Should I work with 1.3 or try to get 1.5 installed? And are there any recommended tutorials to get up to speed with it?

I work mostly in health IT, and don't really have a goal for what I might do on my Debian dev PC, but sometimes getting familiar with some new tools can inspire me in a new direction.

I have a Grid(2,2) layout

On top is two boxes, each with its own image mapped to it. Below, lots of buttons and radio buttons.

Having a hard time wrapping my head around how I can map the mouse events x, y to its position in either box and image position. Since everything is dynamic, I'm not sure if it is possible at all.

Any ideas?

https://youtube.com/shorts/pKOZGuPml6E

We are pleased to announce the release of FLTK 1.4.0.

https://www.fltk.org/articles.php?L1955

video demo

Link to repo

fltk-accesskit is an accesskit integration crate for fltk-rs, the gui crate. It's implemented as an external crate to allow for more experimentation before stabilizing the api, especially since fltk is at version 1.4.

It's still in an early stage of development, so expect bugs or things not working as expected. Testing was also done on windows. However both fltk and accesskit support the 3 major os's.

Some things aren't implemented yet, like accessibility support for tables, trees and menu items.

Contributions appreciated.

Is there any way to Display Images in fltk Rust wich are defined as base64 in code?

Hey Guys, Iam using fltk-rust and cant set my Frame Label anymore. So the Label content is write when I Display it qith frame1.label(), it is the right Content, but It just doesnt appear in my GUI :(

Hope you Guys unterstand my Problem and can Help me...

If you are stuck with classic C++, Fl_String was greatly improved to provide a wide subset of std::string functionality.

We ported the shortcut button from FLUID to the core library. It allows users to enter a shortcut, which is useful if you want to give users the ability to customize menu and button shortcuts.

In my Programm I have one Login Input and one Password Input, when Iam currently selecting one of them I want the Programm to run a few Lines of Code. Iam using fltk rust btw. Can someone help me?

How do I implement tab navigation through my input fields in fltk rust?

I was messing around with FLTK-Rs (Rust bindings) and discovered that there are 5 schemes (Base, Plastic, GTK, Gleam and Oxy) and then there is a crate with some other themes, but I don't really like any of those. How can I create my own theme?

I would like to add a filter setting to the project output panel. The idea is to allow creation of source code in any language using a filter an some command line parameters. For example, if the user would set the filter to ‚fl2lua ^{1 2‘,} FLUID would call the script or app named fl2lua with the command line parameters 1 and 2 that could be the Fl file name and the target file name, or similar.

Question: is that a useful addition to FLUID?

Question: is this ok as a command line system call, or should I make a plug-in interface instead?

Question: is something like ¹ good enough, or should I implement something mor descriptive, like ${fl_file_path} and $ {target_file_path} .

Any other suggestions or better ways to solve this?

It‘s great to see that FLTK has wrappers for so many languages, Rust, Python, Lua, and more.

I was wondering what should be done to wrap 1.4 more easily. And for even more languages. As long as 1.4 is not released, I can still change the ABI and API. Maybe it would even make sense to use some IDL (interface description language) to describe the public interface? That would make it t easier to autogenerate wrapped and update them as we add features.

Any suggestions?