Post by: Mrious_be on February 26, 2007, 12:37:56 PM
Haven't done it yet myself (will do after this post) but there's an upgrade for Camino available on versiontracker and probably somewhere also.
Post by: krissel on February 27, 2007, 03:37:14 AM
Post by: krissel on February 27, 2007, 04:15:22 AM
Post by: Xairbusdriver on February 27, 2007, 10:49:17 AM
I already assume I've maid misteaks, what I want iz two kno the corekt verzhun! 
I'd download it and see, but I'm still in the process of making space available on this drive! Where does all that stuff come from?
Post by: Dick Miller on February 27, 2007, 12:12:35 PM
Post by: Xairbusdriver on February 27, 2007, 09:20:40 PM
1. Get the spel chequing to work?
2. Make the tool bar smaller ( less tall )? ( Why not use the same 'Customize Menu Bar' options like FF and most Mac apps?
)OK, with that solved:
3. How do I add some of the dozens of search engines to the search bar? Google is not the only game in town.
I discovered a manual and none too handy method of blocking certain scripts with the 'hostperm.1' file, but that requires shutting down Camino and editing the file.
Shutting down an app to change a pref is not really 'user-friendly' IMHO. Maybe I;'ve got it backwards, however. Just turn scripts OFF and see which sites break. Shut down, add the site to the 'hostperm.1' file. Start up and find the next site or part of same.As suspected, the look is more Mac like. I can now get to each end of a text box with the normal Mac arrow keys. URLMP works just fine with Camino, of course, so there was no need to import any bookmarks.
Typing is slow with animated gif's running, at least with a lot of them, as when in the reply page here. That was noted in the rtfs.
I'm off to check about any add ons that might be usable...C U L8r.
Don't see any listed at the Camino/Moz site. May be some info in the forums.
Post by: krissel on February 28, 2007, 01:01:55 AM
Hmmm, I don't have any slowdown in typing the main reply page...
I have iType and/or Typeit4me that pop up suggestions or correct my boo boos.
Post by: krissel on February 28, 2007, 02:17:19 AM
A page on my cablevision site wouldn't load but does in the 1.03 release.
Also I was not taken to the main forum after creating a new thread and hence hit 'post thread' twice. Then could not open the extra thread or delete it til after a few tries.
Guess the beta is not quite ready yet.
Post by: Xairbusdriver on February 28, 2007, 08:52:21 AM
QUOTE
pimpmy...
Two of the most over used words of this generation. 
Everything has to be related to sex or self.
But I'll give the link a try ( when nobody's looking
).Have to remember that 'excuse' for double-posting.
The 'Readme' mentioned the possibility of slow typing with animated gifs and even Flash enabled. It might also me related to my rather sluggish system. All I know is that there is no delay in FF.
I'll try Camino again today. My main concern is the reverse way of handling javascripts; enable all and never know what's happening instead of limiting all and allow the ones that are needed. Complete disabling will indicate some are needed, but you may not be able to tell which ones and even when you decide on a useful one, one must copy the call/site, shut down Caminio, edit the 'perf' file, and start up again. I fear that Camino suffers from the all too common "Macs are not a big enough market" syndrome. OTOH, I detest the way FF can't use already built-in OS resources just because Windows doesn't have them!
Post by: krissel on March 02, 2007, 03:48:37 AM
QUOTE(Xairbusdriver @ Feb 28 2007, 09:52 AM) [snapback]120469[/snapback]
I fear that Camino suffers from the all too common "Macs are not a big enough market" syndrome.
That's definitely not the case. Camino is made strictly as a Mac browser only, using all the Apple designed codes. If anything it is more Mac-like than Firefox.
Post by: Xairbusdriver on March 02, 2007, 10:44:58 AM
And the way it handles blocking javascript is the most blatant example. Actually, the way it does it is exactly the way every other browser does it, by default. Exclude everything or enable everything. The first method destroys the usefulness of many sites because they use javascript instead of more standards compatible techniques. Since the user simply sees the broken site, s/he may be tempted to turn js back on. But that takes one back to all the vulnerabilities that is present in js! Again, that is what ever browser I know of is designed, not just Camino.
But FF, with add-ons like NoScript, provides the user with the ability to selectively turn on only the javascripts that are needed/wanted on a per-site basis. In other words, it's an 'opt IN' method. True, Camino can effectlively mimic this behavior if the user is willing to manually edit the 'pref' file. But that will require quite a lot of quiting and restarting Camino. Not a very useful way when surfing the internet, IMHO.
Same methods are used for Flash as far as I know. Again, this is handled by an add-on in FF. Adblocking? Somewhat easier in Camino but not nearly as comprehensive as in FF with add-ons.
My point is that while Mozilla allows this kind of plug-in capability in FF, it apparently cannot or is not used in Camino. Or it is capable but there are no developers willing/able to provide any plug-ins. The result is a fast, Mac based browser that is no more customizable than Safari, and, in fact, not as well supported as Safari. All of which I suggest is because of the smaller market segment of Macs, which is then divided among FF, Opera, Safari and Camino ( and others? ).
Being 'more Mac like' is not the same as being better or equal to something.
