I just moved to a new company. And they use this seemingly cool ORM: IdeaBlade, will let the developer do Linq2SQL on the client (Silverlight) side.
There are performance issue though...
Haven't work with real data yet (it's big) but just the ORM seems to have some down time (due to initialization and query parsing)
I wonder did anyone here used IdeaBlade (DevForce)? is it good?
How does it compare to WCFDataService?
I am facing an issue i.e., i created a login form and main window (after login, if login sucessfull). I implemented the application in mvvm pattern. I don't know how to call the main window after sucessful login using mvvm. Can anybody help me out from here.
I would like to present in a flat area a tree like view.
Each item would be a non-movable panel with its own controls. Each child will have connected with a line (Also selectable). On top of it, some childs are going to have multiple parrents. The closest that i have seen to compare is code map in VS2012 Update 2.
Example: Panel 1 and 2 are parents of panel 3
I would like some pointers where to go, or if there is a custom control as long as it is free and can redistribute with or without source code. When i finish my personal project i will release source. As i am hobbiest programmer, my understanding on WPF is limited, so thank you for your time and patience.
Thanks for suggestion, but i didn't knew what to search. I am currently reading a WPF book and in a book i saw word diagram in it. At that moment i found WPF Diagram Designer article that is perfect. Since my native language is not english i could not remeber word, that would help me search on google
Not quite sure an "e.Handled = true" concept in messenger makes sense since the messages are going to be propogated in a random/arbitrary/indeterminate order. Its really up to the subscriber to determine if the message should be handled. Your "e.Handled = true" concept might just mean that somebody handled it and its up to the subcriber to play nice and check the flag. A lot of messenger implementations fire & forget the notifications in async mode too. Then it makes even less sense.
Now that I'v had a few days to thin about it, the subscriber should pass in it's id to the control Init. Could be a PK or a guid. If there are 3 tabs open, each instance of control would be intiailized with a different id.
Then, each subsequent call would have that Id passed with it. Then control's methods would only act if the Id passed in the message matches that sent in the 'init' method.
That's about how I would do it - although pass a reference to the object rather than just an Id - you then have the advantage of being able to access the object in question from your consumer.
Send Message - "I've just updated this Customer"
Receive Message - do nothing - not interested in this customer
Receive Message - update my list of customers as the value in the CustomerType property matches my filtering criteria.
Receive Message - I'm displaying this actual customer - so I'll refresh myself
the 'handled' approach can be useful; my example is selecting a customer to edit from a list.
If an existing customer edit view is out there, in a 'clean' state, it can take over the job of editing the selected customer - but you don't want another view to do the same thing too!
I have a tab control with two tabs in it,in each tab i have text boxes, the data of the text boxes is being validated using the IDataErrorInfo interface.
If there is an invalid data i am rendering a red ellipsis and a tool tip box using this XAML code:
<!--The template which renders a TextBox when it contains invalid data.--><ControlTemplatex:Key="TextBoxErrorTemplate"><DockPanel><EllipseDockPanel.Dock="Right"Margin="2,0"ToolTip="Contains invalid data"Width="10"Height="10"><Ellipse.Fill><LinearGradientBrush><GradientStopColor="#11FF1111"Offset="0"/><GradientStopColor="#FFFF0000"Offset="1"/></LinearGradientBrush></Ellipse.Fill></Ellipse><!--This placeholder occupies where the TextBox will appear.--><AdornedElementPlaceholder/></DockPanel></ControlTemplate>
Text box XAML:
<!--ID text box--><TextBox.Text><BindingPath="ID"UpdateSourceTrigger="PropertyChanged"><Binding.ValidationRules><DataErrorValidationRule/></Binding.ValidationRules></Binding></TextBox.Text></TextBox>
The problem is when i go to another tab and then come back again the red Ellipses are disappear.
On Tab selection change event, give the datacontext to the textboxes.
Say for example for first tab, you have 3 textboxes in a grid and you provide the class object to be bound as datacontext of the grid; when you select that tab, again give the same object as datacontext to the grid.