Static folder organization. We will use release static versions so that static files for ximpia will be like /ximpia/static/0.2/css/main.css. The release number will be inserted by static django app.We now have common images like blank.png and logo.png for site logo
Model changes: Tags in applications, views. Media in applications. Categories in apps and views. Access through groups. no user access table. Link from application to group
component registry documentation and attribute control exception
Menu icons oriented to service. New menu zone service with state icons (shows current selection). Completed documentation for component register methods.
dbName resolved connection from master / slave pool is saved into context. In case you request an action, first actin db op will resolve and place in context. Other access, like redirecting to a view, etc... will use same connetion. Included dummy context class in core modules.
Fixes to menu icon design
Fix for menu items when user is not logged in and user instance is AnonymousUser. When not login, will get meni items from services that do not require authentication
view access groups
Bug fixes, menu icon urls. Back browser button will call ajax methods, without reloading page. We push url in the browser for view when accessed through ajax. Hitting F5 will call the server view. Views and actions have accessGroups. It is now possible to assign a set of user profiles to access views or execute actions. Added ximpia Group with category and tags to extend django Group model. Groups will have user groups, access groups, applications, discussion groups, etc... Category types parametrized through model Param. Category types: default app gallery, apps, views and groups. Categories: groups and apps
Component registry updates and creates registry. It does not clean by default application and all components related to application. Developer would need to call to clean methods or delete registries with django admin interface. Included SearchIndex in admin.
signup and activate user. Icon unlock to be used by Login menu item. Icons included for signup and activation confirmation view. Bug fixes
Update TemplateService to obtain templates from templates/anyDir directories. Templates can be placed at any directory. Obtaining template path searches for template name in all directories. It caches templates when debug is false. In production servers, templates are cached. Included flow data in components for site
titlebar bugs when zooming and redimension. No need for left position. sectionTitle spans 100% and titleBar alligns to center of sectionTitle. New #id_view_zone div that will keep titlebar, content and pageButtons. Will hold html from templates.
Settings -> Setting, as well as pk changes. Database settings support in visual engine. response.settings will hold settings dictionary with variables from settings table that are mustAutoload=True. Settings are now mapped to applications as well.

ximpia.common.Condition.eval (condition) will evaluate condition string like 'a ==34 && b == 98' and return true / false. Used by condition features in visual components.

ximpia.container.js : Container of components with condition support
startendtag bug fix for tags like <br/> <img .../>, etc... are now parsed correctly. Fix for padding in select boxes. Visual component container with condition support completed.
component conditions integrated into seignup. Form validation (server) bug fix showing form error in popup when form does not validate. New metadata plugin to support multiline template components inside {} Tabs, new lines, etc.. can be included to make components more readable.

Facebook integration, rerender from external renders to activate components related to external renders or binding actions in external render javascript code. Example, in facebook signup render, we set variable socialLogged to true. We have condition that when true, captcha code is not neccessary. Therefore, we need to re-render conditions and other components to update.

Method ximpia.common.Broser.putAttr() to include variable into server response saved into sessioin storage object. This allows visual javascript code to write to response so that conditions can be re-evaluated.
Login with user / password. Icons for login and signup. Change ximpiaId->username. homeLogin slug is "in"
Login / Logout. Show error when loading an url. The page displays the message included in the XpMsgException
Bug fixes. Conditions for menu items. New field condition included in menus tables ViewMenu and ServiceMenu. Condition will be evaluated for response. jsData allows attribute definition, like jsData.response.isLogin, same for setting values. Accepts dictionary assignment and attribute assignment.
core conditions. Used for menu items. Condition table with condition rules and tables ServiceMenuCondition and ViewMenuCondition for list of conditions associated with view menus and service menus. Condition actions: render, disable. This release supports action render. Condition value is boolean to render when condition is met or condition is not met