wassup bro!
kiss my shiny metal ass!

Drupal 6 node.save uses different methods for saving taxonomy for different taxonomy types.

For multiple select based taxonomy:

(php)

$nodeObj->taxonomy = array(2=>array(15,19));

(python)

nodeOb['taxonomy']['2'] = [15,19]

For tags based taxonomy:

(php)

$nodeObj->taxonomy = array(
  'tags' => array(
         2=>'military,navy'
   )
);

sto testando il mio sciocco tool che grabba immagini da flicker (via its api) e le uploada qua via xml-rpc.

Как я уже писал в предыдущем посте, попытка воспользоваться вот этим http://www.beansoftware.com/Windows-Forms-Tutorials/Using-XML-RPC-With-VB.NET.aspx примером для освоения xmlrpc под .net не увенчалась успехом – мы получили длинную противную ошибку о том, что нет такого интерфейса (см. пред. пост)

На счастье, вместе с библиотекой xmlrpc.net поставляются примеры. Попробуем поработать с ними. Примеры в C#, ну да ладно. В крайнем случае перевернем в Vb.Net

Открываем самый простой, по-видимому, пример, называемый MathApp – я думаю, что это вариация того примера, который мы только что разбирали.

Кстати, в директории “интерфейсы” я обнаружил четыре интересных интерфейса:

BloggerAPI.cs

MetaWeblogAPI.cs

и еще два.

Ну до них мы доберемся чуть позже – для начала надо посмотреть, как это вообще работает

Итак, добавляем в наш Solution MathApp  и запускаем

Как и предполагалось, это xml rpc калькулятор.

Давайте посмотрим, как это  работает, чуть поближе.

Собственно интерфейс

int Add(int a, int b);

[XmlRpcMethod("math.Subtract")]

int Subtract(int a, int b);

[XmlRpcMethod("math.Multiply")]

int Multiply(int a, int b);

[XmlRpcMethod("math.Divide")]

int Divide(int a, int b);

}

 Мы видим, что аттрибуты устанавливают, какой реально метод будет вызыван на стороне сервера

Начав работать в Liex, я быстро понял, что домены второго уровня очень быстро блокируются Яндексом.

Я зарегил порядка 20 доменов ру (тогда еще на лиексе можно было регистрировать сколько угодно поддоменов), быстро набрал ссылок по 2 цента, и думал, что вот оно – деньги будут литься рекой без особого напряга с моей стороны.

Но не тут то было. Месяца через полтора, когда эти домены и субдомены начали приносить ощутимый доход – они как то очень быстро “накрылись” и выпали из индекса Яндекса.

Я начал искать другой путь.

Было несколько вариантов.

Самый, на первый взгляд, дешевый – вместо того, чтобы регить домены “ру” по 3 бакса – можно регить info по одному баксу.

Проблема, что домены info куда хуже регистрируются.

Тут на Лиексе подоспел очередной апгрейд – внедрение поддержки XmlRpc интерфейсов.

Я до того никогда не сталкивался с этим XmlRpc, но тема меня заинтересовала, и я начал потихоньку вьезжать.

Не буду здесь подробно обсуждать xmlrpc – это тема другого блога.

Здесь нам важно, что я хочу построить настольную аппликацию, которая будет собирать инфу из фидов (то, тчо делали мои гс, “накрытые” яндексом, переводить ее с английского на русский с помощью гугл-транслятора, и гнать на нужный блог, для заполнения его контентом)

Понятно, что я рассчитываю, если из этого что то выйдет, подключить не один десяток сайтов к такой аппликации.

Joomla uses single interface that is index.php

This page has
includes/defines.php
includes/framework.php

First I like to explain about includes/defines.php

This page has constact to define the path for
(1)root
(2)administrator
(3)xmlrpc
(4)libraries
(5)plugins
(6)installation
(7)templates
(8)cache

Each folder has code for their own means as they have name.

Explanation of includes/framework.php

this page includes library/joomla/import.php

• What a stupid issue!

• What a stupid issue!

• What a stupid issue!

This is a web based client server architecture solution designed for Recycling Industry. There is a POS liked client at every collection centre. And data were sent to web based system for administration. The MyKad reader program was used to collect attendance and membership activation.

How it works? Well, member start recycling and earn points at collection centre by using MyKad. Then go to website ecommerce to redeem products and check points. Administrator using the web admin portal to monitor all collection centre and activity.

Web Front End

Web Back EndMyKad Membership Activation

Collection Centre POS

News Release

abc wong ka jue ka li

