Slashdot Mirror


Dreamweaver MX, Flash MX With CrossOver Office

AstroDrabb writes "It seems that CodeWeavers' CrossOver Office 2.1 now supports Dreamweaver MX and Flash MX. So for those who have been waiting to ditch MS Windows because of these two apps, now is your chance. The announcement from CodeWeavers can be found here and the changelog can be found here. The list of supported applications is also getting pretty impressive."

13 of 333 comments (clear)

  1. Hold your horses about switching by Heartz · · Score: 5, Informative
    Both of the apps only have a bronze medal From the crossover site :
    Bronze Medal The bronze is awarded to applications that install and run, and that can accomplish some portion of their fundamental mission. However, bronze applications generally have enough bugs that we recommend that our customers not depend on their functionality. The most important aspect of a bronze application is that CodeWeavers makes a firm commitment to bring all bronze applications to the silver level in future releases of CrossOver.
    You can't have that if you want to switch and are highly dependant on it. Users will just get frustrated. Both of the apps only have a bronze medal
    1. Re:Hold your horses about switching by jeremy_white · · Score: 5, Informative
      We have a policy to always start an application at Bronze level.

      We know the reality of Wine - it can be very promising, but fail in important ways. So, we try to help our customers be cautious in their adoption. For example, Photoshop, which actually is one of the very best performing applications in CrossOver (it is in heavy use to make major motion pictures), started at Bronze, and is now only at Silver.

      With that said, we have found Dreamweaver to be very complete, with only a few remaining bugs. And we have yet to find a bug in Flash... (but we didn't try as hard there).

      Cheers,

      Jeremy White CEO CodeWeavers

  2. Re:Dreamweaver == bloat by PakProtector · · Score: 5, Informative

    Obviously you know nothing about what CSS is, or are just stupid. Let me enlighten you.

    In the beginning, there was the Web.

    All was good. Bandwidth was, on average, low, but sites were small and to the point, and loaded quickly.

    People began to use frames and many other things, marring the content with style.

    But then, in this dark hour, when web pages loaded slowly and all hope was lost, a light appeared in the darkness.

    It was CSS.

    CSS is based on the idea that content, which is the actual information of a web page, should be entirely seperate from the style of a web page, which is defined by the CSS. If you disable CSS, the webpage should load as plain text and pictures and form elements, no spiffy navigation bar here, no sidebar here. Something that text-readers can understand and that loads very quickly. The CSS file also loads quickly, and by combining the two into one a web page can be made small, while still full of content and aesthetically pleasing.

    --

    Edward@Tomato - /home/Edward/ man woman
    man: no entry for woman in the manual.
    "Qua!?"

  3. Re:Excuse me, by ElWelshWizard · · Score: 2, Informative

    Dreamweaver does not build annoying bloated webpages.

  4. Re:Dreamweaver == bloat by Anonymous Coward · · Score: 2, Informative

    DreamweaverMX was a pretty horrendous application. But Macromedia got their act together with MX 2004 version which was released not too long ago. Old tags were depreciated and new standards took their place, such as complete CSS-based wysiwyg code generation. [table] tags are not default anymore, although I suspect you can revert back to standard HTML 4.1 transitional if you want. It has better integration with FireworksMX 2004, and x-browser compatibility development has greatly benefited.

    Now, the bad part is that DW/FW MX 2004 are very unstable and bloated compared to the previous MX versions. Of course, if you're doing serious web development, Dreamweaver is not for you, but for casual users and people who aren't keen with site design and CSS, it could solve many problems.

    MM_Script JS was quite possibly the worst thing in Fireworks and Dreamweaver had to offer. I haven't checked for its presence in the new version, but avoid it at all costs if you want your sites to be robust and unbloated.

    Also, the content tags you speak of can be easily turned off in the preferences. Both in MX and MX 2004. Your rant about Flash presence is offtopic.

  5. Re:I'll ditch windows by Savage-Rabbit · · Score: 2, Informative

    I'll ditch windows when someone comes up with an OS that supports ALL the applications and games I currently run, and is faster or has some other 'thing' that would be beneficial to me.


    This did exactly that for me, of course the downside is that you have to shell out a thick wad of cash. These Wine ports are nice if you are doing relatively light-weight stuff but as soon as you are working on a major website or a 100mb+ sized Photoshop document with a few dozen layers it is crash city. I prefer native software any day which is why I bought a Mac. That having been said this sort of software will certainly help generate Linux converts since it will more than do the trick for most people.

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
  6. Dreamweaver MX has been running under Wine before by joost.be · · Score: 2, Informative

    I can't recall exactly when, but I remember setting up dreamweaver MX under Wine a while ago (let's say about a year). It is listed in the Wine Application DB, It worked pretty well back then, the only problem was that it crashed when you used the color selection box. I no longer use it now, I've come to my senses and use VIM.

  7. Re:We really need a Dreamweaver under GNU/Linux !! by Anonymous Coward · · Score: 1, Informative
  8. Re:Excuse me, by ajs318 · · Score: 1, Informative

    Good HTML means separating content from presentation as far as possible. So you write the text first, then decide what it should look like. Then you create a style sheet, and base BODY and P on what the majority of the document should look like - leaving you to define .classes for exceptional SPANs and DIVs. If you're really smart, you'll name them after what they represent {<SPAN CLASS="PASTDATE"> and <SPAN CLASS="FUTUREDATE"> are more meaningful than <SPAN CLASS="BLUE"> and <SPAN CLASS="ORANGE"> and will survive a "refit" better - you will still have dates in the future and dates in the past, but they may well not be blue and orange anymore.} Of course, this involves thinking, which humans can do {with varying degrees of effort} but machines can only pretend to do, and in a fashion that looks more limited the longer you study it.

    Anyone can use a stencil, but that does not make them calligraphers. The whole idea of Dreamweaver is fundamentally flawed - attempting to impose a type of user interface onto a task which is, by its nature, unsuited to that user interface. You can't use a point-and-drool system to place precise insertions into text and have it work reliably. It reminds me of a gadget that clips onto the neck of a guitar and allows you to fret and strum the strings using piano-like keys. You can never hope for that to sound better than a guitar played the traditional way, except maybe for a rather limited range of music, and it certainly won't make you into Steve Cradock.

    On the web, there really is no such thing as What You See Is What You Get, because What You See Is Not Necessarily What Everyone Else Gets. Also, Dreamweaver uses <font> tags all the time - how long have we had cascading style sheets now, for chuff's sake? - and I find its "trendy" lowercase tags too hard to spot in a non-context-sensitive editor like vi or pico. {Sometimes it's nice to have a few eye-stabbing caps ..... it's not as if any known browser gives a damn nor is ever likely to ..... if <p> and <P> started meaning different things one day, pretty much the whole Internet would break. Beside which, whatever conceivable use would that ever be? Except making money for monopolistic corporations ..... um .....}

    --
    Je fume. Tu fumes. Nous fûmes!
  9. Re:Excuse me, by Anonymous Coward · · Score: 1, Informative

    >and I find its "trendy" lowercase tags too hard to spot in a non-context-sensitive editor like vi or pico

    I guess W3C thought lowercase tags were pretty trendy too when they came up with the XHTML spec.

  10. On 'trendy' lower case tags. by jonathan_ingram · · Score: 5, Informative

    4.2. Element and attribute names must be in lower case

    XHTML documents must use lower case for all HTML element and attribute names. This difference is necessary because XML is case-sensitive e.g. <li> and <LI> are different tags.

    From here.
  11. Re:Why crossover only works on the converted: by gatzke · · Score: 2, Informative


    Option 3:

    Cheapbytes Linux $3
    OpenOffice FREE

    Option 4:
    For those that only have to read email attachments, just use Crossover plugin with the free word viewer and free excel viewer.

    Other options, win4lin, vmware. I have used both vmware and crossover and I have always been quite happy.

    Linux is about choice and freedom.

  12. Re:My main concern by Anonymous Coward · · Score: 1, Informative

    What in the name of fuck are you talking about?

    Do you seriously think that they are using Tcl/Tk to draw the widgets of Windows apps running under Wine? It was used for the configuration tool and nothing else (and I'm not even sure about that these days).

    That's one serious fucking misapprehension you're labouring under.