MX Tree Menu Extension from InterAKT

milo2man · milo2man

I installed the MX tree menu extension from InterAKT on DW MX and am trying to
create a static tree menu. I set up a site using a local test server (IIS) and
defined the server model as ASP-Javascript. I then created a index.asp page and
tried to add the tree menu using the insert static tree menu command.

I get an error msg saying "Implementation file for server object not found:
C:/Program Files/Macromedia/Dreamweaver
MX/Configuration/ServerBehaviors/ASP_JS/InterAKT/TreeStatMenCom_Data.htm

I looked in this directory and there is indeed no file with this name. Where
do I get it? Has something gone wrong with the installation of the extension. I
uninstalled and reinstalled and this didn't help.

Appreciate your help.

Miloman

Brad Lawryk · Brad Lawryk

Hello milo2man,

Is this the trial version you are using? Or is it one you have already had
and used successfully before but it has stopped?

Also what version of MX Tree and DW are you using?

Brad

> I installed the MX tree menu extension from InterAKT on DW MX and am
> trying to create a static tree menu. I set up a site using a local
> test server (IIS) and defined the server model as ASP-Javascript. I
> then created a index.asp page and tried to add the tree menu using the
> insert static tree menu command.
>
> I get an error msg saying "Implementation file for server object not
> found: C:/Program Files/Macromedia/Dreamweaver
> MX/Configuration/ServerBehaviors/ASP_JS/InterAKT/TreeStatMenCom_Data.h
> tm
>
> I looked in this directory and there is indeed no file with this
> name. Where do I get it? Has something gone wrong with the
> installation of the extension. I uninstalled and reinstalled and this
> didn't help.
>
> Appreciate your help.
>
> Miloman
>

milo2man · milo2man

Hi Brad

I have the free download MX Tree Menu v 1.8.0 from Interakt and am using DW MX
v6.0.

I figure out that the problem was I had added the static tree menu to a DW
template. On pages created from the template, I could edit the treemenu data
but DW did not save it since the data is in the <head> section. After setting
the <TemplateInfo codeOutsideHTMLIsLocked="false"> I was able to edit and save
the treemenu on pages created with the template.

I still find the MX Tree Menu from InterAKT difficult to work with. Especially
the dynamic, database driven server behavior. Can you recommend the Tree Menu
Magic from PVII ?

Cheers.

Brad Lawryk · Brad Lawryk

Hello milo2man,

You can't really compare the MX Tree to PVII Tree Menu Magic. The MX Tree
is Free and very basic in what it can do. A better comparison is MX CSS Menus
with the PVII products. I have used both and both are exceptionally well
put together. You mentioned database driven in your message, if thats the
case then the InterAKT MX CSS Menus is the way to go as the PVII is only
static. The editing of the CSS menus in the InterAKT one is much easier as
well especially if you are not knowledgable in CSS.

As for the static menus, my personal preference is the InterAKT one. But
keep in mind thats only a personal preference thats works best for me. I
havn't experienced any problems with PVII either. Both are awesome. I'd suggest
downloading trials of each and give them a look.

The user interface of MX CSS Menus is much easier to follow than the MX Tree
as well.

Brad

> Hi Brad
>
> I have the free download MX Tree Menu v 1.8.0 from Interakt and am
> using DW MX v6.0.
>
> I figure out that the problem was I had added the static tree menu to
> a DW template. On pages created from the template, I could edit the
> treemenu data but DW did not save it since the data is in the <head>
> section. After setting the <TemplateInfo
> codeOutsideHTMLIsLocked="false"> I was able to edit and save the
> treemenu on pages created with the template.
>
> I still find the MX Tree Menu from InterAKT difficult to work with.
> Especially the dynamic, database driven server behavior. Can you
> recommend the Tree Menu Magic from PVII ?
>
> Cheers.
>

Brad Lawryk · Brad Lawryk

Hello milo2man,

> I have the free download MX Tree Menu v 1.8.0 from Interakt and am
> using DW MX v6.0.

I just saw this part ... you may want to check the compatibility with both
companies. I believe that both products may require at least DW MX2004. I
may be wrong, but be sure to check that as DW 6 is a few years old.

Brad

Nancy *Adobe Community Expert* · Nancy *Adobe Community Expert*

> I just saw this part ... you may want to check the compatibility with both

> companies. I believe that both products may require at least DW MX2004. I
> may be wrong, but be sure to check that as DW 6 is a few years old.

Tree Menu Magic (the Project Seven one) supports all the way back to DW4.0.
MX Tree from Interakt supports back to DMX 6.1.

--
Nancy Gill
Adobe Community Expert
BLOG: [url]http://www.dmxwishes.com/blog.asp[/url]
Author: Dreamweaver 8 e-book for the DMX Zone
Co-Author: Dreamweaver MX: Instant Troubleshooter (August, 2003)
Technical Editor: DMX 2004: The Complete Reference, DMX 2004: A Beginner's
Guide, Mastering Macromedia Contribute
Technical Reviewer: Dynamic Dreamweaver MX/DMX: Advanced PHP Web Development

Al Sparber- PVII · Al Sparber- PVII

"Brad Lawryk" <brad.lawryk@shaw.ca> wrote in message

Just to clarify a few points...

> You can't really compare the MX Tree to PVII Tree Menu Magic. The MX
> Tree is Free and very basic in what it can do. A better comparison is
> MX CSS Menus with the PVII products. I have used both and both are
> exceptionally well put together. You mentioned database driven in your
> message, if thats the case then the InterAKT MX CSS Menus is the way
> to go as the PVII is only static.

If I'm not mistaken, there is a very rigid database structure involved.
You can't just use any database. All of our menu products are easy to
use dynamically, as the markup is in the page and a simple query to any
database will work. Many of our customers deploy this way, though it's
often overkill.

The editing of the CSS menus in the InterAKT one is much easier as

> well especially if you are not knowledgable in CSS.

Well, that's a double-edged sword. By allowing edits in the UI, a very
convoluted CSS structure is required. We believe in the power of CSS and
in giving the user total control at all times and at all levels, with
the simples CSS possible and, of course, lean scripts.

> As for the static menus, my personal preference is the InterAKT one.
> But keep in mind thats only a personal preference thats works best for
> me. I havn't experienced any problems with PVII either. Both are
> awesome. I'd suggest downloading trials of each and give them a look.

We do not provide trial versions. In order to do that with a Dreamweaver
extension, one must write and let loos a rather intrusive and sometimes
dangerous cadre of files. We also support OS X, which would present more
serious compromises.

Just wanted to point these things out :-)

--
Al Sparber - PVII
[url]http://www.projectseven.com[/url]
Popup Menus | Image Galleries | CSS Tutorials & Templates
------------------------------------------------------------------------------------
Newsgroup: [url]news://forums.projectseven.com/pviiwebdev/[/url]
CSS Newsgroup: [url]news://forums.projectseven.com/css/[/url]
DW Newsgroup: [url]news://forums.projectseven.com/dreamweaver/[/url]

milo2man · milo2man

Thanks to everyone for the helpful responses. I managed to solve the server
problem by uninstalling MX Treemenu, updating DW from 6.0 to 6.1 and
reinstalling the extension. The static data menu works fine but the dynamic
database driven behavior is awkward and difficult to use. Here I agree with Al.
Too bad that PVII doesn't provide trial versions.

I have followed the suggestion of Murray to link the treemenu source data page
to the content page. That way, I can change the menu contents at the source and
automatically update all content pages. So I have something that is in between
static and dynamic. Works great for me.

Murray's posting was very helpful.

[q]Originally posted by: Newsgroup User

>I have created a static tree menu using MX Tree Menu extension from
>InterAKT.
> Everything works fine but when I try to save the tree menu as a library
> item, I
> get an error. It seems the library item only contains the part of the tree
> menu
> code that is in <html> section. However, the source data for the tree menu
> is
> located in the <head> section, and this is not saved as part of the
> library
> item.

That's correct.

> Anyone know a way around this problem?

The only way would be to make the menu's javascript be an external file, and
then link that external file to all pages. You could use Find and Replace
to do this.

Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

[/q]

MX Tree Menu Extension from InterAKT

Thread Tools

Display

MX Tree Menu Extension from InterAKT

Similar Questions and Discussions

Menu Command don't display extension menu

DHTML MX Tree Menu

Tree-style menu

dynamic tree menu

Folding Tree Menu...any help?

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Re: MX Tree Menu Extension from InterAKT

Posting Permissions