and the alternative to PDF in office 2007/vista will be Microsofts own format (can't remeber the name). Microsoft will be very sorry to it's customers because they really, really wanted to support a format which is known to the user and x-platform (PFD) but were prevented to do so by a potential lawsuit ?
Verything works fine in breezy (except the card-reader which isn't supported by the kernel at all).
Breeze works like a charm, and i guess once the beta hickups of breeze are fixed it'll run well on this laptop. it's just that the beta (somewhere around flight 4) started to have problems with wither gnome-session or the private instance of dbus which causes several other (gnome-related) problems.
I can second that (the parent). i am running dapper on 2 machines which are frequently updated. on the laptop: the power manager fails which is a pitty. dbus seems to have problems and on both machines (the other one is a 2.4ghz pentium workstation) gnome-session fails upon login after every update (the installation on the desktop computer is plain vanilla without any tweaks). i have to remove loads of ~/.gnome* ~/.gconf* files and login again to get rid of the problems doesn't work every time).
Also, i see that gparted bundeled with ubuntu is version 0.1 (it's in the admin menu by default) which is quiet behind the current "stable" release.
I really hope the ubuntu team isn't rushing out a release which would harm its reputation. I really like ubuntu!
Many companies will not be able to install Vista with all the bells and whistles on their current systems. Home users and early adopters will "beta test" the new features after Vista's release and when Vista hits SP3 the companies will be ready to use all the "tested" and mostly fixed features.
from what i see by using XULRunner, you most probably don't have to wait for a release (unless you need specific platform integration features like minimize to tray, etc.).
There is enough stolen M$ source code around that this won't help much. willing hackers will just exploit other problems for the next (say) 5 years or so.
Security by obscurity. It won't help, but make a lot of knowledgeable customers unhappy.
i fail to see the difference of a webbrowser initiated and a scripted request to a dynamicly generated response.
In any way, permission must be checked, the script shall now work on request data nor send data back to a client with insufficient permission.
Nothing to see here, move along...
-S
i have had the exact oposite situation. i've bee using RH, SuSE at my job and been using primarely debian at home. when i got that acer travel mate i had a hell of a time getting debian sarge/testing to support my hardware (i had to apply 5-6 kernel patches first).
on the other hand, ubuntu was installed in approx. 1 hour and it supported all hardware out of the box (things like bluetooth, firewire, wifi, irda, the buggy intel video card [including accel support], etc.).
ubuntu is now my default linux on the desktop, it is not as stable as debian because they seem to use patches relatively early if a certain piece of hardware is commonly used.
BTW: ubuntu has a hardware database and they seem to force code into their release that is most probably used, not the most stable code tough.
i'd recommend tinyMCE: http://tinymce.moxiecode.com/. a true XHTML editor, works with mozilla 1.3+ (FF1+) and IE5.5+ and probably opera soon. it slim, cleanly programmed, modular and standards compliant. i have done a lot of research about html wysiwyg editors running in browsers and most of them are just a mess (code wise).
> As far as WW1 or WW2 engines, the required machining precision and > seals technology to make something like a Wankel rotary was just > not available. Cylindrical pistons and bores with circular seals are > much simpler.
Wankel built his first "Drehkolbenmotor" (en: "Rotating piston engine") driven boat during WWII, however it was a prototype.
Call it "Ajax", "Web 2" or event "Web 2 enterprise". it is still markup, some javascript and the ability to script http transfers. The full sets of technology was introduced with IE5, then adopetd by mozilla (and since 1.3 the XmlHttpRequest object is compatible with the one of IE) and now opera and safari 2 (khtml) have also a scriptable http client.
I see the ajax approach as a nice way to get surfers used to the idea that a web application does not have to refresh the whole ui upon any action the user takes. however, html is just not suitable for rich user interfaces, scripting the missing bits will be an effort every implementor has to take.
IMHO the real future for such applications lies in WHATWG, XUL and maybe XAML if this technology will be available with vista. Lets see if this is going to happen.
i am a web developer using FF since it was called (codename) Firebird. Fireforx and the mozilla suite (aka Seamonkey) crash about 1 time in a year and i am running it on windows/linux with a couple of extensions.
it's opensource...
Most probably, one needs just to alter the install.rdf (change required version numbers) to get it work somewhat-ish. if it doesn't you have all the source at your finger tips.
now which object does a sloppy coder get with: document.myElement.prop or even document.all.myElement.prop? i don't know, i have never tried it. but it will defenately screw up your code.
use document.getElementById() whenever you can
(this is implemented in IE5).
type about:config into the location bar. it gives you all the config options mozilla offers (not just the options in the dumbed down FF UI).
Cheers,
-S
... open and adhered to, it may not have that chance in the future.
I totally agree. An alternative Browser needs to take enough market share before the release of longhorn which might reder standalone browsers obsolete if IE has enough market share (more MS IE only services like update.m$.com to expect with longhorn).
probabyl by write protecting chrome/installed-chrome.txt and chrome/chrrome.rdf nobody will be able to install extensions. altough the files are downloaded and probably installed the etxensions will not get registered and therefore are not accessable from within moz/FF.
there is one problem, the user might choose to install an extension into his/her personal (home) chrome directory which will not be protected.
and the alternative to PDF in office 2007/vista will be Microsofts own format (can't remeber the name). Microsoft will be very sorry to it's customers because they really, really wanted to support a format which is known to the user and x-platform (PFD) but were prevented to do so by a potential lawsuit ?
FUD!
-S
no, its an acer Travelmate 4651LCi.
Verything works fine in breezy (except the card-reader which isn't supported by the kernel at all).
Breeze works like a charm, and i guess once the beta hickups of breeze are fixed it'll run well on this laptop. it's just that the beta (somewhere around flight 4) started to have problems with wither gnome-session or the private instance of dbus which causes several other (gnome-related) problems.
I can second that (the parent). i am running dapper on 2 machines which are frequently updated. on the laptop: the power manager fails which is a pitty. dbus seems to have problems and on both machines (the other one is a 2.4ghz pentium workstation) gnome-session fails upon login after every update (the installation on the desktop computer is plain vanilla without any tweaks). i have to remove loads of ~/.gnome* ~/.gconf* files and login again to get rid of the problems doesn't work every time).
Also, i see that gparted bundeled with ubuntu is version 0.1 (it's in the admin menu by default) which is quiet behind the current "stable" release.
I really hope the ubuntu team isn't rushing out a release which would harm its reputation. I really like ubuntu!
Many companies will not be able to install Vista with all the bells and whistles on their current systems. Home users and early adopters will "beta test" the new features after Vista's release and when Vista hits SP3 the companies will be ready to use all the "tested" and mostly fixed features.
:)
A smart move
Expect Microsoft to have another excuse for further delay.
from what i see by using XULRunner, you most probably don't have to wait for a release (unless you need specific platform integration features like minimize to tray, etc.).
There is enough stolen M$ source code around that this won't help much. willing hackers will just exploit other problems for the next (say) 5 years or so.
Security by obscurity. It won't help, but make a lot of knowledgeable customers unhappy.
i fail to see the difference of a webbrowser initiated and a scripted request to a dynamicly generated response. In any way, permission must be checked, the script shall now work on request data nor send data back to a client with insufficient permission. Nothing to see here, move along ...
-S
i have had the exact oposite situation. i've bee using RH, SuSE at my job and been using primarely debian at home. when i got that acer travel mate i had a hell of a time getting debian sarge/testing to support my hardware (i had to apply 5-6 kernel patches first).
on the other hand, ubuntu was installed in approx. 1 hour and it supported all hardware out of the box (things like bluetooth, firewire, wifi, irda, the buggy intel video card [including accel support], etc.).
ubuntu is now my default linux on the desktop, it is not as stable as debian because they seem to use patches relatively early if a certain piece of hardware is commonly used.
BTW: ubuntu has a hardware database and they seem to force code into their release that is most probably used, not the most stable code tough.
Cheers,
-S
i'd recommend tinyMCE: http://tinymce.moxiecode.com/. a true XHTML editor, works with mozilla 1.3+ (FF1+) and IE5.5+ and probably opera soon. it slim, cleanly programmed, modular and standards compliant. i have done a lot of research about html wysiwyg editors running in browsers and most of them are just a mess (code wise).
not sure if this is also in seamonkey (aka the mozilla suite), i'd recommend to check this.
> As far as WW1 or WW2 engines, the required machining precision and
> seals technology to make something like a Wankel rotary was just
> not available. Cylindrical pistons and bores with circular seals are
> much simpler.
Wankel built his first "Drehkolbenmotor" (en: "Rotating piston engine") driven boat during WWII, however it was a prototype.
Call it "Ajax", "Web 2" or event "Web 2 enterprise". it is still markup, some javascript and the ability to script http transfers. The full sets of technology was introduced with IE5, then adopetd by mozilla (and since 1.3 the XmlHttpRequest object is compatible with the one of IE) and now opera and safari 2 (khtml) have also a scriptable http client.
I see the ajax approach as a nice way to get surfers used to the idea that a web application does not have to refresh the whole ui upon any action the user takes. however, html is just not suitable for rich user interfaces, scripting the missing bits will be an effort every implementor has to take.
IMHO the real future for such applications lies in WHATWG, XUL and maybe XAML if this technology will be available with vista. Lets see if this is going to happen.
just my 2 swiss cents.
i am a web developer using FF since it was called (codename) Firebird. Fireforx and the mozilla suite (aka Seamonkey) crash about 1 time in a year and i am running it on windows/linux with a couple of extensions.
I really don't get that instabillity crap.
it's opensource ...
Most probably, one needs just to alter the install.rdf (change required version numbers) to get it work somewhat-ish. if it doesn't you have all the source at your finger tips.
i recommend to never use the notation document.elementName.property because objects may get mixed up.
what happens, if someone uses (silly yes, but we are talking about sloppy coders):
now which object does a sloppy coder get with: document.myElement.prop or even document.all.myElement.prop? i don't know, i have never tried it. but it will defenately screw up your code.
use document.getElementById() whenever you can (this is implemented in IE5).
Cheers, -S
type about:config into the location bar. it gives you all the config options mozilla offers (not just the options in the dumbed down FF UI). Cheers, -S
nope, the fix is not even on trunk yet.
probabyl by write protecting chrome/installed-chrome.txt and chrome/chrrome.rdf nobody will be able to install extensions. altough the files are downloaded and probably installed the etxensions will not get registered and therefore are not accessable from within moz/FF.
there is one problem, the user might choose to install an extension into his/her personal (home) chrome directory which will not be protected.