Page 12 of 12 FirstFirst ... 2101112
Results 111 to 116 of 116

Thread: Seeking feedback on the manual

  1. #111
    Join Date
    Dec 2001

  2. #112
    Join Date
    Jan 2004



    I have written a plugin manual for the Ocelot plugin, but it is 1.7mb! 22 pages and lot's of pics!!

    How can I make the PDF smaller, what pic format??


    Todd Reed
    Ocelot Automation Rookie

  3. #113
    Join Date
    Apr 2006


    How to do key combinations is a real mess. It took me ages to figure out how to do a simple key command as ALT + ENTER. It's very cyrptic the way you word it and no example on how to do it. This needs fixing in the manual.

  4. #114
    Join Date
    Nov 2003
    Hove, E Sussex, UK


    Hi John,

    You may of added this already, if not could you add TriggerNode.

    gir.TriggerNode(string GUID, number nodeid, boolean ParentCheck);
    Thx, Dan

    Onwards and Upwards!

  5. #115
    Join Date
    Oct 2001


    manual mentions: "osd.GetStyle("MenuDarkBlue"

    There is no list of existing styles, nor is there any info on how to make one (a template would be nice)

  6. #116
    Join Date
    Nov 2005
    Redditch, UK


    Quote Originally Posted by TooManyToyz View Post
    Just some general feedback and the manual and app.

    Here's what I see. The manual looks like it covers Girder functionality from perspective of the people that wrote it. In other words, it's accurate, but it isn't really written so that an average user will read it and be able to quickly create functional solutions.
    This is my exact frustration with the help files of both Girder and NetRemote... It's driven me crazy at times (after my Palm Tungsten alarm went off this afternoon during a very annoying time with NetRemote's incomplete help I picked up the Palm and bounced it off my bedroom wall without thinking - the lack of examples really annoyed me that much... still don't know where the heck the stylus from the Palm is )

    What is needed are examples and commented examples at that. Examples that shout "LOOK AT WHAT I CAN DO" yet are a confusing mess inside with numerous items having default names do nothing to help new users get to grips with the program. Having had to learn numerous computer languages over the years has brought me into contact with really good to really bad documentation in that time... unfortunately I have to say that the Girder and Netremote documentation aren't the best I have come across... They say a picture tells a thousand words. Well in programming terms a good, commented example can replace a thousand words.

    From the awards that Girder and NetRemote have received I would have expected a greater number of posters here which seems to suggest quite a number of people have tried the package and have got demoralised by the technical requirements to use the programs. Helping new users over the technical hump would greatly improve the take up of the programs IMHO. A lot of people give up when they are baffled by instructions that don't make things clear.

    Like I've said before, the programs themselves aren't bad, it's just having to either guess how to do things or having to ask others stuff that should be in the documentation. NetRemote's MediaBridge Generic Commands is a case in example. I recall reading that these commands are undocumented because Promixis is busy ATM and will give out fixes as needed. This is very unprofessional as it shows that documentation is very much a low priority and that is going to hurt profits in the long run.
    - John H
    * PROMIXIAN TO THE CORE! * (NetRemote2WholeHomePro + Girder5WholeHomePro + USB-UIRT + Touchscreens + WirelessControlSystems + ANNA) == AutomationHeaven
    - "IthinkI'mgoingtobantheuseofthespacebarinfuture..."

Page 12 of 12 FirstFirst ... 2101112

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts