In the classic (and best) Star Wars movie The Empire Strikes Back, Han Solo realizes that his friend Luke Skywalker is in trouble out in the icy wastelands of the ice planet Hoth and that he must go and search for him, perhaps in vain.
His first thought is to use a SnowSpeeder, a fast flying craft that would be ideal for scouting a vast area for life. However, he is told that the speeders are not available because the technicians are having trouble adapting the machines to the extreme temperatures.
Like the SnowSpeeder technician, I’d like to let you know that it’s been difficult adapting the concept of MenuMachine from a plug-in to a full-blown application. There have been many unforeseen issues that we’ve come across, each one adding to the time taken to get MenuMachine out the door.
In many ways, GoLive was an ideal environment for our plug-in. It was self-contained, had great site and link management capabilities and a great SDK that we could use to develop against.
With a standalone application, we can’t rely on having any of this. There is no site management, so we have to build it. There is no link management, so we have to build it. We need to provide the ability for users that don’t have a supported editor to place the menu on their pages.
We also have to work with several very different plug-in APIs, one for each of the HTML editors we need to support. Each one of these is totally different and offers different challenges.
For example, Dreamweaver has a mature plug-in API (where “mature” means “ancient and crusty”), and the support for binary (compiled) plug-ins is pretty rudimentary. Panic’s Coda has a nice SDK, although it’s new and fairly limited. MacRabbit Espresso has a sophisticated SDK but it’s also very new and limited. The list goes on.
At the same time, we need the new version of MenuMachine to create menus that are more sophisticated than MenuMachine 2’s, while also offering great accessibility and flexibility.
All of this takes time. We are trying to build an app that will be fairly bulletproof, and will generate menus that will work in the vast majority of users’ pages. We are doing our best to do this.
We want MenuMachine to be reborn just as much as all of you and we are getting there. The light is at the end of the tunnel. We’re working very, very hard.
August 21st, 2009 at 4:48 pm
Hi Rob,
Love The Empire Strikes Back metaphor!
I’m sure I speak for all MenuMachine fans eagerly awaiting the launch of a standalone version that I hope the technicians can adapt to the extreme temperatures, but I believe that, unlike Hoth, the spring-time is approaching in Queensland, so the rise in temperatures should make their lives a touch easier.
I also believe that MenuMachine (standalone) will blow the socks off of anything currently available for building menus. The plug-in version is way better and more feature laden than Dreamweaver’s Spry menus and WebAssist’s CSS Menu Writer.
All the best in the lead up to the launch of what we all know wil be the best menu creation tool available – MenuMachine.app
Craig
August 21st, 2009 at 6:42 pm
Thanks for posting, Rob. I bet I’m not the only one checking your blog every day to see when it’s coming.
Thanks for not giving up on it.
August 21st, 2009 at 10:38 pm
Thanks for the update.
August 21st, 2009 at 10:59 pm
Thanks for keeping us up to date with all the hard (and probably sleepless) nights you are having. This is going to be one Monster Menu Machine!
August 22nd, 2009 at 2:17 am
Until I have a new Menu Machine, they will have to pry GoLive from my cold, dead hands. The great menus are the centerpiece of what I offer to clients. Please keep plugging away.
August 22nd, 2009 at 9:45 pm
Completely agree: “Until I have a new Menu Machine, they will have to pry GoLive from my cold, dead hands. The great menus are the centerpiece of what I offer to clients. Please keep plugging away.” I couldn’t have said it better.
August 25th, 2009 at 6:53 am
Ditto to what Maryanne Solomon said!
August 25th, 2009 at 9:03 pm
I’ve just realised that this new MM application is critical to Snow Leopard. I never got GL 9 and so have a PPC version of GoLive that will not run under SL. So I cannot manage MM menus using GoLive and DW.
Snow Leopard is finally forcing me to bend to Adobe’s ways and migrate to DreamWeaver. Having said that, over the last few years I’ve been doing a lot more hand coding. It is the menus that I can’t (and don’t want to) do by hand.
August 26th, 2009 at 8:01 am
PowerPC apps will still run in Snow Leopard as long as you ensure that the Rosetta component is installed. I’ve tested this myself.
August 27th, 2009 at 1:58 pm
Would it have just been easier to write a competitor to DreamWeaver?
I’m checking almost every day though. I’d even be happy with something that just worked, much less raising the bar from MM2.. Can’t wait. I’m encouraged that the code editors you’re working with are all my favorites.
Jonathan – Adobe just said that they’re not ‘supporting’ CS2 and CS3, but that doesn’t mean they won’t run. I’m sure that rosetta will run GoLive just as well in Snow Leopard as it does in Leopard.
August 28th, 2009 at 10:35 pm
Hi Rob
Waiting patiently, or trying to
One thing that I hope your looking at that involves the bulletproof thing, the current conflict that swfobject and menumachine have in IE 7 and possibly 8. It’s a hit and miss thing, that happens in some computers and not others. Dreamweaver CS4 new flash insert is using this now and I can confirm menumachine 2.2 is clashing. The work around is to use the version dynamic version at google code where you can place the flash loading script below the script for menumachine. Your probably aware of all this already, but just in case….
Dave
August 31st, 2009 at 12:04 am
thanks for keeping us eagerly waiting folks up to date!
I am running snow leopard since yesterday and golive cs2 and 9 start and seem to work – and faster, too!
but does anyone have problems so far?
just wondering – kai.
August 31st, 2009 at 12:37 am
Yup, I can’t wait for the new version.
I have had it up to here with hand coding css menus.
Without Menumachine on the horizon, I would have started a new business, designing and implementing a new system called menumachine. (It would have been a stand-alone app that seems like a lot of people need and desire)
Do you think it would have been popular???
Thanks for your hard work.
I can’t wait for this!!!
Russ M.
September 4th, 2009 at 1:50 am
Hello Rob,
thank you to develop MM as standalone app.
@Kai – yes I got big problems with GL9 and SL.
It’s doesn’t start anymore
Oliver
September 4th, 2009 at 3:10 am
hi rob,
no problems here so far. the occasionall crash was always normal with golive in my case…
try and delete the preference files of golive.
goog luck! kai.
September 4th, 2009 at 3:10 am
sorry this was meant for oliver…
September 8th, 2009 at 10:01 am
I check your blog about once a week, Rob. Don’t give up! We need something good because Adobe’s Spry menus are a pain in the butt, and very limited.
I’m hoping MenuMachine will generate clean, Standards-based code
September 8th, 2009 at 7:24 pm
@Designer Steve:
Yes, MenuMachine for the Mac will generate list-based HTML code, with CSS and unobtrusive JavaScript. The menus will work without JavaScript enabled and will be fully accessible and search-engine-friendly.
September 9th, 2009 at 4:18 pm
Metaphors are no substitute for tangibles. How long does it take to change a light bulb? Almost given up and a bit tired of the back stroking and rhetoric.
September 10th, 2009 at 1:55 am
I can report that GoLive CS2 is working well in Snow Leopard. Many thanks all!
I’m still looking forward to the standalone!
September 12th, 2009 at 1:23 am
Stuart,
It’s obviously not the same as changing a light bulb. More like the light bulb is now only available in a newer voltage, so all the generators, lines, sockets, and fixtures need to be changed.
Yes, we’re all impatient, but it’s no reason to be rude.
September 16th, 2009 at 7:20 pm
I do not think Stuart is being rude. It has been a very long wait and many people have been forced to give up and find another solution. A firm release date would help immensely with decision making. It is beginning to sound like this product might never be released.
September 17th, 2009 at 8:57 am
Stuart and Chris, I hear you and understand the frustration. Trust me, MenuMachine for the Mac is very real. We will give a release date as soon as we are able.
September 20th, 2009 at 2:24 am
My little company builds a 100% web-based CMS. At last count, we have 52 tasks left before we can launch our third (complete) re-write. I don’t expect to change the world, or even put a minor dent in it, but one of those tasks is to decide on a menuing system, or several, as options. I can’t imagine a better “sister app” than the new MM3. I really hope that the Golive renegades (I count myself as one) who _know_ a good thing when they see it will be able to use MM3 in all sorts of creative apps. I’m certainly hoping that MM3 will work with ours! Best wishes to you and your colleagues, Rob!
September 28th, 2009 at 10:51 pm
Hello Rob
I am one of the many MM2/GL users waiting for MM3. Nearly every website I do uses MM2 menus.
Is it possible to be on a mailing list to get the news when MM3 will be released?
September 30th, 2009 at 9:26 am
Helloooooo Rob…
Is there any light at the end of the tunnel. Is it getting brighter, kinda dim, perhaps flashing.. What color is the light? When you let out a scream in the tunnel does it echo?
Ron ;>)
FYI:We’re running DW CS4 full bore here and copying/pasteing GL/MM code as needed from a parallel menu only site on GL. Works quite well actually.
October 3rd, 2009 at 8:31 am
I had to use Spry menus after all. Lots of coding, but they are better than nothing.
October 7th, 2009 at 9:45 am
do i understand correctly that menumachine is working for some people with snow leopard?
if so, can you please tell me how you made it work?
thanks for any help you can offer.
October 11th, 2009 at 10:01 pm
Ron said: FYI:We’re running DW CS4 full bore here and copying/pasteing GL/MM code as needed from a parallel menu only site on GL. Works quite well actually.
Exactly what I’ve been doing. However, have you checked a page with flash element in it? I’m seeing problems on Explorer, with intermittent results. Sometimes the flash doesn’t show, but a page refresh will force it. If you have run into this, please share.
It was fine in CS3 with MM. Scripts bumping into one another, I suspect. Haven’t tried using includes yet. That’s my next test.
October 13th, 2009 at 2:09 am
Great News and thanks for keep us updated. I’m looking forward to MM3. Still holding out on purchasing a substitute for MM2.
My hope is that once you have finished MM3 you can team up with Panic and make Coda a full blown Dreamweaver competitor. I don’t know about others but I know that I would jump the DW ship in a heart beat. It certainly doesn’t beat what GoLive was. It has some good points but not enough to outweigh the bad ones.
Please think about it.
EX – GoLive user – reluctant Dreamweaver user.
October 14th, 2009 at 4:23 am
As I slowly convert to Dreamweaver and Fireworks way of the web (and cursing every step of the way), one glimmer of hope is knowing that you’re working on getting MM3 ready.
I am using Spry and Fireworks for my new menus these days, but I’ll switch over to MM3 the day you announce it’s ready.
I’ve kept a few sites on GL just because those sites change their menus like socks (and MM2 is so darn easy to use)
I can imagine what a bear that re-writing your program has got to be. Good luck to you!
October 15th, 2009 at 6:00 am
I love the idea of creating a whole new competitor to Dreamweaver..
October 17th, 2009 at 5:30 am
I also love the idea of creating a whole new competitor to Dreamweaver – can´t say it better!
And if MM3 will have it´s own site-management it will be a perfect choice.
Keep it going Rob!
October 17th, 2009 at 5:08 pm
As a GL orphan I can’t wait for MM3 to set me free again.
October 21st, 2009 at 7:35 am
It’s been a couple of months since the last MM3 update. What’s the current status?
October 21st, 2009 at 10:50 am
So that we can prepare any sites currently in production, can you give us an idea how the menumachine object will be placed in the page? Will it just go inside a div tag with it’s own ID?
October 21st, 2009 at 11:58 am
The menu code will vary slightly for the various menu types but in general it will be a straight unordered list with a class name. There will also be code that is placed in the head section that links to the CSS/JS files.
October 22nd, 2009 at 1:04 pm
um…soon?
October 23rd, 2009 at 4:15 am
As soon as MM3 is out and I’m satisfied that it works great on DW, I am going to be unstalling GoLive and will be migrating all my sites to Dreamweaver. Can’t wait although I will miss GoLive!
October 23rd, 2009 at 11:38 am
Hi Rob
Just wondering if we might be seeing anything before the end of the year. I have a large project that I would like to build in Dreamweaver but would be forced to stay in GoLive if I can’t use menumachine (the client needs to change menu items very often and very quickly).
Holding Thumbs.
October 26th, 2009 at 6:24 pm
I have had to switch to DreamWeaver, GoLive was too sketchy in Leopard, can’t imagine what it would be like in Snow Leopard (I did install Rosetta first thing) I had to switch all of my MM menus to CSS/java or CSS only driven code, some of the code that I find is quite complex, but I was able to finally get several types of menus to work. All off them are using unordered lists. I create a library item of just the list so I can update it as needed. Even with the super complex systems that works fine. I do miss using MenuMachine, but I cannot hold up producing websites while waiting for something to work with DreamWeaver. I cannot use GoLive, half the time it won’t even start up and switching between it and DW is a headache worse than hand-coding CSS. I would seriously lose a vast amount of clients if I had to hold up making menus due to one program.
I know it must be very difficult to create a stand alone and I wish great success. No offense, but the risk of not being able to do a very important part of a site is too great. I taught myself how to do it (with the help of several pre-code resources), and I use the Spry menus too. I stay away from Horizontal submenus (I can build them in Fireworks) because I find them difficult to use on a web page. It just really sounds like there are a bunch of issues to meet the standards of the first MM plugin. I know that I had to move on.
October 27th, 2009 at 7:51 am
Our SE’s call our final tasks “sprints,” and that’s exactly what we’re doing to finish our CMS. Per a previous comment of mine, September 20, above, we’d like to consider MM3 as a sister app, and are now ready for anything you can provide to us so that we can see whether or not your app will mesh with our CMS. From everything you describe, it should. Hope so.
October 28th, 2009 at 5:22 am
Well, well, well… I’m back to Mac after many years of NecroSoft suffering. So, I won’t be left aside by the new MenuMachine when it comes, marching triumphally, screaming “fe-fi-fo-fum”, and kicking *ss.
Thing is: As for now, MenuMachine 2.21 is working very well under regular conditions in Snow Leopard.
Meanwhile I pray (which is only a way of speaking) for someone to buy GoLive and continue its development, since my approach to DreamWeaver left me very unimpressed, and quite angry with its user interface (something to REALLY miss about GoLive). I hate it when some product “kills” another not based on quality but mostly on user base and marketing.
Will MM3 have some sort of integration with some other software (and I’m NOT talking about DW here, I’m looking for other options)?
Well, thanks a lot.
Pepino.
October 28th, 2009 at 9:30 am
Yes, on release we plan to also support Panic’s Coda and will be adding support for other editors as soon as possible. It will also be possible to place menus on the page without needing any external HTML editor support.
October 30th, 2009 at 1:37 am
I have to confess. Forgive me, for I have sinned. I was tempted and purchased a competitors extension. It looked good, and it promised much.. But alas, after two days of struggling with it, I couldn’t get a workable menu out of it.
So, is it too late for requests for the new MenuMachine? I imagine that as well thought out as it’s been, these will all be there already.
I’m hoping to continue to be able to build a menu, then apply a new template or style to the same menu without it being ‘replaced’ and having to start over.
Lots of menu styles look good, but many times the images that may be included might be the wrong color for a site’s design. Please make it easy to tint or color the images, or make them available so we can modify them in Photoshop.
Please don’t hide the code so that it can’t be found. The competitors product allowed a menu size to be changed, but it didn’t resize the rollover image when it resized the main image.. Even after manually resizing the rollover image, the code still forced it to be stuck at the default size, making rollovers look awful.
A nice addition to MM3, or an additional product would be an xml sitemap generator. I’ve found that MM2′s html navigation page could be used to make a great sitemap page.
October 30th, 2009 at 12:32 pm
Hi Brian, I’m pretty sure that you’ll be pleased with the new MenuMachine.
October 30th, 2009 at 5:22 pm
… which is due out when again?
Before the end of the year? First quarter 2010? Later?
October 30th, 2009 at 5:44 pm
We have been hoping to have the app out this year (of course) but if we get too close to Xmas then we’ll be releasing early next year.
October 31st, 2009 at 12:42 am
Luckily the other extension was on sale for about 60% off…
October 31st, 2009 at 12:43 am
so i didn’t waste too much money. oops, sorry for double post.
November 3rd, 2009 at 8:27 am
Screenshots and more info would be nice, even if things change during development. Its November already…
November 4th, 2009 at 6:24 pm
Yes indeed, ive been playing with the WebAssists menu plug-in , whilst they are “kinda” nice, they do not compare at all to MM , so keep up the good work guys, your fan base is waiting ^_^
November 6th, 2009 at 2:31 pm
Yes, kinda nice is being kind. Everything I have from them copies over all the images for menus as zero k files, so they don’t work until I go hunting for all the original image.. Even that works better than the ‘other’ company’s product. I’m still going back and forth creating new sites in DW and leaving a div tag open so I can go back in GoLive and insert MenuMachine’s menus…
November 11th, 2009 at 2:30 pm
I want MM3 under my tree!!!!!! Please, Santa, Please!
November 12th, 2009 at 5:31 am
Thanks for your reply, Mr. Keniger.
I’ll take a look at Panic’s Coda, then, to see if it convinces me.
So far, I still have the feeling that I’ll miss GoLive as I have never missed any other piece of software with the sole exception of Jump Zampoli (buying an old Mac to play it and some old Brøderbund CD-ROMs for children is an option I’m considering).
November 12th, 2009 at 9:32 pm
I reckon I’m part of a surprisingly large group who use GoLive CS2 with Leopard, in preference to GL9 or the hated DW. MM seems to be becoming more unstable with every upgrade of Mac OS X, so how about some lateral thinking and an upgrade of the plug-in for now?
November 12th, 2009 at 10:46 pm
Reading all of these posts, there’s a common thread, which is that there are a whole lot of GoLive fans out there, many of them disgusted with Adobe for making such a stupid and arbitrary decision to drop a such a great app, me included. Even after all of the so-called improvements (feature creep) to DW, I still prefer Golive 8.01 for it’s interface, feature set, and plugins, especially MM2. So I’m wondering, what will become of Golive? Hey Adobe: why let a good thing die so ignominiously? Sell it, or give it away, or something. No doubt, there’d be some takers. Just a thought.
November 13th, 2009 at 5:36 pm
Now, I am not a code warrior or anything, but I have spent hours upon hours changing sites from GoLive to DreamWeaver, I am doing another this week. The code GoLive writes is a mess! I too was a rabid fan of GL and I thought the web programers I know that were using DreamWeaver were unduly critical of the code GoLIve wrote, but now that am mucking in it again I do agree with them. It is nightmarish at best to deal with compared to the clean, lean code DreamWeaver writes and its CSS support is fantastic. I guess it is matter of what is important to work with, what you are comfortable with or to expand and learn other ways of dealing with web code. I suspect as the WWW progresses more towards xhmtl and the degradation of html code then GoLive will be less and less useful, perhaps to the point of being non-functional. I suspect that too is why Adobe chose to march forward with DreamWeaver.
I too was very upset to have to learn a new program when Adobe switched, and to have to recode 50 or so sites. But as I work with CSS more and more and CMS more and more, I realize that I depend less and less on the actual program that creates the webpages, I can use TextEdit if forced too. More I know how to hand code (again not that I am great at it nor do I take the time to do it day by day, DreamWeaver saves me a ton of typing) the less I like GoLive. I don’t even have it installed anymore. Sorry to be such the nay-sayer, but honestly folks there is life after GoLive and it is a good life. Nothing to do about it anyway, GoLive is dead.
I will check out MM when it makes an appearance, if it is good I will pay for it again (I have bought and an upgrade and gotten a few clients to buy it) but I am also designing my sites so I don’t depend on it. It can be frosting on the cake, but not the cake
November 14th, 2009 at 5:36 am
I feel somewhat chastened after reading Gabrielle’s comments. I must agree that DW is at this point _is_ a more forward thinking app. After all, the last decent version of GL (8.01) was circa 2005, and a lot has happened since then. Further, I admire Gabrielle for gutting it out and re-coding all of those sites. What a job! I might add that all of our new “static” sites are written in DW. Having said that, my argument is with Adobe, not with DW, or Gabrielle, for that matter. You’ll remember way back when that Adobe purchased “Cyberstudio” from a company called Golive (a really great group of folks, btw), because at the time Adobe didn’t have a decent HTML editor (remember PageMill?), and then they renamed Cyberstudio Golive. But when Adobe purchased Macromedia, something had to give: either DW or GL. Realizing that the Macromedia execs still had clout within their new company, I tried my best to find out what Adobe planned to do with GL. The party line was that they’d “merge” the best features into DW, and GL itself would become a “DW-LIte”, whatever that meant. But as we all know, none of that happened. In essence, Adobe tossed GL over the side in the middle of the night without a ripple. All predictable, logical and a good business decision from the point of view of the suits at Adobe, but for me, a Photoshop user since version 1, and a classmate and admirer of John Warnock, that one decision, was the turning point when it came to my trust in Adobe. That is, the suits had won and the artists and innovators inside of Adobe had lost. Since then, there have been so many instances of arbitrary moves like these, or shifts of functionalities, all designed to bolster sales of one or another of their apps, especially the Creative Suite. Trying to keep up with what I consider to be Adobe’s bottom-line oriented capriciousness (they’d call these moves well-reasoned and appropriate) has become such a time-hole for my colleagues and me, that we’ve come to the conclusion that a only a truly dynamic CMS can be the best all-around solution for the future of the web. So we’ve gone ahead and built one for ourselves, and our clients! DW, GL, or whatever you choose, won’t matter at all to us eventually. As far as the business side goes, we intend to stay under the radar, knowing that we’ll be ants to Adobe’s elephant, but for the time being we’ll be free from Adobe’s monopoly and cynical manipulations at the expense of people like Gabrielle, and especially, Rob Keniger. Kinda like Microsoft, yes? Cheers.
November 15th, 2009 at 4:18 am
I can relate to nearly all comments posted recently. I moved from Pagemill in early days to Cyber GoLive, to Adobe’s GL. Like many of us, I was furious when Adobe removed DC after v6. I have nearly 80 or so websites using mysql. Furious. Eventually, I revisited DW, having rejected the early versions as horrid. But, with CS4, with learning new integration with mysql/php, I have to say (no stones please), I am a convert. I build all my new sites in DW now, am converting nearly 50 older sites as I have the time, and as the client can see a benefit and afford the upgrade. I loved GL. I have moved on to DW, and (ducking) I can do more in DW than I could in GL. The fly in the ointment is missing a decent menu. For now, I use GL8, create a MM menu, copy the code into an include. A bit cumbersome, but doable. I’ve tested at least 10 other menus, and they are no where near what MM is. So, any time you’re ready, Rob, we are too.
No pressure. 
November 17th, 2009 at 3:31 pm
Will someone PLEASE buy GoLive from Adobe and start developing it again? As a one-man shop, I don’t have the time to convert EVERY SINGLE Javascript action on every page of every site I’ve authored to something that Dreamweaver likes (especially MM2!). I know it’s been a while, but Adobe dumped this on us like a ton of heavy stuff, and I can’t stand the Dreamweaver interface! I thought, by now, that Adobe would have rolled over some of the better features of GoLive into Dreamweaver, but no such luck. I’m now faced with the Snow Leopard upgrade…and as most posters here seem to indicate, I probably won’t have more problems with GL CS2 than in Leopard. BUT, I was born and raised on GoLive, born and raised on its plugin interface (which MM2 handles admirably), and Dreamweaver is NOT the answer, no matter how much Adobe tries to make me switch.
November 18th, 2009 at 9:31 pm
hiya again
Ok whilst waiting for the “port” to Dreamweaver, can anyone recommend a pluning that get get us by in the time being?
What i need really is a system where i can make image menu system , and the webassit ones are just aweful!
Thanks
November 18th, 2009 at 10:50 pm
I too have been a long time user of GoLive. I have worked in DW but find the interface very irritating and not as intuitive as GL. Not that I can’t learn to be more efficient, but I need the features of MM. I can’t afford the time porting sites over. So for now I will create my menus in MM2 and use GLCS2. Then include as others have mentioned, in DW. I wish for the merging of GL & DW but I have to move forward. When the new MM comes out I’m there! Keep on working at it. PLEASE! Thank you for listening to a long time HTML coder and ‘just an artist’ triving in a computer world. Bring us the MM beauty.
November 24th, 2009 at 11:22 am
Well it’s now been three months since the last update on the status of MM3—and in a week it will be December.
What’s the latest?
What are the Vegas odds on MM3 being out before the end of the year?
November 30th, 2009 at 3:22 pm
It would be nice to have somewhat normal status updates. It keeps a layer of communication, even if they are short, but it gives us ammo and reasons to keep the faith as you work. It takes but a few minutes to write a quick blog entry to inform us, but in doing so, you let people know how things are going and garner more support as you progress.
December 3rd, 2009 at 5:58 am
Hey, gabrielle… I still use GoLive and I can find no messy code there. And I come from times BEFORE PageMill, when I did sites with BBEdit (in code, that is).
Of course if you let GoLive INCLUDE scripts inside each page, code will be “dirty” or, at least, messy. But changing preferences on that is easy and then each page gets more tidy, less complex, with just a link to the .js file containing the scripts.
As for other code, I found GL to be as messy or as tidy as any other competing product. Perhaps, yes, being already left aside, it hasn’t grown up to meet the latest standards (especially in XHTML, as you point out), but, still, it is my program of choice. It writes nice code (for me), and its user interface is WAY better than that of DW.
And about Rod’s post (november 14th), I can only stand up and applaud. Brilliantly written. Dotted every “i”. My hat off.
January 27th, 2010 at 9:09 am
Is it ready yet? The last update I can find is August. Have you guys given up? GoLive is getting buggier and buggier and with no support, I am having to force myself to switch over – however slowly – to DW. Do we have to give up on MM? Or is there still hope?
January 27th, 2010 at 1:19 pm
I posted an update in December: http://menumachine.com/blog/2009/12/development-update/
March 30th, 2010 at 6:04 am
Can’t wait to get my hands on what is going to be the best menu maker around and one that works with Dreamweaver. I have used 3 different types of menu machines for Dreamweaver and they all suck!. Clunky and very limited. I have to work with other people on my sites and they do not have GoLive so I am forced to use other menu makers so they can edit the menus when I am unavailable. Waiting patiently.