Microsoft Office Word 2007 bisa dipake buat posting blog loh. Ga percaya? Yang lo baca ini gw posting dari Word! Hahaha, amazing! *berlebihan*. Kok bisa yah? Tentu aja karena WordPress udah pasang fitur xmlrpc. Apa itu xmlrpc? Buka aja situsnya tentang xmlrpc. Yang jelas, jadi bisa posting tanpa masuk ke WordPress nya lah. Bisa lewat e-mail, atau lewat aplikasi third-party.

Gimana caranya? Caranya adalah tinggal klik Office Button > New.

Setelah itu pilih New Blog Post dan klik Create.

Kalo misalnya baru pertama kali nyoba ini, pasti disuruh Manage Account dulu.

Tinggal pilih provider blog lo. Karena gw pake WordPress, jadi gw pilih WordPress. Setelah itu setting xmlrpc nya.

Isi blog post url nya ama url blog kalian masing-masing. Terus isi username ama passwordnya. Setelah beres semua, ntar ada notifikasi bahwa akun telah di registrasi. Setelah itu ya tinggal nulis post nya deh . Dan jangan lupa masukin ke kategori tulisan lo. Caranya tinggal klik Insert Category di toolbar bagian Blog.

Pilihan Publish nya pun ada dua, yaitu Publish atau Publish as Draft. Kalo yang Publish as Draft ga akan langsung diterbitin, tapi masuk draft dulu.

Okeh, gw mau coba publish dulu. Ntar kita lanjutin bagian kekurangan dan kelebihannya.

***

[Disclaimer, tulisan di paragraf dan di bawah ini editnya pake WordPress] Okay, barusan gw posting dari Word 2007, dan berhasil dengan sangat memuaskan! Ga ada masala di HTML seperti yang gw perkirakan. Mulus abis!

Kelebihan posting dari Office 2007 adalah:

• Lebih simpel dalam editing gambar. Gw crop gambar-gambar diatas pake fitur crop yang ada di Word wichest ga ada di WordPress. Jadi enak banget buat bikin tutorial kaya postingan ini.
• Tidak memakai browser sehingga lebih cepat. Karena Word adalah aplikasi desktop, jadi proses penulisannya lebih cepat. Kadang kalo bikin posting di WordPress suka lambat, karena setiap kita ketik huruf, javascript bakalan ngecek kalimat yang kita tulis, dan proses tersebut memakan waktu.
• Auto Capitalization, jadi huruf pertama yang kita tulis otomatis berubah jadi  kapital.

Kekurangannya adalah:

• Ga bisa ngasih tag
• Ga bisa ngasih alt tag dalam image
• Ga bisa pake tag read more

Baru segitu aja kelebihan dan kekurangan yang gw temuin. Sisanya mungkin bisa ditambah ama lo sendiri di bagian comment. Jadi untuk menutupi kekurangan tersebut, mending ntar pilihnya Publish as Draft, baru di edit lagi di WordPress. Ga mau kan tulisan setengah jadi kita diliat orang, hehe. See ya!

I’ve noticed an interesting trend in this blog’s visiting statistics of late: quite a few more hits as a result of programming searches – and, specifically, Google’s Summer of Code – are referring people to my blog.  It makes sense, given that Google just completed their application period for mentoring organizations, and will be posting the list of open source companies participating in this year’s rendition on March 18 (tomorrow!), followed very quickly with the official opening of the application period for students on March 23.  Go visit the site for more details! [shameless plug]

Still, I thought I’d respect the wishes of the viewers and post about my latest undertaking over spring break: I’m well into the process of converting my WordPress Synchronizer into an official WordPress plugin.

This project started a few years back.  I’ve been running a local install of WordPress on my MacBook since May of 2006 as a little place to jot down notes, funny observations, reminders…just about anything.  Obviously, this sort of mobility makes it very easy to keep notes – I don’t even need an internet connection.  The problem arises when I want to show particular entries to…particular people.   I didn’t really have a way of doing that, aside from opening up my blog to the world, which I wasn’t really interested in doing.

Since then, I’ve come up with and implemented a few solutions that have worked fairly well up to now.  The idea behind solving this problem has generally remained the same: set up a remote blog at a static URL, implement some sort of authorization system for viewing that blog, and then selectively sync entries from my local blog to my remote blog.

Seems simple enough.  What has changed enormously is the method of implementation.  As you may gather from reading my Wiki entry, the first version of the synchronizer was very crude and extremely error-prone.  It made raw SELECT queries to the database, inserted the information into an HTML form, and POST-ed the data to a specially crafted PHP page on the other end that would parse out the data and feed it via INSERT statements into the remote blog.  Robustness wasn’t exactly what this first attempt was known for, but it worked at the time.

