extjs

anonymous asked:

Traits in all inferior functions.

NOTE: These are really only if these functions are underdeveloped. A lot of the time, these functions aren’t this underdeveloped.

Inferior Ni (ESxP): Poor long-term planning skills, expressing negative feelings towards the future, may have difficulty seeing people’s true intentions

Inferior Ne (ISxJ): Have difficulty seeing unpredictable results, may be too “by the book”, may express negativity towards possible outcomes.

Inferior Si (ENxP): May appear “scatterbrained”, may have difficulty learning from mistakes, can express distrust towards authority and traditional methods.

Inferior Se (INxJ): Might seem somewhat detached from reality, can have difficulty living in the moment and acting on impulse, “head in the clouds”

Inferior Fi (ExTJ): might have difficulty following own personal morals and beliefs, may have trouble dealing with inner emotions, can seem harsh

Inferior Fe (IxTP): might have difficulty following “social norms”, may be unable to understand other people’s emotions, can come across as blunt

Inferior Ti (ExFJ): may have difficulty making decisions based on personal systems, could have trouble analyzing/ using and developing inner logic.

Inferior Te (IxFP): may have problems accepting external facts, can seem to have unrealistic standards/ being organized and rational.

Spring 3,extjs 4,and give it a rest.

Im currently working on a project that utilize the following technologies-restful services using the spring 3 framework and extjs 4 for RIA components.stay tune for more postings on the implementation.

vimeo

I spent a lot of time making these folders work at Fuser. I had to write a lot of custom code to handle the folder tree because the performance for ExtJS tree was too slow and it did not support all the features we needed. Who has a better job the UX, QA, or developers? On this feature, I think all of us lost. It was hard work all around trying to build something that was so custom and did a lot of complex things never seen on the web at the time it was developed.

We estimate that using Sencha products has saved us at least 25% in development time. Plus, the professional documentation and strong, passionate community have helped us to get up to speed quickly.
—  Jean-Damien Hobe, President and founder, TodoBravo
vimeo

Theming ExtJS 4

Really impressive video of extjs4 theming. Including technologies like, css3, sass, compass.

sencha.com
Sencha News: June Edition

The latest edition of Sencha News features six full-length articles, tailored for web designers, Sencha developers, and beginning web app developers. Read about architecting your Ext JS 4 app, replacing Flash with CSS3 Animations, and get a sneak peek of Ext GWT 3.

Note: Newsletter subscribers receive articles before anyone else, so make sure you’re subscribed at the bottom of sencha.com

Proyecto Inicial para sencha ExtJs 6.0

La creacion de un proyecto de Sencha ExtJS 6 usando Sencha CMD es bastante simple. Hacemos la generacion de un proyecto de una forma relativamente sencilla como es usar el comando: >> sencha -sd /ruta_a_framework_6.0/ generate app  app03 app03   Una vez ejecutado el comando de generacion de proyecto nos genera nuestro proyecto que puede […]

https://javascriptx.wordpress.com/2015/07/12/proyecto-in…

View On WordPress

Developer Cheat Sheets

Web Development Cheat Sheets

HTML cheat sheet:
http://floele.flyspray.org/htmlcheatsheet.pdf

CSS cheat sheet:
http://www.addedbytes.com/cheat-sheets/css-cheat-sheet/

PHP cheat sheet:
http://www.addedbytes.com/cheat-sheets/php-cheat-sheet/

Ruby on Rails cheat sheet:
http://www.addedbytes.com/cheat-sheets/ruby-on-rails-cheat-sheet/

MySQL cheat sheet:
http://www.addedbytes.com/cheat-sheets/mysql-cheat-sheet/

Regular Expressions cheat sheet:
http://www.addedbytes.com/cheat-sheets/regular-expressions-cheat-sheet/

Search Engine Optimisation (SEO) cheat sheet:
http://www.seomoz.org/blog/the-web-developers-seo-cheat-sheet

JavaScript & JavaScript Framework Cheat Sheets

JavaScript cheat sheet:
http://www.addedbytes.com/cheat-sheets/javascript-cheat-sheet/

jQuery cheat sheet:
http://www.gscottolson.com/weblog/2008/01/11/jquery-cheat-sheet/

