1. #21
    Ext User
    Join Date
    Jul 2007
    Posts
    4
    Vote Rating
    0
    wxz20032003 is on a distinguished road

      0  

    Default it is greate

    it is greate


    u mean a tag ?just like some open-src program?

  2. #22
    Sencha User
    Join Date
    Jul 2007
    Posts
    26
    Vote Rating
    0
    mglaser is on a distinguished road

      0  

    Default Sorry, I meant Attribute

    Sorry, I meant Attribute


    By tag I meant attribute eg:

    <div id="toolbar" extType="Ext.PagingToolbar" container="gridFoot" dataStore="ds" pageSize="20" displayInfo="true" displayMsg="total {2} results found. Current shows {0} - {1}" emptyMsg="not result to display"></div>

    to instantiate the toolbar rather than:

    var paging = new Ext.PagingToolbar(gridFoot, ds, {
    pageSize: 20,
    displayInfo: true,
    displayMsg: 'total {2} results found. Current shows {0} - {1}',
    emptyMsg: "not result to display"
    });

  3. #23
    Sencha - Community Support Team JeffHowden's Avatar
    Join Date
    Mar 2007
    Location
    Forest Grove, OR
    Posts
    1,038
    Vote Rating
    1
    JeffHowden is on a distinguished road

      0  

    Default


    You should definitely be using namespaces on those attributes:

    HTML Code:
    <div id="toolbar" ext:Type="Ext.PagingToolbar" ext:container="gridFoot" ext:dataStore="ds" ext:pageSize="20" ext:displayInfo="true" ext:displayMsg="total {2} results found. Current shows {0} - {1}" ext:emptyMsg="not result to display"></div>
    Jeff Howden
    Ext JS - Support Team Volunteer
    jeff@extjs.com

    Any and all code samples that are authored by me and posted on the Ext forums or website are hereby released into the public domain and I release anyone or entity of liability by using said code samples unless explicitly stated otherwise.

    Opinions are mine and not necessarily endorsed by Ext, LLC. Please do not contact me directly for assistance unless requested by me.

  4. #24
    Sencha - Ext JS Dev Team Animal's Avatar
    Join Date
    Mar 2007
    Location
    Notts/Redwood City
    Posts
    30,546
    Vote Rating
    64
    Animal is a jewel in the rough Animal is a jewel in the rough Animal is a jewel in the rough

      0  

    Default


    Client side tags are not as useful IMNSHO as server-side tags which may take full Java Objects as attributes, introspect app metadata and create complex markup and script.

    For example, I now have an <aspicio:view> tag which creates a DnD enabled Ext.View of a collection of beans. So in my JSP I have

    Code:
    	<aspicio:column>
    		<aspicio:fieldset style="margin-left:10px" legend="Subcomponents">
    			<aspicio:view
    				style="height:300px"
    				dropgroup="availableSubcomponents"
    				draggroup="availableSubcomponents"
    				id="subComponents"
    				collection="<%=entity.getSubComponents()%>"
    				type="<%=Component.class%>"
    				template="<div id='subcomponent_{id}' class='Subcomponent'><img align='top' height='16px' width='16px' src='{entityImageUrl}'>{componentDescription}</div>"/>
    		</aspicio:fieldset>
    	</aspicio:column>
    	<aspicio:column>
    		<aspicio:fieldset style="margin-left:10px" legend="Available subcomponents">
    			<aspicio:view
    				style="height:300px"
    				dropgroup="availableSubcomponents"
    				draggroup="availableSubcomponents"
    				select="multi"
    				collection="<%=availableSubcomponents%>"
    				type="<%=Component.class%>"
    				template="<div id='component_{id}' class='Component'><img align='top' height='16px' width='16px' src='{entityImageUrl}'>{componentDescription}</div>"/>
    		</aspicio:fieldset>
    	</aspicio:column>
    It provides views of the "Component" objects in the two collections, and allows drag/dropping between the two (because they share dragGroup/dropGroup ids).

    The {xxx} substitution elements in the Template correspond to properties of the bean class.

    Most JSP authors seem to be clueless about Javascript, and this seems like the best way to get a good UI without frightening them!

  5. #25
    Ext User
    Join Date
    Mar 2007
    Posts
    15
    Vote Rating
    0
    cilquirm is on a distinguished road

      0  

    Default


    Quote Originally Posted by mglaser View Post

    <div id="toolbar" extType="Ext.PagingToolbar" container="gridFoot" dataStore="ds" pageSize="20" displayInfo="true" displayMsg="total {2} results found. Current shows {0} - {1}" emptyMsg="not result to display"></div>
    That's dojo-esque, and I personally don't think it's a pretty good idea. When I'm formulating pages, especially rich ones, a lot of them are just bare pages with just a few empty divs here and there.

    The one thing that always bothered me about it was the namespacing of non-xhtml attributes. I mean, if you want to use xhtml, you should be able to do it properly :

    <div id="toolbar" ext:extType="Ext.PagingToolbar" ext:container="gridFoot" ext:dataStore="ds" ext:pageSize="20" ext:displayInfo="true" ext:displayMsg="total {2} results found. Current shows {0} - {1}" ext:emptyMsg="not result to display"></div>


    -a

  6. #26
    Sencha - Community Support Team JeffHowden's Avatar
    Join Date
    Mar 2007
    Location
    Forest Grove, OR
    Posts
    1,038
    Vote Rating
    1
    JeffHowden is on a distinguished road

      0  

    Default


    Quote Originally Posted by Animal View Post
    Client side tags are not as useful IMNSHO as server-side tags which may take full Java Objects as attributes, introspect app metadata and create complex markup and script.
    I agree completely. I only mentioned namespaced attributes because the OP was suggesting client-side tags.
    Jeff Howden
    Ext JS - Support Team Volunteer
    jeff@extjs.com

    Any and all code samples that are authored by me and posted on the Ext forums or website are hereby released into the public domain and I release anyone or entity of liability by using said code samples unless explicitly stated otherwise.

    Opinions are mine and not necessarily endorsed by Ext, LLC. Please do not contact me directly for assistance unless requested by me.

  7. #27
    loukili
    Guest

    Default Lilya Jsf Widgets with Ajax Capabilities Released

    Lilya Jsf Widgets with Ajax Capabilities Released


    Hi guys,

    Lilya - Jsf Widgets with Ajax Capabilities based on ExtJs and JsGraphics is now available (lilya 1.0-beta-1).

    Demo, documentation and downloads at Lilya Home Page

    We need your comments !

    I hope that this work helps interested.

  8. #28
    Ext User
    Join Date
    May 2007
    Location
    Minnesota
    Posts
    66
    Vote Rating
    0
    IGx89 is on a distinguished road

      0  

    Default


    Good to hear! However, on IE7 (haven't tried other browsers) your "View Sources" link just grays out everything without doing anything productive.

  9. #29
    loukili
    Guest

    Default


    thanks matthew. Now it's working.

  10. #30
    Ext User
    Join Date
    Jul 2007
    Posts
    7
    Vote Rating
    0
    quentin is on a distinguished road

      0  

    Default


    loukili,

    your forum registration appears broken. i never received an activation email per the instructions. i am trying to run your demos using an embedded tomcat server and i get the following exceptions:

    com.qlogic.commons.resources.xml.ResourceReaderException: com.qlogic.commons.resources.xml.ResourceReaderException: java.lang.ClassNotFoundException: [C
    at com.qlogic.commons.resources.ResourceEntries.load(ResourceEntries.java:100)
    at com.qlogic.commons.resources.ResourceEntries.<init>(ResourceEntries.java:75)
    at com.qlogic.commons.resources.xml.impls.DefaultResourceReader.<init>(DefaultResourceReader.java:81)
    at com.qlogic.commons.resources.xml.impls.DefaultResourceReader.<init>(DefaultResourceReader.java:101)
    at com.qlogic.products.lilya.JsfUIPlatformServlet.loadPlatform(JsfUIPlatformServlet.java:96)

    and

    com.qlogic.commons.resources.xml.ResourceReaderException: com.qlogic.commons.resources.ResourceCreatorException: la balise [bean] n'est enregistr