Shared sample projects

Since documentation is not up to date, it is not always possible to figure out the latest implementation from the documents or videos.

It would help a lot if COT teams creates a git hub with samples for COT functionality.
1 person likes
this idea
+1
Reply
  • A dedicated set of introductory videos with the most-up-to-date features is available at https://www.youtube.com/playlist?list....

    This playlist shows the most up-to-date techniques of incremental enhancements to the same app that starts with a single table and grows into a complex application with real-world deployment. We will be adding many new episodes that cover various aspects of development and deployment.

    The future episodes will cover deployment with private slots, sharepoint online, google/facebook login, native mobile apps and much more.

    Our product is a "low code" development tool. Seeing a snippet of XML configuration file or a bit of HTML without giving a visual sample is relatively useless. Subscribe to our channel and stay up to date with the latest videos - https://www.youtube.com/user/codeonti.... We are trying to make new videos to go out weekly.

    We are also figuring the best format to transform videos into PDF tutorials.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • To be honest, COT is a "low code"+"low quality"+"high troubleshooting" development tool. Unfortunately, your lack of current documentation and video tutorial approach is not changing this. I have watched first twelve episodes of ToDo App tutorials. You are missing important details in these video tutorials. You are assuming that people makes the same assumption you make while naming their fields. There are cases even the name of controller fields are important.

    For example, Episode 8 about many-to-many fields misses important details. This video was posted on 2nd of March. But there are recent community forum threads related to 'Field with lookup controller not found in target controller'. Although I had watched that video multiple times, I experienced that same issue and had to go through forums and find out important details which were not even talked about in the video.

    If you share working samples with us through GitHub, we can better understand the details missed in video tutorials. This will reduce your support costs and save us a lot of time.

    Also, these samples will give us a chance to provide you some simple repros for issues we encounter. It is not always easy for us to send you our proprietary work for repros. But we may be able to repro them with your shared samples.

    Thanks.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • keturkarslan,

    We certainly take issue with "low quality"+"hight troubleshooting" characterization.

    Please share the name of the other product in your toolbox that offers a perfect mix you are looking for. Better yet, point out the product that in fact has built-in support for many-to-many fields described in Episode 8. The issue in the post described at http://community.codeontime.com/codeo... has been due to some unusual manipulations on the part of the developer that our product is not smart enough to foresee.

    It is true that we do not cover every single aspect of further customization in the 10 minute video. Nor do we try to make assumptions about your database naming conventions. We are simply trying to show the steps one can follow and reproduce in the time approximately equal to the length of the video to eliminate the troubleshooting and guesswork.

    The simplest way to request additional information not covered in the video segments is to post a comment right there on the spot. We will gladly provide additional information or reference materials. Man, we will shout another video if needed!

    Experienced developers tend to make assumptions about certain technologies they encounter in their daily life. Our own team members frequently feel frustration with the work of others. ;-) Generally we find it useful to follow examples to the letter, making them work, and extending the example to meet our requirements.

    The Big Plan (Shhhh!!!)
    ==================

    Our development tool will undergo significant changes after the summer is over. Release 8.7.0.0 will go out in 4-5 weeks from now and introduce generation of native mobile apps to be used as front-ends of your server-side code.

    Another release 8.8.0.0 will be out by the end of August 2017 and will bring about completely disconnected pages that work only in offline mode when running in native front-ends and will also provide transaction input both in native apps and web browser clients in the forms with the DataView fields (Episode 7).

    After the dust is settled we will switch to production delivery of the next generation of the app generator. We call it Code On Time Version 9 or v9.

    We are ditching the current project designer in the favour of integrated JavaScript-based configuration tool, which is built into the apps. The hierarchy of data controllers, pages, fields, databases, tables, and many other things will be displayed alongside the app when activated. Drag & drop operations in the hierarchy and live data forms in design mode will change application definition. Object Inspector similar to the one found in Visual Studio will complement our current object property pages in v9.

    We will provide three alternative implementations of the backend for this new JavaScript-based integrated design environment:

    * One backend is the app generator you are using right now. It will run in the stealth mode on your computer, generate the project and have it compiled in response to your actions. The design environment and backend will not be included in the published apps. This is the equivalent of current Code On Time and will have exactly the same pricing. You will have access to this version, if your activation code is still valid at the time of the release. The projects created with various versions of CoT v8 will be fully compatible with the upcoming v9.

    * The second backend implementation will be hosted in the cloud and include a built-in database designer. It will require no software to be installed on the client device and will be accessible via major web browsers and native front ends for various mobile platforms. This is the equivalent of Unlimited Edition with a monthly subscription pricing model. The infrastructure will be located in Microsoft Azure. The name of this backend is Cloud On Time.

    * The third backend is the product called Private Cloud. This will be a special version of Cloud On Time that can be installed on premises. There will be a perpetual pricing based on the cores of the web server.

    Sample Shared Projects
    ========================
    The cloud app generator will enable easy prototyping and samples for various product features. It will have a community space available to demonstrate various techniques and samples with instant preview. We think it will offer a close equivalent of your idea with an added benefit of instant preview.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • I stand behind my "low quality"+"high troubleshooting" characterization for now. I am not favoring another product in any price range. Otherwise, I would be using that product. Instead, I am opening tickets for COT bugs regularly.

    "Not having a better alternative" should not be a justification for existing quality issues. I believe we (COT Team and us) will all benefit from better reference materials.

    Even having verbose error messages in debug environment will reduce the number of tickets and community forum threads.

    There are multiple recent community discussions for that many-to-many fields issue. I also experienced the same issue. If error message had more details, it would save me some time :)

    -------------

    I am also excited about the COT v9 Roadmap.

    But to get there faster you need better reference materials (including source samples) and higher product quality.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • I'd like to jump on the bandwagon for suggesting that some sample apps be made available on Github (or somewhere). It would be invaluable to be able to load up a project locally, see what it does, then get into COT and see all of the inner workings. Not only would it save lots of time in creating features in a project, but would likely give ideas for new features to add.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated