> The HTML tab would be the coolest and also the hardest (if not impossible)
> part to build. WYSYWIG with the ability to toggle between showing the
> source, or even showing the source for a particular tag.

    I think since Eclipse can use ActiveX control.Why not to use DHTMLEdit Control?

    
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaredcom/html/edcomdownload.asp

    
http://msdn.microsoft.com/library/default.asp?url=/workshop/browser/editing/mshtmleditor.asp


features list:
========================================================================================================

DHTML Editing Component Features
The DHTML component includes editing features that allow even novice HTML users to 
create sophisticated Web pages. Editing features include: 

  a.. Text formatting   Users can set character formatting, including font style, 
face, size, and color. Paragraphs can be justified and indented.


  b.. Editing   The component supports multi-level undo and redo commands. Users can 
use standard Cut, Copy, and Paste commands. Elements can be moved or resized by 
dragging. The component supports a number of keyboard accelerators.


  c.. Drag-and-drop capability   Users can drag any object, text, or element anywhere 
on the page. 
  Note   For an example of how to implement drag-and-drop functionality with the DHTML 
Editing Component as the drop target, see the HTMLDrop sample application. For more 
details about sample applications, see the Samples.htm file in the \SAMPLES directory 
where you installed the DHTML Editing Component SDK.

  d.. Absolute positioning   Elements in the document can be absolutely positioned �� 
that is, users can use CSS style attributes to set their location on the page with the 
equivalent of x and y coordinates. For more details, see Working with Absolutely 
Positioned Elements.


  e.. Search   The component can display a Find dialog box to allow users to search 
for text.


  f.. Hyperlinking   Users can define links and bookmarks in the text.


  g.. Images   Users can insert images into the document.


  h.. Table support   Users can insert tables and can add and delete columns, rows, 
and cells.


  i.. File management   Users can open existing .htm files from disk or from the Web, 
save them to disk, and print them. The document being edited can also be loaded from 
and saved to memory, allowing you to create custom client-server applications.


  j.. Context menus   The component allows you to create a context menu that users can 
display by right-clicking the document.


  k.. Access to the DHTML object model   The component allows access to the document 
using the DHTML document object model (DOM), which exposes a hierarchy of HTML 
elements from the document down to individual elements and their contents. 






----- Original Message ----- 
From: "Geoff Longman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 10, 2002 6:06 AM
Subject: [Tapestry-developer] Beyond Spindle


> So managing the files is a source of problems for newbies.
> 
> Spindle helps (as people tell me on a not-irregular basis) but there's a
> piece or pieces missing.
> 
> What follows is a "pie-in-the-sky" vision. Much of what I'll describe isn't
> doable (by me) right now either because
> there's no support in Eclipse, or because its beyond my abilities.
> 
> What spindle needs is a new editor. A sooper-editor!
> 
> look at http://www.asp.net/ in particular Web Matrix, download it, do the
> first tutorial!
> (warning. don't throw things, I just pointed you at the enemy)
> 
> I spent a few hours playing with it and while it is ASP and therefore sucks,
> the IDE interface rocks.
> You can drag and drop components onto the html editor part of the web-page,
> it has tabs for source, things get wired up as you go.
> A brief summary for sure, check it out or take my word for it.
> 
> I see a Spindle editor that has three tabs:
> WYSIWYG HTML - containing the template
> SPEC - the xml
> JAVA - the java file
> 
> The HTML tab would be the coolest and also the hardest (if not impossible)
> part to build. WYSYWIG with the ability to toggle between showing the
> source, or even showing the source for a particular tag. All the
> functionality currently supplied by the tabs on a Spindle editor would be
> available on this page as pop-ups. Or, perhaps available in an Outline view
> (Spindle's is really simple, navigation only).
> 
> I was looking at the ICE browser recently and they claim that thier
> presentation layer is abstracted from the rest. I wonder how hard it would
> be to implement an SWT version and add the WYSIWYG stuff. Pie in the sky
> though as ICE browser is closed source (and expensive!).
> 
> The SPEC tab would contain a much better XML editor than Spindle provides
> now. Code completion, suggestions, even pop-ups containing some of the
> current non-xml functionality. (Text editors in Eclipse are not my strong
> point)
> 
> And the Java tab would contain, of course, the sourcefile (if there is one).
> The cool thing would be hooking up all three tabs so that if, for example,
> you added a parameter and no such property existed in the java file, you
> could ask (or expect) to have one created. Closely coupling refactoring in
> there so if something changes in one tab, its either automatically updated
> in the others, or the user is given the option of picking and choosing what
> gets updated.
> 
> The next yummie part would be to have a "runtime" implementation of the
> Tapestry internals that's built to run in a development environment. I'd
> like to see the day when one creates a template, adds components, specifies
> the barest minimum amount of parameters (even leaving out some required
> ones), and you can still run the application! The app would open a smart
> browser-like window where you can navigate to all the pages, view the
> underlying template source, navigate the machine state, and if the runtime
> detects that a required parameter value is missing, prompts the developer to
> enter it.
> 
> The runtime stuff would make it possible to set parameters,paths etc with
> cool little popups as the machine state would be available.
> 
> This would also be great for debugging as you could change stuff on the fly.
> Kinda breaks with the spec-is-king paradigm. But,at development time, isn't
> the developer really the king?
> 
> There's a plugin for eclipse out there that records HTTP requests and plays
> them back as a debuggin aid (I forget the name). This would be useful in the
> sooper-spindle world as many pages are very context sensitve so it might be
> difficult or tedious, in some cases, to navigate in the 'runtime' tapestry
> to some pages. Or, a particular page might be hard to debug unless you
> entered this value here on this page and that value on that page first.
> Being able to record the session and play it back in the "runtime" Tapestry
> environment would be a great help! You could automate test cases!
> 
> In fact why not create a Tapestry Perspective in Eclipse that's "tuned" to
> operate with these editors. You could hide the whole Tapestry Project thing
> altogether.
> 
> I read somewhere that redmond spend something like 1.5 billion on the next
> version of Office. Ahh, if only we could do that!
> 
> 
> 
> 
> 
> Geoffrey Longman
> Intelligent Works Inc.
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
> 
N���޵隊X���'���u���)��Y�\�g�����������b�HzG(��M�^���u�ޖ�^�f��)��+-M�^���u�ޖ�^�X���(��~��zw���i����l���q���z���l�X��)ߣ�Z��-�'^��h��


Reply via email to