From: Loren C. <lor...@gm...> - 2014-03-09 14:47:48
|
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 |