labofsahil/github-event-dataset-2012 huggingface dataset:
This function name does not follow the cyphesis convention for method names. It should be camel case, without an underscore line this:

    std::string genereateSlat(size_t length);
Also can this use Caliburn to move the handler to the view model?
Should change to 'seven' here as well.
Судя по нижеследующему коду, логичнее будет [NSMutableString stringWithCapacity:DNA_LENGTH*2], там же у Вас еще и запятые в ней храниться будут. Хотя по сути вполне достаточно [NSMutableString stringWithString: @""]
Собственно, как и требование, чтобы менялось СТРОГО Х ПРОЦЕНТОВ.
Для этого существуют методы доступа getter'ы и setter'ы, чтобы не нарушать икапсуляцию.
Раз вы используете CELL_DIMENSION для заполнения массива, то и при инициализации нужно его использовать.
Yep, I was just rephrasing stuff. One of my defaults is that I'm a perfectionist. ;)
*latest
Sorry, name proposal was targeting at the wrong methods. but the point remains valid. A named arg is less frightening for newcomers then *arg, **kwargs;  would also be nice since you / the user / i could write generator expressions as argument then without prepending an asterisk.
> I think both are fine, do you want me to go through the package and change it?

yes please.
Also here is should be required to specify the subject.
From the logic i saw above, i would assume that passing in a single Locale.US locale should automatically include the Locale.ENGLISH names
I agree! But the aim of this test is to check that it wasn't rolled back, so technically this test should be failing and to be able to make it pass we would have to be explicit about the propagation behavior of our transactional methods.

I believe this is something we need to have on the design call to decide on what behavior we want for  transactional methods calling other transactional methods, i know Darius is inclined towards not rolling back the outer one when the inner one is rolled back.
See Step1 by Darius in the description for https://tickets.openmrs.org/browse/TRUNK-208
We should not put Transactional at the class level, just at the method level so that we can have non transactional service methods.
I'm confused by the "and it wants to redirect" bit.
I probably should have gotten rid of the existing background-color deal here though.
@jeanmonod Yes, that's right
OK, I didn’t know. Will fix.
Yes. I like the idea of including it in the output. Committed in 0786540065320680100abe811cdc15bb77894d05
OK. Left as Nil.
`s/, which is//`
no.  this was handled by a condition in connect, but I moved the condition to the case for clarity.
почему просто константой лучше?
Ну епт. `Ui_.FilesTree_->viewport ()->mapToGlobal (x, y)`, без всяких там учетов хедера.
It might even make sense to "unhide" it, if it's useful.
Quite. Changed to deliver_fn.
What happened to `.with(media_engine, default_voice)`?
seems dead code
I have now clarified this.
Agreed. Could you provide an example of the output format that you think would work better here?
I think you can use contexts without all of shoulda https://rubygems.org/gems/shoulda-context maybe?
Yes, use TypeOfSomething&& here.
Don't know if we can use ActiveSupport methods since some people use
Annotate without Rails.

https://github.com/rails/rails/blob/6ef9fda1a39f45e2d18aba4881f60a19589a2c77/activesupport/lib/active_support/core_ext/object/try.rb#L32


On Fri, Jul 13, 2012 at 4:33 PM, arturtr
<reply@reply.github.com>
wrote:
>> @@ -82,7 +82,7 @@ def get_schema_info(klass, header, options = {})
>>          attrs = []
>>          attrs << "default(#{quote(col.default)})" unless col.default.nil?
>>          attrs << "not null" unless col.null
>> -        attrs << "primary key" if col.name.to_sym == klass.primary_key.to_sym
>> +        attrs << "primary key" if klass.primary_key && col.name.to_sym == klass.primary_key.to_sym
>
> http://api.rubyonrails.org/classes/Object.html#method-i-try
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/ctran/annotate_models/pull/82/files#r1163133



-- 
Alex Chaffee - alex@stinky.com
http://alexchaffee.com
http://twitter.com/alexch
We have to decide here if we want to handle properties or attributes with this syntax.

So far, I assumed we’d handle properties — mainly because of `.innerHTML` and `.textContent`, with a bit of `.style.*` in mind. In this approach, this line would rather be:
```ini
Phone.dataset.helpContent=This is a phone
```
and I guess the code would be quite different.

We could also rely on another approach, which might be a bit more secure:
* use specific aliases (or a specific prefix) for HTML element properties, e.g. `#html` and `#text` for `.innerHTML` and `.textContent` respectively — the rest would be considered as an attribute by default;
* or test if the property exists, change it if it does, or set the attribute if it doesn’t.

Just thinking out loud here. Any opinion about this?
Make private or add javadoc.  Also what's the significance of the epsilon value in the second ternary part?
Okay, I will fix this up.
logging and pass back to the user the issue are 2 different things.
i am still a little concerned about this `self.mapping.device` i dunno where mapping came from?
But how does write skew check work for putMap without NBST, if we don't have the previous versions?
Create a JIRA?
The doc is wrong here as they are now 1 and 2 :)
It would be nice to, but doing so results in Sphinx warnings and incorrect rendering.
If you have them, it'd be nice to include (since this code isn't part of a larger library). If not, don't worry about it.
Not everybody. The unit tests don't need the wait. I won't hold up a merge but can we get a #TODO in here to replace this with a suitable wait?
s/convertis/converti
This class is going to be implemented by external lib. This class will implement this interface https://github.com/ekino/EkinoMetricBundle/blob/master/Interception/MetricInterceptor.php
Oh sorry, I've actually removed this myself a couple of days ago.
Moved the patch from 3.0 branch to master, and re-added it there. Fixing now.
ss-markdown is in misc, not contributing, so the link needs fixing.
Because we replace invalid characters with dashes (with a few exceptions), so if you have multiple adjacent invalids it makes for ugly URLs. Less of a problem with transliteration or unicode URLs, but that's not enabled by default.
I'll add a doc on this line.
This hook actually runs here: https://github.com/ushahidi/Ushahidi_Web/blob/develop/application/libraries/MY_View.php#L42
The last part -layout .. is based on the view name..
I've got ```-``` as a separator because I wanted something the split view_pre_render from the view name and have slightly less chance of naming collisions. 

I can change that in MY_View.php if needed though.
I went ahead and created an issue for this one, #219.
Equality is tested with `===` in `ZendRenderer`. Also comparing this and `ZendRendered` this method looks a lot like copy pasta.
Use get_extension_path to determine the path instead. It also removes . from $name.
This is a hacky little chunk but I don't know what the right way to do this is.
I've updated the filter example. Can you have a look at it ?
Are you sure ``$type`` has the correct type as ``object<Symfony\Component...ts\Fixtures\FooSubType>`` is not a sub-type of ``string``?
Are you sure you want to override the parameter ``$locale``? This often makes code less readable.
`} else {` (single line)
You need to define the return value of the function using a @return style block.
Url shortened wasn't working turning tests or when I recreated the call on the command line. Therefore I implemented my own. If you are happy that the current one works ok I can drop those definition out.
`nil?` tekee saman testi
@eddieajau - Happily - except, I am afraid I don't know what you mean by "turning warnings and notices?" Sorry about that - but if you can explain it for me, I'll certainly try. :) 

(+ your nick is hard to type. Why not use AndrewEddie or bring back Masterchief? Do we get to vote on this? ;- ) )
Capitalized. Same below.
Thanks, you remembered. :)
Strings that include a newline character (\n) must be double-quoted in order the newline character to be registered instead of printing literal \ + n. In the context of this resource, the intent is for a newline character, not literal characters. Please revert this particular change back.
Why did you replace Base.logger by Ticket.logger?
*sigh* I feel like I'm not competent to be writing Java anymore. Fixed.
Every other change in this file (below) has been made because of a simple bug : if luid is still set to "None" when the request to the rwdb has to be made, it crashes (and not only because luid is None, but also because in this case, it's probably because the rwdb is not reachable). So I've added a check (several times) to avoid the bot crashing.
What name should I use? element?
The idea is that you learn. And in this case the idea is to learn how to reuse existing code and adapt it to new needs.
Oh, this is not really user friendly. I imagine rather that instead of saying what is wrong and then user has to manually fix it, is much better to prevent user to get to this state in the first place.

So I would rather do it that when you enable some panel which has dependencies, all dependent panels' checkboxes become checked, but disabled for editing. And bellow it should be written something like "Automatically enabled because panel1 and panel2 dependency."
Which unit is this? Comment!
trying to make sure uniq, and so really just want the username, figured skip "a" to be more likely that get enough of username to be uniq, as limited to 15 chars.
$targetProperty = $this->getProperty()->getTargetProperty();
$localModels[$targetModel->get($targetProperty)]
What I worry about here is that most of the time in practice we end up with missing data values in sample mapping files (e.g., ``NA``). This is especially common for example when using MIMARKS compliant metadata, so I think we'd end up overridding to allow error most of the time. I have to run right now - let me know what you guys think about how to handle this and I'll address later.
Wouldn't be better to use the module platform to understand the underlying OS and apply the related string for loading the extension? You're doing two things at the same time.
Here's an example:

`In [1]: import platform`

`In [2]: platform.uname()`
`Out[2]: 
('Darwin',
 'redbox.local',
 '10.8.0',
 'Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386',
 'i386',
 'i386')`
As you've probably guessed, contains() is problematic because it matches things like "horse_id", and was causing one of the associations tests to fail.

When I proposed making this just equals(), I was informed (can't remember who..) that we also need to make sure it also checks for keys on embedded objects, for example a column name like subobject._id. 

Of course, this should actually be !column.endsWith( "."+ID_FIELDNAME ), I think that will make it safe. I've just made that change.
this has changed, we should rebase on latest release to avoid conflicts in integration and when merging the feature
indentation seems problematic
Can we get a comment above this line with a small description or some usage intentions?
Not sure if this is the best way to do it, but I think it is better than super(optString + " -inputFormat=" + LzoTextInputFormat.class.getName());
Nit: our general convention seems to be using a one liner for inheritdoc.  This file that got hit by the formatter splits it.
both stubed
Good, good. But we do not need extra variable (`request_ip`). You can do all this in one line.
I'm not sure we want this in circus, do we?
Its looks like `.zoomer-overlay` is, but the handles are transparent? But what I mean is to style the edge of `.zoomer-overlay` differently on hover (and maybe while dragging).
Yea, I guess that's a bit nicer.
I think we shouldn't use `CONST` in new code.
I'm sorry, I'm probably just being dumb, but can you point me to where PSOL calls `NgxUrlAsyncFetcher::Init()`?
Not being a regular pandas user, I find this line odd. Why is it needed?
You can change it, if you like
Haha ! Ouais j'suis un mec vachement pointilleux ! :p
This would actually be wrong.  The point is that the photon noise for the galaxy is already in there.  And it's not necessarily only sky_level_pix/100.  That's the minimum noise added, not the maximum.  If that galaxy is rather bright, its photons can have more noise that the sky noise.  So after doing photon shooting we want to make sure only to add the noise from the sky photons.  I've added some clarifying comments to make this hopefully clearer.
I think we can also remove getHalfLightRadius from all the modifiers:  (Add, Convolve, Deconvolve)  That strikes me as better than writing the function and just raising NotImplementedError.
Just a note to update here with whatever we decide about noise type names.
Nope , removed . I needed it to test the controller support .
I guess you didn't really want to push that :-)
to be consistent with the existing code, you should use :
* `checkSequenceIsNotNull(sequence);` to check the given string 
* `assertNotNull(info, actual);` to check actual
Does this controller control the photo of user or photo of farmers, or both?
would be good to add the extra few lines for testing ips in the 169 range, passing in null, passing in "1.1.1.257", etc.
Please use our own random functions.
OK, will log an error



On 10 Jun 2012, at 21:27, Garry Shutler<reply@reply.github.com> wrote:

>> +  require 'evenitron/collector_client'
>> +  require 'evenitron/collector'
>> +
>> +  # Public: convenience method for configuring the gem
>> +  #
>> +  # Examples
>> +  #
>> +  #   Evenitron.configure do |config|
>> +  #     config.system_key = 'your system key'
>> +  #   end
>> +  #
>> +  # Raises StandardError if no system_key passed or found in env variable
>> +  def self.configure
>> +    yield self if block_given?
>> +
>> +    raise StandardError.new("Evenitron system_key required") unless self.system_key
> 
> Say `Rails.logger` isn't quite configured right, I don't know how Rails works but I would say it shouldn't stop the site from running.
> 
> My main priority is to have a running site and logging isn't core to that. I can go away and find out keys, etc and sort logging out but I don't want that to be a hands-in-the-air-the-site-is-down thing.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/evenitron/evenitron-ruby/pull/1/files#r957352
correct. I added a comment line to "label" the intent of the column to the programmers
I would make the last sentence more active "This prevents cross-site scripting attacks, through the use of the "Same Origin Policy"." (not sure if my description of the policy is correct - is it used or inherent?)
Estes metodos ```listaTodasAeronaves()``` e ```consultar(request)``` fazem a mesma coisa. isto é. com execeção do filtro.
Mantenha só o ```consultar(request)``` pq se ninguem digitar nada em ```nome``` vai funcionar como o outro metodo
Made comment clearer:

# The configurations endpoint returns multiple entities when we ask for a single file.
        # This screws up the default implementation of __getitem__ from Collection, which thinks
        # that multiple entities means a name collision, so we have to override it here.
ok, will try that
Was this replaced by the latest lib?
If you take a look at the source file, you'll see examples like this.
This pattern was so common in my clar code that I moved it into the helpers. Basically, this installs a fixture into the sandbox, renames .gitted and other files, then opens the repository. You can call this from `...__initialize()` if you want, or you can call it at the start of each test if you need a different fixture on a per test basis (which I was needing in a couple of different cases).
In fact this should be split into a separate commit. First is the rename and refactoring, then adding the option.
Ты теряешь исключение e.
Надо кешировать предыдущий элемент коллекции. Тогда будет меньше обращений к коллекции по индексу - будет быстрее.
Ah, so you'd prefer that the argument name be text, correct?
added greater_equal
We don't need to require here since utilities is being required by install_generator
Yeah I also wondered about that. you're right, it's probably better.
Yes, code should be avoided at all costs!  I actually removed more lines from sklearn than I added ^^
@larsmans do you think this is good for merge?
I like to be use case driven. We usually illustrate the use cases in examples.

A success would be to make the 3 main Lasso examples faster by just add use_strong_rule parameter to Lasso and ElastcNet

http://scikit-learn.org/stable/auto_examples/linear_model/plot_lasso_coordinate_descent_path.html#example-linear-model-plot-lasso-coordinate-descent-path-py
http://scikit-learn.org/stable/auto_examples/linear_model/plot_lasso_and_elasticnet.html#example-linear-model-plot-lasso-and-elasticnet-py
http://scikit-learn.org/stable/auto_examples/linear_model/plot_lasso_model_selection.html#example-linear-model-plot-lasso-model-selection-py

just keep in mind lasso_path needs sequential strong rules but not Lasso in his default setting with fixed alpha
ce dernier template (tout comme le #include gmp...) devraient être dans un fichier pythran-gpl.h qui serait inclus dans interface.py (je crois)
Sweet. Thanks for the tools!
Well this does work, but I'm begining to have doubts on its viability for forms cloned by various user. What other unique attribute can we use to distinguish cloned forms and relate them with parent forms?
Why we would need that?
Please keep this alphabetical
This one might work
Yes, but don't know if all other slaves are stopping.
One may be stopping, but others want, all are gathered and broadcast.

Only if all have are in getRHS(stopping=true), can it the broadcaster stop requesting the other slaves portions (gatherLocal) and avoid broadcast
Should you pass idxSize instead of -1?
If you can avoid the file trivially yes.
Looks like newLdapSecManager relies on more than ip though..
There is this distinction, yes, but it wasn't always like this and I haven't changed since I'm not entirely sure where this is heading...

I felt the need to split it a few times, though. I think that I ended up putting enough constraints in place that, now, mandate a split...
Aren't links actually supposed to get larger? This seems to keep the link at the same size
raise statement to catch
The nth-arguments features isn't really explicit, you used a better pattern here:
https://github.com/mozilla/addon-sdk/blob/master/packages/api-utils/lib/events.js#L139

   * @param {value} ...
   * More arguments to pass to listeners.
   */
   _emitOnObject: function _emitOnObject(targetObj, type, event /* , ... */) {
We absolutely need a separate error for "no route match" so we can be clear to the developer what happened.
Tabs from Abernathy? :O
I would feel a lot more comfortable if whether to force or not was configurable (and the default set to false). Otherwise, this introduces a potentially dangerous change. If you can make that update, I think its good to merge.
Correction, I fixed it to use peer.  I still need to add report functionality!
This needs in `in_context` method for `Test::Unit`: https://github.com/thoughtbot/shoulda-matchers/blob/master/lib/shoulda/matchers/action_controller/route_matcher.rb#L43
I added a separate README.md and LICENSE.md for the proxy.
Actually I think the hybrid type is satellite image + roads, not just a road map.
This should be kept in place.  the error this represents stems from a failure when interacting with the native LocationManager which is wrapped by TiLocation.  Since the error is not generated by interaction with LocationProviderProxy, moving the error constant to LocationProviderProxy creates a disconnect.
Is there ever a time where Ti will be defined but Titanium won't, or vice versa? I'm wondering if it's redundant.
Not sure if I agree with this from a visual design perspective - I wanted the stats to be small and subtle
Лучше `var new_rating = (rating > 5 || rating < 1) ? 1 : rating;` чем 2 раза `var new_rating`
These are much nicer. Move them to the top of the class, before the constructor. Before even the instance variables.
this should be:

  if default_https_proxy is None:

Also, I am not sure we want to do this: if an ops sets an HTTPS_PROXY, do we really want to remove it when it's not set in the config file ?

I'd say no
Didn't realize you could catch all thrown errors and not specify the particular error you want. I'll change my specs to that once this gets merged; I don't want you to deal with another merge conflict.
I would argue that the former string is easier for a human to parse than this one.  I guess we have precedent in the previous lines though.  reluctant +1 on that change.
we should also check that the specific area is made visible 
#listing-featured.selected 
#listing-popular.selected
#listing-categories.selected
I would prefer us to use `get` instead of `pop`. 

Other than that looks good!
Isn't it simpler to just let the GC handle it? I don't think there is any reason to force RAII on the allocated space here.
Sorry, could you clarify? What is "This"? It is not easily google-able word, unfortunately.
They should be lowercase, too.
are all of these really requirements or are they simply used in the tests .. if the later .. then add these under a new top level section ``require-dev``
Looks good
On 11 Aug 2012 10:25, "Christoph Gritschenberger" <notifications@github.com>
wrote:

> In
> components/services/src/main/java/org/openengsb/core/services/internal/ConnectorManagerImpl.java:
>
> > @@ -44,6 +48,40 @@
> >      private ConnectorRegistrationManager registrationManager;
> >      private ConfigPersistenceService configPersistence;
> >
> > +    private ExecutorService executor = Executors.newFixedThreadPool(5);
> > +    private Semaphore semaphore;
> > +
> > +    class ConnectorInstaller implements Runnable {
> > +        private ConnectorConfiguration configuration;
> > +
> > +        ConnectorInstaller(ConnectorConfiguration configuration) {
> > +            this.configuration = configuration;
> > +        }
> > +
> > +        @Override
> > +        public void run() {
> > +            while (true) {
>
> It could loop indefinitly. But in a separate thread and always with a 30
> second pause while invoking the method
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/openengsb/openengsb-framework/pull/737/files#r1357078>.
>
>
don't know if worth considering allowing double specification if both are the same
Heads up: System.err
I meant the $person variable itself. Are we not working the an instance of \PSU\Person named $person somewhere in here?
This commit crept back into the pull request. If this is removed the rest can be commit.
Have you seen a place where the group itself (as opposed to a member of the group) is trying to perform an administrative operation?
`BatchSendQueue` looks worth

* pulling into another module
* testing
We don't need to really check for a message. :)
Can we use `:name`, `:start`, and `:end`?
Maybe is_persisted would answer destroy? and perhaps there are other ways for create and update (comparing the created_at etc)
this, i like this DSL change
My point is: do not use uniConv at all
si, eso me di cuenta después del commit. xD
I did consider skipping already CIDR'd addresses with something like `/\d{1,3}$/` but it seemed hacky and not worth the effort. Instead just sanitise everything.
m_author ( author ? new TwitterUser (parent) : author) и в инит лист
Should we be checking for `$rootel` visibility here as well, like we do above?
@croby: It's semi-3rd party. We have a lot of Sakai-specific changes in this file. I can revert the change if necessary.
right sorry, misunderstood the question. FF and Webkit handle this fine.
Storing these vars on ``self`` is ugly, because they are transient information for a given call to ``import_data``, not relevant persistent state for the ``CaseImporter``. A ``CaseImporter`` instance could have its ``import_data`` method called multiple separate times. Storing on ``self`` is convenient because it means you don't have to pass stuff around / return values as much, but what it's actually doing is allowing you to not think as clearly about separating the responsibilities of each method, and clearly identifying each method's input and output data. Stuff should only be stored on ``self`` when it really is state that "belongs" to the entire instance.
Can we switch this to `.on('hover')`?
assertEquals() the stored UUID?
Should we be caching by default?
By only supporting <code>Filter</code> and removing <code>Query</code> you removed the support for <code>$top</code> query option. I know that <code>$select</code> is not working on tables but <code>$top</code> does work. Also there could be extra query options to be added in the future which will be used for tables so why make the code here very dependent on the case?
is ``vectorize`` needed now that you are using numpy.cos etc in dtk.bicycle?
Case statements are case-insensitive
I think we can use chef file resource here instead of this ruby block
http://wiki.opscode.com/display/chef/Resources#Resources-File
Please put spaces between variables, operators, and numbers.
Yeah, then we don't need to add the array conversion. Sounds good

I've seen that use of undef in other modules and never liked it - feels ugly. Will have a think if there's a better approach over lunch :)
Git instead SVN
and here? why?
Yes, I think the main thrust was to get the user and sysadmin docs up to scratch and then come back to the developer docs.
be careful with bundle which still support 2.0 as enumNode is a 2.1 feature.
parameters is a list of strings. It works with the eventSource or polling uri. If the uri is something like http://localhost/events?starttime={0}&stoptime={1}
you can specify client side or server side the parameters like so
"parameters": [  
      "starttime" ,"stoptime" 
    ]
for find and replace.
Oops, this method is misnamed.  It should be OpenMaterialProperty.  I'll fix it.
I'd replace the `ALLOWABLE_PARAMS` constant with a method. Constants aren't thread safe, and even though this shouldn't change, I find it better to just always use a method.

```ruby
def allowable_params
  [
    :city, :close_date, :date_of_proof, :first_name,
    :food_stamps, :last_name, :monthly_income, :number_of_children, :open_date,
    :phone, :proof_of_residency_type, :rent, :residency_date,
    :proof_of_residency_type, :smokes, :spouse, :ssn, :state, :street,
    :utilities, :zip ,:created_at, :updated_at
  ]

  def neighbor_params
    params.require(:neighbor).permit(*allowable_params)
  end
```
这段编码转换的程序应该放在整个if之外，用来过滤所有$content吧？除非前面的转换能保证其结果一定是utf8编码的。哪些可以确认是utf8，需要做点儿工作
NGHUTPR
You should probably create a list as an attribute of the InstanceQuotas class, and then save the IDs of all the instances you create. Then you won't have to find them for this method.
probably not... that one just slipped. removing it.
Leave it as is for now - I agree, this is a bigger problem and I don't want to hold your feature up over it.
I don't have a strong opinion. Both looks good to me. +0 for `binary` :)
Will address in the IPy support patch.
Programmatically anticipating, interpreting, and correcting user mistakes is a slippery slope, fraught with introduced data ambiguities and increased difficulty in testing / exploding test cases.  A better alternative, particularly in an API, would be to (if possible/practical) validate the entire field list against a comprehensive, well-defined regex-based schema.
Ok! Nice point of view i will take a deeper detail on this on the next improves for the BB!
Yeah, I actually submitted CloudMade/Leaflet#1042 which Vladimir declined and I think that was reasonable.
Looks like $length is not defined in here?
'available' and 'unavailable' are the only status's i know of...
Ack how did I miss those.
не уверен, что с оптимизируется, поэтому сначала бы сохранил ссылку на sparse_table_[log], а потом уже в ней сделал бы два обращения
I try to avoid referring to the user directly, as it's superfluous information unless there is another way for the dragging to occur.  Could you elaborate on why the current narrative is incorrect from a technical perspective?

Thanks
ditto re kinds of types
However, there may be other properties as well. The view could, for example, be an image view which is having its `image` property set along with `left` - the `image` forces a resize. What we need to do is keep in mind that any property which dictates a view's content should possibly be able to be layout-batched.

One possible solution is to use KVC and simply `[self setValuesForKeysWithDictionary]` which will have the interesting side effect of batching ALL property setting on the view. It also reduces the code of this method to a single line after the arg check.
The whole thing should be only done if (pack.isIncrementalVersion() {
is 2.0.2-SNAPSHOT loaded in nexus repo yet?
This should be a check() call. We should also move this logic and the id check below into the validateConfig function. That way all of our validation is in one place.
Removed almond and replaced it with webworks require
I don't think `locate_user` really expresses what this function does very well - something like `centerMapAtCurrentPosition` would be better. It's a little long but not too bad... I'm open to other suggestions anyway.

Can we try and stick to camel case for the javascript function names anyway - it's what we've been using everywhere else.