Safari 2.0 -- will we be compatible?

willeffects · 2005-04-13 21:53:11

http://weblogs.mozillazine.org/hyatt/ar … tml#005905

It supports this method. Will xinha work with that? Anyone here a beta tester for Safari 2.0?

Will

gogo · 2005-04-14 00:30:05

Interesting. It would be nice if we could support Safari too, but it won't be before V1.0 (of Xinha), by which time hopefully the browser specific code might be able to be split out into separate scripts - I want xinha.js, xinha-ie.js and xinha-gecko.js, and one day then xinha-safari.js (or xinha-khtml.js if that functionality is passed back to khtml for konq etc).

I do have PearPC around here somewhere so I *could* at a pinch do that development, but it would be better for somebody who has a real (much faster) Mac to do that.

niko · 2005-04-15 03:20:55

yeah, that would be great!
i could use konqueror all the time then

...but it will take some time till this is finished i think... and wysiwyg-editors would be two-times complex then (a 3rd browser... puh, much to test )

...abut the xinha-ie and xinha-gecko:
i like the idea too - but doesn't get reading the code much more complicated? (and writing too ofcourse)

gogo · 2005-04-15 07:14:37

niko wrote:

...abut the xinha-ie and xinha-gecko:
i like the idea too - but doesn't get reading the code much more complicated? (and writing too ofcourse)

Well, I don't think so, as long as it's abstracted in the right way. Sure for small differences just roll them togethor, but I'm thinking for the large bits of code (whole methods) that are specific to one or the other, to cut down on the weight for loading into a single browser.

guillaumed · 2005-04-16 16:40:33

gogo,

I also think that the code should be defined into a global xinha.js and specific xinha-xxx.js!!! It's simplier to understand and like for foreign languages some specific users can validate one implementation even if they didn't write it..

Can you tell us when you planed to do that?

willeffects · 2005-05-11 21:17:53

Latest Safari has designMode. Does that mean it will work for us?

http://weblogs.mozillazine.org/hyatt/ar … tml#007962

HTML Editing
Safari 1.3 supports HTML editing, both at the Objective-C WebKit API level and using contenteditable and designMode in a Web page. The new Mail app in Tiger uses WebKit for message composition. You can write apps that make use of WebKit's editing technology and deploy them on Panther and Tiger.

gogo · 2005-05-11 21:23:57

will: almost certainly won't right now, Xinha is full of things to work around problems in both IE and Mozilla as while similar in implementation of contentEditable/designMode they are different - I expect Safari will be different again and require some specialised code.

It's a bit difficult for me to develop for safari, seeing as I don't actually have a mac.

niko · 2005-05-12 10:41:24

I'm just installing OSX 10.3.9
And I found a demo:
http://www.xs4all.nl/~hhijdra/stefan/Co … table.html

...of course our priority should now be to release a stable xinha, then implement support for safari.

kimss · 2005-05-12 14:33:47

Getting a minimac would probably solve alot, the pricetag has become low to enter the mac marked, ive been thinking of purchasing one of my own just to be able to check webpages and stuff for the mac, having pages and scripts that work in all browsers has become a must lately.

Nice going Niko with you OSX, but as you mentioned - a v1.0 releasy of Xinha would be much more appretiated...

Mvh,
Kim Steinhaug
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Easy CMS - Et brukervennlig publiseringssystem - Easy Webshop - Nettbutikk med krefter

Last edited by kimss (2006-02-27 19:23:12)

willeffects · 2005-05-13 03:08:57

Here is some information on how they got safari to work somewhat in htmlarea

http://www.dynarch.com/forums/521

niko · 2005-05-13 04:39:31

nice, we should look at those changes!

...but before implementing safari-support we should think about a browser-specific-code-separation solution i think.
i have no idea how this could be done best...

willeffects · 2005-05-13 16:15:25

well although ideal code is ideal, the reality is Apple users are growing more and more pro Safari. So if we dont support it they are going to complain and blame our sites for not supporting them. Because of this I am much more interested in finding a quick fix. Though that is party because we are building a site that supports an Apple only software so its something I now have to face... (even though I have no Mac and no damn safari)

kimss · 2005-05-16 21:20:29

Have to agree there with willeffects, a quickfix is much better than a water-proof-fix in "near"-future, However there is a little problem, we need people who understand the core of xinha to work from a Mac to debug the problems.

But regarding the seperation of code for different browsers. Couldnt this be acomplished quite simple?

1. We need a browser sniffer.
2. Xinha looks mosltly organized, all is placed into functions.
3. Move all functions that are browser specific into own .js files
4. Let the sniffer load the correct js file

I may be missing some major things here, but it sounds very simple, atleast in my head.

gogo · 2005-05-16 22:52:00

Will & Kim: patches welcome.

willeffects · 2005-05-19 01:51:28

kimss wrote:

1. We need a browser sniffer.

