bartvde

 	  	  
Published: 08:59 CEST 04-07-2013 /Thomson Reuters /Source: Imtech /XAMS: IM /ISIN: NL0006055329

Royal Imtech lanceert volledig gegarandeerde 4 voor 1 claimemissie van circa EUR 500 miljoen

NIET BESTEMD OM TE WORDEN VRIJGEGEVEN, VERSPREID OF GEPUBLICEERD
IN DE VERENIGDE STATEN, AUSTRALIE, CANADA OF JAPAN 
 
Claimemissie belangrijke volgende stap in financiële herstructurering van Royal Imtech

bartvde

PID   COMMAND      %CPU  TIME     #TH   #WQ  #PORT #MREG RPRVT  RSHRD  RSIZE  VPRVT  VSIZE  PGRP PPID STATE    UID  FAULTS    COW       MSGSENT   MSGRECV   SYSBSD     SYSMACH    CSW       PAGEINS
63-   kav          92.7  12:20:32 112/2 1    255+  1272+ 507M+  13M    546M+  680M+  1349M+ 63   1    running  0    48201019+ 13494     1652595+  837500+   54137032+  9314027+   79458816+ 6050

bartvde

      '_spatial': function(node, obj, func) {
        var args = [], container = {};
        this.readChildNodes(node, container);
        if (goog.isDef(container.geometry)) {
          args.push(this.gml_.createGeometry(container));
        } else {
          args = container.bounds;
        }
        if (goog.isDef(container['distance'])) {
          args.push(container['distance']);

bartvde

Ext.ns('gxp.plugins');

gxp.plugins.MFGrid = Ext.extend(gxp.plugins.Tool, {

    ptype: "gxp_mfgrid",

    init: function(target) {
        this.outputAction = 0;
        this.createStore();
        this.outputConfig = {width: 350, height: 300};

bartvde

    // create a new attributes store
    store = new GeoExt.data.FeatureStore({
        fields: [
            {name: 'geometry'},
            {name: 'name', type: 'string'},
            {name: 'type', type: 'string'}
        ],
        proxy: new GeoExt.data.ProtocolProxy({
            protocol: new OpenLayers.Protocol.HTTP({
                url: "http://demo.mapfish.org/mapfishsample/2.2/wsgi/pois",

bartvde

Met uw login en wachtwoord kunt u vervolgens inloggen en handelen zodra uw storting binnen is.

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.

bartvde

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

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

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