![]() It's not going to improve to a point which is going to satisfy you, me or others, its like one of these bits of software from yester-year which plods along, apealing to fewer and fewer, before disappearing into oblivion due to lack of support. Brackets has some very nice features but they are not being improved.īack to DW, why bother when you could be concentrating on better options. Adobe just seem totaly out of their depth or at the very least dis-interested in this particular market. I mean what use is that when you need to use the browser tools to inspect an element. It's split window has a poor implementation, its live view is poor unless you like Adobe specific code injected into the browser. Take brackets for instance, another Adobe web-app, its barely changed since its release, left to 3rd party sources to produce useful plugins, which is not so bad but its UI is woefully behind the time now, you can't change the file tree to your prefered color scheme or your liking. What I guess we need to kmow is why they are persisting with a dead product, is there actually some logic to it, that we are overlooking. They don't have good market share like their other products do. ![]() I honestly don't think Adobe are interseted in this kind of market any longer as there are too many other players and its conceeded defeat. If on the other hand it is to make it into a professional product, then are the resources and backing from Adobe available, because if not, it is a no go for the future. If it is to remain on the same track, (used mainly by beginners and casual users) then there is no point in us hoping for anything more. I don't use CC, so any 'here is a years CC subscription' is worthless. Replys or discussions with any Dw team member are now none existant. Anyone thinking they can influence anything, forget it. I found some members of the CAB and prerelease insulting, and lacking in knowledge, (though not all). As I have said previously 'why should I bother'. I see no mention of a stand alone css prefixer though, which as I have said previously makes Dw a 'do not use' for many.Īs for the pre-release, and testing. ![]() Plus css and the js api's, at what stage in the recomendation process will a spec be included in code hints, as many specs are WD's but stable and well supported by browsers.ĭw's code editor could use a lot of work, but the little information provided does not allow me to make any judgement. As html5 contains much more than most people think, and in my experiance, much more than the Dw team think. I was pleased to read that code hinting would be for ALL html5, css and js, but I would be interested to know what is ment by 'ALL'. I started a discussion regarding the blog post, but so the team does not miss my post in that discussion, here it is again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |