ANNOUNCEMENT: New libraries available
Emmanuel Frecon
Just a few lines to let you know that I have just spent a few hours
packaging and making available some libraries. These are all covered
with a BSD license. Enjoy.
winapi : http://www.sics.se/~emmanuel/?Code:winapi
The winapi library is a Tcl library that offers access to the
low-level Win32 API. The philosophy of winapi is to give the
programmer total control over the calls being made, at the expense of
longer code. winapi attempts to mimick as closely as possible the
Windows API: it uses names and naming conventions that are similar,
offers Tcl commands that have the same order of arguments,
represents flags and masks using the same names as their Windows
constants counterparts and represent structures by lists of even
length containing the keys and values of the structures.
notifier : http://www.sics.se/~emmanuel/?Code:notifier
The notifier library implements a new Tcl/Tk widget that presents
itselfs as an (animated) notifier that pops up from one of the side of
the screen in a direction that can be chosen. The notifier is a new
toplevel and it is up to the caller to fill it in with content.
osd : http://www.sics.se/~emmanuel/?Code:osd
The osd library implements a new Tcl/Tk widget that presents itselfs as
an (animated) notifier that pops up from one of the side of the screen
in a direction that can be chosen. The osd features an image and an
informative message.
fullscreener : http://www.sics.se/~emmanuel/?Code:fullscreener
The fullscreener library forces an existing window from any Windows
application to remain on top of a fullscreen blank frame, which will
ensure the presence of one and only one window on the screen.
Emmanuel Frécon
Two more libraries are out now, sorry for the piecewise announcement.
gestures : http://www.sics.se/~emmanuel/?Code:gestures
The gestures library implements a low level Tcl service for gesture
recognition. Mouse and keyboard events are pushed into the service,
which will callback interested parties whenever a matching gesture has
been recognised. The library does not draw on the screen, this is left
to the caller.
floatingbbar : http://www.sics.se/~emmanuel/?Code:floatingbbar
The floatingbbar library implements a new Tcl/Tk widget that presents
itself as an (animated) floating button bar that pops up from one of the
side of the screen in a direction that can be chosen. The floatingbbar
features any number of buttons.
Erik Leunissen
> ...
> winapi : http://www.sics.se/~emmanuel/?Code:winapi
> The winapi library is a Tcl library that offers access to the
> low-level Win32 API. The philosophy of winapi is to give the
> programmer total control over the calls being made, at the expense of
> longer code. winapi attempts to mimick as closely as possible the
> Windows API: it uses names and naming conventions that are similar,
> offers Tcl commands that have the same order of arguments,
> represents flags and masks using the same names as their Windows
> constants counterparts and represent structures by lists of even
> length containing the keys and values of the structures.
Just curious: did you (more or less) determine how winapi compares to
the twapi extension?
( http://wiki.tcl.tk/9886 )
Erik Leunissen
--
leunissen@ nl | Merge the left part of these two lines into one,
e. hccnet. | respecting a character's position in a line.
Emmanuel Frécon
> Emmanuel Frecon wrote:
>> ...
>> winapi : http://www.sics.se/~emmanuel/?Code:winapi
>> The winapi library is a Tcl library that offers access to the
>> low-level Win32 API. The philosophy of winapi is to give the
>> programmer total control over the calls being made, at the expense of
>> longer code. winapi attempts to mimick as closely as possible the
>> Windows API: it uses names and naming conventions that are similar,
>> offers Tcl commands that have the same order of arguments,
>> represents flags and masks using the same names as their Windows
>> constants counterparts and represent structures by lists of even
>> length containing the keys and values of the structures.
>> ...
>
> Just curious: did you (more or less) determine how winapi compares to
> the twapi extension?
> ( http://wiki.tcl.tk/9886 )
There are some comments about this on the wiki. In general, TWAPI
provides a higher-level access to the win32 API, while I tried to keep
the programmer's experience as close as possible to the real thing in
winapi. The procedures have the same name as their functions
equivalents, etc. This lowers the threshold for people that already know
how to program Windows. TWAPI has far more functions than winapi, so
your best bet is TWAPI if you are out for a specific feature. On the
other hand, winapi has grown out of personal needs and I am releasing it
in order to see if there are people interested in extending it. I don't
want to compete with TWAPI, I think that the libraries are on two
different levels.