Friday, October 26, 2007
Wednesday, August 08, 2007
Monday, July 09, 2007
Thursday, July 05, 2007
Wednesday, June 20, 2007
Tuesday, June 12, 2007
Wednesday, May 23, 2007
Quercus is Caucho Technology's fast, open-source, 100% Java implementation of the PHP language. Quercus is a feature of Caucho Technology's Resin Application Server and is built into Resin - there is no additional download/install. Developers using Resin can launch PHP projects without having to install the standard PHP interpreter (http://www.php.net) as Quercus takes on the role of the PHP engine.
Quercus + Amfphp = Good Things :)
Wednesday, May 16, 2007
Friday, May 04, 2007
<mx:Button label="Remove" click="outerDocument.remove()"/>
Wednesday, April 25, 2007
Wednesday, April 11, 2007
I'll be releasing amfphp 2 before I retire, and I have someone here that is interested in picking up amfphp, someone I can't mention just yet but trust me that my successor will be a very talented and respected member of the community that I am sure will do an awesome job with the project.
As to which you should choose between amfphp and WebORB, it depends. Mark loves his WebORB, and I love amfphp, but they are different projects, and have different design goals, so that either one is most appropriate for different uses. The differences are subtle though, I'll be the first to admit, which is why I wasn't particularly thrilled about WebORB and SabreAmf when they first came out, as I felt it was a duplication of efforts (much like the well-publicized argument over SWX with Aral). But regardless, the effort has already been put in, so there's no use in stopping it now. I'll restate the design goals of amfphp from the homepage:
- Nothing required - PHP4/PHP5 compatible, no extensions needed
- Low footprint, lightweight, fast
- Convention over configuration (service and class mapping)
- Can be embedded into a framework (see CakeAmfphp, Seagull)
- Services are "non-specific" PHP classes that are portable to anything without code change
- Productivity tools included (service browser, code gen, profiling)
- Batteries included - XML-RPC, JSON
- Not a framework by itself (use your own)
I'd like if Mark could put up a similar statement of design goals for weborb so that users can make an informed decision.
As for the issue of the AMF extension, I've contacted Mark about it, and in theory weborb could be made compatible, and SabreAMF will be eventually (as far as I can tell). I don't think Mark wants to do it though, perhaps because of the way the serializer is implemented on their side. My personal feeling is that the serializer and unserializer in WebORB are misadapted to the realities of PHP, split into several classes for doing simple, computationally intensive things, but one could argue (and I'm sure that Mark would) that clarity of code was chosen over performance, a valid decision if it doesn't affect performance that much (and Mark is right, the 50-200ms difference won't really make a difference in most projects, but in some which have very high traffic it most definitely will, which is why the AMF extension was made).
Thanks Patrick, I'm happy to talk about the goals we have for WebORB.The vision for the product is to provide the best possibledesign/runtime platform for Flex applications and .NET/PHP/Rubybackends. Our goals include:
- - non-intrusive approach
- - ease-of-use
- - simplicity of integration
- - extensibility
- - increased developer productivity
plus all the usual suspects expected anywhere from a one person shopto a major enterprise:
- - performance
- - reliability
- - scalability
Currently we're wrapping up a new release for WebORB for .NET and assoon as it is out in production, we will port all the new features toPHP and Ruby. That said, it means all the features one would find inour .NET edition are going to be available in WebORB for PHP (andRuby). For example, take a look at WebORB Data Management for Flex(http://www.themidnightcoders.com/weborb/dotnet/wdmf-faq.shtm), thisis something Flex/PHP developers would love to have. On top of thisadd real-time messaging, remote shared object support, data push, codegenerator, performance monitor, etc.
I highly value code clarity and elegant software design and I amstrongly convinced that a product with a clear and well-thought outdesign does NOT have to suffer in the area of performance. All ourproducts share the same design. As a result, porting features orfixing bugs takes only a fraction of time than creating a newimplementation from scratch. For instance, it took us only three weeksto create the very first release of WebORB for PHP.
And lastly, when choosing an open-source product (and this is strictlymy personal opinion) I would recommend going for one backed by acommercial entity. After all, if I bet my business on it, I want tomake sure I have someone to call at 3am in the morning if things go bad.
Friday, March 16, 2007
Tuesday, February 27, 2007
Monday, February 19, 2007
Monday, February 12, 2007
Tuesday, January 30, 2007
Monday, January 29, 2007
BUG DESCRIPTION: errorString property is causing a buggy behavior, if i set an empty String to this property in order to clean a validation error for a TextInput control then its layout changes, it gets a weird black color on its border.
< mx:application><mx:textinput id="buggy"></mx:textinput><mx:button label="Show Bug" click="buggy.errorString = ''"></mx:button></mx:application>
mx_internal var origBorderColor:Number;
/** A bunch of Code Here**/
* Set the appropriate borderColor based on errorString.
* If we have an errorString, use errorColor. If we don't
* have an errorString, restore the original borderColor.
private function setBorderColorForErrorString():void
if (!_errorString _errorString.length == 0)
saveBorderColor = true;
// Remember the original border color
saveBorderColor = false;
origBorderColor = getStyle("borderColor");
var focusManager:IFocusManager = focusManager;
var focusObj:DisplayObject = focusManager ?
if (focusManager && focusManager.showFocusIndicator &&
focusObj == this)
Thursday, January 25, 2007
Friday, January 19, 2007
I thought I had a valid workaround when I stopped adding and removing the itemRenderer at Run-Time and just applied it to every column but I am still getting the error sometimes. My small example show the exact error I am getting so if anybody has any ideas please leave me a comment. The problem with learning new technologies is that you can never be sure if it is the technology or the programmer causing the problem. :)