On Fri, 04 Jan 2013 19:17:41 +0000 Christopher Michael <cpmicha...@comcast.net> said:
> Tom Hacohen <t...@stosb.com> wrote: > > >Trunk is e18... > > > > > >On Fri, Jan 4, 2013 at 7:06 PM, Christopher Michael > ><cpmicha...@comcast.net>wrote: > > > >> Michael Blumenkrantz <michael.blumenkra...@gmail.com> wrote: > >> > >> >On Fri, 04 Jan 2013 19:01:10 +0000 > >> >Christopher Michael <cpmicha...@comcast.net> wrote: > >> > > >> >> Michael Blumenkrantz <michael.blumenkra...@gmail.com> wrote: > >> >> > >> >> >On Fri, 04 Jan 2013 18:50:17 +0000 > >> >> >Christopher Michael <cpmicha...@comcast.net> wrote: > >> >> > > >> >> >> Ummmm WHY ??? > >> >> >> Composite is an optional module for e17. Why would you remove > >the > >> >> >Optional to disable it ?? > >> >> >> > >> >> >> Dh > >> >> > > >> >> > > >> >> >2 commits before that: > >> >> > > >> >> >e: remove dropshadow module > >> >> > > >> >> >dropshadow module conflicts with composite, which will be always > >> >> >enabled > >> >> > by future commits. Remove the module to allow turning composite > >as > >> >> > always-enabled. > >> >> > >> >> Missed that commit. Thanks :-) > >> >> > >> >> So by this logic now, composite is now Required for e17 ? > >> >> > >> >> If we remove the option to disable comp in the wizard then you > >should > >> >probably also remove the ability to Unload the composite module from > >> >the modules list (as that is effectively what was just dobe by > >removing > >> >the wizard option) > >> >> > >> >> dh > >> > > >> >it will no longer be a module within a couple days, so that's not > >> >necessary > >> > >> I see. Well thanks for clearing that up :-) Tho I was under the > >impression > >> that Composite would not be a Requirement until E18...must have > >missed the > >> secret meeting where this was discussed for e17. > >> > >> dh > >> > >> > >------------------------------------------------------------------------------ > >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > >> much more. Get web development skills now with LearnDevNow - > >> 350+ hours of step-by-step video tutorials by Microsoft MVPs and > >experts. > >> SALE $99.99 this month only -- learn more at: > >> http://p.sf.net/sfu/learnmore_122812 > >> _______________________________________________ > >> enlightenment-devel mailing list > >> enlightenment-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > > > > > >-- > >Tom. > >------------------------------------------------------------------------------ > >Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > >much more. Get web development skills now with LearnDevNow - > >350+ hours of step-by-step video tutorials by Microsoft MVPs and > >experts. > >SALE $99.99 this month only -- learn more at: > >http://p.sf.net/sfu/learnmore_122812 > >_______________________________________________ > >enlightenment-devel mailing list > >enlightenment-devel@lists.sourceforge.net > >https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > Ahhhhh Now that actually does clear things up :-) Hmm would have thought e18 > development would have been a new branch or folder in the tree. Did not > realize that development was going to happen in-tree (on top of ezisting > e17). So there are no plans to "keep" e17 then ? (meaning development of e18 > is happening now and we are rewriting e17 code in-place so that when e18 geta > done there will be no more e17 aside from the 1.7 branch) as far as i'm concerned trunk is the direct path to e18. it comes out when we have at least some decent milestones in there (eg comp on core) and we have done stabilization. i'm currently thinking the elm in dialogs may wait for e19 - not that we dont make it possible - it just wont be feasible to go redo them all for e18. elm needs theme work for that etc. - so when elm's theme work is done, then we can go gangbusters there. in the meantime comp in core is a worthy bit of work on its own - as putting the code in is just one step. the next is a lot of re-jigging of what is a window and what is not inside of e17. ie .. remove lots of windows... but for e18 we will likely just start with a few -eg like bg/container window. in theory we need to do menus, popups, shelf etc. too - likely the lst thing to be de-windowized will be border frames. this may not go in for e18. it depends on how much time elapses and how the above de-windowing goes. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
