Where to find reference for PyGObject [closed] - documentation

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm working on a Python based source code editor. I've created a clean layout with a Gtk.Notebook. Creating a main layout was easy with Glade, but right after I imported gi.repository, everything got hard. It's very hard to find documentation. From pydoc I can 't get anything, only method signatures, which are usually *args, **kwargs. I often need to check what a method returns or takes in, and I haven't really started signals and other stuff yet.
Is there a complete/almost-complete documentation, especially for GtkSource? GtkSource is especially undocumented.

You should probably read my answer to a similar SO question: PyGObject GTK+ 3 Documentation. In short, you should refer to the GtkSourceView API Reference for C. Don't worry, it's not hard. When you see "GtkSourceView" in the C docs you know it's "GtkSource.View" in Python. When you see "gtk_source_view_new" in C docs you know it's the constructor in Python "GtkSouce.View()". You can set any GTK+ property in the constructor and there is usually get_foo/set_foo style methods for each property.
Therefore, you can do things like:
view = GtkSouce.View(indent_width=4, show_line_numbers=True)
view.get_buffer().set_text("Hello World!")
Remember, GTK+ widgets are objects so you need to pay attention to the hierarchy to find all the methods and properties for a widget.

Related

Is there some where a list of the built-in functions for Swift? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
As I am new in Swift, quite often when I want to do a basic thing, I "recreate" functions which have actually already been created (built-in functions: sort, equals, find, contains, etc.) so I was wondering if you had a link with all those functions details and explications (with examples as well would be awesome!)
I found this but it's quite old (june 2014) and not everything is documented.
You can see everything that Swift provides “out of the box” by typing the name of a Swift built-in (like String), then command-clicking it. Example:
This takes you to a generated file declaring all of Swift's built-in types and functions. (The file does not exist in the Xcode bundle. It is generated on demand in memory from the file Swift.swiftdoc, which exists in several places in the Xcode.app bundle.)

clojure.lang, etc. api [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Are the JavaDocs for clojure.lang, etc. available online? Do I need to build it myself from the Clojure source?
Thanks.
if you want descriptions for functions and even examples, visit ClojureDocs
you can even contribute ;)
Javadocs don't exist, per se. If you look at the Java source code, it's very sparsely documented. Certainly you could generate a skeleton yourself, but it probably wouldn't be all that useful anyway as much of the language is self-implemented (in clojure), using Java mostly for bootstrapping the core functionality. I don't think clojure.lang package is really intended to be used directly.
To learn about Clojure functions you can:
Use (doc) and (find-doc) from a repl
Use the API reference at clojure.org
See ClojureDocs, per #Belun's answer

Where can I QuickForm2 documentation [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I spent the past few hours searching for a tutorial/documentation for QuickForm2 but seems like there is no such thing other than the examples attached with the package itself which are not sufficient at all. I tried looking through the API documentation but I can't find a method called addElement for example which is the most used method there. I just need any good tutorial about the second version of the package or would you please tell me where can i find the methods (addElement, addRule, element specific methods like setValue, setOptions, setContent ... etc).
There is a bunch of examples here (on Ubuntu):
/usr/share/doc/php5-common/PEAR/HTML_QuickForm2/examples/
If you are on another distro you can do:
locate QuickForm2
I'm not too familiar with QuickForm, but a google search found this page:
http://pear.php.net/reference/HTML_QuickForm2-latest/li_HTML_QuickForm2.html
I think you're possibly struggling because the methods you're looking for are in the base classes.
For example:
Element mentions that it Includes Node.php.
Node has an addRule method (and a setValue one).
addElement looks like its in the Container class
The documentation for HTML_QuickForm2 is in the PEAR manual: http://pear.php.net/manual/en/package.html.html-quickform2.php
addElement is in HTML/QuickForm2/Container.php.

Detailed Valgrind internals documentation [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm thinking of making a D interface to Valgrind's client request API. By mucking around in the header files and de-compiling stuff, I could eventually figure out what it's doing but I'm wondering if their is a authoritative document on how things work? (BTW I already found this document but it doesn't have enough info)
What I'm looking for would answer questions like: How do I generate the macros to wrap/call a function that returns a 32bit machine word and takes a 64bit float?
In the valgrand manual, it describes the existing client request prototypes at the bottom of http://valgrind.org/docs/manual/manual-core-adv.html but none of these support passing 64bit floats. You could split it into two longs and pass it that way. It does look pretty hairy.
The authoritative document on how it works is the source code. If the tech docs are incomplete, then use the source.
I would also suggest looking at the sources of libraries that use the client request mechanism.

Where is the documentation for wxAUIToolbar? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I looked in http://docs.wxwidgets.org/trunk/ but could't find the documentation for it.
Does anyone know where it is and/or why it's not there?
I can explain why it's not there in a sense - there's no Doxygen annotations in the header file where the class is declared. As for why not, I'm guessing that the AUI authors isn't a big fan of Doxygen - I believe AUI was developed as a third party addition to wxWidgets, and has only relatively recently been merged in, so a few differences in things like this are to be expected.
The class is declared in include/wx/aui/auibar.h, it inherits wxControl, and from a quick look through the public methods it's probably not that hard to figure out.
There are some wxAuiToolbar examples in the aui sample program (samples/aui/auidemo.cpp). This should give a few more clues.
Until someone contributes some documentation updates, I'm afraid a bit of detective work is probably needed.