Re: Cursor Issues to be resolved

OK, points taken.

To be clear though, I am not involved in the callisto project!  I'm 
just a fan.

Mike


On Wednesday, October 9, 2002, at 01:25 PM, Christian Stocker wrote:

> On Wed, 2002-10-09 at 18:39, Michael Slattery wrote:
>> I am in favor of scope reduction in terms of browser support.
>
> in the really short term, we will only support mozilla...
>>
>> The rest will sound like scope explosion, or at least a swap-out:
>>
>> I still think the short term solution for the cursor is not to try and
>> develop a fake cursor in parallel with the moz efforts.
>> For all of the xopus efforts, their contentEditable doesn't do what
>> this group wants.
>>
>> I believe Christian can get a cursor working, but I feel that if Moz 
>> is
>> promising something as well, then we should all burn our calories on
>> something else.
>
> It will take at least another 3 months until 1.3 is out and i'm not 
> sure
> if contentEditable will be in that until then.. This is too long for a
> lot of people...
>
>> My personal favorite: let's improve the pop-up supplemental forms we
>> already use!   Efforts here will be useful even after the browsers fix
>> the cursor.
>>
>> I think the short term solution is to use pop-up forms the way
>> callistocms works.  I know it is a touch more clumsy, but we can give
>> the user the option to toggle between in-line and pop-up editing, and
>> it is still 500% better than a conventional web app, with all the
>> latency and reloads.
>
> You're demo is really nice (still too much reloads IMHO :) ) and BXE 
> has
> something similiar with "Edit Source", if we could do that nicer/better
> integrated, this would be a great help for a lot of people (thinking of
> "slow computers" for example :) ). On the other hand, we want a WYSIWYG
> Editor and callistocms' solution is near on that, but not what we're
> dreaming about, therefore putting our resources in that is not 
> something
> we'd really like to do. But as the code is already out there, it would
> maybe not be a big task...  And all this doesn't mean, it can't be
> integrated in BXE and with a nice switch to turn it on/off, it 
> shouldn't
> disturb anyone.
>
> chregu
>
>
>> The main trade off is that in-line is more elegant when content is
>> being entered in a serial fashion - the idea of the default or 'give 
>> me
>> this element next after I get out of this one'  behavior is brilliant!
>
>
>>
>> The pop-up forms is more efficient when trying to relocate an
>> individual element, for example, or changing the element type.
>> Already we have to popup secondary forms when metadata or additional
>> content is needed, like images or links.    So adding the content to
>> primary elements in a pop-up isn't that big a leap.
>>
>>
>>
>> Please try out
>> http://admin.demo.callistocms.com/.cms/
>> demo:demo
>>
>> and tell me what you like and hate about it.  I will dig in and help 
>> to
>> get the pop-ups working if there is buy-in here.
>>
>>
>
>
> -- 
> bx-editor-dev mailing list
> [email protected]
> http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
>

-- 
bx-editor-dev mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev