bartvde

<wfs:Transaction xmlns:wfs="http://www.opengis.net/wfs" service="WFS" version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<wfs:Update typeName="asbuilt:NOTES" xmlns:asbuilt="http://www.sfmta.com/">
<wfs:Property><wfs:Name>MEMO</wfs:Name><wfs:Value>sssss</wfs:Value></wfs:Property>
<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc"><ogc:FeatureId fid="DOCS.98997"/></ogc:Filter>
</wfs:Update></wfs:Transaction>

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport version="1.0.0"
  xsi:schemaLocation="http://www.opengis.net/ows http://localhost:80/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows">

bartvde

java.lang.NullPointerException: id
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:208)
	at org.geogit.storage.bdbje.JEObjectDatabase.exists(JEObjectDatabase.java:170)
	at org.geogit.storage.bdbje.JEStagingDatabase.get(JEStagingDatabase.java:151)
	at org.geogit.cli.porcelain.Diff$FullPrinter.print(Diff.java:185)
	at org.geogit.cli.porcelain.Diff.runInternal(Diff.java:110)
	at org.geogit.cli.AbstractCommand.run(AbstractCommand.java:32)
	at org.geogit.cli.GeogitCLI.execute(GeogitCLI.java:327)
	at org.geogit.cli.GeogitCLI.processCommand(GeogitCLI.java:263)
	at org.geogit.cli.GeogitCLI.main(GeogitCLI.java:216)

bartvde

// override to always use the proxy also on same origin requests
OpenLayers.Request.makeSameOrigin = function(url, proxy) {
    if (proxy) {
        if (typeof proxy == "function") {
            url = proxy(url);
        } else {
            url = proxy + encodeURIComponent(url);
        }
    }
    return url;

bartvde

Ext.ns("myapp.plugins");

myapp.plugins.AddLayers = Ext.extend(gxp.plugins.AddLayers, {

    ptype: "myapp_addlayers",

    addActions: function() {
        var actions = {
            iconCls: 'gxp-icon-addlayers',
            text: this.findActionMenuText,

bartvde

bart-van-den-eijndens-macbook-pro:geoserver-geonode-ext bartvde$ ./startup.sh 
CompilerOracle: exclude net/sf/saxon/event/ReceivingContentHandler.startElement
[INFO] 
NOTE: Maven is executing in offline mode. Any artifacts not already in your local
repository will be inaccessible.

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building GeoNode GeoServer Extensions
[INFO]    task-segment: [jetty:run]

bartvde

bart-van-den-eijndens-macbook-pro:geoserver-geonode-ext bartvde$ ls /var/lib/geoserver/geonode-data/
data			gwc			imports			printing2		temp			wcs.xml			wps.xml
demo			gwc-gs.xml		logging.xml		process_tmp_dir		uploader		wfs.xml
global.xml		gwc-layers		logs			security		uploader.xml.example	wms.xml
gs-data			images			printing		styles			uploads			workspaces

bartvde

* should XML class still have read and write functions, or just use goog.dom.xml functions straight up?

bartvde

diff --git a/src/script/plugins/LayerTree.js b/src/script/plugins/LayerTree.js
index 7c04c07..b53c701 100644
--- a/src/script/plugins/LayerTree.js
+++ b/src/script/plugins/LayerTree.js
@@ -223,6 +223,12 @@ gxp.plugins.LayerTree = Ext.extend(gxp.plugins.Tool, {
                 }
                 attr.listeners = {
                     rendernode: function(node) {
+                        var cb = node.getUI().checkbox;
+                        if (cb && Ext.get(cb).getAttribute('type') === 'checkbox') {

bartvde

.mapstory-grid-cls img {
    visibility: hidden !important;
    opacity: 0 !important;
    filter: alpha(opacity=0) !important;
}

bartvde

Why the future of Sencha's Ext JS is looking a lot less promising IMHO now than 5 years ago (from a geospatial developer perspective):

* the default look and feel of Ext JS is starting to become an issue (people seem fed up with the desktop like look and feel)
* do you still meet (geospatial) (core) developers enthusiastic about the technology?
* the migration from version 3 to 4 is a PITA and might not even happen for some libraries, which will give people the choice of moving on to a different technology (at the same or even less cost) [1]
* no single solution that works well on both mobile and desktop

[1] Please note that I currently have no clue what the new framework / technology is that people will migrate to most, or based on which frameworks new libraries will be created.

Also, as a developer, I have invested a lot of time and energy in this technology, so for me this is a bad thing in a way.