exist-development — eXist Developer's List

Re: [Exist-development] Java7

[Dannes W. <da...@ex...>]

please could you verify in Oxygen which java version is actually used?

my bet is..... Java6 :-( where to find:




regards

Dannes


On Thu, May 1, 2014 at 11:29 AM, Jens Østergaard Petersen <oe...@gm...
> wrote:

> Hi,
>
> Does this mean that one cannot access eXist-db from oXygen?
>
> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to:
> java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException :
> Unsupported major.minor version 51.0
>
> is the error I get.
>
> Jens
>
> On 30 Apr 2014 at 20:11:45, Dannes Wessels (da...@ex...) wrote:
>
> All,
>
> we finally changed git 'develop' to compile with java7; So we can make use
> of all features introduced in that java version that is introduced
> 2011-07-28 already
>
> https://github.com/eXist-db/exist/pull/207
>
> regards
>
> Dannes
> ------------------------------------------------------------------------------
>
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> unparalleled scalability from the best Selenium testing platform
> available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] Java7

[Jens Ø. P. <oe...@gm...>]

Hi Dmitriy,

The jars referenced from oXygen (the data source drivers) are the jars compiled in the latest eXist-db version.

Switching to a version before the change (making the references apply to the older version) and everything works again.

I am on Mac OS X 10.9.2 running the oXygen build from April 3, 2014. I am still running java version 1.7.0_51, if that matters.

Jens

On 1 May 2014 at 11:32:46, Dmitriy Shabanov (sha...@gm...) wrote:

Did you update eXist's jar at oXygen?

On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...> wrote:
Hi,

Does this mean that one cannot access eXist-db from oXygen?

Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to: java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException : Unsupported major.minor version 51.0

is the error I get.


--
Dmitriy Shabanov

Re: [Exist-development] Java7

[Dmitriy S. <sha...@gm...>]

Did you update eXist's jar at oXygen?

On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen
<oe...@gm...>wrote:

> Hi,
>
> Does this mean that one cannot access eXist-db from oXygen?
>
> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to:
> java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException :
> Unsupported major.minor version 51.0
>
> is the error I get.
>


-- 
Dmitriy Shabanov

Re: [Exist-development] Java7

[Jens Ø. P. <oe...@gm...>]

Hi,

Does this mean that one cannot access eXist-db from oXygen?

Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to: java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException : Unsupported major.minor version 51.0

is the error I get.

Jens

On 30 Apr 2014 at 20:11:45, Dannes Wessels (da...@ex...) wrote:

All, 

we finally changed git 'develop' to compile with java7; So we can make use of all features introduced in that java version that is introduced 2011-07-28 already 

https://github.com/eXist-db/exist/pull/207 

regards 

Dannes 
------------------------------------------------------------------------------ 
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE 
Instantly run your Selenium tests across 300+ browser/OS combos. Get 
unparalleled scalability from the best Selenium testing platform available. 
Simple to use. Nothing to install. Get started now for free." 
http://p.sf.net/sfu/SauceLabs 
_______________________________________________ 
Exist-development mailing list 
Exi...@li... 
https://lists.sourceforge.net/lists/listinfo/exist-development 

[Exist-development] Java7

[Dannes W. <da...@ex...>]

All,

we finally changed git 'develop' to compile with java7; So we can make use of all features introduced in that java version that is introduced 2011-07-28 already

https://github.com/eXist-db/exist/pull/207

regards

Dannes

[Exist-development] Possible very serious concurrency issue with XQueryURLRewrite

[Casey J. <cas...@jo...>]

I think I have found what I believe to be a very serious concurrency issue
in the XQueryURLRewrite code (eXist develop). This has been very hard to
track down so please bare with me as I describe what I have seen so far.

I was noticing that every so often when there were several simultaneous
requests to my application the result from one request would return the
wrong result. Specifically, it would return the same result as another
request that happened at a similar time.

I started to debug this and found that the mixup happens with a parameter
(via <add-parameter/>) somewhere in the rewrite code. I tried to create a
reproducible test for this, but I can only seem to recreate it every so
often and only with my production code, which is obviously much more
complex than the simple tests cases I was creating.

So I started doing a code review on the rewrite servlet, but after a few
hours I decided it might be a good idea to ask the community.

My controller is located at /api/get/controller.xql and  the xquery it gets
forwarded to is located at /api/get/document.xql

My request calls look like this:
http://localhost:8080/api/get/[document-uri]?view=web

For instance:
http://localhost:8080/api/get/db/documents/langref/preface.dita?view=web

My controllers role is to parse out the document-uri from this string and
turn it into a request param forwarded to document.xql. This is essentially
what my controller.xql looks like.

let $path := replace(replace(substring-after(request:get-url(), 'get'),
"//", "/"), ' ', '%20')

let $out := util:log-system-out(concat("RW: ", $path))

<dispatch xmlns="http://exist.sourceforge.net/NS/exist">

 <forward url="/api/get/document.xql" >

  <add-parameter name="path" value="{$path}"/>

 </forward>

 </dispatch>

and in document.xql I get the param I set like so:

let $path := request:get-parameter('path', '')

let $out := util:log-system-out(concat("Compiling: ",$path))

....

(Note the bolded debug messages in the code above as I will reference them
later)

Now I have noticed that every so often, the "path" parameter which comes
into the request gets replaced with a different one from another request.

I know this because I can look at the jetty request logs and I can see a
request come into the server, then I can see the debug output in my
controller, that shows that $path is parsed correctly, but then in my
document.xql I never see this path get printed in the debug statement.
Instead I see two debug statements with the "path" for a different request.

Consider the following debug output:

(Line: 18 /api/get/controller.xql) RW:
/db/documents/archSpec/dita_technicalContent_InformationTypes.dita

(Line: 18 /api/get/controller.xql) RW:
/db/documents/archSpec/dita_concept_topic.dita

(Line: 18 /api/get/controller.xql) RW:
/db/documents/archSpec/dita_generic_task_topic.dita

(Line: 18 /api/get/controller.xql) RW:
/db/documents/archSpec/dita_task_topic.dita

(Line: 18 /api/get/controller.xql) RW:
/db/documents/archSpec/dita_reference_topic.dita

(Line: 40 /api/get/document.xql) Compiling:
/db/documents/archSpec/dita_task_topic.dita

(Line: 40 /api/get/document.xql) Compiling:
/db/documents/archSpec/dita_technicalContent_InformationTypes.dita

(Line: 40 /api/get/document.xql) Compiling:
/db/documents/archSpec/dita_task_topic.dita

You can see here that the call for dita_generic_task_topic.dita comes into
the controller, but never makes it into document.xql. Instead, there are
two calls where dita_task_topic.dita is the "path" param.

So this leads me to believe that there is a very serious issue where some
data is being shared between request threads. My code review lead me to
believe this is related  to the RewriteConfig because it keeps a set of
mappings in memory, and while the methods to get these mappings are
synchronized, it seems that they can return a URLRewrite instance (In this
case PathForward) that is shared between multiple threads, and thus when
the controller result is parsed can overwrite parameters stored in the
URLRewrite instance.

I am hoping that someone who is more familiar with this code can take a
look for me. Obviously if params are indeed being overwritten then this
could inadvertently cause all kinds of problems in applications that may
delete or alter data.

Thanks!


-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.

[Exist-development] XQuery startup trigger

[Dannes W. <da...@ex...>]

All,

this morning I added a startup trigger that allows to start arbitrary xquery scripts during the startup of eXist-db.
It requires a change in conf.xml:

 <startup>
     <triggers>

       <trigger class="org.exist.collections.triggers.XQueryStartupTrigger">
         <parameter name="xquery" value="/db/script1.xq"/>
         <parameter name="xquery" value="/db/script2.xq"/>
       </trigger>

     </triggers>
 </startup>

regards

Dannes

Re: [Exist-development] A flaw with the at in a flwor expression.

[Loren C. <lor...@gm...>]

I found my problem.

Sent from my iPad

> On Mar 23, 2014, at 4:32 PM, Loren Cahlander <lor...@gm...> wrote:
> 
> 
> Hello folks.  I found what appears to be a bug in the at expression in a flwor statement. (current codebase)  I have the following in a function module:
> 
> declare function xs2svg:recurse($node as node()?, $model as map()) as item()* {
>     if ($node) 
>     then
>         let $children := $node/node()
>         let $count := map:entry('count', count($children))
>         let $parent-y := map:entry('parent-y', $model('y-position'))
>         let $parent-x := map:entry('parent-x', $model('x-position'))
>         let $x-position := map:entry('x-position', xs:integer($model('x-position')) + xs:integer($model('width')) + 45)
>         let $id := $model('id')
>         return
>             for $cnode at $position in $children
>                 let $new-id := xs:string($id) || '_' || xs:string($position)
>                 let $new-map := map:new((
>                                     map:entry('id', $new-id ),
>                                     map:entry('y-position', xs:integer($model('y-position')) + (($position - 1) * (46 + 25))), 
>                                     $x-position,
>                                     $parent-x, 
>                                     $parent-y, 
>                                     $count,
>                                     map:entry('position', $position)
>                                     ))
>                 order by $position
>                 return xs2svg:process-node($cnode, $new-map) 
>     else ()
> };
> 
> I get the following values 10, 12, 14, 15, ... instead of 1, 2, 3, 4, ...
> 
> When I run the following in eXide, it does give the proper values:
> 
> xquery version "3.0";
> 
>     let $doc := doc('http://www.docbook.org/xml/5.0/xsd/docbook.xsd')//xs:schema
>     let $children := $doc/node()
>     let $results := for $cnode at $position in $children
>                     return <result name='{$cnode/@name}' position='{$position}'></result>
>                     
> return <results>{$results}</results>
> 
> 
> I am attaching the XAR.  Run the code in modules/runsvg.xq
> 
> 
> I am in the process of translating the code for http://xsdvi.sourceforge.net/ipo.svg from java to an XQuery function module.
> 
> <xsd-lib-0.1.xar>

