Hello,
The most common problems that we encounter during SmartFrog development are
parse-time problems, particularly failed schema predicates. In a large enough
system of nested components, the source of the error is often hard to trace,
going on SmartFrog error output alone (why can't this attribute be resolved?) I
wonder if it is possible to obtain some additional information to help with
parse-time debugging, either by changing some system setting, or by adding
something to component scripts?
Dmitry Epstein | Developer
Allied Testing
T +7 495 544 4869 Ext 417
M +7 926 215 7336
www.alliedtesting.com
We Deliver Quality.
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Smartfrog-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartfrog-users
