Normative

  • Normative for skins names unification
    This is only for img developers.


    After the release of many skins i just realized that is time to estabilish a normative to merge the names in the .esml file, this is to have all the skins compatible on the already developed img.


    Colosseum, Da Vinci,Gemini, Pli, Castle, SifTeam, Nabilosat, DS Team, Juliet, SF team,ruDREAM,2 Gethe Stormreaken,Polar Team,DBBrothers,Ronaldd,Hydra,Peter Pan





    So use the same names for every of em, my proposal is the following:


    <value name="volume.slider.pos.x"
    <value name="volume.slider.pos.y"
    <value name="volume.slider.width"
    <value name="volume.slider.height"

    <value name="g_volume.progress.pos.x"
    <value name="g_volume.progress.pos.y"
    <value name="g_volume.progress.width"
    <value name="g_volume.progress.height"


    <img name="g_volume_progress"


    <img name="progress_snr_small"
    <img name="progress_agc_small"
    <img name="progress_ber_small"
    <img name="progress_event"


    <img name="audio_no"
    <img name="audio_on"
    <img name="vt_no"
    <img name="vt_on"

    <eLabel name="k1" - TV Mode
    <eLabel name="k2" - Radio Mode
    <eLabel name="k3" - Files Mode
    <eLabel name="k4" - VCR
    <eLabel name="k5" - Timer
    <eLabel name="k6" - Setup
    <eLabel name="k7" - Games
    <eLabel name="k8" - Information
    <eLabel name="k9" - Shutdown
    <eLabel name="k0" - (free for possible name)


    <eLabel name ="fq_text"
    <eLabel name ="feq"
    <eLabel name="pol"

    <eLabel name ="fc"
    <eLabel name ="fc_fec"


    <eLabel name ="sr_text"
    <eLabel name ="sr_snr"


    <eLabel name ="videoformat"


    <eLabel name ="date"


    <eLabel name="pro_name"


    <eLabel name ="cam_info"
    <eLabel name ="ecm_info"


    <eLabel name="time"
    <eLabel name="fulltime"


    <eLabel name="ta_active" (tv signal)
    <eLabel name="now" (current event)

    <eLabel name ="snr"
    <eLabel name ="snr_num"
    <eProgress name ="snr_progress"


    <gProgress " name="g_snr_progress"

    <eLabel name ="agc"
    <eLabel name ="agc_num"
    <eProgress name ="agc_progress"


    <gProgress name="g_agc_progress"

    <eLabel name ="ber"
    <eLabel name ="ber_num"
    <eProgress name ="ber_progress"


    <gProgress name="g_ber_progress"

    <eLabel name="picon"


    <eLabel name ="button_card"
    <eLabel name ="button_emu"
    <eLabel name ="button_spider" (rete or net)


    <eProgress name="progress_bar"


    <gProgress name="progress_event"


    <eLabel pixmap="button_red" name="button_red_enabled"
    <eLabel pixmap="button_gray" name="button_red_disabled"
    <eLabel pixmap="button_green" name="button_green_enabled"
    <eLabel pixmap="button_gray" name="button_green_disabled"
    <eLabel pixmap="button_yellow" name="button_yellow"
    <eLabel pixmap="button_yellow" name="button_yellow_disabled"
    <eLabel pixmap="button_blue" name="button_blue" />
    <eLabel pixmap="button_blue" name="button_blue_disabled"

    <eLabel pixmap="osd_crypt_no" name="osd_crypt_no"
    <eLabel pixmap="osd_crypt_on" name="osd_crypt_on"
    <eLabel pixmap="osd_dolby_no" name="osd_dolby_no"
    <eLabel pixmap="osd_dolby_on" name="osd_dolby_on"
    <eLabel pixmap="osd_format_no" name="osd_format_no"
    <eLabel pixmap="osd_format_on" name="osd_format_on"
    <eLabel pixmap="maudio_no" name="button_yellow_disabled"
    <eLabel pixmap="maudio_on" name="button_yellow_enabled"
    <eLabel pixmap="vtext_no" name="button_blue_disabled"
    <eLabel pixmap="vtext_on" name="button_blue_enabled"
    <eLabel pixmap="plo" alphatest="on" (developer's team logo)


    <eLabel pixmap="beta_ecm" name="beta_ecm"
    <eLabel pixmap="beta_emm" name="beta_emm"
    <eLabel pixmap="beta_no" name="beta_no"
    <eLabel pixmap="irdeto_ecm" name="irdeto_ecm"
    <eLabel pixmap="irdeto_emm" name="irdeto_emm"
    <eLabel pixmap="irdeto_no" name="irdeto_no"
    <eLabel pixmap="seca_ecm" name="seca_ecm"
    <eLabel pixmap="seca_emm" name="seca_emm"
    <eLabel pixmap="seca_no" name="seca_no"
    <eLabel pixmap="via_ecm" name="via_ecm"
    <eLabel pixmap="via_emm" name="via_emm"
    <eLabel pixmap="via_no" name="via_no"
    <eLabel pixmap="nagra_ecm" name="nagra_ecm"
    <eLabel pixmap="nagra_emm" name="nagra_emm"
    <eLabel pixmap="nagra_no" name="nagra_no"
    <eLabel pixmap="cw_ecm" name="cw_ecm"
    <eLabel pixmap="cw_emm" name="cw_emm"
    <eLabel pixmap="cw_no" name="cw_no"
    <eLabel pixmap="nds_ecm" name="nds_ecm"
    <eLabel pixmap="nds_emm" name="nds_emm"
    <eLabel pixmap="nds_no" name="nds_no"
    <eLabel pixmap="conax_ecm" name="conax_ecm"
    <eLabel pixmap="conax_emm" name="conax_emm"
    <eLabel pixmap="conax_no" name="conax_no"


    <img name="menu_osd" src="menu_osd.png" (vertical menu)

    <img name ="bandamenu" src ="bandamenu.png" (horizontal menu)


    <object name="ezap_lite"
    Thank you for your cooperation


    Ciao
    Army

  • I believe the suggestion made here is viable. However, cryptic and ambiguous naming convensions must be avoided. Moreover, descriptions for each entry must be written and indoctrinated to enable the developers to understand and implement as intended by the author and agreed upon by each of the image maintainers. This may seem like overkill now, but later will help developer, maintainer and more importantly the user to precisely understand the entries.

    johnbock


    13.0/19.2
    NFS/QNAP TS-219P/debian - lenny
    NFS/eSATA SheevaPlug/emdebian (ubifs) - squeeze

  • Quote

    Originally posted by matrix10
    Thx Army


    This will make our life more easy.


    ByE MX


    Io ho fatto la proposta adesso pensaci tu che sai l'inglese vedi se puoi mettere d'accordo i vari sviluppatori di img io purtroppo parlo solo italiano


    Altri codici


    DreamCrypt CA Visuation


    <eLabel pixmap="dc_ecm" name="dc_ecm"
    <eLabel pixmap="dc_emm" name="dc_emm"
    <eLabel pixmap="dc_no" name="dc_no"


    Ca ID


    name="caid_text"
    name ="ca_id"


    Provider ID


    name="prvid_text"
    name ="prv_id"



    Ciao
    Army

  • If this should be normative, it would be good if everyone could understand. Don't you agree?

    johnbock


    13.0/19.2
    NFS/QNAP TS-219P/debian - lenny
    NFS/eSATA SheevaPlug/emdebian (ubifs) - squeeze

  • Quote

    Originally posted by johnbock
    If this should be normative, it would be good if everyone could understand. Don't you agree?


    Hai ragione ma io parlo solo italiano


    Ciao
    Army

  • Quote

    Original von army


    Hai ragione ma io parlo solo italiano


    Ciao
    Army


    Oh, now I understand :rolleyes:

    johnbock


    13.0/19.2
    NFS/QNAP TS-219P/debian - lenny
    NFS/eSATA SheevaPlug/emdebian (ubifs) - squeeze

  • if you a making skins and images you will understand
    more or less all commands if not
    then you have to learn if you like.


    Skins language is like with all other programming.


    MX

  • Quote

    Original von matrix10
    if you a making skins and images you will understand
    more or less all commands if not
    then you have to learn if you like.


    Skins language is like with all other programming.


    MX


    I've have already designed and implemented my own Skin; that's not the problem. I was being sarcastic: I'm not italian literate;)

    johnbock


    13.0/19.2
    NFS/QNAP TS-219P/debian - lenny
    NFS/eSATA SheevaPlug/emdebian (ubifs) - squeeze