Back when I joined Flumotion, my team was given the choice between implementing a HTML/JavaScript or a Flex powered back office. Most developers I know would immediately turn down the later for a number of reasons:

• Platform portability, notably turning down mobile users.
• Flash plugin sometimes appears to only work properly on Windows machines, raising performance issues.
• Commitment to a proprietary technology.
• Smaller choice of developers and community resources.
• What is it with Adobe and their beloved RIA buzzword anyway? I don’t see anyone else using it!
• Obviously not as trendy as Ajax.

among others that spiced up the discussion.

But there were some particular reasons to strongly consider it in our specific case. For one, we would be working with media management, editing and playback of video, a technology closely tied with Flash at the moment, so it was really about going with Ajax with some Flex components or just Flex alone. Truth is I already had my share of pain working on projects with a heavy Ajax interface, from what our Product Manager expectations of the product, I could see those memories coming to light again. Furthermore, and more on a personal perspective, I felt tempted to give it a try and only afterward draw my conclusions. Based on that, I handed my vote out to Flex.

A few months later, I have a better shaped opinion, I had some nice surprises, as well as really disappointing ones!

I need to give credit to PyAMF for the achievement of making Python and Django integration the easiest possible. On very few occasions I had to step out of my backend bubble and worry about issues regarding frontend. The AMF protocol itself helped here, a little but nice example feature I recall is that datetimes are always passed in UTC, being the Flash plug-in responsible of handling the offset, based on the client timezone system setting. Not having to worry about details such as these was a joy and made the development process faster, allowing me to focus on backend performance. In the end I was developing a Python request handler, very far from your regular Django application, using little more than the ORM and URL handlers.

But there was a few downturns along the way. First, only the fact that code was compiled made me feel in a strange place a lot of times. Every small fix implies a full build and update on production code. I believe that hot fixing should be avoided at all cost, but it is still needed sometimes and this only made it harder, heavier and even more dangerous. Then of course there were the problems of the Flash plugin on Linux, it is really frustrating for a guy that stays 80% of his time on a console having to deal with Firefox taking away all system resources the minute you open something Flash making it virtually impossible to test without booting up a virtual machine. On AMF itself, I never quite understand for the data transferred to come “encrypted” in a weird format, it certainly didn’t made it feel safer or smaller. Also, the fact that each messaged carried a message ID and time, made it harder to smart cache responses. Although I came up with a interesting cache decorator for AMF requests that I will post in the future, I would have preferred to do it on a lower level so that I wouldn’t have to waste time decoding the AMF requests (yes, as fast as it is it’s always unneeded overhead).

But the one thing that really annoyed me was the cross domain sandbox issue. As the project architect, it was very frustrating being forced to spread several copies of a crossdomain.xml file that makes very little sense to me. To date, no one as yet succeeded in properly justifying it and proving me wrong, but I will get into this issue on a following post, don’t worry.

As a conclusion, in the context of this specific project, I believe we made the right choice. Still, I very much doubt that we will see Adobe’s “Rich Internet Applications” taking over Ajax anytime soon. The new media support on HTML5 is here to confirm that. Rare examples like Google Wave make me believe that given the right developers (I presume), it is possible to make very nice JavaScript powered applications.

That said, on a future decision, my vote would again depend on the project details and target audience, but in most cases I can think of at the moment I would have to go with Ajax.

If you have a similar experience with a different outcome, I would very much like to hear you!

Just like evry other CMS has a default theme which is the first page the user sees after installing the CMS on the server, we also needed a default theme.

A default theme must be very simple to use and has minimal requirements on the part of the end user.We prefered to have a more shiny theme instead of a totally vanilla theme.So I searched the net and found a cool theme named Glossy Blue by ndesign-studio.After some tweaking of the theme,here is what we got:

There are a lot of other themes which will be made for the project and my team is working on themes.We plan to build theme for photoblogs,video/podcasts , magazine etc…All suggestions are welcome.

По ходу разработки проекта столкнулся с необходимостью замерять чистое время загрузки скрипта с CDN средствами javascript.

