I posted this in the Interface Help forums but it was probably the wrong place, then I saw this forum and thought it'd be best here.

I have been developing an addon for quite some time now and became frustrated with creating the FrameXML file for it. I had an app written in VB.Net that helped me do quick and simple things and thought I'd move it over to Silverlight and share it.

Because it's written in Silverlight 3, it's not an executable and you can be rest assured that it is completely harmless. (Silverlight does not have access to anything on your computer)

UI XML Editor
*Works best in Firefox and IE 2008. Doesn't not work in 64bit browsers.

It basically writes the XML code as well as the Lua Code for the widgets as you draw the components on the screen. It's very simple and straight forward right now because I use it mainly for laying out my Options panels and etc. It's good for positioning components and setting up the hierarchy of them.

It allows for easy editing of a widgets properties and scripts when they are selected.

It's good if you want to get a quick and dirty design for a frame and copy and paste the code into your xml as well.

To use it:
-Click the Frame component in the ToolBox. Click the upper left corner of the frame in the drawing area and drag down and to the left to draw it. Other components can be added to the frame by selecting them and placing them inside the frame.

-Press escape to hide the crosshairs and use the hand to move components around.

-Drag components to the trash can to delete them.

-Selected components are highlighted in blue.

-Selecting a component will highlight it's respective code in the xml. (A bit buggy right now, sometimes have to click the FrameXML area as least ones to get it to start working)

There are still a lot of little bugs to work out, but I need a little help finding them. I got a lot to add and a lot of ideas to improve it.

Try it out and let me know what you think! If you would like to use it, please do so and PM any bugs you might come across. Thanks!

I appreciate Xrystal. There are so many little things that can go wrong in Lua code, such as a misplaced quotation mark (one i found a bit earlier) that can cause it to completely not work. They are very easy to fix, I just need help finding all of them.

I plan on this app evolving into a full fledged Addon IDE. In a couple weeks, it should be able to all widgets, present templates for each, allow for Lua function and variable coding, intellisense, and an Object Library of the FrameXML.

I've been working on it for 3 days now, and Silverlight is just amazing. I used to program in Flash, but Silverlight is made for online apps. If you have any suggestions or critiques, please inform me. Constructive criticism is what makes applications well rounded and useful to many people.

I had a quick play with it and its possible that I didn't spot how to stop it from happening but once I clicked on an object to draw I couldn't stop drawing.

Eg. I made a frame, scrollframe etc then clicked on button and made a button or two then when I tried to select one to move it around I couldn't, it just made another button parented to the one I had clicked on. I didn't test to see if pressing escape releases the drawing stamp but thought I would mention it just in case.

The way I code is a lot different but I will say from the code it generates it will definitely speed up my more complex addons.

As to Silverlight programming. I was wondering what that was all about, now I know

Xrystal, sorry but I forgot to mention that you need to press "Escape" to return to the normal cursor in which you can Drag/Select other widgets. I'm so used to AutoCAD that this is second nature to me. If there is anyway that you think might be better to accommodate this task, please share.

And as for Silverlight not working with Linux, I agree. I dream of the day when there will be such a powerful tool that is compatible across all platforms. There is however an open source implementation of Silverlight for Linux known as Moonlight which is used to run Silverlight applications on Linux. Perhaps you could try this.

Nah, it's cool. I just had a quick play with it and it was the first thing I spotted. I assumed that escape was a possible key to press but wanted to point it out just in case it was something more obscure or obvious that I didn't realise

And as for Silverlight not working with Linux, I agree. I dream of the day when there will be such a powerful tool that is compatible across all platforms. There is however an open source implementation of Silverlight for Linux known as Moonlight which is used to run Silverlight applications on Linux. Perhaps you could try this.

it is only first generation of Silverlight that is working with Moonlight, and barely that due to crappy implementations.

I did a little testing on it again last night and found a few problems. I guess the default backgrounds and border I'm using for the widgets causes them to appear extremely black in game.

What are some good default backdrops that are used for each widget?
Mainly...
-Scrollframe
-Frame
-Statusbar
-Editbox

