Questions, ideas for 30-Aug-2011 - “Ask the XAF and XPO Teams” webinar

In general, any idea of pre-interaction is good, i like it.

The question is what you can get from such meetings and what you can give to your customers on such "ask" webinars.

You get enough amount of issues/questions/suggestions to have general impression of potential problems

But you can rather use such meeting to give your customers a clear vision of where are XAF/XPO going to

So I would suggest you asking what kind of future (~3-6 months) do your customers want to see for XAF and what kind of options you can suggest :)

You know, waiting for silverlight-ization of web interfaces in XAF has brought so much fun to almost all of us, that sharing such clues would be really appreciated

My main question would be: what type of future you want me (as a developer) to orient to: jquery-ization of web projects (with all features supported by jqueryui.com) or silverlight-ization?

I like the idea of being able to suggest topics of discussion up front as I have watched a number of webinars of this type but have come away somewhat none the wiser in the past.

My suggestion and my biggest challenge to date, working with XAF has been a lack of understanding (on my part) of how the framework fundementals work together. In other words, when I try to do something using a view controller or something where I am tweeking the code, I stuggle to know what to change and where to update the code.

Granted I have not sat down and looked at the source code, and honestly I try to find a solution to the problem on the support website and see if anyone else has tried to do the same thing, but in general it would help if we were given a overview of how the framework fits all of these pieces together to make up the "framework".

I realise that this could be quite a task, but I certainly could do with a better understanding of the underlying mechanics of the framework.

I agree with c Pitt, it would be a great help if we had some general idea's of the lifecycles and the connection between the parts (order of events, what happens when, dependencies, generating of views, loading of data, context's of data, ...). Of course most points are here and there documented, but very fragmented without "the great picture", without coherence. Only "create a controller ...", but without description what happens under the hood. I realized already 2 small apps with XAF and still feel like a total newby.

Lately, one of my apps has shown the red cross when a user scrolled through a listview. Of course during my vacation.

Apparently something has gone wrong during the preparation of the presentation of some piece of info.

My question is: how can i quickly discover the offending row and property without trial-and-error with the debugger?

And what about some sort of automatic quarantining (and reporting) of the offending property, while keeping the view intact as much as possible?

Probably won't make it to attend the live show, but will view the recorded session. Keep up the good work and hooray for this preparatory initiative!

Willem