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

Alpha Time picker. Here is a useful feature I missed.

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

    #16
    Re: Alpha Time picker. Here is a useful feature I missed.

    But, Ken, if you were being just a bit reasonable, you would try to understand that no one... no one... creates and puts into production a component with only 1 or 2 controls which do not do anything. In fact, it's usually the opposite with components being created with far too much capability.

    Components are being built with 50+ controls across many pages/panels, embedded components, Javascript processing, server-side processing, offline capabilities and host of other features. This is the norm.

    Your example of 1 or 2 orphan controls doesn't happen in the real world. I'm surprised you don't understand that.

    Comment


      #17
      Re: Alpha Time picker. Here is a useful feature I missed.

      When I look Michaels time picker example and I look the output html page and then I compare the source code 1600 lines needed plus 1,6 MB javascript to produce the most simple time picker I really do not understand it. Not at all.

      Comment


        #18
        Re: Alpha Time picker. Here is a useful feature I missed.

        Originally posted by kkfin View Post
        When I look Michaels time picker example and I look the output html page and then I compare the source code 1600 lines needed plus 1,6 MB javascript to produce the most simple time picker I really do not understand it. Not at all.
        Is it really 1.6Mb? If so, then I have to agree with Ken, that's pretty heavy for what it is.
        My largest UX component is 1.9Mb in total ... and it is a monster in terms of number of controls!
        Last edited by iRadiate; 03-13-2017, 12:43 PM. Reason: corrected size
        Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

        Comment


          #19
          Re: Alpha Time picker. Here is a useful feature I missed.

          We posted this component because a customer asked us to change something in the time picker display.

          I was shocked how easy the change was to make in Alpha.

          The component is running on a G5 server in Central Java, Indonesia. When we host development components there DNS will be very slow. The internet is truly terrible so speed is not really a fair talking point.

          Time picker.png

          Comment


            #20
            Re: Alpha Time picker. Here is a useful feature I missed.

            Well... if someone doesn't want to understand... then they can't understand.

            However, I have to agree with Ken and Stephen... if I required a component containing 2 controls... and that component has no logic, and serves no useful purpose, but that loads 1.7Mb of libraries and 1600 lines of code... that's simply too much. So I would have to go off and find a better development system to create and run my useless component and try my very best to get it as small as possible.

            I'll bet I could do this without jQuery and make it smaller than Ken's at .63Mb... and that jQuery min is 85Kb??? Yikes... that's huge for just 2 time controls. That 85,000 bytes... ridiculous... for just running 2 controls... doesn't make any sense.

            Comment


              #21
              Re: Alpha Time picker. Here is a useful feature I missed.

              Just noticed this I know it is Knit picking but I would be fired if I served this up.

              Here is same done with jqwidgets. Link in the post.

              I realise I don't need the bloated UX but I do need to quickly fulfil my customers desires. I don't have time or the desire to find every little component bug test it and learn a different paradigm for each element. I would rather put another processor in the server and give SQL a little more ram.

              Comment


                #22
                Re: Alpha Time picker. Here is a useful feature I missed.

                Michael, prototyping something is another question. If you look my example source code you notice I have also used code generator. It did took from me two lines of own javascript to produce the example. But my prototypes footprint is totally different like yours.

                The hard thing seems to understand is that whatever you do with UX the minimum output is 1600 lines of code plus 1,6 MB javascript. It is same do you publish just a period or 50 controls. You get always full load source code. If you publish 50 -100 UX you can just wonder how hard your server hast to work serving meaning less source code. Also UX is today maybe the most common building block that developers use also for very simple tasks so this problem hits hard for the performance of developers applications.

                Comment

                Working...
                X