Загрузка и исполнение скрипта меряется довольно легко:

function loadAndExecuteScript(url, callback){
      var script = document.getElementsByTagName('script')[0];

      script.type = "text/javascript";

      if (script.readyState){  //IE
          script.onreadystatechange = function(){
              if (script.readyState == "loaded" ||
                      script.readyState == "complete"){
                  script.onreadystatechange = null;
                  callback(Number(new Date()) - t);
              }
          };
      } else {  //Others
          script.onload = function(){
              callback(Number(new Date()) - t);
          };
      }

      var t = Number(new Date());
      script.src = url;
  }

Чтобы замерять только загрузку, приходится выкручиваться примерно вот так:

function loadScript(url, callback) {
      if (navigator.userAgent.toLowerCase().indexOf('msie') !== -1) {
          var xhr = window.ActiveXObject ? new ActiveXObject("Microsoft.XMLHTTP") : new XMLHttpRequest(),
              time = false;

          xhr.onreadystatechange = function() {
            if (xhr.readyState==1 && !time)
              time = Number(new Date());

            if (xhr.readyState==4)
              callback(Number(new Date()) - time);
          }

          xhr.open("GET", url, true);
          xhr.send(null);
      }
      else
      {
        var iframe = document.getElementsByTagName('iframe')[0],
            time = Number(new Date());

        iframe.onload = function(){
            callback(Number(new Date()) - time);
        };

        iframe.src = url;
      }
  }

Если в нормальных браузерах можно просто загрузить файл js в iframe и померять время его загрузки, то у IE, как обычно, свой путь. Увидев непривычный mime IE предложит пользователю сохранить его. Попытки загрузить JS в картинку (а также FRAME, OBJECT, и еще полдесятка тэгов) к позитивному результату также не приводит — он либо видит неожиданный mime в неожиданном месте либо не дает замерять, как в случае с BGSOUND (помните такой? ).
Я выкрутился через XHR–запрос. При попытке выполнить XHR–запрос к другому домену все браузеры обычно делают вид, как–будто ничего и не случилось (и не выполняют его), ИЕ же выдает confirmation на обращение к внешнему ресурсу. Не очень секьюрно с его стороны, но, по–крайней мере, позволяет решить мою задачу хоть как–то (без привлечения Flash через Flex).

Не исключено, впрочем, что проблема эта уже тысячу раз была кем–то решена, а я просто не смог найти решение. Впрочем, еще поищу

P.S.
А посоветуйте хороший HTTP сниффер под Mac OS X, который умеет замерять время выполнения запросов? Хочу проверить точность результатов.

Burde sove snart

Just found this link in the SDL MAME website today and thought I’d make a full post about it. It is a front end you can use on Mac OSX for SDL MAME. Makes SDL MAME easy for the rest of us folks. If you don’t feel comfortable using terminal on your Mac but you still want to use the latest version of MAME and not just the last version of MAME OSX. The Windows users aren’t the only people who can use the latest version of MAME, so can you.

MameTunes (Frontend)

One reason that I chose MythTV early on was for its ability to interface with other “satellite” frontend machines that I could place around the house in various locations where I have already installed hardwired Ethernet jacks.  Unless I wish to stream demanding high definition content, the frontend machines do not need to be equipped with expensive or modern hardware.

Here’s a case in point example.  I’ve had an old Dell Inspiron 8200 kicking around for a while that has a bad IDE controller.  It refuses to boot from the hard disk or the optical drive.  By most consequences, this machine is pretty much useless as is.  Enter PXE booting.  A BIOS setting in the 8200 allows for network booting.

I have experimented with linux and network booting in the past and have had joy using Diskless Remote Boot in Linux (DRBL) to network boot a DSL iso file from my Linux server to other computers around the house.  NFSRoot is a popular alternative and requires a dedicated box running a DHCP & TFTP servers and PXELINUX to boot a root filesystem over NFS.  My experience with this method has been frustrating and I never did get it working correctly using Debian.

