LOL Well, I was thinking XML as a validate-able data format. I didn't actually have a plan. .INI file?
I'd like to avoid the wizard concept... I think it's less convenient. Tabs, ok, wizard... yik I figured if it supported JavaScript or something, there could a moderate level of customization without significant effort. Plus, I think I'm going to have JavaScript embedded somewhere in here anyway (in the PGO automation tool); probably in the form of IronJS (http://github.com/fholm/IronJS) G Garrett Serack | Open Source Software Developer | Microsoft Corporation I don't make the software you use; I make the software you use better on Windows. From: Ritchie Annand [mailto:[email protected]] Sent: Thursday, April 22, 2010 11:38 AM To: Garrett Serack Cc: [email protected] Subject: Re: [Coapp-developers] Idea: Providing a generic user interface for configuring applications Wait, WinForms? :) What sort of configuration abilities are you looking for? Are you thinking more about a hierarchy of properties (akin to an XML file) or something a little more process-oriented (tasks/wizards)? If you're looking to have it like an XML sort of hierarchy, do the nodes need to be unique? Just asking, because I put together a Configuration framework piece a while back (no UI) and one of the issues was that if you wanted to support database or registry, then you had to avoid XML's ability to have multiple nodes of the same name. A mildly generic snap-in sounds like fun. What would the JavaScript be used for? --=- Ritchie ----- Original Message ----- From: Garrett Serack <[email protected]> Date: Thursday, April 22, 2010 11:45 am Subject: [Coapp-developers] Idea: Providing a generic user interface for configuring applications To: "[email protected]" <[email protected]> > (this may be something we'll look at a few months down the road) > > CoApp conformant packages are can not interact with the user at > install time. > > However, after installation, a user will want to configure an > application, and perhaps there should be a simplified method to > building a common User Interface for configuring them, rather > than relying on users to edit text files manually, or play > around registry keys, etc. > > And, now that I think about it, it would help with remote > administration if it all hooked up like a mmc snapin. > > It appears that MMC 3.0 supports a .NET Winforms model for > building snapins. http://msdn.microsoft.com/en- > us/library/ms692744%28v=VS.85%29.aspx > I've got a really cool idea percolating in my head... kindof a > mildly generic snapin that can expose simple configuration > concepts via an xml file (+Javascript?) so that app publishers > can leverage a very consistent UI for configuring everything. > > Plus, this makes it all easy to remotely configure CoApp- > installed applications on remote machines. > > [Description: fearthecowboy]<http://fearthecowboy.com/> > > Garrett Serack | Microsoft's Open Source Software Developer | > Microsoft Corporation > Office:(425)706- > 7939 email/messenger: > [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>> > blog: > http://fearthecowboy.com<http://fearthecowboy.com/<http://fearthecowboy.com%3chttp:/fearthecowboy.com/>> > twitter: > @fearthecowboy<http://twitter.com/fearthecowboy> > > I don't make the software you use; I make the software you use > better on Windows. > > > > > > >
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
