uwg
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3
Micro Window-Gadgets 0.2.0
Micro Window-Gadgets is a lightweight gadget/windowing toolkit for C and X11. more>>
UWG is a lightweight gadget/windowing toolkit for C and X11. Interfaces are described using XML and are turned into C code using the ubuildinit utility. Currently, only a small percentage of the planned gadgets are implemented.
Micro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.
Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.
However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department. Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular.
Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control. And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).
Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.
<<lessMicro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.
Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.
However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department. Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular.
Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control. And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).
Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.
Download (0.30MB)
Added: 2006-12-04 License: GPL (GNU General Public License) Price:
1055 downloads
Micro Window-Gadgets Builder 0.1.3
Micro Window-Gadgets Builder is a rapid application development environment (or IDE) for UWG (micro window-gadgets). more>>
Micro Window-Gadgets Builder or in short UWGBuilder is a rapid application development environment (or IDE) for UWG (micro window-gadgets). Essentially it is a graphical editor for UWG user-interfaces, with project-control and other handy bits.
In terms of the interface, Borlands Delphi is probably the closest commercial product. UWGBuilder primarily reads and writes XHPD files, XML markup describing the interface (with code and other things embedded in it); these are converted into C code proper using the ubuildinit tool (and would be triggered from within a generated makefile).
Although not much of the project code is implemented yet, the intention is to use autoconf, automake and friends to handle building projects. As well as building stand-alone UWG/X11 applications, UWGBuilder can be used to edit interfaces for RAPP (remote applications).
UWGBuilder currently has most of the visual gadget database (of UWG gadgets), that generally works in terms of building interfaces. Property and code editing is mostly there too. Various bits of project load/save/etc. also working, but no compilation support yet.
Most of UWGBuilder is based on the earlier WGBuilder (for the previous C++ window-gadgets), though it is a fairly fresh implementation.
<<lessIn terms of the interface, Borlands Delphi is probably the closest commercial product. UWGBuilder primarily reads and writes XHPD files, XML markup describing the interface (with code and other things embedded in it); these are converted into C code proper using the ubuildinit tool (and would be triggered from within a generated makefile).
Although not much of the project code is implemented yet, the intention is to use autoconf, automake and friends to handle building projects. As well as building stand-alone UWG/X11 applications, UWGBuilder can be used to edit interfaces for RAPP (remote applications).
UWGBuilder currently has most of the visual gadget database (of UWG gadgets), that generally works in terms of building interfaces. Property and code editing is mostly there too. Various bits of project load/save/etc. also working, but no compilation support yet.
Most of UWGBuilder is based on the earlier WGBuilder (for the previous C++ window-gadgets), though it is a fairly fresh implementation.
Added: 2006-08-28 License: GPL (GNU General Public License) Price:
1156 downloads
ubuildinit 0.2.0
ubuildinit is a utility for use with micro window-gadgets. more>>
ubuildinit is a utility for use with micro window-gadgets (UWG) that generates C source and header files from XML descriptions of visual interfaces.
Interfaces are described using XHPD, an XML-based hierarchical program description.
Micro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.
Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.
However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department.
Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular. Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control.
And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).
Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.
<<lessInterfaces are described using XHPD, an XML-based hierarchical program description.
Micro WG is a C `version of WG. In general, UWG is somewhat more light-weight than WG. Firstly because its written in C and not C++. Secondly because it does not yet provide all the features of WG. Also, it should be significantly easier to `connect UWG to KRoC.
Why UWG ? Its now the case that there are many `widget libraries for programmers to choose from. The traditional X11 widget libraries (X Toolkit Intrinsics), GTK, QT, Motif, wxWindows, TK, etc.. GTK and QT are probably the most common for an average users desktop system -- as the graphics libraries of Gnome and KDE respectively. C++, used by WG, provides a largely type-safe environment for gadget programming -- i.e. the structure/nature of gadgets fit neatly into the C++ type (class) heirarchy.
However, C++ ultimately suffers from the same problems as some other `object-orientated languages -- namely leaky encapsulation. When writing WG, some of the limitations (maybe features) of C++ caused significant problems, particularly in the function-pointer department.
Object-orientation is a fine model for data, but it does not work well when `bolted-on to sequential languages -- C++ and Java in particular. Forcing a sequential flow-of-control through something that we tried to break into objects only leads to problems. E.g. when executing inside the method of one object, is it safe to delete another object ? -- well, only if that other object wasnt involved (and still is involved) in the flow-of-control.
And this you cannot easily tell. Furthermore, in many cases, `delete may be substituted for any object interaction (method-call).
Also, a lot of modern GUI toolkits seem unnecessarily bloated. C++ (and other `frilly languages) can be blamed for some of this, but not all of it. WG isnt bloated yet, but its not far off. UWG is therefore an attempt at a lightweight (size and speed) gadget toolkit for X11, programmed in C.
Download (0.14MB)
Added: 2006-12-04 License: GPL (GNU General Public License) Price:
1054 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above uwg search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed