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

Number of UX components in a PhoneGap Mobile Application

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

    Number of UX components in a PhoneGap Mobile Application

    I've looked at the sample applications built by Alpha and all of them seem to have a single UX component. Is that by design or by limitation. Suppose you wanted to build a mobile app with several different modules. Could you put each module in it's own UX and have a single menu that opens a UX which is in turn filled with Panel Cards?

    Mostly curious about the best approach to take for mobile applications that extend beyond a simple few panel cards.

    Thanks,
    Jeremy

    #2
    Re: Number of UX components in a PhoneGap Mobile Application

    Yes... use the Embedded Object control, found under Other Controls, for embedding a "child" UX component into a main... or "parent" UX component. In the embedded component control properties, look at Optimization for the different options you have for loading the embedded UX.

    Comment


      #3
      Re: Number of UX components in a PhoneGap Mobile Application

      I have a one stop shop approach on this an it works fine and I don't use embeded controls, I'm not saying embeded controls is not an option, I'm just saying I don't use them successfully and that's just me I suppose, many of my build work perfectly with 10 plus data bound View Box or List components in a single UX, the planning is the key. Both ways will certainly get you to where you want to be. Using the parent child relationships in List controls keeps things very tight and efficient. I would say this - don't overuse anything in your build - every control has many properties and generates a lot of code, reuse where possible using dynamic javascript behind the scenes to repurpose controls, whenever possible. If you go down the path I use, ensure when planning your tables, ensure every field had a unique value that represents the table, a common practice is to say use ID as the field name for the primary key and an Identity setting in all the tables - what you need to keep in-mind is the tables and fields are going to be in the one space so you have a prefix like EmployeeID, CientID, CategoryID etc. and do the same in every field of the table and then you can use AA's power to dynamically generate Controls as you develop in the UX - good luck..
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Re: Number of UX components in a PhoneGap Mobile Application

        I use nested lists like Pete and re-use controls where possible. I don't know that naming the fields is important to the code, but knowing what your working with is so I can say that's some good advice as well - naming makes it easier to remember what the heck your doing, lol. On the flip side, I also use embedded UX's and THAT seems to be working out very well, in fact even better and I will say why.
        So the difference between Pete's advice and Davids is (for me) a matter of upkeep.
        I have one UX that is very large with about 10 lists, if I make an update and that update has repercussions affecting other lists - then the whole UX is botched since my application is live and have users actually using this UX - I get phone calls.
        I also have another UX with four embedded UX's, if I make a change to one of the UX's not as many users would notice because it's just a piece that might be botched and everything else is still rolling swimmingly.

        So in short I think they both offered good advice. Planning is the key. I have that one large UX with many nested lists because it is so very much easier to cascade changes and reuse controls with out creating variables, state or session because the values are all there and everything about the data from several tables is all loaded.
        It really depends on what your use case is, I guess.
        Why not build it both ways? See what works for you.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

        Working...
        X