I would like to create my own metamodel by extending a third party EMF meta model. Currently I am using a third party ecore-model and would like to add an extra attribute to a specific EClass. I cannot change the existing metamodel due to the opensource license agreement. I have searched internet for the solutions, but failed to find any. Any help will be appreciated.
You can take a look to the EMF-Facet project:
https://www.eclipse.org/facet/
...EMF Facet proposes a solution to extend existing Ecore metamodels without having to modify them. The idea is to provide non-intrusive mechanisms to add new features (types, attributes, operations and references) to a metamodel...
I'm not sure that exactly what you are searching for, but perhaps it can give your ideas or pointers to others technologies.
Related
This question is about Options, a feature in Adobe's proprietary language HTL:
https://helpx.adobe.com/experience-manager/htl/using/expression-language.html
Expression Option Sightly
My simple question: Can I extend HTL by implementing my own custom Options? If so, how?
Yes, you can implement your own custom options for an HTL expression. You will need to implement a Filter and add it to the compiler.
But you shouldn't, as:
This is not a designed extension point. You will need to fork the implementation and modify it, thus becoming responsible for keeping it up-to-date further down the road.
You can most probably get the same results by using the public APIs (such as https://github.com/Adobe-Marketing-Cloud/htl-spec/blob/master/SPECIFICATION.md#221-use).
In case you think there's a very good reason for adding or modifying expression options, you can propose an HTL specification change (and also contribute the implementation in Sling).
No. To implement custom options you will have to extend the respective plugin that supports that expression. those classes are not exported by sightly scripting compiler bundle and are not available to be customized.
I want to build an web application(ASP.NET MVC 6) that can add modules/plugins without having to rewrite my source code.
Already read about MEF and Areas but are not helping much.
Someone who has overcome this problem that can help me?
Depends on which part of the web application you are targeting.
1.If it's in the request pipeline you would make a Middleware package.
2.It's it's in HTML you would make a TAG Helper package.
3.If it's an intrinsic functionality you would extend appropriate classes and throw them into a package. An example of this would be helpful extension methods or methods to add claims given a claims principal.
4.If you want to go even further you could create your own Visual Studio templates that you can use to pre-fill your options upon creation.
EDIT
contacted the author of play-js-validation. Bleeding edge stuff; Play has to be compiled against scala virtualized on to-be-released 2.10, and nested case classes are not yet supported. Really impressive project, I hope it comes to fruition as the prototype does almost exactly what I was hoping for...
Found this:
https://github.com/namin/play-js-validation
Anyone know if there are plans for built-in client-side validation in Play 2.0?
I am currently generating controller, model (with form validation), and dao scala files based on an existing DB schema; would love to include client-side validation as part of that process!
Thanks for clues, insider knowledge, etc.
p.s. Play user group is, to say the least, busy; most posts seem to be completely ignored (of course, many Stackoverflow Play-related questions go unanswered as well, so this thread may be DOA...)
There's no such plans I'm afraid, at least didn't hear about (note: I'm not a dev team member, just Player)
Check tickets on Play's Lighthouse
On the other hand I doubt if this fits Play's assumptions at all. Client-side validation is done with some external JS solution which should not be determined by framework, nobody said that it should use ie. jQuery by default.
Finally, the only thing to use client-side validation is just to include the JS libs and add proper attributes to your form fields, ie it will create tag that you can validate with jQuery Validation plugin:
#inputText(entrantForm("identitynumber"),
'_label->"Identity number",
'class -> "required",
'minlength -> "11",
'maxlength -> "11")
I see work is still going on with new features on MEF (MEF Codeplex site) and they are shipping MEF 2 beta releases, however they do not have any decent documentation on what the new features are experimenting/exploring/building?
So, what are the new features (in a little bit of detail please, a sentance or two for each would be great) that are part of MEF 2?
I know one big feature is support for open generics. This allows us to import parts that look like this:
IRepository<T>
{
}
using an import that looks like this
[Import(typeof(IRepository<>))]
private IRepository<Users> userRepository;
From the preview documentation
Support for generic types.
Convention-based programming model that enables you to create parts based on naming conventions rather than attributes.
Multiple scopes.
I am using the Zend Framework and I cannot locate in the documentation the values I can specify in the application.ini file. Does anyone have a link to where I could see them?
Thanks,
Darren
There is no exhaustive list, since you can specify arbitrary configuration values that are specific to your app.
The "built-in" stuff is mostly about configuting build-in resource plugins, so a good source of information on those might help you. The manual describes them in fair detail.