|
|
|
[
Permlink
| « Hide
]
Zach Garner - 04/Dec/07 02:13 PM
I've got to say, if this could be done without adding undo strain on the project, this would be a great feature for an IDE that's careening dangerously close to eclipsing that other popular web development tool.
See also http://www.aptana.com/trac/ticket/6491
 . @ Jeff L
I agree with you, this shouldn't be viewed as a high priority. Just adding a vote for it. I agree that there are more important issues, still a huge number of people are using a WYSIWYG interface for updating site's with only a minute knowledge of html.
I believe there is a gap (market) between users who code and users who use a CMS to update there site. A Simple WYSIWYG would be great . Even integrating Kompozer as a preview would do.
I think this should be given a high priority, especially if AJAX is going to compete effectively with FLEX. A wysiwyg would bring a lot more people into the promotion and development of AJAX as a whole. As it stands right now, there is a severe learning curve to AJAX and development is still too expensive when compared to FLEX. From a marketing standpoint, if AJAX is going to really take off, it needs a wysiwyg. This is just my 2 cents.
I second this. I think the simpler way to implement this is to support only XHTML strict, and follow W3C specifications only. Take a look to:
Vex or eZing Builder Voted. I spent the day gleefully coding with Aptana, finally content to have put that "other" IDE behind me. But when it came down to it, the absence of a "design mode" with WYSIWYG functionality is simply too much for me to make the switch. I am usually coding 6-8 sites at the same time - I am too busy to not need a more graphical environment to supplement my hand coding. Sorry Aptana, I hope you solve this sooner than later, because if you don't, I'll find another open-source project that will. And I'm sure many others will too.
I like http://sourceforge.net/projects/pweditor/
It's implemented in IE and Firefox versions, so I imagine it could be embedded in Aptana....
Alternatively, I have a javascript I use with some E-Mail forms on webpages that does WYSIWYG in IE/Firefox... maybe it could be worked into Aptana? As coder I as most disagree to this request. If the intellisense is good enough, I will never need a WYSIWYG editor. Certainly not if it's not perfect.
@ Jeff L, Glen Ainscow, Jon Ege Ronnenberg
I agree, vote against. Aptana focuses on helping Web programmers write clean code quickly, which is why I like it. WYSIWYGs will always compromise mark-up quality, which is something I'm glad to see Aptana not supporting. I vote against it - if you want to make a website you should learn how to write the code - otherwise make something with Open Office Documents or M$ Word - Aptana should spend time implementing useful features for real developers.
I completely vote for it. WYSIWYG is becoming a new standard for a reason.
Limiting design, development, and production of internet sites strictly to the perception of those who only see code is severly limiting the progress of creativity for those who think differently. It also seems to be a bit of an elitist attitude by denying people other ways of being creative. I don't feel this follows the open source mentality at all. The idea that a wysiwyg interface is for the inexperienced or unlearned is false. Wysiwyg is not a crutch, it is a tool. I am a 'real' developer (both design and web applications), and currently use both aptana pro and dreamweaver.
I find that I use aptana probably 75% of the time, and much prefer it. However, for some projects dreamweaver's wysiwyg interface is a real time saver, and I find that even if I have to clean a little auto-generated code overall efficiency is improved. There are other members of my team that are more 'visually' oriented, and can, for instance, lay out a web page in dreamweaver, then clean the code faster than I can type (and I am not too shabby). So, in light of my own experiences I vote for this. The priority of this feature for me is not high - possibly this can be integrated as a plugin, so those not needing the functionality can use aptana without the resource overhead? I have used other editors (WordPerfect, FrameMaker, etc.) but WordPerfect's code and format views allowed you to switch quickly between both – marvellous. If you were a fast typist you could use the code pane but for stuff like adjusting the columns of tables, margins, graphics, etc. the format view was the best. So I vote for it. We need an Open Source Creative Suitcase (pun intended) that is WYSIWYG and code oriented, to go with Gimp, Inkscape, and all our other tools.
For a beginner it is more easy learn HTML with WYSIWYG. Every developer was in the past a beginner. There are always several ways to get a result. Why not with an wysiwyg integration in Aptana?
JBossTools (http://jboss.org/tools
) already integrates Mozilla composing capabilities with Eclipse to obtaing a pretty good WYSIWIG editor, but it is JSF/JSP oriented only, but, since it is LGPL maybe Aptana could use its code base as a starting point and enhance it for plain Jaxer, ASP, PHP, Ruby, etc. Now that many web pages are interactive, they are more like applications. We can take a lead from software developers. While it is no doubt still possible to design and implement a window or dialogue entirely by cutting code, most developers these days use a form designer, which writes the code silently behind the scenes. Of course, the functionality behind the buttons and sliders is still coded in an IDE because that is the appropriate mode. So I disagree with those developers who attach some kind of moral superiority to code cutting. When the task is visual the appropriate tool is also visual. When the task is text, the appropriate tool is an editor. And, in the best of both worlds you can switch freely from left- to right-brain mode, whichever is easier for you.
So I am with the people who want Aptana Studio to be more like a visual and textual IDE. Why exactly are some of you AGAINST a WYSIWYG capability? If you don't want it, don't use it.
Here are some arguments for WYSIWYG: I am all for it, WYSIWYG is a really important part of web design and developing rich applications.
When you are developing a visual program, a visual editor is as useful as code completion and syntax highlighting. I vote against this feature. WYSIWYG in almost useless unless you develop non-tableless sites. Aptana is about programming and should not emulate Dream Weaver.
Dream Weaver yes, FLEX no. The WYSIWYG for FLEX is very powerful and reduces development time considerably. Microsoft has also jumped into the game with its XAML and silverlight. This is where everything is moving. AJAX needs to keep up.
It really depends on whom the app is intended for. If you want to draw a larger user audience than professional designers, then a WYSIWYG interface is mandatory. There are millions of people who build and maintain their own websites; I am one of them. We can't all learn to speak HTML fluently, it's simply too time-consuming and the time consumed just isn't necessary if the interface can do the work for us. I need to spend my time on developing my site content, not the code.
I just this evening discovered and downloaded Aptana. It looks attractive and very professional just from the appearance. But as soon as I discovered that it has no WYSIWYG editor, within a minute of the first load, forget it, I'm uninstalling. Too bad, it looked like a good tool for me. Almost none of us is capable of visualizing the exact preview of the code. The time-consuming (endless if you are a perfectionist) iterations of coding and previewing is eliminated by wysiwyg. Instead of uploading and refreshing the browser you just swap the views by a click. And more - you can cut, copy and paste more easily in wysiwyg! Not agree?
In my work I receive news by email and put it up on the web. It would save a lot of time if I could just copy it as it is. I could be more sure of not loosing any formattings. Without wysiwyg + drag'n drop I have to read the text and find out eash <i> and <b> and so and scroll in two windows and write more code than necesary. Wysiwyg can be used as a creative tool! The optimist see posibilities in eash problem. The pessimist see problems in each posibility. i definitely vote for it. it's almost need no reason.
if you only want a clean code support, you can alway use notepadd++, why need aptana? c'mon. how many of us did not use any wysiwyg tools? only codes? i work alot using dojotoolkit. you can make layouts using only code. but did anyone? most always use to separate tool, one for design, one for code. even myeclipse with visual editor cost only $31.75 a year, why aptana wont? cheers |
|||||||||||||||||||||||||||||||||||||||||||
 |
|
Enhancement
Reviewed
Unprioritized
Add support for a WYSIWYG editor in Aptana