source file: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/botocore/docs/waiter.py
file stats: 65 lines, 10 executed: 15.4% covered
1. # Copyright 2015 Amazon.com, Inc. or its affiliates. All Rights Reserved. 2. # 3. # Licensed under the Apache License, Version 2.0 (the "License"). You 4. # may not use this file except in compliance with the License. A copy of 5. # the License is located at 6. # 7. # http://aws.amazon.com/apache2.0/ 8. # 9. # or in the "license" file accompanying this file. This file is 10. # distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF 11. # ANY KIND, either express or implied. See the License for the specific 12. # language governing permissions and limitations under the License. 13. from botocore import xform_name 14. from botocore.compat import OrderedDict 15. from botocore.docs.utils import DocumentedShape 16. from botocore.utils import get_service_module_name 17. from botocore.docs.method import document_model_driven_method 18. 19. 20. class WaiterDocumenter(object): 21. def __init__(self, client, service_waiter_model): 22. self._client = client 23. self._service_name = self._client.meta.service_model.service_name 24. self._service_waiter_model = service_waiter_model 25. 26. def document_waiters(self, section): 27. """Documents the various waiters for a service. 28. 29. :param section: The section to write to. 30. """ 31. section.style.h2('Waiters') 32. section.style.new_line() 33. section.writeln('The available waiters are:') 34. for waiter_name in self._service_waiter_model.waiter_names: 35. section.style.li( 36. ':py:class:`%s.Waiter.%s`' % ( 37. self._client.__class__.__name__, waiter_name)) 38. self._add_single_waiter(section, waiter_name) 39. 40. def _add_single_waiter(self, section, waiter_name): 41. section = section.add_new_section(waiter_name) 42. section.style.start_sphinx_py_class( 43. class_name='%s.Waiter.%s' % ( 44. self._client.__class__.__name__, waiter_name)) 45. 46. # Add example on how to instantiate waiter. 47. section.style.start_codeblock() 48. section.style.new_line() 49. section.write( 50. 'waiter = client.get_waiter(\'%s\')' % xform_name(waiter_name) 51. ) 52. section.style.end_codeblock() 53. 54. # Add information on the wait() method 55. section.style.new_line() 56. document_wait_method( 57. section=section, 58. waiter_name=waiter_name, 59. event_emitter=self._client.meta.events, 60. service_model=self._client.meta.service_model, 61. service_waiter_model=self._service_waiter_model 62. ) 63. 64. 65. def document_wait_method(section, waiter_name, event_emitter, 66. service_model, service_waiter_model, 67. include_signature=True): 68. """Documents a the wait method of a waiter 69. 70. :param section: The section to write to 71. 72. :param waiter_name: The name of the waiter 73. 74. :param event_emitter: The event emitter to use to emit events 75. 76. :param service_model: The service model 77. 78. :param service_waiter_model: The waiter model associated to the service 79. 80. :param include_signature: Whether or not to include the signature. 81. It is useful for generating docstrings. 82. """ 83. waiter_model = service_waiter_model.get_waiter(waiter_name) 84. operation_model = service_model.operation_model( 85. waiter_model.operation) 86. 87. waiter_config_members = OrderedDict() 88. 89. waiter_config_members['Delay'] = DocumentedShape( 90. name='Delay', type_name='integer', 91. documentation=( 92. '
The amount of time in seconds to wait between ' 93. 'attempts. Default: {0}
'.format(waiter_model.delay))) 94. 95. waiter_config_members['MaxAttempts'] = DocumentedShape( 96. name='MaxAttempts', type_name='integer', 97. documentation=( 98. '
The maximum number of attempts to be made. ' 99. 'Default: {0}
'.format(waiter_model.max_attempts))) 100. 101. botocore_waiter_params = [ 102. DocumentedShape( 103. name='WaiterConfig', type_name='structure', 104. documentation=( 105. '
A dictionary that provides parameters to control ' 106. 'waiting behavior.
'), 107. members=waiter_config_members) 108. ] 109. 110. wait_description = ( 111. 'Polls :py:meth:`{0}.Client.{1}` every {2} ' 112. 'seconds until a successful state is reached. An error is ' 113. 'returned after {3} failed checks.'.format( 114. get_service_module_name(service_model), 115. xform_name(waiter_model.operation), 116. waiter_model.delay, waiter_model.max_attempts) 117. ) 118. 119. document_model_driven_method( 120. section, 'wait', operation_model, 121. event_emitter=event_emitter, 122. method_description=wait_description, 123. example_prefix='waiter.wait', 124. include_input=botocore_waiter_params, 125. document_output=False, 126. include_signature=include_signature 127. )


1 about me
Hi! My name is Evan -- I'm a performance and strength coach turned developer. I grew up in
a small town in Maine where all my family still lives! After college, I started my fitness
career
in NYC and then moved to Seattle in 2017.
I am completing a Full-Stack Web Developer program through the University of Washington with skills in CSS, HTML,
JavaScript, and various back-end programs. I am most passionate about the UI/UX design of web
applications
- the mixture of creative vision and technical skills.


| Time/Day | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| 8:00hs | Embedded systems | Embedded systems | |||
| 10:00hs | Digital signal processing | Software engineering | |||
| 13:00hs | Digital signal processing | Artificial Intelligence | Artificial Intelligence | ||
| 15:00hs | Software engineering | ||||
| 19:00hs | Computer Networks | ||||
| 21:00hs | Web programming | Computer Networks | Web programming |


{% extends 'reviewapp/base.html' %} {% block content %}
{{ restaurant.category.category_text }}
There are no reviews for {{ restaurant.restaurant_text }} yet.
Would you like to start writing a review?


Hi Valerie!
Dell Boomi
Sydney: The 29 Dec 11:39 am
New Wippli
New Wippli
Thank you Valerie!
We've received your Wippli
and you'll hear from us soon!
Close
Powered by


Modules
Prerequisites
- Welcome Quest
- Power of Puppet Quest
- Resources Quest
- Mainfest Quest
- Variables Quest
- Conditions Quest
- Ordering Quest
- Classes Quest
Quest Objectives
- Understand the purpose of Puppet modules
- Learn the basic structure and layout of modules
- Write and test a simple module
Getting Started
So far we've seen some simple examples of Puppet code, but what makes Puppet such an adaptable tool? When it comes to getting things done, it's all about the module. A Puppet module is a self-contained bundle of code and data, organized around a particular purpose. The code would encompass manifests, the data would include all the source files, templates etc that you need to accomplish the purpose of the module. Everything we have learned until this point and more can come together as part of a module. When you're ready, type the following command:
quest --start modules
What's a Module?
If resources and classes are the atoms and molecules of Puppet, we might consider modules our amoebas: the first self-contained organisms of the Puppet world. Until now, we've been writing one-off manifests to demonstrate individual Puppet topics, but in actual practice, every manifest should be contained within a module.
Thus far, in order to gain insight into Puppet's language features and syntax, we have been writing one-off manifests, perhaps using a source file for the contents of some configuration file (as we did for the SSH daemon configuration) etc. We have to remember, however that Puppet is designed to help you manage lots of systems (not just one system) from a central point - the master.
Although it is possible to list all the resources (users, files, package, services, cron tasks etc) that you need to manage on a system in one huge manifest, and then apply that manifest on the system, this is not scalable. Neither is it composable, or flexible enough to be reused. Classes were our first stop on the path to learning how to create 'blocks' - building blocks that we can use to describe the configuration of the systems we seek to manage.
There is still a missing part of the puzzle. When you ask Puppet to, say, include ssh
on a particular node, or, as we did in the Power of Puppet quest, classify a node (learn.localdomain) with a class (lvmguide), how does Puppet know where to find the definition for the class, in order to ensure that the specified configuration is realized?
The answer is, we agree to put the class definitions in a standard location on the file system, by placing the manifest containing the class definition in a specific directory in a module.
Simple put, a Module is a directory with a specific structure - a means for us to package everything needed to achieve a certain goal. Once we agree to stick to this standard way of doing this, a significant benefit is the ability to share our work, such that others who seek to achieve the same goal can re-use our work. The Forge is the central location where you can find modules that have been developed by others.
In our initial Quest, we were able to use an Apache module from the Forge. This let us easily install and configure an Apache webserver to host the website version of this Quest Guide. The vast majority of the necessary code had already been written, tested, documented, and published to the Puppet Forge.
Modules provide a structure to make these collections of pre-written Puppet code, well, modular. In order to enable Puppet to access the classes and types defined in a module's manifests, modules give us a standard pattern for the organization of and naming of Puppet manifests and other resources.
Module Path
All modules are located in a directory specified by the modulepath variable in Puppet's configuration file. On the Learning VM, Puppet's configuration file can be found at /etc/puppetlabs/puppet/puppet.conf
.
Task 1 :
Find the modulepath on the Learning VM.
If you're ever wondering where your modulepath is, you can find it by running the puppet agent
command with the --configprint
flag and specifying modulepath
:
puppet agent --configprint modulepath
What the returned value tells us is that Puppet will look in the directories /etc/puppetlabs/puppet/modules
and then in /opt/puppet/share/puppet/modules
to find the modules in use on the system. Classes and types defined by modules in these directories will be available to Puppet.
Module Structure
The skeleton of a module is a pre-defined structure of directories that Puppet already knows how to traverse to find the module's manifests, templates, configuration files, plugins, and anything else necessary for the module to function. Of these, we have encountered manifests and files that serve as the source for configuration files. We will learn about the rest in due course.
Remember, /etc/puppetlabs/puppet/modules
is in our modulepath. Use the ls
command to see what's in that directory:
ls /etc/puppetlabs/puppet/modules
There's the apache
module we installed before, as also the lvmguide
module that is use to set up the quest guide website. Use the tree
command to take a look at the basic directory structure of the module. (To get a nice picture, we can use a few flags with the tree command to limit our output to directories, and limit the depth to two directories.)
tree -L 2 -d /etc/puppetlabs/puppet/modules/
You should see a list of directories, like so:
/etc/puppetlabs/puppet/modules/
└── apache
├── files
├── lib
├── manifests
├── spec
├── templates
└── tests
Once you get down past this basic directory structure, however, the apache
module begins to look quite complex. To keep things simple, we can create our own first module to work with.
Task 2 :
First, be sure to change your working directory to the modulepath. We need our module to be in this directory if we want Puppet to be able to find it.
cd /etc/puppetlabs/puppet/modules
You have created some users in the Resources and Manifests quests, so this resource type should be fairly familiar. Let's make a users
module that will help us manage users on the Learning VM.
The top directory of any module will always be the name of that module. Use the mkdir
command to create your module directory:
mkdir users
Task 3 :
Now we need two more directories, one for our manifests, which must be called manifests
, and one for our tests, which must be called (you guessed it!) tests
. As you will see shortly, tests allow you to easily apply and test classes defined in your module without having to deal with higher level configuration tasks like node classification.
Go ahead and use the mkdir
command to create users/manifests
and users/tests
directories within your new module.
mkdir users/{manifests,tests}
If you use the tree users
command to take a look at your new module, you should now see a structure like this:
users
├── manifests
└── tests
2 directories, 0 files
Task 4 :
Create a manifest defining class users:
The manifests directory can contain any number of the .pp
manifest files that form the bread-and-butter of your module. Whatever other manifests it contains, however, the init.pp
manifest defines the module's main class, which must have same name as the module itself, in this case, users
.
Go ahead and create the init.pp
manifest in the users/manifests
directory. (We're assuming you're still working from the /etc/puppetlabs/puppet/modules
. The full path would be /etc/puppetlabs/puppet/modules/users/manifests.init.pp
)
nano users/manifests/init.pp
Now in that file, add the following code:
class users {
user { 'alice':
ensure => present;
}
}
We have defined a class with just the one resource in it. A resource of type user
with title alice
.
Use the puppet parser
tool to validate your manifest:
puppet parser validate users/manifests/init.pp
For now, we're not going to apply anything. This manifest defines the users
class, but so far, we haven't declared it. That is, we've described what the users
class is, but we haven't told Puppet to actually do anything with it.
Declaring Classes from Modules
Remember when we talked about declaring classes in the Classes Quest? We said we would discuss more on the correct way to use classes in the Modules Quest. Once a class is defined in a module, there are actually several ways to declare it. As you've already seen, you can declare classes by putting include [class name]
in your main manifest, just as we did in the Classes Quest.
The include
function declares a class, if it hasn’t already been declared somewhere else. If a class has already been declared, include
will notice that and do nothing.
This lets you safely declare a class in several places. If some class depends on something in another class, it can declare that class without worrying whether it’s also being declared elsewhere.
Task 5 :
Write a test for our new class:
In order to test our users
class, we will create a new manifest in the tests
directory that declares it. Create a manifest called init.pp
in the users/tests
directory.
nano users/tests/init.pp
All we're going to do here is declare our users
class with the include
directive.
include users
Try applying the new manifest with the --noop
flag first. If everything looks good, apply the users/tests/init.pp
manifest without the --noop
flag to take your users
class for a test drive, and see how it works out when applied.
Use the puppet resource
tool to see if user alice
has been successfully created.
So What happened here? Even though the users
class was in a different manifest, we were able to declare our test manifest. Because our module is in Puppet's modulepath, Puppet was able to find the correct class and apply it.
You just created your first Puppet module!!
Classification
When you use a Node Classifier, such as the Puppet Enterprise Console, you can classify nodes - which is to say that you can state which classes apply to which nodes, using the node classifier. This is exactly what we did when we use the PE Console to classify our Learning VM node with the lvmguide
class in the Power of Puppet quest. In order to be able to classify a node thus, you must ensure all of the following:
- There is a module (a directory) with the same name as the class in the modulepath on the Puppet master
- The module has a file called
init.pp
in themanifests
directory contained within it - This
init.pp
file contains the definition of the class
Once you starting writing and using modules, you can start creating composable configurations for systems. For example, let's say that you have a module called 'ssh' which provides class ssh, another called 'apache' and a third called 'mysql'. Using these three modules, and the classes provided by them, you can now classify a node to be configured with any combination of the three classes. You can have a server that has mysql and ssh managed on it (a database server), another with apache and ssh managed on it (a webserver), and a server with only ssh configured on it. The possibilities are endless. With well-written, community-vetted, even Puppet Supported Modules from the Forge, you can be off composing and managing configuration for your systems in no time. You can also write your own modules that use classes from these Forge modules, as we did with the lvmguide
class, and resuse them too.
Review
- We identified what the features of a Puppet Module are, and understood how it is useful
- We wrote our first module!
- We learned how modules (and the classes within them) can be used to create composable configurations by using a node classifier such as the PE Console.


