I want to make a Qt Quick Controls 2-based installer. Doing so from scratch will take several hours from my time, so I want to use the Qt Installer Framework. It's possible?
So far I have customized wizard pages using style sheets, and even replace some pages with custom ones, but they are QWidget-based pages, and I need Qt Quick Controls 2-based pages.
Related
I have a website developed in old technologies like ASP, ActiveX, COM and some other legacy technologies. I want to re write the application in ASP.Net MVC, I'm not sure how to remove those ActiveX and COM and which is the alternate option to use for those components. Another pain point is i do not have the source code of ActiveX and COM dlls, So we want to re-write the application as earliest possible, can anyone suggest the possible option that how i can start migration.
Is it possible that i can replace the ActiveX components one by one ant test the functionality and re-write another Activex component?
Also can somebody share the materials/links to best understand ACtivex and COM ?
I have literally had to do exactly the same thing.
I want to answer your question properly:
Is it possible that i can replace the ActiveX components one by one ant test the functionality and re-write another Activex component?
You could but that sounds unnecessary.
Also can somebody share the materials/links to best understand ACtivex and COM ?
Create a blank ASP project
Set the target framework to be whatever (.net 2.0?)
Copy and paste all your files into this project, so that the web.config is in the root.
Now, to get your COM and Activex elements, right click the "References" folder and add reference. Goto "Extensions" and you should see COM modules there. You need at least the Microsoft ActiveX etc etc scripts. I imagine you have some lines like CreateObject('ADODB.CONNECTION'). You can search using the object explorer as to which COM modules contain which objects.
Tick them to include them, then build.
It might take a bit of fiddling, and there were some objects I couldn't find, and also some I had to download an install manually (but then after that they appeared in the extensions menu, so it was straightforward).
I managed to get an ASP2 project working in Visual Studio 2015 this way.
Does anyone know a good, complete, simple asp.net project that implements Twitter bootstrap.
I want to create a website that uses ASP.net and is responsive and uses bootstrap. That involves probably a lot of libraries and links to jquery, etcetera. The first time it is a lot of investigation and somebody must have done this before and might be willing to give me a head start.
Thanks in advance!
ASP.Net Web Forms Template and MVC Template come with Twitter Bootstrap already.
Once you select Web Forms Template or MVC Template (Screen Shot 2), it'll download all required styles, scripts and fonts via NuGet
I'm working on an straight ASP.Net application. (no additional frameworks).
I've got several user controls (not custom controls) which I'd like to be able to package into a DLL for reuse/redistribution across several other applications. Ideally, we'd like to have everything self contained in (.ascx and source files) a DLL which could be added to the target project's references.
When embedding the user controls into .aspx pages, we'd like to be able see those controls in Visual Studio design view.
I've been looking around and seen several possible solutions for this.
Can anyone point me to a clear tutorial/example which will help step me through this process?
John, as far as I am aware, what you are asking is not possible, at least not out of the box with the .net Framework. When you build a UserControl in ASP .NET app and compile the solution, as you may have realized, the UserControl would be included in the dll of the project to which it belongs; it won't have a separate dll of its own. Since the UserControl won't have a dll of its own, you won't be able to make it available in the design view/toolbox.
For what you are asking, you might want to consider creating ServerControls instead. Server controls are harder to create than UserControl, if I recall correctly, you have to code it entirely, wont have designer available, but when you are done and compile, ServerControl will have it's own dll, which could be made available in CustomControls under Toolbox.
If you want a starting point for ServerControl, I would highly recommend watching the video from KudVenkat. His explanation and demos are second to none.
Link to the tutorial
I'm working on a pretty big application for Flex/Air. We are using GraniteDS and Tide to interact with the model from our Java EE server.
I've been reading about modularization and Modules in Flex. The application has already been built, and I'm figuring a way out to re-design some classes and parts. From what I've read so far, I understand a Module is a different swf which can be dynamically load. Most of the tutorials/documentation are oriented to Flash "programmers" who are using Flex or Air instead of real developers, so that makes online resources harder to get.
What I can't understand - yet - is how to encapsulate ActionScript classes or MXML views under this module.
I've separated some of the code into libraries. For example, the generated code from Granite is in a "server" library. But I would like to separate parts of the logic with its Moderators, Controllers and Views. Are modules the way to go? Is there a "modules for dummies" or "head first Flex Modules for programmers" like tutorial in order to get a better perspective in order to build my architecture? When to choose libraries and when to choose modules?
I'm using Flex 3.5, and a migration to Flex 4 is way far into the future, so no Flex 4 answers please, thanks!
Modules are the answer for encapsulating UI into different sections that do not depend on each other. Think of them like applications inside of applications.
If you want to encapsulate "code", meaning non-ui actionscript, then you really just want classes and packages of classes. You could also package that code into a swc, which is just a compiled version of that code that you can include in multiple projects (I think this is what you meant by libraries).
You wouldn't want to create a module just to contain non-ui code. You wouldn't want to use modules for separating out the model/view/controller in your application.
If you have part of your application, that for the most part runs completely on its own, with no real dependencies on the rest of the application except for maybe a little bit of information passed in, then it makes sense for modules.
Where we use modules mostly is for an application that has different sections to it where you are only working in one section at a time. There is no need for the other sections to be taking up resources, so we have the different sections in modules and load/unload them as necessary.
Does that help?
Edit in reply to the comment below:
By libraries I meant Flex Library
Projects, where you encapsulate
classses and use the swc. Can you have
these libraries inside a Flex Project?
(I use a separate Library Project for
each new library).
Yes, you can use these swc's (Libraries of code) inside of your flex projects. Just drop the swc in the lib directory in your flex/flash builder project and the code is automatically added to your classpath. Just make sure that everything that the code inside a single swc needs is inside that swc. Don't make a swc rely on another swc to function.
I was curious how in the typical ASP.NET MVC mentality one could build a platform that others could develop plugins for. I mean, how would those plugins look like?
Like exiting user controls for WebForms, encapsulating all layers in themselves, or three different files representing the model the view and the controller. I should develop the core of a CMS, that I'd like others to build plugins for later on. Which mentality is better for that, classic Web Forms or ASP.NET MVC?
I need developers to be able to separately build components for that. Is it possible to encapsulate the MVC directory structure in a component DLL file and then when I reference the DLL file, to be able to directly access the component's model, view, or controller as part of the general MVC structure?
The most promising component techniques have come from the guys over at lostechies.com and Mvccontrib in the form of Portable Areas. Portable Areas allows an entire MVC app to be appended onto an existing application. So its not just a UI component but also provides all the work flow and screen integration as well.
Open Forum does something like this as well. I don't know how, but it is very plug and play.
For straight up plugin architecture there is an interesting screencast and source code for Rob Connery's link text. He takes advantage of the App-Code directory to slide new plugins into place without having to edit the main site.