From: Mathieu B. <mat...@po...> - 2004-01-22 17:08:42
|
Kevin Brosius wrote: >>>And entice is build and working! Except for the icons in the top right >>>>corner they doesn't show up but i know the shortcuts already so >>>>everything is fine to me! >>>> >>>>Thanks >>>> >>>> >> >> >> >>No icons in the upper right, even when you mouse over that window >>region? That is working here... >> >> >> > > Yes, exactly the text in the corner move to the left to give icons place and the text under appears to explain what the action is but there is no icons! Maybe a compilation problem where it couldn't add the icons correctly ? -- Mathieu Bruneau École Polytechnique de Montréal |
From: Vincent T. <to...@ma...> - 2004-01-22 17:24:39
|
> Kevin Brosius wrote: > > >>>And entice is build and working! Except for the icons in the top right > >>>>corner they doesn't show up but i know the shortcuts already so > >>>>everything is fine to me! > >>>> > >>>>Thanks > >>>> > >>>> > >> > >> > >> > >>No icons in the upper right, even when you mouse over that window > >>region? That is working here... > >> > >> > >> > > > > > > Yes, exactly the text in the corner move to the left to give icons place > and the text under appears to explain what the action is but there is no > icons! Maybe a compilation problem where it couldn't add the icons > correctly ? same problem for me. Maybe i also missed something regards |
From: Corey D. <at...@at...> - 2004-01-22 17:26:40
|
* Mathieu Bruneau (mat...@po...) wrote: > Kevin Brosius wrote: > > >>>>And entice is build and working! Except for the icons in the top > >>>>right corner they doesn't show up but i know the shortcuts > >>>>already so everything is fine to me! > >>>> > >>>>Thanks > >>>> > >> > >>No icons in the upper right, even when you mouse over that window > >>region? That is working here... > > Yes, exactly the text in the corner move to the left to give icons place > and the text under appears to explain what the action is but there is no > icons! Maybe a compilation problem where it couldn't add the icons > correctly ? > Does your theme have any images? The default theme should look something like. http://www.atmos.org/images/entice.jpg Make sure you have the eet imlib2_loader installed. __ Corey Donohoe atmos.org |
From: Didier C. <did...@sp...> - 2004-01-29 23:17:27
Attachments:
Screenshot.png
|
On 22/01/04, at 11:26 -0600, Corey Donohoe <at...@at...> wrote: > * Mathieu Bruneau (mat...@po...) wrote: > > Kevin Brosius wrote: > > > > >>>>And entice is build and working! Except for the icons in the top > > >>>>right corner they doesn't show up but i know the shortcuts > > >>>>already so everything is fine to me! > > >>>> > > >>>>Thanks > > >>>> > > >> > > >>No icons in the upper right, even when you mouse over that window > > >>region? That is working here... > > > > Yes, exactly the text in the corner move to the left to give icons place > > and the text under appears to explain what the action is but there is no > > icons! Maybe a compilation problem where it couldn't add the icons > > correctly ? > > > Does your theme have any images? The default theme should look > something like. http://www.atmos.org/images/entice.jpg > Make sure you have the eet imlib2_loader installed. > I think that I've the same problem! Take a look at my attachment! All my imlib2 loaders are here! rpm -qa | grep imlib gives: ------------------------- imlib-devel-1.9.13-12 imlib2-loader_jpeg-1.1.0-1 imlib2-devel-1.1.0-1 imlib2-1.1.0-1 imlib2-loader_tga-1.1.0-1 imlib2-loader_gif-1.1.0-1 imlib2-loader_pnm-1.1.0-1 imlib2-loader_bmp-1.1.0-1 imlib2-loader_png-1.1.0-1 imlib2-loader_argb-1.1.0-1 imlib2-loader_xpm-1.1.0-1 imlib-1.9.13-12 imlib2-loader_gzbz2-1.1.0-1 --------------------------- and btw as you would also notice I've that error too: ---------------------------------------------------- ERROR: lt_dlclose (can't close resident module) ---------------------------------------------------- Can anybody help out? I'm using RH9-FC1 (sort of a hybrid system of both!) With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg / didierbe at sps dot nus dot edu dot sg |
From: Corey D. <at...@at...> - 2004-01-30 22:38:55
|
* Didier Casse (did...@sp...) wrote: > > I think that I've the same problem! Take a look at my attachment! > All my imlib2 loaders are here! Just to be sure checkout http://www.atmos.org/docs/entice/index.html#requirements You can skip the imlib2 stuff there, what you already have should suffice. > > rpm -qa | grep imlib gives: > > ------------------------- > imlib-devel-1.9.13-12 > imlib2-loader_jpeg-1.1.0-1 > imlib2-devel-1.1.0-1 > imlib2-1.1.0-1 > imlib2-loader_tga-1.1.0-1 > imlib2-loader_gif-1.1.0-1 > imlib2-loader_pnm-1.1.0-1 > imlib2-loader_bmp-1.1.0-1 > imlib2-loader_png-1.1.0-1 > imlib2-loader_argb-1.1.0-1 > imlib2-loader_xpm-1.1.0-1 > imlib-1.9.13-12 > imlib2-loader_gzbz2-1.1.0-1 > --------------------------- This is good, entice is going to take advantage of all of these loaders, it'll support more formats than evas will alone :) > > and btw as you would also notice I've that error too: > > ERROR: lt_dlclose (can't close resident module) k, I'm not really sure here. This is coming from the container in esmart(container_plugin.c), I think. I'm not sure of the difference between lt_dlclose and dlclose. try running esmart_test on some images $ esmart_test pr0n/*.jpg Basically entice won't work right if your container plugins aren't working properly. So that might be your problem. You can check to make sure that it's not edje itself that's giving you issues. $ edje /usr/local/share/entice/themes/default.eet Click on the entice group, you should have buttons and stuff. If that's working, esmart's container is the issue, and we have a new problem to address. :) > > ---------------------------------------------------- > > Can anybody help out? I'm using RH9-FC1 (sort of a hybrid system of both!) I think marmot running something like this, and last i checked entice was working ok for him. __ Corey Donohoe atmos.org |
From: Didier C. <did...@sp...> - 2004-01-31 03:12:04
|
On 28/01/04, at 23:16 -0600, Corey Donohoe <at...@at...> wrote: > Just to be sure checkout > http://www.atmos.org/docs/entice/index.html#requirements Hi Corey, This is the one I checked out first. Everything is in my box. > > ERROR: lt_dlclose (can't close resident module) > k, I'm not really sure here. This is coming from the container in > esmart(container_plugin.c), I think. I'm not sure of the difference > between lt_dlclose and dlclose. try running esmart_test on some images > $ esmart_test pr0n/*.jpg Ah! Sometimes it works (rarely) but most of the time it gives: -------------------------------------------------------------------------- bg_ebg_trans: cannot create transparency pixmap, no valid wallpaper set. bg_ebg_trans: could not read root-window property _XROOTPMAP_ID... -------------------------------------------------------------------------- > Basically entice won't work right if your container plugins aren't > working properly. So that might be your problem. You can check to make > sure that it's not edje itself that's giving you issues. > > $ edje /usr/local/share/entice/themes/default.eet The Edje test program works fine. It once in a while give a segmentation fault when I click on the entice thumb, but I guess this is no big deal > > Click on the entice group, you should have buttons and stuff. If that's > working, esmart's container is the issue, and we have a new problem to > address. :) > esmart doesn't seem to be so smart in this case! The esmart test wasn't so successful. What's the next step? With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg / didierbe at sps dot nus dot edu dot sg |
From: Corey D. <at...@at...> - 2004-01-30 23:15:52
|
* Didier Casse (did...@sp...) wrote: > > Hi Corey, > This is the one I checked out first. Everything is in my box. yay ! cool. > > > > ERROR: lt_dlclose (can't close resident module) > > k, I'm not really sure here. This is coming from the container in > > esmart(container_plugin.c), I think. I'm not sure of the difference > > between lt_dlclose and dlclose. try running esmart_test on some images > > > $ esmart_test pr0n/*.jpg > > Ah! Sometimes it works (rarely) but most of the time it gives: > > -------------------------------------------------------------------------- > bg_ebg_trans: cannot create transparency pixmap, no valid wallpaper set. > bg_ebg_trans: could not read root-window property _XROOTPMAP_ID... > -------------------------------------------------------------------------- > Erm... The trans stuff shouldn't be keeping the container from working. But since the trans stuff is the background for the container you'll prolly get garbled data all over the canvas. What wm are you running? > > > Basically entice won't work right if your container plugins aren't > > working properly. So that might be your problem. You can check to make > > sure that it's not edje itself that's giving you issues. > > > > $ edje /usr/local/share/entice/themes/default.eet > > The Edje test program works fine. It once in a while give a segmentation > fault when I click on the entice thumb, but I guess this is no big deal edje shouldn't segv viewing the theme edje. the signals are just saying "do this" and "do that" but the edje viewer won't really act on those signals, they're hooked in externally by your app. > > > Click on the entice group, you should have buttons and stuff. If that's > > working, esmart's container is the issue, and we have a new problem to > > address. :) > > > esmart doesn't seem to be so smart in this case! The esmart test wasn't so > successful. What's the next step? Oh esmart is still smart ! Just being stubborn. :) * What version of libtool are you using? * Does commenting out the e_container_layout_plugin_set(e->container, "entice"); call in src/bin/entice.c about line 125 help? You'll have to recompile but you should be able to test from the src dir ./entice /path/to/some/image.png It might be easiest to drop by #edevelop on irc.freenode.net if you'd be interested in debugging this in realtime. :) I'm glad it's not entice, but I'm not sure what the container plugin's deal is on your system. __ Corey Donohoe atmos.org |
From: Didier C. <did...@sp...> - 2004-01-30 18:31:06
|
On 29/01/04, at 01:29 -0600, Corey Donohoe <at...@at...> wrote: > * What version of libtool are you using? libtool-1.4.3-5 > * Does commenting out the e_container_layout_plugin_set(e->container, > "entice"); call in src/bin/entice.c about line 125 help? You'll have to > recompile but you should be able to test from the src dir > ./entice /path/to/some/image.png It helped more than I had imagined. Now it works fine! Really cool! But with the default.eet I don't see much buttons around (no buttons I would say!), so I replaced it with the winter.eet by rephorm and now it looks similar to this http://rephorm.com/rephorm/design/winter/entice.png and I could load a directory of 100+ photos. :-p > > It might be easiest to drop by #edevelop on irc.freenode.net if you'd be > interested in debugging this in realtime. :) > Already debugged thanks to you. I thank you very much for your time Corey. > I'm glad it's not entice, but I'm not sure what the container plugin's > deal is on your system. It looks like it! PS: How come my emails don't get to the E-devel list??!??!? And yours get in faster than mine although I sent first to the list! Again many thanks. Cheers, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg / didierbe at sps dot nus dot edu dot sg |
From: Didier C. <did...@sp...> - 2004-01-29 19:49:27
|
On 29/01/04, at 15:54 +0800, Didier Casse <did...@sp...> wrote: > On 29/01/04, at 01:29 -0600, Corey Donohoe <at...@at...> wrote: > > > * What version of libtool are you using? > > libtool-1.4.3-5 > > > * Does commenting out the e_container_layout_plugin_set(e->container, > > "entice"); call in src/bin/entice.c about line 125 help? You'll have to > > recompile but you should be able to test from the src dir > > ./entice /path/to/some/image.png > > It helped more than I had imagined. Now it works fine! Really cool! > Let me take what I said back for a second! Now entice can only view images not large than 800x600. I had some images with JPEG 2048x1536 DirectClass 8-bit 1308kb 0.0u 0:01 and it gave me this error message. ---------------------------- length smaller than size length smaller than size length smaller than size length smaller than size length smaller than size ---------------------------- and could not load any Might be the fact that I commented out the line 125! For the moment, it's not possible for me to troubleshoot in realtime! Cheers, Didier. |
From: Corey D. <at...@at...> - 2004-01-30 22:22:47
|
* Didier Casse (did...@sp...) wrote: > On 29/01/04, at 15:54 +0800, Didier Casse <did...@sp...> wrote: > > > On 29/01/04, at 01:29 -0600, Corey Donohoe <at...@at...> wrote: > > > > > * What version of libtool are you using? > > > > libtool-1.4.3-5 > > > > > * Does commenting out the e_container_layout_plugin_set(e->container, > > > "entice"); call in src/bin/entice.c about line 125 help? You'll have to > > > recompile but you should be able to test from the src dir > > > ./entice /path/to/some/image.png > > > > It helped more than I had imagined. Now it works fine! Really cool! > > Yeah, but for some reason you're stuck with the normal container. I had this problem on ppc, but it was fixed a few weeks back. > > Let me take what I said back for a second! Now entice can only view images > not large than 800x600. odd. > > I had some images with JPEG 2048x1536 DirectClass 8-bit 1308kb 0.0u 0:01 > and it gave me this error message. > ---------------------------- > length smaller than size > length smaller than size > length smaller than size > length smaller than size > length smaller than size > ---------------------------- > and could not load any This is related to container scrolling, not to the image displaying. It's a debugging printf saying "Don't scroll!!!!" :) > > Might be the fact that I commented out the line 125! nup, it's not, well shouldn't be... :) > > For the moment, it's not possible for me to troubleshoot in realtime! understandable. __ Corey Donohoe atmos.org |
From: Corey D. <at...@at...> - 2004-01-30 23:09:00
|
* Didier Casse (did...@sp...) wrote: > > It helped more than I had imagined. Now it works fine! Really cool! > > But with the default.eet I don't see much buttons around (no buttons I > would say!), so I replaced it with the winter.eet by rephorm and now it > looks similar to this > > http://rephorm.com/rephorm/design/winter/entice.png Maybe your edje_cc isn't generating the theme properly. You can grab a copy of it at http://www.atmos.org/files/entice.eet > > and I could load a directory of 100+ photos. :-p > > > I'm glad it's not entice, but I'm not sure what the container plugin's > > deal is on your system. > > It looks like it! > > PS: How come my emails don't get to the E-devel list??!??!? And yours get > in faster than mine although I sent first to the list! SF mailing lists seem lagged, we just happened to get each others emails before sf got around to letting everyone else get them. :) __ Corey Donohoe atmos.org |
From: Didier C. <did...@sp...> - 2004-01-29 14:12:45
|
On 29/01/04, at 02:40 -0600, Corey Donohoe <at...@at...> wrote: > * Didier Casse (did...@sp...) wrote: > > > > It helped more than I had imagined. Now it works fine! Really cool! > > > > But with the default.eet I don't see much buttons around (no buttons I > > would say!), so I replaced it with the winter.eet by rephorm and now it > > looks similar to this > > > > http://rephorm.com/rephorm/design/winter/entice.png > Maybe your edje_cc isn't generating the theme properly. You can grab a > copy of it at http://www.atmos.org/files/entice.eet works perfectly now as far as the design is concerned. I can see all the buttons and scroll arrows. Thanks. Does that mean that there's also a problem with the default.eet in CVS? Cheers, Didier |
From: Corey D. <at...@at...> - 2004-01-31 07:08:46
|
* Didier Casse (did...@sp...) wrote: > On 29/01/04, at 02:40 -0600, Corey Donohoe <at...@at...> wrote: > > > * Didier Casse (did...@sp...) wrote: > > > > > > It helped more than I had imagined. Now it works fine! Really cool! > > > > > > But with the default.eet I don't see much buttons around (no buttons I > > > would say!), so I replaced it with the winter.eet by rephorm and now it > > > looks similar to this > > > > > > http://rephorm.com/rephorm/design/winter/entice.png > > Maybe your edje_cc isn't generating the theme properly. You can grab a > > copy of it at http://www.atmos.org/files/entice.eet > > works perfectly now as far as the design is concerned. I can see > all the buttons and scroll arrows. Thanks. > > Does that mean that there's also a problem with the default.eet in CVS? There is no default.eet in CVS. Make builds default.eet for you,which is why i thought the problem might be with your edje_cc. That theme didn't solve the problem with your large images not being displayed properly, did it? If it didn't, can you paste the output that epsilon gives on the file(requires the absolute path). $ epsilon /path/to/image.jpg > > Cheers, > Didier __ Corey Donohoe atmos.org |
From: Didier C. <did...@sp...> - 2004-01-30 17:05:37
|
On 29/01/04, at 03:17 -0600, Corey Donohoe <at...@at...> wrote: > * Didier Casse (did...@sp...) wrote: > > On 29/01/04, at 02:40 -0600, Corey Donohoe <at...@at...> wrote: > > > > > * Didier Casse (did...@sp...) wrote: > > > > > > > > It helped more than I had imagined. Now it works fine! Really cool! > > > > > > > > But with the default.eet I don't see much buttons around (no buttons I > > > > would say!), so I replaced it with the winter.eet by rephorm and now it > > > > looks similar to this > > > > > > > > http://rephorm.com/rephorm/design/winter/entice.png > > > Maybe your edje_cc isn't generating the theme properly. You can grab a > > > copy of it at http://www.atmos.org/files/entice.eet > > > > works perfectly now as far as the design is concerned. I can see > > all the buttons and scroll arrows. Thanks. > > > > Does that mean that there's also a problem with the default.eet in CVS? > There is no default.eet in CVS. Make builds default.eet for you,which is I did not realize that the default.eet wasn't present! > why i thought the problem might be with your edje_cc. That theme didn't > solve the problem with your large images not being displayed properly, > did it? No it didn't, it only solved the design problem. I couldn't see any buttons w/ the original default.eet, but now I can see the logo, grid-like background and everything else. > If it didn't, can you paste the output that epsilon gives on the > file(requires the absolute path). > > $ epsilon /path/to/image.jpg > $ epsilon /home/didier/tmp/Photos/Picture 001.jpg returns: ----------------------------------------------------------- Thumbnail for /home/didier/tmp/Photos/Picture 001.jpg needs to be generated: OK ----------------------------------------------------------- With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg / didierbe at sps dot nus dot edu dot sg |
From: Mathieu B. <mat...@po...> - 2004-02-02 02:22:17
|
>>>Basically entice won't work right if your container plugins aren't >>>working properly. So that might be your problem. You can check to make >>>sure that it's not edje itself that's giving you issues. >>> >>>$ edje /usr/local/share/entice/themes/default.eet >>> >>> >>The Edje test program works fine. It once in a while give a segmentation >>fault when I click on the entice thumb, but I guess this is no big deal >> >> >edje shouldn't segv viewing the theme edje. the signals are just saying >"do this" and "do that" but the edje viewer won't really act on those >signals, they're hooked in externally by your app. > > >>>Click on the entice group, you should have buttons and stuff. If that's >>>working, esmart's container is the issue, and we have a new problem to >>>address. :) >>> >>> >>> Ok that part isn't working, i tried to recompile and get this working but hasn't got any chance... Any hint on what to do ? (I tried with the entice.eet send on the mailing list a few days ago too) -- Mathieu Bruneau Aka ROunofF École Polytechnique de Montréal |
From: Mathieu B. <mat...@po...> - 2004-02-02 06:07:56
|
Mathieu Bruneau wrote: > >>>> Basically entice won't work right if your container plugins aren't >>>> working properly. So that might be your problem. You can check to >>>> make >>>> sure that it's not edje itself that's giving you issues. >>>> >>>> $ edje /usr/local/share/entice/themes/default.eet >>>> >>> >>> The Edje test program works fine. It once in a while give a >>> segmentation >>> fault when I click on the entice thumb, but I guess this is no big >>> deal >> >> edje shouldn't segv viewing the theme edje. the signals are just saying >> "do this" and "do that" but the edje viewer won't really act on those >> signals, they're hooked in externally by your app. >> >> >>>> Click on the entice group, you should have buttons and stuff. If >>>> that's >>>> working, esmart's container is the issue, and we have a new problem to >>>> address. :) >>>> >>>> >>> > Ok that part isn't working, i tried to recompile and get this working > but hasn't got any chance... > Any hint on what to do ? > > (I tried with the entice.eet send on the mailing list a few days ago too) > Ok I had my problem solved with the help from rephorm, evas ./configure wasn't able to find Eet.h and Edb.h! Maybe abort the ./configure if the option --enable-image-loader-eet --enable-image-loader-edb are given and the test failed ? (Maybe autofoo will make this more "friendly") -- Mathieu Bruneau École Polytechnique de Montréal |