Copy link to clipboard
Copied
I really don't know what do to after using Muse.
I started using the Dreamweaver with StudioMx but few months ago started using Muse.
Muse......March 26, 2018 we will release the final feature improvement release ...
Adobe doesn't even recommend Dreamweaver.
Should I come back to Dw?
Really need you advice.
thank you for reading,
James
Coming back to the original question about Dreamweaver. It's a copy-paste from another discussion, but I do hope you understand why.
Like I promised, I checked with the senior management about the future of Dreamweaver, and their answer was that they see no reason to stop developing the product. Dreamweaver will continue to exist, period.
I understand that no amount of reassurance will suffice, but I do want to put other Dreamweaver users visiting this post at ease.
I am marking my answer as corre
...Copy link to clipboard
Copied
W_J_T wrote
tiff_meek wrote
The left brain and right brain operate in two very different ways. We each have a propensity for left brain thinking or right brain thinking. Creatives or tech-heads. Some people lean heavily one way or the other. Some can slide between the two. Either way these are all legitimate 'ways of being' and should be respected. I have met many people who cannot fathom the design space. And I have met many people who struggle with highly technical stuff. It isn't because they are lazy or don't care. It's simply because they are that kind of person.
Sorry, I do not agree with the whole concept of different mindsets separating the two and creating "an unsurmountable barrier". If people want to they can indeed learn. People may be better in this or that, but they can learn as they desire and are willing to put forth the effort towards.
---
As a side note: Why are you writing your thesis in the Dreamweaver forum? Why not compile all these thoughts and much more and post them in the Muse forum since you desire Adobe to fulfill your needs of a visual based web design tool. Do you want or expect Dreamweaver to facilitate these desires?
I didn't remotely suggest "an insurmountable barrier" let alone write it. I have no idea why you seem so personally invested in jumping to conclusions about what I write. It's as if you want to attack me as a person rather than sticking to the topics/debate at hand. What is your motive? This isn't a pissing contest my friend.
I touch type at 100wpm so it's pretty easy for me to type a lot in a short space of time - if that's what you sarcastically refer to as my 'thesis'. I make no apologies for it. If for some reason the length of my responses offends you then I'd suggest you ignore them. It's a free country. Well at least it is where I live.
Just in case you hadn't noticed, I'm simply responding to questions being asked of me by people on this forum (yourself included). I originally posted because the conversation was in regards to Muse users and I simply joined in with an alternative argument. Isn't that what a forum is for?
If everyone here is prepared to discuss only the topic of the original post, that's fine with me. But please don't ask me to do it when nobody else is (yourself included).
To answer your last question. I don't care if Adobe creates a tool for designers in Dreamweaver, in a re-imagined version of Muse (with a different name/functionality), or whether it breaks new ground with something completely different. I'm here to express that we NEED tools for developers and WYSIWYG tools for designers, and it would probably be even better if we had a tool that worked for both. And I'm here to express that no matter what anybody thinks, these tools will come. There is no way for there to be advancement in the web arena without these technologies coming at some stage in the future. Cheers Tiff
Copy link to clipboard
Copied
I think you took that way too personally, before going on your rant.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
tiff_meek wrote
The left brain and right brain operate in two very different ways.
That's an old myth dating back to the late 1800's. I used to work in brain imaging. Unless you have some underlying pathology, trauma or genetic condition, you're using both halves of your brain equally or everything.
Now whether or not you have a "head" for math, spelling, design, languages, music, coding or whatever comes down to exposure and personal enthusiasm for the subject. I can certainly understand a lack of enthusiasm for coding but please don't tell me for one moment that your brain precludes you from doing it. It just 'aint so.
Copy link to clipboard
Copied
https://forums.adobe.com/people/Nancy+OShea wrote
tiff_meek wrote
The left brain and right brain operate in two very different ways.
That's an old myth dating back to the late 1800's. I used to work in brain imaging. Unless you have some underlying pathology, trauma or genetic condition, you're using both halves of your brain equally or everything.
Now whether or not you have a "head" for math, spelling, design, languages, music, coding or whatever comes down to exposure and personal enthusiasm for the subject. I can certainly understand a lack of enthusiasm for coding but please don't tell me for one moment that your brain precludes you from doing it. It just 'aint so.
Check out Jill Bolte Taylor, she has an incredibly fascinating book, and you may find that there is more to the story than meets the eye. Nevertheless, humans have a tendency to be logical, focused and analytic versus broad-minded and creative, and ultimately this has to come from the brain. Scientists have many theories regarding how and why that might be (nature vs nurture etc) but I personally think we are yet to fully understand the process. Although my statement might have been a little antiquated in its language use (sorry about that), the overall concept of technical vs creative in the workplace still applies. Cheers Tiff
Copy link to clipboard
Copied
I can accept that people are more suited for one thing than another, but I cannot accept that it is impossible to learn how design works or how code works. Doing both is probably not suited fully to the majority of people, but if a designer can run their own business, deal with clients, finances, and manage a workforce, then they must be able to not only think logically, (code) but also think abstractly, (design).
No one who only thinks in one direction would be able to function fully in any profession.
Copy link to clipboard
Copied
I can accept that people are more suited for one thing than another, but I cannot accept that it is impossible to learn how design works or how code works. Doing both is probably not suited fully to the majority of people, but if a designer can run their own business, deal with clients, finances, and manage a workforce, then they must be able to not only think logically, (code) but also think abstractly, (design).
No one who only thinks in one direction would be able to function fully in any profession.
Agree.
Copy link to clipboard
Copied
pziecina wrote
I always wonder when I hear people say, "I cannot code, my brain does not think that way", or "I cannot design, I don't understand it", are saying those things simply because they have been told them, or don't want to understand them.
Left Brain - vs - Right Brain ( Degenerative disease - vs- learning HTML / CSS )
How I May Move Forward From Muse
Sigh.
Copy link to clipboard
Copied
W_J_T wrote
pziecina wrote
I always wonder when I hear people say, "I cannot code, my brain does not think that way", or "I cannot design, I don't understand it", are saying those things simply because they have been told them, or don't want to understand them.
Left Brain - vs - Right Brain ( Degenerative disease - vs- learning HTML / CSS )
How I May Move Forward From Muse
Sigh.
I guess that's why they are Muse users - brainless - well those that want to compare someone confined to wheelchair and telling them 'come on walking is easy' to someone being able bodied and yet too lazy to learn code........humm the mind boggles, really.
Copy link to clipboard
Copied
W_J_T wrote
Left Brain - vs - Right Brain ( Degenerative disease - vs- learning HTML / CSS )
How I May Move Forward From Muse
Sigh.
Personally I have given up on the Muse users who don't want to code at all. You can only help people who want to be helped.
As for those willing to learn a little, I'm willing to discuss if their requirerments could be met, and willing to help, though as far as Dreamweaver is concerned no one in this forum can say if or what Adobe or the Dreamweaver team is willing to consider or do. So even if ex-Muse users do join in, they must remember everything we discuss or suggest concerning Dreamweaver itself is purely hypothetical.
Copy link to clipboard
Copied
W_J_T wrote
pziecina wrote
My answer to that was to put myself through a graphic design diploma course, and work part time for a graphic design company. A little extreem maybe, but only then did I see the flaws in the thinking of both, and realise that often we talked about the same thing but used different words, (the term, lost in translation, describes the problem).
Admirable & Applaudable.
Impressive. I have always believed to be better at anything you need to understand the process forwards and backwards. If more people would work harder to understand the other facets which come before and beyond them, then not only could they do their own jobs better but the overall process and industry would be in a better place. That goes for web, print, you name it. But sadly most people remain compartmentalized in their approach and thinking, which stagnates the understanding and process around them.
I started out in the newspaper industry, collating papers in the night, then moved to the dark room, then onto the art bench doing hand paste up for the paper and the printshop. Then my boss bought an Apple computer. It was a tiny thing with a hard drive large enough to put together just one page of the paper (in black and white). Then we had to clear the drive and start again. They were incredible days. Exciting because the technology was so new in the world. I used the first versions of Adobe's software, and of course, QuarkXpress. There were no courses to take, it was all too new. Instead I had to take the user manual home and study it, and then go to work and see if I could apply it. Use my own initiative. I'd get butterflies going to work because it was just so damn cool. And so I became a 'graphic designer' without even realising it. Then the internet emerged. That blew my mind. I bought some of the first little books that hit the shelves in my town on coding and studied them at home, and started making my own sites. And so I became a 'web developer' without even realising it. Names meant nothing back then. It was simply all new and exciting. GoLive came along at some stage and that was fun. For many years I was a graphic/web designer/developer, as well as many other things as well. Each time computers and software (and my skills) would advance, my organisation would offer a new service to its clients. Of course the web didn't have all the functionality it has today. It was very simple. But back then even the simplest site seemed like a small miracle. My broad skillset in a new technology made it super easy to get work. Unfortunately, as technologies progressed it got harder and harder to keep up with everything. I was using drum scanners and manipulating/colour correcting images in Photoshop, designing logos in Illustrator, doing graphic design in InDesign, learning 3D software, experimenting with FileMaker, creating websites with code and GoLive etc... it just went on and on. I realised then that I had to bite the bullet and specialise a little more, otherwise I would be a jack of all trades and master of none. But those years of creating websites and doing graphic design were fundamental in giving me an understanding of how the web works, and made it super easy for me to subsequently work alongside web developers because I knew the constraints they were dealing with. For many years, while I couldn't write code efficiently anymore, I could certainly read it and understand it for the most part. This enabled me to design according to the capabilities of the code. And it enabled me to speak with developers using their own language. These days I'm way out of touch with what is possible on the internet at the high end. But at the local level, and for the vast majority of jobs, I still have a great understanding and can still work hand in hand with developers, which creates efficiencies in the workplace. I think it's a huge advantage to have an understanding of design as a web developer, and to have an understanding of code as a graphic designer/web designer (UI designer etc). It has certainly been an advantage for me in my career. Cheers Tiff
Copy link to clipboard
Copied
tiff_meek wrote
I started out in the newspaper industry, collating papers in the night, then moved to the dark room, then onto the art bench doing hand paste up for the paper and the printshop. Then my boss bought an Apple computer. It was a tiny thing with a hard drive large enough to put together just one page of the paper (in black and white). Then we had to clear the drive and start again. They were incredible days. Exciting because the technology was so new in the world. I used the first versions of Adobe's software, and of course, QuarkXpress. There were no courses to take, it was all too new. Instead I had to take the user manual home and study it, and then go to work and see if I could apply it. Use my own initiative. I'd get butterflies going to work because it was just so damn cool.
You became a graphic designer because you were young, motivated and interested and needed to move on and use the current ways of producing artwork, that being DTP. You made time to read the bulky Xpress manual, play around with the program and save a page of information to your 3.5 inch floppy discs. In those days you couldnt even save a hi-res image to a disk until the Syquest arrived, a much bigger disc.
tiff_meek wrote
Then the internet emerged. That blew my mind. I bought some of the first little books that hit the shelves in my town on coding and studied them at home, and started making my own sites. And so I became a 'web developer' without even realising it. Names meant nothing back then. It was simply all new and exciting. GoLive came along at some stage and that was fun. For many years I was a graphic/web designer/developer, as well as many other things as well.
You became a web-developer because you were still relatively young, motivated and interested and needed to branch out from DTP to give yourself a better opportunity of surviving in an increasingly competitive and cut throat world. If you didnt code back in those days you were probably using all the wrong techniques and appraoches to web-development like absolutely positioned <divs> which fooled people into thinking they could build a website until a professional web devloper pointed out to them their website didn't work. Those people who only wanted to use absolutely positioned <divs> didn't want to know as it upset their cosy 'drag and drop' world but they were selling themselves and their client short. Those people who did want to know and didnt want to sell their cleint and themselves short, learnt to code.
tiff_meek wrote
Unfortunately, as technologies progressed it got harder and harder to keep up with everything. I was using drum scanners and manipulating/colour correcting images in Photoshop, designing logos in Illustrator, doing graphic design in InDesign, learning 3D software, experimenting with FileMaker, creating websites with code and GoLive etc... it just went on and on. I realised then that I had to bite the bullet and specialise a little
more, otherwise I would be a jack of all trades and master of none.
You were getting slightly older, less motivated and learning became harder. I'm 59 + a few months and if someone told me I had to learn web-coding now because it was key to if I survived or not in the workplace I couldn't do it. I'm less motivated, less able to take onboard new concepts and quite frankly dont have the desire to do so UNLESS its a game changer. Young people SHOULD learn tro code IF their intention is to have a long-term career in web development. Those older than 50 and are just starting out with a view to a career in web-develoment are just kidding themselves. They might make a few bucks here and there and the odd few may get lucky, but its over once you reach a ceratin age in this game.
These days I much prefer to use the knowledege and skills I have accumulated over a number of years web developing in a consulting capacity and learning provider rather than actually sitting down and building a complete website which I find largely boring now. I still do it when called upon but its not something which particualry interests me any longer.
Copy link to clipboard
Copied
<humour>ok.. I understand now .. why ? the polemics... sass... node... git... gulp... grunt... </humour>
Copy link to clipboard
Copied
https://forums.adobe.com/people/B+i+r+n+o+u wrote
<humour>ok.. I understand now .. why ? the polemics... sass... node... git... gulp... grunt... </humour>
To me they are not game changers, mostly 'ignorant' developers using a sledge hammer to crack a nut in a lot of situations because its the current trend. I guess those that are insecure need to find more complex ways of doing simple tasks to justify their existence and desire to be taken seriously as someone who provides anything better than some amatuer can produce with one of Al's cheap and cheerful limited option extensions.
Copy link to clipboard
Copied
as I said .. it was humour... come down...
I see that you still stand up on your rock... "None shall pass"...
what exists around is buffoonery, or is an excuse for exhibition ... I am pure ... I am the one who drinks rainwater and feeds on olive leaves ...
and to always stay in humor ... I like this scene ... Monty Python And The Holy Grail- The Black Knight - YouTube et celle là aussi Monty Python - Constitutional Peasants Scene (HD) - YouTube
Copy link to clipboard
Copied
and what's about this one... Monty Python - "Not Dead Yet" Scene (HD) - YouTube
Copy link to clipboard
Copied
https://forums.adobe.com/people/B+i+r+n+o+u wrote
what exists around is buffoonery, or is an excuse for exhibition ... I am pure ... I am the one who drinks rainwater and feeds on olive leaves ...
Given my frequent posts about the liking of a alcoholic drink or 2, I dont think so. Nothing buffoonery or exhibitionist about me. if youre mistaking that for being passionate then that's your perspective.
Copy link to clipboard
Copied
still on your rock...
Copy link to clipboard
Copied
There in no disgrace in being a rock. Id rather be paired up with a rock than a weasel.
Copy link to clipboard
Copied
two time this week that you became insulting...
Copy link to clipboard
Copied
I was talking in general terms, not about you specifically. Its like treading on egg shells around here.
Copy link to clipboard
Copied
osgood_ wrote
tiff_meek wrote
I started out in the newspaper industry, collating papers in the night, then moved to the dark room, then onto the art bench doing hand paste up for the paper and the printshop. Then my boss bought an Apple computer. It was a tiny thing with a hard drive large enough to put together just one page of the paper (in black and white). Then we had to clear the drive and start again. They were incredible days. Exciting because the technology was so new in the world. I used the first versions of Adobe's software, and of course, QuarkXpress. There were no courses to take, it was all too new. Instead I had to take the user manual home and study it, and then go to work and see if I could apply it. Use my own initiative. I'd get butterflies going to work because it was just so damn cool.
You became a graphic designer because you were young, motivated and interested and needed to move on and use the current ways of producing artwork, that being DTP. You made time to read the bulky Xpress manual, play around with the program and save a page of information to your 3.5 inch floppy discs. In those days you couldnt even save a hi-res image to a disk until the Syquest arrived, a much bigger disc.
tiff_meek wrote
Then the internet emerged. That blew my mind. I bought some of the first little books that hit the shelves in my town on coding and studied them at home, and started making my own sites. And so I became a 'web developer' without even realising it. Names meant nothing back then. It was simply all new and exciting. GoLive came along at some stage and that was fun. For many years I was a graphic/web designer/developer, as well as many other things as well.
You became a web-developer because you were still relatively young, motivated and interested and needed to branch out from DTP to give yourself a better opportunity of surviving in an increasingly competitive and cut throat world. If you didnt code back in those days you were probably using all the wrong techniques and appraoches to web-development like absolutely positioned <divs> which fooled people into thinking they could build a website until a professional web devloper pointed out to them their website didn't work. Those people who only wanted to use absolutely positioned <divs> didn't want to know as it upset their cosy 'drag and drop' world but they were selling themselves and their client short. Those people who did want to know and didnt want to sell their cleint and themselves short, learnt to code.
tiff_meek wrote
Unfortunately, as technologies progressed it got harder and harder to keep up with everything. I was using drum scanners and manipulating/colour correcting images in Photoshop, designing logos in Illustrator, doing graphic design in InDesign, learning 3D software, experimenting with FileMaker, creating websites with code and GoLive etc... it just went on and on. I realised then that I had to bite the bullet and specialise a little
more, otherwise I would be a jack of all trades and master of none.
You were getting slightly older, less motivated and learning became harder. I'm 59 + a few months and if someone told me I had to learn web-coding now because it was key to if I survived or not in the workplace I couldn't do it. I'm less motivated, less able to take onboard new concepts and quite frankly dont have the desire to do so UNLESS its a game changer. Young people SHOULD learn tro code IF their intention is to have a long-term career in web development. Those older than 50 and are just starting out with a view to a career in web-develoment are just kidding themselves. They might make a few bucks here and there and the odd few may get lucky, but its over once you reach a ceratin age in this game.
These days I much prefer to use the knowledege and skills I have accumulated over a number of years web developing in a consulting capacity and learning provider rather than actually sitting down and building a complete website which I find largely boring now. I still do it when called upon but its not something which particualry interests me any longer.
It sure helps to have an understanding of code. But at the same time I have to say that I've known web designers who know nothing of code but still have an understanding of what's possible. Ultimately, once we have the right software, it will guide us intuitively so that we are aware and able to use every bit of functionality available to its best advantage. I am putting this out into the universe so that it will come true!!!
LOL! Yes you're probably right though it kills me to say so. These days as a Creative Director for a large national organisation my role is expansive and different every day. From my perspective, with my eyesight slowly failing with age, and my brand new capacity to get migraines if I spend too long at the computer, I now thank my lucky stars if I don't have to spend the entire day looking into a computer screen.
Cheers Tiff
Copy link to clipboard
Copied
tiff_meek wrote
LOL! Yes you're probably right though it kills me to say so. These days as a Creative Director for a large national organisation my role is expansive and different every day. From my perspective, with my eyesight slowly failing with age, and my brand new capacity to get migraines if I spend too long at the computer, I now thank my lucky stars if I don't have to spend the entire day looking into a computer screen.
Cheers Tiff
Happens to us all. I started on Quark 3.2. I don't know what version we are up to today but when I used v7 a couple of years ago it was the same as v3.2 give or take a few useless and largely uneccessary additions. About the biggest innovation Quark ever added to its core program was drop-shadows by default........that was a 'trend' too, which I never bought into either.
Copy link to clipboard
Copied
Copy link to clipboard
Copied