As it would be normal, after an web application launches, feedback starts pumping in. This is true in the case of MyLinkVault also.
There was a lot of positive feedback. It seems you people actually like it. That's very good to know.
For a list of main changes read the quote below from the MyLinkVault site:
- Increased Customization
- You can now change the font, color, and size of your link titles and link descriptions via Settings.
- Link Privacy Settings
- Individual links can now be set as either Public or Private. If links are Private, they can only be seen by the user. If they are Public, they can appear in lists like the New Links list and the Popular Links list. Users can set the default setting for new links in the Settings area.
- New Links and Popular Links
- You can now see lists of new links and popular links.
- Multiple Page Support
- We've added the ability to store link categories on multiple pages, for those users with lots of links. To do this, you'll first need to enable this feature via the Settings area. Once enabled, a drop down box will appear in the top right of the My Links page showing your list of pages.
- Locking and Unlocking
- You can now lock and unlock your links page. When locked, you will be unable to drag-and-drop categories and links, but will still be able to edit them.
- User Interface
- Along with a new site design and color scheme, we've made a number of small changes to the user interface that we think make the site easier to use.
Give it a spin, try the new MyLinkVault facelift.
Tech credits
On another level I have seen a discussion on a forum about what techniques were used on MyLinkVault. And I realised that I have forgotten to credit a few people for their scripts I used.
The first one which really deserves a lot of applause is Dean Edward and his great cssQuery function. Next on the list we have Aaron's onDOMload super script that helps with the executing of events before the whole page is loaded. And finally there the minmax CSS fix for IE.


at 09:24 on 08/Jan/2006
Comment by Aaron Barker
Thanks for the mention of using onDOMload. This is the first time, that I know of, that someone has used the script. It's nice to see it out in the open.
I haven't tried this yet to confirm, but I would think you could use the cssQuery function in place of the getElementsBySelector function. All getElementsBySelector does is return an array of elements, which I believe is what cssQuery does... and much more powerfully to boot. So if you changed onDOMload to use cssQuery and then axed the getElementsBySelector part of the code, you'd save a little bit of filesize.
Just a thought. Thanks again for the mention.