jQueryUI Icon Reference cheat sheet:
http://www.petefreitag.com/cheatsheets/jqueryui-icons/

MooTools cheat sheet:
http://mediavrog.net/blog/2008/06/11/mootools/mootools-12-cheat-sheet/

Prototype cheat sheet:
http://thinkweb2.com/projects/prototype/prototype-1602-cheat-sheet/

Scriptaculous cheat sheet:
http://www.slash7.com/articles/2006/04/22/scriptaculous-cheat-sheet-1

extJs cheat sheet:
http://huseyint.com/projeler/extjs-cheat-sheets/

YUI cheat sheet:
http://developer.yahoo.com/yui/#cheatsheets

Also…

Wordpress Help Sheet
http://www.quicklycode.com/wp-content/files/wordpress_helpsheet.jpg

For some time now I´m thinking about where to post my code snippets, technical hints and … All that stuff that is not worth a complete blog or that does not have the quality for an official blog at my homepage or elsewhere but that contains more than 140 characters (Twitter restriction).

Till today I did this in local files, wikis at my personal server, google sites, …

From now on I will post those things here at tumblr.

The areas I will post about will be

If you are interested in these topics stay tuned and follow me.

validation in Ext Js

參考 API 文件

form>field>Text >  getErrors method  check this out  

驗證分為3個階段:

  1. 第一階段  (驗證過或不過都不會中斷驗證程序)
    檢查 validator屬性 的自訂function

  2. 第二階段 (只要驗證不過 就不會繼續往下檢查)
    檢查 Basic Validation  也就是 allowBlank  minLength  maxLength  這三個屬性
     
  3. 第三階段
    才是檢查 VTypes  的部分  用來檢查這個欄位是否填寫正確

感想:

所以我的感覺是說 對於設計這個Ext Js的人來說,

Vtype在他的想法裡面 應該只是用來檢查 欄位到底填的對不對,

欄位為空的事情檢查Vtype 之前該先做的事,

因為欄位如果空的驗不過,在這個理論下就不用檢查填的對不對了。

然後就是為了符合一些其它的需求(例如說我們現在想做的功能)

提供了一個自訂validator 的屬性, 讓基本驗證 和Vtype驗證之前就先檢查

Theming extjs in Netzke

How to use Sass und Compass within the Netzke-Framework inside RubyOnRails.

Sass und Compass with Netzke Install Sass and the Compass gem:

sudo gem install sass
sudo gem install compass

Initialize Compass within the current Rails-project:

compass init rails .

Include the gem to your current gemfile:

gem “compass”, “>= 0.11.1”

Modify the extpath in the sass-config File to

$ext_path = “../../”

Go to the public/extjs - Folder:

compass compile resources/sass

Create new Themes

Inside extjs/resources copy “sass” to “your-theme”.
You can delete all files here, except config.rb, ext-all.scss and a new create file:

ext-all-“your-theme”.scss.

If you don’t know how to handle modifications, look at the others files, before you delete them (you can also keep them if you like).

Again you can create the pure css-files with:

compass compile resources/sass

Now you can use the new created theme in your application with the following addition:

<%= netzke_init :ext_theme => :your-theme %>

Creating Stylesheets is a continues process. To fasten the testing of your current changes, you can say compass to look automatically for updates and creating the css.

compass watch resources/sass

References
http://dev.sencha.com/deploy/ext-4.0.0/docs/guide/theming.html
http://compass-style.org/install/

Despliegue de Proyecto de Login de Usuario basado en Sencha ExtJs 6: Servidor Remoto (PHP)

Despliegue de Proyecto de Login de Usuario basado en Sencha ExtJs 6: Servidor Remoto (PHP)

El uso de un servidor se ha vuelto una necesidad en este campo hay muchos servidores que aplican como buena opcion segun cada lenguaje de programacion, pues segun cada criterio uno debe escoger la mejor opcion posible para mi en mi particular forma de pensar creo que heroku es muy bueno pues soporta una buena variedad de lenguajes de programacion y ademas es un servidor cloud muy potente.

Ver…

View On WordPress

Automating Ext Model Creation from Sequelize Model Definitions

