I think one of the issues we have is that namespace is not declared as it would be in other languages. I have inferred, as have others, that the namespace is everything except the last component of the class name. This seems to work to an extent but if we were to clarify this as the desired behaviour we could specify which namespaces we wish to use rather than have them be determined through (side effects of) class naming...
Andy On Mon, 8 Jan 2018 at 10:53, Cedric Bail <ced...@ddlm.me> wrote: > Hi Dave, > > > -------- Original Message -------- > > Subject: [E-devel] Eo/Eolian namespace definition > > Local Time: January 7, 2018 9:28 AM > > UTC Time: January 7, 2018 5:28 PM > > From: d...@gurumeditation.it > > To: Enlightenment <enlightenment-devel@lists.sourceforge.net> > > > > Hi all, > > > > I'm playing again with eolian and python, and I'm facing an issue with > > regards class names and namespaces separation (I already raised this in > the > > past) > > > > A first intro to python namespaces (I think apply to any other high-level > > language): > > > > - in py every class must live in a given namespace and you use the class > as: > > from <namespace> import <class> > > - every namespace in python is a separate .so file > > > > The basic question is: > > is the Efl.Text (interface) inside the Efl.Text namespace? > > do I need to put the Text interface inide the Efl.Text .so file? > > > > NO) if the resonse is no, then in python will become: > > from efl.ui import Button > > from efl import Text > > from efl.text import Font > > > > this feels wrong to me, as Text is not in the text namespace > > > > YES) if the response is YES: > > from efl.ui import Button > > from efl.text import Text > > from efl.text import Font > > > > this one seems correct to me, but this means that the full name of the > Text > > class should be Efl.Text.Text (this is a must in python, and probably in > > all other langs) > > I think that Text is maybe a bad example as it might be best to move it to > the Efl.Gfx namespace. In general I think our Efl top namespace is to > crowded and would be better cleaned up. I am guessing this would solve many > problem for python, no ? In general, do you have rules for naming and > namespaces that you would like us enforcing ? If we had, we could enforce > them in eolian. > > Cedric > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- http://andywilliams.me http://ajwillia.ms ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
