UISerializer

re: UISerializer

HumanCompiler — Sat, 07 Jun 2003 22:58:00 GMT

Interesting indeed...i think i know what the problem is...has to do with what type the Tag is...it's an Object Property, but obviously would allow you to store a string (or anything else) in it and I didn't take that into consideration...I'll have to think about the best way to approach that one as I'm sure it would happen quite often...glad you got it and thanks for making me think ;)

re: UISerializer

Mike Gunderloy — Sat, 07 Jun 2003 22:52:00 GMT

Hmmmm.....interesting. Because actually - the Tag property on the TreeView that I used to create the XML (via your SaveXML call) stores literal strings in the Tag property. These strings happen to be the names of Panel controls on the same form, but I'm not actually putting direct object references in the tag.

So, I hand-edited the XML to make the Tag System.String, and it now loads like a champ. Looks like the issue is on the Save side instead.

re: UISerializer

HumanCompiler — Sat, 07 Jun 2003 22:20:00 GMT

Mike, yah, sorry about that, it's not perfect ;) It seems not to do very well with object references and in the case of your TreeNode with the Tag with an object reference to your pnlMain, it obvious didn't do it right :P I'm still trying to figure out how to setup Object References :( So no, I have no quick fix yet for you, sorry!

I'd imagine that if there is interest in this, I can expand it to include assembly references (which would also shorten the XML, so you wouldn't have to put the full name every time :P), object references (that would point to another node or something like that so it wouldn't redefine the entire object again), etc...but for now I have some other projects I have to take care of. :-\

re: UISerializer

Mike Gunderloy — Sat, 07 Jun 2003 22:07:00 GMT

I took a look at XmlTreeView, because it would actually be useful in one of my current projects. However, it appears to be barfing on Tag properties when reloading. I'm getting "Value cannot be null" from somewhere deep inside the serialization layer. Here's a stripped-down XML that will (I think) trigger the problem:

<System.Windows.Forms.TreeNodeCollection>
<System.Windows.Forms.TreeNode>
<System.Boolean Name="Checked">False</System.Boolean>
<System.Windows.Forms.TreeNodeCollection Name="Nodes">
<System.Windows.Forms.TreeNode>
<System.Boolean Name="Checked">False</System.Boolean>
<System.Windows.Forms.TreeNodeCollection Name="Nodes">
<System.Windows.Forms.TreeNode>
<System.Boolean Name="Checked">False</System.Boolean>
<System.String Name="Text">Publish Names</System.String>
<System.Int32 Name="ImageIndex">-1</System.Int32>
<System.Int32 Name="SelectedImageIndex">-1</System.Int32>
<System.Object Name="Tag">pnlPublishNames</System.Object>
</System.Windows.Forms.TreeNode>
</System.Windows.Forms.TreeNodeCollection>
</System.Windows.Forms.TreeNode>
</System.Windows.Forms.TreeNodeCollection>
<System.String Name="Text">CopyBoy 2.0 Beta 1</System.String>
<System.Int32 Name="ImageIndex">-1</System.Int32>
<System.Int32 Name="SelectedImageIndex">-1</System.Int32>
<System.Object Name="Tag">pnlMain</System.Object>
</System.Windows.Forms.TreeNode>
</System.Windows.Forms.TreeNodeCollection>

I'll pound on this a bit myself, but figured you might have a quick "aha" fix :)

re: UISerializer

HumanCompiler — Sat, 07 Jun 2003 19:23:00 GMT

Cool, Don! There's a lot more that could be done with it, but I hope you enjoy what's there! ;)

JosepheCooney, yah, your brother's project sounds really cool! I'll have to check it out. That thought (in one way or another) was crossing my mind too, as in, "why not just send entire apps over the net this way, so you don't have to deal with the security hassles of 'no touch' deployment'"...thanks for the link! :)

oh and btw, you can serialize more than just the UI (at least I think), as it's just using reflection and grabbing anything public, but it does have to be a project that has access to WindowsForms though, because it uses the Design Time support to figure out what should and shouldn't be serialized.

re: UISerializer

JosephCooney — Sat, 07 Jun 2003 19:13:00 GMT

My brother Dominic is working on a mobilization framework for .NET applications as part of his Ph.D. Instead of serializing the UI you can serialize a whole thread and send it to another computer (providing they have the right stuff installed) where it will re-hydrate and continue running. He has a "mobliezed" version of notepad which I have seen him enter text into on his lap top, drag and drop it on his iPaq in network neighbourhood, where it appears and continues running with the same stuff on the screen. Obviously it is not limited to serializing UI but that is one of the coolest ways to demo it. Check it out here if you're interested...(appologies to my brother if I've in any way mis-represented his cool Ph.D project).

http://www.dcooney.com/mobile.html

re: UISerializer

DonXML — Sat, 07 Jun 2003 15:23:00 GMT

Erik,
Cool. I've downloaded it, and will be playing with it over the weekend.

DonXML