Every game needs a user interface that matches its look and feel. The purpose
of glooey is to help you make such an interface. Towards this end, glooey
provides 7 powerful placement widgets, a label widget, an image widget,
3 different button widgets, a text entry widget, a variety of scroll boxes
and bars, 4 different dialog box widgets, and a variety of other miscellaneous
widgets. The appearance of any widget can be trivially customized, and
glooey comes with built-in fantasy, puzzle, and 8-bit themes to prove it
(and to help you hit the ground running if your game fits one of those genres).
The philosophy behind glooey is that deriving subclasses from a basic set of
widgets with no default style is the most elegant way to control how
widgets look. This approach is flexible because subclasses can customize or
override most aspects of the basic widgets. But it's also surprisingly
succinct and powerful: specifying a style is usually as simple as setting
a class variable, and styles can be easily composed using either inner
classes or previously defined widgets. This philosophy makes glooey easy
to get started with, and powerful enough to support even the most
complicated games.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-glooey listed in the above command, you can pick from the names under the Packages section.
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
graphics/py-pyglet: update to 2.0.0
- Preserve pyglet 1.x as graphics/py-pyglet1
- Add mutual conflicts between graphics/py-pyglet1 and graphics/py-pyglet
- Switch all consumers to graphics/py-pyglet1 as it's likely
that no consumer is compatible with pyglet 2.x yet
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Every game needs a user interface that matches its look and feel. The purpose
of glooey is to help you make such an interface. Towards this end, glooey
provides 7 powerful placement widgets, a label widget, an image widget,
3 different button widgets, a text entry widget, a variety of scroll boxes
and bars, 4 different dialog box widgets, and a variety of other miscellaneous
widgets. The appearance of any widget can be trivially customized, and
glooey comes with built-in fantasy, puzzle, and 8-bit themes to prove it
(and to help you hit the ground running if your game fits one of those genres).
The philosophy behind glooey is that deriving subclasses from a basic set of
widgets with no default style is the most elegant way to control how
widgets look. This approach is flexible because subclasses can customize or
override most aspects of the basic widgets. But it's also surprisingly
succinct and powerful: specifying a style is usually as simple as setting
a class variable, and styles can be easily composed using either inner
classes or previously defined widgets. This philosophy makes glooey easy
to get started with, and powerful enough to support even the most
complicated games.
WWW: https://pypi.org/project/glooey