I thought I would give it another shot and attempt to create a diskless frontend using the Inspiron.  I skipped all the manual configuration and opted to use a script available with the Knoppmyth distro to create a diskless frontend.  Basically the script sets up and configures the DHCP and TFTP servers on the myth backend and does all the hard work.  The Knoppmyth wiki has a good entry on how to get this going:

http://www.knoppmythwiki.org/index.php?page=DisklessFrontend

One thing that must be considered is that your frontend hardware will most likely be different from the backend hardware where the script was executed.  In my situation, from the backend, I had to reconfigure /nfsroot/dell8200/etc/X11/xorg.conf to get it play nicely with the Inspiron.  After a lot of googling and trial and error, I came up with a working xorg.conf that was compatible with the Inspiron’s 1600×1200 display.  Once changed, I had a diskless frontend working on the Inspiron with recorded programs available and live TV from the Motorola 6200 cable box.

Below is my xorg.conf for the Dell Inspiron 8200.  Note that I haven’t been successful getting an updated Nvidia driver installed for the older Nvidia graphics in the 8200.  One other issue involves navigating menus on the frontend.  When cycling through the menu using the arrow keys on the keyboard, it seems that two button clicks are being registered causing the menu to skip ahead one extra level – an annoying issue.  More time needed but it’s a good start…

# File generated by xorgconfig.

#

# Copyright 2004 The X.Org Foundation

#

# Permission is hereby granted, free of charge, to any person obtaining a

# copy of this software and associated documentation files (the “Software”),

# to deal in the Software without restriction, including without limitation

# the rights to use, copy, modify, merge, publish, distribute, sublicense,

# and/or sell copies of the Software, and to permit persons to whom the

# Software is furnished to do so, subject to the following conditions:

#

# The above copyright notice and this permission notice shall be included in

# all copies or substantial portions of the Software.

#

# THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL

# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF

# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

# SOFTWARE.

#

# Except as contained in this notice, the name of The X.Org Foundation shall

# not be used in advertising or otherwise to promote the sale, use or other

# dealings in this Software without prior written authorization from

# The X.Org Foundation.

#

# **********************************************************************

# Refer to the xorg.conf(5x) man page for details about the format of

# this file.

# **********************************************************************

# **********************************************************************

# Module section — this  section  is used to specify

# which dynamically loadable modules to load.

# **********************************************************************

#

Section “Module”

# Alps Touchpad

#    Load   “synaptics”

# This loads the DBE extension module.

Load        “dbe”  # Double buffer extension

# This loads the miscellaneous extensions module, and disables

# initialisation of the XFree86-DGA extension within that module.

SubSection  “extmod”

Option    “omit xfree86-dga”   # don’t initialise the DGA extension

EndSubSection

# This loads the font modules

#    Load        “type1″

Load        “speedo”

Load        “freetype”

#    Load        “xtt”

# This loads the GLX module

Load       “glx”

# This loads the DRI module

#    Load       “dri”

EndSection

# **********************************************************************

# Files section.  This allows default font and rgb paths to be set

# **********************************************************************

Section “Files”

# The location of the RGB database.  Note, this is the name of the

# file minus the extension (like “.txt” or “.db”).  There is normally

# no need to change the default.

RgbPath “/usr/X11R6/lib/X11/rgb”

# Multiple FontPath entries are allowed (which are concatenated together),

# as well as specifying multiple comma-separated entries in one FontPath

# command (or a combination of both methods)

#

#

FontPath   “/usr/share/fonts/misc/”

FontPath   “/usr/share/fonts/TTF/”

FontPath   “/usr/share/fonts/Type1/”

#    FontPath   “/usr/share/fonts/CID/”

FontPath   “/usr/share/fonts/75dpi/”

FontPath   “/usr/share/fonts/100dpi/”

FontPath   “/usr/share/fonts/local/”

#    FontPath   “/usr/share/fonts/Speedo/”

#    FontPath   “/usr/share/fonts/TrueType/”

#    FontPath   “/usr/share/fonts/freefont/”

# The module search path.  The default path is shown here.

