DOCSLIB.ORG

EPICS How-Tos

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
EPICS How-Tos EPICS How-Tos Sep 10, 2021 Contents 1 Installation on Linux/UNIX/DARWIN (Mac)1 1.1 What is EPICS about?..........................................1 1.2 Prepare your system...........................................1 1.3 Install EPICS...............................................1 1.4 Test EPICS................................................2 1.5 Create a demo/test ioc to test ca and pva.................................3 1.6 Add the asyn package..........................................4 1.7 Install StreamDevice (by Dirk Zimoch, PSI)..............................5 2 Packages required for EPICS on Centos 87 2.1 Overview.................................................7 2.2 Packages required to build EPICS base.................................8 2.3 Packages required by the sequencer...................................8 2.4 Packages required by epics-modules/asyn................................8 2.5 Packages required by the Canberra and Amptek support in epics-modules/mca............8 2.6 Packages required by the Linux drivers in epics-modules/measComp.................8 2.7 Packages required by areaDetector/ADSupport/GraphicsMagick....................8 2.8 Packages required by areaDetector/ADEiger..............................9 2.9 Packages required to build aravis 7.0.2 for areaDetector/ADAravis...................9 2.10 Packages required to build areaDetector/ADVimba...........................9 2.11 Packages required to build EDM.....................................9 2.12 Packages required to build MEDM...................................9 3 Creation of an Input/Output Controller (IOC) 11 4 Installation on Windows 15 4.1 Introduction............................................... 15 4.2 Required Tools.............................................. 16 4.3 Choice 1: Compiler........................................... 16 4.4 Choice 2: Build Environment and Tool Installation........................... 16 4.5 Choice 3: Static or DLL Build / Deployment.............................. 17 4.6 Windows Path Names.......................................... 17 4.7 Put Tools in the PATH.......................................... 18 4.8 Install and Build............................................. 18 5 How To Port EPICS to a new OS/Architecture 31 i 6 Common Database patterns 33 6.1 Pull Alarm Status w/o Data....................................... 33 6.2 Combined Setting and Readback..................................... 33 7 How to run an EPICS Collaboration Meeting 35 7.1 Organization............................................... 35 7.2 Communications............................................. 36 7.3 Facilities................................................. 36 7.4 Agenda.................................................. 36 8 How to Avoid Copying Arrays with waveformRecord 37 8.1 Example................................................. 37 9 How to find which IOC provides a PV 43 9.1 Find Host and TCP port......................................... 43 9.2 Find which process is using a TCP port (Linux only).......................... 44 9.3 Find information about a process (Linux only)............................. 44 9.4 Additional: Finding the procServ/screen running an IOC (Linux only)................. 44 ii CHAPTER 1 Installation on Linux/UNIX/DARWIN (Mac) 1.1 What is EPICS about? We assume that you know more or less what EPICS is. Here we want to start from scratch and get to the point where we have a working server, offering some PVs for reading (caget or pvget) and writing (caput or pvput), and we read and write on them from another terminal, either on the same machine or on another one in the same network. If you are going to use two different machines, you will have to repeat the steps for installing EPICS for both of them. 1.2 Prepare your system You need make, c++ and libreadline to compile from source. On macOS these dependencies can be installed by using e.g. homebrew. On Linux you can use apt-get install. The Packages required for EPICS on Centos 8 document lists all of the packages required to build EPICS base, the sequencer, synApps modules, and areaDetector. 1.3 Install EPICS mkdir $HOME/EPICS cd $HOME/EPICS git clone --recursive https://github.com/epics-base/epics-base.git cd epics-base make After compiling you should put the path into $HOME/.profile or into $HOME/.bashrc by adding the following to either one of those files: export EPICS_BASE=${HOME}/EPICS/epics-base export EPICS_HOST_ARCH=$(${EPICS_BASE}/startup/EpicsHostArch) export PATH=${EPICS_BASE}/bin/${EPICS_HOST_ARCH}:${PATH} 1 EPICS How-Tos EpicsHostArch is a program provided by EPICS that returns the architecture of your system. Thus the code above should be fine for every architecture. 1.4 Test EPICS Now log out and log in again, so that your new path is set correctly. Alternatively, you can execute the three lines above beginning with export directly from the terminal. Run softIoc and, if everything is ok, you should see an EPICS prompt. softIoc epics> You can exit with ctrl-c or by typing exit. Voilà. Ok, that is not very impressive, but at least you know that EPICS is installed correctly. So now let us try something more complex, which will hopefully suggest how EPICS works. In whatever directory you like, prepare a file test.db that reads like record(ai,"temperature:water") { field(DESC,"Water temperature in the fish tank") } This file defines a record instance called temperature:water, which is an analog input (ai) record. As you can imagine DESC stays for Description. Now we start softIoc again, but this time using this record database. softIoc-d test.db Now, from your EPICS prompt, you can list the available records with the dbl command and you will see something like epics> dbl temperature:water epics> Open a new terminal (we call it nr. 2) and try the command line tools caget and caput. You will see something like your prompt> caget temperature:water temperature:water0 your prompt> caget temperature:water.DESC temperature:water.DESC Water temperature in the fish tank your prompt> caput temperature:water 21 Old : temperature:water0 New : temperature:water 21 your prompt> caput temperature:water 24 Old : temperature:water 21 New : temperature:water 24 your prompt> caget temperature:water temperature:water 24 ... etc. Now open yet another terminal (nr. 3) and try camonitor as 2 Chapter 1. Installation on Linux/UNIX/DARWIN (Mac) EPICS How-Tos camonitor temperature:water First, have a look at what happens when you change the temperature:water value from terminal nr. 2 using caput. Then, try to change the value by some tiny amounts, like 15.500001, 15.500002, 15.500003. You will see that camonitor reacts but the readings do not change. If you wanted to see more digits, you could run camonitor-g8 temperature:water For further details on the Channel Access protocol, including documentation on the caput, caget, camonitor... command line tools, please refer to the Channel Access Reference Manual. In real life, however, it is unlikely that the 8 digits returned by your thermometer (in this example) are all significant. We should thus limit the traffic to changes of the order of, say, a hundredth of a degree. To do this, we add one line to the file test.db, so that it reads record(ai,"temperature:water") { field(DESC,"Water temperature in Lab 10") field(MDEL,".01") } MDEL stands for Monitor Deadband. If you now run softIoc-d test.db with the new test.db file, you will see that camonitor reacts only to changes that are larger than 0.01. This was just a simple example. Please refer to a recent Record Reference Manual for further information. 1.5 Create a demo/test ioc to test ca and pva mkdir -p $HOME/EPICS/TEST/testIoc cd $HOME/EPICS/TEST/testIoc makeBaseApp.pl -t example testIoc makeBaseApp.pl -i -t example testIoc make cd iocBoot/ioctestIoc chmod u+x st.cmd ioctestIoc> ./st.cmd #!../../bin/darwin-x86/testIoc < envPaths epicsEnvSet("IOC","ioctestIoc") epicsEnvSet("TOP","/Users/maradona/EPICS/TEST/testIoc") epicsEnvSet("EPICS_BASE","/Users/maradona/EPICS/epics-base") cd "/Users/maradona/EPICS/TEST/testIoc" ## Register all support components dbLoadDatabase "dbd/testIoc.dbd" testIoc_registerRecordDeviceDriver pdbbase ## Load record instances dbLoadTemplate "db/user.substitutions" dbLoadRecords "db/testIocVersion.db", "user=junkes" dbLoadRecords "db/dbSubExample.db", "user=junkes" #var mySubDebug 1 #traceIocInit cd "/Users/maradona/EPICS/TEST/testIoc/iocBoot/ioctestIoc" iocInit (continues on next page) 1.5. Create a demo/test ioc to test ca and pva 3 EPICS How-Tos (continued from previous page) Starting iocInit ############################################################################ ## EPICS R7.0.1.2-DEV ## EPICS Base built Mar 8 2018 ############################################################################ iocRun: All initialization complete 2018-03-09T13:07:02.475 Using dynamically assigned TCP port 52908. ## Start any sequence programs #seq sncExample, "user=maradona" epics> dbl maradona:circle:tick maradona:compressExample maradona:line:b maradona:aiExample maradona:aiExample1 maradona:ai1 maradona:aiExample2 ... etc. ... epics> Now in another terminal, one can try command line tools like caget, caput, camonitor, cainfo (Channel Access) pvget, pvput, pvlist, eget,... (PVAccess) 1.6 Add the asyn package cd $HOME/EPICS mkdir support cd support git clone https://github.com/epics-modules/asyn.git cd asyn Edit $HOME/EPICS/support/asyn/configure/RELEASE and set EPICS_BASE like EPICS_BASE=${HOME}/EPICS/epics-base Comment IPAC=... and SNCSEQ=..., as they are not needed for the
Load more

Recommended publications
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]
  • Buildsystems and What the Heck for We Actually Use the Autotools
    Buildsystems and what the heck for we actually use the autotools Tom´aˇsChv´atal SUSE Packagers team 2013/07/19 Introduction Who the hell is Tom´aˇsChv´atal • SUSE Employee since 2011 - Team lead of packagers team • Packager of Libreoffice and various other stuff for openSUSE • openSUSE promoter and volunteer • Gentoo developer since fall 2008 3 of 37 Autotools process Complete autotools process 5 of 37 Make Why not just a sh script? Always recompiling everything is a waste of time and CPU power 7 of 37 Plain makefile example CC ?= @CC@ CFLAGS ?= @CFLAGS@ PROGRAM = examplebinary OBJ = main.o parser.o output.o $ (PROGRRAM) : $ (OBJ) $ (CC) $ (LDFLAGS) −o $@ $^ main.o: main.c common.h parser.o: parser.c common.h output.o: output.c common.h setup.h i n s t a l l : $ (PROGRAM) # You have to use tabs here $(INSTALL) $(PROGRAM) $(BINDIR) c l e a n : $ (RM) $ (OBJ) 8 of 37 Variables in Makefiles • Variables expanded using $(), ie $(VAR) • Variables are assigned like in sh, ie VAR=value • $@ current target • $<the first dependent file • $^all dependent files 9 of 37 Well nice, but why autotools then • Makefiles can get complex fast (really unreadable) • Lots of details to keep in mind when writing, small mistakes happen fast • Does not make dependencies between targets really easier • Automake gives you automatic tarball creation (make distcheck) 10 of 37 Autotools Simplified autotools process 12 of 37 Autoconf/configure sample AC INIT(example , 0.1, [email protected]) AC CONFIG HEADER([ config .h]) AC PROG C AC PROG CPP AC PROG INSTALL AC HEADER STDC AC CHECK HEADERS([string.h unistd.h limits.h]) AC CONFIG FILES([ Makefile doc/Makefile src/Makefile]) AC OUTPUT 13 of 37 Autoconf syntax • The M4 syntax is quite weird on the first read • It is not interpreted, it is text substitution machine • Lots of quoting is needed, if in doubt add more [] • Everything that does or might contain whitespace or commas has to be quoted • Custom autoconf M4 macros are almost unreadable 14 of 37 Automake bin PROGRAMS = examplebinary examplebinary SOURCES = n s r c /main .
    [Show full text]
  • Building Gridlab-D from Source on Windows with MSYS2 Installing MSYS2: the MSYS2 Environment Is Used to Build Gridlab-D 4.1 Or Newer for the Windows OS
    Building GridLAB-D from Source on Windows with MSYS2 Installing MSYS2: The MSYS2 environment is used to build GridLAB-D 4.1 or newer for the Windows OS. It can be downloaded from https://www.msys2.org/. From the website download the appropriate MSYS2 installer for 32bit (i686) and 64bit (x86_64) OS’s. The website also walks through the installation process. This guide will also walk through the installation process for the 64bit installer. Once the installer is downloaded the execute the installer. This is the first window that pops up. Click Next. It will then ask where to install MSYS2 64bit. The default location is C:\msys64 for MSYS2 64bit. Once the location has been specified click Next. Then it will ask where to create the program’s shortcuts. Use an existing one or create a new name. Once a destination is chosen click Next. At this point the installer begins to install MSYS2 onto the computer. Once installation is complete click Next. Then click Finish and installation is successful. Setting Up the MSYS2 Environment: To start the MSYS2 environment start msys2.exe. A window like below should pop up. As can be seen MSYS2 provides a Linux-like command terminal and environment for building GNU compliant C/C++ executables for Windows OS’s. When Running the MSYS2 environment for the first time updates will need to be performed. To perform update run $ pacman -Syuu Type “y” and hit enter to continue. If you get a line like the following: Simply close the MSYS2 window and restart the MSYS2 executable.
    [Show full text]
  • Linux from Scratch 版本 R11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇
    Linux From Scratch 版本 r11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇ 由 Gerard Beekmans 原著 总编辑：Bruce Dubbs Linux From Scratch: 版本 r11.0-36-中⽂翻译版 : 发布于 2021 年 9 ⽉ 21 ⽇ 由 由 Gerard Beekmans 原著和总编辑：Bruce Dubbs 版权所有 © 1999-2021 Gerard Beekmans 版权所有 © 1999-2021, Gerard Beekmans 保留所有权利。 本书依照 Creative Commons License 许可证发布。 从本书中提取的计算机命令依照 MIT License 许可证发布。 Linux® 是Linus Torvalds 的注册商标。 Linux From Scratch - 版本 r11.0-36-中⽂翻译版 ⽬录 序⾔ .................................................................................................................................... viii i. 前⾔ ............................................................................................................................ viii ii. 本书⾯向的读者 ............................................................................................................ viii iii. LFS 的⽬标架构 ............................................................................................................ ix iv. 阅读本书需要的背景知识 ................................................................................................. ix v. LFS 和标准 ..................................................................................................................... x vi. 本书选择软件包的逻辑 .................................................................................................... xi vii. 排版约定 .................................................................................................................... xvi viii. 本书结构 .................................................................................................................
    [Show full text]
  • Project-Team CONVECS
    IN PARTNERSHIP WITH: Institut polytechnique de Grenoble Université Joseph Fourier (Grenoble) Activity Report 2016 Project-Team CONVECS Construction of verified concurrent systems IN COLLABORATION WITH: Laboratoire d’Informatique de Grenoble (LIG) RESEARCH CENTER Grenoble - Rhône-Alpes THEME Embedded and Real-time Systems Table of contents 1. Members :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2. Overall Objectives :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 3. Research Program :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 3.1. New Formal Languages and their Concurrent Implementations2 3.2. Parallel and Distributed Verification3 3.3. Timed, Probabilistic, and Stochastic Extensions4 3.4. Component-Based Architectures for On-the-Fly Verification4 3.5. Real-Life Applications and Case Studies5 4. Application Domains ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::5 5. New Software and Platforms :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 5.1. The CADP Toolbox6 5.2. The TRAIAN Compiler8 6. New Results :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 6.1. New Formal Languages and their Implementations8 6.1.1. Translation from LNT to LOTOS8 6.1.2. Translation from LOTOS NT to C8 6.1.3. Translation from LOTOS to Petri nets and C9 6.1.4. NUPN 9 6.1.5. Translation from BPMN to LNT 10 6.1.6. Translation from GRL to LNT 10 6.1.7. Translation of Term Rewrite Systems 10 6.2. Parallel and Distributed Verification 11 6.2.1. Distributed State Space Manipulation 11 6.2.2. Distributed Code Generation for LNT 11 6.2.3. Distributed Resolution of Boolean Equation Systems 11 6.2.4. Stability of Communicating Systems 12 6.2.5. Debugging of Concurrent Systems 12 6.3. Timed, Probabilistic, and Stochastic Extensions 12 6.4. Component-Based Architectures for On-the-Fly Verification 13 6.4.1.
    [Show full text]
  • Bioperl What’S Bioperl?
    Bioperl What’s Bioperl? Bioperl is not a new language It is a collection of Perl modules that facilitate the development of Perl scripts for bioinformatics applications. Bioperl and perl Bioperl Modules Perl Modules Perls script input Perl Interpreter output Bioperl and Perl Why bioperl for bioinformatics? Perl is good at file manipulation and text processing, which make up a large part of the routine tasks in bioinformatics. Perl language, documentation and many Perl packages are freely available. Perl is easy to get started in, to write small and medium-sized programs. Where to get help Type perldoc <modulename> in terminal Search for particular module in https://metacpan.org Bioperl Document Object-oriented and Process-oriented programming Process-oriented: Yuan Hao eats chicken Name object: $name Action method: eat Food object: $food Object-oriented: $name->eat($food) Modularize the program Platform and Related Software Required Perl 5.6.1 or higher Version 5.8 or higher is highly recommended make for Mac OS X, this requires installing the Xcode Developer Tools Installation On Linux or Max OS X Install from cpanminus: perlbrew install-cpanm cpanm Bio::Perl Install from source code: git clone https://github.com/bioperl/bioperl-live.git cd bioperl-live perl Build.PL ./Build test (optional) ./Build install Installation On Windows Install MinGW (MinGW is incorporated in Strawberry Perl, but must it be installed through PPM for ActivePerl) : ppm install MinGW Install Module::Build, Test::Harness and Test::Most through CPAN: Type cpan to enter the CPAN shell. At the cpan> prompt, type install CPAN Quit (by typing ‘q’) and reload CPAN.
    [Show full text]
  • Project Skeleton for Scientific Software
    Computational Photonics Group Department of Electrical and Computer Engineering Technical University of Munich bertha: Project Skeleton for Scientific Software Michael Riesch , Tien Dat Nguyen , and Christian Jirauschek Department of Electrical and Computer Engineering, Technical University of Munich, Arcisstr. 21, 80333 Munich, Germany [email protected] Received: 10 December 2019 / Accepted: 04 March 2020 / Published: 23 March 2020 * Abstract — Science depends heavily on reliable and easy-to-use software packages, such as mathematical libraries or data analysis tools. Developing such packages requires a lot of effort, which is too often avoided due to the lack of funding or recognition. In order to reduce the efforts required to create sustainable software packages, we present a project skeleton that ensures the best software engineering practices from the start of a project, or serves as reference for existing projects. 1 Introduction In a recent essay in Nature [1], a familiar dilemma in science was addressed. On the one hand, science relies heavily on open-source software packages, such as libraries for mathematical operations, implementations of numerical methods, or data analysis tools. As a consequence, those software packages need to work reliably and should be easy to use. On the other hand, scientific software is notoriously underfunded and the required efforts are achieved as side projects or by the scientists working in their spare time. Indeed, a lot of effort has to be invested beyond the work on the actual implementation – which is typically a formidable challenge on its own. This becomes apparent from literature on software engineering in general (such as the influential “Pragmatic Programmer” [2]), and in scientific contexts in particular (e.g., [3–6]).
    [Show full text]
  • Technical Computing on the OS … That Is Not Linux! Or How to Leverage Everything You‟Ve Learned, on a Windows Box As Well
    Tools of the trade: Technical Computing on the OS … that is not Linux! Or how to leverage everything you‟ve learned, on a Windows box as well Sean Mortazavi & Felipe Ayora Typical situation with TC/HPC folks Why I have a Windows box How I use it It was in the office when I joined Outlook / Email IT forced me PowerPoint I couldn't afford a Mac Excel Because I LIKE Windows! Gaming It's the best gaming machine Technical/Scientific computing Note: Stats completely made up! The general impression “Enterprise community” “Hacker community” Guys in suits Guys in jeans Word, Excel, Outlook Emacs, Python, gmail Run prepackaged stuff Builds/runs OSS stuff Common complaints about Windows • I have a Windows box, but Windows … • Is hard to learn… • Doesn‟t have a good shell • Doesn‟t have my favorite editor • Doesn‟t have my favorite IDE • Doesn‟t have my favorite compiler or libraries • Locks me in • Doesn‟t play well with OSS • …. • In summary: (More like ) My hope … • I have a Windows box, and Windows … • Is easy to learn… • Has excellent shells • Has my favorite editor • Supports my favorite IDE • Supports my compilers and libraries • Does not lock me in • Plays well with OSS • …. • In summary: ( or at least ) How? • Recreating a Unix like veneer over windows to minimize your learning curve • Leverage your investment in know how & code • Showing what key codes already run natively on windows just as well • Kicking the dev tires using cross plat languages Objective is to: Help you ADD to your toolbox, not take anything away from it! At a high level… • Cygwin • SUA • Windowing systems “The Unix look & feel” • Standalone shell/utils • IDE‟s • Editors General purpose development • Compilers / languages / Tools • make • Libraries • CAS environments Dedicated CAS / IDE‟s And if there is time, a couple of demos… Cygwin • What is it? • A Unix like environment for Windows.
    [Show full text]
  • Perl on Windows
    BrokenBroken GlassGlass Perl on Windows Chris 'BinGOs' Williams “This is your last chance. After this, there is no turning back. You take the blue pill - the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill - you stay in Wonderland and I show you how deep the rabbit-hole goes.” A bit of history ● 5.003_24 - first Windows port ● 5.004 - first Win32 and Cygwin support, [MSVC++ and Borland C++] ● 5.005 - experimental threads, support for GCC and EGCS ● 5.6.0 - experimental fork() support ● 5.8.0 - proper ithreads, fork() support, 64bit Windows [Intel IA64] ● 5.8.1 - threads support for Cygwin ● 5.12.0 - AMD64 with Mingw gcc ● 5.16.0 - buh-bye Borland C++ Time for some real archaeology Windows NT 4.0 Resource Kit CDROM ActivePerl http://www.activestate.com/perl ● July 1998 - ActivePerl 5.005 Build 469 ● March 2000 - ActivePerl 5.6.0 Build 613 ● November 2002 - ActivePerl 5.8.0 Build 804 ● November 2005 - ActivePerl 5.8.7 Build 815 [Mingw compilation support] ● August 2006 - ActivePerl 5.8.8 Build 817 [64bit] ● June 2012 - ActivePerl 5.16.0 Build 1600 ● Built with MSVC++ ● Can install or use MinGW ● PPM respositories of popular modules ● Commercial support ● PerlScript – Active Scripting engine ● Perl ISAPI Strawberry Perl http://strawberryperl.com ● July 2006 - Strawberry Perl 5.8.8 Alpha 1 released ● April 2008 - Strawberry Perl 5.10.0.1 and 5.8.8.1 released ● January 2009 - first portable release ● April 2010 - 64bit and 32bit releases ● May 2012 - Strawberry Perl 5.16.0.1 released ● August
    [Show full text]
  • Libreoffice Magazine Brasil Diagramado No Libreoffice Draw EDITORIAL
    Magazine Ano 1 - Edição 1 Outubro de 2012 Caso de uso: LibreOffice na Secretaria de Segurança do Rio de Janeiro Light Proof a nova sensação Tutorial: do LibreOffice Desenvolvendo Entrevistas com Extensões Basic desenvolvedores do LibreOffice e e c c e e n n a a i i r r o o t t c c i Artigos | Dicas | Tutoriais | e muito mais... i V V LibreOffice Magazine Brasil Diagramado no LibreOffice Draw EDITORIAL Sobre partos e renascimentos Editores No mês de setembro comemoramos dois anos de criação da The Eliane Domingos de Sousa Document Foundation. Sinto-me particularmente agradecido por ter Olivier Hallot Vera Cavalcante embarcado em uma aventura de alto risco, mas com a convicção que era a coisa certa a ser feita em 2010. Com um capital intelectual Redação: vasto sobre uma tecnologia que estava ainda mostrando seus frutos, Ana Cristina Geyer Moraes fiquei receoso dos rumos tomados pela empresa que mantinha o Eliane Domingos de Sousa OpenOffice.org em uma camisa de força que o impedia de evoluir no José Carlos de Oliveira compasso que o mercado exigia de uma suíte office que almeja a Klaibson Ribeiro maturidade. Michael Meeks Na época, eu era membro eleito do Conselho da Comunidade, Noelson Alves Duarte composto por alguns representantes das comunidades mundo afora, Raimundo Santos Moura e uma maioria de funcionários do principal patrocinador. Na reunião Raul Pacheco da Silva anual do Conselho, com a participação do principal executivo do Swapnil Bhartiya projeto OpenOffice.org da empresa, soubemos que a participação da comunidade não era estratégica para os objetivos empresariais e que Tradução a condução do projeto seria feita pela empresa a revelia da David Jourdain comunidade.
    [Show full text]
  • Mobile Cloud Based Compiler : a Novel Framework for Academia
    International Journal of Advancements in Research & Technology, Volume 2, Issue4, April‐2013 445 ISSN 2278‐7763 Mobile Cloud based Compiler : A Novel Framework For Academia Mahendra Mehra, Kailas.k.Devadkar, Dhananjay Kalbande 1Computer Engineering, Sardar Patel Institute of Technology, Mumbai, India; 2 Computer Engineering, Sardar Patel Institute of Technology, Mum- bai, India. Email: [email protected], [email protected], [email protected] ABSTRACT Cloud computing is a rising technology which enables convenient, on-demand network access to a shared pool of configurable computing resources. Mobile cloud computing is the availability of cloud computing services in a mobile ecosystem. Mobile cloud computing shares with cloud computing the notion that services is provided by a cloud and accessed through mobile plat- forms. The paper aims to describe an online mobile cloud based compiler which helps to reduce the problems of portability and storage space and resource constraints by making use of the concept of mobile cloud computing. The ability to use compiler ap- plication on mobile devices allows a programmer to get easy access of the code and provides most convenient tool to compile the code and remove the errors. Moreover, a mobile cloud based compiler can be used remotely throughout any network con- nection (WI-FI/ GPRS) on any Smartphone. Thus, avoiding installation of compilers on computers and reducing the dependen- cy on computers to write and execute programs. Keywords: Mobile cloud computing; mobile web services; JASON; Compiler; Academia 1 INTRODUCTION The classroom is changing. From the time school bell rings to smartphones, and desktops. The cloud helps ensure that stu- study sessions that last well into the night, students and facul- dents, teachers, faculty, parents, and staff have on-demand ty are demanding more technology services from their access to critical information using any device from any- schools.
    [Show full text]
  • Builder Documentation Release 3.26.0
    Builder Documentation Release 3.26.0 Christian Hergert, et al. Sep 13, 2017 Contents 1 Contents 3 1.1 Installation................................................3 1.1.1 via Flatpak...........................................3 1.1.1.1 Command Line....................................3 1.1.2 Local Flatpak Builds......................................4 1.1.3 via JHBuild...........................................4 1.1.3.1 Command Line....................................4 1.1.4 via Release Tarball.......................................5 1.1.5 Troubleshooting.........................................5 1.2 Exploring the Interface..........................................5 1.2.1 Project Greeter.........................................6 1.2.2 Workbench Window......................................6 1.2.3 Header Bar...........................................7 1.2.4 Switching Perspectives.....................................7 1.2.5 Showing and Hiding Panels...................................7 1.2.6 Build your Project........................................7 1.2.7 Editor..............................................9 1.2.8 Autocompletion......................................... 11 1.2.9 Documentation......................................... 11 1.2.10 Splitting Windows....................................... 12 1.2.11 Searching............................................ 14 1.2.12 Preferences........................................... 15 1.2.13 Command Bar.......................................... 16 1.2.14 Transfers...........................................
    [Show full text]