DHTMLX Ajax Toolkit has been extended with a new UI component – dhtmlxFolders . This component provides flexible and effective solution for creating Ajax-enabled file/image browsers, product catalogs, web-shop interfaces, etc.
St. Petersburg, Russia, February 25, 2008 - DHTMLX has released dhtmlxFolders , Ajax/DHTML component that displays numerous objects with the same data structure in different views and layouts. The component can be used as a basis for file/image browsers, product catalogs, search engine results or any kind of informational resources.
dhtmlxFolders can be easily implemented in any Ajax-based website/application. Rich and robust JavaScript API gives developers wide possibilities to customize component’s view and behaviour. The component’s appearance can be defined through XSL or JavaScript and changed on the fly.
Thursday, 28 February 2008
dhtmlxFolders – Ajax Solution for Creating File Browser or Items Explorer Interfaces
PartCover: New Open Source Code Coverage Tool
Last September Peter Waldschmidt, the creator of NCover, made NCover a commercial product. NCover was a free tool and had become a popular choice, especially among open source projects. Gnoso, Peter’s company, has continued to embrace the open source community by providing free licenses to open source projects. This has not been enough for some open source projects. In response PartCover has be receiving increased attention.
PartCover is an open source code coverage tool for .Net very similar to NCover. It includes a console application, GUI coverage browser, and xsl transforms for use in CC.Net.
SharpDevelop, an open source IDE for .NET, has switched to PartCover as of their Beta 1 for version 3.0.
ASF Grants Synapse Separate, Top-Level Project Billing
Even if the announcement that Apache Software Foundation (ASF) granted Synapse separate, top-level project billing last week didn't generate major waves of uproar of reaction and commentary, it remains a significant move to the overall state of a burgeoning open source SOA arena. Initially, after first catching wind of Synapse in early spring of last year, I was thrown off slightly by some of the divergent descriptions/understandings of the effort that were floating around the web and as is the case with incubated open source projects it was a rapidly changing code base looking to grow in a more concisely defined direction over time. Since this is normally the case with early stage open source efforts especially those that set out to tackle broad scale areas of competency like SOA...
...provided three main functions: managing virtualized connections, service management and message transformation. Previously, it was useful for exchanges made through SOAP-based Web services where management of the exchanges were available through the WS-* protocols. Now support has been extended to numerous open standards such as HTTP, SOAP, FTP, SMTP, XML, XSLT, XPath, JMS, Web Services Security (WSS), Web Services Reliable Messaging (WS-RM), and more.
