CHERYL We were discussing the stable table at Microsoft today. That's a topic that could fill a folder with interesting files (if we weren't so half-baked)!
Murray challenged that there was any need, and he and I got into a tiff about code vs design approach. You popped in like an angel (as usual) and diced some particulars. Into the soup pot went the realativity of keyboard space and spacer.gif (actually, virtual spacer gif). Also, what about those extensive tons of <span> lines in nested tables. How do they effect various browsers and connection speeds? Is there a way to downsize code without destroying the nest? I've tried without success. What are tags that could provide a solution?
My last post hit the day's end shut down. It was the most important.
EW's best innovation for developers is really the snippet tool. Microsoft needs to further develope the snippet tool; give it a Vista flare. There's still time. It is the only archive apparatus in the program. It has the potential to be an online exchange system for web developers almost immediately. But with minimal tweak it can be very attractive.
Example 1:- Some nerd shows up with a copy of a table template for static page layout using nested html tables. He pastes the snippet code into a forum. Forum participants participants post CSS versions. Participants copy snippets it into their snippet collections and test it out, some time in the future implementing their own improvements and inserting their comments. Back to the forum, and paste new alternatives to the original nerd post. And oh, here's some links (if anyone cares). What a frazzel!
Example 2:- Expression Web, EW needs an enhanced snippets tool, ST. ST needs to allow developers to link into an EW SharePoint, EWS for web developers with a link on the Page Editor Options/Code Snippets tab. The site can be opened in the browser or in EW. When opened in EW, ST allows visitors to toggle snippet sharing. Important or conclusive developments can be archived in a library. EWS shows five lists when it is opened from the Code Snippets tab while visiting the EW SharePoint. The lists are:
- My Snippets - including selection boxes to select what snippets to share (let others see)
- Other Snippets - including each users name and a selection boxes to select snippets to keep
- Add-Ins - download information and free snippets from Microsoft
- Shared Files - the goodies uploaded by users to a shared file library
- Microsoft Expressions - the site, of course, four major links and some subsite links in a framed tree list
Microsoft Expression Web newsgroups could simply be framed into a transition to the SharePoint.
Some thoughts are in order.
- First, the conservative element is going to initially freak and regress into staring at the newsgroup frame.
- Second, permissions allow access to My Snippets, Other Snippets and Shared Files only to visitors with a registered copy of EW, not FP.
- Third, the newsgroup frame, Add-Ins and Microsoft Expressions are public turf.
- Fourth, the continued and historical visitor volume is assured; however, the EWS webmaster may need a TOC tool to manage a list of active topic pools, downsizing visitor congestion if EWS gets more popular.
- Fifth, topics can only be posted by registered owners of the EW product, not the FrontPage product.
Points 2 and 5 are obviously market assessors: stats can be emailed to sales and wherever.
EWS can be set up by Microsoft in a day. ST update patch could take a few days. No problemo! What do you think?
((Cheryl, is this 80's style post rhetoric or do you think this goes somewhere?))