Could anyone tell me the events that are fired during a Silverlight control's lifecycle please?
For instance in ASP.NET you would have PreInit, Init, PreLoad, Load, etc.
After much Googling I came across the following. It's not brilliant, and it appplies to Silverlight 2, but it's a start...
http://www.dotblogs.com.tw/kan/archive/2009/03/03/7351.aspx
This is a much better control lifecycle description.
Related
I have been working quite sometime with Blackberry application development but customizing UI and components is something am not very familiar with. I understand that the sublayout, paint, getpreferredWidth, getpreferredHeight methods are to be overridden to customize layouts and components. But still the idea is very vague to me. I am still not able to confidently proceed with the development of UI using these concepts. Can someone explain to me the basics of this? I would like to have a clear understanding from the experts out there.
Best thing to do is look at the source code to the Advanced UI Components that RIM provides, in conjunction with the API documentation.
I'm new to MVC but am working hard to find my way through it. I'm currently at the point where I know enough to be dangerous, but not quite enough to actually do anything useful.
I'm building a site which I'd like to be very flexibly "skinable". It could also end up quite large, so I really want to use areas.
I found this great article about skinning.
and this great thread on writing a custom view engine that is "area aware".
I'm thinking of throwing myself in the deep end and seeing if I can build a custom view engine that is both area aware and has theme support. I guess that it's kind of a hybrid of these two articles.
Before I start - and also, more to the point - "before I start, lose hair, finish, implement and build my massive app on it", can anyone comment if they think that this is a good idea?
I'm just wondering if there's a library out there that already does this, or a much easier way that I'm completely missing...
Any suggestions most welcome!!
Thanks in advance,
Z
If you're going to do something, it's generally a good idea to have a good reason to do it.
If you're objective is to enable themes, the easiest way to do this is to set the theme in viewData and have a custom HtmlHelper include the necessary .css and .js references based on the viewdata's theme key.
For a more robust solution, Telerik has an open source extension of ASP.NET MVC, which is very useful for developing your UI and enables theme-functionality : http://demos.telerik.com/aspnet-mvc . Using their starter kit would probably save you a good bit of time.
I am working with a new project which is really complex and is written with MVC 1.0 and heavy jQuery implemenation. Since there is not a lot of documentation it is almost impossible to trace the flow of commands in the entire application. So I am trying to debug it and learn the implementation, but with jquery implementaion, it gets harder to understand the flow of commands and which function is called at what moment.
I was wonderng if there is a method to find out where the cursor is in the code at any given moment in time? Step into amd breakpoints has not been working for me that great. Is there any other tricks I might not be aware of to debug a MCV app?
I really appreciate your help.
Pause your debugging session
anytime.
Select the correct thread (using the 'Thread' dropdown)
Use Show next statement
I realise that it is fairly easy to query performance counters in code and display these on an ASPX page but does anyone know if a product already exists which is basically a web version of PerfMon - free or otherwise?
many thanks
Marcus
HP SiteScope can do this.
I'm thinking of experimenting with alternative View Engines for ASP.NET MVC, and would like to know what other people are using.
Please let me know 1) Which View Engine you use, and 2) Why.
The standard 'web-forms' view engine is of course a valid answer, but please say so only if you have decided to use it for a reason, not just 'Becuase I can't be bothered to change it' ;)
Thank you!
Most of the time, I use a 'standard' view engine - however, since MVC is so extensible, what happens is that sometimes we only need to inherit from it, override some little bit of functionality, and then plug it back in.
In addition, having looking at the Spark view engine, their particular style of making view code didn't gel well with me, but that's no fault of theirs - just different strokes for different folks.
The standard view engine has the most functionality in terms of both Visual Studio compatibility and ASP.NET MVC compatibility, but it's the least readable.
Spark view engine is usually preferred by most people, mainly because it has a nicer view, and it's mostly "compatible" with the designer crews, who only know how to create HTML pages. It also has some C# IntelliSense support for Visual Studio 2008. If you need to give out the view to designers Spark is the best choice.
Coming from the rails/merb world I actually prefer NHaml, because it's very expressive, and DRY, although it's not really "designer friendly". It also has some C# IntelliSense support too. (N)Haml is a view engine that people either hate or love because it's terse nature.
As far as i know these are the only three view engines that have support for C# Intellisense (and only for VS 2008, although work to get them run under VS 2010 is in progress), which can help a lot, and which usually people who want to switch from the "standard" view engine consider a "must-have".
Don't forget however that you can mix view engines in a project, so you can use the standard view engine where you need it's functionality but switch to spark/nhaml/anything else if they suit your needs better.