Edit: Added support for function generation. Functions can be created by selecting the Functions tab, clicking the "+" button to the lower right, and defining the function in the table. Functions defined here will be used for the autocomplete source when defining script handlers in the designer. They are also written out to the Lua code tab.

Line in question generated by code is as follows:
frmOption.fsWidth = CreateFontString("frmOptionfsWidth","OVERLAY",frmOption)
This needs to be changed to
frmOption.fsWidth = frmOptions:CreateFontString("frmOptionfsWidth","OVERLAY",frmOption)
for this error to be bypassed

Line in question in my addon :
frmOption.fsWidth:SetFont("Fonts\FRIZQT__.TTF",10)
needs to be changed to
frmOption.fsWidth:SetFont("Fonts\\FRIZQT__.TTF",10)
For it to bypass that error.

Resulting screen display with no other code changes on my point is as follows:

It did speed up the design of the options screen but there is a lot of duplicated code there and as you can see doesn't quite work the way I planned it to work. Not sure if I will use this in the long run as I tend to make reusable functions to do this stuff for me but designing wise it may come in useful. Only time will tell.

Hopefully the above changes can be worked in somewhere and if I can easily correct the visual result in a way you can implement then I will let you know what I did to correct the problems. But grats on a useful feature as I am sure there are tons of people that will benefit more in the long run.

Oh, and if all the posting above wasn't a guide I do all my coding in lua so perhaps the xml side of things are working very well in comparison.

And also, I will add that apart from the name and text fields I didn't do any alterations inside the visual designer, so if that is the cause of the above problems that's great I actually forgot I hadn't done that but I'm not sure setting values for the sliders would fix the layout of the fontstrings which I suspect are due to the fact that they are art elements more than objects. I usually manage to tie them to a physical object and move them that way.

Okay, looks like I may have to go back to my usual way of designing interfaces. Way too many things to change unfortunately for me. Anyways, in light of the fontstring alignments I haven't found an easy way around it yet with the code automatically generated. As I pointed out in the last post the problems could be due to my not setting the other fields.

Aha, I figured out why everything seemed extra codey to the way I usually work. The screenshot below I just wrote from the ground up with the following code. Where I use the UI Options templates it cuts down alot of the code which I personally don't need to alter. For those that like full control over their controls may be quite happy with your utility unfortunately it isn't for me in its current state. The same layout ( which you could see didn't work successfully ) took up at least 3 times the amount of coding which was unnecessary in my case. All I need to do is now set the anchors the way I usually do, although at present they look fine so far, and also set up the coding to reflect the changes and default values. And of course my SetMovable function needs to be set up along with the other related functions.

Xrystal, thanks for all the feedback. This will really help with my development.

I have actually been using it a lot to make the Options panel for an addon recently, and while doing so have discovered many bugs in the XML side, but haven't been able to hit the Lua side yet. These bugs are very easy to fix, but are a bit misleading when trying to spot them.

The default backdrop was being used on all widgets. This didn't fair well when used by a checkbox (it made them completely black). The same goes for Sliders.

Font string offsets on checkboxes were also off.

There are many bugs like this, and I'm constantly finding them and squashing them. Each time, the app advances.

The code you posted gives me a couple ideas in helping out those that use templates as well. Perhaps a feature in which the user can create templates and drag them onto the screen. This would set the code up, both in XML and Lua, to create the template and all the frames that would inherit from it.

I absolutely love the feedback, I get more and more ideas for it each time. I haven't had a chance to update the app the past couple of days, but here soon I should have a pretty nice update.

There is now an early Alpha of Moonlight 3 which supports SOME of Silverlight 3. However it's buggy (though the version I am using is a couple weeks old). It was put up in time for the Olympics (since all of the Olympic video and many of the photos use Silverlight 3 players).

This XML/Lua Generator, kinda works with the rev of Moonlight 3 that I have installed (some of the Generator loads, the tabs and buttons can be seen and function, kinda, but not much else at the moment). I will see if there is an updated Moonlight 3 alpha and see if it helps. However this will be a couple of days as I have a pretty full slate for tomorrow.