Buckle-up Friends - it's time to go back to the wild west.
PHP everywhere - its low barrier to entry
Very powerful as part of a LAMP solution
Custom PHP solutions made life better...
...well, more dynamic
...well, ok, we went crazy.
Custom solutions created custom problems:
Developers started to standardize solutions that were "user" focused
So what does that mean for you?
Every module needs a .info file to alert Drupal that it exists. The .info file requires you have:
What it looks like right now
name = My Very Own Module
description = A module for the 2012 BAD camp PHP training.
core = 7.x
You can also include the following:
Taken from: http://drupal.org/node/542202
What it could look like
name = My Very Own Module
description = A module for the 2012 BAD camp PHP training.
core = 7.x
package = Four Kitchens
dependencies[] = views
php = 5.3
stylesheets[all][] = style.css
stylesheets[print][] = print.css
scripts[] = js/script.js
configure = admin/config/content/my_module
This is where most of your code will actually live. It is the center of all of your coding.
So, this is where we start into the nitty gritty PHP site of creating our code. Creating the awesome things that we are going to embark upon...
... wait... how do we do that?
Let's take a look at:
Imagine if you will....
Drupal is very much like this bizarre story of invertebrate fulfillment
minus the snails
NOW we can start writing our code, and to do that we are going to use some new hooks. Namely hook_menu() and hook_permission().
Both of these hooks will be found in 99% of each module that is coded.
This hook will allow you to create your own pages on your Drupal site. You pass back an array, where the keys are the URLs that you are assigning.
function YOUR_MODULE_menu() {
$items = array();
$items['your/url/in/full'] = array();
return $items;
}
For hook_menu to work, you must return within your array. Here are those variables:
function YOUR_MODULE_menu() {
$items['your/full/url'] = array(
'title' => t(''),
'page callback' => '',
'type' => MENU_NORMAL_ITEM,
'access callback' => '',
'access arguments' => array(''),
);
return $items;
}
function YOUR_MODULE_menu() {
$items['your/full/url'] = array(
'title' => t('This is my site.'),
'page callback' => 'YOUR_MODULE_your_function_name',
'type' => MENU_NORMAL_ITEM,
'access callback' => 'user_access',
'access arguments' => array('??????'),
);
return $items;
}
What is this access thing?
This is where hook_permission comes into play...
hook_permission is how you tell Drupal the permissions that your module needs to use. It allows you to assign certain role groups permission to use or not use features within your module.
After you set your own permissions, you can use user_access to check and see if the current user has permissions to access that section of your code.
function YOUR_MODULE_permission() {
return array(
'' => array(
'title' => t(''),
'description' => t(''),
),
);
}
function YOUR_MODULE_permission() {
return array(
'permission name' => array(
'title' => t('What you want to call it'),
'description' => t('A description to be shown on Drupal\'s permission page'),
),
);
}
So, within hook_menu() access arguments, we would put 'permission name'.
function YOUR_MODULE_menu() {
$items['your/full/url'] = array(
'title' => t('This is my site.'),
'page callback' => 'YOUR_MODULE_your_function_name',
'type' => MENU_NORMAL_ITEM,
'access callback' => 'user_access',
'access arguments' => array('permission name'),
);
return $items;
}
function YOUR_MODULE_permission() {
return array(
'permission name' => array(
'title' => t('What you want to call it'),
'description' => t('A description to be shown on Drupal\'s permission page'),
),
);
}
tagsWhat is a theme?
What is your quest
Ignore that one... A theme is just a module, with the specific goal of assigning the front end structure to the site. It is still made up by the same basic parts.
A .info file, to alert Drupal of our theme
But instead of a .module file, we use a template.php file to do any PHP within.
A .module is for modules, and can contain any hooks
The template.php is just for theme preprocessors (mainly) and usually doesn't contain non-theme hooks
This can get a little... weird. BUT as long as you remember to put your hooks in a module... you will be alright.
Lets look at a preprocess function.


