Once upon a time, at a time in my life when I was earning a living wage of a manner sufficient for a substantial software purchase -- and when I was, sort of, looking towards a possibility of possibly digging in with web development --  in that same "Once upon a time," I'd purchased a license for Adobe Dreamweaver (Dw) CS5.5, as well as purchasing a couple of eBooks about the Adobe Dreamweaver platform -- as in regards to it being both a web development platform and an element of the Adobe Creative Suite. 

Since that time, Adobe has released the cloud-based Adobe Creative Suite 6 (CS6) and the cloud-based storage service, Adobe Creative Cloud. Adobe CS6 uses largely a cloud-based application model, largely oriented towards Creative Cloud, as the latter being a cloud-based subscription service. In short, Dreamweaver CS5.5 -- though it is still supported -- may not be as well supported as it may've been before Adobe made the "Cloud switch." Specifically, Dreamwever CS5.5 is installed like an ordinary software application. Dreamweaver CS6, however, is installed like an "App from the cloud." 

Candidly, I'm none too mystified by Adobe's CS6 cloud architecture, though I would not wish to seem to defame Adobe for their having adopted such an application model. Sure, it would "Make sense" from Adobe's point of view, at least -- at least, insomuch as with regards to product marketing

Personally, I'd purchased a license to Dw 5.5 as it being a stable, professionally designed web development platform. I'd not expected it was going to be "Pushed to the cloud" by Adobe, however. Personally, in all candor, I do feel at least a little nonplussed for that design decision, on Adobe's part. I consider that have no need to install any of the additional Adobe Creative Suite applications. I've not studied at any of the latest, oh-so-hipster-friendly schools for "Design", and I'm not working in a professional design house of any such style.  In a pragmatic sense, moreover: For any single application in the Adobe Creative Suite -- whether or not excepting Adobe Dreamweaver, which I have been able to install, again, though only after having searched through my old laptop, to find the file containing the original Dreamweaver CS5.5 installer, which I'd previously download from the Adobe web site. Much to my sense of chagrin, the CS5.5 installer is no longer published by Adobe.

So, rather than setting about to adopt the entire Adobe Creative Suite, I would just as well prefer to seek an alternative in free/open source software, alternative to any of the Creative Cloud applications. Candidly, I've no desire to become too beholden to any item within the Adobe products platform. I have never been so much of a supporter of the Adobe monolith -- I'm even more noplussed by it, now.  Moreover, I've not any wish to subscribe to any single month's worth of Creative Cloud application access, if for accessing just a single software application. The complimentary cloud storage feature that comes along with the for-fee access -- that doesn't really sweeten it up to me, in any way. There's also Dropbox, as one provider of cloud-based, i.e. network-based storage service.

Although I am sorely nonplussed by Adobe's design decisions, towards CS6 -- namely, with my sense of simple angst centering on Adobe Creative Suite's latter day "Desktop as a service" kind of product model, and now I would wonder whether any more of the Adobe Creative Suite applications  are really so novel, after all -- but I know that there are alternatives to the Adobe products, alternatives that are available in free/open source software. Although those alternatives might not seem, not in every regard,  to have so much "Spit and polish" in comparison to the professionally designed and commercially supported Adobe Creative Suite applications, but personally, I don't imagine as if that could be so much a quality of the Adobe model, itself.  

Personally, I don't imagine as if there could be anything of any particular magic to any single corporation. I don't either feel a lot of a sense of goodwill towards Adobe's design decisions around CS6, considering that they've nearly abandoned the previous CS5.5 production model. To those of us us who have purchased, each, a legal license for a CS5.5 product, essentially we would now be pressured to either "upgrade" -- with the additional costs then involved of the Adobe Creative Cloud -- and that, if simply to have our own desktops in alignment with Adobe's own model, or else one must accept that those products in one's desktop platform are now, insomuch, obsoleted by Adobe.  Considering that the pricing model for those applications, in their CS5.5  editions, was really far from the "$5 clearance bin" model -- in other words, that one mush shell out a distinct amount of common currency, to legally purchase such a software license -- and considering, moreover, that "Upgrade" to CS6 is presented at no remarkable discount, I'm sure it may be swell for the new CS6 adopters, but I for one am through with following the Adobe product line.

I certainly have a sense of respect for the Adobe corporation, but I am sorely nonplussed by redesign of CS5.5 towards the CS6 "Cloud" model. Though I might think to center much of my angst on the design of the  cloud model itself, but my concern is moreso in how Adobe has now given a "Cold shoulder" to adopters of CS5.5 and previous editions of the Adobe Creative Suite. 

Although I am so nonplussed, but I have no desire to try to make any sort of an "Edge marketing" response to Adobe's own product model. I would simply not seek to extend of the Adobe platform, 

Considering Adobe Dreamwever -- originally, Macromedia Dreamweaver -- as it being a software application available only under a proprietary/closed-source model, inasmuch in a very practical sense:, Dreamweaver would not be compatible with the Debian Free Software Guidelines (DFSG). 

In that light, I've discovered that KompoZer provides a useful analogue to the Adobe Dreamweaver platform. I should not wish to harbor any sense of angst about Adobe, then, considering that there is that practical alternative to the matter that's been so much the source of the angst, in the matter's origins within Adobe's latter day decisions as with regards to software design and marketing, and that strange and vague term, "The cloud". 

So, I would not wish to share any much more about my own user experience with Adobe Dreamweaver CS5.5. Here are some succinct notes, however:

  • "Snippets" in Adobe Dreamweaver CS5.5
    • Useful small things. for entering repetitive markup within web page source code.
    • See also: Article by Greg Rewis namely focusing on the user interface of the Snippets Panel in Adobe Dreamweaver
    • Personally, I've considered using "snippets" simply for purpose of entering the repetitive text for 'sidebar' and 'endnote' blockquotes in an HTML document -- with not too much of an illustration being available about that, at present, it's a simple matter of HTML markup, Cascading Stylesheets (CSS) and web page formatting.
    • I am now therefore whether I should wish to extend on the Adobe Dreamweaver(r) Snippets file format.
      • Sure, that might seem like a simple thing, if that was the only element in my decision as such?
      • KompoZer provides an alternative web development platform. 
      • Candidly, I should no wish to go out of my way to make any extensions as I might add to KompoZer --- or to my own broader web development platform -- to resemble Dreamwever itself, or the Adobe Creative Suite.
      • ...although I've not researched the extensions API for KompoZer, "as of yet."
      • ......Kompozer It extends on Mozilla, though.
      • ......So, there's another good edge to it.
      • ......Because Firefox OS, B2G, Cairo UI toolkit, but also there's Qt, and Linux, Common Lisp ... -- and although GIYF, certainly, Mozilla has developed quite a professional development framework, nonetheless, in Mozilla's continuing presence within the broader "Web browser industry"
      • ......So, I might have to choke down my  own preference of Qt to the Cairo UI toolkit, if simply to more consider adopting the Mozilla platform. In that much, it rather entails a decision -- effectively -- "GTK or Qt?" whether or not by way of the Cairo UI Toolkit. Although there may be a Qt implementation available of Cairo, but certainly most applications using Cairo would be using the GTK Cairo implementation.
      • ......and though KompoZer might not be the only alternative to Dreamweaver, in all of software platforms development, but insofar as KompoZer integrates any components of the Mozilla browser platform, there's Qt's Webkit as an alternative to the "web browser part" of the Mozilla platform.
      • So, there's also Qt.
    • The pathname of the user's Dreamweaver 'snippets' storage folder differs, (1) whether the host OS is running either Microsoft Windows XP or, alternately, Microsoft Vista or any later edition of the Microsoft Windows desktop operating system platform --consulting [xref] -- and (2) whatever is the exact edition of the Dreamweaver platform (e.g. ... CS 2 ...CS 5.5, )
    • In order to "synchronize snippets" -- such a trivial feature, sure -- a software program should endeavor to check whether the host OS is Microsoft Windows XP or not, before endeavoring to synchronize files into or out of the user's own snippets directory.
    • ...observing also [xref] as in regards to that the 'snippets' folder is not created under the user's configuration data folder until when the user would have added a snippet to the user's own Dreamweaver configuration.
    • Lastly, there's something about a UI configuration API for Dreamweaver Extensions, publishing some functions for the Snippets Panel
    • Analogy: 'Snippets' in the Eclipse IDE
    • Further work, in a thesis sense?
      • "State of the art," in web development?
        • "Web apps"
        • Free open source software => Phonegap => Cordova .... 
        • Intel XDK
        • see also: Coffeecup's web-based interface layouts
      • Towards further applications of the Qt toolkit
        • , by Derek Molloy
        • ARM microcontroller architectures
        • GCC on Microsoft Windows - CygWin, MinGW, and proprietary alternatives
        • Bundling for compiler toolkits - C and C++
        • Qt on the Microsoft Windows platform
        • Qt on other ARM platforms, including mobile thin client platforms.
Small thing, to adopt an alternative web development platform? it does entail some broader decisions though.