summaryrefslogtreecommitdiff
path: root/.gitignore
Commit message (Collapse)AuthorAge
* build: Remove WebhelperPhilip Chimento2017-04-12
| | | | | | | Webhelper is now in its own repository: https://github.com/endlessm/webhelper https://phabricator.endlessm.com/T16203
* Remove parallel version of WebHelper compatible with WebKit2-3.0Mario Sanchez Prada2016-04-21
| | | | | | | | | | | | | | | We are no longer shipping the Webkit2-3.0 API on Endless and Virtual School has already been migrated to the newer WebKit2-4.0 API after having fixed all the regressions there and so it makes no sense to keep this any longer. Besides, after the WebKitGTK+ upgrade from 2.4.9 to 2.4.11 debian does no longer ship the WebKit2GTK+-3.0 packages (and there's no point on us bringing them back) so, actually, we can not keep this anyway, so let's remove it. This commit basically reverts 8c837e660853abd03c97a98815f73146eb57c010, but considering all the changes integrated ever since (not a "clean" revert). https://phabricator.endlessm.com/T11388
* Generate version macros from configurePhilip Chimento2015-08-31
| | | | | | | | | | | | This adds EOS_SDK_MAJOR_VERSION, EOS_SDK_MINOR_VERSION and EOS_SDK_MICRO_VERSION as macros in eosversion.h whose values are generated from configure with AC_SUBST, rather than in config.h using AC_DEFINE. They are also public API, so they get documenation and Since: annotations. [endlessm/eos-sdk#3071]
* gitignore coverage fileMatt Watson2015-08-19
| | | | [endlessm/eos-sdk#3438]
* Create a parallel version of WebHelper2 for WebKit2-3.0Philip Chimento2015-08-07
| | | | | | | | We cannot switch eos-virtual-school to WebKit2-4.0 because of regressions, but we already committed to using WebHelper2 to localize it. This adds a version of WebHelper2 that is compatible with WebKit2-3.0. [endlessm/eos-sdk#3430]
* Implement web actions in WebHelper2Philip Chimento2015-05-21
| | | | | | | | | | | This allows communicating with the host program through URIs of the form webhelper://action?param=value&param2=value2. Actions can be defined on the WebHelper object and given a callback in Javascript. Unfortunately we have to use a private C library to register the URI scheme, because of https://bugs.webkit.org/show_bug.cgi?id=116672 [endlessm/eos-sdk#291]
* WebHelper2 for translating WebKit2 viewsPhilip Chimento2015-05-21
| | | | | | | | | | | This adds a new Javascript module, WebHelper2. It's the WebKit2 analogue to WebHelper. It offers a facility for calling gettext() on the contents of DOM elements in your web page. It accomplishes this using an extension module that's loaded into WebKit's web process. [endlessm/eos-sdk#291]
* Remove section from .gitignorePhilip Chimento2015-05-20
| | | | | | | | This section contained several names that weren't necessary to ignore. Specifically "lib" would ignore any "lib" directory, which was dangerous. The whole section seemed unnecessary. [endlessm/eos-sdk#291]
* Integrate Jasmine with AutomakePhilip Chimento2015-04-17
| | | | | | | This runs the tests during "make check" using jasmine-gjs, and outputs results in the TAP format that Automake understands. [endlessm/eos-sdk#3054]
* Remove ancient test runnerPhilip Chimento2015-04-17
| | | | | | | This test runner dates from even before eos-jasmine, and is not used anywhere. [endlessm/eos-sdk#3054]
* Initial implementation of image creditsPhilip Chimento2015-03-25
| | | | | | | | | | | | | | | | | | | | | This is a rough implementation of an "About"-like dialog for image attribution in SDK applications. You can press the 'secret' hotkey Shift+Ctrl+A to get a dialog with thumbnails and attribution information for the images in the app's GResource. Clicking on the thumbnail opens the image's original URI in the browser, if known. Clicking on the text opens the image's license text in the browser, if known. For this, you need to add a JSON file to the app's GResource and pass its GResource path to the EosApplication:image-attribution-file property. The format of this JSON file is described in the documentation for EosApplication. The dialog uses GtkTreeView because we didn't have GtkListBox when I started implementing it over a year ago. This places some limitations on the UI; the links behave weirdly and the mouse pointer doesn't change to a hand when hovering over the links. [endlessm/eos-sdk#2934]
* Enable Gjs and C coverage reports.Sam Spilsbury2015-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We now provide a new m4 module eos-coverage.m4, which is installed into the system aclocal directory. This macro provides three new commands for SDK consumers to use: EOS_COVERAGE_REPORT([languages]) - Enables a "coverage report". The first argument is a space separated list of unquoted languages to collect coverage information for. Valid values at the moment are "c" and "js". For each language specified, the macro will check for support for collecting coverage and enable reporting accordingly. Raw coverage output goes in $(abs_top_builddir)/_coverage/output/$language accordingly. The macro then checks to see if a coverage reporter, either genhtml, or cobertura, is available and enables them. A reporter must be installed and available for coverage reports to be generated. The coverage-genhtml is enabled if lcov is installed and available. This is generally used by developers themselves as it creates a self-contained report. The coverage-covertura is enabled if a program called lcov-result-merger is installed and a python module called lcov_cobertura are installed. lcov-result-merger can be installed from Node Package Manager. lcov_cobertura can be installed from PyPI. lcov-result-merger is necessary because each test suite is run in a separate subprocess and so there will be multiple entries per source file in the coverage.lcov file generated by gjs. lcov_cobertura doesn't handle that properly and so the results need to be merged together properly. JavaScript Coverage Details =========================== A variable called EOS_JS_COVERAGE_FILES should be defined containing a list of all javascript files to be considered a "part of" the coverage report, before EOS_COVERAGE_RULES are substituted. For example: EOS_JS_COVERAGE_FILES = $(SRCS) @EOS_COVERAGE_RULES@ AM_JS_LOG_FLAGS += @EOS_COVERAGE_JS_LOG_FLAGS@ C/C++ Coverage Details ====================== Certain additions also need to be made for Makefiles where coverage reporting is enabled on a C project: @EOS_COVERAGE_RULES@ AM_CFLAGS += @EOS_C_COVERAGE_CFLAGS@ AM_LDFLAGS += @EOS_C_COVERAGE_LDFLAGS@ If a target's CFLAGS is overridden and AM_CFLAGS is not used, then @EOS_C_COVERAGE_CFLAGS@ must be added to its CFLAGS. Blacklisting patterns ===================== If a path should not appear in the coverage report, then it can be blacklisted by adding a glob expression to EOS_COVERAGE_BLACKLIST_PATTERNS. Clean rules =========== A clean-coverage target is added to the dependencies for the clean-local target automatically by EOS_COVERAGE_RULES. [endlessm/eos-shell#2264]
* Remove Endless Wikipedia library from SDKRory MacQueen2014-05-27
| | | | [endlessm/eos-sdk#693]
* Update .gitignore to deal with Automake 1.13Philip Chimento2014-01-17
| | | | | | | For convenience for those of us who are running later Ubuntu versions [endlessm/eos-sdk#444] [endlessm/eos-sdk#444]
* Clean up the structure of the tests directorySam Spilsbury2014-01-15
| | | | | | | | Move all the tests for the SDK into tests/endless, move all the demos into tests/demos, move all the smoke tests into smoke-tests [endlessm/eos-sdk#444]
* Integrated JSON extraction utilityFernando2013-12-10
| | | | | | | | | | | | The utility used in eos-english and eos-programming-app was integrated and installed as part of the SDK CR comments addressed include: - Integrated new facilities available on GTK - Removed duplicate prototype declaration - Reformatted CLEANFILES var declaration - Used configure.ac to get @PACKAGE_VERSION@ - Added version() and usage() utilities [endlessm/eos-sdk#335]
* 'eos-application-manifest' tool with subcommandsPhilip Chimento2013-10-18
| | | | | | | | This is the framework for an 'eos-application-manifest' tool with subcommands as in git. Currently the 'help' and 'version' subcommands are implemented. [endlessm/eos-sdk#152]
* Forgot to rename eos.css.inPhilip Chimento2013-10-07
| | | | Pushing directly to dev, because it is holding up the build.
* Documentation for WebHelperPhilip Chimento2013-09-19
| | | | | | | | This adds the infrastructure for autogenerating HTML documentation from a Javascript module using NaturalDocs, and then adds documentation comments to webhelper.js. [endlessm/eos-sdk#302]
* Add editor temporary files to the ignore fileEmmanuele Bassi2013-09-19
|
* Add a test case for the FlexyGrid widgetEmmanuele Bassi2013-09-19
| | | | [endlessm/eos-sdk#1015]
* First attempt at an EOS test runnerPhilip Chimento2013-09-16
| | | | | | | | This adds a script eos-run-test which is adapted from gjs_run_tests, but does not try to discover the tests itself. Instead, in keeping with Automake's test suite facilities, it takes the filename of a test to run. [endlessm/eos-sdk#290]
* Need to distribute dummy file for make distcheckPhilip Chimento2013-09-09
| | | | | | | | | The dummy file necessary to get 'make check' to do the doc tests correctly was generated at build time, but that way it doesn't support the VPATH build that 'make distcheck' tests. The simplest way is to distribute the dummy file. [endlessm/eos-sdk#295]
* Use Automake's parallel test harnessPhilip Chimento2013-09-04
| | | | | | | | | | This gets rid of a long-standing workaround and makes it easier to start using a proper test harness for Javascript unit tests. Unfortunately, it requires a workaround to be able to run gtkdoc-check on the documentation, but the workaround is not too bad. [endlessm/eos-sdk#122]
* Integrate Wikipedia into SDK build systemPhilip Chimento2013-08-02
| | | | | | | | Now you should be able to import the app generator using const EndlessWikipedia = imports.wikipedia.EndlessWikipedia; [endlessm/eos-sdk#206] [endlessm/eos-sdk#206]
* Add CSS files in a GResourcePhilip Chimento2013-06-27
| | | | | | | | resource:///com/endlessm/sdk/ is now the official GResource path for SDK resources. Right now the GResource contains reset.css (from GTK) and endless-widgets.css (from eos-theme). [endlessm/eos-sdk#125]
* Added hack so configure works with automake 1.13 and 1.11Matt Watson2013-06-20
| | | | | | The problem was with needing the serial-tests option in 1.13 More details here http://gnu-automake.7480.n7.nabble.com/serial-tests-option-and-backwards-compatibility-td19571.html
* Build Javascript API documentationP. F. Chimento2013-05-06
| | | | | | | g-ir-doc-tool is buggy, and doesn't build very good documentation, but it is better than nothing. Building the JS documentation is turned off by default and turned on for 'make distcheck'. [endlessm/eos-sdk#18]
* Avoid warnings on Automake 1.12P. F. Chimento2013-04-22
| | | | | | | Use AM_PROG_AR, AM_PROG_CC_C_O, and -Wno-portability to avoid warnings on Automake 1.12 [#26]
* Enable GObject introspectionPhilip Chimento2013-04-17
| | | | | | | After running 'make install', run test/smoke-tests/introspection.js (and its Python counterpart) to test whether the GIR has been installed correctly. [#1]
* Autogenerate documentation with Gtk-docPhilip Chimento2013-04-17
| | | | | | | | Run './configure --enable-gtk-doc' to turn on building documentation, or use --disable-gtk-doc to disable it (for faster builds.) It builds as part of the regular 'make' invocation, though you can use 'make docs' to build only the documentation. [#1]
* Add test frameworkPhilip Chimento2013-04-17
| | | | | | | There are automated tests which run when you do 'make check', and also smoke tests which demonstrate one piece of functionality, which can be used as a sort of sanity check or demo. [#1]
* Internationalize the shared libraryP. F. Chimento2013-04-17
| | | | | | Add infrastructure for translating the single string in the shared library. [#1]
* Skeleton build system to build a shared libraryPhilip Chimento2013-04-17
| | | | | | Builds a dummy shared library that exports one symbol for testing, eos_hello_sample_function(). [#1]
* Initial commitKyle2012-12-13
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 12:48:57 +0000