DfE enquiries
Central newsdesk 020 7783 8300
General enquiries 0370 000 2288
Press release
New college of teaching and more high-quality training to support a world-class teaching profession.
Plans to support the creation of a new, independent college of teaching that will help to put teachers on a par with other high-status professions like law and medicine, and a new fund to champion more high-quality professional development for teachers, have been announced today (20 March 2015) by Education Secretary Nicky Morgan and Schools Minister David Laws.
Great teachers are at the heart of the government’s plan for education, with the rise in standards in recent years made possible because of their hard work and commitment.
But the government recognises the crucial reforms it has introduced have asked a lot of the profession, which is why it wants to give more back. For this reason, last month, the Education Secretary and the Deputy Prime Minister, Nick Clegg, pledged to support the profession to tackle the issue of unnecessary and unproductive workload by announcing a series of actions including:
The plans announced today will build on these commitments by ensuring England’s teachers have the support and leadership they need, further raising the status of teaching and putting the profession in England on a par with the best in the world, so that teachers can achieve the best possible outcomes for their pupils, by:
Education Secretary Nicky Morgan said:
In my role as Education Secretary I’ve have been very fortunate to have met with more than 700 superb teaching professionals from across the country - all dedicated to preparing the next generation of pupils for life in modern Britain.
I am very pleased to announce that we intend to support the ‘claim your college’ consortium as it establishes a new college of teaching - addressing the absence of a professional body for teachers in England.
And, through the new professional development fund, we will provide more teachers with access to the types of high-quality professional development opportunities that teachers and school leaders have told us they want and that will place the teaching profession in England on a par with the best in the world and ensure our children get the best possible education.
Schools Minister David Laws said:
The key to building a stronger economy and a fairer society is ensuring we have excellent teachers in our schools to inspire pupils to achieve their full potential.
We already have world-class teachers doing just that, but we want to champion them even further by helping them to place teaching on an equal footing with other high-status professions like medicine and law.
The new sector-led college of teaching, independent from the government, will help to achieve that vision, and more high-quality, evidence-based professional development will support the profession to grow and learn.
Vicky Beer, Chair of the Teaching Schools Council, said:
I welcome today’s announcement which is another important step towards a school-led system, helping school leaders and teachers to take greater responsibility for developing their profession.
The announcement of the first phase of the new professional development fund, with its important focus on building robust evidence, will help to consolidate the existing excellent work of the teaching schools network, and give even more teachers access to the types of professional development that make a real different to them and their pupils.
Angela McFarlane, CEO and Registrar of the College of Teachers, said:
The ‘claim your college’ consortium welcomes government’s recognition of the significant boost that a new college of teaching could give to raising the status of the teaching profession in England, and supporting teachers as they develop their professional practice.
We are all agree that a new body needs to be fully independent of government - set up and owned by teachers for teachers - but we are delighted to accept an offer of initial support from government, on the clear understanding that any and all such support must not in any way compromise the independence of the new college.
We will be working through details of the proposed support over the course of the coming months. We very much look forward to pressing ahead with the set-up of the new organisation, building on support received from The Mercer’s Company, and welcoming more teachers to join us in this exciting and hugely significant development.
David Weston, CEO of the Teacher Development Trust and the newly appointed chair of the group, said:
I am delighted to have been asked to chair the expert group. I and the other members of the group will be listening carefully and working together with the wider profession to help set a respected and constructively challenging standard for the professional development of all teachers. We want to articulate this clearly, in a way that will help leaders, teachers and other stakeholders to develop practice that ultimately helps more teachers thrive and more young people succeed.
I am keen to ensure that our work is underpinned by the existing and emerging research about the use of evidence and teachers’ professional development. We have an excellent group of talented teachers, leaders and academics from across the sector, and we are determined to draw on the knowledge and expertise from across all schools and the wider system. I would ask everyone who works in and with schools to please share your experience and your wisdom with us to help us get this important process right for everyone.
The plans outlined today will build on work the government has already undertaken to support the teaching profession, including:
Central newsdesk 020 7783 8300
General enquiries 0370 000 2288
Published: 20 March 2015