[Exist-development] A flaw with the at in a flwor expression.

[Loren C. <lor...@gm...>]

Hello folks.  I found what appears to be a bug in the at expression in a flwor statement. (current codebase)  I have the following in a function module:

declare function xs2svg:recurse($node as node()?, $model as map()) as item()* {
    if ($node) 
    then
        let $children := $node/node()
        let $count := map:entry('count', count($children))
        let $parent-y := map:entry('parent-y', $model('y-position'))
        let $parent-x := map:entry('parent-x', $model('x-position'))
        let $x-position := map:entry('x-position', xs:integer($model('x-position')) + xs:integer($model('width')) + 45)
        let $id := $model('id')
        return
            for $cnode at $position in $children
                let $new-id := xs:string($id) || '_' || xs:string($position)
                let $new-map := map:new((
                                    map:entry('id', $new-id ),
                                    map:entry('y-position', xs:integer($model('y-position')) + (($position - 1) * (46 + 25))), 
                                    $x-position,
                                    $parent-x, 
                                    $parent-y, 
                                    $count,
                                    map:entry('position', $position)
                                    ))
                order by $position
                return xs2svg:process-node($cnode, $new-map) 
    else ()
};

I get the following values 10, 12, 14, 15, ... instead of 1, 2, 3, 4, ...

When I run the following in eXide, it does give the proper values:

xquery version "3.0";

    let $doc := doc('http://www.docbook.org/xml/5.0/xsd/docbook.xsd')//xs:schema
    let $children := $doc/node()
    let $results := for $cnode at $position in $children
                    return <result name='{$cnode/@name}' position='{$position}'></result>
                    
return <results>{$results}</results>


I am attaching the XAR.  Run the code in modules/runsvg.xq


I am in the process of translating the code for http://xsdvi.sourceforge.net/ipo.svg from java to an XQuery function module.

Re: [Exist-development] Java 8

[Dannes W. <da...@ex...>]

Hi,

On Wed, Mar 19, 2014 at 11:27 PM, Adam Retter <ad...@ex...> wrote:

> . It could just be that
> eXist has a VERY old version of Ant with it (2010)... should probably
> be updated sometime soon! Compared to when really compile with JDK 7 I
> get different messages, i.e. no errors on JDK 7!
>

So many exclamation marks :-)

The current shipped version is 1.8.2, it seems we have a good reason to
upgrade right now..... :-)

regards

Dannes



-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

Re: [Exist-development] Java 8

[Adam R. <ad...@ex...>]

The JDK's I am using are all the official Oracle ones as I am on a Mac:

I have been compiling and running eXist on JDK 7since I fixed the test
suite to work with Java 7, a few months ago.

I can also compile eXist on JDK 7,if I both target Java 1.7 and set
the source compliance level to 1.7 in build.properties, which is good
news, no pre 1.6 code kicking about then!

At present I cannot compile eXist on JDK 8, due to errors from the
AspectJ compiler.
NOTE: For some reason when do attempt to compile eXist on JDK 8, Ant
is still reporting that it is Compiling with Java 1.7, which I think
is wrong, my JAVA_HOME is set to JDK8 and if I run java -version, I
see that it prints out the details for JDK 8. It could just be that
eXist has a VERY old version of Ant with it (2010)... should probably
be updated sometime soon! Compared to when really compile with JDK 7 I
get different messages, i.e. no errors on JDK 7!

I also appear to be able to run eXist (compiled with JDK 7) on JDK 8.
Remember if you are rebuilding an existing eXist, then you also need
to run "build.sh xquery" to re-generate the XQuery parser in eXist
(this is not part of the default build), otherwise it will not run on
JDK 8!

I can however compile and run the eXist test suite on JDK 8 (still set
as target / source 1.7). Unfortunately there are 6 failing tests,
whilst that may not sound like a lot, we normally have zero. Also two
of these tests are in the security infrastructure and the others seem
to be XQuery and Range Index related, so my advice would not be to use
eXist on JDK 1.8 in production just yet.



On 18 March 2014 15:43, Loren Cahlander <lor...@gm...> wrote:
> With the coming release of java 8 on March, 25, have there been tests of eXist against the new release?
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

[Exist-development] Java 8

[Loren C. <lor...@gm...>]

With the coming release of java 8 on March, 25, have there been tests of eXist against the new release?

Re: [Exist-development] [Exist-open] Apostrophe in document name results in error 404 via WebDAV

[Hungerburg <pc...@my...>]

Moved to exist-dev.

I am just a user, that happened, out of fondness with the product, to 
peek at the code and mess with it a little. I'd like to expand on the 
analysis, a top-down approach, to try and find the vocabulary needed to 
get a clear picture.

1) The sandwitch: eXist-db lies between two interfaces -- the public 
interface (rest, webdav, xmlrpc, etc.) on the one side -- its own 
internal storage and messaging and, for binary resources, the operating 
systems file system on the other side.

# The public interface is documented in RFC, but there are also a number 
of implementations to watch, one wants to interact with, that not always 
strictly conform or have different interpretations of what the standard 
says.

# The internal storage, seemingly, can accomodate almost anything. The 
operating system interface though is different on linux, mac and 
windows, although in a small degree.

Some translation has to happen inbetween: transparent and idempotent. 
Most of it (not all) is done in the xmldb-uri class. The documentation 
there is a little scarce and sometimes directly misleading.

2) Main areas of interest:

# URI layer: A name passed in as a path-segment (GET,PUT) is encoded 
differently from a name passed in as a query-segment (GET, POST). Both 
must decode to the same: The current practice of double-en/de/coding is bad.

# FS layer: How to handle names that are valid in URIs, but (mostly) 
NTFS prohibits? The other way round: one wants to store UTF-8 names 
instead of percent-encoded (as in a URI) non-ASCII diacritics etc.

# Messaging layer: of course it was best, to always pass java.net.URI 
objects, but for performance reasons a plain String is preferred 
sometimes… This gets hairy soon, very clear guides on normalization must 
be in place.

All in all quite some effort required, for probably marginal gains. I 
suspect though that, the more people use webdav the more the need to do 
something will show. People are used to certain inconveniences in using 
web-based systems, unlike when interacting with something that looks 
like a conventional filesystem.

Kind regards

Peter

Re: [Exist-development] [expath] Re: Start of the new look for the dashboard

[Adam R. <ada...@go...>]

Likewise I do not understand how this is possible in EXPath. To say the
least you would need to implement in XQuert and/or XSLT which elevates it
immediately beyond XPath solely.  You will also need many vendor extensions
which have not yet Bern addressed by EXPath and you will presumably need
some sort if client server api, again this has not been addresses by EXPath
really.

I think there are too many prerequisites which are missing for this to be a
common project shared between implementations at present. Rather, I would
suggest that you abstract implementation specifics behind well defined
api's into modules which could be replaced at a later date by other
implementations.
On 11 Mar 2014 05:28, "Joe Wicentowski" <jo...@gm...> wrote:

> Hi Loren,
>
> Thanks again for your efforts on this.  I'm not entirely convinced
> this makes sense as an EXPath project.  Are you saying that other
> EXPath implementations have the need for a GUI dashboard?  There isn't
> even an EXPath standard on package installation GUI interfaces, which
> would seem to me to be a prerequisite for a GUI that helps navigate
> between the installed packages.  Not to say this couldn't be of use
> some day, but perhaps your idea is advanced beyond the needs of the
> EXPath community at this stage.
>
> Unless EXPath folks from other projects say otherwise, perhaps this is
> best conceived as simply a replacement for the eXist-db Dashboard?
>
> Just my two cents.
>
> Joe
>
> On Thu, Mar 6, 2014 at 10:47 AM, Loren Cahlander
> <lor...@gm...> wrote:
> > Hello Joe,
> >
> > The idea of this occurred during the eXist-db pre-conference session.
> >
> >  The idea would be to abstract out the difference between the
> implementations and have those as control panels to get displayed just like
> apps get displayed.
> >
> > The control panels could then be written just like any other webapp, but
> calling implementation specific functions.
> >
> > Loren
> >
> > Sent from my iPad
> >
> >> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
> >>
> >> Hi Loren,
> >>
> >> Nice start.  Could you expand a bit on how you see this effort being a
> >> broader EXPath project?
> >>
> >> Joe
> >>
> >> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
> >> <lor...@gm...> wrote:
> >>> Adding the EXPath mailing list to the discussion.
> >>>
> >>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
> >>>>
> >>>> Just to add my own 2 cents.
> >>>>
> >>>> From my experience of developing 2 plugins for the dashboard, I have
> >>>> to say that it was incredibly hard to do and frustrating as I could
> >>>> not really achieve the display I wanted. I also find a very uneasy
> >>>> mismatch between plugins and XARs.
> >>>>
> >>>> I think it would be much simpler if everything was XARs but there was
> >>>> a certain XAR template, that effectively displays the XAR inline
> >>>> within the dashboard in the same way that plugins currently work. It
> >>>> would be nice if I could author a plugin, without having to really
> >>>> know anything about the dashboard. It seems to me that this technology
> >>>> already exists in the form of Web Components and we should embrace
> >>>> these and not invent something else.
> >>>>
> >>>> Regards frameworks, I don't mind which you use for the UI
> >>>> particularly, however if there is going to be any Javascript, I have a
> >>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
> >>>> have instead been having a very happy life in the last year or so by
> >>>> just using Angular.js.
> >>>>
> >>>>
> >>>>
> >>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
> >>>>> Hi Loren,
> >>>>>
> >>>>> i appreciate efforts to improve the dashboard. It was just a first
> quick
> >>>>> sketch back then and it's about time to think of version 2. As it's a
> >>>>> central part of the eXist user interface we should however design it
> >>>>> sensibly and gather as much input as possible.
> >>>>>
> >>>>> So first thing would be about sharing the ideas and mockups and
> ideally
> >>>>> allow comments to certain elements online (does anyone know a tool
> allowing
> >>>>> that?). Same applies to the actual code - why not setup it as a repo
> on the
> >>>>> eXistdb github (i'll ask Wolfgang about that) so more interested
> people can
> >>>>> participate.
> >>>>>
> >>>>> My first questions about your sketch:
> >>>>> am i getting you right that you'd like to make a distinction between
> our
> >>>>> current plugins (which handle administrative things within eXist)
> and the
> >>>>> actual xar applications and put them in a kind of toolbar? If so, i
> agree in
> >>>>> general with the idea - however i'm not sure if i favour a toolbar
> for that
> >>>>> - probably i can come up with some alternative so let me think about
> it.
> >>>>>
> >>>>> We should also probably define some requirements:
> >>>>> - defnitely should be responsive (+1 for your effort to do so)
> >>>>> - should allow for themes. It's a matter of taste if you like shades
> or
> >>>>> prefer a flat look. Same applies to backgrounds. So a design should
> use
> >>>>> sensible CSS classes from ground up and favor a simple and clean
> markup
> >>>>> underneath.
> >>>>> - we have to think about icon sizes as scaling (as a result of
> responsive
> >>>>> design) not always works good out of the box and icons might look
> ugly for
> >>>>> certain resolutions. So we have to test and see if we need to apply
> one (or
> >>>>> several) standard size(s)
> >>>>> - we should keep highres displays in mind (retina)
> >>>>>
> >>>>> I appreciate the use of Polymer as it seems to be ideal for the job.
> We need
> >>>>> to keep in mind however that all the plugins would need
> re-implementation as
> >>>>> they depend on Dojo at the moment - this can be quite an undertaking.
> >>>>>
> >>>>> Great that you triggered the effort - it's been on my list for quite
> some
> >>>>> time so it's time to get it going.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Joern
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <
> lor...@gm...>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hello Folks,
> >>>>>>
> >>>>>> Please take a look at http://greatlinkup.com/foo/
> >>>>>>
> >>>>>> From our discussion at the eXist pre-conference session, I am
> working on a
> >>>>>> new dashboard that should be general for all EXPath implementations.
> >>>>>>
> >>>>>> The differences between implementations would be in the control
> panels.  I
> >>>>>> am planning on moving the control panels out of the plugins.  I am
> planning
> >>>>>> on placing the control panels in /db/system/controls for eXist.
>  The control
> >>>>>> panels will have a smaller icon and the icons will be on the top
> bar.  When
> >>>>>> a control panel icon is selected, then the control panel then
> slides down
> >>>>>> underneath the top bar.  An example of this can be seen by
> selecting the
> >>>>>> first icon on the top bar and see the drop-down to show the control
> panels.
> >>>>>>
> >>>>>> The squares below are for the launch of each app.  I have made the
> page
> >>>>>> mobile responsive.  It is also made using the Polymer web
> components and not
> >>>>>> bootstrap.
> >>>>>>
> >>>>>> Loren
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ------------------------------------------------------------------------------
> >>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>>> Perforce.
> >>>>>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>>>>> Faster operations. Version large binaries.  Built-in WAN
> optimization and
> >>>>>> the
> >>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>>>
> >>>>>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>>> _______________________________________________
> >>>>>> Exist-development mailing list
> >>>>>> Exi...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------------
> >>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>> Perforce.
> >>>>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>>>> Faster operations. Version large binaries.  Built-in WAN
> optimization and
> >>>>> the
> >>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>> _______________________________________________
> >>>>> Exist-development mailing list
> >>>>> Exi...@li...
> >>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Adam Retter
> >>>>
> >>>> eXist Developer
> >>>> { United Kingdom }
> >>>> ad...@ex...
> >>>> irc://irc.freenode.net/existdb
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> >>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>> Faster operations. Version large binaries.  Built-in WAN optimization
> and the
> >>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>> _______________________________________________
> >>> Exist-development mailing list
> >>> Exi...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "EXPath" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to exp...@go....
> > To post to this group, send email to ex...@go....
> > Visit this group at http://groups.google.com/group/expath.
> > For more options, visit https://groups.google.com/groups/opt_out.
>
> --
> You received this message because you are subscribed to the Google Groups
> "EXPath" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to exp...@go....
> To post to this group, send email to ex...@go....
> Visit this group at http://groups.google.com/group/expath.
> For more options, visit https://groups.google.com/d/optout.
>

Re: [Exist-development] [expath] Re: Start of the new look for the dashboard

[Loren C. <lor...@gm...>]

Since it is too early for a general EXPath dashboard, this will be initially for eXist only.  I am planning on designing it so that a general purpose one will be easier to implement.  I will appreciate input from the community to get enough input to make a better dashboard.  I have given some folks accounts for the wiki on my server.  If you desire an account, then send me a request.

Thanks,
Loren

On Mar 11, 2014, at 5:06 AM, Joern Turner <joe...@gm...> wrote:

> I agree with you here Joe. Especially after i shortly talked about it with Wolfgang - eXist uses some extensions and special behaviors that are not (yet?) part of expath.
> 
> However i fully agree support the idea of renewing the exist dashboard. Mostly we'd like to get rid of the Dojo dependency which makes it hard to extend and maintain. So first goal in my view should be to develop a new UI based upon web components (or to be more precise Polymer). It will also help as a migration path as polymer allows to load dependencies for components. So we can develop the new dashboard without actually having to also reimplement all the plugins in one go (which would surely be a large burden to do in one step).
> 
> One thought which is definitely worth thinking about is to make a distinction between plugins and actual apps as Loren suggested. Maybe it goes the other way round - first develop a new dashboard for eXist and later on abstract the experiences for a more general expath effort.
> 
> 
> On Tue, Mar 11, 2014 at 6:28 AM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Loren,
> 
> Thanks again for your efforts on this.  I'm not entirely convinced
> this makes sense as an EXPath project.  Are you saying that other
> EXPath implementations have the need for a GUI dashboard?  There isn't
> even an EXPath standard on package installation GUI interfaces, which
> would seem to me to be a prerequisite for a GUI that helps navigate
> between the installed packages.  Not to say this couldn't be of use
> some day, but perhaps your idea is advanced beyond the needs of the
> EXPath community at this stage.
> 
> Unless EXPath folks from other projects say otherwise, perhaps this is
> best conceived as simply a replacement for the eXist-db Dashboard?
> 
> Just my two cents.
> 
> Joe
> 
> On Thu, Mar 6, 2014 at 10:47 AM, Loren Cahlander
> <lor...@gm...> wrote:
> > Hello Joe,
> >
> > The idea of this occurred during the eXist-db pre-conference session.
> >
> >  The idea would be to abstract out the difference between the implementations and have those as control panels to get displayed just like apps get displayed.
> >
> > The control panels could then be written just like any other webapp, but calling implementation specific functions.
> >
> > Loren
> >
> > Sent from my iPad
> >
> >> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
> >>
> >> Hi Loren,
> >>
> >> Nice start.  Could you expand a bit on how you see this effort being a
> >> broader EXPath project?
> >>
> >> Joe
> >>
> >> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
> >> <lor...@gm...> wrote:
> >>> Adding the EXPath mailing list to the discussion.
> >>>
> >>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
> >>>>
> >>>> Just to add my own 2 cents.
> >>>>
> >>>> From my experience of developing 2 plugins for the dashboard, I have
> >>>> to say that it was incredibly hard to do and frustrating as I could
> >>>> not really achieve the display I wanted. I also find a very uneasy
> >>>> mismatch between plugins and XARs.
> >>>>
> >>>> I think it would be much simpler if everything was XARs but there was
> >>>> a certain XAR template, that effectively displays the XAR inline
> >>>> within the dashboard in the same way that plugins currently work. It
> >>>> would be nice if I could author a plugin, without having to really
> >>>> know anything about the dashboard. It seems to me that this technology
> >>>> already exists in the form of Web Components and we should embrace
> >>>> these and not invent something else.
> >>>>
> >>>> Regards frameworks, I don't mind which you use for the UI
> >>>> particularly, however if there is going to be any Javascript, I have a
> >>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
> >>>> have instead been having a very happy life in the last year or so by
> >>>> just using Angular.js.
> >>>>
> >>>>
> >>>>
> >>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
> >>>>> Hi Loren,
> >>>>>
> >>>>> i appreciate efforts to improve the dashboard. It was just a first quick
> >>>>> sketch back then and it's about time to think of version 2. As it's a
> >>>>> central part of the eXist user interface we should however design it
> >>>>> sensibly and gather as much input as possible.
> >>>>>
> >>>>> So first thing would be about sharing the ideas and mockups and ideally
> >>>>> allow comments to certain elements online (does anyone know a tool allowing
> >>>>> that?). Same applies to the actual code - why not setup it as a repo on the
> >>>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
> >>>>> participate.
> >>>>>
> >>>>> My first questions about your sketch:
> >>>>> am i getting you right that you'd like to make a distinction between our
> >>>>> current plugins (which handle administrative things within eXist) and the
> >>>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
> >>>>> general with the idea - however i'm not sure if i favour a toolbar for that
> >>>>> - probably i can come up with some alternative so let me think about it.
> >>>>>
> >>>>> We should also probably define some requirements:
> >>>>> - defnitely should be responsive (+1 for your effort to do so)
> >>>>> - should allow for themes. It's a matter of taste if you like shades or
> >>>>> prefer a flat look. Same applies to backgrounds. So a design should use
> >>>>> sensible CSS classes from ground up and favor a simple and clean markup
> >>>>> underneath.
> >>>>> - we have to think about icon sizes as scaling (as a result of responsive
> >>>>> design) not always works good out of the box and icons might look ugly for
> >>>>> certain resolutions. So we have to test and see if we need to apply one (or
> >>>>> several) standard size(s)
> >>>>> - we should keep highres displays in mind (retina)
> >>>>>
> >>>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
> >>>>> to keep in mind however that all the plugins would need re-implementation as
> >>>>> they depend on Dojo at the moment - this can be quite an undertaking.
> >>>>>
> >>>>> Great that you triggered the effort - it's been on my list for quite some
> >>>>> time so it's time to get it going.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Joern
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hello Folks,
> >>>>>>
> >>>>>> Please take a look at http://greatlinkup.com/foo/
> >>>>>>
> >>>>>> From our discussion at the eXist pre-conference session, I am working on a
> >>>>>> new dashboard that should be general for all EXPath implementations.
> >>>>>>
> >>>>>> The differences between implementations would be in the control panels.  I
> >>>>>> am planning on moving the control panels out of the plugins.  I am planning
> >>>>>> on placing the control panels in /db/system/controls for eXist.  The control
> >>>>>> panels will have a smaller icon and the icons will be on the top bar.  When
> >>>>>> a control panel icon is selected, then the control panel then slides down
> >>>>>> underneath the top bar.  An example of this can be seen by selecting the
> >>>>>> first icon on the top bar and see the drop-down to show the control panels.
> >>>>>>
> >>>>>> The squares below are for the launch of each app.  I have made the page
> >>>>>> mobile responsive.  It is also made using the Polymer web components and not
> >>>>>> bootstrap.
> >>>>>>
> >>>>>> Loren
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ------------------------------------------------------------------------------
> >>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>>> Perforce.
> >>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
> >>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
> >>>>>> the
> >>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>>>
> >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>>> _______________________________________________
> >>>>>> Exist-development mailing list
> >>>>>> Exi...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------------------------
> >>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>> Perforce.
> >>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
> >>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
> >>>>> the
> >>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>> _______________________________________________
> >>>>> Exist-development mailing list
> >>>>> Exi...@li...
> >>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Adam Retter
> >>>>
> >>>> eXist Developer
> >>>> { United Kingdom }
> >>>> ad...@ex...
> >>>> irc://irc.freenode.net/existdb
> >>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> >>> With Perforce, you get hassle-free workflows. Merge that actually works.
> >>> Faster operations. Version large binaries.  Built-in WAN optimization and the
> >>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>> _______________________________________________
> >>> Exist-development mailing list
> >>> Exi...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >
> > --
> > You received this message because you are subscribed to the Google Groups "EXPath" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to exp...@go....
> > To post to this group, send email to ex...@go....
> > Visit this group at http://groups.google.com/group/expath.
> > For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups "EXPath" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to exp...@go....
> To post to this group, send email to ex...@go....
> Visit this group at http://groups.google.com/group/expath.
> For more options, visit https://groups.google.com/d/optout.

Re: [Exist-development] [expath] Re: Start of the new look for the dashboard

[Michael K. <mi...@sa...>]

> 
> On Tue, Mar 11, 2014 at 6:28 AM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Loren,
> 
> Thanks again for your efforts on this.  I'm not entirely convinced
> this makes sense as an EXPath project. 

I've been rather puzzled that this conversation should be taking place on the EXPath list. I haven't followed very closely, so perhaps I've missed something, but at the moment I don't see any EXPath opportunities here.

Michael Kay
Saxonica

Re: [Exist-development] [expath] Re: Start of the new look for the dashboard

[Joern T. <joe...@gm...>]

I agree with you here Joe. Especially after i shortly talked about it with
Wolfgang - eXist uses some extensions and special behaviors that are not
(yet?) part of expath.

However i fully agree support the idea of renewing the exist dashboard.
Mostly we'd like to get rid of the Dojo dependency which makes it hard to
extend and maintain. So first goal in my view should be to develop a new UI
based upon web components (or to be more precise Polymer). It will also
help as a migration path as polymer allows to load dependencies for
components. So we can develop the new dashboard without actually having to
also reimplement all the plugins in one go (which would surely be a large
burden to do in one step).

One thought which is definitely worth thinking about is to make a
distinction between plugins and actual apps as Loren suggested. Maybe it
goes the other way round - first develop a new dashboard for eXist and
later on abstract the experiences for a more general expath effort.


On Tue, Mar 11, 2014 at 6:28 AM, Joe Wicentowski <jo...@gm...> wrote:

> Hi Loren,
>
> Thanks again for your efforts on this.  I'm not entirely convinced
> this makes sense as an EXPath project.  Are you saying that other
> EXPath implementations have the need for a GUI dashboard?  There isn't
> even an EXPath standard on package installation GUI interfaces, which
> would seem to me to be a prerequisite for a GUI that helps navigate
> between the installed packages.  Not to say this couldn't be of use
> some day, but perhaps your idea is advanced beyond the needs of the
> EXPath community at this stage.
>
> Unless EXPath folks from other projects say otherwise, perhaps this is
> best conceived as simply a replacement for the eXist-db Dashboard?
>
> Just my two cents.
>
> Joe
>
> On Thu, Mar 6, 2014 at 10:47 AM, Loren Cahlander
> <lor...@gm...> wrote:
> > Hello Joe,
> >
> > The idea of this occurred during the eXist-db pre-conference session.
> >
> >  The idea would be to abstract out the difference between the
> implementations and have those as control panels to get displayed just like
> apps get displayed.
> >
> > The control panels could then be written just like any other webapp, but
> calling implementation specific functions.
> >
> > Loren
> >
> > Sent from my iPad
> >
> >> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
> >>
> >> Hi Loren,
> >>
> >> Nice start.  Could you expand a bit on how you see this effort being a
> >> broader EXPath project?
> >>
> >> Joe
> >>
> >> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
> >> <lor...@gm...> wrote:
> >>> Adding the EXPath mailing list to the discussion.
> >>>
> >>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
> >>>>
> >>>> Just to add my own 2 cents.
> >>>>
> >>>> From my experience of developing 2 plugins for the dashboard, I have
> >>>> to say that it was incredibly hard to do and frustrating as I could
> >>>> not really achieve the display I wanted. I also find a very uneasy
> >>>> mismatch between plugins and XARs.
> >>>>
> >>>> I think it would be much simpler if everything was XARs but there was
> >>>> a certain XAR template, that effectively displays the XAR inline
> >>>> within the dashboard in the same way that plugins currently work. It
> >>>> would be nice if I could author a plugin, without having to really
> >>>> know anything about the dashboard. It seems to me that this technology
> >>>> already exists in the form of Web Components and we should embrace
> >>>> these and not invent something else.
> >>>>
> >>>> Regards frameworks, I don't mind which you use for the UI
> >>>> particularly, however if there is going to be any Javascript, I have a
> >>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
> >>>> have instead been having a very happy life in the last year or so by
> >>>> just using Angular.js.
> >>>>
> >>>>
> >>>>
> >>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
> >>>>> Hi Loren,
> >>>>>
> >>>>> i appreciate efforts to improve the dashboard. It was just a first
> quick
> >>>>> sketch back then and it's about time to think of version 2. As it's a
> >>>>> central part of the eXist user interface we should however design it
> >>>>> sensibly and gather as much input as possible.
> >>>>>
> >>>>> So first thing would be about sharing the ideas and mockups and
> ideally
> >>>>> allow comments to certain elements online (does anyone know a tool
> allowing
> >>>>> that?). Same applies to the actual code - why not setup it as a repo
> on the
> >>>>> eXistdb github (i'll ask Wolfgang about that) so more interested
> people can
> >>>>> participate.
> >>>>>
> >>>>> My first questions about your sketch:
> >>>>> am i getting you right that you'd like to make a distinction between
> our
> >>>>> current plugins (which handle administrative things within eXist)
> and the
> >>>>> actual xar applications and put them in a kind of toolbar? If so, i
> agree in
> >>>>> general with the idea - however i'm not sure if i favour a toolbar
> for that
> >>>>> - probably i can come up with some alternative so let me think about
> it.
> >>>>>
> >>>>> We should also probably define some requirements:
> >>>>> - defnitely should be responsive (+1 for your effort to do so)
> >>>>> - should allow for themes. It's a matter of taste if you like shades
> or
> >>>>> prefer a flat look. Same applies to backgrounds. So a design should
> use
> >>>>> sensible CSS classes from ground up and favor a simple and clean
> markup
> >>>>> underneath.
> >>>>> - we have to think about icon sizes as scaling (as a result of
> responsive
> >>>>> design) not always works good out of the box and icons might look
> ugly for
> >>>>> certain resolutions. So we have to test and see if we need to apply
> one (or
> >>>>> several) standard size(s)
> >>>>> - we should keep highres displays in mind (retina)
> >>>>>
> >>>>> I appreciate the use of Polymer as it seems to be ideal for the job.
> We need
> >>>>> to keep in mind however that all the plugins would need
> re-implementation as
> >>>>> they depend on Dojo at the moment - this can be quite an undertaking.
> >>>>>
> >>>>> Great that you triggered the effort - it's been on my list for quite
> some
> >>>>> time so it's time to get it going.
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Joern
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <
> lor...@gm...>
> >>>>> wrote:
> >>>>>>
> >>>>>> Hello Folks,
> >>>>>>
> >>>>>> Please take a look at http://greatlinkup.com/foo/
> >>>>>>
> >>>>>> From our discussion at the eXist pre-conference session, I am
> working on a
> >>>>>> new dashboard that should be general for all EXPath implementations.
> >>>>>>
> >>>>>> The differences between implementations would be in the control
> panels.  I
> >>>>>> am planning on moving the control panels out of the plugins.  I am
> planning
> >>>>>> on placing the control panels in /db/system/controls for eXist.
>  The control
> >>>>>> panels will have a smaller icon and the icons will be on the top
> bar.  When
> >>>>>> a control panel icon is selected, then the control panel then
> slides down
> >>>>>> underneath the top bar.  An example of this can be seen by
> selecting the
> >>>>>> first icon on the top bar and see the drop-down to show the control
> panels.
> >>>>>>
> >>>>>> The squares below are for the launch of each app.  I have made the
> page
> >>>>>> mobile responsive.  It is also made using the Polymer web
> components and not
> >>>>>> bootstrap.
> >>>>>>
> >>>>>> Loren
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ------------------------------------------------------------------------------
> >>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>>> Perforce.
> >>>>>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>>>>> Faster operations. Version large binaries.  Built-in WAN
> optimization and
> >>>>>> the
> >>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>>>
> >>>>>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>>> _______________________________________________
> >>>>>> Exist-development mailing list
> >>>>>> Exi...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------------
> >>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> >>>>> Perforce.
> >>>>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>>>> Faster operations. Version large binaries.  Built-in WAN
> optimization and
> >>>>> the
> >>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>>>> _______________________________________________
> >>>>> Exist-development mailing list
> >>>>> Exi...@li...
> >>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Adam Retter
> >>>>
> >>>> eXist Developer
> >>>> { United Kingdom }
> >>>> ad...@ex...
> >>>> irc://irc.freenode.net/existdb
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> >>> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> >>> Faster operations. Version large binaries.  Built-in WAN optimization
> and the
> >>> freedom to use Git, Perforce or both. Make the move to Perforce.
> >>>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> >>> _______________________________________________
> >>> Exist-development mailing list
> >>> Exi...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/exist-development
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "EXPath" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to exp...@go....
> > To post to this group, send email to ex...@go....
> > Visit this group at http://groups.google.com/group/expath.
> > For more options, visit https://groups.google.com/groups/opt_out.
>

Re: [Exist-development] [expath] Re: Start of the new look for the dashboard

[Joe W. <jo...@gm...>]

Hi Loren,

Thanks again for your efforts on this.  I'm not entirely convinced
this makes sense as an EXPath project.  Are you saying that other
EXPath implementations have the need for a GUI dashboard?  There isn't
even an EXPath standard on package installation GUI interfaces, which
would seem to me to be a prerequisite for a GUI that helps navigate
between the installed packages.  Not to say this couldn't be of use
some day, but perhaps your idea is advanced beyond the needs of the
EXPath community at this stage.

Unless EXPath folks from other projects say otherwise, perhaps this is
best conceived as simply a replacement for the eXist-db Dashboard?

Just my two cents.

Joe

On Thu, Mar 6, 2014 at 10:47 AM, Loren Cahlander
<lor...@gm...> wrote:
> Hello Joe,
>
> The idea of this occurred during the eXist-db pre-conference session.
>
>  The idea would be to abstract out the difference between the implementations and have those as control panels to get displayed just like apps get displayed.
>
> The control panels could then be written just like any other webapp, but calling implementation specific functions.
>
> Loren
>
> Sent from my iPad
>
>> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
>>
>> Hi Loren,
>>
>> Nice start.  Could you expand a bit on how you see this effort being a
>> broader EXPath project?
>>
>> Joe
>>
>> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
>> <lor...@gm...> wrote:
>>> Adding the EXPath mailing list to the discussion.
>>>
>>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
>>>>
>>>> Just to add my own 2 cents.
>>>>
>>>> From my experience of developing 2 plugins for the dashboard, I have
>>>> to say that it was incredibly hard to do and frustrating as I could
>>>> not really achieve the display I wanted. I also find a very uneasy
>>>> mismatch between plugins and XARs.
>>>>
>>>> I think it would be much simpler if everything was XARs but there was
>>>> a certain XAR template, that effectively displays the XAR inline
>>>> within the dashboard in the same way that plugins currently work. It
>>>> would be nice if I could author a plugin, without having to really
>>>> know anything about the dashboard. It seems to me that this technology
>>>> already exists in the form of Web Components and we should embrace
>>>> these and not invent something else.
>>>>
>>>> Regards frameworks, I don't mind which you use for the UI
>>>> particularly, however if there is going to be any Javascript, I have a
>>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
>>>> have instead been having a very happy life in the last year or so by
>>>> just using Angular.js.
>>>>
>>>>
>>>>
>>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>>>>> Hi Loren,
>>>>>
>>>>> i appreciate efforts to improve the dashboard. It was just a first quick
>>>>> sketch back then and it's about time to think of version 2. As it's a
>>>>> central part of the eXist user interface we should however design it
>>>>> sensibly and gather as much input as possible.
>>>>>
>>>>> So first thing would be about sharing the ideas and mockups and ideally
>>>>> allow comments to certain elements online (does anyone know a tool allowing
>>>>> that?). Same applies to the actual code - why not setup it as a repo on the
>>>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>>>>> participate.
>>>>>
>>>>> My first questions about your sketch:
>>>>> am i getting you right that you'd like to make a distinction between our
>>>>> current plugins (which handle administrative things within eXist) and the
>>>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>>>>> general with the idea - however i'm not sure if i favour a toolbar for that
>>>>> - probably i can come up with some alternative so let me think about it.
>>>>>
>>>>> We should also probably define some requirements:
>>>>> - defnitely should be responsive (+1 for your effort to do so)
>>>>> - should allow for themes. It's a matter of taste if you like shades or
>>>>> prefer a flat look. Same applies to backgrounds. So a design should use
>>>>> sensible CSS classes from ground up and favor a simple and clean markup
>>>>> underneath.
>>>>> - we have to think about icon sizes as scaling (as a result of responsive
>>>>> design) not always works good out of the box and icons might look ugly for
>>>>> certain resolutions. So we have to test and see if we need to apply one (or
>>>>> several) standard size(s)
>>>>> - we should keep highres displays in mind (retina)
>>>>>
>>>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>>>>> to keep in mind however that all the plugins would need re-implementation as
>>>>> they depend on Dojo at the moment - this can be quite an undertaking.
>>>>>
>>>>> Great that you triggered the effort - it's been on my list for quite some
>>>>> time so it's time to get it going.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Joern
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>>>>> wrote:
>>>>>>
>>>>>> Hello Folks,
>>>>>>
>>>>>> Please take a look at http://greatlinkup.com/foo/
>>>>>>
>>>>>> From our discussion at the eXist pre-conference session, I am working on a
>>>>>> new dashboard that should be general for all EXPath implementations.
>>>>>>
>>>>>> The differences between implementations would be in the control panels.  I
>>>>>> am planning on moving the control panels out of the plugins.  I am planning
>>>>>> on placing the control panels in /db/system/controls for eXist.  The control
>>>>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>>>>> a control panel icon is selected, then the control panel then slides down
>>>>>> underneath the top bar.  An example of this can be seen by selecting the
>>>>>> first icon on the top bar and see the drop-down to show the control panels.
>>>>>>
>>>>>> The squares below are for the launch of each app.  I have made the page
>>>>>> mobile responsive.  It is also made using the Polymer web components and not
>>>>>> bootstrap.
>>>>>>
>>>>>> Loren
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>>> Perforce.
>>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>>> the
>>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>>>
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Exist-development mailing list
>>>>>> Exi...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>> Perforce.
>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>> the
>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Exist-development mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Adam Retter
>>>>
>>>> eXist Developer
>>>> { United Kingdom }
>>>> ad...@ex...
>>>> irc://irc.freenode.net/existdb
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>
> --
> You received this message because you are subscribed to the Google Groups "EXPath" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to exp...@go....
> To post to this group, send email to ex...@go....
> Visit this group at http://groups.google.com/group/expath.
> For more options, visit https://groups.google.com/groups/opt_out.

Re: [Exist-development] Start of the new look for the dashboard

[Loren C. <lor...@gm...>]

I just made the wiki pages viewable by all.

On Mar 9, 2014, at 10:47 AM, Loren Cahlander <lor...@gm...> wrote:

> I have the following website available as a wiki for this project: https://greatlinkup.com/wiki.  
> 
> 	https://greatlinkup.com/wiki/projects/expathdashboard/EXPath_Dashboard.html
> 
> For those of you that are interested in collaborating on this general purpose EXPath Dashboard Web App:
> Let me know and I will create an account for you
> We will start with identifying requirements
> 
> 
> Loren Cahlander
> Principal
> GreatLinkUp, LLC
> cah...@gr...
> lor...@gm...
> +1-651-747-6910
> 
> 
> 
> On Mar 6, 2014, at 11:47 AM, Loren Cahlander <lor...@gm...> wrote:
> 
>> Hello Joe,
>> 
>> The idea of this occurred during the eXist-db pre-conference session.
>> 
>> The idea would be to abstract out the difference between the implementations and have those as control panels to get displayed just like apps get displayed.
>> 
>> The control panels could then be written just like any other webapp, but calling implementation specific functions.
>> 
>> Loren
>> 
>> Sent from my iPad
>> 
>>> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
>>> 
>>> Hi Loren,
>>> 
>>> Nice start.  Could you expand a bit on how you see this effort being a
>>> broader EXPath project?
>>> 
>>> Joe
>>> 
>>> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
>>> <lor...@gm...> wrote:
>>>> Adding the EXPath mailing list to the discussion.
>>>> 
>>>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
>>>>> 
>>>>> Just to add my own 2 cents.
>>>>> 
>>>>> From my experience of developing 2 plugins for the dashboard, I have
>>>>> to say that it was incredibly hard to do and frustrating as I could
>>>>> not really achieve the display I wanted. I also find a very uneasy
>>>>> mismatch between plugins and XARs.
>>>>> 
>>>>> I think it would be much simpler if everything was XARs but there was
>>>>> a certain XAR template, that effectively displays the XAR inline
>>>>> within the dashboard in the same way that plugins currently work. It
>>>>> would be nice if I could author a plugin, without having to really
>>>>> know anything about the dashboard. It seems to me that this technology
>>>>> already exists in the form of Web Components and we should embrace
>>>>> these and not invent something else.
>>>>> 
>>>>> Regards frameworks, I don't mind which you use for the UI
>>>>> particularly, however if there is going to be any Javascript, I have a
>>>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
>>>>> have instead been having a very happy life in the last year or so by
>>>>> just using Angular.js.
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>>>>>> Hi Loren,
>>>>>> 
>>>>>> i appreciate efforts to improve the dashboard. It was just a first quick
>>>>>> sketch back then and it's about time to think of version 2. As it's a
>>>>>> central part of the eXist user interface we should however design it
>>>>>> sensibly and gather as much input as possible.
>>>>>> 
>>>>>> So first thing would be about sharing the ideas and mockups and ideally
>>>>>> allow comments to certain elements online (does anyone know a tool allowing
>>>>>> that?). Same applies to the actual code - why not setup it as a repo on the
>>>>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>>>>>> participate.
>>>>>> 
>>>>>> My first questions about your sketch:
>>>>>> am i getting you right that you'd like to make a distinction between our
>>>>>> current plugins (which handle administrative things within eXist) and the
>>>>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>>>>>> general with the idea - however i'm not sure if i favour a toolbar for that
>>>>>> - probably i can come up with some alternative so let me think about it.
>>>>>> 
>>>>>> We should also probably define some requirements:
>>>>>> - defnitely should be responsive (+1 for your effort to do so)
>>>>>> - should allow for themes. It's a matter of taste if you like shades or
>>>>>> prefer a flat look. Same applies to backgrounds. So a design should use
>>>>>> sensible CSS classes from ground up and favor a simple and clean markup
>>>>>> underneath.
>>>>>> - we have to think about icon sizes as scaling (as a result of responsive
>>>>>> design) not always works good out of the box and icons might look ugly for
>>>>>> certain resolutions. So we have to test and see if we need to apply one (or
>>>>>> several) standard size(s)
>>>>>> - we should keep highres displays in mind (retina)
>>>>>> 
>>>>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>>>>>> to keep in mind however that all the plugins would need re-implementation as
>>>>>> they depend on Dojo at the moment - this can be quite an undertaking.
>>>>>> 
>>>>>> Great that you triggered the effort - it's been on my list for quite some
>>>>>> time so it's time to get it going.
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> Joern
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>>>>>> wrote:
>>>>>>> 
>>>>>>> Hello Folks,
>>>>>>> 
>>>>>>> Please take a look at http://greatlinkup.com/foo/
>>>>>>> 
>>>>>>> From our discussion at the eXist pre-conference session, I am working on a
>>>>>>> new dashboard that should be general for all EXPath implementations.
>>>>>>> 
>>>>>>> The differences between implementations would be in the control panels.  I
>>>>>>> am planning on moving the control panels out of the plugins.  I am planning
>>>>>>> on placing the control panels in /db/system/controls for eXist.  The control
>>>>>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>>>>>> a control panel icon is selected, then the control panel then slides down
>>>>>>> underneath the top bar.  An example of this can be seen by selecting the
>>>>>>> first icon on the top bar and see the drop-down to show the control panels.
>>>>>>> 
>>>>>>> The squares below are for the launch of each app.  I have made the page
>>>>>>> mobile responsive.  It is also made using the Polymer web components and not
>>>>>>> bootstrap.
>>>>>>> 
>>>>>>> Loren
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>>>> Perforce.
>>>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>>>> the
>>>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>>>> 
>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>>>> _______________________________________________
>>>>>>> Exist-development mailing list
>>>>>>> Exi...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ------------------------------------------------------------------------------
>>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>>> Perforce.
>>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>>> the
>>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Exist-development mailing list
>>>>>> Exi...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Adam Retter
>>>>> 
>>>>> eXist Developer
>>>>> { United Kingdom }
>>>>> ad...@ex...
>>>>> irc://irc.freenode.net/existdb
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Exist-development mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
> 

Re: [Exist-development] Start of the new look for the dashboard

[Loren C. <lor...@gm...>]

I have the following website available as a wiki for this project: https://greatlinkup.com/wiki.  

	https://greatlinkup.com/wiki/projects/expathdashboard/EXPath_Dashboard.html

For those of you that are interested in collaborating on this general purpose EXPath Dashboard Web App:
Let me know and I will create an account for you
We will start with identifying requirements


Loren Cahlander
Principal
GreatLinkUp, LLC
cah...@gr...
lor...@gm...
+1-651-747-6910



On Mar 6, 2014, at 11:47 AM, Loren Cahlander <lor...@gm...> wrote:

> Hello Joe,
> 
> The idea of this occurred during the eXist-db pre-conference session.
> 
> The idea would be to abstract out the difference between the implementations and have those as control panels to get displayed just like apps get displayed.
> 
> The control panels could then be written just like any other webapp, but calling implementation specific functions.
> 
> Loren
> 
> Sent from my iPad
> 
>> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
>> 
>> Hi Loren,
>> 
>> Nice start.  Could you expand a bit on how you see this effort being a
>> broader EXPath project?
>> 
>> Joe
>> 
>> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
>> <lor...@gm...> wrote:
>>> Adding the EXPath mailing list to the discussion.
>>> 
>>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
>>>> 
>>>> Just to add my own 2 cents.
>>>> 
>>>> From my experience of developing 2 plugins for the dashboard, I have
>>>> to say that it was incredibly hard to do and frustrating as I could
>>>> not really achieve the display I wanted. I also find a very uneasy
>>>> mismatch between plugins and XARs.
>>>> 
>>>> I think it would be much simpler if everything was XARs but there was
>>>> a certain XAR template, that effectively displays the XAR inline
>>>> within the dashboard in the same way that plugins currently work. It
>>>> would be nice if I could author a plugin, without having to really
>>>> know anything about the dashboard. It seems to me that this technology
>>>> already exists in the form of Web Components and we should embrace
>>>> these and not invent something else.
>>>> 
>>>> Regards frameworks, I don't mind which you use for the UI
>>>> particularly, however if there is going to be any Javascript, I have a
>>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
>>>> have instead been having a very happy life in the last year or so by
>>>> just using Angular.js.
>>>> 
>>>> 
>>>> 
>>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>>>>> Hi Loren,
>>>>> 
>>>>> i appreciate efforts to improve the dashboard. It was just a first quick
>>>>> sketch back then and it's about time to think of version 2. As it's a
>>>>> central part of the eXist user interface we should however design it
>>>>> sensibly and gather as much input as possible.
>>>>> 
>>>>> So first thing would be about sharing the ideas and mockups and ideally
>>>>> allow comments to certain elements online (does anyone know a tool allowing
>>>>> that?). Same applies to the actual code - why not setup it as a repo on the
>>>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>>>>> participate.
>>>>> 
>>>>> My first questions about your sketch:
>>>>> am i getting you right that you'd like to make a distinction between our
>>>>> current plugins (which handle administrative things within eXist) and the
>>>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>>>>> general with the idea - however i'm not sure if i favour a toolbar for that
>>>>> - probably i can come up with some alternative so let me think about it.
>>>>> 
>>>>> We should also probably define some requirements:
>>>>> - defnitely should be responsive (+1 for your effort to do so)
>>>>> - should allow for themes. It's a matter of taste if you like shades or
>>>>> prefer a flat look. Same applies to backgrounds. So a design should use
>>>>> sensible CSS classes from ground up and favor a simple and clean markup
>>>>> underneath.
>>>>> - we have to think about icon sizes as scaling (as a result of responsive
>>>>> design) not always works good out of the box and icons might look ugly for
>>>>> certain resolutions. So we have to test and see if we need to apply one (or
>>>>> several) standard size(s)
>>>>> - we should keep highres displays in mind (retina)
>>>>> 
>>>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>>>>> to keep in mind however that all the plugins would need re-implementation as
>>>>> they depend on Dojo at the moment - this can be quite an undertaking.
>>>>> 
>>>>> Great that you triggered the effort - it's been on my list for quite some
>>>>> time so it's time to get it going.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Joern
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>>>>> wrote:
>>>>>> 
>>>>>> Hello Folks,
>>>>>> 
>>>>>> Please take a look at http://greatlinkup.com/foo/
>>>>>> 
>>>>>> From our discussion at the eXist pre-conference session, I am working on a
>>>>>> new dashboard that should be general for all EXPath implementations.
>>>>>> 
>>>>>> The differences between implementations would be in the control panels.  I
>>>>>> am planning on moving the control panels out of the plugins.  I am planning
>>>>>> on placing the control panels in /db/system/controls for eXist.  The control
>>>>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>>>>> a control panel icon is selected, then the control panel then slides down
>>>>>> underneath the top bar.  An example of this can be seen by selecting the
>>>>>> first icon on the top bar and see the drop-down to show the control panels.
>>>>>> 
>>>>>> The squares below are for the launch of each app.  I have made the page
>>>>>> mobile responsive.  It is also made using the Polymer web components and not
>>>>>> bootstrap.
>>>>>> 
>>>>>> Loren
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ------------------------------------------------------------------------------
>>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>>> Perforce.
>>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>>> the
>>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>>> 
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Exist-development mailing list
>>>>>> Exi...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>>> 
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>> Perforce.
>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>> the
>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Exist-development mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Adam Retter
>>>> 
>>>> eXist Developer
>>>> { United Kingdom }
>>>> ad...@ex...
>>>> irc://irc.freenode.net/existdb
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Start of the new look for the dashboard

[Loren C. <lor...@gm...>]

Hello Joe,

The idea of this occurred during the eXist-db pre-conference session.

 The idea would be to abstract out the difference between the implementations and have those as control panels to get displayed just like apps get displayed.

The control panels could then be written just like any other webapp, but calling implementation specific functions.

Loren

Sent from my iPad

> On Mar 6, 2014, at 11:34 AM, Joe Wicentowski <jo...@gm...> wrote:
> 
> Hi Loren,
> 
> Nice start.  Could you expand a bit on how you see this effort being a
> broader EXPath project?
> 
> Joe
> 
> On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
> <lor...@gm...> wrote:
>> Adding the EXPath mailing list to the discussion.
>> 
>>> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
>>> 
>>> Just to add my own 2 cents.
>>> 
>>> From my experience of developing 2 plugins for the dashboard, I have
>>> to say that it was incredibly hard to do and frustrating as I could
>>> not really achieve the display I wanted. I also find a very uneasy
>>> mismatch between plugins and XARs.
>>> 
>>> I think it would be much simpler if everything was XARs but there was
>>> a certain XAR template, that effectively displays the XAR inline
>>> within the dashboard in the same way that plugins currently work. It
>>> would be nice if I could author a plugin, without having to really
>>> know anything about the dashboard. It seems to me that this technology
>>> already exists in the form of Web Components and we should embrace
>>> these and not invent something else.
>>> 
>>> Regards frameworks, I don't mind which you use for the UI
>>> particularly, however if there is going to be any Javascript, I have a
>>> strong preference to avoid Dojo entirely (and if possible jQuery). I
>>> have instead been having a very happy life in the last year or so by
>>> just using Angular.js.
>>> 
>>> 
>>> 
>>>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>>>> Hi Loren,
>>>> 
>>>> i appreciate efforts to improve the dashboard. It was just a first quick
>>>> sketch back then and it's about time to think of version 2. As it's a
>>>> central part of the eXist user interface we should however design it
>>>> sensibly and gather as much input as possible.
>>>> 
>>>> So first thing would be about sharing the ideas and mockups and ideally
>>>> allow comments to certain elements online (does anyone know a tool allowing
>>>> that?). Same applies to the actual code - why not setup it as a repo on the
>>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>>>> participate.
>>>> 
>>>> My first questions about your sketch:
>>>> am i getting you right that you'd like to make a distinction between our
>>>> current plugins (which handle administrative things within eXist) and the
>>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>>>> general with the idea - however i'm not sure if i favour a toolbar for that
>>>> - probably i can come up with some alternative so let me think about it.
>>>> 
>>>> We should also probably define some requirements:
>>>> - defnitely should be responsive (+1 for your effort to do so)
>>>> - should allow for themes. It's a matter of taste if you like shades or
>>>> prefer a flat look. Same applies to backgrounds. So a design should use
>>>> sensible CSS classes from ground up and favor a simple and clean markup
>>>> underneath.
>>>> - we have to think about icon sizes as scaling (as a result of responsive
>>>> design) not always works good out of the box and icons might look ugly for
>>>> certain resolutions. So we have to test and see if we need to apply one (or
>>>> several) standard size(s)
>>>> - we should keep highres displays in mind (retina)
>>>> 
>>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>>>> to keep in mind however that all the plugins would need re-implementation as
>>>> they depend on Dojo at the moment - this can be quite an undertaking.
>>>> 
>>>> Great that you triggered the effort - it's been on my list for quite some
>>>> time so it's time to get it going.
>>>> 
>>>> Thanks,
>>>> 
>>>> Joern
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>>>> wrote:
>>>>> 
>>>>> Hello Folks,
>>>>> 
>>>>> Please take a look at http://greatlinkup.com/foo/
>>>>> 
>>>>> From our discussion at the eXist pre-conference session, I am working on a
>>>>> new dashboard that should be general for all EXPath implementations.
>>>>> 
>>>>> The differences between implementations would be in the control panels.  I
>>>>> am planning on moving the control panels out of the plugins.  I am planning
>>>>> on placing the control panels in /db/system/controls for eXist.  The control
>>>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>>>> a control panel icon is selected, then the control panel then slides down
>>>>> underneath the top bar.  An example of this can be seen by selecting the
>>>>> first icon on the top bar and see the drop-down to show the control panels.
>>>>> 
>>>>> The squares below are for the launch of each app.  I have made the page
>>>>> mobile responsive.  It is also made using the Polymer web components and not
>>>>> bootstrap.
>>>>> 
>>>>> Loren
>>>>> 
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>>> Perforce.
>>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>>> the
>>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>> 
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>>> _______________________________________________
>>>>> Exist-development mailing list
>>>>> Exi...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>> 
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>> Perforce.
>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>> the
>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Exist-development mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Adam Retter
>>> 
>>> eXist Developer
>>> { United Kingdom }
>>> ad...@ex...
>>> irc://irc.freenode.net/existdb
>> 
>> 
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Start of the new look for the dashboard

[Joe W. <jo...@gm...>]

Hi Loren,

Nice start.  Could you expand a bit on how you see this effort being a
broader EXPath project?

Joe

On Thu, Mar 6, 2014 at 8:19 AM, Loren Cahlander
<lor...@gm...> wrote:
> Adding the EXPath mailing list to the discussion.
>
> On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:
>
>> Just to add my own 2 cents.
>>
>> From my experience of developing 2 plugins for the dashboard, I have
>> to say that it was incredibly hard to do and frustrating as I could
>> not really achieve the display I wanted. I also find a very uneasy
>> mismatch between plugins and XARs.
>>
>> I think it would be much simpler if everything was XARs but there was
>> a certain XAR template, that effectively displays the XAR inline
>> within the dashboard in the same way that plugins currently work. It
>> would be nice if I could author a plugin, without having to really
>> know anything about the dashboard. It seems to me that this technology
>> already exists in the form of Web Components and we should embrace
>> these and not invent something else.
>>
>> Regards frameworks, I don't mind which you use for the UI
>> particularly, however if there is going to be any Javascript, I have a
>> strong preference to avoid Dojo entirely (and if possible jQuery). I
>> have instead been having a very happy life in the last year or so by
>> just using Angular.js.
>>
>>
>>
>> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>>> Hi Loren,
>>>
>>> i appreciate efforts to improve the dashboard. It was just a first quick
>>> sketch back then and it's about time to think of version 2. As it's a
>>> central part of the eXist user interface we should however design it
>>> sensibly and gather as much input as possible.
>>>
>>> So first thing would be about sharing the ideas and mockups and ideally
>>> allow comments to certain elements online (does anyone know a tool allowing
>>> that?). Same applies to the actual code - why not setup it as a repo on the
>>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>>> participate.
>>>
>>> My first questions about your sketch:
>>> am i getting you right that you'd like to make a distinction between our
>>> current plugins (which handle administrative things within eXist) and the
>>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>>> general with the idea - however i'm not sure if i favour a toolbar for that
>>> - probably i can come up with some alternative so let me think about it.
>>>
>>> We should also probably define some requirements:
>>> - defnitely should be responsive (+1 for your effort to do so)
>>> - should allow for themes. It's a matter of taste if you like shades or
>>> prefer a flat look. Same applies to backgrounds. So a design should use
>>> sensible CSS classes from ground up and favor a simple and clean markup
>>> underneath.
>>> - we have to think about icon sizes as scaling (as a result of responsive
>>> design) not always works good out of the box and icons might look ugly for
>>> certain resolutions. So we have to test and see if we need to apply one (or
>>> several) standard size(s)
>>> - we should keep highres displays in mind (retina)
>>>
>>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>>> to keep in mind however that all the plugins would need re-implementation as
>>> they depend on Dojo at the moment - this can be quite an undertaking.
>>>
>>> Great that you triggered the effort - it's been on my list for quite some
>>> time so it's time to get it going.
>>>
>>> Thanks,
>>>
>>> Joern
>>>
>>>
>>>
>>>
>>>
>>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>>> wrote:
>>>>
>>>> Hello Folks,
>>>>
>>>> Please take a look at http://greatlinkup.com/foo/
>>>>
>>>> From our discussion at the eXist pre-conference session, I am working on a
>>>> new dashboard that should be general for all EXPath implementations.
>>>>
>>>> The differences between implementations would be in the control panels.  I
>>>> am planning on moving the control panels out of the plugins.  I am planning
>>>> on placing the control panels in /db/system/controls for eXist.  The control
>>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>>> a control panel icon is selected, then the control panel then slides down
>>>> underneath the top bar.  An example of this can be seen by selecting the
>>>> first icon on the top bar and see the drop-down to show the control panels.
>>>>
>>>> The squares below are for the launch of each app.  I have made the page
>>>> mobile responsive.  It is also made using the Polymer web components and not
>>>> bootstrap.
>>>>
>>>> Loren
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>>> Perforce.
>>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>>> the
>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Exist-development mailing list
>>>> Exi...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>> Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>> the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>>
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

[Exist-development] LDAP Groups

[Dulip W. <wit...@as...>]

Hi Adam,
I have a  issue with the LDAP groups for the current trunk (2013.03.06)

When I create user,  I have configured the security.xml so that a ldap 
user is created as a  group user belonging  to "biblio.users"
So tha entry looks like this.
So I have the configuration like this.

  <group name="domain us...@ad..."/>
   <group name="biblio.users"/>


But when I now run  script  to create a user collection in a folder, 
which belong to biblio.users group, the LDAP user does not have the 
rights to create.

xquery version "3.0";
let $user := "dul...@ad..."
return
sm:get-permissions(xs:anyURI("/db/resources/users")),
xmldb:create-collection("/resources/users", 
"dul...@ad..."),
sm:chgrp(xs:anyURI("/resources/users/dul...@ad..."), 
"biblio.users"),
sm:get-permissions(xs:anyURI("/resources/users/dul...@ad...")),

exerr:ERROR Permission to modify permissions is denied for user 
'dul...@ad...' on 
'/resources/users/dul...@ad...': You do not have 
appropriate access rights to modify permissions on this object [at line 
9, column 1]

I earlier assumed, that if I am in both biblio.users and domain 
us...@ad... , that I should be able to change the 
permissions, and it worked.  Am I doing something wrong against the 
newer security model  ?


If I have only   this <group name="biblio.users"/> the script runs.


<sm:permission xmlns:sm="http://exist-db.org/xquery/securitymanager" 
owner="editor" group="biblio.users" mode="rwxrwxrwx">
<sm:acl entries="0"/>
</sm:permission>
/db/resources/users/dul...@ad...
<sm:permission xmlns:sm="http://exist-db.org/xquery/securitymanager" 
owner="dul...@ad..." group="biblio.users" 
mode="rwxr-xr-x">
<sm:acl entries="0"/>
</sm:permission>

Re: [Exist-development] Start of the new look for the dashboard

[Loren C. <lor...@gm...>]

Adding the EXPath mailing list to the discussion.

On Mar 6, 2014, at 6:48 AM, Adam Retter <ad...@ex...> wrote:

> Just to add my own 2 cents.
> 
> From my experience of developing 2 plugins for the dashboard, I have
> to say that it was incredibly hard to do and frustrating as I could
> not really achieve the display I wanted. I also find a very uneasy
> mismatch between plugins and XARs.
> 
> I think it would be much simpler if everything was XARs but there was
> a certain XAR template, that effectively displays the XAR inline
> within the dashboard in the same way that plugins currently work. It
> would be nice if I could author a plugin, without having to really
> know anything about the dashboard. It seems to me that this technology
> already exists in the form of Web Components and we should embrace
> these and not invent something else.
> 
> Regards frameworks, I don't mind which you use for the UI
> particularly, however if there is going to be any Javascript, I have a
> strong preference to avoid Dojo entirely (and if possible jQuery). I
> have instead been having a very happy life in the last year or so by
> just using Angular.js.
> 
> 
> 
> On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
>> Hi Loren,
>> 
>> i appreciate efforts to improve the dashboard. It was just a first quick
>> sketch back then and it's about time to think of version 2. As it's a
>> central part of the eXist user interface we should however design it
>> sensibly and gather as much input as possible.
>> 
>> So first thing would be about sharing the ideas and mockups and ideally
>> allow comments to certain elements online (does anyone know a tool allowing
>> that?). Same applies to the actual code - why not setup it as a repo on the
>> eXistdb github (i'll ask Wolfgang about that) so more interested people can
>> participate.
>> 
>> My first questions about your sketch:
>> am i getting you right that you'd like to make a distinction between our
>> current plugins (which handle administrative things within eXist) and the
>> actual xar applications and put them in a kind of toolbar? If so, i agree in
>> general with the idea - however i'm not sure if i favour a toolbar for that
>> - probably i can come up with some alternative so let me think about it.
>> 
>> We should also probably define some requirements:
>> - defnitely should be responsive (+1 for your effort to do so)
>> - should allow for themes. It's a matter of taste if you like shades or
>> prefer a flat look. Same applies to backgrounds. So a design should use
>> sensible CSS classes from ground up and favor a simple and clean markup
>> underneath.
>> - we have to think about icon sizes as scaling (as a result of responsive
>> design) not always works good out of the box and icons might look ugly for
>> certain resolutions. So we have to test and see if we need to apply one (or
>> several) standard size(s)
>> - we should keep highres displays in mind (retina)
>> 
>> I appreciate the use of Polymer as it seems to be ideal for the job. We need
>> to keep in mind however that all the plugins would need re-implementation as
>> they depend on Dojo at the moment - this can be quite an undertaking.
>> 
>> Great that you triggered the effort - it's been on my list for quite some
>> time so it's time to get it going.
>> 
>> Thanks,
>> 
>> Joern
>> 
>> 
>> 
>> 
>> 
>> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
>> wrote:
>>> 
>>> Hello Folks,
>>> 
>>> Please take a look at http://greatlinkup.com/foo/
>>> 
>>> From our discussion at the eXist pre-conference session, I am working on a
>>> new dashboard that should be general for all EXPath implementations.
>>> 
>>> The differences between implementations would be in the control panels.  I
>>> am planning on moving the control panels out of the plugins.  I am planning
>>> on placing the control panels in /db/system/controls for eXist.  The control
>>> panels will have a smaller icon and the icons will be on the top bar.  When
>>> a control panel icon is selected, then the control panel then slides down
>>> underneath the top bar.  An example of this can be seen by selecting the
>>> first icon on the top bar and see the drop-down to show the control panels.
>>> 
>>> The squares below are for the launch of each app.  I have made the page
>>> mobile responsive.  It is also made using the Polymer web components and not
>>> bootstrap.
>>> 
>>> Loren
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>> Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>> Faster operations. Version large binaries.  Built-in WAN optimization and
>>> the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>> Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries.  Built-in WAN optimization and
>> the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>> 
> 
> 
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

Re: [Exist-development] Start of the new look for the dashboard

[Adam R. <ad...@ex...>]

Just to add my own 2 cents.

>From my experience of developing 2 plugins for the dashboard, I have
to say that it was incredibly hard to do and frustrating as I could
not really achieve the display I wanted. I also find a very uneasy
mismatch between plugins and XARs.

I think it would be much simpler if everything was XARs but there was
a certain XAR template, that effectively displays the XAR inline
within the dashboard in the same way that plugins currently work. It
would be nice if I could author a plugin, without having to really
know anything about the dashboard. It seems to me that this technology
already exists in the form of Web Components and we should embrace
these and not invent something else.

Regards frameworks, I don't mind which you use for the UI
particularly, however if there is going to be any Javascript, I have a
strong preference to avoid Dojo entirely (and if possible jQuery). I
have instead been having a very happy life in the last year or so by
just using Angular.js.



On 6 March 2014 10:10, Joern Turner <joe...@gm...> wrote:
> Hi Loren,
>
> i appreciate efforts to improve the dashboard. It was just a first quick
> sketch back then and it's about time to think of version 2. As it's a
> central part of the eXist user interface we should however design it
> sensibly and gather as much input as possible.
>
> So first thing would be about sharing the ideas and mockups and ideally
> allow comments to certain elements online (does anyone know a tool allowing
> that?). Same applies to the actual code - why not setup it as a repo on the
> eXistdb github (i'll ask Wolfgang about that) so more interested people can
> participate.
>
> My first questions about your sketch:
> am i getting you right that you'd like to make a distinction between our
> current plugins (which handle administrative things within eXist) and the
> actual xar applications and put them in a kind of toolbar? If so, i agree in
> general with the idea - however i'm not sure if i favour a toolbar for that
> - probably i can come up with some alternative so let me think about it.
>
> We should also probably define some requirements:
> - defnitely should be responsive (+1 for your effort to do so)
> - should allow for themes. It's a matter of taste if you like shades or
> prefer a flat look. Same applies to backgrounds. So a design should use
> sensible CSS classes from ground up and favor a simple and clean markup
> underneath.
> - we have to think about icon sizes as scaling (as a result of responsive
> design) not always works good out of the box and icons might look ugly for
> certain resolutions. So we have to test and see if we need to apply one (or
> several) standard size(s)
> - we should keep highres displays in mind (retina)
>
> I appreciate the use of Polymer as it seems to be ideal for the job. We need
> to keep in mind however that all the plugins would need re-implementation as
> they depend on Dojo at the moment - this can be quite an undertaking.
>
> Great that you triggered the effort - it's been on my list for quite some
> time so it's time to get it going.
>
> Thanks,
>
> Joern
>
>
>
>
>
> On Thu, Mar 6, 2014 at 4:49 AM, Loren Cahlander <lor...@gm...>
> wrote:
>>
>> Hello Folks,
>>
>> Please take a look at http://greatlinkup.com/foo/
>>
>> From our discussion at the eXist pre-conference session, I am working on a
>> new dashboard that should be general for all EXPath implementations.
>>
>> The differences between implementations would be in the control panels.  I
>> am planning on moving the control panels out of the plugins.  I am planning
>> on placing the control panels in /db/system/controls for eXist.  The control
>> panels will have a smaller icon and the icons will be on the top bar.  When
>> a control panel icon is selected, then the control panel then slides down
>> underneath the top bar.  An example of this can be seen by selecting the
>> first icon on the top bar and see the drop-down to show the control panels.
>>
>> The squares below are for the launch of each app.  I have made the page
>> mobile responsive.  It is also made using the Polymer web components and not
>> bootstrap.
>>
>> Loren
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>> Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries.  Built-in WAN optimization and
>> the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb