Python Programmer

Location:  Gdansk, Poland

Quick Links

View  Show Available Profiles


Writing Eviscape API Hosted App

Public  tutorial posted on  Wed, 11 Feb 2009 by  iapain


Writing simple API Hosted APP

 

In previous post( <span class="http-markup"><a href="http://www.eviscape.com/evis/how-to-created-eviscape-hosted-apps-reehrdma/" rel="nofollow">http://www.eviscape.com/evis/how-to-created-eviscape-hosted-apps-reehrdma/</a></span> ) I explained how you can create an hosted application on eviscape. In this post I'll explain how you can create simple cool ajax application on eviscape using eviscape API and jQuery.

 

Open your hosted app (code window). You can write any valid HTML and you may also use Django template, by default we pass {{ member }}(user name), {{ member_id }}(id of an user), {{ node }}(current node name), {{ node_id }}(current_node_id).

 

In this example, we'll create a simple app which would fetch all evis of nodes.

  • Import jQuert
  • Add supportive HTML
  • Add Javascript

 Here is you go <span class="http-markup"><a href="http://www.eviscape.com/hosted/apps/7oky4uwo0mjw8ypzawdias8tav1nbqtp" rel="nofollow">http://www.eviscape.com/hosted/apps/7oky4uwo0mjw8ypzawdias8tav1nbqtp</a></span>

 

and source can be viewed here <span class="http-markup"><a href="http://www.eviscape.com/apps/source/7oky4uwo0mjw8ypzawdias8tav1nbqtp" rel="nofollow">http://www.eviscape.com/apps/source/7oky4uwo0mjw8ypzawdias8tav1nbqtp</a></span>

 


    #10

    At least we should have member_name, node_name (as well as mem_name, nod_name)

    i.e. member is not clear


    - SimonRedfern (Simon Redfern) 5 years, 1 month ago (Permalink )
    #9

    I like your white background :-)


    - SimonRedfern (Simon Redfern) 5 years, 1 month ago (Permalink )
    #8

    I think we should stick to {{ member_name }}


    - iapain (iapain) 5 years, 7 months ago (Permalink )
    #7

    Simon loves {{ mem_name }} :)


    - iapain (iapain) 5 years, 7 months ago (Permalink )
    #6

    Lets add some markup here :)


    - iapain (iapain) 5 years, 7 months ago (Permalink )
    #5

    checking duplication

    For now we are supporting both {{ mem_id }} and {{ member_id }}. Here its templating language, there its API calls


    - iapain (iapain) 5 years, 7 months ago (Permalink )
    #4

    For now we are supporting both {{ mem_id }} and {{ member_id }}. Here its templating language, there its API calls


    - iapain (iapain) 5 years, 7 months ago (Permalink )
    #3

    but but but. then users will become confused because the API calls use different names. So I would say we could offer the long form (member_name) and the short form (mem_name). But we should emphasise the short form for consistency because consistency in naming conventions is more important than any one "style" of the moment.


    - SimonRedfern (Simon Redfern) 5 years, 7 months ago (Permalink )
    #2

    Well I still prefer mem_id, mem_name, nod_name, nod_id_current - but if we must have something else then at least it must be consistent: member_id, member_name, node_name, node_id_current


    - SimonRedfern (Simon Redfern) 5 years, 7 months ago (Permalink )
    #1

    Ahh Hosted apps are like myspace & facebooks apps


    - Bart-Simpson (iapain) 5 years, 7 months ago (Permalink )