(Un?)fortunately, what killed this iteration was a cataclysmic hard drive failure.  Rather than go through the arduous process of inventing custom POST fields and data validation, I took another route in re-implenting this functionality: XML-RPC.  WordPress implements a large range of APIs – Blogger, MetaWeblog, MoveableType, etc – and utilizing this interface would be a great deal simpler, more secure, and much more robust.  Plus it wouldn’t require any specialized receiving functionality on the remote blog.

This worked decently well for awhile.  Unfortunately, a recent release of WordPress broke this functionality.  I had made the (apparently fatal) assumption that posts accumulate linearly-discernible post IDs; that is, a new post will have a post ID of the previous post, plus 1.  A recent upgrade of WordPress changed that, assigning unique post IDs incrementally to drafts and post edits, leaving large post ID gaps between final, published entries.  This threw my synchronizer out of alignment, as the post IDs of the remote blog no longer matched up with those of the local one, so posts started duplicating themselves remotely.

So rather than continue to wrestle with third-party woes, I decided to take it one step further: integrate it as a full-fledged WordPress plugin. This would allow use of the internal API and security checks, further alleviating detail-induced headaches and giving me a very nice sandbox to play in.  The only downside has been the learning curve for familiarizing myself with the WordPress insides, and how “actions” and “hooks” are registered with the system.

Oh yes, I spent a few hours wading through the WordPress Codex, learning how plugins are “hooked” into the system:

add_action($action_name, $callback_function);
add_filter($filter_name, $callback_function);

They function very similarly. “actions” are performed after WordPress itself takes some specific action – posting an entry, updating a page, etc – while “filters” are essentially data intermediaries that sit between the browser and the database. Yes, their names speak for themselves.

Beyond that, there was still the issue of creating menu items in the administration panel, which can be done by:

add_menu_page($pagetitle, $menutitle, $accesslevel, $file);
add_submenu_page($parent, $pagetitle, $menutitle, $accesslevel, $file);

There are also some specialized functions which are equivalent add_submenu_page() with specific existing menus (like Options, Management, or Themes) in the place of the $parent parameter.

So now I can hook functionality into WordPress through the hook callbacks, plus provide menu options in the administration panel for configuring the plugin itself. At the moment, I’ve completed the configuration setup page, and have the templates around the pages where the actual data synchronization is performed. Unfortunately, there are three major hurdles left to scale before implementation can be completed.  To wit:

-Data Representation.  Coming up with a sound way of representing synchronized entries in the database is proving diffiult.  Previously, I had simply stored the date of the most recent synchronization, and any entries with timestamps occurring afterward were prepped for remote sync’ing.  However, this doesn’t allow for selective synchronization – picking and choosing which entries are sync’ed, and which are not.
-Process Efficiency.  The easiest way to synchronize two data sets is to compare all the elements of both sets.  The problem here is that, with blogs, the data sets are collections of entries, and with time those sets will only increase in size.  This means the synchronization process will suffer progressive performance degradation.  At present, I already have over 3000 entries, and the XML-RPC package crashes when I try to retrieve every single one at once.
-Remote Rules.  What assumptions can I logically make about the remote blog?  Should I assume it won’t be touched other than when synchronizations occur?  Should I assume it’s just another regular blog that is regularly updated, but which occasionally receives entries from another blog as well?  These sorts of questions, depending on their answers, introduce a whole host of implementation concerns – most notably, how do I classify a “unique” entry when synchronizing it?

These are challenges that are helping shape plans for my content management system, which I am planning on “breaking ground” with during the summer at IBM in Raleigh (on weekends, of course!).  Since I will be at ExtremeBlue, I will not be participating in this year’s Summer of Code (much as I wish I could).  I mean, I could, but I suspect I wouldn’t have time to sleep or eat.  Perhaps next summer will feature my return to open source programming – Apache, Joomla!, Drupal, Pidgin, and WordPress are doing some pretty amazing things with which I’d love to become involved.

Apply for Google Summer of Code!  You won’t regret it.  Particularly if you apply for Joomla! and your mentor is Amy. Leslie Hawthorn and the rest of the Google team is spectacular.

As for me…time to get back to coalescent theory, computational learning theory, and tagalongs (yes, the Girl Scout cookie, buahaha).

cURL is a project name which came from  ‘Client for URLs’, originally with URL spelled in uppercase to make it obvious it deals with URLs. cURL has basically two products, a command line and a library. We are more concerned with the library as that is used with PHP for cURL calls. LibCurl is a free and easy-to-use client-side URL transfer library, supporting FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, FILE, LDAP and LDAPS. libcurl supports HTTPS certificates, HTTP POST, HTTP PUT, FTP uploading, kerberos, HTTP form based upload, proxies, cookies, user+password authentication, file transfer resume, http proxy tunneling and more…

