| Author |
Message |
Gonçalo Boléo
Guest
|
 Posted:
Fri Jan 07, 2005 6:46 pm Post subject:
Extending the WebAuthor Dialogs |
|
|
I wan't to extend and modify the dialogs of WebAuthor.
Do you recommend this?
Where can i find documentation for this?
thanks,
Gonçalo Boléo |
|
| Back to top |
|
 |
rdcpro
Guest
|
| Posted:
Sat Jan 08, 2005 5:05 am Post subject:
RE: Extending the WebAuthor Dialogs |
|
|
Well, I have a few comments, though no real recommendation.
We "borrowed" the browse internal links dialog, because I wanted to change
how it worked slightly (to use GUIDs rather than the URL). I figured there
would be a chance that these ASPX pages would change in some future service
pack, so I copied them to our templates directory, made the changes (it was
just a one-liner javascript change anyway), and went on my merry way.
Then later we installed SP1a.
Some time later still, we noticed that some of the images in the dialog box
weren't being rendered, and some other goofy things were happening. After a
few minutes of research, I discovered that SP1a changed some of the CSS class
names from using underscores to using hyphens. And instead of a linked image
for submit, they changed the buttons to...well...buttons, and deleted the
original image.
Not a big deal to fix, but it did make me think twice. When we installed
SP1a, we didn't do a *complete* regression test of every piece of
functionality in the site...
In a similar vein, I created some Sharepoint Portals where the requirements
involved *substantial* changes to the ASPX templates. Because I was
concerned about change management and version control, I created a VSS
repository of the changed templates. When a service pack is installed, we do
it as though you would create a separate development branch in a CVS system.
Then we "merge" the main branch and the service pack branch. This identifies
any changes to the files that may have occured in the service pack, and you
can then deal with each individual change separately.
It may not make it easier to deal with changes, but I think it means fewer
surprises.
So, I would say that while you *could* make changes to the web author
dialogs, I wouldn't guarantee this isn't going to cause headaches in the
future, because I've found that they *do* change these things.
Regards,
Mike Sharp
"Gonçalo Boléo" wrote:
| Quote: | I wan't to extend and modify the dialogs of WebAuthor.
Do you recommend this?
Where can i find documentation for this?
thanks,
Gonçalo Boléo
|
|
|
| Back to top |
|
|
Gonçalo Boléo
Guest
|
| Posted:
Mon Jan 10, 2005 4:55 pm Post subject:
Re: Extending the WebAuthor Dialogs |
|
|
Thanks for your recommendation!
I can see some future problems i can have, that i never realise that could
happen.
"rdcpro" <rdcpro@community.nospam> wrote in message
news:E9C45CCF-963F-499E-BEC2-B17779BA8183@microsoft.com...
| Quote: | Well, I have a few comments, though no real recommendation.
We "borrowed" the browse internal links dialog, because I wanted to change
how it worked slightly (to use GUIDs rather than the URL). I figured
there
would be a chance that these ASPX pages would change in some future
service
pack, so I copied them to our templates directory, made the changes (it
was
just a one-liner javascript change anyway), and went on my merry way.
Then later we installed SP1a.
Some time later still, we noticed that some of the images in the dialog
box
weren't being rendered, and some other goofy things were happening. After
a
few minutes of research, I discovered that SP1a changed some of the CSS
class
names from using underscores to using hyphens. And instead of a linked
image
for submit, they changed the buttons to...well...buttons, and deleted the
original image.
Not a big deal to fix, but it did make me think twice. When we installed
SP1a, we didn't do a *complete* regression test of every piece of
functionality in the site...
In a similar vein, I created some Sharepoint Portals where the
requirements
involved *substantial* changes to the ASPX templates. Because I was
concerned about change management and version control, I created a VSS
repository of the changed templates. When a service pack is installed, we
do
it as though you would create a separate development branch in a CVS
system.
Then we "merge" the main branch and the service pack branch. This
identifies
any changes to the files that may have occured in the service pack, and
you
can then deal with each individual change separately.
It may not make it easier to deal with changes, but I think it means fewer
surprises.
So, I would say that while you *could* make changes to the web author
dialogs, I wouldn't guarantee this isn't going to cause headaches in the
future, because I've found that they *do* change these things.
Regards,
Mike Sharp
"Gonçalo Boléo" wrote:
I wan't to extend and modify the dialogs of WebAuthor.
Do you recommend this?
Where can i find documentation for this?
thanks,
Gonçalo Boléo
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in