Re: [E-devel] Release schedule

2009-01-29 Thread Veli Ogla Sungutay
On Thu, Jan 29, 2009 at 2:04 AM, Toma tomha...@gmail.com wrote:


 I propose February 14th. Its close, realistic, and might dull the
 loneliness of Valentines Day. :)

 -Toma.




Ahaha, indeed.

-- 
Veli Sungutay
http://www.lyciasoft.com
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Release schedule

2009-01-29 Thread Toma
2009/1/29 sda dmitry.serpok...@gmail.com:
 On 09:04 Thu 29 Jan , Toma wrote:

 As the top of the page says, we need to finalize the list of things
 TODO.

 hi guys,

 i'm not the dev so beg your pardon if things below are out of scope.

 1) after the review of a mentioned page
 (http://trac.enlightenment.org/e/wiki/Release)
 i decide to fill 'trac' with some more 'tickets'/(requests) instead of
 the page modification. assume that it's your (and not mine) decision to
 set a milestone to the Release.

 2) there're no 'magic' word  we're all aware about (no doubt that it ...
 you know...). here it is (in capital letters):
   == SYSTRAY ==
 suppose that clear definition of our POV to this case is required. it's
 o'k not to make one and explain why. but Release of a Desktop Shell
 without a tray will attract less Users i guess. yes, Wiki FAQ advise to
 use 'trayer', 'stalonetray', etc., but references to the various
 discussions are unable to state the case clear.


There was a systray mention on there a while ago... maybe it was a
different TODO list. Added in modules-extra for now.

 3) annoying question related to the color and font config modules. as
 it was mentioned by Raster:

thats what i meant - just wouldn't compile the color and font config modules.
they they wont appear anywhere. code will be there - just not being compiled 
or
used until its fixed.

 ok. but does it mean that all themes/(.edj files) which use custom fonts
 and/or color_class:-es will require maintenance? if Yes!, then
 suppose that the info should be spread all over the community or only new
 default theme will remain usable (it's a nice option, but some may
 prefer other variants).


I think scraping the modules to config it would be good, but leave the
support for it via enlightenment_remote would be good as well. If
anyone was keen, they could revamp it and reintroduce into a major
release eg, E17.1. That way, we dont need to alter themes, and if you
really want, just include a brief howto in the theme about. Kind of
like what i did with Cerium.

 4) another chewing gum - Should add lua support? (optional) Just
 make a decision and say it. No/Yes - doesn't matter much (though the
 amount of maintenance if Yes will be sufficient). it's a pity that
 both VM's ('embryo' and 'lua') can't exist together.


More of a pending decision. Someone was working on an alternate
environment with LUA working. Results of that work are yet to be
debated and trialed I guess? My personal

 5) last couple of days i'm using 'Ecomorph' and it's much more stable
 then bling module. suppose that bling should be improved (in terms
 of stability) or explicitly marked as 'unstable'. yes, FAQ tells that
 E17 doesn't work with composite, but it's an easy task for bling now
 to create a nice segfault of E17 :).

 offtop http://en.opensuse.org/Ecomorph

Only thing stopping ecomorph from being an official module is that it
needs drastic changes to the main tree, IIRC. Someone feel free to
correct me on that as I havent looked into it.


 6) as i mentioned in trac ticket #201 the gap exist in a window
 management between E16/eesh and E17/enlightenment_remote. it could be
 nice to eliminate this mismatch especially for the experienced Users
 of E16.


Like buying a new TV, you need to learn the new remote. :)

 7) the bridge between qt - edje  gtk - edje still under
 heavy discussion suggest to create a couple of themes like existing
 Clearlooks (it's really nice) to match the major ones used by others.
 dunno about qt (don't use it here) but it's an easy task to copy a
 couple of most popular gtk+ ones.


With the development of QEdje, a cross to QT/KDE with an E theme might
be possible with a bit more persistence. But again, I havent even
looked at QEdje and friends since they were released a while back. But
in all honesty, we shouldnt worry too much about that. What we SHOULD
worry about, is the cross themeing of E with EWL and ETK. It is all
very possible, but as a themer yourself, its quite tedious to add the
other parts and duplicate and so on. We could of course, investigate
making the toolkits (Or toolkit) work with edje parts from an E theme.


 thanks for your kind attention.
 regards,
 sda


NP.
Toma-

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] Evas+winxp get errors on engine direct3d

2009-01-29 Thread Vincent Torri

Hey,

 I get the direct3d module compiled. To make it compile I move the header
 d3dx9.h to the file where it's needed,
 files that compile with g++. So I make the following changes:

[snip]

I have applied your changes with some modifications. Can you check that 
the compilation is fine with your mobo ?

about the problem when executing a program, I'll check that soon

Vincent

--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel