This document discusses Sparkle, an open-source software update framework for macOS. It provides an overview of appcasting via RSS feeds, how to set up Sparkle in an app to check for and download updates, and best practices for building appcast feeds including recommended metadata fields. Key points covered include how to specify the appcast URL, update check frequency, and whether to show release notes. The document also describes how Sparkle parses version strings and compares versions to determine update availability.
This document summarizes an OpenShift State of the Union presentation given at Devoxx 2012. It provides a brief history of OpenShift including its acquisition by Red Hat in 2010 and open sourcing in 2012. It then demonstrates how to get started with OpenShift including signing up, installing client tools, creating a domain and applications, deploying applications using Git, and available web cartridges. Tips and demos of deploying sample applications are also provided.
This document discusses SIMBL, a technology for customizing Cocoa applications on Mac OS X. It provides 18 links to articles about SIMBL and how it can be used to add custom menu items, override methods, and otherwise modify Cocoa applications' behavior through the use of plugins. The document also includes example code for using SIMBL to add a "Show in Browser" menu item to a document-based application and override an application method while still calling the original.
This document summarizes an OpenShift State of the Union presentation given at Devoxx 2012. It provides a brief history of OpenShift including its acquisition by Red Hat in 2010 and open sourcing in 2012. It then demonstrates how to get started with OpenShift including signing up, installing client tools, creating a domain and applications, deploying applications using Git, and available web cartridges. Tips and demos of deploying sample applications are also provided.
This document discusses SIMBL, a technology for customizing Cocoa applications on Mac OS X. It provides 18 links to articles about SIMBL and how it can be used to add custom menu items, override methods, and otherwise modify Cocoa applications' behavior through the use of plugins. The document also includes example code for using SIMBL to add a "Show in Browser" menu item to a document-based application and override an application method while still calling the original.
This document contains a list of 84 application names across multiple categories including media players, backup software, file management tools, and system utilities.
This document discusses considerations for evaluating educational apps for iPads. It provides tables that categorize apps according to curriculum areas, Gardner's multiple intelligences, 21st century skills and literacies, and limitations. The tables help educators select apps that align with curricular goals and support different learning styles. When choosing apps, educators should consider how well they integrate with the curriculum, support various intelligences and literacies, and can be easily managed and monitored for inappropriate content.
This document lists over 200 software programs across various categories like data recovery, antivirus, office suites, graphics and design, media players, remote access, web browsers and more. It includes both commercial and free/open source software options and provides direct links to download pages for some.
Development: What they don't teach you in collegeBinny V A
The document discusses important skills that are not taught in college for programming including version control systems, Linux, testing, deployment scripts, editors, debuggers, and shells. It emphasizes using Git and Subversion for version control and recommends learning Linux, testing, and automation tools. Common programming languages, frameworks, principles, and online resources are also listed.
Drupal is widely adopted by leading technology companies for powering their websites and integrating into their applications. It is popular among companies in fields like aerospace, consumer software, developer communities, e-commerce, games and gaming, robotics, and security. Major tech brands that use Drupal include AOL, AT&T, Dell, Ericsson, Eucalyptus, Garmin, Intel, LinkedIn, Novell, Nvidia, PayPal, Symantec, Twitter, and Yahoo.
Development: What They Don't Teach You in CollegeBinny V A
The document discusses important skills that are not taught in college for development including version control systems, environments like Linux, testing, deployment scripts, editors, debuggers, shells and more. It emphasizes source control using tools like Git and Subversion. Frameworks like Rails, Django and tools like jQuery are also mentioned.
Red Hat Nordics 2020 - Apache Camel 3 the next generation of enterprise integ...Claus Ibsen
In this session, we'll focus on:
Camel 3: Demos of how Camel 3, Camel K and Camel Quarkus all work together, and will provide insights into Camel’s role in the next major release of Red Hat Integration products.
Camel K: This serverless integration platform provides low-code/no-code capabilities, where integrations can be snapped together quickly using the powers from integration patterns and Camel’s extensive set of connectors.
Camel Quarkus: Using Knative (the fast runtime of Quarkus) and Camel K brings awesome serverless features, such as auto-scaling, scaling to zero, and event-based communication, with great integration capabilities from Apache Camel.
You will also hear about the latest Camel sub-project Camel Kafka Connectors which makes it possible to use all the Camel components as Kafka Connect connectors.
Finally we bring details of the roadmap for what is coming up in the Camel projects.
SouJava May 2020: Apache Camel 3 - the next generation of enterprise integrationClaus Ibsen
In this session, we'll discuss:
- What’s Apache Camel: An overview of Camel and what you use it for and why you should care.
- Camel 3: Demos of how Camel 3, Camel K and Camel Quarkus all work together, and will provide insights into Camel’s role in the next major release of Red Hat Integration products.
- Camel K: This serverless integration platform provides low-code/no-code capabilities, where integrations can be snapped together quickly using the powers from integration patterns and Camel’s extensive set of connectors.
- Camel Quarkus: Using Knative (the fast runtime of Quarkus) and Camel K brings awesome serverless features, such as auto-scaling, scaling to zero, and event-based communication, with great integration capabilities from Apache Camel.
You will also hear about the latest Camel sub-project Camel Kafka Connectors which makes it possible to use all the Camel components as Kafka Connect connectors.
Finally we bring details of the roadmap for what is coming up in the Camel projects.
And after the presentation we have about 30 minutes of QA answering all the questions from the audience.
Embracing concurrency for fun utility and simpler codekamaelian
The document discusses embracing concurrency for simpler code. It notes that hardware is becoming more concurrent, but most programming languages and tools treat concurrency as difficult. The Kamaelia project aims to make concurrency easy and usable for novice and advanced developers alike through fundamental control structures and messaging between components. Examples shown include using pipelines, graphlines, servers, and backplanes to build concurrent applications in a simple way.
The Evolution of Internet-Scale Event Notification ServicesHiroshi Ono
The document discusses the evolution of internet-scale event notification services from past to present to future. In the past, event-based integration occupied niche applications and adapted to loosely-coupled systems. Presently, crossing trust domains raises new internet concerns. Looking to the future, there is an explosion of diverse and competing protocol proposals that will likely converge based on selection criteria. The document aims to provide context on existing systems, identify design choices, discuss new research issues, and inform principled design selections.
This document discusses using mobile JavaScript frameworks like PhoneGap, Cordova, XUI and Lawnchair to build native mobile apps with HTML, CSS and JavaScript. It highlights the PhoneGap and Cordova APIs for accessing device sensors, data and outputs. It also briefly mentions JavaScript libraries like Zepto, Sencha and jQuery Mobile that can be used for DOM manipulation on mobile.
The document promotes an online integrated development environment (IDE) called Cloud9 that allows developers to code from any device without limitations. It can be run from anywhere, supports cursor and tab syncing between devices, and debugging state syncing. The IDE servers are scalable and behind a load balancer for high availability. Developers can use their own virtual machines and it integrates with services like GitHub.
@kaosbeat explaining how we made a 2nd screen app from idea to implementation and then took it further by making tools to be used in the TV studio on top of that, using the same technology. Node.js, redis, EC2, RoR, ...
Developer tools have come a long way but still have room for improvement. There are now many browsers and platforms to develop for, each with their own set of tools. While this provides more options, it can also be overwhelming and make developers less satisfied. Current tools focus on debugging JavaScript, inspecting HTML and CSS, profiling network activity and more. Many are open source and have thriving communities contributing extensions and improvements. The future remains focused on continued enhancements to core tools, cross-browser debugging, and better tools for new platforms and technologies.
The document discusses embracing concurrency for simpler code. It notes that hardware is becoming massively concurrent, providing an opportunity. While concurrency is viewed as hard, the fundamental problem may be lack of proper tools. Imperative languages often overlook concurrency as a core concept. A variety of desktop and media applications could benefit from a concurrent approach. The document advocates using concurrent components that communicate via messages while keeping data private. It also discusses software transactional memory and different perspectives in APIs for concurrent systems. Finally, it presents examples of using pipelines and graphlines as part of a concurrency domain specific language.
This document contains a list of 84 application names across multiple categories including media players, backup software, file management tools, and system utilities.
This document discusses considerations for evaluating educational apps for iPads. It provides tables that categorize apps according to curriculum areas, Gardner's multiple intelligences, 21st century skills and literacies, and limitations. The tables help educators select apps that align with curricular goals and support different learning styles. When choosing apps, educators should consider how well they integrate with the curriculum, support various intelligences and literacies, and can be easily managed and monitored for inappropriate content.
This document lists over 200 software programs across various categories like data recovery, antivirus, office suites, graphics and design, media players, remote access, web browsers and more. It includes both commercial and free/open source software options and provides direct links to download pages for some.
Development: What they don't teach you in collegeBinny V A
The document discusses important skills that are not taught in college for programming including version control systems, Linux, testing, deployment scripts, editors, debuggers, and shells. It emphasizes using Git and Subversion for version control and recommends learning Linux, testing, and automation tools. Common programming languages, frameworks, principles, and online resources are also listed.
Drupal is widely adopted by leading technology companies for powering their websites and integrating into their applications. It is popular among companies in fields like aerospace, consumer software, developer communities, e-commerce, games and gaming, robotics, and security. Major tech brands that use Drupal include AOL, AT&T, Dell, Ericsson, Eucalyptus, Garmin, Intel, LinkedIn, Novell, Nvidia, PayPal, Symantec, Twitter, and Yahoo.
Development: What They Don't Teach You in CollegeBinny V A
The document discusses important skills that are not taught in college for development including version control systems, environments like Linux, testing, deployment scripts, editors, debuggers, shells and more. It emphasizes source control using tools like Git and Subversion. Frameworks like Rails, Django and tools like jQuery are also mentioned.
Red Hat Nordics 2020 - Apache Camel 3 the next generation of enterprise integ...Claus Ibsen
In this session, we'll focus on:
Camel 3: Demos of how Camel 3, Camel K and Camel Quarkus all work together, and will provide insights into Camel’s role in the next major release of Red Hat Integration products.
Camel K: This serverless integration platform provides low-code/no-code capabilities, where integrations can be snapped together quickly using the powers from integration patterns and Camel’s extensive set of connectors.
Camel Quarkus: Using Knative (the fast runtime of Quarkus) and Camel K brings awesome serverless features, such as auto-scaling, scaling to zero, and event-based communication, with great integration capabilities from Apache Camel.
You will also hear about the latest Camel sub-project Camel Kafka Connectors which makes it possible to use all the Camel components as Kafka Connect connectors.
Finally we bring details of the roadmap for what is coming up in the Camel projects.
SouJava May 2020: Apache Camel 3 - the next generation of enterprise integrationClaus Ibsen
In this session, we'll discuss:
- What’s Apache Camel: An overview of Camel and what you use it for and why you should care.
- Camel 3: Demos of how Camel 3, Camel K and Camel Quarkus all work together, and will provide insights into Camel’s role in the next major release of Red Hat Integration products.
- Camel K: This serverless integration platform provides low-code/no-code capabilities, where integrations can be snapped together quickly using the powers from integration patterns and Camel’s extensive set of connectors.
- Camel Quarkus: Using Knative (the fast runtime of Quarkus) and Camel K brings awesome serverless features, such as auto-scaling, scaling to zero, and event-based communication, with great integration capabilities from Apache Camel.
You will also hear about the latest Camel sub-project Camel Kafka Connectors which makes it possible to use all the Camel components as Kafka Connect connectors.
Finally we bring details of the roadmap for what is coming up in the Camel projects.
And after the presentation we have about 30 minutes of QA answering all the questions from the audience.
Embracing concurrency for fun utility and simpler codekamaelian
The document discusses embracing concurrency for simpler code. It notes that hardware is becoming more concurrent, but most programming languages and tools treat concurrency as difficult. The Kamaelia project aims to make concurrency easy and usable for novice and advanced developers alike through fundamental control structures and messaging between components. Examples shown include using pipelines, graphlines, servers, and backplanes to build concurrent applications in a simple way.
The Evolution of Internet-Scale Event Notification ServicesHiroshi Ono
The document discusses the evolution of internet-scale event notification services from past to present to future. In the past, event-based integration occupied niche applications and adapted to loosely-coupled systems. Presently, crossing trust domains raises new internet concerns. Looking to the future, there is an explosion of diverse and competing protocol proposals that will likely converge based on selection criteria. The document aims to provide context on existing systems, identify design choices, discuss new research issues, and inform principled design selections.
This document discusses using mobile JavaScript frameworks like PhoneGap, Cordova, XUI and Lawnchair to build native mobile apps with HTML, CSS and JavaScript. It highlights the PhoneGap and Cordova APIs for accessing device sensors, data and outputs. It also briefly mentions JavaScript libraries like Zepto, Sencha and jQuery Mobile that can be used for DOM manipulation on mobile.
The document promotes an online integrated development environment (IDE) called Cloud9 that allows developers to code from any device without limitations. It can be run from anywhere, supports cursor and tab syncing between devices, and debugging state syncing. The IDE servers are scalable and behind a load balancer for high availability. Developers can use their own virtual machines and it integrates with services like GitHub.
@kaosbeat explaining how we made a 2nd screen app from idea to implementation and then took it further by making tools to be used in the TV studio on top of that, using the same technology. Node.js, redis, EC2, RoR, ...
Developer tools have come a long way but still have room for improvement. There are now many browsers and platforms to develop for, each with their own set of tools. While this provides more options, it can also be overwhelming and make developers less satisfied. Current tools focus on debugging JavaScript, inspecting HTML and CSS, profiling network activity and more. Many are open source and have thriving communities contributing extensions and improvements. The future remains focused on continued enhancements to core tools, cross-browser debugging, and better tools for new platforms and technologies.
The document discusses embracing concurrency for simpler code. It notes that hardware is becoming massively concurrent, providing an opportunity. While concurrency is viewed as hard, the fundamental problem may be lack of proper tools. Imperative languages often overlook concurrency as a core concept. A variety of desktop and media applications could benefit from a concurrent approach. The document advocates using concurrent components that communicate via messages while keeping data private. It also discusses software transactional memory and different perspectives in APIs for concurrent systems. Finally, it presents examples of using pipelines and graphlines as part of a concurrency domain specific language.
This document discusses new business models and opportunities for operators through software-defined platforms (SDP) and over-the-top (OTT) services. It notes that APIs allow for different levels of integration between services, from light integration with no data sharing to deep integration where services are fully interoperable. It also discusses strategies for distributing APIs, including targeting long-tail or short-tail developers, and using SDKs, customized APIs, or retail APIs to expose APIs. The document examines strategic choices around intrinsic motivation, distribution methods, and standardization to realize opportunities from SDP and OTT services.
The document introduces SD, a peer-to-peer bug tracking tool developed by Best Practical to allow tracking bugs offline and syncing work across devices. SD uses a decentralized model where each installation can pull changes from any other replica. It supports syncing with other bug trackers like RT, Trac and Google Code. The author argues that cloud services make users dependent while SD empowers fully offline and distributed work by syncing like users naturally share files.
1) Most social media initiatives undertaken by corporations are unsuccessful because corporate organizations do not understand how to properly utilize social media.
2) Only 19% of brands take advantage of the success generated by 82% of social media activities.
3) Startups are generally more successful than corporations with social media because corporations do not have a clear understanding of how to engage with social media.
The document discusses modern JavaScript and HTML5 and breaks stereotypes about JavaScript development. It covers topics like JavaScript before HTML5, how JavaScript is used with HTML5, revenue opportunities for JavaScript applications, and provides examples of non-traditional uses of JavaScript beyond web browsers, such as for games, devices and appliances. It concludes with a demo of JavaScript games and LED control to illustrate its potential as a platform and for future web applications.
The document appears to be notes from Aaron Straup Cope discussing various topics related to web development, APIs, communities, and content management. It touches on tools, techniques and challenges like JavaScript, PHP, caching, data storage, image processing, deploying applications, and managing fear and uncertainty. Various URLs are included for photos, projects and talks related to topics in the notes.