Anonymous user
Talk:Window creation/X11: Difference between revisions
→Classification: Tagged first part of page with section title; commented on OSX low-level details
(Describe rationale for task specialization) |
(→Classification: Tagged first part of page with section title; commented on OSX low-level details) |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 1:
==Classification==
These examples should be included under [[User Output - graphical]]. --[[User:Short Circuit|Short Circuit]] 01:59, 18 November 2008 (UTC)
:They should also (obviously) be changed to display "Goodbye, World!"--[[User:Mwn3d|Mwn3d]] 02:27, 18 November 2008 (UTC)
Line 13 ⟶ 14:
:::::: To just give a "short", non-comprehensive list of GUI toolkits usable from C++: raw Windows API, Xlib, Carbon, MFC, Xt, Motif, Gtk+, Qt, wxWidgets, Ultimate++, ...
:::::: Of course, one could restrict to the basic GUI facility of the corresponding platform, i.e. raw Windows API for Windows, Xlib for Linux/Unix (AFAIK X is the only relevant windowing system on Unix-type systems) etc. But then, most non-trivial programs are not written using those low-level APIs (well, for X, in principle one could even go one level lower and explicitly use the X protocol to communicate with the server, but that's even more unlikely to be used in any serious program). --[[User:Ce|Ce]] 13:46, 19 November 2008 (UTC)
::::::: The other relevant low-level API for Unix is the native one for OSX. Mind you, that's one that Apple strongly discourages developers from using. Instead, they go with using Cocoa which is much higher level. –[[User:Dkf|Donal Fellows]] 10:52, 10 March 2010 (UTC)
Just seen that there is [https://jna.dev.java.net/javadoc/com/sun/jna/examples/unix/package-tree.html X for Java] too. [[User:Blue Prawn|Blue Prawn]] 20:23, 29 November 2008 (UTC)
Line 32 ⟶ 33:
::::: To be exact, '''is it the intention of this task to prohibit the use of toolkits?''' If so, it ''must'' be stated clearly in the task definition. —[[User:Dkf|Donal Fellows]] 15:27, 17 August 2009 (UTC)
:::::: Given how people have been solving this task, I've specialized it to say that toolkits shouldn't be used. This invalidates none of the existing solutions. (I've written one in Tcl which lets me show off a bunch of cool things, given that we don't have a standard lib for this low a level of access.) I still think that a toolkit is the ''right'' way to do this thing in production code, but this task is about doing it the hard way. —[[User:Dkf|Donal Fellows]] 23:23, 21 August 2009 (UTC)
== Back on the subject of task specificity ==
I don't care to argue against the task existing as it is, but as specific as its intent is (and looking back on past discussion) I'd like to see one of two things: Either rename the task to [[Window creation/X11 (native)]], and specify clearly that the task is intended to describe working with X11 system objects directly, or fold it back into a more generic task. This task is specific in intent, but not sufficiently clear on what that intent is; if a task creator has to disproportionately step in to moderate examples, then the task isn't clear enough. --[[User:Short Circuit|Michael Mol]] 04:41, 10 March 2010 (UTC)
| |||