In one of the applications I’m building I’m using Node.js, Express, Sequelize and Ext. All are fantastic tools but not necessarily meant to work together in perfect harmony (specifically Sequelize and Ext.)

Because I’m lazy I wanted my Node.js application to provide some standard boilerplate code for me; rather than writing it out myself long-hand. Once such case is in the Ext.data.Model definitions required for the client-side of the application.

Models are subject to change, a lot, and so it’s actually kind of not a stupid idea to have as much of the low-hanging fruit “just taken care of” as possible. This keeps your front-end application in sync with your backend and you could easily extend this to produce static files if you wanted to reduce processing overhead (although it’s not going to be much anyway.)

The way that Ext autoloads model classes for your application is pretty simple and it’s easy to hack once you know that it will convert:

MyApp.model.User

Into something like (a web request for):

http://server.com/app/model/User.js

From here, using an Express router (I stuck mine in the routes/index.js file of a default Express bundle, something like:

var router = require("express").router;

router.route("/app/model/:modelname")
    .get(
        function (req, res) {
            "use strict";
            var modelName = req.params.modelname.replace(/\.js/, "");
            res.send(router.app.tools.buildExtModel(modelName));
        }
    );

router.init = function (_app) {
    router.app = _app;
}

module.exports = router;

The above takes the url from the Ext loader, drops the .js bit and then calls a subordinate function which actually builds up the model definition from the Sequelize class. *These functions are buried in a “tools” class that’s global to the application.

Produce an Ext.data.Model Def.

buildExtModel:
    function (forModelString) {
        var model = tools.app.db[forModelString],
            fieldDefs = tools.clientCompatibleFieldDefs(model),
            output = "";

        output += "Ext.define(\"MyApp.model." + forModelString + "\",\n";
        output += JSON.stringify(
            {
                "extend": "Ext.data.Model",
                "fields": fieldDefs
            }
        ) + "\n";
        output += (");");

        return output;
    },

Build a List of Fields

This builds a field list that is compatible with Ext. Sadly our naming convention probably won’t support additional platforms but goddamn if I’m gonna write all this boilerplate by hand! You could conceivably implement support for any kind of output model definition, Objective-C classes, Java classes, etc.

clientCompatibleFieldDefs:
    function (model) {
        var fieldDefs = [{"name": "id", "type": "int"}],
            fieldKey,
            field,
            fieldType;

        for (fieldKey in model.rawAttributes) {
            if (model.rawAttributes.hasOwnProperty(fieldKey)) {
                if (fieldKey !== "id") {
                    field = model.rawAttributes[fieldKey];
                    fieldDefs.push(
                        {
                            "name": fieldKey,
                            "type": tools.sequelizeToExtFieldType(field)
                        }
                    );
                }
            }
        }

        return fieldDefs;
    },

Convert Field Types

This converts between Sequelize and Ext.data.Model field formats. If a field type is not represented it (the type) will not be included in the output and Ext will infer a type of “string” for safety. You could build this up to support whatever other field types your specific instance employs.

Of note here, Sequelize doesn’t define all models the same. Sometimes field types are objects, sometimes they are functions and other times they are just strings. In my particular case I’m only handling the “private” _typeName and the string form of “type.”

sequelizeToExtFieldType:
    function (field) {
        var fieldType,
            fieldMatch = {
                "INTEGER": "int",
                "STRING": "string",
                "VARCHAR": "string",
                "DATETIME": "date"
            };

        if (field.hasOwnProperty("_typeName")) {
            fieldType = fieldMatch[field._typeName];
        } else if (field.hasOwnProperty("type") &&
            typeof(field.type) === "string") {
            fieldType = fieldMatch[field.type];
        }

        return fieldType;
    }

What Next?

After I built this it occurred to me that it would be much better to use text-based templates (like Mustache or Jade) to build up the output. I started looking at using Jade but unfortunately it trends heavily toward making HTML output which you just end up fighting with. Mustache would probably work if you could iterate easily and likely I’ll move in that direction when I have more time. Right now I supply both my Ext.data.Model and Ext.data.Store class definitions using this pattern. Hope you find it useful, let me know.