You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by rahmoune patrick <js...@yahoo.fr> on 2006/09/26 17:46:16 UTC

RE : Re: FisheyeList problem using nightly

No pb, I am waiting for your version with scroller :-)
   
  Lots of other things to work on.
   
  Thank you
   
  patrick
  
Werner Punz <we...@gmx.at> a écrit :
  rahmoune patrick schrieb:
> Hi all,
> 
> I'm using Myfaces 1.1.5 + tomahawk nightly (from the 25/09) + facelets +
> ajax4jsf + shale and I'm unable to make the fisheye list works.
> 
> I get the following error message in Firefox
> 
> postCreate is not defined in .../xxx/xxx/xxx/ dojo.js line 263
> 
> Does someone has seen this pb before? 
> 
> patrick
> 
Just to explain, I am adding scroller functionality currently and I am
almost done with it, the code was a major overhaul of the original dojo
code and will be pushed back to dojo.

I fixed some isses yesterday, along the lines of some postcreate
problems caused by the original dojo code and my extension (but not the
exactly same error, I would never have committed the codebase
if I had it)

So all I can say is please hang tight and wait a little bit longer, the
commit will be tonight.
After that the problems hopefully will be gone.



 		
---------------------------------
 Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici. 

Re: RE : Re: RE : Re: FisheyeList problem using nightly

Posted by Werner Punz <we...@gmx.at>.
rahmoune patrick schrieb:
> Hi werner !!
>  
> It is working now. Thank you very much.
>  
> I've tested the scroller and it is working.
>  
> I'm sorry to tell you this but I do not like it 
>   - I think the arrow should be placed elsewhere. They are too closed
> from the items. But I don't know where, maybe on the bottom ?
>   - I don't like to arrow icon
>  
> :-)
>  

Yes the scroller positions are too near to the icons
and the scroller icons themselves are no icons, just plain dojo buttons,
but expect changes in this area soon anyway.

(probably some css attributes... I have to look into the dojo button api)

I am aware of those problems.

Thanks for testing, dont expect any breakage of the fisheye in the near
future anymore, just visual corrections on the parts you already noticed.
It was more of a concern to me to get the thing working properly again
than the visual aspects of it.


Re: RE : Re: RE : Re: RE : Re: FisheyeList problem using nightly

Posted by Werner Punz <we...@gmx.at>.
Ok since it is not that needed anymore, I will investigate
the two new problems tomorrow (my hands need rest)


Werner Punz schrieb:
> rahmoune patrick schrieb:
>> Hi Werner,
>>  
>> After some investigation, if I provide an absolute url "http://....." to
>> the icon attribute
>> of the navigation menu item. The icon pb is solved.
> Ok this looks like some bug in the original fisheye code,
> not sure what happens there.
> 
> But I hope I can reproduce it here, to see how this has occurred.
> 
> 
>> Any explanation of what's going on is welcome?
>> Anyway, I don't have any blocking pb with the fish eye list now.
>>  
>> For the itemPadding property I will stay with 10
>>  
> no problem, thanks for testing.
> 
> 


Re: RE : Re: RE : Re: RE : Re: FisheyeList problem using nightly

Posted by Werner Punz <we...@gmx.at>.
rahmoune patrick schrieb:
> Hi Werner,
>  
> After some investigation, if I provide an absolute url "http://....." to
> the icon attribute
> of the navigation menu item. The icon pb is solved.
Ok this looks like some bug in the original fisheye code,
not sure what happens there.

But I hope I can reproduce it here, to see how this has occurred.


> Any explanation of what's going on is welcome?
> Anyway, I don't have any blocking pb with the fish eye list now.
>  
> For the itemPadding property I will stay with 10
>  
no problem, thanks for testing.


RE : Re: RE : Re: RE : Re: FisheyeList problem using nightly

Posted by rahmoune patrick <js...@yahoo.fr>.
Hi Werner,
   
  After some investigation, if I provide an absolute url "http://....." to the icon attribute
  of the navigation menu item. The icon pb is solved. 
  Any explanation of what's going on is welcome? 
  Anyway, I don't have any blocking pb with the fish eye list now.
   
  For the itemPadding property I will stay with 10
   
  Thank you again 
   
  patrick
   
  
Werner Punz <we...@gmx.at> a écrit :
  rahmoune patrick schrieb:

> 
> If I ask to the view to be re-rendered (click on the menu again), the
> arrows are displayed but the items are no more displayed. But, what is
> funny is tha t the tooltips are displayed.
> 
Definitely my new code... I will look into it, that problem is new...
Which browser? Which version? As I said, I never had the problem.
Just a sidequestion, do you have cookies disabled, because the scroller
uses cookie savestating for keeping its state. (Dojo mechanism)

