I
Ignacio Renuncio
Hi everybody,
I've downloaded and taken a look to the FP2002 SDK (to my knowledge,
the only available) looking for ways to extend Frontpage. After
reading it, I don't clearly see what is the best method of extending
FP to suit my needs.
The situation is:
- A group of teachers need to create SCORM exercises but I haven't
found any application that can extend Frontpage to this extent.
- The SCORM exercises skeleton will be written in Javascript or Flash
and will have their internal information stored in a XML file.
I've looked in the SDK and it seems to be a lot of methods to extend
FP:
a.- Create a COM Add-in that uses FP through the object model
b.- Create a DTC (design-time control)
c.- Create a Frontpage Web Component
d.- Create a Frontpage component (bot)
e.- Create a Wizard
f.- Use VBA macros that exploit the FP object model
Does anybody have a clue concerning which ones to use and which ones
not?
Hints:
1.- I only want the control to exist in the authoring environment
2.- I don't want to have a cliente-side ActiveX that needs to be
downloaded
3.- I don't want to use Frontpage extensions at the server
4.- I want to use a VB-like (RAD) language to create these extensions,
not scripting, not HTML. I want a rich and dynamic interface.
In short, what I want is to extend FP in a way that an author can
create complex content locally and edit it through a window or wizard
in Frontpage, without knowing anything of the real code (he/she will
only see/edit XML contents through a friendly interface). He/she won't
need even a web server at all. All of the contents will work in a
client-only environment (IE6).
My guess about each of the options are:
a.- Is possible but there are probably better options. I see it more
of a way of integrating FP it with other applications and such.
b.- May be the best option. Is it used in the real world?
c.- Is not powerful enough because the interface is really HTML pages
and this way all of the XML handling and the complex UI should be in
HTML (improductive).
d.- Usually needs server-side components and/or FP Server Extensions.
The client-only approach for FP Components seems to be deprecated -
use DTC instead?
e.- Possible but I don't know if easier to build and maintain than 'a'
or 'b'
f.- Scripting? No thanks.
Could anybody help me? Which option would you use to extend FP?
Thanks a million.
I've downloaded and taken a look to the FP2002 SDK (to my knowledge,
the only available) looking for ways to extend Frontpage. After
reading it, I don't clearly see what is the best method of extending
FP to suit my needs.
The situation is:
- A group of teachers need to create SCORM exercises but I haven't
found any application that can extend Frontpage to this extent.
- The SCORM exercises skeleton will be written in Javascript or Flash
and will have their internal information stored in a XML file.
I've looked in the SDK and it seems to be a lot of methods to extend
FP:
a.- Create a COM Add-in that uses FP through the object model
b.- Create a DTC (design-time control)
c.- Create a Frontpage Web Component
d.- Create a Frontpage component (bot)
e.- Create a Wizard
f.- Use VBA macros that exploit the FP object model
Does anybody have a clue concerning which ones to use and which ones
not?
Hints:
1.- I only want the control to exist in the authoring environment
2.- I don't want to have a cliente-side ActiveX that needs to be
downloaded
3.- I don't want to use Frontpage extensions at the server
4.- I want to use a VB-like (RAD) language to create these extensions,
not scripting, not HTML. I want a rich and dynamic interface.
In short, what I want is to extend FP in a way that an author can
create complex content locally and edit it through a window or wizard
in Frontpage, without knowing anything of the real code (he/she will
only see/edit XML contents through a friendly interface). He/she won't
need even a web server at all. All of the contents will work in a
client-only environment (IE6).
My guess about each of the options are:
a.- Is possible but there are probably better options. I see it more
of a way of integrating FP it with other applications and such.
b.- May be the best option. Is it used in the real world?
c.- Is not powerful enough because the interface is really HTML pages
and this way all of the XML handling and the complex UI should be in
HTML (improductive).
d.- Usually needs server-side components and/or FP Server Extensions.
The client-only approach for FP Components seems to be deprecated -
use DTC instead?
e.- Possible but I don't know if easier to build and maintain than 'a'
or 'b'
f.- Scripting? No thanks.
Could anybody help me? Which option would you use to extend FP?
Thanks a million.