#    ModulePath “/usr/X11R6/lib/modules”

EndSection

# **********************************************************************

# Input devices

# **********************************************************************

# **********************************************************************

# Core keyboard’s InputDevice section

# **********************************************************************

Section “InputDevice”

Identifier    “Keyboard1″

Driver  “kbd”

Option “AutoRepeat” “500 30″

Option “XkbRules”   “xorg”

Option “XkbModel”   “pc101″

Option “XkbLayout”  “us”

EndSection

# **********************************************************************

# Core Pointer’s InputDevice section

# **********************************************************************

Section “InputDevice”

Driver            “mouse”

Identifier  “USB-Mouse”

Option            “Device”    “/dev/input/mice”

Option            “Emulate3Buttons” “true”

Option            “ZAxisMapping”    “4 5″

EndSection

#Section “InputDevice”

#  Driver  “synaptics”

#  Identifier     “Alps”

#  Option   “Device”          “/dev/psaux”

#  Option   “Protocol”        “auto-dev”

#  Option   “LeftEdge”        “120″

#  Option   “RightEdge”       “830″

#  Option   “TopEdge”         “120″

#  Option   “BottomEdge”            “650″

#  Option   “FingerLow”       “14″

#  Option   “FingerHigh”            “15″

#  Option   “MaxTapTime”            “180″

#  Option   “MaxTapMove”            “110″

#  Option   “EmulateMidButtonTime”  “75″

#  Option   “VertScrollDelta” “20″

#  Option   “HorizScrollDelta”      “20″

#  Option   “MinSpeed”        “0.4″

#  Option   “MaxSpeed”        “0.8″

#  Option   “AccelFactor”           “0.02″

#  Option   “EdgeMotionMinSpeed”    “15″

#  Option   “EdgeMotionMaxSpeed”    “15″

#  Option   “UpDownScrolling” “1″

#  Option   “CircularScrolling”     “1″

#  Option   “CircScrollDelta” “0.1″

#  Option   “CircScrollTrigger”     “2″

#EndSection

#######################This is old touchpad

#Section “InputDevice”

#    Identifier   “Mouse1″

#    Driver “mouse”

#    Option “Protocol”    “GlidePointPS/2″

#    Option “Device”      “/dev/input/mouse0″

#    Option “Emulate3Buttons”

#EndSection

# **********************************************************************

# Monitor section

# **********************************************************************

# Any number of monitor sections may be present

Section “Monitor”

Identifier  “Monitor0″

# HorizSync is in kHz unless units are specified.

# HorizSync may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync   31.5 – 90.0

#    HorizSync    30-64         # multisync

#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies

#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.

# VertRefresh may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 59.0 – 85.0

EndSection

# **********************************************************************

# Graphics device section

# **********************************************************************

# Device configured by xorgconfig:

Section “Device”

Identifier  “Card0″

Driver      “nv”

# unsupported card

#VideoRam    65536

# Insert Clocks lines here if appropriate

EndSection

# **********************************************************************

# Screen sections

# **********************************************************************

# Any number of screen sections may be present.  Each describes

# the configuration of a single screen.  A single specific screen section

# may be specified from the X server command line with the “-screen”

# option.

Section “Screen”

Identifier  “Screen 1″

Device      “Card0″

Monitor     “Monitor0″

DefaultDepth 24

Subsection “Display”

Depth       8

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″

“640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       16

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       24

Modes       “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

EndSection

# **********************************************************************

# ServerLayout sections.

# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes

# the way multiple screens are organised.  A specific ServerLayout

# section may be specified from the X server command line with the

# “-layout” option.  In the absence of this, the first section is used.

# When now ServerLayout section is present, the first Screen section

# is used alone.

Section “ServerLayout”

# The Identifier line must be present

Identifier  “Simple Layout”

# Each Screen line specifies a Screen section name, and optionally

# the relative position of other screens.  The four names after

# primary screen name are the screens to the top, bottom, left and right

# of the primary screen.  In this example, screen 2 is located to the

# right of screen 1.

Screen “Screen 1″