Do you get this error also if you hit a full page refresh or just if you
hit the menu?
What happens exactly? Do you hit a button and then everything has
dissapeared or does it happen if you scroll?
Sorry to be so precise here, but the info is a little bit to vague to
nail the problem down.

> Second,
> 
> If I set the itemPadding property to 30, (note my item size is 48), the
> item get the same
> size of the arrow !!!
> 

I will look into that as well, not a big one, but has to be fixed...

I think I will move to the original dojo code for non scroller cases,
in the renderer, to remove problems like those which I did not have upfront.

(I did my own class for that)

So expect things to work for you again tomorrow with the old dojo
fisheye code.



 		
---------------------------------
 Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici. 

Re: RE : Re: RE : Re: FisheyeList problem using nightly

Posted by Werner Punz <we...@gmx.at>.
rahmoune patrick schrieb:

>  
> If I  ask to the view to be re-rendered (click on the menu again), the
> arrows are displayed but the items are no more displayed. But, what is
> funny is tha t the tooltips are displayed.
>  
Definitely my new code... I will look into it, that problem is new...
Which browser? Which version? As I said, I never had the problem.
Just a sidequestion, do you have cookies disabled, because the scroller
uses cookie savestating for keeping its state. (Dojo mechanism)

Do you get this error also if you hit a full page refresh or just if you
hit the menu?
What happens exactly? Do you hit a button and then everything has
dissapeared or does it happen if you scroll?
Sorry to be so precise here, but the info is a little bit to vague to
nail the problem down.

> Second,
>  
> If I set the itemPadding property to 30, (note my item size is 48), the
> item get the same
> size of the arrow !!!
>  

I will look into that as well, not a big one, but has to be fixed...

I think I will move to the original dojo code for non scroller cases,
in the renderer, to remove problems like those which I did not have upfront.

(I did my own class for that)

So expect things to work for you again tomorrow with the old dojo
fisheye code.


RE : Re: RE : Re: FisheyeList problem using nightly

Posted by rahmoune patrick <js...@yahoo.fr>.
Hi werner !!
   
  It is working now. Thank you very much.
   
  I've tested the scroller and it is working.
   
  I'm sorry to tell you this but I do not like it  
    - I think the arrow should be placed elsewhere. They are too closed from the items. But I don't know where, maybe on the bottom ?
    - I don't like to arrow icon
   
  :-)
   
  But I don't need the scroller now.
   
  I still have some pb with the fish eye list that may not be related to the component itself.
   
  First,
   
  If I  ask to the view to be re-rendered (click on the menu again), the arrows are displayed but the items are no more displayed. But, what is funny is that the tooltips are displayed.
   
  Second,
   
  If I set the itemPadding property to 30, (note my item size is 48), the item get the same
  size of the arrow !!!
   
  Hope this help.

  patrick
   
  ps: sorry for the tipo, it is very late here.
  
Werner Punz <we...@gmx.at> a écrit :
  rahmoune patrick schrieb:
> No pb, I am waiting for your version with scroller :-)
> 
> Lots of other things to work on.
> 
Hi Patrick, i just committed the scrollable version
if you add a param visibleWindow with a scroller window size
in number of icons you get the added scroller functionality
if you leave that out, you get the normal fisheye without any added 
scroller buttons....

Please give the latest trunk code a test (you have to do a self build), 
if it works now again
if not, please send me a copy of your generated html markup
so that I can look into the problem tomorrow night...

I am very eager to have this tested in real world situations
because the changes I made to the original fisheye code were severe
and I do not have enough testcases on my hand...



 		
---------------------------------
 Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. Cliquez ici. 

Re: RE : Re: FisheyeList problem using nightly

Posted by Werner Punz <we...@gmx.at>.
rahmoune patrick schrieb:
> No pb, I am waiting for your version with scroller :-)
>  
> Lots of other things to work on.
>  
Hi Patrick, i just committed the scrollable version
if you add a param visibleWindow with a scroller window size
in number of icons you get the added scroller functionality
if you leave that out, you get the normal fisheye without any added 
scroller buttons....

Please give the latest trunk code a test (you have to do a self build), 
if it works now again
if not, please send me a copy of your generated html markup
so that I can look into the problem tomorrow night...

I am very eager to have this tested in real world situations
because the changes I made to the original fisheye code were severe
and I do not have enough testcases on my hand...