Development/Languages/Smoke - Revision history

Phanect: Removed old language bar

2012-03-12T16:52:13Z

Removed old language bar

Burel: /* CMakeLists.txt */ Updated to work with the modularized smoke libraries.

2011-12-23T18:07:29Z

‎CMakeLists.txt: Updated to work with the modularized smoke libraries.

Burel: /* hello.cpp */ Updated to work with modularized smoke libraries.

2011-12-23T18:04:23Z

‎hello.cpp: Updated to work with modularized smoke libraries.

Show changes

Arnorehn at 15:00, 24 August 2011

2011-08-24T15:00:48Z

Neverendingo: /* Setting up the SMOKE generator */

2011-06-29T18:43:52Z

‎Setting up the SMOKE generator

Neverendingo: /* Setting up the parser */

2011-06-29T18:43:23Z

‎Setting up the parser

Neverendingo: /* hello.cpp */

2011-06-29T18:42:08Z

‎hello.cpp

Neverendingo: Text replace - "" to ""

2011-06-29T18:41:35Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T18:37:48Z
Text replace - "<code xml>" to "<syntaxhighlight lang="xml">"

				
				
				
				
			
			← Older revision
			Revision as of 18:37, 29 June 2011
			
Line 271:
Line 271:
  A very simple smokeconfig.xml would look like this:   A very simple smokeconfig.xml would look like this:
    
− <code xml> + <syntaxhighlight lang="xml">
  <config>   <config>
       <moduleName>myapp</moduleName>        <moduleName>myapp</moduleName>



Burel: Add link to API Documentation page
2010-04-09T05:34:55Z
Add link to API Documentation page

				
				
				
				
			
			← Older revision
			Revision as of 05:34, 9 April 2010
			
Line 41:
Line 41:
  [[Development/Architecture/KDE4/Solid|Solid]],   [[Development/Architecture/KDE4/Solid|Solid]],
  [[Soprano]]   [[Soprano]]
  + 
  + = API Documentation =
  + Info on the Smoke API is available on our [[Development/Languages/Smoke/API_Documentation|API Documentation]] page.
    
  = Usage example =   = Usage example =

← Older revision		Revision as of 16:52, 12 March 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Languages/Smoke}}~~
	= Overview =		= Overview =
	'''SMOKE''' is a introspective wrapper around the Qt and KDE frameworks.		'''SMOKE''' is a introspective wrapper around the Qt and KDE frameworks.

@@ Line 219: / Line 219: @@
 set(hello_src hello.cpp)
 add_executable(hello ${hello_src})
-target_link_libraries(hello smokeqt)
+target_link_libraries(hello smokebase smokeqtcore smokeqtgui)
 </pre>
 This assumes that you've installed KDE4 and kdebindings. If you only have SmokeQt installed, you need to adjust the paths accordingly.

@@ Line 4: / Line 4: @@
 Legend has it that SMOKE stands for '''S'''cripting '''M'''eta '''O'''bject '''K'''ompiler '''E'''ngine
-Not only does it provide wrappers for every function in every class,
+Information about all classes and all methods/functions is stored in
-but it also contains meta-information allowing queries of what
+cross-referencing tables for fast look-ups. Thereby the whole API of a wrapped library can be used.
-functions are available and their arguments and return-types.
-All classes, all methods, with all arguments, along with various flags
+The main purpose of SMOKE is making it easier to write bindings from
-reflecting staticness, virtuality, etc. are stored into
-cross-referencing arrays for fast lookups. One can thus read (and call) the whole
-Qt API by simply reading/searching these arrays.
-−
-The main purpose of SMOKE is to make it possible to write bindings from
 scripting languages to Qt and KDE - with an emphasis on ease of use and flexibility.
-You can find out more about SMOKE by checking out the
+You can find out more about SMOKE by checking out the git repositories of the
-[http://websvn.kde.org/trunk/KDE/kdebindings/ kdebindings module] of KDE's SVN.
+[https://projects.kde.org/projects/kde/kdebindings kdebindings module].
 At the time of writing, the [[Development/Languages/Perl|Perl bindings]], [[Development/Languages/Ruby|Ruby bindings]], [[Development/Languages/Qyoto|C# bindings]] and [[Development/Languages/PHP-Qt|PHP bindings]] are known to use it, you might find valuable usage information there.

@@ Line 325: / Line 325: @@
 Again, our revised command line looks like this by now:
-<code>smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp \
+<syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp \
 -smokeconfig smokeconfig.xml -- myapp_includes.h</syntaxhighlight>
 And this is it. If you run the command (of course it has to be adjusted to use your own headers and classnames), you should end up with a smokedata.cpp and a bunch of x_*.cpp files which you can compile into one libsmokemyapp.so library.

@@ Line 234: / Line 234: @@
 For convenience, the options and switches that smokegen requries are stored in an xml-file. Such config files for Qt-based APIs and KDE-based APIs are already installed with the smokeqt and smokekde libs (in <prefix>/share/smokegen). Give them to smokegen with the -config option, as in
-<code>smokegen -config /usr/share/smokegen/kde-config.xml</syntaxhighlight>
+<syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml</syntaxhighlight>
 You can extend options, like include dirs, by giving additional parameters on the command line. For example, you can give additional include dirs with the -I flag:
-<code>smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp</syntaxhighlight>
+<syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp</syntaxhighlight>
 smokegen --help will show a complete list of possible options. You'll typically only need -I, -dm, -o and sometimes -g (the default generator in the config.xml files is 'smoke', but sometimes you might want to override it with 'dump' to get a list of classes).
@@ Line 244: / Line 244: @@
 smokegen then expects a list of headers after a double dash. Typically we write an 'include-all' header, like Qt does, to simplify matters. It's also the most secure way to conditionally include headers (on different platforms for example) and later get the smoke compilation right. Such an include file could look like this:
-<code cppqt>
+<syntaxhighlight lang="cpp-qt">
 // the parser doesn't understand the __attribute__ stuff of GCC - disable it for the smokegen run.
 #define MYAPP_EXPORT
@@ Line 263: / Line 263: @@
 So our command line now looks like this:
-<code>smokegen -config /usr/share/smokegen/kde-config.xml \
+<syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml \
 -I /usr/include/MyFancyApp -- myapp_includes.h</syntaxhighlight>

@@ Line 47: / Line 47: @@
 = Usage example =
 == hello.cpp ==
-<code cppqt>
+<syntaxhighlight lang="cpp-qt">
 #include <smoke.h>
 #include <smoke/qt_smoke.h>