On Fri, Feb 21, 2014 at 10:21 AM, Robert Heller <hel...@deepsoft.com> wrote: > At Fri, 21 Feb 2014 09:19:28 +0900 Carsten Haitzler (The Rasterman) > <ras...@rasterman.com> wrote: >> On Thu, 20 Feb 2014 09:28:23 -0500 Robert Heller <hel...@deepsoft.com> said: >> > At Thu, 20 Feb 2014 22:45:58 +0900 Carsten Haitzler (The Rasterman) >> > <ras...@rasterman.com> wrote: >> > > On Thu, 20 Feb 2014 07:39:02 -0500 Robert Heller <hel...@deepsoft.com> >> > > said: >> > > >> > > > At Thu, 20 Feb 2014 17:01:28 +0900 Carsten Haitzler (The Rasterman) >> > > > <ras...@rasterman.com> wrote: >> > > > >> > > > > >> > > > > On Wed, 5 Feb 2014 12:05:12 -0500 Robert Heller <hel...@deepsoft.com> >> > > > > said: >> > > > > >> > > > > > I am doing some tests with efreet_menus and I am getting an error >> > > > > > message: >> > > > > > >> > > > > > *** main: favorites menu file >> > > > > > is /home/heller/.e/e/applications/menu/favorite.menu CRI: >> > > > > > lib/efreet/efreet_menu.c:624 efreet_menu_parse() eina_log_print() >> > > > > > unknown domain -1, original message format 'Efreet_menu: Menu file >> > > > > > didn't start with <Menu> tag.' >> > > > > >> > > > > i don't know - but one of the tags before menu must be making efreet >> > > > > unhappy. elimination will tell you which. :) >> > > > >> > > > >> > > > It turned out that I had not run efreet_init() in my test program, so >> > > > efreet was not properly initialized. >> > > >> > > aha! :) >> > >> > BTW: efreet_init() is not (obviously) documented. I found it by looking at >> > e_main.c in the enlightenment source tree. I guess this is a (minor) >> > documentation bug...Efreet.h >> >> i see documentation for it... from Efreet.h: >> >> /** >> * @return Value > @c 0 if the initialization was successful, @c 0 otherwise. >> * @brief Initializes the Efreet system >> */ >> EAPI int efreet_init(void); >> >> ??? > > There isn't an *obvious* link to it on the main Efreet documentation page: > > http://docs.enlightenment.org/stable/edje/efreet_main.html > > So, unless ones knows where to look, one won't find it. *I* only found it by > greping for efreet calls in e_main.c in enlightenment-0.18.2/src/bin/. > > So, it is a documentation bug, somewhere...
Since the merge of our libraries, the navigation in our documentation has become more complex as going to modules or files do not point now to the context of the library we are looking at. I think we really need some one to spend time and caring about it. Basically it is a know issue at this stage and we don't have any resource on it. Patch are obviously welcome and it is a task that new comer can tackle as documentation is already there, just lacking in accessibility (In general I think documentation is something new comers are the best to tackle as for most of the old dev, it is now difficult to remember what it was to learn it). -- Cedric BAIL ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