So before I go with details on the sample program, make sure you got cURL and xmlrpc modules installed for PHP. This can be easily done by compiling the cURL and xmlrpc extensions from PHP source and linking it though the php.ini file. Once that is done make sure
you can see the modules installed using phpinfo function.

Once all looks good when cURL and xmlrpc installations have been verified, you can use the following code in PHP to do the xmlrpc calls…

//Using the XML-RPC extension to format the XML package
$request = xmlrpc_encode_request($method, array($user, $pass));
$req = curl_init($service_url);

//Close the cURL connection
curl_close($req);

//Decoding the response to be displayed
echo xmlrpc_decode($response);

–
Shoaib Mir
shoaibmir[@]gmail.com

Esse post é só um teste do uso do Google Docs para postar no AP.

Pra quem ainda não sabia… o Google Docs pode ser usado pra se editar posts e publicá-los diretamente no AP (ou qualquer outro blog do Blogger, WordPress.com ou WordPress.org, LiveJournal, etc — ou então via as APIs do Blogger, do MovableType ou do MetaWeblog).

Para configurar tudo (para o WordPress e usando um Google Docs em inglês) vá para os settings do seu Google Docs e clique em edit info… em Blog settings. Lá vc entra a informação necessária, porém, para o WP, escolha a API do MetaWeblog e digite o seu blog no seguinte formato: http://YOURSITE.wordpress.com/xmlrpc.php.

Depois, basta criar um documento normalmente, trabalhar nele à vontade e, depois de salvá-lo, quando vc já estiver satisfeito e quiser publicá-lo no blog, basta escolher publish e clicar o botão para publicar no seu blog.

Voilà

P.S.: Agora que as plataformas de serviços Web2.0 estão razoavelmente bem desenvolvidas, essa pode não parecer uma grande vantagem, afinal de contas vc pode exportar todos os seus posts de dentro do WP e tudo mais. Mas, quem quiser guardar cópias do que posta no blog, pode usar essa estratégia como uma forma de backup: seus posts ficam devidamente arquivados no Google Docs e são mantidos sincronizados com o blog (de forma que qualquer alteração ou edição no Google Docs implica na atualização do post no blog ). Mais ainda, também é possível se usar todas as ferramentas/técnicas de colaboração disponíveis no Google Docs para se editar um post com muitos autores, de modo colaborativo (com direito a controle de versão e tudo mais). Então, é um bixinho que vale a pena morder… só pra ver no que dá.

As an introduction to programming I decided to divulge into a full-fledged project, instead of working on smaller programs. Considering the lack of a good Python WordPress library I decided to combine the features of two separate programs (Vimpress [http://www.vim.org/scripts/script.php?script_id=1953] and a WordPresslib [http://www.blackbirdblog.it/programmazione/progetti/28]) and XML-RPC to create a full-scale WordPress-compatible library and client for Python.
Currently I’m converting these two functional (by that I mean function based as opposed to object oriented) libraries to one complete objective library. I’m still at the beginning steps, defining classes and functions, but it’s functional to the point of being able to post! (see previous blog entry)

I couldn’t really find as good a quote as I wanted but this does describe how I feel about apache-xmlrpc – It did what I wanted in such a convoluted way that I’ve managed to switch implementations and accomplish the same level of sucess in a few hours that have consumed a few days.

The learning process over the last few days I’m sure helped make the turnaround time possible but I’m still positive I’ve made the right decision.

I will make a note though that some of my quotes just don’t seem right coming from someone who’d been in fear of layoffs for sometime – I think they might be concerned that someone goes postal if they get laid off and any quips like the one above can probably be misconstrued.

It was a successful work day though I’m glad to have killed one path to success to get on one that’s infinitely shorter.

Une etape importante dans la realisation de notre application est la synchronisation avec differents intranets existants: cela permet en autre de faire en sorte qu’une modification sur un intranet local (basiquement un changement de numero de telephone) se repercute sur notre application, et vice et versa. Sur certains intranets locaux, un logiciel interne indique le status d’un utilisateur, c’est egalement tres plaisant de voir ce status se mettre a jour sur notre application.

Pour cela, nous avons mis en place une API permettant d’effectuer les modifications sur notre application. Cette API prend la forme d’une application Symfony recevant du XML via des requetes GET/POST (a la maniere d’un systeme REST, mais tres allege et adapte a notre application), et en fonction de ce dernier, met a jour notre base de donnees.

Nous avons fait une petite librairie PHP permettant de faciliter les echanges en generant le XML et en offrant une abstraction aux requetes CURL. Ainsi, avec un petit CRON present sur chaque intranet local, on peut facilement remettre a jour les donnees de notre application, un petit screen pour illustrer cela :

…and this is using BloGTK, which seems a little bit better.
it support tags, too!

better…