DesktopX Common information
Monday, October 4, 2004 by _Martin_ | Discussion: WinCustomize News
As we all get more sophisticated in creating DesktopX widgets we are setting parameters. The issue with this is that, if these parameters are not organised in a consistent manner then where several objects need the same kind of information we will find ourselves having to configure these each time.
Before this becomes too much of a problem I propose that we create some standards that users can set and developers can access.
For example:
Name information (title, forename, surname, suffix, nickname)
Address (Line 1, Line 2, City, State/Area, Zip/Postal Code, Country)
Measurements (imperial/metric)
etc, etc
Do people think this makes sense? If so, what information do you think would be useful?
Before this becomes too much of a problem I propose that we create some standards that users can set and developers can access.
For example:
Name information (title, forename, surname, suffix, nickname)
Address (Line 1, Line 2, City, State/Area, Zip/Postal Code, Country)
Measurements (imperial/metric)
etc, etc
Do people think this makes sense? If so, what information do you think would be useful?
 |
|
Page 1 of 2 | |
|
|---|
JoeWang
Reply #3 Monday, October 4, 2004 2:05 PM
Reply #3 Monday, October 4, 2004 2:05 PM
This would be nice for not having to enter the zip code to each new weather object again. I always thougt, I've told DesktopX my zip code so many times, but it keeps asking for it.
wombatDK
Reply #4 Monday, October 4, 2004 2:11 PM
Reply #4 Monday, October 4, 2004 2:11 PM
I'd say its a good idea. By the way, where are persistent variables stored now?
Ravenkall
Reply #6 Monday, October 4, 2004 3:04 PM
Reply #6 Monday, October 4, 2004 3:04 PM
As food for thought:
How much of the user information could come from a MS Passport profile? (or any of the other similar solutions)
The type of information collected in these solutions could be a good starting point for discussion.
Having the option to wrap around an existing profile solution would make some users happy as they would not need to re-enter their information again. Could be written in a way to have importers/translators for all kinds of sources...
How much of the user information could come from a MS Passport profile? (or any of the other similar solutions)
The type of information collected in these solutions could be a good starting point for discussion.
Having the option to wrap around an existing profile solution would make some users happy as they would not need to re-enter their information again. Could be written in a way to have importers/translators for all kinds of sources...
Will Rose
Reply #7 Monday, October 4, 2004 3:43 PM
Reply #7 Monday, October 4, 2004 3:43 PM
Martin,
I agree that this is a good idea. I think it should be structured in two parts: 1) A "GlobalWidgetPreferences" key that contains the sort of information you describe, and then a subkey called "AppSpecific" where individual widgets can store their own proprietary information (each in its own subkey), but in this agreed-upon place, instead of spreading it all over in random registry entries of disk files.
That will be better than the semi-chaos that now exists in terms of widget data storage.
Cheers,
Will
I agree that this is a good idea. I think it should be structured in two parts: 1) A "GlobalWidgetPreferences" key that contains the sort of information you describe, and then a subkey called "AppSpecific" where individual widgets can store their own proprietary information (each in its own subkey), but in this agreed-upon place, instead of spreading it all over in random registry entries of disk files.
That will be better than the semi-chaos that now exists in terms of widget data storage.
Cheers,
Will
47songs
Reply #8 Monday, October 4, 2004 6:27 PM
Reply #8 Monday, October 4, 2004 6:27 PM
I have yet to create anything on this site (or any site for that matter), but I guarantee you, if I ever do, I will NEVER give you my measurements!!
Thomas Thomassen
Reply #9 Monday, October 4, 2004 7:15 PM
Reply #9 Monday, October 4, 2004 7:15 PM
In stead of using the registry, how about using XML? I think XML will be more manageble than using the registry. Say if I want to transfer my settings from one computer to antoher, I would much rather just copy an XML file or and directory of XML files containg my setting than having to roam around in the registry to get them.
And besides this is the sort of stuff where the power of XML comes to life.
Though it would be nice of there was a central site that contained a list of these XML template files. Preferable somewhat managed so unnessesary duplicates are created.
And besides this is the sort of stuff where the power of XML comes to life.
Though it would be nice of there was a central site that contained a list of these XML template files. Preferable somewhat managed so unnessesary duplicates are created.
RomanDA
Reply #10 Monday, October 4, 2004 7:30 PM
Reply #10 Monday, October 4, 2004 7:30 PM
I think this could be good for color settings. IE: If my desktop is using Green as its main color, and that is stored somewhere, then when my app loads (and happens to have a Green color) I can set it to use Green as its default (which could be overridden if wanted by the user).
The XML could work ok, but that would mean if i want YOUR settings you can just send me your XML Setting file. That could be interesting.
The ZIP is a major one for weather Apps, its so dumb for all of us to have multiple places for this info to be stored.
The XML could work ok, but that would mean if i want YOUR settings you can just send me your XML Setting file. That could be interesting.
The ZIP is a major one for weather Apps, its so dumb for all of us to have multiple places for this info to be stored.
mrtee
Reply #11 Monday, October 4, 2004 10:00 PM
Reply #11 Monday, October 4, 2004 10:00 PM
Couldn't this be a page in SDC? Called (perhaps) "User Presets".
XX
Reply #12 Tuesday, October 5, 2004 12:10 AM
Reply #12 Tuesday, October 5, 2004 12:10 AM
Excellent idea. I'm tired of setting stuff after theme save again and again. I would also use it for my crystallized desktop stuff and etc.
Suriken
Reply #13 Tuesday, October 5, 2004 12:25 AM
Reply #13 Tuesday, October 5, 2004 12:25 AM
GOOD IDEA !!! 
yes this is good
and a good widget to create that maybe is distributed with dx in later builds would be one that lets you specify all this information in one 'wizard' [like when you set up a program] (at least the global information eg zip, name , (some things could be imported originally from registry as default and changeable by the user))
if we use xml it would also have to be in a specified directory or whatever
maybe as a persistent object but i dont want the information disappearing due to uninstalling desktopx or updating a theme
yes this is good
and a good widget to create that maybe is distributed with dx in later builds would be one that lets you specify all this information in one 'wizard' [like when you set up a program] (at least the global information eg zip, name , (some things could be imported originally from registry as default and changeable by the user))
if we use xml it would also have to be in a specified directory or whatever
maybe as a persistent object but i dont want the information disappearing due to uninstalling desktopx or updating a theme
_Martin_
Reply #14 Tuesday, October 5, 2004 2:53 AM
Reply #14 Tuesday, October 5, 2004 2:53 AM
OK - What I'll do is start working on a draft object for this and a sample of how to use it.
What I can also do is create an object that can read certain registry information that may be of use such as custom folders for documents etc.
I know some of use might be able to dismantle the registry but this would make things easier for all.
I can also look at a way in which the settings could be exported to a file and therefore reimport them. I think this would be easier to manipulate than an XML file (good idea though that is).
Oh and Donna, good one, that got my morning off to a good start
What I can also do is create an object that can read certain registry information that may be of use such as custom folders for documents etc.
I know some of use might be able to dismantle the registry but this would make things easier for all.
I can also look at a way in which the settings could be exported to a file and therefore reimport them. I think this would be easier to manipulate than an XML file (good idea though that is).
Oh and Donna, good one, that got my morning off to a good start
JeremyG
Reply #15 Tuesday, October 5, 2004 6:21 AM
Reply #15 Tuesday, October 5, 2004 6:21 AM
I have a working model of this somewhere in my archives of DesktopX code. But I havent worked with desktopX in a long time, i always ended up very frustrated. 
Thomas Thomassen
Reply #16 Tuesday, October 5, 2004 6:27 AM
Reply #16 Tuesday, October 5, 2004 6:27 AM
XML is very easy. I'm actaully working on a XHTML parser to validate XHTML files. It can esily be converted to read XML files. As for where the setting to be saved I reakon it can simply be made in any directory that the user spesify. That way you can very esily make different setups. The path of the directory would be saved in the script object persitent storage.
nainu
Reply #17 Tuesday, October 5, 2004 6:48 AM
Reply #17 Tuesday, October 5, 2004 6:48 AM
I agree that XML (if size is a matter - zip it up) is a good solution. In fact a few standards exist already that cover personal settings and preferences stored in XML.
Another solution might be the ever famous "property"-files that many applications and installers use. Split into sections and with simple key/value lines.
Either way it could be used together with some sorta of namespace mechanism (isn't that included in the new widgets?) to allow distinction between general settings, widget specific settings and more.
Easy again would be the implementation of a user interface that is able to map the names/names spaces/keys to a hierarchical, extensible layout for settings.
That's my 2 cents
Another solution might be the ever famous "property"-files that many applications and installers use. Split into sections and with simple key/value lines.
Either way it could be used together with some sorta of namespace mechanism (isn't that included in the new widgets?) to allow distinction between general settings, widget specific settings and more.
Easy again would be the implementation of a user interface that is able to map the names/names spaces/keys to a hierarchical, extensible layout for settings.
That's my 2 cents
Septimus
Reply #18 Tuesday, October 5, 2004 9:32 AM
Reply #18 Tuesday, October 5, 2004 9:32 AM
I'd lean to more the XML store, as for some reason the registry settings used by Mormegils widgets, which are perfectly good, reset. I though I knew why and how to stop it, but I failed and it means I cannot use any of his Core objects or widgets as the settings don't stay, they just reset to the default.
Thomas Thomassen
Reply #19 Tuesday, October 5, 2004 11:39 AM
Reply #19 Tuesday, October 5, 2004 11:39 AM
I tell you what, give me time out this week and I'll see if I have time to complete my XML parser and make the first draft of a XML setting tool.
Another thing about XML is that it's crossover compatible with basicly any system, so exising XML setting schemes can easily be used with little or no modifications.
Another thing about XML is that it's crossover compatible with basicly any system, so exising XML setting schemes can easily be used with little or no modifications.
_Martin_
Reply #20 Tuesday, October 5, 2004 11:43 AM
Reply #20 Tuesday, October 5, 2004 11:43 AM
OK - I'll make it XML based - that way the various antivirus/firewalls etc are less likely to get upset with it too.
I'll get started tonight and have a draft in the next couple of days.
I'll get started tonight and have a draft in the next couple of days.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 1 of 2 | |
|
|---|
Reply #1 Monday, October 4, 2004 2:01 PM
- Shorcuts (shorcut 1, url / target of the shorcut 1 shorcut 2, url / target of the shorcut 2 ...) (eg. Wincustomize, https://www.wincustomize.com Word, Winword.exe etc.)
- Weather settings (location (eg. FRXX0145) measurement units etc)
- Media Player settings (volume (eg. from 1 to 100) radio names and urls (eg. CNN, http://www.cnn.asx))
- Time zone
- Language (is this doable ?)
Thanx for the great idea Martin.