Giter VIP home page Giter VIP logo

latticist's Introduction

latticist

latticist is an R package, providing a graphical user interface for exploratory visualisation.

I am not maintaining latticist any more. I have moved it to github, as requested by some users, in the hope that it may be adopted.

The original project page is still up at https://latticist.googlecode.com/ and it has a list of screenshots that is not reproduced here.

latticist's People

Contributors

floybix avatar landroni avatar

Stargazers

avatar avatar

Watchers

avatar avatar avatar

Forkers

landroni george-koutsostamatis djmarais vamshibandari

latticist's Issues

CRAN checks: assignments to the global environment

And the last item of the failed CRAN checks:

Found the following assignments to the global environment:
 File ‘latticist/R/latticeStyleGUI.R’:
   assign("trellis.par.theme", list(), globalenv())
   assign("trellis.par.log", list(), globalenv())
   assign("trellis.par.log", list(), globalenv())
   assign("trellis.par.theme", trellis.par.get(), globalenv())
   assign("trellis.par.theme", trellis.par.get(), globalenv())
   assign("trellis.par.log", tmplog, globalenv())
   assign("trellis.par.theme", trellis.par.get(), globalenv())
   assign("trellis.par.theme", trellis.par.get(), globalenv())
   assign("trellis.par.theme", trellis.par.get(), globalenv())

Are the assignments to globalenv() necessary? Can we avoid them?

Unexported objects imported by ':::' calls

As per Brian's CRAN checks:

* checking dependencies in R code ... WARNING
Unexported objects imported by ':::' calls:
  ‘lattice:::compute.packet’ ‘playwith:::blockRedraws’
  See the note in ?`:::` about the use of this operator.
  Including base/recommended package(s):
  ‘lattice’
See the information on DESCRIPTION files in the chapter ‘Creating R
packages’ of the ‘Writing R Extensions’ manual.

?':::' has this to say:

Note

It is typically a design mistake to use ::: in your code since the corresponding object has probably been kept internal for a good reason. Consider contacting the package maintainer if you feel the need to access the object for anything but mere inspection.

I checked both lattice and playwith, and in both cases the offending functions are indeed not exported. I suspect we can easily export blockRedraws in playwith... Do you see any issues with that?

As for compute.packet, should I contact lattice maintainers?

* checking R code for possible problems ... NOTE

R CMD check on current trunk complains as follows:

  • checking R code for possible problems ... NOTE

    latticeStyleToBasePar : setAlpha: warning in rgb(crgb[1], crgb[2],
    crgb[3], crgb[4], max = 255): partial argument match of 'max' to
    'maxColorValue'
    latticistCompose : doCompose : deparse1: warning in deparse(expr, width
    = 500, control = NULL, backtick = TRUE): partial argument match of
    'width' to 'width.cutoff'
    latticeStyleGUI: no visible binding for global variable ‘category’

I'm not sure what this is about, nor how it should be fixed. Ideas?

CRAN checks: `no visible binding for global variable` and `no visible global function definition for`

OK, now for the second part of the failed CRAN checks.

There are several no visible binding for global variable and no visible global function definition for:

* checking R code for possible problems ... NOTE
 custom.theme.black: no visible global function definition for
   ‘brewer.pal’
 latticeStyleDemo: no visible binding for global variable
   ‘environmental’
 latticeStyleGUI: no visible binding for global variable
   ‘brewer.pal.info’
 latticeStyleGUI: no visible binding for global variable ‘category’
 latticeStyleGUI: no visible global function definition for ‘gpar’
 latticeStyleGUI : loadQualPal: no visible global function definition
   for ‘brewer.pal’
 latticeStyleGUI : <anonymous>: no visible global function definition
   for ‘display.brewer.all’
 latticeStyleGUI : setRegions: no visible global function definition for
   ‘brewer.pal’
 latticistToolConstructor : <anonymous> : reCompose: no visible global
   function definition for ‘updateMainCall’
 latticistToolConstructor : <anonymous> : reCompose: no visible global
   function definition for ‘playDevSet’
 latticistToolConstructor : <anonymous> : reCompose: no visible global
   function definition for ‘playNewPlot’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkHBox’
 latticistToolConstructor : <anonymous> : niceButton: no visible global
   function definition for ‘gtkEventBox’
 latticistToolConstructor : <anonymous> : niceButton: no visible global
   function definition for ‘gtkLabel’
 latticistToolConstructor : <anonymous> : addCBEHandlers: no visible
   global function definition for ‘gSignalConnect’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkVBox’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gSignalConnect’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkImageNewFromFile’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkLabel’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkButton’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkComboBoxEntryNewText’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkVSeparator’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkCheckButton’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkSpinButton’
 latticistToolConstructor : <anonymous>: no visible global function
   definition for ‘gtkComboBoxNewText’
 latticist_playwith: no visible global function definition for
   ‘playwith.getOption’
 latticist_playwith: no visible global function definition for
   ‘playwith’

Is there something straightforward that can be done avoid hitting these, or would this require major surgery?

Packages in Depends field not imported from: ‘lattice’ ‘latticeExtra’ ‘vcd’

R CMD check on current trunk complains as follows:

  • checking dependencies in R code ... NOTE
    Packages in Depends field not imported from:
    ‘lattice’ ‘latticeExtra’ ‘vcd’
    These packages needs to imported from for the case when
    this namespace is loaded but not attached.
    See the information on DESCRIPTION files in the chapter ‘Creating R
    packages’ of the ‘Writing R Extensions’ manual.

Any ideas on how this should be fixed? I suspect that the NAMESPACE should have several additional import calls, but I'm not sure if I should import an entire package or just some functions..

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.