The v2.1 preview of Azure Form Recognizer Labeling tool which is recently published has a feature to compose models, When do we need to use is? Can anyone explain me some usecase for that?
Currently it's recommended to build one model for each form type in custom form. Model compose allows you to compose up to 100 models, hence one analyze call can process many type of forms - form type classification will be done automatically for you.
Related
I am very new to using SPFx and have a general question about using its Pub/Sub model via sp-dynamic-data with DynamicDataSourceManager.
I have been using React and react Contexts/Providers quite a bit in the past and was wondering:
What are the main differences between using the native SPFx dynamic data tools VS. React contexts/providers.
Any advantages or disadvantages to using either aside from preference.
Thank you in advance!
As far as I know, the pub/sub for SPFx assumes communication between different web parts (applications). For example, if you have a List View on the page, and want to react to events from it, you could subscribe to its events (for example, user selected an item). Means, it is intended for interaction between different web parts / applications (from different manufacturers, maybe) that live on the same page.
In React, you are usually working within the boundaries of your own application. But, in principle, the idea is similar to context/provider - one entity publishes an event and another subscribes to it.
I want to create a custom data type in Umbraco 7.3 without using AngularJS but I cannot do it because I don't have any knowledge about AngularJs.
I googled and saw that all of examples wrote by using AngularJs.
Is there any way to create a custom data type in Umbraco 7.3 without using Angular?
If not, please introduce some good sources to learning Angular that should be simple and practical.
No I don't believe it is possible since the interface is all in Angular but I could be wrong. Certainly the method that the team would prefer us to use is the Angular method. I have to be honest it was a little bit of a leap for me too creating my first editor but it's really not that difficult, trust me.
There is a good thread in the Umbraco form here: https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/46925-Custom-datatype-in-umbraco-701
And I would advise downloading the Umbraco source as the best examples are in the source itself.
If I remember correctly, you can generate custom property editors using just C# classes and class attributes. Or you can extend existing data types and tweak them. The only problem is you're limited to lists and displaying existing JSON feeds - most of which is best done using extensions like uComponents and NuPickers.
Have you viewed Nibble's blog? He's the primary source for most things data type related.
For your situation, the nuPickers dot net extensions sounds best. There's examples on this link.
I am trying to use angular schema form, http://schemaform.io/ While I find it great, I think it is too much like a platform solution and I am having to dig into the code to truly understand it in order to get it doing what I need with custom decorators. I am also finding the 'shema=' vs 'form=' to be very confusing.
I am now leaning towards the 'roll your own', Can anyone recommend using another package other than angular-schema-form or going the home grown route to maintain control? I have a hard time relying on 3rd party products when I don't fully understand them (or would code them differently) or if they will suite our needs.
So any options out there besides schema-form or any good starter packages for a home grown form generator using angularjs?
Angular Schema Form at its core is a template manager to reduce effort and manage re-use easily via config. You are more than capable to make your own Angular components and pass information to them via the UI Schema.
To elaborate on the differences JSON Schema is a standard for defining data models and the UI Schema (form) definition in ASF is specifically for the presentation layer, this also includes overrides of some data model properties.
There is no point in rolling a custom solution when knowing the internal workings of an open source offering provides you the ability to contribute and improve the library which is an even better result that everyone doing their own thing and re-inventing the wheel each time.
I posted a question on the Drupal forum about whether I should build my database in Drupal using content-types or the database abstraction layer and schema module: [here][1]
Any advice would be greatly appreciated.
[1]: https://drupal.stackexchange.com/questions/98020/should-i-use-content-types-or-database-abstraction-layer
I'd recommend using content types.
For a PHP coder, sometimes using the Drupal User Interface to build things feels non-intuitive, but in the long run you're going to benefit a lot from doing things "the drupal way.
Once you reverse engineer your need into a content type and all it's associated fields, install the modules that provide those field types and set things up, you'll start to see the benefits.
Validation on all the data-entry froms will already be done for you.
Multiple display modes are available for your data (email addresses can be shown with or without mailto: links, images can be shown using any of Drupal's image styles)
Integration with other Drupal modules already exists, and will be supported (almost anything built with fields is available to views)
By writing your own schema you'll need to handle all these things yourself (and more), and not just once, but you'll need to maintain all that custom code over time.
Learn to leverage the community and all the great work that's been done already, you'll save yourself time in the long run :)
What i see you are going to have shop site.
You may tray this:
https://drupal.org/project/commerce_kickstart
, i've found it usefull once. It's drupal distribution with nice themed shop rady to use straight forward.
And of course do it with content type + views + entity reference modules.
Here is a link to a comment that answers the question I asked. It backs up what arpitr outlined in their answer on the orignal post on the drupal forum, whose answer is also in agreement with jenlampton's suggestion above.
https://drupal.org/comment/7848011#comment-7848011
I will implement my system using node entities until the need arises to build a custom entity (if it ever does).
The top answer in this forum give a good way to evaluate whether to use nodes or custom build an entity:
https://drupal.stackexchange.com/questions/22586/when-is-it-appropriate-to-create-an-entity-versus-just-adding-a-new-content-type
i have played around with dynamic data website. is there something similar for winforms.
if there isn't anything out there for doing the same with winforms than the question would be why not? we have a massive ERP application that we want to migrate from AS400 to .Net
Winform application. my initial thoughts were to have all the maintenances be as simple as Dynamic Data Website project.
I would think that WPF would be a better starting point then WinForms, as it has support for style to say how item of data are displayed.
Dynamic Data makes it easy to edit your DB on the web. For desktop (and web) apps take a look at the new Microsoft LightSwitch:
http://msdn.microsoft.com/en-us/lightswitch/gg441300
LightSwitch doesn't use Windows Forms. Rather it creates a Silverlight App that can run both on the desktop and the web. Pretty cool.
Dynamic data is using the routing functionality of the MVC framework. In Windows forms we don't have this approach of fetching data with URLs from a server.
I am not sure how this model could fit into Windows forms.
I think it's pretty hard to create something like dynamic data for Windows Forms.
My biggest concern is here, once you created that Framework, how do you configure it? I mean if you want to change 1 form to be a bit different than the others :-)
I think its better to generate Forms for the various tables in the Database context, using a powerful Grid control from one of the big vendors. And then you can configure those.
Remember this is a different approach then the dynamic data one, where no code is generated before compile time
I think the reason you don't see something like this in winform applications is because it's much easier to store a HTML page inside a database and then display it on the screen formatted properly when using a web application because your browser knows how to format the HTML.
You would have to, stored in the database, know where each label and field would go on the form in some sort of co-ordinates fashion (or you could use a layout 3rd party control) but the amount of work that would take might be tedious to do properly.
The dynamic data website I worked on did not take input from the user. It only displayed different web pages to the user and allowed the admin person to easily make changes to the content. If you wanted a user to beable to save data then that would even be more complex because you have to worry about validation, required fields, etc.
If you have lots of users that need to see different information based on their access level then I would just suggest having a table in the database that tells the system whether or not they should see the field on the form. Then use a 3rd party layout panel to format the visible fields.
my 2 cents
As much as Dynamic Data looks simple and cheap enough to access a database it wouldn't work for an ERP system anyways. Business systems are more than moving data between database and the user interface, they require business rule actions when saving data and while retrieving the may require some massaging to ensure meaningful presentation of storage optimized data.
If you still like to pursue this option it would be very easy to create an application that is build on top of Entity Framework.
I'm not aware of a Dynamic-Data-alike, but (having written one before, years ago, for ASP) I don't actually think it would be that hard, particularly with WPF and its templating support.
Actually if you were really clever you could probably 'borrow' the backend from Dynamic Data, and just reimplement the UI as WPF.
Would make a fun little project actually.
Alternative answer: Use Microsoft Access. No really.
Alternative answer #2: So why not just use Dynamic Data then?