On 13/02/13 08:00, Nathan Baxter wrote: > On 13/02/2013 06:44, Carsten Haitzler (The Rasterman) wrote: >> On Tue, 12 Feb 2013 14:02:14 +0000 Nathan Baxter >> <[email protected]> said: >> >>> On 12/02/13 13:42, Carsten Haitzler (The Rasterman) wrote: >>>> On Tue, 12 Feb 2013 12:09:35 +0000 Nathan Baxter >>>> <[email protected]> said: >>>> >>>> i would KILL for someone to take charge of www... do the css, html, any php >>>> (please keep it simple - php is adequate. no fancy cms's or frameworks >>>> thanks)... and take charge of any gfx/design as well. pull together >>>> people/team to do it too AND to keep maintaining it over time... i'd LOVe >>>> that... no toes being stepped on. i'd also just like it to complement our >>>> current default theme/look. :) not clash. :) >>> That shouldn't be a problem, I've been studying the default to try and >>> wrap my head round edje (no joy) and a lot of what I've come up with so >> edje is easy. think of it as an overgrown xcf or psd... with each layer >> actually having a position and size.. and different states too that it can >> transition between... the size and position is both relative and absolute >> depending on params or any combination of that.. and relative TO something... >> (or nothing == relative to the object as a whole). layers (parts) can also be >> text... blocks of formatted text and simple rects. it's just what e16 themes >> had.. but on 3 container ships worth of steroids, and with a cherry on top. >> :) >> oh and some parts (layerS) can embed whole new "external" objects into them >> and >> thus control their size/position, visiblity and more... :) >> >> stuff works in reverse too... sizing of parts can be "reverse worked out" to >> set a font, size and blob of text then ask the object "so given this >> content.. >> what is your minimum size?". :) a lot of the ui sizing is controlled this >> way. >> >>> far relies on the current look of the base site anyway, just different >>> methods of implementation. I do need to spend a little more time with >>> php, but I'm confident enough (far more confident than I am with edje - >>> which is why I *still* haven't released any dr17 themes.). >> hehehehe ok ok... once u get used ot edje.. u'll wish u had it in >> html/css/php... :) > > That's something I don't doubt. :) > >>>> hre's the catch - it'd be bad to half do it then vanish. :) so if you want >>>> to "commit" then by all means... you are more than invited! all you need is >>>> commit access. the rest is already automated. if you "get" how the current >>>> simple php works - you can build and change from there as you see fit >>>> (theres the u.php that triggers an update if you open it in any browser for >>>> example... :)). >>> I appreciate that. As previously mentioned I haven't made any major >>> advances in theme land since DR16 and I know I said before (2005 I >>> think) that I'd remain commited to keeping up to date and trying to stay >>> involved, but at least I didn't drop 23 Ounces of Glass 2 on any one ;) >> ahahahahhaah :) well if you want to do this and actually make it happen, then >> it's all open doors. > > I do want to make it happen. > >>> As for commit access: I'll keep plugging at this externally for the rest >> right now that'll be a bit painful as we are about to move from svn to git... >> so it may go thru some hiccups.... but it'll become "git push access" in the >> end... you'll want a phabricator account when its all set up etc. > > If that's the case, I'll just work on a base XCF so I have a map of what > I feel needs to be done. > As soon as www is a git module I'll start the implementation. > >>> of the week, if at the end of this time I feel I've made a significant >>> and substantial improvement a commit bit would be useful, otherwise I'll >>> keep plugging at it until we're all happy! Alternatively I could start >>> small and branch out, the only problem with that is <td>'s don't float ;) >> see above.. git move happening nowish... so it'll end up being git access and >> may end up being next week or so so.. once www becomes a git module of its >> own. :) >> >>> How far back does browser support need to go? >> for browsers? ummm tbh thats a good q. while i'd LIKE ie6 to work.. and >> netscape 1.1... and mosaic... reality is there is only so much we can >> sensibly >> do. i think i'd say "make ie7 work" ie... when ie finally stopped being AS >> crap >> and begin to think of the modern world a little.... but it depends on how >> hard >> it is. > > There are more than a few tricks for this, it is time consuming, but not > impossible. > My job generally requires IE6 compatibility any way so I have the means > to test this. > > If a site works In IE 6,7,8, FF, Chrome, Opera and elinks we should have > most of the bases covered.
Really? Do people still care about IE6? Seriously dude, don't bother with this one. It's officially dead for a long time. Less than 6% of the world uses ie6, most of it from China. I think it's safe to say that less than 0.000000000000006% of the people that enter the E website use IE6. We can easily verify that with some server logs. http://www.ie6countdown.com/ -- Tom. ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
