I am going to develop a Google Gadget container site, that will be able to host OpenSocial compatible widgets (that I believe are Google gadgets, too, right?). Do you have any guidance where to start?
I know that the good start is the iGoogle Developer Home site and that framework what I would like exists - Shindig, but is little clumsy. Tutorial links do not work, for start. Do you think it would be wise to use Shindig? Maybe just for a start and then develop any customizations, if needed? Or would be wiser to start from scratch?
So where to start? Do you have any advices, tips or other useful resources to get on faster with this topic?
I guess I can start with Compliance - Gadget Server?
Shindig is the recommended way and the best way that a lot of people get started. I have seen a port of Shindig that runs on the app engine, but can no longer find the solution.
As for the tutorial links not working, they work fine for me. It must be noted that a lot of the link point to your localhost which mean you have to have the gadget server running.
Related
I've seen multiple questions, along the same lines as this, however they're usually quite outdated, and/or not answered well if at all.
I've been experimenting with Visual Studio LightSwitch, but it has many problems, and is also considered dead by much of the community now, just as Access is.
There isn't really much to say, so my question is, IS there a decent alternative? Or do I just have to make do with Access?
As you've already seen, there is no straight route. What to choose usually ends up in "that depends", and so it does - the only common factor is, that you are facing a total rewrite.
However, one way to cut it really short for a setup with few and known remote users, is to use Remote Desktop and Terminal Services of a Windows Server.
LightSwitch is not officially dead. I have done a few applications with it, and it is fun because it is so much different from Access with its firm screen design. Originally, it required Silverlight which now is dead, but today you use HTML5 at the client, so it won't get outdated right away.
From Access to Web the usual path is PHP.
The question is pretty clear I think, but I will elaborate on why I'm asking it.
I created a little blog engine based on OneNote. Basically, the blog configuration asks for an access to OneNote. Then the user chooses a section under which the blog posts are stored.
There is a cron script that will use all these informations to automatically get new pages, fetch the medias and cache every, and finally display the posts.
I chose OneNote because I own three Windows 8 computers and a Windows Phone, so OneNote was an easy choice, as I didn't want to get an other application to manage my blog.
There is still a lot to do (as always with softwares...), but I want to make this more or less an open source project, so that other people can install it on their websites and link it directely to OneNote.
The only "big" obstacle for this now is that authentication in the OneNote API needs to register the application on the Live Connect, and specify a redirect domain. So every user wishing to use this blog engine on their server will have to register their own application... That will look complicated just for a blog, especially if you're not tech-savvy.
Is there a way to "skip" or work around this requirement, even if it requires the user to make the section public (as it is for a blog, this doesn't seem too much to ask) ?
Thank you in advance,
Cheers
Sounds like an awesome project! When you get it released be sure to let us know at #OneNoteDev.
Unfortunately, at this time there's no way to circumvent the requirement for Live Connect OAuth configuration. You could offer a hosted variant so only you need to worry about the LiveID configuration.
I'm a relative beginner using Google Apps Script and JavaScript, but I've been playing around with bot for days now and I've created a few simple programs and I'd really like to try and get started on my dream project, even if it takes me forever. I'd like some advice on what I should use in terms of making the UI and what database I should use to hold the information (and if this app is even possible).
The App
I'd like to create an online novel management app that utilizes Google Drive as it's source for files. The UI would have a tree that showcases all the google drive files in the novel. When a scene is clicked, the scene opens up for editting.
Questions
Is this app a possibility?
If so, in terms of a UI, what do you think I should use? The google
provided UIbuilder? The HTML service - for example, can I have a
frame on the right that the google doc that needs to be editted
can open up in on the right?
Lastly, what database should I use? The database would have to store
chapter names and positions, as well as scene names, positions,
and the google doc ID that the scene corresponds to. I've got a
handle on ScriptDB and Spreadsheets... And if either of these two
aren't the best option, would some other database work better? And
why?
This app will, hopefully, be able to give an overview of a novel in tree form, allow you to open a particular scene and edit it, create new scenes, and also change the order in which the scenes are displayed. And then when the person finishes their novel, the app will compile all the scenes into one novel (also in google Drive).
Any insight or suggestions would be greatly appreciated!
Having a look at the questions you recently posted I think I have a pretty good idea of what you are trying to do and it looks like an exciting project... I can only encourage you to start it as soon as you can even if you're not comfortable with all the tools you will need to use, the best learning method is probably to work on something important to you.
Now your 3 questions : 1 - This is perfectly doable in the GAS environment and shouldn't be too hard to go through.
2 - the GUI builder is an easy way to start with UI but it lacks a number of features and tools that you will be needing (tree for example ) and is not so easy to expand if you ever need to. Depending on your knowledge in html, the choice is mainly between UiApp and html service... I would choose UiApp because I'm not good at all in html (but that's not relevant here ;-) but both are capable of building what you want, are easily expandable and not too hard to debug. The advantage could go to html service if you are going to look for 'nice looking features' because it opens the door to 3rd party tools... but again, this is a matter of personal choice.
3 - A recent post from Mogsdad showed that spreadsheet are faster than scriptDb for data storage and manipulation. I find it also easier since I can have a global view on data in the spreadsheet when debugging. Of course Spreadsheet must be considered as a container and data manipulated at array level to benefit from maximum performance. I use that in a lot of database application with full satisfaction.
Sorry for these "general considerations" that don't comply to sto standards ;-)
Yes, it seems that all of the things you are requesting are not too ridiculous. I recommend sticking to Google services because they are all easily integrated. To start off, you may want to use the UI builder/UI services. There may be a point in this project where you may want some functionality that the UiApp doesn't provide. At that point, you might want to switch over to HtmlService.
My answer is the same for the databases question. You might want to use a spreadsheet for your database so that you will be able to easily edit it by hand if you need to. You may not have the performance that another database would give you, but it will be fairly easy to test and mess around with your spreadsheet "database."
You could start out with getting the basics down. There's a serious amount of data out there. I would suggest you research on an "as-needed" basis. Design some work-/dataflow patterns for your app, for which you could try to use the Fluid UI extension for Chrome. Have a look at this from Mozilla on the designing of apps.
When you've gone through this you might want to have a look at Phonegap and the basics of web development and how you could combine the two.
There's also several ways of using/storing data. You could try WebSQL though it they no longer develop it. You could look at IndexedDB. You could try to use cookies.
Seriously, have a look around. You might also like the books of Wrox. They're very informative and have great work with reading demo's. Though the books are huge ;)
Does anyone know of any good tutorials that would show me how to create a sitemap similar to the image below. I can't figure out how to add the different sections underneath like the Your Account, FAQs, etc.
Any help would be extremely helpful. Thank you.
google search for instagram
What you want is what Google calls Sitelinks.
The process is automated and it's not possible right now to create them but you can manage them with the Google's web master tools. The algorithm used by Google to generate them is not public.
You can try this: http://www.xml-sitemaps.com/, or just google 'xml sitemap generator'
I remember that what happened (in my 'previous' life, when I had to take care of all the gory details of our company site) I just followed google's recommended seo suggestions. It was painstaking and slow, but over time when we started turning up at the top of sear results, that exactly how google presented us. It pulled relevant information on it's own and created that nice display. Looking at my old codebase I don't even see a sitemap file there. But I do remember using one of those online generators and then hand turning it a bit.
I'm developing pretty normal, non-brilliant Web 2.0 applications, like blogs, forums, social networks, etc.
APIs, mashups, greasemonkey-like works are okay for developers. But for end-users, my websites can't provide something more than a-gazillion-paper magazine. I want my users to create their own program logic to create information, access to data and communicate each other based on their own way.
The most advanced programmability on the websites are all about "Show 20 results per page", moving GUI elements around or changing colors of design.
Is there a study or do you have an idea to make websites allow their users to manipulate/create application logic, data structure, access methods both in client-side and server-side easily?
Thanks!
Please accept my apologizes for poor English, I'm not a native speaker.
Short answer, no. Long answer, not yet but this is probably a long term goal of web development overall. There are some "build your own web apps" web apps around but none of them go much beyond your simple description.
The most useful thing I have come across is something called pyjsglade:
http://sourceforge.net/projects/pyjsglade/
Which lets someone build a web gui in an IDE which then automagically turns into a webpage with full AJAX capabilities. It doesn't do everything you want but it's worth a look certainly.