Technoblog

Wordpress и LiveJournal

Boris Kirzner — Fri, 28 Mar 2008 20:46:49 +0000

Куча полезной информации на сайте wiki.noljads.com.

Кросспост из Wordpress в ЖЖ.

Плагин Live+Press (домашняя страница плагина почему-то недоступна).
Я брал пропатченую версию для Wordpress 2.0 и выше вот здесь. У меня на Wordpress 2.3.3 на заработал
Плагин LiveJournal Crossposter. Работает замечательно. При желании можно запостить все старые посты из Wordpress в ЖЖ.

Question Marks When Writting in Cyrillic Language

Boris Kirzner — Thu, 27 Mar 2008 21:18:59 +0000

Переименовать в базе данных collation с “latin1_swedish_ci” на “utf8_unicode_ci” не помогло, так что открутил назад.

А вот если закомментировать в файле wp-config.php две строчки, превратив

define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');

// define('DB_CHARSET', 'utf8');
// define('DB_COLLATE', '');

то все работает нормально.

P.S. Как выяснилось, в процессе перестановки collate туда-сюда, в части старых постов почему-то заглючили отдельные символы (тире и кавычки, хотя и не везде). Пришлось подправить вручную.

The rule of thumb

Boris Kirzner — Thu, 03 Jan 2008 09:12:30 +0000

If you may configure something using Spring — never ever try to configure the same thing with Hibernate.

Sorry, Gavin.

Is the modern software getting more and more humanlike?

Boris Kirzner — Thu, 20 Dec 2007 17:10:47 +0000

The colleague of mine just got this from his IntelliJ IDEA 7.0.2:

At least it apologizes…

Good old IE bug?

Boris Kirzner — Mon, 12 Nov 2007 12:54:01 +0000

May someone explain me why the following HTML code is causing IE6 SP2 crash?

 xmlns="http://www.w3.org/1999/xhtml">


    
        
             style="table-layout:fixed">
                 width="20"/>

Bonus: CodeColorizer

Playing around with IntelliJ IDEA 7

Boris Kirzner — Tue, 30 Oct 2007 08:11:06 +0000

There is something charming in those small things IDE developers make for us.

Mainsoft makes one more step forward to developing Grasshopper community

Boris Kirzner — Wed, 11 Jul 2007 12:52:08 +0000

This week Mainsoft introduced a new source of information for all Grasshopper users: «The Grasshoppers» blog.

Although currently there is only one person actually blogging there, this is a promising step forward to developing a rich community of both Grasshopper users and developers.

By the way, it worth to take a look at full Grasshopper bloggers list.

Mono and CafePress

Boris Kirzner — Tue, 26 Jun 2007 06:36:25 +0000

Since CafePress is still lacking any kind of Mono project stuff, I decided to make one of my own.

There is nothing better than starting you morning with a good cup of Mono…

Source code inspection framework wanted

Boris Kirzner — Mon, 11 Jun 2007 08:07:27 +0000

Another example of problem similar to hashCode() mutability is an option for broken «consistent with equals» contract imposed by implementation of java.util.TreeSet while implementing java.util.Comparator.

Actually, both of these cases (as well as a numerous others) are just an evidence of much wider problem - the requirement to follow some kind of contract various infrastructure implementations rely on and lack of ability to validate/impose such a constraints using existing IDEs and tools. The basic of this is the fact no IDE vendor can track an implementations of an infrastructure libraries existing (the best support feasible to achieve is Microsoft-style solution: an inspection for .Net framework libraries embedded into Visual Studio) and thus creating inspections “by reaction” will always loose the battle.

The best way to avoid the gap between software component and the inspections is to eliminate the “broken phone” between the software developer, the documentation developer and the inspections developer. This presents an «inspection by creator» paradigm - inspections are developed in parallel with a software component (and in ideal case by the the same software developer), embedded within the component, and shipped with it.

Summarizing the basic requirements for such a framework:

Development simplicity: the inspection language should provide a way to create an inspections in declarative manner, rather than by reflection-style coding.
Lexical compliance: the inspections declaration language should be close enough to the syntax of programming language constructs inspections apply to (thus, there should coexist inspections framework implementations of the common functionality for the different platforms like Java and .Net and different per programming language extensions on the same platform like C# and VB.Net).
Multiple inspection sources: there should be and option for predefined inspections (shipped with the framework), vendor inspections (developed and shipped with particular software component) and ad-hoc custom inspections (in-house development of software component users).
Binding: there should be a way to associate the inspections with the related code structures (classes, methods, fields and properties) and ideally — keep and maintain them within the code.
Universality: inspections should be applied in «to subject» and «to object» manners (i.e. relate to the code structure associated with the inspection or to the code caller).

Upon meeting the two first requirements the last three can be easily accomplished by using existing standard mechanisms like annotations and attributes.

A new security blog around

Boris Kirzner — Tue, 05 Jun 2007 08:32:35 +0000

Imperva CTO, Amichai Shulman has launched his own security-oriented blog.

He moistly writes about enterprise security «metas», providing a lot of valuable background information resources. A must-read for any enterprise-level developer.