Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

In UX component, when to use GRID versus LIST?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    In UX component, when to use GRID versus LIST?

    I'm looking for some opinions on when to use a GRID versus a LIST in a UX component.

    For basic actions it seems the LIST is well suited to a mobile device with small screen real estate. With various buttons and events you can pop up additional information as required (though this can complicate your UX design and the number of panels).

    For complex actions and multi-field displays it seems the GRID component is the better choice. However this doesn't scale as well.

    I built my original mockup application in A5v11 and used GRIDs to test table completeness and interaction. However, now I'm building UX components for what is expected to be primarily a mobile application.

    So I'm looking for both opinion and experience (lessons taught in pain) regarding what may be the best choice.

    I'm in the middle of building things now... so anything anyone has to offer will be appreciated.

    #2
    Re: In UX component, when to use GRID versus LIST?

    Working a lot with both I find grids to be the ideal front end for searching and displaying results while the Ux component is perfect for showing the detail view in a form. The UX component is much more flexible in layout, design and controls and has the added advantage of not having to be data bound. This allows me to display for instance photos from a directory in a list control populated by a custom xbasic function and not having to embed the files in my database or resort to coding image reference fields.
    Brad Weaver, President
    ComputerAid International
    Ottawa ON Canada
    Versailles KY USA
    www.compuaid.com

    Comment


      #3
      Re: In UX component, when to use GRID versus LIST?

      Brad,

      Thanks for the input. That's the kind of stuff I find useful.

      I'm not having much success with GRIDs within a UX/mobile context. Mine were originally designed to be tight and small as a sidebar to a main screen with PDF content within the A5v11 browser-based arena. They don't seem to render very well in the UX component. It could be me (and my properties) or perhaps the CSS files... though they aren't unusual.

      I'm largely working to redesign using LISTs and popup info for anything that doesn't fit easily on the smallest of PDA screens.

      I'm having a lot of challenges getting things to work for multiple screen orientations and device types. Simple scaling of a component to "fit the entire panel" works well. But anywhere where I've got more than one element in a panel results in some sizing oddities. I'll finish my working mockup and then have the folks at Alpha take a look (too many things to post in one bug or one forum).

      If you have a chance and it doesn't expose anything proprietary, I'd be interested in seeing a screen shot or two of your app just to take measure on what others are doing.

      (Trivia: I'm a fellow Canuck; Saskatchewanite, then T.O. area x 5yrs, then NYC x 8yrs, then Austin x10 yrs. I'll check out your company!)

      Comment

      Working...
      X