I am developing an application in PHP which uses ExtJs 4 as its front end. I have selected a theme from the examples they are provided with the source download. I am trying to take out the theme from package, but It seems the examples are not stand alone. They are linked with other examples. Somebody help me to take it out.
Related
I am working with ASPNet Boilerplate. In the documentation I was going through the NavigationProvider. What I wanted to do was to define how the menus should appear without having to hard code them at client-end.
However as the documentation points out, I couldn't find how it's being used in the downloaded template (Asp.net core with AngularJS - version 3.6.0) since there are no references made to NavigationProvider in any of the classes.
The sample Task application seems to be for an older version of Abp.
I would highly appreciate if anyone can point me to a documentation/sample for this.
The question says it all really. If you are writing a WPF application, how are you integrating the application help? What is the state of play in mid-2013?
It seems that there is no clear answer to this from an afternoon with a search engine, but several options:
Write your own fancy tooltip based help (but where are you getting your data from?)
Use .CHM files and the Windows Forms help system (seems archaic to me).
Use Microsoft Help Viewer 1.X or Microsoft Help 2.0.
There is some confusion as to which is more recent / approved of by MS. It appear Help Viewer 1.X might be the recommended option over Microsoft Help 2.0. It doesn't help that the names are so similar...
What is the status of 2.0? Should we use it? Was it ever fully deployed?
Use a third-party product to author your help files and link to them somehow - DocToHelp/NetHelp, NetAdvantage on-line help, etc...
Furthermore, what XAML based mark-up / attributes are you using to provide the necessary context? What is the recommended method?
It seems surprising there is no clear path for supporting application based help in WPF.
My current preference is to use a third party help authorizing system to generate HTML based help.
We then use a WebBrowser to display this help as needed. The authoring system we use makes it fairly easy to extract out a single page from the main help (each "topic" is a single HTML file, and can be included with full contents or not as desired).
Granted, this definitely felt like a bit of a nasty hack at first - but once we wrote the basic plumbing (some attached properties for xaml to specify attributes for context location and add behavior to trigger help, etc), it's fairly clean.
One very nice advantage to this approach, however, is a single help system build works perfectly in all contexts - we can include the documentation online, expose it locally for use in a browser, and use it with context from within our application directly.
Just downloaded the sencha complete trial as I want to try my hand at mobile apps. I am trying to follow the guide located at http://miamicoder.com/2012/how-to-create-a-sencha-touch-2-app-part-1/ just go get an idea of how everything goes. Right off the bat I am having a problem.
The guide at 'Organizing A Sencha Touch Application In Directories And Files' shows the file structure. Well, I open Sencha Architect and choose to create a new Sencha Touch 2.1.x project. Project Inspector shows nothing similar to what the guide does. Is this guide for an older version or what? I am assuming this is my directory structure, but completely different than what is listed.
Help!
The file structure in that guide does appear to be correct, but of course, I would always trust the product from the creator of the framework over an external guide. Thing is, ST2 let's you put things lots of different places and customize those locations in app.js and app.json. I wouldn't worry about the folder structure if you're going through Architect so much as it will put things where they need to go and it'll include them in your app.js file correctly.
That all said, you may want to check the official Sencha documentation on Architect for any questions like this.
I am getting this error on page load itself.
Error: [Ext.extend] Attempting to extend from a class which has not been loaded on the page.
javascript//ext-4.1.1a/ext-all-debug.js
Line 4391
I'm not able to render the page at all. Any ideas?
I have also used extjs4 compatibility for migration.
Are you using all of the resources outlined here, including the screencasts? The videos take a little time commitment, but I think you'll find them quite helpful as they walk through several examples of how to debug exactly these types of issues. Learning to debug effectively will be the best way to tackle this type of migration.
There's no class named 'TreeNodeUI' in ExtJS. If you want treepanel, then you need to extend 'treepanel'. Please have a look at examples given on Sencha website before trying out any code.
First, my question might sound like a duplicate, but I have been going through a lot of questions on this forum and haven't found the answer to what I am looking for.
I have an existing web application built using Java, struts2 and jsps. I want the web site to be mobile - friendly. I am not looking at developing native apps right now. I want the mobile-site to have a native-app like appearance. So if a user goes to the browser on a mobile and accesses my site it should have that native look and feel. So I looked at Sencha touch 2 to begin with. I am new to Mobile development and would appreciate help in understanding how to go about evaluating Sencha touch 2 as a viable option. I see from examples that in ST the UI is mostly built using ExtJs javascript.
My questions are the following
Is there a way to port my existing jsps and html to the mobile view , without building them from scratch?
Since the css for the site is currently built for 'screen' media, this will obviously have to be worked out , but does Sencha Touch
provide any functionality of using an existing css and customising it
for a mobile device?
Appreciate your help,
Unfortunately, the answer to your first question is no.
Java/JSP and Javascript are totally different in essence. No convention could be made to convert between these two.
For the second one, SASS/SCSS might be the things you're looking for: http://sass-lang.com/. It's because Sencha Touch components' CSS properties are build through SCSS files. You can take advantage of these. For further ideas, see: http://www.sencha.com/blog/an-introduction-to-theming-sencha-touch