I recently found this sniffer which seems to let us access any information we need. Maybe overkill but might be worthwhile http://www.dithered.com/javascript/brow … index.html

Will

kimss · 2005-05-20 09:47:51

Well, Im pretty satisfied using this one : http://www.webreference.com/tools/brows … cript.html
Its a load of code for just the simple tasks, but one could easilly pick out the lines to use for the detection needed.

Since I dont have a Mac Mini at the moment, I dont see a reason for me jumping into this at the moment, sorry Gogo, I dont have the time either for such large workloads on my spare time, however I will try as best possible to chip in on the smaller tasks - and I will keep sharing my thoughts with you people,

niko · 2005-05-24 01:48:39

I just got a post from Stanislas Rolland (the one who posted on dynarch.com) saying that he published his changes on sourceforge:
http://cvs.sourceforge.net/viewcvs.py/t … iew=markup

willeffects · 2005-05-25 15:10:28

Thats great. It doesnt look like too many changes. If only I had a damn mac (working on it) I could test it out...

gogo · 2005-05-25 17:45:58

Does anybody know why Stanislas is using HTMLArea from mishoo instead of Xinha? Is mish restarting htmlarea development?

mtmosier · 2005-05-26 21:10:16

gogo wrote:

Is mish restarting htmlarea development?

I'm not entirely certain this is mish, but it would appear so.

http://www.dynarch.com/projects/htmlarea/

wymsy · 2005-05-26 21:41:24

gogo wrote:

Does anybody know why Stanislas is using HTMLArea from mishoo instead of Xinha?

It looks like he is customizing a version of HTMLArea 3 for use as a module in Typo3, a CMS. Probably not related to whatever Mishoo is doing.

adam.jimenez · 2005-06-27 04:35:43

Is any xinha developer actively working on this or is it planned for a future version ie 2.0?

gogo · 2005-06-27 12:42:36

Nobody is working on it. There are no plans to do so, unless a keen developer with a mac comes along, or somebody buys me a mini-mac, or konq gets a 100% compatable content editable system.

mharrisonline · 2005-06-27 20:01:50

I don't think mishoo is continuing development. That site has been there a long time, and the forum is filled up with what seem to be unanswered requests for help http://www.dynarch.com/forums/17/page:11

wymsy · 2005-06-27 21:21:34

gogo wrote:

Nobody is working on it. There are no plans to do so, unless a keen developer with a mac comes along, or somebody buys me a mini-mac, or konq gets a 100% compatable content editable system.

I might take a crack at it, but probably not until after we get xinha 1.0 released. And I get a whole bunch of other stuff out of the way. Unless someone gets to it before me...

Xinha Discussion Forum

Announcement

#1 2005-04-13 21:53:11

Safari 2.0 -- will we be compatible?

#2 2005-04-14 00:30:05

Re: Safari 2.0 -- will we be compatible?

#3 2005-04-15 03:20:55

Re: Safari 2.0 -- will we be compatible?

#4 2005-04-15 07:14:37

Re: Safari 2.0 -- will we be compatible?

#5 2005-04-16 16:40:33

Re: Safari 2.0 -- will we be compatible?

#6 2005-05-11 21:17:53

Re: Safari 2.0 -- will we be compatible?

#7 2005-05-11 21:23:57

Re: Safari 2.0 -- will we be compatible?

#8 2005-05-12 10:41:24

Re: Safari 2.0 -- will we be compatible?

#9 2005-05-12 14:33:47

Re: Safari 2.0 -- will we be compatible?

#10 2005-05-13 03:08:57

Re: Safari 2.0 -- will we be compatible?

#11 2005-05-13 04:39:31

Re: Safari 2.0 -- will we be compatible?

#12 2005-05-13 16:15:25

Re: Safari 2.0 -- will we be compatible?

#13 2005-05-16 21:20:29

Re: Safari 2.0 -- will we be compatible?

#14 2005-05-16 22:52:00

Re: Safari 2.0 -- will we be compatible?

#15 2005-05-19 01:51:28

Re: Safari 2.0 -- will we be compatible?

#16 2005-05-20 09:47:51

Re: Safari 2.0 -- will we be compatible?

#17 2005-05-24 01:48:39

Re: Safari 2.0 -- will we be compatible?

#18 2005-05-25 15:10:28

Re: Safari 2.0 -- will we be compatible?

#19 2005-05-25 17:45:58

Re: Safari 2.0 -- will we be compatible?

#20 2005-05-26 21:10:16

Re: Safari 2.0 -- will we be compatible?

#21 2005-05-26 21:41:24

Re: Safari 2.0 -- will we be compatible?

#22 2005-06-27 04:35:43

Re: Safari 2.0 -- will we be compatible?

#23 2005-06-27 12:42:36

Re: Safari 2.0 -- will we be compatible?

#24 2005-06-27 20:01:50

Re: Safari 2.0 -- will we be compatible?

#25 2005-06-27 21:21:34

Re: Safari 2.0 -- will we be compatible?

Board footer