# Each InputDevice line specifies an InputDevice section name and

# optionally some options to specify the way the device is to be

# used.  Those options include “CorePointer”, “CoreKeyboard” and

# “SendCoreEvents”.

#InputDevice “Mouse1″ “CorePointer”

#InputDevice “Alps” “CorePointer”

InputDevice “USB-Mouse” “AlwaysCore”

InputDevice “Keyboard1″ “CoreKeyboard”

EndSection

# Section “DRI”

#    Mode 0666

# EndSection

]]> http://hasin.wordpress.com/2009/10/01/jqueryhooking-form-submit-and-making-it-an-ajax-request/ Thu, 01 Oct 2009 16:20:51 +0000 hasin http://hasin.wordpress.com/2009/10/01/jqueryhooking-form-submit-and-making-it-an-ajax-request/ http://danielwang.wordpress.com/2009/09/09/facebook%e5%a6%82%e4%bd%95%e5%81%9a%e8%ae%be%e8%ae%a1/ Wed, 09 Sep 2009 02:36:00 +0000 wangdayu http://danielwang.wordpress.com/2009/09/09/facebook%e5%a6%82%e4%bd%95%e5%81%9a%e8%ae%be%e8%ae%a1/

Facebook的设计团队分享了他们的设计理念，以及他们是如何为2.5亿用户设计产品的。特别的是，他们强调了以下几点：

• 自己动手，亲历亲为（get your hands dirty）
• 尽早且频繁地分享设计（share early & often）
• 设计过程要从项目开始延续到结束（be there from start to finish）
• 不要爱上你的设计（don’t fall in love）

尤其重要的是确保设计师有足够的技术能力来写很多代码。
其他一些信息：

• Facebook设计团队的工作包括产品设计、市场营销、UI模式、品牌和前端开发。整个团队由15个产品设计师、5个UI工程师、5个用户体验研究员、4个交互设计师和1个内容架构师。在这个约有1000个员工的公司中，设计团队总共有25人。

• 通过撰写从前端到后端代码全部代码，将设计和技术融合进整个公司的文化。

1）设计师需要参与整个过程：从战略到发布。这不同于其他公司。

• Facebook花费了很多时间和精力来保证设计师能参与到整个产品开发流程。
• 例如：3月的主页改版发布，精简信息架构和提高页面信息的流动速度。这样的改变需要同时涉及数据结构和视觉结构。
• 在确定视觉风格后，开始写代码来制作原型。设计师通过写代码来了解真实的数据如何在页面布局中工作。
• 不断地平衡取舍，通过不断地迭代交互设计和视觉设计来做很多尝试。
• 给管理层和其他团队展示静态的产品原型并做交互演示。
• 让设计师写代码能发现细节问题并快速执行修改。

2）尽早且频繁地分享想法。了解用户能帮助实现更好的设计。

• 在Facebook没有创意总监，取而代之的是自下而上的设计团队组织架构。这对于团队能分享他们的创意至关重要。
• 开发相应工具来实现高效地分享。其中一个工具叫Pixelcloud，类似于一个带评论功能的在线图库。自从在3月发布了这个工具后，大约每天有15张创意图片通过这个网站得到分享。
• 整个工作组涵盖视觉设计和前端开发，这确保了Facebook的设计保持一贯的风格。所有的工作组都有固定的时间来给设计师提供反馈。
• 例如：隐私向导的设计。在项目立项阶段（kickoff phase），召集12个用户并向他们展示30个原型，以此来决定产品的开发方向。在产品开发阶段，再次召集相对较少的用户，向他们展示7个原型来决定具体的设计。
• 反馈是有效的。尽可能多的和早的获取反馈，这有助于节约项目时间。

3）勤动手，最重要的是理解代码是如何运行的。所有的设计师都要写一些HTML，CSS，甚至PHP。

• 模糊设计和技术的区别。设计师也能调试代码和创建快速原型。
• 设计师往往错在设计过于简洁，而工程师则错在提供过多功能。
• 理解你所为之工作的媒介类型，然后不断反思你的设计。
• 快速行动。Facebook在许多领域有很多竞争对手，而用户使用网络的习惯也在持续改变，所以快速地迭代更新产品很重要。
• 最核心的是，Facebook相信最有效的方式是快速发布产品，然后看看用户是如何使用的。
• 原型在说谎。它们通常缺乏内容和上下文联系。因此需要使用真实的内容和页面设计来理解具体的设计是如何工作的。
• 为了快速反应，我们需要快速地制作原型。例如：评论的UI首先在内部测试并修改，然后才发布给用户。新的设计打破了原有的信息流里的视觉线路。
• 设计师一般每周大约会提交40个版本的代码。

4）不要爱上你的设计。软件的生命是短暂的，它总是在变化，你需要接受这个事实。

• 你的目的是确保设计工作正常并能持续改进。
• 不要怀念今天的成就，要永远向前看。作为一个设计师，你需要预测并思考在下一年事情将发生怎样的变化。
• 在Facebook，设计存在时间最长的是首页，从2004年发布，历时18个月。
• 例如：全局导航的改版。在数月里尝试了无数的想法。甚至在昨天网站的头部又变了。
• 相比以往任何时候，我们的工作都远没有完成。
• 对大多数功能都做A/B测试。清晰地定义度量效果的标准并进行测量，但切忌不要让度量标准来驱动设计。

What ?

If you’re looking forward to optimize the frontend in your Symfony project or to introduce different CSS or JavaScript versions to each language in your application there’s a nice plugin that will help you with that. It’s called sfMinifyTSPlugin and it integrates Google’s minify library so you know it’s good stuff .

Why ?

What makes it stand out from the rest of Symfony minify plugins is the fact that you don’t need to change anything in your .htaccess file or any other server stuff, just an out-of-the-box cool plugin.

The other nice thing about it is that you can implement it either as a filter or with a helper.

The fun part is also that the authors implemented some symfony tasks to help you clear-cache and fix permissions.

The cache files names are generated with a date so you’ve got all the usefull info about it and speeds up your web application just like that.

So don’t hesitate to experiment with this cool plugin in your future Symfony applications.

If you are a front-end developer, come back and look at this skills map weekly, to see what skills you have already, and what skills you are missing.

First you need to set up the backend to allow it to communicate

You first need to stop the mythtv backend which is currently running, at the root prompt enter:

/etc/init.d/mythtv-backend stop

You can also stop the mysql server, enter:

/etc/init.d/mysql stop

You need to edit the my.cnf file and add a '#' symbol in front of the line 'bind address' to allow the front end to access the mysql database:

nano /etc/mysql/my.cnf

Nate Koechley a senior frontend engineer at YUI Team Yahoo!, he gave a presentation on “Professional Frontend Engineering.”

It covers the foundations of the discipline, some of its core ideas, and some of of its best practices. If you are looking to reset your own assumptions about “web development” or “frontend work”; If you are new to the discipline, or backend engineers transitioning to the frontend, this is also a fantastic resource to you.

Video can be watched here

Ich habe beschlossen den Fokus wieder stärker auf Web / Web 2.0 zu setzen, möchte mir aber offen halten trotzdem andere Themen zu behandeln. Wer näheres über die Ausrichtung des Blogs wissen will kann dies unter About nachlesen.

Zurzeit muss ich mich für ein Projekt intensiv mit einem meiner Web-Lieblingsthemen beschäftigen: Content-Management-Systeme (kurz CMS). CMS-Systeme dienen dazu den Inhalt (Content) von Webseiten besser zu verwalten. Dabei herrscht meist eine strikte Trennung zwischen dem sogenannten Frontend (die Website ansich, die der Webseitenbesucher sieht) und dem Backend (der Bereich in dem der Inhalt der Webseite verwaltet wird). Man kann dies durchaus mit dem Blogging System von WordPress vergleichen: Man loggt sich in das „Backend“ ein, schreibt/ändert/löscht dort einen Artikel und die Änderungen werden im “Frontend” (bei WordPress der Blog) sichtbar.

Jedoch sind CMS-Systeme um einiges Komplexer als etwas WordPress. Bei der Gestaltung von Webseiten gibt es ja individuelle Bedürfnisse, die von diesen Systemen abgedeckt werden sollen. So gibt es für die meisten CMS-Systeme sogenannte Extensions. Das sind „Plugins“, welche die Funktionalitäten des CMS-Systems erweitern. So gibt es zb. Extensions für ein News-System, Webshop… Ein CMS System muss also viele Bereiche abdecken, die über eine herkömmliche Blogging Software hinausgehen. Solche Bereiche sind zum Beispiel:

• Rechteverwaltung für Backend-Benutzer
• Mehrsprachigkeit
• Multi-Site-Management
• ausgereifte Redaktionssysteme
• Workflow-Management
• verschachtelte, dynamische Menüs
• Erweiterbarkeit mit Extensions (wie zb. Webshop)
• …

Am Markt gibt es unzählige CMS-Systeme. Die meisten Systeme sind zu bezahlen. Es gibt jedoch auch einige Open-Source CMS-Systeme, die immer ausgereifter werden und immer mehr an Bedeutung gewinnen. Ich möchte versuchen den Lesern das Thema CMS näherzubringen, indem ich ab jetzt jede Woche 1-2 wichtige Open-Source CMS-Systeme  kurz vorstelle, die ich vorher in einem Testsystem teste. Diese Artikel veröffentliche ich unter der Serie “Open-Source CMS”.

I have temporarely defected to using windows xp since I’m having a lot of problems with ubuntu’s performance.

Everything was going sweet, blazing fast performance, but since I haven’t used windows seriously in like a year and a half I kinda lost sensitivity for it. I had no antivirus whatsoever and naturally I downloaded a crack that turned out not be a crack and now windows is completely fucked. *sigh* good old times.

Surprisingly enough, the antivirus I was familiar with in windows, Avast! and AVG, all have linux versions. There’s also this linux antivirus called ClamAV.It’s a command line antivirus. Can you see my boner? Right, you know why? Because it’s not there. There’s this other thing called clamtk in the repositories which is a graphical frontend for clamav. It has a lot of talk about signatures which I suspect is maybe the antivirus database, and starts with a warning saying your distro may or may not have them preconfigured. By them I mean two configuration files. You know, the ones that end in .conf and need to be handwritten. Right. Anyway, I tried to update the signatures and what do you know?, everything is up to date. Then I notice this

Still no boner

Think I’m gonna waste another second of my life with this just because it’s released under the GPL? Think again.

To install avast!, just go to the website and download and install the deb. Don’t forget you need to register with them to have a valid key. You will find it in the accessories menu and it kinda looks like this:

Strange ain't it?

AVG you can get here. Nothing to point out, also appears in accessories. Now when you try to update it says “No permission to run whatever”. For a while there I thought they didn’t really mean permission, but turns out they do. You need to run it as root to update. Damn fine work AVG, real good. Fuckin assholes. Run sudo avggui in the console, or, alternatevely, right click the applications menu and go to “edit menus”. There, find avg, right click properties. Then on the command instead of “avggui” put “gksu avggui” and you’ll never have to think about this again. Here’s the screen.

Good thing you warn me of that shit on every single fuckin start

What’s the conclusion? I’m dying to go back to linux and get away from 2h30m worth of throughout anti virus and spyware scans, but I need hired geeks to make my laptop run sweet again.

Follow-up: Linux Format recommends BitDefender. Looks ok, probably worth a shot.

Se você atualizou seu Joomla! provalvelmente deve ter notado uma string “LAST_UPDATED2″ no frontend no lugar onde deveria aparecer a data da última atualização.

Para resolver este problema é muito simples.
Abra o arquivo pt-BR.ini na pasta language/pt-BR e adicione a string:

- LAST_UPDATED2=última atualização em %s abaixo de LAST UPDATED=última atualização

Deve aparecer assim:

LAST UPDATED=última atualização
LAST_UPDATED2=última atualização em %s