This package contains the framework for building configuration applications. There are two main classes that must be implemented to use this framework. One is a single class that is the subject of the management, the other is a command factory and the commands (more on that in a moment).
The framework is arranged with a CommandSource pushing Command objects on a queue and a CommandProcessor popping commands from the queue and executing. The CommandSource references a CommandFactory to build command instances from the native form supported by the CommandSource. Both the CommandSource and the CommandProcessor can run on worker threads or on a single thread. By default, the CommandSource runs on the calling thread and the CommandProcessor runs on a worker thread. The CommandController is responsible for connecting the source and the processor to the processing queue and for starting threads and/or running the source and processor run methods.
Default implementations are provided for the queue, the CommandSource and the CommandProcessor. Implementation of the CommandFactory, the Command derivations and the subject class are application specific. A base CommandFactory implementation is provided. The default CommandSource takes its input from standard in, so simple command line applications require little framework code.
A complete application (e.g. the VIX cache configuration utility) is constructed something like:
public static void main(String[] argv)
{
...
try
{
CacheManagerImpl cacheManager = CacheManagerImpl.getSingleton();
CommandFactory commandFactory = InteractiveCacheCommandFactoryImpl.getSingleton();
CommandController


{% load static %} {% load staticfiles pipeline json_script_escape %}
As part of its commitment to good governance, National Treasury (NT) is making available the extensive municipal financial data it has been collecting since 2003/4.
Users are encouraged to utilise this data to leverage public participation in governance, create value for developers, business, researchers and others.
Subject to certain limitations summarized below, you are free to use the data on this website and published through our APIs (Application Programming Interface) freely and flexibly, for both commercial and non-commercial purposes, at no cost.
This is only a summary of the Terms of Use Policy. Please see the full policy below.
You MAY:
You MAY NOT:
NT is committed to enabling good governance, through increasing transparency to strengthen citizen oversight and promote accountability. Therefore, it is making available the extensive municipal financial data it has been collecting since 2003/4.
The purpose of this Terms of Use policy is primarily to indicate how this website and data may be used, and what limitations are placed on the use thereof. You are encouraged to use and re-use the data that is available on this website and published through our APIs freely and flexibly, subject to the conditions set out herein.
Users are encouraged to utilise this data to leverage public participation in governance, create value for developers, business, researchers and others. Users should also be aware of the potential limitations of the datasets.
Should you come across any inconsistencies in the data or any problematic data on this website that may need to be corrected, please do let us know by contacting us at<EMAIL_ADDRESS>We will endeavour to respond to all queries and comments as soon as possible.
Municipal Money is an initiative of the National Treasury, which has collected extensive municipal financial data over several years and would like to share this information with the public.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
Municipal Money is an initiative of the National Treasury, which hosts extensive amounts of municipal financial data, submitted by municipalities. In order to share this data with the public, National Treasury has enlisted the help of an external partner, Code for South Africa – an NGO that promotes informed public decision-making using technology.
Municipal Money is a free, impartial, politically neutral, online tool to find out about how municipal funds are spent. Our aim is to help citizens understand where public money is spent and whether this is within acceptable norms, not to comment on how it is spent. In doing so we hope to empower our citizens, strengthen civic oversight and promote accountability. We hope that Municipal Money will be a useful tool for everyone, regardless of their political persuasion and their views on public spending.


Caught Read-Handed
Alex Childers, CS 328
Validate by pasting .xhtml copy's URL into
https://html5.validator.nu/


- add(boolean) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given boolean
value, appending it to the end of
the list.
- add(long) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given long
value, appending it to the end of
the list.
- add(double) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given double
value, appending it to the end of
the list.
- add(String) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given String
value, appending it to the end of the list.
- add(byte[]) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given byte value, appending it to the end of the list.
- add(Date) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given Date
value, appending it to the end of the list.
- add(int, boolean) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given boolean
value, inserting it at the given
index in the list.
- add(int, long) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given long
value, inserting it at the given
index in the list.
- add(int, double) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given double
value, inserting it at the given
index in the list.
- add(int, String) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given String
value, inserting it at the given
index in the list.
- add(int, byte[]) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given byte value, inserting it at the given index in the list.
- add(int, Date) - Method in class com.dropbox.sync.android.DbxList
-
Adds the given Date
value, inserting it at the given index
in the list.
- addListener(DbxAccount.Listener) - Method in class com.dropbox.sync.android.DbxAccount
-
Adds a DbxAccount.Listener which will be called each time the
account changes: i.e.
- addListener(DbxAccountManager.AccountListener) - Method in class com.dropbox.sync.android.DbxAccountManager
-
- addListener(DbxFile.Listener) - Method in class com.dropbox.sync.android.DbxFile
-
Adds a listener that will be called when there's a change to the sync
status, file info, or contents of this file or other versions of the same
file.
- addListListener(DbxDatastoreManager.ListListener) - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
- addPathListener(DbxFileSystem.PathListener, DbxPath, DbxFileSystem.PathListener.Mode) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Registers a listener that will be called when there's a change
to info or contents of a file or folder at the given path, or
optionally to its children or descendants.
- addSyncStatusListener(DbxDatastore.SyncStatusListener) - Method in class com.dropbox.sync.android.DbxDatastore
-
Adds a listener that will be called when there's a change to the sync
status of this datastore, as returned by
DbxDatastore.getSyncStatus()
.
- addSyncStatusListener(DbxFileSystem.SyncStatusListener) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Registers a listener that will be called when there's a change
to the status of background synchronization, as returned by
DbxFileSystem.getSyncStatus()
.
- anyFailure() - Method in class com.dropbox.sync.android.DbxSyncStatus
-
Convenience method for determining whether any operation failed,
and getting an appropriate exception to throw.
- anyInProgress() - Method in class com.dropbox.sync.android.DbxSyncStatus
-
Convenience method for checking whether any type of operation is
in progress.
- appendString(String) - Method in class com.dropbox.sync.android.DbxFile
-
Appends the given string encoded in UTF-8 to the file.
- asList() - Method in class com.dropbox.sync.android.DbxTable.QueryResult
-
Returns a list containing all the resulting records, loaded into memory.
- awaitFirstSync() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Waits for the first sync of this cache to be complete (as
defined by
DbxFileSystem.hasSynced()
, so that valid file info is
available.
- DbxAccount - Class in com.dropbox.sync.android
-
Represents a specific user's Dropbox account.
- DbxAccount.Listener - Interface in com.dropbox.sync.android
-
Callback interface for listeners to be notified when a
specific account changes.
- DbxAccountInfo - Class in com.dropbox.sync.android
-
Information about a user's Dropbox account.
- DbxAccountManager - Class in com.dropbox.sync.android
-
This is the entry point for the Sync API.
- DbxAccountManager.AccountListener - Interface in com.dropbox.sync.android
-
Interface for receiving notifications of a new account being
linked or an existing account being unlinked.
- DbxAccountManager.ConfigurationMismatchException - Exception in com.dropbox.sync.android
-
- DbxAccountManager.MultipleAccountsException - Exception in com.dropbox.sync.android
-
Thrown when the app attempts to link with a Dropbox account while
already linked.
- DbxDatastore - Class in com.dropbox.sync.android
-
A datastore is a container for app data.
- DbxDatastore.SyncStatusListener - Interface in com.dropbox.sync.android
-
A listener that will be called when there's a change to the sync
status of this datastore.
- DbxDatastoreInfo - Class in com.dropbox.sync.android
-
Info about a Dropbox datastore.
- DbxDatastoreManager - Class in com.dropbox.sync.android
-
The Datastore Manager allows you to access datastores in a user's Dropbox.
- DbxDatastoreManager.ListListener - Interface in com.dropbox.sync.android
-
A listener that will be called when there's a change to the list of
known datastores.
- DbxDatastoreStatus - Class in com.dropbox.sync.android
-
- DbxException - Exception in com.dropbox.sync.android
-
Base class for exceptions.
- DbxException.AlreadyOpen - Exception in com.dropbox.sync.android
-
Specified file is already open.
- DbxException.ApiUsage - Exception in com.dropbox.sync.android
-
Specific usage or arguments.
- DbxException.Disallowed - Exception in com.dropbox.sync.android
-
The app attempted an operation that isn't allowed by its access
level.
- DbxException.DiskSpace - Exception in com.dropbox.sync.android
-
Insufficient storage space.
- DbxException.Exists - Exception in com.dropbox.sync.android
-
Specified file or folder already exists.
- DbxException.InvalidParameter - Exception in com.dropbox.sync.android
-
Bad parameter value, such as attempting to delete or move the root
directory.
- DbxException.Network - Exception in com.dropbox.sync.android
-
Network failure.
- DbxException.NetworkConnection - Exception in com.dropbox.sync.android
-
Failure to establish a network connection.
- DbxException.NetworkTimeout - Exception in com.dropbox.sync.android
-
Network timeout.
- DbxException.NotFound - Exception in com.dropbox.sync.android
-
Specified file or folder doesn't exist.
- DbxException.NoThumb - Exception in com.dropbox.sync.android
-
No thumbnail is available.
- DbxException.Parent - Exception in com.dropbox.sync.android
-
Parent of a specified file or folder doesn't exist, or is a file
rather than a folder.
- DbxException.Quota - Exception in com.dropbox.sync.android
-
The user's Dropbox quota is full.
- DbxException.RecoverableSystem - Exception in com.dropbox.sync.android
-
System failure that should be recoverable in some way.
- DbxException.Server - Exception in com.dropbox.sync.android
-
Error reported by the server.
- DbxException.Ssl - Exception in com.dropbox.sync.android
-
Failure to establish SSL communication.
- DbxException.Unauthorized - Exception in com.dropbox.sync.android
-
Application or user isn't authorized.
- DbxFields - Class in com.dropbox.sync.android
-
Allows you to access a set of fields, which might be stored in a record
in a datastore, or might be a temporary set not yet saved in a record.
- DbxFields() - Constructor for class com.dropbox.sync.android.DbxFields
-
Creates a new temporary set of fields held in memory, without being included in a record.
- DbxFields(DbxFields) - Constructor for class com.dropbox.sync.android.DbxFields
-
Creates a new temporary set of fields held in memory, without being included in a record.
- DbxFields.AtomType - Enum in com.dropbox.sync.android
-
The atomic value types: those which can be included in lists.
- DbxFields.FieldNotFound - Exception in com.dropbox.sync.android
-
Thrown when attempting to get the value of a field that isn't present.
- DbxFields.IllegalFieldName - Exception in com.dropbox.sync.android
-
Thrown when an illegal field name is given.
- DbxFields.ValueType - Enum in com.dropbox.sync.android
-
The possible types of datastore field values, as stored on the server.
- DbxFields.WrongValueType - Exception in com.dropbox.sync.android
-
Thrown when attempting to get a field that isn't of the specified type.
- DbxFile - Class in com.dropbox.sync.android
-
Provides access to a file in Dropbox.
- DbxFile.Listener - Interface in com.dropbox.sync.android
-
A listener that will be called when there's a change to the sync
status, file info, or contents of this file.
- DbxFile.StreamExclusionException - Exception in com.dropbox.sync.android
-
Thrown when attempt was made to read or write this DbxFile when an existing
stream is already open.
- DbxFileInfo - Class in com.dropbox.sync.android
-
Info about a Dropbox file system entry.
- DbxFileStatus - Class in com.dropbox.sync.android
-
- DbxFileStatus.PendingOperation - Enum in com.dropbox.sync.android
-
Indicates the pending operation on a file.
- DbxFileSystem - Class in com.dropbox.sync.android
-
Provides access to the files and folders in a user's Dropbox.
- DbxFileSystem.PathListener - Interface in com.dropbox.sync.android
-
A listener to be called when there's a change at a given path, or
optionally to its descendants.
- DbxFileSystem.PathListener.Mode - Enum in com.dropbox.sync.android
-
Specifies the situations in which a listener should be notified.
- DbxFileSystem.SyncStatusListener - Interface in com.dropbox.sync.android
-
- DbxFileSystem.ThumbFormat - Enum in com.dropbox.sync.android
-
Specifies the desired format when opening a thumbnail.
- DbxFileSystem.ThumbSize - Enum in com.dropbox.sync.android
-
Specifies the desired size when opening a thumbnail.
- DbxList - Class in com.dropbox.sync.android
-
Allows you to access a list value, which might be stored in a field in a
DbxRecord
or
DbxFields
, or might be a temporary list created by a
constructor and not saved in any field.
- DbxList() - Constructor for class com.dropbox.sync.android.DbxList
-
Creates new empty DbxList
which can hold a list not yet
inserted into any records.
- DbxList(DbxList) - Constructor for class com.dropbox.sync.android.DbxList
-
Creates new DbxList
holding a list not yet inserted into any
records.
- DbxPath - Class in com.dropbox.sync.android
-
Represents a path in Dropbox, relative to the root which is visible to your app.
- DbxPath(String) - Constructor for class com.dropbox.sync.android.DbxPath
-
- DbxPath(DbxPath, String) - Constructor for class com.dropbox.sync.android.DbxPath
-
Creates a new
DbxPath
representing a child or descendant
of a parent path.
- DbxPath.InvalidPathException - Exception in com.dropbox.sync.android
-
Thrown when a given string isn't a valid Dropbox path, due to
invalid characters, names, or encodings.
- DbxRecord - Class in com.dropbox.sync.android
-
A record represents an entry in a particular table in a datastore.
- DbxRecord.IllegalRecordId - Exception in com.dropbox.sync.android
-
Thrown when an illegal record ID is given.
- DbxSyncStatus - Class in com.dropbox.sync.android
-
The current status of background synchronization for a
DbxFileSystem
.
- DbxSyncStatus.OperationStatus - Class in com.dropbox.sync.android
-
The current status of one type of background synchronization operation.
- DbxTable - Class in com.dropbox.sync.android
-
A collection of records that lets you query for existing records or insert new ones.
- DbxTable.IllegalTableId - Exception in com.dropbox.sync.android
-
Thrown when an illegal table ID is given.
- DbxTable.QueryResult - Class in com.dropbox.sync.android
-
Represents the records returned by a query on a
DbxTable
.
- DbxTable.ResolutionRule - Enum in com.dropbox.sync.android
-
- DEFAULT_DATASTORE_ID - Static variable in class com.dropbox.sync.android.DbxDatastoreManager
-
- delete(DbxPath) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Deletes a file, or recursively deletes a folder.
- deleteDatastore(String) - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
Deletes a datastore by ID.
- deleteField(String) - Method in class com.dropbox.sync.android.DbxFields
-
Removes the field with the given name.
- deleteField(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Removes the field with the given name.
- deleteRecord() - Method in class com.dropbox.sync.android.DbxRecord
-
Deletes this record.
- displayName - Variable in class com.dropbox.sync.android.DbxAccountInfo
-
The recommended string to display to identify an account.
- download - Variable in class com.dropbox.sync.android.DbxSyncStatus
-
Status of downloading file contents into the
cache.
- get(String) - Method in class com.dropbox.sync.android.DbxTable
-
Returns the record with the given ID, or null
if the record doesn't exist.
- getAccount() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Returns DbxAccount
associated with this DbxFileSystem
.
- getAccountInfo() - Method in class com.dropbox.sync.android.DbxAccount
-
Returns the
DbxAccountInfo
for this account, if available, or
null
otherwise.
- getAppendStream() - Method in class com.dropbox.sync.android.DbxFile
-
Returns a stream that can be used to append data to this file.
- getBoolean(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a boolean
field with the given name, which must
exist and be of the correct type.
- getBoolean(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a boolean
element at the given index, which must
exist and be of the correct type.
- getBoolean(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a boolean
field of the given name, which must
exist and be of the correct type.
- getBytes(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a byte field of the given name, which must
exist and be of the correct type.
- getBytes(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a byte element at the given index, which must
exist and be of the correct type.
- getBytes(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a byte field of the given name, which must
exist and be of the correct type.
- getChild(String) - Method in class com.dropbox.sync.android.DbxPath
-
Treats this path as a folder and returns the path of a
child file or folder with the given name.
- getDatastore() - Method in class com.dropbox.sync.android.DbxTable
-
- getDate(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a Date
field of the given name, which must
exist and be of the correct type.
- getDate(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a Date
element at the given index, which must
exist and be of the correct type.
- getDate(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a Date
field of the given name, which must
exist and be of the correct type.
- getDouble(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a double
field of the given name, which must
exist and be of a numerical type.
- getDouble(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a double
element at the given index, which must
exist and be of a numerical type.
- getDouble(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a double
field of the given name, which must
exist and be of a numerical type.
- getFieldType(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the type of value in the field with the given name, or null
if the field isn't set.
- getFieldType(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the type of value in the field with the given name, or null
if the field isn't set.
- getFileInfo(DbxPath) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Returns info about a given file or folder by path.
- getId() - Method in class com.dropbox.sync.android.DbxDatastore
-
Returns the ID of this datastore.
- getId() - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the ID of this record.
- getId() - Method in class com.dropbox.sync.android.DbxTable
-
Returns the ID of this table.
- getInfo() - Method in class com.dropbox.sync.android.DbxFile
-
Returns info about this file.
- getInstance(Context, String, String) - Static method in class com.dropbox.sync.android.DbxAccountManager
-
Initializes the Dropbox Sync API if necessary, and returns an object for
interacting with the Sync API.
- getLinkedAccount() - Method in class com.dropbox.sync.android.DbxAccountManager
-
Returns the
DbxAccount
for the linked Dropbox account, if any.
- getList(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns a
DbxList
object for reading and writing the contents of a
List field of the given name.
- getList(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns a
DbxList
object for reading and writing the contents of a
List field of the given name.
- getLong(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a long
field of the given name, which must
exist and be of the correct type.
- getLong(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a long
element at the given index, which must
exist and be of the correct type.
- getLong(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a long
field of the given name, which must
exist and be of the correct type.
- getManager() - Method in class com.dropbox.sync.android.DbxDatastore
-
- getName() - Method in class com.dropbox.sync.android.DbxPath
-
Returns the unqualified name of the file or folder at this path.
- getNewerStatus() - Method in class com.dropbox.sync.android.DbxFile
-
Checks for newer versions of this file, and returns the synchronization
status of a newer version, if any.
- getOrCreateList(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns a
DbxList
object for reading and writing the contents of a
List field of the given name.
- getOrCreateList(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns a
DbxList
object for reading and writing the contents of a
List field of the given name.
- getOrInsert(String) - Method in class com.dropbox.sync.android.DbxTable
-
Returns the record with the given ID, or inserts a new record with the
given ID and no fields.
- getOrInsert(String, DbxFields) - Method in class com.dropbox.sync.android.DbxTable
-
Returns the record with the given ID, or inserts a new record with the
given ID and a copy of the given fields.
- getParent() - Method in class com.dropbox.sync.android.DbxPath
-
Returns the path of the folder containing this path, or
null
if the path is "/"
.
- getPath() - Method in class com.dropbox.sync.android.DbxFile
-
Gets the path used to open or create this file.
- getReadStream() - Method in class com.dropbox.sync.android.DbxFile
-
Returns a stream that can be used to read data from this file.
- getString(String) - Method in class com.dropbox.sync.android.DbxFields
-
Returns the value of a String
field of the given name, which must
exist and be of the correct type.
- getString(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the value of a String
element at the given index, which must
exist and be of the correct type.
- getString(String) - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the value of a String
field of the given name, which must
exist and be of the correct type.
- getSyncStatus() - Method in class com.dropbox.sync.android.DbxDatastore
-
Returns the current status of synchronizing this datastore.
- getSyncStatus() - Method in class com.dropbox.sync.android.DbxFile
-
Returns the current status of synchronizing this version
of this file.
- getSyncStatus() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Returns the status of background synchronization.
- getTable(String) - Method in class com.dropbox.sync.android.DbxDatastore
-
Returns a reference to the table with the given ID in this datastore.
- getTable() - Method in class com.dropbox.sync.android.DbxRecord
-
Returns the table that contains this record.
- getTables() - Method in class com.dropbox.sync.android.DbxDatastore
-
Returns a set of all tables in the datastore that currently contain any records.
- getType(int) - Method in class com.dropbox.sync.android.DbxList
-
Returns the type of the element at the given index.
- getUserId() - Method in class com.dropbox.sync.android.DbxAccount
-
Returns the user ID for this account.
- getWriteStream() - Method in class com.dropbox.sync.android.DbxFile
-
Returns a stream that can be used to write data to this file.
- iconName - Variable in class com.dropbox.sync.android.DbxFileInfo
-
The name of an appropriate icon to display for the file, taken from the
Dropbox icon library.
- id - Variable in class com.dropbox.sync.android.DbxDatastoreInfo
-
The ID of the datastore.
- inProgress - Variable in class com.dropbox.sync.android.DbxSyncStatus.OperationStatus
-
Indicates that operations are in progress or queued for retry.
- insert() - Method in class com.dropbox.sync.android.DbxTable
-
Inserts a new record with no fields, generating a new unique ID for the
resulting record.
- insert(DbxFields) - Method in class com.dropbox.sync.android.DbxTable
-
Inserts a new record with a copy of the given the given field values, generating
a new unique ID.
- isCached - Variable in class com.dropbox.sync.android.DbxFileStatus
-
Whether this file revision is available in the local
cache.
- isConnected - Variable in class com.dropbox.sync.android.DbxDatastoreStatus
-
Set when the API is in active communication with the server, so that remote
changes are likely to be visible quickly, and local changes can be uploaded
soon.
- isDeleted() - Method in class com.dropbox.sync.android.DbxRecord
-
Returns whether this record has been deleted.
- isDescendantOf(DbxPath) - Method in class com.dropbox.sync.android.DbxPath
-
Returns whether the given path is a descendant of this one.
- isDownloading - Variable in class com.dropbox.sync.android.DbxDatastoreStatus
-
Set when there are remote changes that need to be downloaded from the server.
- isEmpty() - Method in class com.dropbox.sync.android.DbxList
-
Returns whether this list is empty.
- isFile(DbxPath) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Checks whether a file exists at the given path.
- isFolder - Variable in class com.dropbox.sync.android.DbxFileInfo
-
Whether this is a folder.
- isFolder(DbxPath) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Checks whether a folder exists at the given path.
- isLatest - Variable in class com.dropbox.sync.android.DbxFileStatus
-
Whether this file revision is the latest known revision.
- isLinked() - Method in class com.dropbox.sync.android.DbxAccount
-
Returns whether this account is currently linked.
- isOpen() - Method in class com.dropbox.sync.android.DbxDatastore
-
Returns whether this DbxDatastore
is currently open (i.e.
- isSameOrDescendantOf(DbxPath) - Method in class com.dropbox.sync.android.DbxPath
-
Returns whether the given path is the same as or a descendant of this
one.
- isShutDown() - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
Checks whether this instance has been shut down, either explicitly with
a call to
DbxDatastoreManager.shutDown()
, or implicitly when its account was unlinked.
- isShutDown() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Checks whether this instance has been shut down, either explicitly with
a call to
DbxFileSystem.shutDown()
, or implicitly when its account was unlinked.
- isSyncActive - Variable in class com.dropbox.sync.android.DbxSyncStatus
-
Background synchronization system is actively
processing or waiting for changes.
- isThumb() - Method in class com.dropbox.sync.android.DbxFile
-
Determines whether this instance represents a thumbnail, as opposed to file contents.
- isUploading - Variable in class com.dropbox.sync.android.DbxDatastoreStatus
-
Set when there are local changes that need to be uploaded to the server.
- isValidFieldName(String) - Static method in class com.dropbox.sync.android.DbxFields
-
Returns true if id
is a valid name for a field in a DbxRecord
.
- isValidId(String) - Static method in class com.dropbox.sync.android.DbxRecord
-
Returns true if id
is a valid ID for a DbxRecord
.
- isValidId(String) - Static method in class com.dropbox.sync.android.DbxTable
-
Returns whether id
is a valid ID for a DbxTable
.
- iterator() - Method in class com.dropbox.sync.android.DbxTable.QueryResult
-
Returns an iterator which can be used to enumerate the resulting records.
- onAccountChange(DbxAccount) - Method in interface com.dropbox.sync.android.DbxAccount.Listener
-
Called when the observed account is unlinked, or account
info changes.
- onDatastoreListChange(DbxDatastoreManager) - Method in interface com.dropbox.sync.android.DbxDatastoreManager.ListListener
-
Called when there's a change to the list of known datastores.
- onDatastoreStatusChange(DbxDatastore) - Method in interface com.dropbox.sync.android.DbxDatastore.SyncStatusListener
-
Called when there's a change to the sync status of this
datastore
- onFileChange(DbxFile) - Method in interface com.dropbox.sync.android.DbxFile.Listener
-
Called when there's a change to the sync status,
file info, or contents of this file.
- onLinkedAccountChange(DbxAccountManager, DbxAccount) - Method in interface com.dropbox.sync.android.DbxAccountManager.AccountListener
-
Called whenever a new account is linked, or an existing
account is unlinked.
- onPathChange(DbxFileSystem, DbxPath, DbxFileSystem.PathListener.Mode) - Method in interface com.dropbox.sync.android.DbxFileSystem.PathListener
-
Called when there's a change to a path for which a listener is
registered.
- onSyncStatusChange(DbxFileSystem) - Method in interface com.dropbox.sync.android.DbxFileSystem.SyncStatusListener
-
Called when there has been a change to the status of background
synchronization.
- open(DbxPath) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Opens an existing file, using the latest cached revision if any exists,
or otherwise using the latest known version.
- openDatastore(String) - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
Open an existing datastore by its ID.
- openDefault(DbxAccount) - Static method in class com.dropbox.sync.android.DbxDatastore
-
Opens the default datastore for the given DbxAccount
.
- openDefaultDatastore() - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
Opens the default datastore, which will be created if it doesn't exist.
- openThumbnail(DbxPath, DbxFileSystem.ThumbSize, DbxFileSystem.ThumbFormat) - Method in class com.dropbox.sync.android.DbxFileSystem
-
Opens a thumbnail for existing file, using the latest cached thumbnail if any
exists, or otherwise using the latest known version of the file.
- orgName - Variable in class com.dropbox.sync.android.DbxAccountInfo
-
The user's organization's name, if available, or null
otherwise.
- SDK_VERSION_NAME - Static variable in class com.dropbox.sync.android.DbxAccountManager
-
The human-readable version number for this SDK.
- serialVersionUID - Static variable in exception com.dropbox.sync.android.DbxAccountManager.ConfigurationMismatchException
-
- serialVersionUID - Static variable in exception com.dropbox.sync.android.DbxAccountManager.MultipleAccountsException
-
- serialVersionUID - Static variable in exception com.dropbox.sync.android.DbxException
-
- set(String, boolean) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given boolean
value,
replacing any prior value.
- set(String, long) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given long
value,
replacing any prior value.
- set(String, double) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given double
value,
replacing any prior value.
- set(String, String) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given String
value,
replacing any prior value.
- set(String, byte[]) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given byte value
replacing any prior value.
- set(String, Date) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to the given Date
value,
replacing any prior value.
- set(String, DbxList) - Method in class com.dropbox.sync.android.DbxFields
-
Sets a field with the given name to List value with a copy of
the contents of the given
DbxList
, replacing any prior value.
- set(int, boolean) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
boolean
value.
- set(int, long) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
long
value.
- set(int, double) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
double
value.
- set(int, String) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
String
value.
- set(int, byte[]) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
String value.
- set(int, Date) - Method in class com.dropbox.sync.android.DbxList
-
Replaces the element at the given index with a new
Date
value.
- set(String, boolean) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given boolean
value,
replacing any prior value.
- set(String, long) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given long
value,
replacing any prior value.
- set(String, double) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given double
value,
replacing any prior value.
- set(String, String) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given String
value,
replacing any prior value.
- set(String, byte[]) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given byte value,
replacing any prior value.
- set(String, Date) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to the given Date
value,
replacing any prior value.
- set(String, DbxList) - Method in class com.dropbox.sync.android.DbxRecord
-
Sets a field with the given name to List value with a copy of
the contents of the given
DbxList
, replacing any prior value.
- setAll(DbxFields) - Method in class com.dropbox.sync.android.DbxFields
-
Copies all of the fields from the given object to this object,
replacing any prior values.
- setAll(DbxFields) - Method in class com.dropbox.sync.android.DbxRecord
-
Copies all of the fields from the given object to this object,
replacing any prior values.
- setResolutionRule(String, DbxTable.ResolutionRule) - Method in class com.dropbox.sync.android.DbxTable
-
Set rule as the resolution pattern for conflicts involving the field
of the given name in all records in this table.
- shutDown() - Method in class com.dropbox.sync.android.DbxDatastoreManager
-
Shuts down this DbxDatastoreManager
and stops background synchronization.
- shutDown() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Shuts down this DbxFileSystem
and stops background synchronization.
- size - Variable in class com.dropbox.sync.android.DbxFileInfo
-
The size, in bytes, of the file content.
- size() - Method in class com.dropbox.sync.android.DbxList
-
Returns the number of elements in this list.
- startLink(Activity, int) - Method in class com.dropbox.sync.android.DbxAccountManager
-
Starts the authentication process to link a new account.
- startLink(Fragment, int) - Method in class com.dropbox.sync.android.DbxAccountManager
-
Starts the authentication process to link a new account.
- startLink(Fragment, int) - Method in class com.dropbox.sync.android.DbxAccountManager
-
Starts the authentication process to link a new account.
- sync() - Method in class com.dropbox.sync.android.DbxDatastore
-
Apply all outstanding changes to the datastore, and also incorporate remote changes
into this datastore.
- syncNowAndWait() - Method in class com.dropbox.sync.android.DbxFileSystem
-
Forces a check for new file info from the server, and waits for it
to complete.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFields.AtomType
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFields.ValueType
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFileStatus.PendingOperation
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFileSystem.PathListener.Mode
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFileSystem.ThumbFormat
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxFileSystem.ThumbSize
-
Returns the enum constant of this type with the specified name.
- valueOf(String) - Static method in enum com.dropbox.sync.android.DbxTable.ResolutionRule
-
Returns the enum constant of this type with the specified name.
- values() - Static method in enum com.dropbox.sync.android.DbxFields.AtomType
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxFields.ValueType
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxFileStatus.PendingOperation
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxFileSystem.PathListener.Mode
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxFileSystem.ThumbFormat
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxFileSystem.ThumbSize
-
Returns an array containing the constants of this enum type, in
the order they are declared.
- values() - Static method in enum com.dropbox.sync.android.DbxTable.ResolutionRule
-
Returns an array containing the constants of this enum type, in
the order they are declared.