I would like to know if it was possible to perform dependency injection for native platforms accessibility features, as Automation Properties is not good enough.
By this, I mean that I would like to add hints/descriptions and other native accessibility features to my Xamarin. Forms view items such as entries or labels. If it isn't possible or this is a silly way of doing it, is there another way to apply native accessibility?
Pointing me in the right direction or a small example would be very helpful :D Thank you
Related
I have created a webapp using Wix, which relies heavily on the repeater element to display content from a database inside a repeating element. Repeaters do pretty much exactly what I want, but I realize they are built on a pretty sophisticated API, and there's a lot of stuff making this happen in the background.
Ultimately for this project, a native iOS app is the end goal. However, I have no experience in xcode - but willing to learn. Before I get in too deep, is there any kind of functionality I could find to achieve something like this?
Thanks in advance
You can't convert Wix Repeater element to Xcode. But, you can make deep customization to your Wix elements by using Wix Corvid.
If you not familiar with it, it's is a developing platform integrated into the Wix ecosystem that allows users to build advanced sites. Among other things, it’s able to create and manage databases, build dynamic pages, host user-generated content and more.
Assume you have to develop an app, which needs a completely customized user interface so that you can not use any standard UI objects in Xcode.
How would you proceed to create such an user interface? Would you use the interface builder? Would you create something like a master parent UIView? What are the best practices to achieve this?
What would be the most elegant solution with less code duplication?
If by "complete customization" you mean the look and feel of the app,
then I suggest to design the IB objects you require using some design IDE's such as photoshop and then use those slices for your project.
This is the best option I find so far to get a complete customized look with minimal code, and by minimal, I mean you don't actually require any coding. You can do this complete customization within your Interface builder.
However, I don't think you can completely ignore standard UI objects as you require them to add basic functionality.
If customized controls are what you are looking for, then I suggest you to create separate custom control classes so that they can be reused anywhere in your project, or in other projects too.
Here are two wonderful tutorials on custom controls:
http://www.raywenderlich.com/36288/how-to-make-a-custom-control
http://www.raywenderlich.com/56885/custom-control-for-ios-tutorial-a-reusable-knob
Hope this helps!
I have been learning to develop my own plugins and components for joomla! 2.5.
After a couple of months of developing features for my site, I am starting to realise that some of the components I have created could have probably been just as effective if I'd developed them as a plugin for com_content or com_user.
My question is what's the best way to decided if a full component is needed and when is it ok to use one or multiple plugins to give the same functionality.
My feeling at the moment is that plugins are a much nicer way to go due to them being self contained. Maybe I've answered my own question, and components are needed when interaction between elements is more complicated, where as plugins can be used for very modular functions.
Anyone else have a view?
Components and Plugins are completely different types of extensions.
Components are applications/systems that will appear in the content area such as VirtueMart and where the articles are shown. Consider them as software for you computer.
Plugins are there to manipulate Joomla and/or there extensions it's using. They contains functions that are associated with trigger events. So in a nutshell, they are there to extend the functionality of an existing extension.
So so answer your question, have a think about what you are creating and if will be an aplication or something to extend functionality.
Hope this helps
I'm wondering if there is some kind of best practice on how to make your application able to take third party developer's own plugins and how to get started on that. I'd love to have a view in my settings where the user can add or remove the plugins. To me this is completely new so I'm thankful for any hint.
Have a look at the Code Loading Programming Topics section on plug-in archietecture.
This section describes how to architect an application for extensibility through plug-ins. If you want to make your application modular, customizable, and easily extensible, you should read this section to learn about the different ways to build a plug-in architecture.
For a mid sized application that makes use of MEF catalogs is there really any advantage in my using Prism modules rather than just putting the different functionality into different class libraries. I just can't see why I would need to use Modules.
Anyone have any thoughts on this?
Thanks,
Richard
Modules are used when you want to perform initialization actions when the module is loaded. This can be for example the registration of views to regions using the Prism IRegionManager interface.
Whater PVitt Saying is correct plus i would like to add to it.
Modules are always a good option for the scalability.
you can easily do future enhancements by having Regions,each region having some view associated with it and each view in different module.
when i say each view in different module it means you should find out which view is having some other view related to it and make a clubed view of these two views and have single module for these views. after all its your call.
for e.g.consider your application has a menu.Toolbar for each menu item is same i.e. having same functionality then you can have ToolbarView+Menuview inside "MenuView".MenuModule will have this final MenuView.
So my opion is go with modular approach if you have any future enhancement or if your project is going to change time to time like new functionalities on user demand etc.
Modules are a wonderful way to allow multiple development teams to develop at the same time. Also assist your to organize and maintain the Single Responsibility principle of SOLID principles in a Project level.
It helps your to have separation of concerns.