Adrian Sutton wrote:
Did you notice in your development of an WYSIWYG HTML editor things
from the specification that
- were very difficult to implement?
- were missing in the HTML language itself to make it easier to
control the editing?
There are a couple of things to note
On Wed, 21 Feb 2007, Andrew Fedoniouk wrote:
I agree that HTML DOM is not suitable for WYSIWYG editing.
I beg to differ. It is true that an editing style sheet may be
needed to avoid problems with delivery style sheets that use the
display and visibility properties to hide content, or which
At 17:15 -0500 UTC, on 2007-02-21, Adrian Sutton wrote:
[...]
When people get into writing they want to focus purely on what they are
writing and they don't want to have to think for a second about how the
authoring tool they are using wants them to work. If you want the tool to
succeed you
On Wed, 21 Feb 2007 22:38:48 +0100, Elliotte Harold [EMAIL PROTECTED] wrote:
... most of the tools that
have been built have been built by programmers with more experience in
WYSIWYG word processors than in semantic markup. The semanticists who
have built GUI tools have not had the necessary
Interesting thread (including various sub-ravels thereof).
Suppose in a semantically charged, but markup-impoverished medium such as
the textual narrative (constituting the majority of the content of the web
as we know it), we seek to build the word processor that generates not only
the
One of the other options we have is to reverse-geocode the lat/lon and
then return different levels of granularity based on that information
42.351036, -71.049378 = 332 Congress St, Boston, MA 02210
So sites like fandango that would only require a zipcode, we would only
need to provide them a
Ryan Sarver wrote:
The biggest problem with this implementation is that it requires an
additional service on top of standard GPS.
I wasn't envisaging any geocoding services. In my example, the address
would be one the user had entered, and (assuming the machine has GPS at
all) the browser
Gerv, this is great feedback. I agree that it's important to think of
fixed devices also being able to produce location information,
especially without needing any type of location-sensing hardware or
software.
In terms of user's being able to give different addresses, I feel that
is the job of
On Thu, 22 Feb 2007 15:07:29 +0100, Ron van den Boogaard [EMAIL PROTECTED]
wrote:
On Wed, 21 Feb 2007 10:47:50 +0100, Charles McCathieNevile wrote:
As people got printers and desktop publishing a
few people made the crazy multi-font unreadable pages that were all
the rage in the mid-80s
Ryan Sarver wrote:
I tried to search through the archives to
see if the discussion had come up before and didn’t find anything, so
please forgive me if it has.
Something slightly relevant has been discussed in the context of wf2 [1]
We have been successful in exposing it through the
Since I am a newbie in this regard, what do you think about passing something
like User-Geolocation in the header of the request so that the server has
access to the information as well?
Obviously this is subject to some settings and privacy control on the UA, but
it would allow the server to
- Original Message -
From: Dave Raggett [EMAIL PROTECTED]
To: Andrew Fedoniouk [EMAIL PROTECTED]
Cc: Adrian Sutton [EMAIL PROTECTED]; Karl Dubost [EMAIL PROTECTED];
whatwg@lists.whatwg.org
Sent: Thursday, February 22, 2007 3:09 AM
Subject: Re: [whatwg] Authoring Re: several messages
On Wed, 21 Feb 2007 20:31:11 -, Ryan Sarver
[EMAIL PROTECTED] wrote:
var location = window.getLocation();
For some applications location given in format other than lat/long may be
more useful and less privacy-sensitive.
For example name of the city might be good enough if you order
I'll start:
* XForms Tiny's |calculate| attribute
* |required| attribute with expression values
(formerly XForms Tiny's |needed| attribute)
* |valid| (formerly XForms Tiny's |constraint| attribute)
* |disabled| attribute with expression values
(formerly XForms Tiny's |relevant|
| input type=number name=cc1_4
| select name=cc1_exp_month[...]/select /
| select name=cc1_exp_year[...]/select
don't you see cc1_exp_year as a bit of a problem? i hope webforms3 addresses
the name hacking that has become standard in web frameworks to flatten multiple
db
15 matches
Mail list logo
