What is happening with the MediaWiki Wave project? Have you guys heard
of that? WYSIWYG for MediaWiki with all of wave's features could be a
starting point for this idea.
On Nov 19, 2:54 pm, SantaBrígida
wrote:
> I guess the closest we are getting towards this dream is with the Code
> Snippet Gad
I guess the closest we are getting towards this dream is with the Code
Snippet Gadget. Search for a wave with the tags 'code', 'snippet' and
you shall find it. The wave ID is googlewave.com+252By2RZbMagM
Yours,
Luciano.
On 18 nov, 23:57, Olreich wrote:
> Or, have the live update only happen when
Wow! What a response! Thank you :)
I have read the full discussion now and Im not sure I got everything,
since Im a bit too tired, but...
You said that WYSIWYG-editing might be hard if you are several users
working on the same page
- Possible solution: A function that lets you highlight/cut out/m
Perhaps a better use of resources would be to add these "missing"
layout/formatting features directly into Wave? Improve the existing WYSIWYG
features of Wave, in other words, without giving up and reimplementing it
elsewhere? Many users of a web publishing tool may find the editor
capabilities i
It looks like I was the only one that was especially concerned with
WYSIWYG or gadgets. I think it is wise to focus on approaches that
take advantage of as many of the Wave tools as possible. So you guys
have a point about the emphasis on robots. Maybe another more general
suggestion might be to
A gadget for display makes sense, a gadget for editing essentially
skips the entire idea of collaborative editing (WYSIWYG editing makes
it much more difficult to do things collaboratively, as that's a ton
of rendering without canvas). I disagree with WYSIWYG in general
though, as I've used Dreamwe
Seems like a good idea to me. Wave API does seem vaguely inappropriate
now that we're talking about design rather than whether or not the API
can handle it.
On Nov 19, 12:04 pm, Jason Livesay wrote:
> Obviously, there is more than one valid and useful approach to this idea of
> website editing in
On Thu, Nov 19, 2009 at 9:04 AM, Jason Livesay wrote:
> in a Wave. I just wanted to mention again that I personally would put more
> effort into the gadget and WYSIWYG side of things than to the robot and
> markup side of things. I feel
So, I don't mean to dissuade anyone from working on thin
Obviously, there is more than one valid and useful approach to this idea of
website editing in a Wave. I just wanted to mention again that I personally
would put more effort into the gadget and WYSIWYG side of things than to the
robot and markup side of things. I feel that web development has rea
Or, have the live update only happen when the HTML is valid (the
entire web could be improved by forcing validation xD). Though that
might cause some SERIOUS overhead for the robot.
On Nov 18, 9:52 pm, cmdskp wrote:
> And have some nice DOCUMENT_CHANGED tag and attribute auto-completing
> done by
And have some nice DOCUMENT_CHANGED tag and attribute auto-completing
done by the robot. =)
The main problem is nested content and how when one user is maybe
working on one section of the IFrame it suddenly jumps around because
another person has inserted an incomplete tag above - could be
disturb
Great idea. I think the best method of editing would be to have a HTML/
JS/CSS syntax highlighter (Robot). A gadget (essentially just an
iframe pointing at a temp-website with the data in it) showing a
rendered version of the web-page based upon the current code. This
will enable the web-page code
12 matches
Mail list logo
