by jcompagner » Wed Jan 02, 2013 1:02 pm
I don't think that if we would reproduce a un-minified war that you would be able to debug it better.
Because that is then java->javascript code of the servoy code itself. That is not really useful at all for you. Don't think that will make debugging a bit easier (you also don't debug through servoy java code in smart/web client)
I guess the problem is more that your servoy js code is not directly a function in scripting but a just a String (solution.js file) that is evalled .. Maybe we could improve this a bit, that we don't eval the exported js function you define in the developer. but we do eval the solution model generated stuff. (we had this before until we implemented also the solution model for the mobile then we had to create the form or global scopes differently)
Make a case for this if you want so that debugging your own javascript functions, defined in the developer, in the browser will be easier. I hope we can come with a nicer solution for this, but we need to look if this is really possible.
Your specific case, property of a relation that comes up as an undefined error, we already can support a bit better.
Do create a case for this, so that we will check, if you ask for a relation (that is defined as a relation in the mobile solution) but you didn't export the data in the service solution you will be warned before this error happens.
Johan Compagner
Servoy