-
tomman
"Eternal Youth"
-
tomman
webdevs realized they can't age beyond 35 if they keep adopting the latest bleeding edge Chromeisms, er, "features" every wek
-
tomman
otherwise they will turn 70 by next Sunday
-
nsITobin
tomman: is THAT what happened to me.. i didn't so now I am aging faster?
-
njsg
there's a trick to work that around, so that we can say you're aging slower, and it won't look like slower to you
-
njsg
you just need go move very, very fast
-
njsg
cf. "On the Elecrodynamics of Moving Bodies"
-
hardys
lightning doesn't work with the new build 2.53.21 beta 1 pre from today
-
frg_Away
hardys there were 0 changes in the code for Lightning. Works for me. Make sure you have 6.2.21 in the add-ons manager. If not you probably have an old copy in your profile whivh needs to be uninstalled.
-
hardys
frg_Away: Thanks for the hint, Lightning didn't update automatically
-
hardys
frg_Away: now all good again :)
-
frg_Away
hardys if it didn't update automatically there is a copy in your profile
-
frg_Away
Don't install it manually or you will have the same problem with the next version
-
nsITobin
it would be really nice to eventually rearchitech lightning into a seperate suite component rather than leeching off mailnews ui just with a few inetgration points
-
frg_Away
done in central but people always complaining about it when the not use it. Would no longer be possible to disable it.
-
nsITobin
frg_Away: so let me get this str8.. people would complain about a suite being more of a suite
-
frg_Away
yes but eventually I would like this and cZ move in
-
nsITobin
also if people will accept programaically disabled rather than not-installed.. well shit that isn't hard..
-
nsITobin
there is this seperation of the suite as Netscape Communicator and the suite as a toolkit app in the context of SeaMonkey and the Suite toolkit featuresets are .. and i can't believe I am admitting it.. less important than the application as an integrated suite is..
-
frg_Away
I would like to uncouple Lightning a bit from mailnews and add ctrl+3 for it. Just no time to pursue it.
-
nsITobin
standalone calendar UI would have helped.. it decended from the XPFE form.. would have to build a new host window then transfer from extension to the ui component
-
nsITobin
create a proper prefpane etc
-
frg_Away
I think this topic popped up before and we discussed it. Just no time to actually do it.
-
frg_Away
next life maybe :)
-
nsITobin
maybe in its earlier form when i was planning standalone calendar
-
nsITobin
lightning threw a wrench into so much of Interlink's dev
-
nsITobin
virtually haulted UI changes
-
nsITobin
bbl
-
nsITobin
store
-
njsg
re disabling components, a question is how much is saved/avoided if it's not compiled, it would be interesting if having just the browser could narrow down the build size
-
njsg
(standalone calendar UI, like Sunbird?)
-
nsITobin
yes njsg
-
nsITobin
but only the extension parts remain
-
nsITobin
and whatever was reused from sharedui
-
frg_Away
njsg doen't matter much. You won't even notice.
-
nsITobin
well as I said if people are willing to just out of sight out of mind certain components of the suite so what is presented is what they want and use most then that has some good potental and cheap impl
-
nsITobin
and as a matter of history xpfe still had mailcomps and mailnews core built in just the UI was excluded as xpinstall would populate the chrome based on your choices
-
nsITobin
only difference between that and disabling programatically is that the actual files are still there its just you aren't presented any entry points to it